Root Proposal/Theory for External SD storage solution on F6

jckwpt · Aug 29, 2015

WarrantyVoider said:
As far as I know, the recovery ported by pressy4pie is CWM. TWRP was ported by hroark13. I am not sure which one you meant, but I've tested all three (two versions of TWRP) and they all work for me. You should be able to use any one of those for Xperion.

Are you still using the init.d version? When your phone boots up, does it take a long time? I'd suggest trying the binary version because Xperion would apparently load the binary version earlier than it would the init.d version. The commands to stop/start sensord should still be usable, but if the partition becomes available too late, perhaps putting those commands in an init.d script wouldn't be effective (without some long "sleep" time).

As for the zip extraction problem using the binary version, I'm attaching the .md5 checksum file for the latest -sensorfix.zip. Rename the .txt file to .md5. With the .md5 file, the recovery should verify the zip before attempting to flash/install (for TWRP at least, I don't remember whether CWM does so). Let me know if the recovery reports matching md5 but you still get the extraction error.

I have the sensord file in init.d but its sitting idle there, not being initiated as I reported several replies earlier, no change. Phone boot up: not necessarily a long time, normal load time.
For the past week Ive been trying to figure out the usage of this file without success. Apologies, I think Im slow at this. I changed your file extension to .md5. I tried installing it but couldn't find it after the rename process in recovery.

WarrantyVoider · Aug 30, 2015

jckwpt said:
I changed your file extension to .md5. I tried installing it but couldn't find it after the rename process in recovery.

Sorry, I wasn't trying to be cryptic. You seemed to know how to deal with an init.d script and were able to input console commands, so I just figured I'd skip the details.

The .md5 file is just a checksum (text file). Recovery (TWRP at least) can check the integrity of a zip file before installing if there's an accompanying .md5 file. You've mentioned installing the -sensorfix.zip returns the extraction error. I provided the .md5 file to see whether recovery has trouble reading the zip file. To use the .md5 file, put "DataOnSD-sensorfix.zip.md5" in the same folder as "DataOnSD-sensorfix.zip".

Anyway, back to the original problem.
Option 1: switch to the binary version.
So, in your case, to switch from the init.d version to the binary version: 1) Delete 00DataOnSD in /system/etc/init.d. 2) Reboot to recovery. 3) Install DataOnSD-install.zip. 4) Install DataOnSD-sensorfix.zip. 5) Reboot to system and check that everything works.

Option 2: stick with the init.d version
If you want to try to figure out the init.d version again: 1) Delete 00DataOnSD from /system/etc/init.d. 2) Save the content of 00DataOnSD in post #623 as "DataOnSD.sh". 3) Replace the existing "DataOnSD.sh" inside DataOnSD-initd.zip with the new version. 4) Reboot to recovery. 5) Install the new DataOnSD-initd.zip. 6) Reboot to system and check that everything works.
Note: I am not sure, but perhaps your file manager allows you to edit DataOnSD.sh inside DataOnSD-initd.zip directly. If so, you could do that instead of steps 2 and 3.

You can do option 2 manually by directly replacing the old 00DataOnSD in /system/etc/init.d with the new one. But you might need to set the file ownership to root and permissions to 744 or 777. I think Xperion would automatically set the permissions of an init.d script to 777, but I am not sure.

Let me know if any particular step is confusing or if everything goes as expected but the issue remains.

jckwpt · Sep 1, 2015

WarrantyVoider said:
Sorry, I wasn't trying to be cryptic. You seemed to know how to deal with an init.d script and were able to input console commands, so I just figured I'd skip the details.

The .md5 file is just a checksum (text file). Recovery (TWRP at least) can check the integrity of a zip file before installing if there's an accompanying .md5 file. You've mentioned installing the -sensorfix.zip returns the extraction error. I provided the .md5 file to see whether recovery has trouble reading the zip file. To use the .md5 file, put "DataOnSD-sensorfix.zip.md5" in the same folder as "DataOnSD-sensorfix.zip".

Anyway, back to the original problem.
Option 1: switch to the binary version.
So, in your case, to switch from the init.d version to the binary version: 1) Delete 00DataOnSD in /system/etc/init.d. 2) Reboot to recovery. 3) Install DataOnSD-install.zip. 4) Install DataOnSD-sensorfix.zip. 5) Reboot to system and check that everything works.

Option 2: stick with the init.d version
If you want to try to figure out the init.d version again: 1) Delete 00DataOnSD from /system/etc/init.d. 2) Save the content of 00DataOnSD in post #623 as "DataOnSD.sh". 3) Replace the existing "DataOnSD.sh" inside DataOnSD-initd.zip with the new version. 4) Reboot to recovery. 5) Install the new DataOnSD-initd.zip. 6) Reboot to system and check that everything works.
Note: I am not sure, but perhaps your file manager allows you to edit DataOnSD.sh inside DataOnSD-initd.zip directly. If so, you could do that instead of steps 2 and 3.

You can do option 2 manually by directly replacing the old 00DataOnSD in /system/etc/init.d with the new one. But you might need to set the file ownership to root and permissions to 744 or 777. I think Xperion would automatically set the permissions of an init.d script to 777, but I am not sure.

Let me know if any particular step is confusing or if everything goes as expected but the issue remains.

When using Option 2, it basically reloads my phone to the original stock software. Sensor does work, but Ive lost all of my proposed external storage space and all the settings along with it. Basically its reverted back to stock....

WarrantyVoider · Sep 1, 2015

jckwpt said:
When using Option 2, it basically reloads my phone to the original stock software. Sensor does work, but Ive lost all of my proposed external storage space and all the settings along with it. Basically its reverted back to stock....

Hmm... I thought you were using Xperion? Deleting the "00DataOnSD" init.d script removes the hack, so the phone would go back to using internal storage. Maybe that's what you meant? To change from the Xperion rom back to the stock rom would require you to either flash the stock rom or restore a backup.

Right now your files, data, settings, etc. should still be on the SD card. The hack is disabled until you re-enable/reinstall it. When you do, either by using the init.d version or by using the binary version, your data should hopefully reappear, assuming your rom files are still intact. So don't do anything to alter the ext4 volume on the SD card.

I am not sure what's happened in your case. How did you install the hack originally? Are you using one of the custom recoveries (pressy4pie's CWM 6.0.4.6, hroark13's TWRP 2.6.3.0 or 2.8.0.0)? Did you run into any installation problems when you tried Option 2 mentioned above? I guess you don't want option 1. Did you get on-screen messages when you installed the zip(s) in recovery?

Let me know what you're comfortable doing. Use a working custom recovery to install a zip file or two? All the files and instructions for the binary version are already available. I can answer if you have specific questions. I can package the init.d version with the workaround (post #623) into a flashable zip if you need that. If you prefer to work with console commands to install either version manually, I can help with that too. I don't know what you know and what you don't, so I am just trying to present options to you so that you can make that determination.

jckwpt · Sep 1, 2015

Im so sorry.... I spoke too soon without thinking. It didnt revert me back to stock. It reverted me back to the orginal Xperion installation with the original screen and icons of a new installation. How confusing that comment was! Sorry about that.

Option 1 isnt really viable on my phone cuz I cant install any of your files except the initd file. All the install, sensorfix, etc files wont load for me.

Its actually ok right now. I really like the way the phone works. Your simple few instruction lines I run in terminal with each reboot, which Im fine with. Just takes another 20 sec. With those 3 lines, the phone doesnt freeze looking for the sensor during apps that require it so its already a great solution for me. Thank you already for all your hard work!

WarrantyVoider · Sep 2, 2015

@jckwpt
I see. Maybe your recovery isn't working? You can install hroark13's TWRP. Download the apk. Install the apk. Open app. Install recovery. Reboot to recovery.

I can tell you the console commands to install the init.d script without using recovery. You'd either use ADB or terminal emulator. It's a bit tedious to type all the commands in a terminal emulator on the phone's small keyboard though. You can also use a file manager to copy the script to the directory, change the file ownership, and change the permissions. I am not familiar with the file manager included in Xperion, so I am not sure whether that file manager does all those things.

If you're able to restore the init.d script but the sensor fix still won't work, another possibility is to put the "stop sensord; sleep 1; start sensord" in a script like:

Code:

#!/system/bin/sh

stop sensord
sleep 1
start sensord

Then use Script Manager or a similar app to trigger it automatically after boot-up.

If you're manually entering the commands, you can just skip "sleep 1":

Code:

su
stop sensord
start sensord
exit

The time gap between the "stop sensord" and "start sensord" when you manually enter commands is long enough of a delay.

Let me know if you want specific instructions for something in particular. I am not trying to intimidate anyone with technical jargon. If you're like me who wants technical details to understand how things work, I'll gladly share what I know. If you're a user who just wants straightforward instructions to get things to work, just let me know. I usually try to guess based on the info provided in the question or request, but I don't always guess correctly.

jckwpt · Sep 7, 2015

Once again, thanks WarrantyVoider!

I found out all along I have been using hroark13's TWRP. Your script worked this time.
So I used

#!/system/bin/sh

stop sensord
sleep 1
start sensord

adding at the end of 00DataOnSD file in the init.d folder. No need to manually C&P after bootup now.
This is great. Dunno why my system is so different or has difficulties to others, but it all worked out well.
Thank you again!

The-Truth · Sep 18, 2015

I myself had most success with the Data on SD hack. But thats me and the sweet tricks WV has created that I like to run most. But glad the method youre using is working for you man.

Scotophor · Dec 22, 2017

If anyone cares about a success story of this old mod on a REALLY old phone not much mentioned in this topic, way back in post #16, OP JVene mentioned that his version would work on an LG Optimus F3, which is how Google search brought me here. After studying this entire thread, and with a little knowledge of my phone, I didn't notice anything about the F6 filesystem that appeared any different from the F3's, so I decided to give it a try.

My phone is a FreedomPop bargain-basement special, LS-720 running on Android 4.1.2 and using a slightly modified (by FreedomPop) stock Virgin Mobile ROM and TWRP 2.8.0.0. I bought it a little over a year ago and during most of that time, I've been using Apps2SD by Vicky Bonick, with a SDext2 partition of 2GB and recently ran into the "wall" mentioned somewhere herein, at the point where I still ran out of internal /data storage space.

As a "hands-on" tinkerer, after uninstalling all of the excess apps that Apps2SD allowed and going back to apps on internal storage only, I chose to use the files from post # 251 and the manual/file manager installation method from post # 253, using Total Commander. I'm using a Samsung EVO 64GB U1/C10 card formatted with about 24GB FAT32, 32GB ext4, 2.5GB ext4, and 1GB Linux Swap partitions. The second ext4 partition is for possible future use in case I eventually need it for expanding /cache by a symlink or bind method, or anything like that. On first boot, the /data copying process only took about 2 minutes, which surprised me since I read here that it might take as long as 15-20 minutes with a nearly full /data partition. After the auto-reboot into Android system, everything looked fine. Accelerometer and magnetic sensors work, Settings > Storage reports 30GB total (WOOHOO!) I let the phone sit for 5 minutes and rebooted again. No apparent changes. I'll report back if any problems show up later.

Root Proposal/Theory for External SD storage solution on F6

Newbie

Android Enthusiast

Newbie

Android Enthusiast

Newbie

Android Enthusiast

Newbie

Android Expert

Lurker

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads