• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] included /data

mercury0x000d

mercury0x000d

The ultra-modern operator
How would I go about including a /data partition in my ROM? I figured this would be as simple as including /system and handled it accordingly, but it's not working for some reason. I'm wanting to do this to have a certain look and certain settings for all the apps be already in effect at startup. Any tips would be appreciated!
 
just take my rom as an example make sure you have the jbrd400 data fix in the system...

I really don't like system apps that have updates every month so i have taken them out of my system and they install as data... that way when an update comes along it overwrites the old one...

sorry.. I have been able to do what you where saying but only with certain apps... by also including a /data/data/ folder... but doesnt work all the time for all apps...
 
smartmanvartan said:
just take my rom as an example make sure you have the jbrd400 data fix in the system...

I really don't like system apps that have updates every month so i have taken them out of my system and they install as data... that way when an update comes along it overwrites the old one...

sorry.. I have been able to do what you where saying but only with certain apps... by also including a /data/data/ folder... but doesnt work all the time for all apps...
Click to expand...

I agree, that can be annoying at least, and waste space at most. Also, I'm going for this approach since then the end user can easily delete the apps they don't want. Could I get a link to your ROM?
 
I haven't looked at voltron but I imagine smartmanvan uses edify commands. Just remember that your bins (dd, etc) either need to be in sbin or you need to leave /system mounted
 
Sorry it's taking me longer then expected and I wanted to do one last thing... drewhill77, as i said including app data in the data folder works sometimes but not all the time and with very few apps... your method sounds sound but i would need an example because i do not in fact use edify command and would like to see in action... you said it was in the noob rom updater-script?
 
smartmanvartan said:
Sorry it's taking me longer then expected and I wanted to do one last thing... drewhill77, as i said including app data in the data folder works sometimes but not all the time and with very few apps... your method sounds sound but i would need an example because i do not in fact use edify command and would like to see in action... you said it was in the noob rom updater-script?
Click to expand...


Yeah...I'm at work now and don't have access to a PC or I'd just post that particular line. It's towards the bottom of the script on n00b. Something like run_program (dd if=/tmp/splash.img of=/dev/block/mmcblk0p14)
 
Yes, I saw it, and Shin used the same approach in his Snapdragon splash screen flashable. But what I tried doesn't work at all, for zero apps. I'll post my installer-script when I get back home tonight.
 
drewhill77 said:
Did you place the binary in /sbin and extract /sbin to /tmp?
Click to expand...

No, I didn't. Are you referring to the install-binary? And why do I need to do this? Not trying to be a pain, I just don't understand why all this needs done when /system is so easy to mount lol
 
Here's the pertinent build.prop section:

Code: 
ui_print("Unmounting partitions:");
ui_print("   /system");
unmount("/system");
ui_print("   /data");
unmount("/data");
ui_print(" ");

ui_print("Formatting partitions:");
ui_print("   /system");
format("ext4", "EMMC", "/dev/block/mmcblk0p15");
ui_print("   /data");
format("ext4", "EMMC", "/dev/block/mmcblk0p18");
ui_print(" ");

ui_print("Mounting partitions:");
ui_print("   /system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p15", "/system");
ui_print("   /data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p18", "/data");
ui_print(" ");

ui_print("Extracting files from ROM image to partitions:");
ui_print("   WarpOEM 1.55/system -> /system");
package_extract_dir("system", "/system");
ui_print("   WarpOEM 1.55/data -> /data");
package_extract_dir("data", "/data");
ui_print(" ");
 
Last edited:
Right...well like you said in your op package_extract doesn't work for /data. The binaries I'm talking about are dd and such. They need to be in /sbin for the updater script to access them or if you want to use the ones in /system/bin you'll have to write out a full .sh script and run_program that in the updater script
 
Use dsi's kitchen to extract boot.img go to the ramdisk and put busybox and dd in /sbin. In your updater script do a package dir extract "data" to /tmp then do a run_program ("/sbin/busybox", "dd", "if=/tmp", "of=/data").

I'm not 100% sure of how I just formatted that so check it against shin or mrbobos updater scripts
 
drewhill77 said:
Use dsi's kitchen to extract boot.img go to the ramdisk and put busybox and dd in /sbin. In your updater script do a package dir extract "data" to /tmp then do a run_program ("/sbin/busybox", "dd", "if=/tmp", "of=/data").

I'm not 100% sure of how I just formatted that so check it against shin or mrbobos updater scripts
Click to expand...

Okay... again, a couple questions lol

Why is it that you have to use the dd program to do the copy when package_extract should do the same job? I mean, both methods are copying stuff to /data, just in different ways. I guess I don't see why what's going on works / doesn't work and that's what I'm trying to understand.

And what is /tmp? Do I have to format or mount it first? Or is it just ready to go?

Thanks a lot for your help so far, man :)
 
I honestly don't know why package extract doesn't work and can't guarantee that dd will work as I haven't had opportunity to try it myself. I just know other people have been able to use it when package extract didn't work on other phones. As far as /tmp its good to go...no mount or format needed
 
This is just a guess but I'm betting that the updater_binary doesn't support package extract to /data. I'm guessing zte either actively removed it to encumber the creation of custom roms or just didn't bother to include it since an "official" update wouldn't need to touch /data except to format it.
 
drewhill77 said:
This is just a guess but I'm betting that the updater_binary doesn't support package extract to /data. I'm guessing zte either actively removed it to encumber the creation of custom roms or just didn't bother to include it since an "official" update wouldn't need to touch /data except to format it.
Click to expand...

Wouldn't surprise me. Sounds like something ZTE would do lol If that's the case, I guess even then we can be thankful it's not as bad as HTC!
 
mercury0x000d said:
Wouldn't surprise me. Sounds like something ZTE would do lol If that's the case, I guess even then we can be thankful it's not as bad as HTC!
Click to expand...


Lol true dat! Lemme know if that works...if not I've a couple other ideas that may but I need access to my PC to check a couple things and I won't be home from work till 2am est.
 
Okay, so if it worked, I should be able to mount /data and use the file manager in TWRP to see the proper folders in their proper places immediately, right? I don't think I should have to reboot...
 
mercury0x000d said:
Okay, so if it worked, I should be able to mount /data and use the file manager in TWRP to see the proper folders in their proper places immediately, right? I don't think I should have to reboot...
Click to expand...


I'm not sure...maybe??? Lol...if not then reboot and see if they are
 
You must log in or register to reply here.
Back
Top Bottom