Hi guys as you know our Xperia 2011 use yaffs2 for the mtd partitions, but it doesn't have too.
I bit the bullet, formated system, cache and data as ext4 from updater-script, knowing that alliance (nightelf) kernels had support for this.
It boots and runs lovely
Sent from my MT11i using XDA
mpiekp said:
Hi guys as you know our Xperia 2011 use yaffs2 for the mtd partitions, but it doesn't have too.
I bit the bullet, formated system, cache and data as ext4 from updater-script, knowing that alliance (nightelf) kernels had support for this.
It boots and runs lovely
Click to expand...
Click to collapse
Any noticeably difference? Run any benchmarks? I never understood why SE used yaffs2 for phones, same as why ext4 isn't supported by default, but that's other story
Anw, I guess now you can only install rom via .zip from CWM? Or maybe even flashtool wouldn't complain, but I guess PCC would complain for sure
p.s. respect for trying that
report pros and cons
Lol to revert just flash s zip that formats as yaffs, will try flashtool, although don't expect an issue as it basically raw writes the sin, which are complete img files including filesystem.
Benchmarks would be pointless, due to running experimental build anyway so nothing to compare to, but things like file manger appear more responsive.
All I can say is try it, make sure the updater-binary you use can accept 4 arguments for format and mount (hint the one in codename can), place that into any Rom zip and edit the updater-script.
So the format line is like this
format("ext4", "MTD", "system", "0");
Sent from my MT11i using XDA
Wonderful and brave find!! ext4 are supposed to be safer (journalism), but can have some overhead.
I have seen a script that even converts live yaffs2 to ext4 in some other forum, so that formatting is not required.
Otherwise, after format, you can restore the backups!
I am really interested to know if the partitions can be resized, so that we can have more space for /data (instead of 100 mb /cache and such a large /system)
Actually having checked how its mounted, it appears to have ignored the fs type
Still I'm going to persue this, what are the default part sizes? Esp part mtd1 where vendor gets mounted as on gb vendor is empty
Sent from my MT11i using XDA
mpiekp said:
Actually having checked how its mounted, it appears to have ignored the fs type
Still I'm going to persue this, what are the default part sizes? Esp part mtd1 where vendor gets mounted as on gb vendor is empty
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Maybe those links help you understand :
http://forum.xda-developers.com/showthread.php?t=1566846
http://forum.xda-developers.com/showthread.php?t=1449917
how can we check the type of our partitions?
I'm researching a bit, and people say that yaffs2 is better than ext4 for NAND memory.
I need to research a bit more on this matter.
I am here to learn.Thanks for sharing.
termagazis said:
how can we check the type of our partitions?
Click to expand...
Click to collapse
FOUND IT! :D
Install Terminal emulator
AND TYPE THIS:
su
Click to expand...
Click to collapse
df
Click to expand...
Click to collapse
It gives you all the info you need. If you won't type su, it would not give you MTD partitions' info.
Searched this http://www.computerhope.com/unix/udf.htm according to the image shown here http://forum.xda-developers.com/showthread.php?t=1566846 did I realised that.
400 for system is excessive, should be safe to bring down to 300, forget vendor 6m is not worth worrying.
With /cache that could be another 200mb for data.
Also boot is a worry, formatting the blocks of mtd doesn't appear to work, could rewrite the array, but may kill boot, which would be a hard brick.....
Sent from my MT11i using XDA
Yaffs designed for nand flash based embedded systems
Ext4 is not for that
Sent from my MT11i using XDA
leajian said:
FOUND IT! :D
Install Terminal emulator
AND TYPE THIS:
It gives you all the info you need. If you won't type su, it would not give you MTD partitions' info.
Searched this http://www.computerhope.com/unix/udf.htm according to the image shown here http://forum.xda-developers.com/showthread.php?t=1566846 did I realised that.
Click to expand...
Click to collapse
in the image you gave it doesnt say in what format is every partition.(yaffs or ext3,ext4)
termagazis said:
in the image you gave it doesnt say in what format is every partition.(yaffs or ext3,ext4)
Click to expand...
Click to collapse
In that case, just time
mount
Click to expand...
Click to collapse
in Terminal Emulator and see that every partition is reported on what filesystem it is.
More info @ http://www.cyberciti.biz/faq/linux-how-to-determine-find-out-file-system-type/
Or run it as root
Sent from my MT11i using XDA
yacloo said:
Yaffs designed for nand flash based embedded systems
Ext4 is not for that
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Before you will notice any degradation of NAND, you will sell this phone and forget about it, so...
I made a mess
do I change file system? dont i change it? good or bad?
Actually, it is that easy.
However, all the kernels are set to mount as yaffs, so you also need to unpack and edit the config files in the kernel too.
Sent from my MT11i using XDA
Related
Hi,
If i convert to EXT4 from CWM settings, will stock ROM have any issues or it's going to work just fine?
got anwer at #moto-atrix IRC chan.
I need custom kernel which supports EXT4 first.
purpler said:
got anwer at #moto-atrix IRC chan.
I need custom kernel which supports EXT4 first.
Click to expand...
Click to collapse
Once you get the appropriate kernel the CWM conversion works great. Keep in mind, whenever you wipe a partition through CWM/fasboot you will need to re-run the script, as they will get formatted back to ext3. They can still get mounted as ext4, but all of the optimizations will be gone.
What's the benefit of converting to ext4?
Milenko2121 said:
What's the benefit of converting to ext4?
Click to expand...
Click to collapse
Faster file transfers, processing, and the ability to read extremely large files. As far as I know at least, as I'm no expert
Sent from my MB860 using xda premium
Hi all.
I'm thinking to convert my file system from rfs to ext4. For that I downloaded the conversion app from the cf-root thread, but I'm not sure that this is safe enough to go.
I have ~20 MB free space on system, I have cwm 5 installed, and I'm on 2.3.6 XKT7. (I would like to have ext4 system, to flash turboboost and lagfree.) Could you tell me something? Is it 100% safe, doesen't it harm the phone? Naturally I made a backup with Titanium Backup, and with cwm, but it would be better just to have nothing changed, only the file system...
I did it about 2 month ago. Everything work great, I don't have any problems. Don't wait, just do it
since i didnt see you have written CF-root kernel is installed on your phone first i have to remind you that CF-root ext4 tool won't work without it!
and second (just a little correction); you do not need to have your file system as ext4 in order to use turboboost and lagfeee... they are scripts to make some changes in the way your phone decides what to do when it comes to manage things in its functioning system like ram management.. on the other hand, ext4 tool is an apk to easily change your memories' formats to ext4 from rfs..
but still i would recommend you to make an ext 4 convertion, it makes difference.. and also using ONE of those scripts..
_delice_doluca_ said:
since i didnt see you have written CF-root kernel is installed on your phone first i have to remind you that CF-root ext4 tool won't work without it!
and second (just a little correction); you do not need to have your file system as ext4 in order to use turboboost and lagfeee... they are scripts to make some changes in the way your phone decides what to do when it comes to manage things in its functioning system like ram management.. on the other hand, ext4 tool is an apk to easily change your memories' formats to ext4 from rfs..
but still i would recommend you to make an ext 4 convertion, it makes difference.. and also using ONE of those scripts..
Click to expand...
Click to collapse
So I just don't understand this. In the lagfree thread, it says, that the system has to be in ext4 format, to make the tool work.
And in the other hand, I read, that turboboost and lagfree together are the best way, to make the Ace a true ace.
So than... I'm as confused as I can be.
kmarci said:
So I just don't understand this. In the lagfree thread, it says, that the system has to be in ext4 format, to make the tool work.
And in the other hand, I read, that turboboost and lagfree together are the best way, to make the Ace a true ace.
So than... I'm as confused as I can be.
Click to expand...
Click to collapse
Nobody out there to help a bit...?
Okay, so basically as the title says, I want to get back to rfs since I want to use cwm, and because ever since I flashed icy fusion I don't even get the speed benefits of ext4, even though all my partitions are supposedly still in ext4 format (weid, I know). Now I don't want to lose my data, and for some reason my Odin packages I try to make never work and just brick my device, so here is my idea. Could I make dumps of my partitions using terminal emulator, then somehow flash those using cwm? Or is it not possible? Thank You.
Sent using Tapatalk
iJimaniac said:
Okay, so basically as the title says, I want to get back to rfs since I want to use cwm, and because ever since I flashed icy fusion I don't even get the speed benefits of ext4, even though all my partitions are supposedly still in ext4 format (weid, I know). Now I don't want to lose my data, and for some reason my Odin packages I try to make never work and just brick my device, so here is my idea. Could I make dumps of my partitions using terminal emulator, then somehow flash those using cwm? Or is it not possible? Thank You.
Sent using Tapatalk
Click to expand...
Click to collapse
Well, klin's kernel works with cwm, so if you make a backup from there (or use an existing backup), rename it from .ext4 to .rfs (basically using the ext4 converting instructions in reverse), you *should* be able to get back to rfs. To answer your second question, yes, you can dump your partitions, but you would need to create an odin-flashable package with them, and dd (the command you would use) dumps retain the filesystem (so ext4 dumps are flashed as ext4, and so on).
Yes, but am I correct in thinking if I enter cwm to create a nandroid, my data partition will be wiped because of the cwm bug with ext4? What I am trying to do is make a backup without losing my data. I might just have to lose my data and restore apps with titanium backup.
Sent using Tapatalk
iJimaniac said:
Yes, but am I correct in thinking if I enter cwm to create a nandroid, my data partition will be wiped because of the cwm bug with ext4? What I am trying to do is make a backup without losing my data. I might just have to lose my data and restore apps with titanium backup.
Sent using Tapatalk
Click to expand...
Click to collapse
Klin's kernel's CWM seems to NOT wipe your data, at least in my experience, so you should be good to go if you flash it.
hanthesolo said:
Klin's kernel's CWM seems to NOT wipe your data, at least in my experience, so you should be good to go if you flash it.
Click to expand...
Click to collapse
Hmm, I didn't realize that, thanks for the tip!
Sent using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1620255
Hey, I just saw this on the portal, looks like it could be a solution to the problem?
Sent using Tapatalk
Okay so, true to your word, klin's r3 doesn't have the bug. Unfortunately I now get an error when I try making a nandroid. It gets to "backing up /cache..." then gives me " Unable to find mounted volume: /cache
Error finding an appropriate handler" and immediately returns to the main menu without finishing the nandroid. Any ideas what to do? Would wiping cache be safe with this problem?
Some updates: wiping cache did nothing to fix the problem. I can dump the cache partition fine using terminal emulator and the dd command. When I use the "mount" command, cache is not listed in the partitions.
This is starting to creep me out. I think something to do with it is after flashing icyfusion going from klassic r5 with all partitions converted to ext4, I started getting rfs-like io preformance (quadrant benchmarks), even though "mount" said all partitions are still ext4.
Sent using Tapatalk
If you want to get back to rfs that bad do the following.
1. make a nandroid backup
2. change the .ext4 to rfs like when you want to convert
3. flash the total recovery method with the STOCK kernel.
4. Then flash a kernel that supports the .tar backup (klin or terrasilent)
5. restore your backup and you should be in rfs with your backup.
Me I use terrasilent and I don't lose data when I backup. Maybe when you change the .ext4 to .rfs try to unmount using the computer before the device.
Well, if you read my above posts you can see that I can't make a nandroid because of something concerning the cache partition. It cancels there. Thank you for replying!
Sent using Tapatalk
iJimaniac said:
Well, if you read my above posts you can see that I can't make a nandroid because of something concerning the cache partition. It cancels there. Thank you for replying!
Sent using Tapatalk
Click to expand...
Click to collapse
Oh didin't read the cache part... Hmm you can always make a backup of your data partition and then make a nandroid backup from terrasilent.
I am not exactly sure if it is the kernal's fault, or something messed up with partitions. I doubt terrasilent would fix it. I have also now tried restoring the cache partition from a previous nandroid, and it restores (I guess), but it still gives me the same error when backing up.
Sent using Tapatalk
Sorry for abandoning this thread, I forgot about it . Perhaps you can mount it manually? Try using the partition listed when you are booted into android to mount it eg. Mount /Dev/block/stlx. I also suppose that to fix all of this easily, you can return to stock with a pit, but you will have too have a backup of your data.
I tried and get:
# mount /Dev/block/st11
mount: can't find /Dev/block/st11 in /etc/fstab
Sent using Tapatalk
iJimaniac said:
I tried and get:
# mount /Dev/block/st11
mount: can't find /Dev/block/st11 in /etc/fstab
Sent using Tapatalk
Click to expand...
Click to collapse
its stl not st
zaclimon said:
its stl not st
Click to expand...
Click to collapse
Whoops, typo, here is direct copy/paste from terminal emulator;
$ export PATH=/data/local/bin:$PATH
$ su
# mount /Dev/block/stl11
mount: can't find /Dev/block/stl11 in /etc/fstab
#
Sent using Tapatalk
iJimaniac said:
Whoops, typo, here is direct copy/paste from terminal emulator;
$ export PATH=/data/local/bin:$PATH
$ su
# mount /Dev/block/stl11
mount: can't find /Dev/block/stl11 in /etc/fstab
#
Sent using Tapatalk
Click to expand...
Click to collapse
it's because of the caps *d*. You should write
# mount /dev/block/stl11
Same result:
$ export PATH=/data/local/bin:$PATH
$ su
# mount /dev/block/stl11
mount: can't find /dev/block/stl11 in /etc/fstab
#
Sent using Tapatalk
iJimaniac said:
Same result:
$ export PATH=/data/local/bin:$PATH
$ su
# mount /dev/block/stl11
mount: can't find /dev/block/stl11 in /etc/fstab
#
Sent using Tapatalk
Click to expand...
Click to collapse
can you send me your /etc/recovery.fstab to see if /cache is in it? and which rom are you using?
Umm, I don't have a recovery.fstab, just a "vold.fstab" and a "fstab". I am using icy fusion.
Sent using Tapatalk
Hi all, my first post here, I hope its not in the wrong section
I know this will probably be a very noob question, but I have been trying to create a .zip file with my stock rom I downloaded from a site, (I have a HTM-H9500 [MTK 6582]), I was creating the zip in android kitchen, but whatever i do i always get Error: status 0 in CWM, I read that this would probably because of update-binary or updater-script, I have tried creating update-script (without the r) and CWM directly says that its very old and that i should create updateR-script, however when i do all the process again with updater-script I get this annoying status 0 error.
What can i do? I searched this topic in the net and all the sugestions people had said havent worked for me.
Thanks in advance and sorry for my bad english.
Replace the update-binary file from an existing custom ROM of your device with the ROM you made using kitchen that should do the job.
Also while adding the file to zip make sure you set the compression to store
Hit thanks if I helped.
Sent from my C5302 using XDA Free mobile app
Tech N You said:
Replace the update-binary file from an existing custom ROM of your device with the ROM you made using kitchen that should do the job.
Also while adding the file to zip make sure you set the compression to store
Hit thanks if I helped.
Sent from my C5302 using XDA Free mobile app
Click to expand...
Click to collapse
Hi! Thanks for the quick answer, the thing is because my phone is not very popular i havent found any other custom rom other than the stock specifically for my phone (thats why i was trying to port from another device that is very similar, but first i tried to do this process with my stock rom) so i dont have any other update-binary file other than this one.
About the other thing, how can i change the compression rate in android kitchen ?
Again, thanks a lot and sorry for my english
AlpinoSoyYo said:
Hi! Thanks for the quick answer, the thing is because my phone is not very popular i havent found any other custom rom other than the stock specifically for my phone (thats why i was trying to port from another device that is very similar, but first i tried to do this process with my stock rom) so i dont have any other update-binary file other than this one.
About the other thing, how can i change the compression rate in android kitchen ?
Again, thanks a lot and sorry for my english
Click to expand...
Click to collapse
Go to play store and download zipme app.
Create any flashable app using zip me and then copy it to PC. Open the META-INF Folder then com->android ->Google then open it and you'll see a update-binary file. That is your stock binary
Open the final zip after creating the ROM. If om Windows open the zip (ROM) created and open the zip created using zipme.
Copy the update-binary from zipme ZIP to kitchen created zip and when you'll do this you will see a menu that will ask that are you sure about adding this file, search around a bit and you'll see the compression option
Tech N You said:
Go to play store and download zipme app.
Create any flashable app using zip me and then copy it to PC. Open the META-INF Folder then com->android ->Google then open it and you'll see a update-binary file. That is your stock binary
Open the final zip after creating the ROM. If om Windows open the zip (ROM) created and open the zip created using zipme.
Copy the update-binary from zipme ZIP to kitchen created zip and when you'll do this you will see a menu that will ask that are you sure about adding this file, search around a bit and you'll see the compression option
Click to expand...
Click to collapse
Seriously, thanks lot, means a lot to me, im not used to get much help in forums haha, what you said worked flawlessly, now i get status 7 error, but this means where going somewhere, il keep digging to fix this.
Thanks again
AlpinoSoyYo said:
Seriously, thanks lot, means a lot to me, im not used to get much help in forums haha, what you said worked flawlessly, now i get status 7 error, but this means where going somewhere, il keep digging to fix this.
Thanks again
Click to expand...
Click to collapse
Glad to help friend
Status 7 is error with your mount points.
In your updater-script when you'll open it (open using NOTEPAD++ ONLY, don't use notepad or wordpad) you will see two lines as
Format ("MTD", "SYSTEM"); and other would be mount.
Check these two lines and replace them with your device mount paths
You'll be having no problem.!
Tech N You said:
Glad to help friend
Status 7 is error with your mount points.
In your updater-script when you'll open it (open using NOTEPAD++ ONLY, don't use notepad or wordpad) you will see two lines as
Format ("MTD", "SYSTEM"); and other would be mount.
Check these two lines and replace them with your device mount paths
You'll be having no problem.!
Click to expand...
Click to collapse
Thanks !
In my updater-script I have this two lines
format("MTD", "system");
mount("MTD", "system", "/system");
I know i should know this by now but what are you refering to with 'your device mount paths'?
Thanks a lot, trying to learn here
AlpinoSoyYo said:
Thanks !
In my updater-script I have this two lines
format("MTD", "system");
mount("MTD", "system", "/system");
I know i should know this by now but what are you refering to with 'your device mount paths'?
Thanks a lot, trying to learn here
Click to expand...
Click to collapse
Do you have a recovery.img for your device?
Extract it using kernel kitchen and then after extracting it you' ll get a folder named ramdisk.
Open it go to etc and then recovery.fstab.
Open it with notepad++ and see the mount paths for your device just copy and replace it.
Mount path is the line that tell CWM where to install the particular files. If you face any problems then attach your recovery.img and updater-script and I'll have look at it
Tech N You said:
Do you have a recovery.img for your device?
Extract it using kernel kitchen and then after extracting it you' ll get a folder named ramdisk.
Open it go to etc and then recovery.fstab.
Open it with notepad++ and see the mount paths for your device just copy and replace it.
Mount path is the line that tell CWM where to install the particular files. If you face any problems then attach your recovery.img and updater-script and I'll have look at it
Click to expand...
Click to collapse
Well i didnt had kernel kitchen so after downloading it and runing it i only found those 5 options:
1 work with boot.img files
2 work with kernel.sin and ftf files
3 work wih kernel.elf files
4 work with init ramdisk
5 editing bootsplash image
But nothing to extract recovery.img, i suposed that i should just change recovery.img name to boot.img and do the process but i get an empty folder in the output folder, what should I do?
Thanks thanks thanks again
Google this tool "std unpack" open to first link and download that tool.
Drag your recovery.img to STD unpack and you'll get your files.
Alternatively you can also use kitchen to unpack the recovery.img
Just go to advanced options then go to boot unpacking tools and follow steps as suggested
Sent from my C5302 using XDA Free mobile app
Tech N You said:
Google this tool "std unpack" open to first link and download that tool.
Drag your recovery.img to STD unpack and you'll get your files.
Alternatively you can also use kitchen to unpack the recovery.img
Just go to advanced options then go to boot unpacking tools and follow steps as suggested
Sent from my C5302 using XDA Free mobile app
Click to expand...
Click to collapse
Seriously, sorry to be this stupid, but i cant find anything googling "std unpack" "std unpack tool" or "std unpack download" just a bunch of c++ questions..
Thanks again..
EDIT: nevermind i did it with kitchen like you said in advanced options, this is what I have in recovery.fstab
# mount point fstype device [device2]
/misc emmc /dev/misc
/data ext4 /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p6
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
How should i change the lines: format("MTD", "system"); and mount("MTD", "system", "/system"); according to that?
Again, thanks for the extensive help
AlpinoSoyYo said:
Seriously, sorry to be this stupid, but i cant find anything googling "std unpack" "std unpack tool" or "std unpack download" just a bunch of c++ questions..
Thanks again..
EDIT: nevermind i did it with kitchen like you said in advanced options, this is what I have in recovery.fstab
# mount point fstype device [device2]
/misc emmc /dev/misc
/data ext4 /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p6
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
How should i change the lines: format("MTD", "system"); and mount("MTD", "system", "/system"); according to that?
Again, thanks for the extensive help
Click to expand...
Click to collapse
Ready to help always
Use this command for format.
format("ext4", "EMMC", "/dev/block/mmcblk0p5", "system") ;
For mount statement just replace format with mount and keep rest same.
Tech N You said:
Ready to help always
Use this command for format.
format("ext4", "EMMC", "/dev/block/mmcblk0p5", "system") ;
For mount statement just replace format with mount and keep rest same.
Click to expand...
Click to collapse
Thanks again man...
Im still getting status 7 error but now it says format() expects 3 args, got 4
AlpinoSoyYo said:
Thanks again man...
Im still getting status 7 error but now it says format() expects 3 args, got 4
Click to expand...
Click to collapse
Update-binary error only. Try to get a update-binary for your mobile model this is only the problem rest everything is ok.
Also keep a nandroid backup ready if anything goes wrong just explore your device. If it is a Mediatek6557 (just a example) device then search for the any handset running the board of mtk 6557 and download it's custom ROM and replace update-binary and it will work. Download CPU-Z for your phone from play store to get detailed information of your device and board.
Tech N You said:
Update-binary error only. Try to get a update-binary for your mobile model this is only the problem rest everything is ok.
Also keep a nandroid backup ready if anything goes wrong just explore your device. If it is a Mediatek6557 (just a example) device then search for the any handset running the board of mtk 6557 and download it's custom ROM and replace update-binary and it will work. Download CPU-Z for your phone from play store to get detailed information of your device and board.
Click to expand...
Click to collapse
Well thanks, i'll kep searching, one last thing, why would my update-binary wont work? i mean, im using stock rom and trying to flash stock rom again, why would i need a different one?
AlpinoSoyYo said:
Well thanks, i'll kep searching, one last thing, why would my update-binary wont work? i mean, im using stock rom and trying to flash stock rom again, why would i need a different one?
Click to expand...
Click to collapse
You using stock ROM but according to device it doesn't know stock or custom for it everything we flash is just a external source which is implemented in it.
Tech N You said:
You using stock ROM but according to device it doesn't know stock or custom for it everything we flash is just a external source which is implemented in it.
Click to expand...
Click to collapse
Well like you said i kept searching and found an update binary that did the trick and everything flashed just fine, however, even though i didnt get a bootloop, when i turn on the phone it shows the brand logo as always and then its just a black screen.
Any ideas? Thanks !!
Check the permissions in updater-script to and hope you can boot into recovery, restore the phone to old state and then using kitchen convert your updater-script (edify) to update-script (amend) and check for errors. Ignore error with the format and mount command
Sent from my C5302 using XDA Free mobile app
Tech N You said:
Check the permissions in updater-script to and hope you can boot into recovery, restore the phone to old state and then using kitchen convert your updater-script (edify) to update-script (amend) and check for errors. Ignore error with the format and mount command
Sent from my C5302 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks again, what should i look for in permissions in updater-script?
and update-script (without r) gives me problems when i try to flash in cwm
Update-script is old format and isn't used much more. New devices use updater-script for flashing
Sent from my C5302 using XDA Free mobile app
Good afternoon. As the 8 GB aren't enough for me, I've been looking for a solution. While doing so, I found the INT2EXT4 script, which mounts /data on the second partition of the SD card. The first time I flashed it (after enabling init.d support with an app) it didn't work at all. Then, I realised this script is written assuming that the second partition of the card is mmcblk0p2. But on the M4, it's mmcblk1p2 (found it out with another app).
I changed those lines on the script, but it didn't work either. I analyzed all the lines, and I can't see where the problem could be. Has anyone tried this, or could somebody help me with this issue? I think it could be really useful for a lot of users.
Another thing: flashing the file through TWRP gave me an error, so I copied the file directly to /system/etc/init.d and set the permissions manually. I hope this is not a problem, but let me know if it could be...
sounds interesting... ill take a look at it soon!
Have you checked the "adress" of internal sd? In the script there is a connection between internal and external storage so i would assume that both "adresses" need to be correct in order for the script to work. Just an opinion....
Sent from my SM-G901F using XDA Free mobile app
vader20 said:
Have you checked the "adress" of internal sd? In the script there is a connection between internal and external storage so i would assume that both "adresses" need to be correct in order for the script to work. Just an opinion....
Sent from my SM-G901F using XDA Free mobile app
Click to expand...
Click to collapse
several1989 said:
sounds interesting... ill take a look at it soon!
Click to expand...
Click to collapse
I think there's a problem with the commands that the script uses. If I try to do umount from the terminal, nothing happens. So maybe the script doesn't work in this phone, but if any of you are able to make it do so, let me know. So I think it's better to build the kernel from source, but before that make changes in the fstab file. With that, /data will be mounted at the second partition of the sdcard directly at boot time. Trying to do this now, but I'm facing some difficulties building the kernel. If I make it work, I'll post it
Testé folder Mouth playstore