Why won't updater-binary mount /system? TWRP doesn't give me any helpful errors, apart from:
Code:
unable to mount /system
Here is the code:
Code:
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/by-name/FACTORYFS", "/system", "");
Older versions of Android worked with this:
Code:
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/by-name/FACTORYFS", "/system");
But it still gives the same error.
Any help appreciated.
P.S. what's the last argument for?
Related
I'm planning on using the UpdatezipCreator from this thread http://forum.xda-developers.com/show....php?t=1274736 to build an update script for some APK updates I want to package up. It appears this app has the ability to build a update-binary file for you.
I have APK files in both the system/app and data/app that I want to be copied to my phone. I'm confused on a few things.
First thing, can I have multiple destinations for the files in the script? I haven't found any examples with two destinations and there doesn't seem to be a spot to configure the source which makes me think it just takes everything in the zip and puts it in the folder you specifiy in the package_extract_dir function and that adding a second "package_extract_dir" function would confuse it.
The second question is I keep running across scripts that us busybox instead of the built in commands. Why would you need to/want to do that?
This is what I would think would work for my script:
Code:
ui_print("Preparing to update");
ui_print("Copying files..");
package_extract_dir("system", "/system");
package_extract_dir("data", "/data");
ui_print("Done! You can reboot your system now!");
I know I need a mount command before the package_extraction but I don't know which I should use and if I need a second mount for the /data/app folder as well.
"run_program("/sbin/busybox", "mount", "/system");"
or
"mount("/dev/block/stl6", "system", "/system", "rw");"
The folder structure of my zip is;
Zip
/system/app/apk files
/data/app/apk files
/META-INF
Do this in your updater-script:
Code:
run_program("/sbin/busybox", "mount", "/data");
run_program("/sbin/busybox", "mount", "/system");
ui_print("Preparing to update");
ui_print("Copying files..");
package_extract_dir("system", "/system");
package_extract_dir("data", "/data");
run_program("/sbin/busybox", "umount", "/data");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Done! You can reboot your system now!");
Hey thar.
Im making a custom 2.3.4 ROM for the Samsung EH02 (Admire/Vitality).
Im using CWM 5.0.2.7 which only requires 2 args, so one of these _should_ work, but do not format or mount.
Code:
format("MTD", "system")
mount("MTD", "system", "/system");
package_extract_dir("system", "/system");
Code:
format("MTD", "/dev/block/stl12")
mount("MTD", "/dev/block/stl12", "/system");
package_extract_dir("system", "/system");
The Code is solid -- no errors (No log file either). Its just not formatting or mounting the stated partitions.
As Im not too familiar with Samsung development, any help from devs would be greatly appreciated.
Thanks in advance.
~Spz0
I decided to give this a try.
Its a very simple flash and I guess an easy beginner task.
All I'm doing is adding S_opener.ogg to the notifications directory.
It's not in FJs AOSP rom and I just want to flash it after flashing his updates.
I found a tool that makes creating the zip pretty easy AFAIK
http://forum.xda-developers.com/showthread.php?t=1248486
I want to mount the system, copy the file, unmount.
The default script is below.
I have three questions before I create and flash this....don't wanna brick it
1)What's our mount point?
2)On the extract directory, can I use the parent like it is or do I have to specify by drilling down? (/system/media/audio/notifications)
3)Does it unmount? Is that part of the extract command?
THANKS!
Here's the script:
ui_print("Preparing to update");
# mounting system as r/w - ATTENTION - set the the mount point
# to the proper for your device! Example mountr command is
# mounting system for Samsung GT-I5800 aka Galaxy 3
mount("/dev/block/stl6", "system", "/system", "rw");
ui_print("Copying....");
# copy system content to the system directory on your device
package_extract_dir("system", "/system");
ui_print("Done! You can reboot your system now!");
Cool project. Good luck.
Yea. I thought it would be a cool way to get a better idea of what it takes for these developers.
Any developers able to lend me a hand here?
I think my questions are clear....
I'd appreciate it.
Thanks!
Why not team up with Jessooca. She wants to learn too. Plus I think she will get more attention than you.
1) I find it easiest to use the "busybox" mount
-- this will always be compatible with just about any custom ROM. (no need to know the mount partition)
2) Yes, just use the parent directory
3) No, it doesn't unmount automatically (not that it really needs to anyway)
If copying system apps, you can also save some time by wiping dalvik-cache and rebooting right here in the script.
Here is a generic script good for just about anything you might want to throw into system/
Code:
ui_print("Updating System...");
show_progress(0.1, 0);
ui_print(" ");
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("system", "/system");
run_program("/sbin/busybox", "umount", "/system");
ui_print(" ");
ui_print("Wiping Cache & Rebooting...");
run_program("/sbin/busybox", "mount", "/data");
delete_recursive("/data/dalvik-cache");
run_program("/sbin/busybox", "umount", "/data");
run_program("/sbin/reboot");
Hope this is helpful for you
Thanks! I found busy box in xbin. I also looked at fjs rom script and that's what he uses. I'll give it a shot
Sent from my SAMSUNG-SGH-I717 using xda premium
Bummer. I feel like I'm so close...
I have flashed three times and luckily no side effects but the file isn't there....
sbin doesn't have busybox in it but system/xbin does
So I did this:
Code:
ui_print("Preparing to update");
ui_print("Updating System...");
show_progress(0.1, 0);
ui_print("Coying Opener Notification");
run_program("/system/xbin/busybox", "mount", "/system");
package_extract_dir("system", "/system");
run_program("/system/xbin/busybox", "umount", "/system");
ui_print(" ");
ui_print("Done! You can reboot your system now!");
And that doesn't work either...
The cool thing is that I'm learning quite a bit with all these failures
That's why I chose a 'simple' task
Tried this to but it didn't work.
It flashed and said it went but the file isn't there....
Guess I'll try again tomorrow.
Code:
ui_print("Preparing to update");
ui_print("Updating System...");
show_progress(0.1, 0);
mount("/dev/block/mmcblk0p24", "system", "/system");
ui_print("Copying files Opener Notification");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Done! You can reboot your system now!");
You see /system/xbin/busybox while booted normally; however
when booted in recovery it sees /sbin -- trust me on this.
If you still want to use standard partition mounting try this:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p24", "/system");
Thanks for your help on this. I'll try sbin today. I trust ya
I did try that string but it threw an error and said I had four variables and it only wanted three.
Sent from my SAMSUNG-SGH-I717 using xda premium
hmm yeah well I just plucked that one out of a ROM installer
the /sbin/busybox mount has worked well for me over lots of zip and lots of different ROMs
Yep, that did it! Thanks
My first successful zip
Now to figure out how to make that the default notification.
It looks like it's in the build.prop but I haven't searched enough on xda yet.
I found the default notification for the ROM in build.prop but can't find where the current default notification is.
Is that in a file similar to build.prop?
Every time I flash a ROM I'm playing with, using the clear data options I added, it clears the sdcard too?
I'm using this code with the AROMA installer:
Code:
# Clear Data
if file_getprop("/tmp/aroma/clear.prop","selected.1") == "1"
then
ui_print("@Wiping Data...");
delete_recursive("/system");
delete_recursive("/data");
delete_recursive("/preload");
endif;
ui_print("@Clearing Cache and Dalvik...");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache");
delete_recursive("/dalvik/dalvik-cache");
The only instance of format I have is here:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p9", "0");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/cache");
run_program("/sbin/mount", "/dev/block/mmcblk0p12", "/dalvik");
run_program("/sbin/busybox", "mount", "/sdcard");
Which is confusing me a lot
Bump
Can someone please shed some sort of light as to why this deletes the contents of the SD card?
Is it possible to clear system and data within an updater-script WITHOUT killing my internal sd card?
I think its the
Code:
delete_recursive("/preload");
line thats doing it - i don't have that line, neither do any of the other Roms updater scripts that ive looked at
Remove it and see what happens
MattBooth said:
Every time I flash a ROM I'm playing with, using the clear data options I added, it clears the sdcard too?
I'm using this code with the AROMA installer:
Code:
# Clear Data
if file_getprop("/tmp/aroma/clear.prop","selected.1") == "1"
then
ui_print("@Wiping Data...");
delete_recursive("/system");
delete_recursive("/data");
delete_recursive("/preload");
endif;
ui_print("@Clearing Cache and Dalvik...");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache");
delete_recursive("/dalvik/dalvik-cache");
The only instance of format I have is here:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p9", "0");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/cache");
run_program("/sbin/mount", "/dev/block/mmcblk0p12", "/dalvik");
run_program("/sbin/busybox", "mount", "/sdcard");
Which is confusing me a lot
Click to expand...
Click to collapse
Such an old thread, just trying my luck.
How were you able to run the function "delete_recursive" in updater-script?
I dont see it as part of the official functions list.
Nikil07 said:
How were you able to run the function "delete_recursive" in updater-script?
I dont see it as part of the official functions list.
Click to expand...
Click to collapse
Write such a function at your own
Syntax
delete_recursive <file-or-dir1> [... <file-or-dirN>]
Example
Code:
delete_recursive()
{
for d in "[email protected]"; do rm -rf "$d" 2>/dev/null; done
}
jwoegerbauer said:
Write such a function at your own
Syntax
delete_recursive <file-or-dir1> [... <file-or-dirN>]
Example
Code:
delete_recursive()
{
for d in "[email protected]"; do rm -rf "$d" 2>/dev/null; done
}
Click to expand...
Click to collapse
Hey, thanks for the response.
But how will I be able to run these functions as part of the updater-script?
And also, regular unix commands like ls, rm are not available in recovery.
1. You add these lines of code to the very beginning of the updater script, but after the line #!/sbin/sh or similar one
2. Recovery ( at least the Stock Recovery ) merely is a menu what offers you some options, it's not an Android terminal
Maybe this is not correct forum, but I used dsixda's kitchen. Everything went fine, but in updater-script file I have got an error:
Code:
mount("ext4", "EMMC", "???", "/data");
Kitchen warned me to fix this, but I need to replace the ??? signs with correct
Code:
/dev/block/<something>
like this:
Code:
mount("ext4", "EMMC", "/dev/block/stl12", "/system"); "0 /system/
My question is, how I can fix <something> to be correct? Every help is appreciated!
Solved! I do not even have any files in /data to flash.
Mods: please delete this thread.
Sent from my Prestigio tablet using XDA Developers 4 Premium app