MORE INFO IN POST 3 HERE
I am happy to announce the release of my new utility script. This script currently has 11 functions as noted below. It runs in recovery with the help of sdutility which is another script that procures the necessary permissions and file location for some of the features. Some of these options are copied from Cyanogen's various scripts located in his recovery image.
Option 11 will ask you what size to make the swap and ext partitions and then it will partition your sdcard for you using the remaining space for fat32.
The menu looks like this:
Code:
1) Enable SDcard to USB
2) Disable SDcard to USB
3) Upgrade ext2 > ext3
4) Upgrade ext3 > ext4
5) Fix Permissions
6) Repair Filesystem
7) Clear Dalvik-Cache
8) Clear ext partition
9) Backup APPS on ext to FAT32
10) Restore APPS from FAT32 to ext
11) Partition SDcard
Q) Quit Utiltity Menu
Enter Number> _
i am going to get you samuel jackson's wallet from pulp fiction because that is what you are with these scripts.
I think these scripts, along with miketaylor00's fix_rotate script, need to be included in every ROMs /system/bin folders.
Btw, why the . in "./sdcard/sdutility"? I'll probably just move these scripts over to the /system/bin folder on my phone for consistency.
That is an execute command and is required because /sdcard is not in $PATH. sdutility copies the utility script which is the actual script doing all the work to /sbin, setting permissions to 755, and launching it. The point of all of that is with the script on the sdcard it can't partition it without deleting itself.
Fingerlickin said:
That is an execute command and is required because /sdcard is not in $PATH. sdutility copies the utility script which is the actual script doing all the work to /sbin, setting permissions to 755, and launching it. The point of all of that is with the script on the sdcard it can't partition it without deleting itself.
Click to expand...
Click to collapse
I follow... guess I can just keep it on SDcard to run it from.
I looked at the files and figured that's how it worked... I did copy utility to my system/bin and ran it from recovery console. I even backed up my apps using option 9. It gave me an access denied error from line 173 (the fi command in the script). However, it seems it did back up the apps.
dude, this is awesome. im gunna try it out later... using my ubuntu partition.
anyways, when you backup your apps from the ext partition, does it copy over the google apps as well?
backing up the apps copies the /system/sd/app folder to /sdcard/appbackup.
To the best of my knowledge this is NOT a violation because you are backing up your OWN apps including any closed source apps. As long as you don't distribute these apps you are fine.
P.S. I bought a movie tonight and immediately put it in my computer and ripped it. My reason for this is my computer stores all my movies and my xbox streams them to my TV. Nothing wrong with this because I am not distributing the movie to other people.
Fingerlickin said:
backing up the apps copies the /system/sd/app folder to /sdcard/appbackup.
To the best of my knowledge this is NOT a violation because you are backing up your OWN apps including any closed source apps. As long as you don't distribute these apps you are fine.
P.S. I bought a movie tonight and immediately put it in my computer and ripped it. My reason for this is my computer stores all my movies and my xbox streams them to my TV. Nothing wrong with this because I am not distributing the movie to other people.
Click to expand...
Click to collapse
hey finger, let your xbox stream video to my tv as well.
Fingerlickin said:
backing up the apps copies the /system/sd/app folder to /sdcard/appbackup.
Click to expand...
Click to collapse
I feel the urge to clarify this.
mounts both ext and fat32
check to see if both folders exist and creates /sdcard/appbackup if it doesn't
THEN it copies the CONTENTS OF /system/sd/app to /sdcard/appbackup
but david, I'm a good law abiding citizen and that would be illegal.
catch me on gtalk
So has anyone else had the access denied error referencing line 173?
Fingerlickin... any chance you could work with Cyanogen to integrate this with his recovery? I'm thinking it's time for a Cyanogen Recovery v1.5.
Great work fingerlickin
Unasari, the orig plan for this was to make cyan's recovery more noob friendly, hopefully cyan will roll this into his new recovery and add trackball support to it for the mt3g users. Don't be surpised if you see a wrecking crew modified recovey image
Great work I see all of us got something to keep us busy now.
I am looking into the line 173 error now. We need MT3G support before cyan will touch it, working on that too.
I can't recreate the error at line 173. Lets see if others have the problem as well.
Updated to v1.1 see post 3 HERE for details.
This has a possible fix for your line 173 error. I didn't anticipate someone trying to backup apps when they don't have any apps installed on the ext or you try to backup apps after partitioning the card because there obviously isn't a /system/sd/app directory in this case. I have no idea if this will fix your problem or not.
I also included support for ADB (MT3G) YAY
Updated again.
v1.2
updated to fix_permissions v1.29
fix_permissions always has the -r option
Related
After flashing Haykuro's H build to my girlfriend's phone without a wipe everything went a little screwy. So I moved all of her data to the ext2 partition of her sd card, flashed JF RC33 back to her phone and then tried symlinking the data directory. This brought back alot of the same issues (she was getting an inconsistent system ID error).
So I went back to the default data directory as it stood after flashing rc33 and started copying over the /data/data/[app package] folders from the sd card for only the apps that she really needed the data for and even though I can read them in the terminal, for some reason whenever I try to start any apps that I copied the folders over for, they force close immediately. My only thought is that maybe they're owned by the wrong group or something. I tried chmoding them all 777 to see if that helped, but it didn't. I know I have to do a chown to change the owner of the files, but what should I chown it to? 0?
/data/data/* is 755, and the content is owned by the various sandboxed users (Except a handful of androids own services, which is owned by 1000 and 1001).
Symlinking the data directory itself should work just fine, i had the whole data partition symlinked out, until i just decided to mount my ext2 partition as /data.
Well, symlinking the data directory isn't fine. As I said in the original post there's something wrong with her data directory and whenever I boot up with the entire thing symlinked it says it needs a factory reset as there are inconsistent system IDs. So I'm trying to just add them back one by one. Is there any way to determine which user/group ID an app is running as so I can chown the data folder for that app to be the same? My thought is it has to come down to an ownership issue.
I'm far from a guru, but you may want to consider a couple of things.
I finally moved my data off of my sd. I had tons of quirks and force closes as long as data was on the ext2 partition. You may consider just moving apps and dalvik-cache.
If it's your GID that is incorrect, you should be able to go into the sd/data and "ls -l" to see what the ownership for each file looks like. Then verify that is carrying over when you copy it back to internal flash. If it's changing the group you can do a chgrp and change it back to what ever it was in the sd/data directory. Same goes for ownership also... ls-l will tell you who owns it and what group. Like you said, you can chown to change that.
I reall don't think this is going to solve your problems, but give it a shot. Ultimately, i think you're going to have to wipe data. If you did a nandroid before it went south, you might be alright.
Beyond that, i got nuthin... Good luck.
If it was my phone, I would've just wiped it and not thought twice about it. But my g/f is a fanatic about her shopping lists, todo lists, etc.
What I'm thinking about doing when I get home is running a ls -l on the app directory to see if I can see what group ID each of the apps are running at because I'm fairly certain that's what the problem is. The apps are running as one user id after the wipe, but the data is owned by another user id that was being used before the wipe.
Run it, and quickly check the UID with ps ("busybox ash", then "ps", or jut "busybox ps"
, the first one starts a shell, so you only have to write "ps"), then compare to the UID/GID of the files (ls -l, again with busybox).
If they don't match, you should change them with "chown uid:gid /data/data/directory".
If the UID's GID's are correct, you should just copy the contents of the directories out, wipe, run the apps once, and copy the content back in (Then you'll know the correct UID).
You can always take a nandroid backup if you don't trust me
Thanks Joushou, that's actually what I was looking for. I couldn't remember the command to see what the apps are running as. Now, considering they force close immediately, would I be able to run ps before I click force close and still see the IDs?
So in this format, which numbers are the user/group ids? I'm guessing the username is the first column.
USER.....PID PPID...VSIZE RSS..WCHAN PC............NAME
app_24 174 33 89264 13412 ffffffff afe0c824 S com.android.calendar
app_28 186 33 86828 11076 ffffffff afe0c824 S com.android.alarmclock
app_36 217 33 88892 11828 ffffffff afe0c824 S edu.mit.locale
Nevermind, that was from a regular ps. Did busybox ps and it turned up the number I was looking for, thanks Joushou!
LPChris said:
Nevermind, that was from a regular ps. Did busybox ps and it turned up the number I was looking for, thanks Joushou!
Click to expand...
Click to collapse
So were you able to get it working again?
Froyo sux....with apps i get all types of complications...ive done everything re-format and used all methods...no A2SD method works including Google's. I want the Old Method on the Ext.....but not even Rodriguez' works...anyone solutions or people suffering? cuz its either i cant put all my apps or they dont install....i even had a 'Contact Storage' problem where it bloated so big...my phone said i had low memory
+1
Anyone has a working solution for FRF50?
how bout you wait till froyo source is out then when can have all kinds of goodies
teflon252 said:
Froyo sux....with apps i get all types of complications...ive done everything re-format and used all methods...no A2SD method works including Google's. I want the Old Method on the Ext.....but not even Rodriguez' works...anyone solutions or people suffering? cuz its either i cant put all my apps or they dont install....i even had a 'Contact Storage' problem where it bloated so big...my phone said i had low memory
Click to expand...
Click to collapse
Try this rom
http://forum.xda-developers.com/showthread.php?t=644438
I'm not sure but I heard that Froyo doesn't like EXT partitions ...
Perhaps the kernel on the upper link should work. Give a try =)
i'm trying it now....let u kno how it works..and thanks for the suggestions
NO LUCK....DOESNT EVEN READ EXT PARTITION...I DUNNO what the hell KING is talking about
I have stock rooted froyo, and the apps that can be pushed to the sd card go to the fat32 part.
I have not tried using a2sd yet.
I will try pushing an app thru adb tonight to sd and see if it installs.
Update: I installed a couple of apps to the sdcard with ADB. One I don't use anymore, and one that I had installed from the market. I had to uninstall Google Earth, but I now have it installed on the sdcard and it is working just as well as if it were on the phone. Also tried Tower Raiders Free, and it also installed to the sdcard and plays with no problems. So I don't know if froyo needs the ext partition or not, but the newest ADB release does not in order for apps to work.
the benefit of EXT is space and i already have so many apps installed already from previous....the new method allows me only half and i would have to re-install all and for some reason...regular froyo doesnt sit well with my phone....like in 'manage application' it just says calculating...and i can never install certain apps
paul's (MoDaCo) r16 + have apps2sd on ext partition as an option.. i've been using it on ext4 since r16 dropped have about 75 apps including google earth and flash and have 135mb left on internal .. advanced task manager says 223mb with 20 apps running
did u have to activate the option? and how?
no .. its automatic... there are 2 ways... google (froyo) crappy apps2sd and our way of doing things.. just have your sd card fat32 /ext2/3/4 and thats it .. disregard the google froyo a2sd
You can try Darktremor A2SD and see if that works.
The rom you are on would need to have some form of a2sd launch command in the init.rc. In the old stuff, it would be a matter of putting the following lines in the init.rc:
1. Look for a line called class_start default. Add the next two lines above the class_start line:
start a2sd
on property:cm.filesystem.ready=1
2. Go to the end of the file and type the following:
service a2sd /system/bin/logwrapper /system/bin/sh /system/bin/a2sd
disabled
oneshot
Now, I'm not sure about Froyo and its Apps2SD...I'm not sure if you need to find the lines in init.rc (assuming they are actually in that file) and comment them out.
But try the program and see if it works.
http://www.darktremor.info/files/a2sd/a2sd-2.7-2-signed.zip
teflon252 said:
Froyo sux....with apps i get all types of complications...ive done everything re-format and used all methods...no A2SD method works including Google's. I want the Old Method on the Ext.....but not even Rodriguez' works...anyone solutions or people suffering? cuz its either i cant put all my apps or they dont install....i even had a 'Contact Storage' problem where it bloated so big...my phone said i had low memory
Click to expand...
Click to collapse
+1 (topic)
Anyone tried the above post on froyo?
A link to step by step instructions will be appreciated.
Some steps here: http://wiki.cyanogenmod.com/index.php/Apps2SD but dont know what else is needed for froyo.
I want this because my /data partition is completely out of space, and no more apps can be moved using the froyo method.
Forcing all apps to install by default on the sd card is buggy at best.
update: works, see the below post, http://forum.xda-developers.com/showpost.php?p=6952103&postcount=16
Is SWAP partition still necessary ?
I've read that swap is not needed. Works without one for me
@britoso - i see you talk of this file - a2sd-2.7-update3-signed.zip - is that a rom?
milomak said:
@britoso - i see you talk of this file - a2sd-2.7-update3-signed.zip - is that a rom?
Click to expand...
Click to collapse
its a flashable update that installs the a2sd components to your system.
Here is the thread, first message has instructions: http://forum.xda-developers.com/showthread.php?t=670087
britoso said:
+1 (topic)
Anyone tried the above post on froyo?
A link to step by step instructions will be appreciated.
Click to expand...
Click to collapse
just wanted to note that this works fine on Froyo FRF83 too.
I used Paul Obrien's FRF83 rooted, deodexed rom.
1)nandroid+ext
2)flash frf83
3)flash apps2sd
4)reboot
5)bootloop!
to fix it:
Code:
adb remount
adb shell mkdir /system/sd
adb shell
/system/bin/a2sd install
a2sd repair
a2sd check
6)success!
edit: it does not start automatically on reboot, flash leofroyo's boot.img in bootloader mode to fix it
fastboot flash boot leofroyoboot.img
Click to expand...
Click to collapse
i seen this in the Samsung Galaxy S I9000 and i tried it out on the vibrant and it works perfect, its probably the easiest way to partition your SD card and i can confirm it fixes the lag, i will post my scores shortly...... THANKS RYANZA you saved me weeks of research. go here for more info
http://forum.xda-developers.com/showthread.php?t=751864
[UTIL] One Click Lag Fix 2.0
This version (2-3) is now open for BETA testing! It is known to work on many devices, but still has known issues that could greatly affect you. Please read this whole post a few times until you understand!
Details about what this fix does:
Creates a VIRTUAL EXT2 filesystem inside the stock RFS filesystem on the internal SD card, with a 4KB block size. This means that this lag fix creates a buffer between the real filesystem and the android system. This buffer should reduce the amount of disk I/O required for all operations by utilizing EXT2 buffering, as well as not writing file access times to disk, etc.
Folders that are currently supported:
/data/data
/data/system
/data/dalvik-cache
/data/app
/data/app-private as a symlink to /data/app/app-private
/dbdata/databases is not supported. It appears to be ROM backed, and can cause problems if overwritten.
Benefits over version 1
1.5GB of application data available, with no data loss.
e2fsck of the EXT2 partition on each boot.
Correct busybox version included! YES!
/app and /app-private directory included in the fix for faster application installs.
/dbdata/databases included in the fix, expected to give a big performance boost for apps that use it.
Mounts instead of symlinks for extra performance as OS does less work (about 100 or so more quadrant).
Benefits over other lag fixes
Open source, with full comments and ease of editing.
Works on any and all firmware versions, including any yet unreleased froyo versions (that don't change file structure).
Credits
Big thanks to mimocan for putting us all on the right track in how to sort out lag problems!
Big thanks to ykk_five for showing us all how well loopback filesystem mounting works!
Big thanks to cyanogen mod for e2fsck
Requirements for One Click Lag Fix 2.0
Rooted phone - http://www.addictivetips.com/mobile/how-to-root-and-unroot-samsung-galaxy-s-i9000-with-a-single-click/
Windows computer with SGS Drivers (Samsung Kies), or the ability to read through the batch file and run it yourself.
(Beta Release) The ability to reflash your device if something goes wrong.
No other lag fix installed. If you installed One Click Lag Fix 1.0, then use the uninstall function which came with that lag fix before running this lag fix. (Untested but assumed to be working, please help out here.)
1.5GB of freespace on Internal SD Card for swap files while the fix is working (/sdcard).
"Internal phone storage" in Settings->SD Card must read greater than 500mb (0.5GB) of free space.
How to run One Click Lag Fix 2.0
Place your phone into USB debugging mode: Settings->Applications->Development
Attach your device to your computer. Do not mount the drives.
Download the attached ZIP file.
Unzip to a folder of your choice.
Double click "lagfixme.bat".
Don't double click "unlagfixme.bat".
Wait for it to complete.
You will need your phone to be unlocked when it runs the script, so that you can accept the permissions request that will appear on your device.
How to remove One Click Lag Fix 2.0
Double click "unlagfixme.bat"
Wait for it to complete.
Known Issues For All Versions
Some custom firmwares use up all available space in /system. This fix requires some libraries to be placed in /system/lib. These libraries are used to create the filesystem properly, and to check it for errors on every boot.
If your firmware does not have the available space (around 1mb) in /system, do not use this fix! Your phone will not boot and will have to be restored from backup / reflashed.
Current known firmwares with this issue: None yet. Please provide the firmware version+mods if you encounter this issue. It will show up as an out of space error in the log, under 'Copying libraries'.
Known Issues 2-1, 2-2
Paid apps from the market have issues.
Google maps and other pre-installed ROM-backed applications have issues.
2-3 Changes from 2-2
/dbdata has been removed. This fixes maps issues.
/app-private is now a symlink to /app/app-private. This fixes paid apps issues.
Alternate installation methods for similar fixes
Tayutama has made an update.zip version that is easy to install - http://forum.xda-developers.com/show...&postcount=208
Chainfire has a .NET version of this fix with some nice features - http://forum.xda-developers.com/showthread.php?t=751513
I recommend starting from scratch to avoid any problems
my setup is
1.) True 2.1 Samsung T mobile Image http://tinyurl.com/2bc5b6r
2.)BETA OC 1.2Ghz (no added steps for now)
kernel-vibext4-oc1.tar.md5
MD5:d1e26f769406c5d368492855c7b5059e
...you can try his new version of the kernel if you like, my phone i runs fine on the beta , so i havent tried the new ones
more info on the kernal hack http://forum.xda-developers.com/showthread.php?t=744655
3.) RyanZAEXT2LagFix BETA 2-3.zip http://forum.xda-developers.com/attachment.php?attachmentid=384443&d=1282320979
this is the exact order in which i modded my phone and i have no ran into any problems, it was a smooth process , and yes it was my first time modding my samsung phone and i rate it as very easy to do.
Click to expand...
Click to collapse
Frequently Asked Questions
Q: My apps are force closing while this fix is running, and I can't use my phone!
A: By design. The script has backed up/copied your apps over to the internal SD card (remember the requirement about 1.5GB of free space on the SD card?). It is now overwriting them with a 1.5GB file. As the file overwrites an app that is trying to do something, it will probably force close. This is normal.
Closing all running apps, and removing widgets before running this fix can make the process much smoother, though.
Q: The script can't transfer files to my phone / The script can't run / Help help I'm dieing!
A: Read the first post again.
Q: My paid apps from the market don't show up.
A: I will hopefully have a fix for this sooner or later. Hold tight! It's in the known issues. I don't have access to paid apps, so I can't test this.
Q: Does this need busybox?
A: No, busybox is included.
Q: I only have 200mb of free space now! What gives?
A: The lag fix has made a 1.5GB file, and is storing all of the data inside there. The side effect is that the free space meter is now incorrect. Sorry, this can't be helped.
You can check real free space by using ADB like this:
Code:
adb shell
su
busybox df -h
Q: When I use a backup tool, the backup is now 1.5GB big! It's taking forever!
A: The backup tool isn't designed to work with this fix. It will work, it just won't work well. Hopefully this fix will be short lived, and either Samsung will give us a new update, or someone will give us a good custom firmware that can natively mount what we need, where we need it. Or someone might come out with a better backup manager. Until then, we suffer.
Q: Will a reflash wipe this fix?
A: Yes, a reflash will wipe everything this fix did.
Q: Can this brick my phone?
A: If you know how to get to the download mode from power off (hint: volumedown+home+power), then almost nothing short of throwing your phone off a tall building can actually brick it. If you can't do this though, or don't know someone who can, then you're better off waiting for samsung to release a fix. Anything that moves files around on your device has the potential to break things, and this fix has no QA department.
Q: Why is /dbdata not included in your fix, but other people have included it?
A: Other people have included it in the same way my 2-2 fix includes it. However, /dbdata is ROM backed. This means that the real files are on ROM, and only the changes appear in the /dbdata folder. When copying or moving files from this folder, you would need to specify each folder by exact name to ensure that it was copied across, and each firmware can have their own names. (This is because RFS wildcard will not catch an unused ROM backed file.) In some cases, you can get lucky and have this work perfectly because you have already used all the files in /dbdata. There is no fail safe method to do this though, and /dbdata does not make a big difference to performance. (It is already on NAND flash.) If you want to try your luck, v2-2 is still available.
Q: Why does this lag fix work? Is it slowly destroying my phone?
A: Let's say an application counts from 1 to 10, and writes the value each time to disk.
Stock:
1 -> App tells RFS to write 1 to disk -> RFS writes 1 to disk -> RFS writes journal saying to changed the value on the disk.
2 -> App tells RFS to write 2 to disk -> RFS writes 2 to disk -> RFS writes journal saying to changed the value on the disk.
..
9 -> App tells RFS to write 9 to disk -> RFS writes 9 to disk -> RFS writes journal saying to changed the value on the disk.
10 -> App tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 20. Speed: SLOW! Wear and tear on disk: HIGH!
Lag Fix:
1 -> App tells EXT2 to write 1 to disk -> EXT2 stores 1 in RAM.
2 -> App tells EXT2 to write 2 to disk -> EXT2 stores 2 in RAM.
..
9 -> App tells EXT2 to write 9 to disk -> EXT2 stores 9 in RAM.
10 -> App tells EXT2 to write 10 to disk -> EXT2 stores 10 in RAM.
..
EXT2 tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 2. Speed: FAST! Wear and tear on disk: LOW!
This isn't exactly what is happening, but it gives you the general idea.
Q: Can this mod work on other Android devices? Would we see a performance boost on them as well? If not why is it limited to the Galaxy S?
A: SGS has very very good hardware, but it has some parts of it's hardware poorly implemented. The filesystem that samsung chose to use is custom-built using FAT32 as a base, RFS. It has a lot of the problems that FAT32 has, and should have been left back in the 90s, or even the 80s.
One of the big issues with it is how it handles multiple requests - it blocks. It blocks everything. When your mail app wants to read the mail you just tried to view, but your twitter app is busy writing a new tweat it just received, your mail app is forced to wait.
This is bad, but it could be worse! And it is... your twitter app didn't just get one tweat, it got 50 tweaks. It is busy writing the tweats one by one to the filesystem. This would be fine, since all modern filesystems will buffer writes, so instead of writing each one at a time, they will batch them together and write it as a big chunk. Uh oh - RFS does no buffering at all! After each write, it will also write an update to the grafted-on journal system. Guess what happened to your mail you were trying to view while all this happened? It 'lagged' and you got a black screen for half a second, before the mail popped into view.
Luckily the hardware on the device is so good that you usually don't even notice the problem until you have a lot of apps running, all writing their updates when you unlock the phone.
This is mostly speculation based on experiments done on RFS -- RFS is closed source, and we have no idea if the problems are just badly set settings (such as a block size that is too small), coding bugs in the implementation, or if RFS is just really that badly designed.
This fix just grafts a buffer on top of the RFS filesystem, using a very very simple and fast filesystem, EXT2. It fixes most of the issues by writing to RFS as seldom as possible.
So no, this fix won't fix other devices, since they're already running quite close to maximum speed. The SGS at stock is running nowhere near maximum speed, and this lag fix takes it a bit closer. You could probably speed up other devices by tweaking the filesystem settings to give them a big buffer or similar, but it isn't really needed. (I haven't actually tried to put an EXT2 onto any other Android phone, as I don't have any other Android phone, so this is just speculation.)
Q: My phone is fast now!
A: Yeah.
Last edited by RyanZA; 18th August 2010 at 10:52 PM..
I used this yesterday. Works a treat! Just be patient when its running.
Texted While Driving
You need to fix the links if you reposted it
lqaddict said:
You need to fix the links if you reposted it
Click to expand...
Click to collapse
i fixed the links before i reposted it and re-added the attachments , is there a certain link i forgot to fix ?
===============================================================
===============================================================
One Click Lag Fix for Galaxy S I9000
===============================================================
===============================================================
__________________________________________________________
Pushing required files to /sdcard - Please wait.
* daemon not running. starting it now *
* daemon started successfully *
mkdir failed for /sdcard/lagfixtemp, File exists
cannot stat 'createlagfix.txt': No such file or directory
cannot stat 'playlogos1': No such file or directory
cannot stat 'userinit.sh': No such file or directory
cannot stat 'busybox': No such file or directory
cannot stat 'e2fsck': No such file or directory
cannot stat 'libext2_blkid.so': No such file or directory
cannot stat 'libext2_com_err.so': No such file or directory
cannot stat 'libext2_e2p.so': No such file or directory
cannot stat 'libext2_profile.so': No such file or directory
cannot stat 'libext2_uuid.so': No such file or directory
cannot stat 'libext2fs.so': No such file or directory
cannot stat 'mke2fs': No such file or directory
cannot stat 'resize2fs': No such file or directory
cannot stat 'tune2fs': No such file or directory
Now running lag fix. On your device, select allow root privledges!"
/system/bin/sh: Can't open /sdcard/lagfixtemp/createlagfix.sh
Script complete!
* server not running *
Press any key to continue . . .
any help?
did you unzip the files and put them all in the same directory ???
bobby915 said:
===============================================================
===============================================================
One Click Lag Fix for Galaxy S I9000
===============================================================
===============================================================
__________________________________________________________
Pushing required files to /sdcard - Please wait.
* daemon not running. starting it now *
* daemon started successfully *
mkdir failed for /sdcard/lagfixtemp, File exists
cannot stat 'createlagfix.txt': No such file or directory
cannot stat 'playlogos1': No such file or directory
cannot stat 'userinit.sh': No such file or directory
cannot stat 'busybox': No such file or directory
cannot stat 'e2fsck': No such file or directory
cannot stat 'libext2_blkid.so': No such file or directory
cannot stat 'libext2_com_err.so': No such file or directory
cannot stat 'libext2_e2p.so': No such file or directory
cannot stat 'libext2_profile.so': No such file or directory
cannot stat 'libext2_uuid.so': No such file or directory
cannot stat 'libext2fs.so': No such file or directory
cannot stat 'mke2fs': No such file or directory
cannot stat 'resize2fs': No such file or directory
cannot stat 'tune2fs': No such file or directory
Now running lag fix. On your device, select allow root privledges!"
/system/bin/sh: Can't open /sdcard/lagfixtemp/createlagfix.sh
Script complete!
* server not running *
Press any key to continue . . .
any help?
Click to expand...
Click to collapse
djkdawg said:
did you unzip the files and put them all in the same directory ???
Click to expand...
Click to collapse
i extracted all files to desktop and ran lagfix.bat from there
bobby915 said:
i extracted all files to desktop and ran lagfix.bat from there
Click to expand...
Click to collapse
do you have usb debugging enabled? do you have any other lag fix installed ?
djkdawg said:
do you have usb debugging enabled? do you have any other lag fix installed ?
Click to expand...
Click to collapse
Got it working thanks
bobby915 said:
Got it working thanks
Click to expand...
Click to collapse
no problem, download the quadrant standard app and run the test and post your score
I got 2072 quadrant score for the phone after the fix, how did the OP manage to get 2700+?
I'm still on version 1 with no issues. Any major differences or Improvements.
Uninstalled the Alpha fix and tried this one. upon reboot, I'm getting an error:
Memory Full
Internal phone storage is nearly full
Delete/Uninstall some applications or data
Didn't have this problem with the alpha fix.
Guess I shouldn't had played with the beta.
Any ideas?
Running Stock Kernel, just rooted.
I'm running Unlagfix now to remove.
Side note: I noticed that my custom font settings disappeared... Icons still appear to be in the same place.
Update:
I just re-read the FAQ. Storage reporting error... heh.. doh.
However, when running uninstall, it started streaming the following error message about 20-30 times over:
cp: write error: No space left on device.
Can't create directory 'data/bak/app': No space left on device
Update again:
Unlagfix didn't seem fully successful. All my application data/etc disappered. Looks like they are still in the /data/ directory, but not showing up on the device.
Here is a listing result
If I'm reading this correct, does that mean the Unfixlag didn't complete it's task? Looks like I still have a 1.5gb partition for data.
Tairen said:
I got 2072 quadrant score for the phone after the fix, how did the OP manage to get 2700+?
Click to expand...
Click to collapse
i started from scratch, i flash the true tmobile vibrant image to start from scratch, you dont have to do this but i did. Link is below
http://tinyurl.com/2bc5b6r <-- true tmobile vibrant image, it also includes odin
after that was done, i used the utility to format my card, you can get the one click utility below
http://forum.xda-developers.com/showthread.php?t=751864
after that i reboot, install the app and did a test and thats how i got my speeds.
edit: after installing all my apps back, i actually average about 2400-2500 , i havent seen the 2722 after installing all my apps
i would start from scratch like i did when i first tried it, because i think the other lagfixes actually jacked something up. follow the steps below
i started from scratch, i flash the true tmobile vibrant image to start from scratch, you dont have to do this but i did. Link is below
http://tinyurl.com/2bc5b6r <-- true tmobile vibrant image, it also includes odin
after that was done, i used the utility to format my card, you can get the one click utility below
http://forum.xda-developers.com/showthread.php?t=751864
after that i reboot, install the app and did a test and thats how i got my speeds.
Spiffywerks said:
Uninstalled the Alpha fix and tried this one. upon reboot, I'm getting an error:
Memory Full
Internal phone storage is nearly full
Delete/Uninstall some applications or data
Didn't have this problem with the alpha fix.
Guess I shouldn't had played with the beta.
Any ideas?
Running Stock Kernel, just rooted.
I'm running Unlagfix now to remove.
Side note: I noticed that my custom font settings disappeared... Icons still appear to be in the same place.
Update:
I just re-read the FAQ. Storage reporting error... heh.. doh.
However, when running uninstall, it started streaming the following error message about 20-30 times over:
cp: write error: No space left on device.
Can't create directory 'data/bak/app': No space left on device
Update again:
Unlagfix didn't seem fully successful. All my application data/etc disappered. Looks like they are still in the /data/ directory, but not showing up on the device.
Here is a listing result
If I'm reading this correct, does that mean the Unfixlag didn't complete it's task? Looks like I still have a 1.5gb partition for data.
Click to expand...
Click to collapse
Just a heads up!
A new version is available for people having trouble with this lag fix, check it out here:
http://forum.xda-developers.com/showthread.php?t=760571
It is designed to be easy to use and a lot safer.
Just wanted to say thanks to djkdawg for posting this and RyanZA for all the work!
im having font issues how about anyone else? i had choko cooky as my default and now it doesnt work anymore...
edit: no fonts work...
Code:
Making new directories to use as mount points for later.
We will now create a 1.5GB real EXT2 partition /data
Will take a long time.
dd: /data/linux.ex2: No space left on device
Linking loopback to the 1.5GB data file store
Creating the EXT2 filesystem
mke2fs 1.40.8 (13-Mar-2008)
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
Creating a mountpoint for files.
Mounting device
mount: Invalid argument
Copying data across. This could take a bit of time.
I keep getting this error when attempting to install. Not sure what's going on. I've got 8.5gb free on internal memory before beginning install. That should be plenty.
I understand that the solution to this question may already exist in the forums, however, I did check high and low for it, and was unable to locate one.
Here goes:
I like (as I'm sure others do) to install apps2sd, something I'm able to do thanks to the actively-rooted and cyanogen-modded N1 that I use.
Unfortunately, the actual *install* files *themselves* from all Market-downloaded apps seem to remain in the phone's internal memory, clogging up preciously limited space. How do I get rid of these install files? I tried using a file manager to go into the mnt/asec directory to get rid of *.pkg's, but these seem to be uninstall-protected (I'm not even sure if I'm making a mistake from the get-go in trying to purge the *.pkg's), so I'm kind of back to the drawing board on this one.
Any help on this would be pretty invaluable folks.
Thanks,
Eli
If you've installed a lot, your dalvik cache will grow pretty big. That's found in /data/dalvik-cache.
Thanks Rusty - but my /data dir is completely empty (unless there are invisible folders; if there are, who you know how I can make them visible?).
Best,
Eli
You need SU access to view /data, make sure what you're using to browse it supports that.
Ahh, thanks Rusty - will do that
Your DATA folder is inaccessible, unless you use Root Explorer or other file explorer with root privileges (ES Explorer, for example - but it doesn't work with all ROMs).
There are no PKGs. There are APKs. And you're wrong in your assumption that they aren't used. This is no PC, this is Android, forget what you used to know, you need to learn again. APKs are the actual applications being ran, without them you can't execute anything, and using old Apps2SD, AKA Apps2EXT, you can move your /data/data to SD (EXT partition) and /data/dalvik-cache to /cache. CM doesn't support Apps2EXT, but it can be easily installed and used, following the guide in DarkTremor's thread. Read Wiki in my sig, it'll point you in the right direction. You can start by reading FAQ, question 9.
seekingandroid said:
I understand that the solution to this question may already exist in the forums, however, I did check high and low for it, and was unable to locate one.
Here goes:
I like (as I'm sure others do) to install apps2sd, something I'm able to do thanks to the actively-rooted and cyanogen-modded N1 that I use.
Unfortunately, the actual *install* files *themselves* from all Market-downloaded apps seem to remain in the phone's internal memory, clogging up preciously limited space. How do I get rid of these install files? I tried using a file manager to go into the mnt/asec directory to get rid of *.pkg's, but these seem to be uninstall-protected (I'm not even sure if I'm making a mistake from the get-go in trying to purge the *.pkg's), so I'm kind of back to the drawing board on this one.
Any help on this would be pretty invaluable folks.
Thanks,
Eli
Click to expand...
Click to collapse
1) The .apk isn't the install file it _is_ the application. The are no "install only" parts to an android app
2) Anything on /mnt/asec is already on your sdcard using froyo-style a2sd
3) .so files in /data/data/xxx/lib and /data/dalvik-cache are the primary causes of full /data partitions
EDIT: Fixed! Procedure I used was to download Danifunker's system dump, move it to /sdcard/ via adb push, then run the following:
Code:
adb shell
su dd if=/sdcard/mmcblk1p21.img of=/dev/block/mmcblk1p21
This completely refreshed my /system folder. Original post below:
--------------------------------------------------------------
Hello XDA forumgoers, longtime reader first time poster here. I'm currently posting because I made a few mistakes. Several mistakes, actually.
1. In my quest to de-bloat my XT860, I accidentally removed one file too many, which caused my phone to mysteriously not have a cell signal. (com.motorola.service.main kept crashing.) So I hit the forum and grabbed a system dump from this thread (thanks Willis111):
http://forum.xda-developers.com/showthread.php?p=17501981
I had bought the phone with some version of Cyanogenmod Recovery installed by the previous owner, so I was able to use that and ADB to stick the .apks and .odex files in the /system/app folder, chmod 644 them, and even factory reset for good measure.
2. As I soon found out, I had somehow made things worse. The phone, when boot into, shows the "press android to begin" page, but com.motorola.service.main and some other apps keep FCing on me, and I can't progress past that screen. In my haste, I didn't backup any of my system folders at all, though, I still backed up my apps with Titanium.
Tl;dr:
presumably none of the /system/app apks boot, most notably com.motorola.service.main. How do I fix this? Can I?
Try to flash
http://forum.xda-developers.com/showthread.php?t=1288823
You also need to chown 0:0 both the apk and the odex
Have you tried using my original system dump? It was taken with dd, so things like symlinks and the other sort should be functional. The only caveat is that a number of apps were frozen at the time, so you may need to unfreeze them with titaniumbackup.
http://www.multiupload.com/SORQERFAYT
DoubleYouPee: Is this that chinese rom I've heard of? I heard that if I flash this, I can't root my phone. So I think I'll save this one as a last resort.
eww245: chown'd, no result.
daniflunker: how do I open this?
jonsicoli said:
DoubleYouPee: Is this that chinese rom I've heard of? I heard that if I flash this, I can't root my phone. So I think I'll save this one as a last resort.
eww245: chown'd, no result.
daniflunker: how do I open this?
Click to expand...
Click to collapse
What about rootkeeper?
DoubleYouPee said:
What about rootkeeper?
Click to expand...
Click to collapse
I can't get past the "click android" screen, so I probably can't install or run it. Any way to do it via adb or Cyanogenmod Recovery?
I really appreciate the help.
jonsicoli, if you want to restore your *entire* /system folder (not just apps) you would run a similar command-set as this.
1. Copy the file to the internal memory
adb push c:\path.to.folder\mmcblk1p21.img /sdcard
the file will be located in the root of the sdcard (or you could drag and drop the file in USB storage mode)
2. Do a full restore on system memory *I have not checked to ensure this is working... but a command similar to this should work
adb shell
su dd if=/sdcard/mmcblk1p21.img of=/dev/block/mmcblk1p21
- wait -
(it would have to write about 500mb and replace all of the contents of /system )
reboot
_______________________________________________________
Okay, if you just want to look at the files, you could use a linux machine to mount the filesystem (it is a standard ext3 FS) or you could do what I have done on my windows system:
Install EXT2FsD from http://sourceforge.net/projects/ext2fsd/files/latest/download?source=files
Then install OSFMount from http://www.osforensics.com/tools.html
Point the OSFMount program to the img file that you downloaded and assign it a drive then voilla!
I am pretty sure this is a bit of overkill, but this should completely restore your system close to factory (minus the APKs that were upgraded/disabled, plus the fact root was done)
Thanks Danifunker! I reset my entire /system folder, and restoring my user app backup. I'm just relieved to have my phone back. Now to mark this thread as solved.
Awesome!!!!!! Glad to hear my system dump works! Thanks for testing
My command lines were written correctly also I guess?
Sent from my XT860 using XDA App
searched for like 8 hours until i found this thread. Just what i needed, i had system image for 2.3.6 from your other post but no command.