Related
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
I REALLY need some assistance, think I screwed my phone, really want to avoid a hard wipe.
I installed Lockbot the other day, has some issues with dual lock layers (i.e. the lockbot app wasn't disabling my HTC lock so I had two unlocks.). emailed dev and he sent me a beta version to hopefully correct issue. I only received an apk file from him.
FYI I am on fresh 1.1, rooted.
I used the kitchen to puch this file: "LockBotPro_1.10.0_beta.apk" to /system/app.
The install went successfully, but later after a reboot I face a HUGE issue. The lockbot app is hanging upon reboot and will not unlock. At first I thought i would still be okay, I had ATK and Advanced Task manager both running at start up, so I can enter both of them through my notification drop down menu. I used both to kill the task-to no avail it is still locked. I tried to use advanced task manager to uninstall lockbot - to no avail, it cannot be removed.
Then I tried to pull back the file through kitchen, to no avail.
I don't know what to do. I cannot get my phone to unlock and i cannot pull the file off through adb or kitchen. DOES ANYONE HAVE ANY IDEA ON HOW TO FIX THIS??????
I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone
wtphoto said:
I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone
Click to expand...
Click to collapse
I have tried to pull the file in both adb and in kitchen. Would it have installed as something other than the name I pushed it under?
Even if the phone is hard locking (kind of rare of android. even in all the stupid f'd up things I've done I've only hard locked my phone to the point that I couldn't even get in to adb once or twice) then the file system is still completely accessible while it's booting up. You can use the "pull any file" from the kitchen and check off that you want it to delete it after it's done. Just get it all queued up in the kitchen and then power on your phone. Once it gets passed the HTC logo wait a few seconds and then run the pull file from the kitchen. Should work just fine for you.
The alternative (if you are comfortable with adb) would be to boot your phone in to recovery (can also be done through the kitchen, even when it's in the middle of booting) and then type the following from a command prompt:
adb shell mount /system
adb shell rm /system/app/your-application.apk
FYI for future reference you should push these types of applications to /data/app. Your hard locks could either be caused by the fact that the beta just broke things, or it could be that you have a copy of it in both /data/app and in /system/app.
the problem is that you dont want to just pull the file all that does is create a copy of the file where ever you pull it to you need to use the rm cmd to actually remove the file and have you tried to do this from the recovery menu before the phone boots? I mean I am by no means an expert but commonsence says that if you do it in the recovery menu that it would be gone when the phone actually boots and the problem would be gone.
edit: sweet im not a complete noob anymore I was right about removing from the recovery. flipz explained it better though.
thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!
TF1984 said:
thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!
Click to expand...
Click to collapse
I'll be here.
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
You have a nandroid backup... don't you? Actually what you can try doing is flashing fresh right on top of itself. You won't lose any settings and it will overwrite everything in /system/app.
I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.
TF1984 said:
I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.
Click to expand...
Click to collapse
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).
Flipz I swear one day I am going to make a sizeable donation to you. If I can only find some extra money.
I think you have helped in every issue I have had after rooting, there haven't been many but you are always helpful when I run into trouble.
Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.
TF1984 said:
Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.
Click to expand...
Click to collapse
Might be worth it for you to try clearing your dalvik-cache to see if it fixes your FC's. If that doesn't work then my guess is you are using apps2sd and the symlink got broken somewhere along the way.
And no problem.
Yes I am using apps2sd. I tried the davlik clear cache in kitchen earlier today in attempt to fix the lockbot (I don't know, figured maybe it would work since i have no idea what that does to begin with).
Question, I did pull my sd card out earlier while the phone was off. Then booted and it only went into a boot loop, is that likely to have caused the FCs?
Does that mean that I cannot ever remove the sd card at all or will always cause this problem...cause that would friggin suck a big one!
flipzmode said:
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4942088&postcount=2 -- post #2 from the fresh rom thread from back in november.
The reason I don't like it is because it puts your phone at a huge risk of having problems once anything goes wrong. If you install a program that causes issues, a nandroid backup will not resolve the issue because the application is installed on your SD card not your phone. If your phone starts going crazy as reported here and here, then even just a restore possibly won't fix it. You might need to go as far as to wipe your SD card too. If you are lucky enough to have a restore fix your problems you will still need to reinstall every app, even if you didn't wipe your card. And on top of that when you try to reinstall any app it will think it's still installed, even though you restored your phone. But when you click "uninstall" it will just freeze half the time because there's nothing on the phone for it to actually install. I have also read many threads that say if you happen to boot the phone up without the SD card in then it will screw everything up.
Click to expand...
Click to collapse
yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?
TF1984 said:
yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?
Click to expand...
Click to collapse
Make sure you aren't forgetting the leading slash. /data/app not data/app. But no, nothing special. That should work. Although if using apps2sd you might want to push to /data/sd/app. It should work regardless because a2sd sets up a symlink but if your stuff is messed up then it might not be working right.
TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
Type this command in to mount:
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
That will mount the /system volume and put it in read-write mode.
Once you are finished deleting the file, type:
umount /system
Then reboot the phone.
Edit: If you want to mount the /data volume, type: mount -o rw -t yaffs2 /dev/block/mtdblock5 /data
Hello XDA team
First of all, I think that this is the appropiate forum for this question, but if it doesn´t, please feel free to move to the correct thread.
I have a spanish Vodafone HTC Magic (32B) and after several combinations I have found that the most suitable partition system for my SD card is Fat32 + 128 MG of Swap. I really hate a2sd and Ext partitions because my device doesn´t really need them, and it only mess my apps.
I´m searching a way to disable a2sd from the .zip files of ROMs in order to be able to install in my phone, but I´m not sure hot to made it
If I take, for example, MightyMax latest ROM (MghtyMax1.9.1) and extract the contents, I find "a2sd" under /system/bin, so, if I remove this app and zip again the ROM, will I be able to "Skip" this feature? should I edite the user.conf and or userinit.sh files?
Many thanks for your help
Rgds
If its a question it goes to Q&A no matter what type of question it is. Just an FYI ^_^
u can try it. I dont know if it will work or not. Just remove all traces of a2sd and resign the update.zip. The other thing is, u can just not have an ext2 partition. That will disable a2sd from the first boot...
nephron said:
u can try it. I dont know if it will work or not. Just remove all traces of a2sd and resign the update.zip. The other thing is, u can just not have an ext2 partition. That will disable a2sd from the first boot...
Click to expand...
Click to collapse
The problem is that ROMs that require a2sd won´t boot (tried MLGIN, MightyMax, Sense Hero..) with my partition layout, they all keeps in the boot screen
thats because u they want ur layout to be like this
fat32,ext2,swap
the only thing u can do is
fat32,ext2,swap
then remove ext2 leaving a gap. After that, expand your fat32 to cover over the ext2.
so ur new layout would be fat32,swap but the swap partition would be on the third partition... (i think )
You could try using the script included in Wes Garner's update here to disable A2SD (should be able to replace the script in the update file of the ROM you are using).
Moved to Q&A
daveid said:
You could try using the script included in Wes Garner's update here to disable A2SD (should be able to replace the script in the update file of the ROM you are using).
Click to expand...
Click to collapse
Many thanks Daveid, sound very interesting, I will give it a try later..
I tried re-build the MghtyMax ROM removing the a2sd bin file and adjusting the user.conf and userinit.sh files but after installing the "new" ROM (it installs just fine) the phone keeps forever in the "Vodafone" bootscreen... Any ideas??
Rgds
iamarock said:
Many thanks Daveid, sound very interesting, I will give it a try later..
I tried re-build the MghtyMax ROM removing the a2sd bin file and adjusting the user.conf and userinit.sh files but after installing the "new" ROM (it installs just fine) the phone keeps forever in the "Vodafone" bootscreen... Any ideas??
Rgds
Click to expand...
Click to collapse
Your SD card has three partitions right? And, why remove the a2sd bin file? I would use the modified script I linked you to, make a very small ext2 partition - so you can put your user.conf & userinit.sh files on it, and see what that does.
What is the logcat (or ddms) output during boot up?
daveid said:
What is the logcat (or ddms) output during boot up?
Click to expand...
Click to collapse
Sorry but I think that I'm a newbee with this kind of issues, how can I get the boot logs???
Many thanks
daveid said:
Your SD card has three partitions right? And, why remove the a2sd bin file? I would use the modified script I linked you to, make a very small ext2 partition - so you can put your user.conf & userinit.sh files on it, and see what that does.
What is the logcat (or ddms) output during boot up?
Click to expand...
Click to collapse
Sorry guys but nothing seems to work for me...
-I have tried to disable a2sd editing the user.conf file and re-building the ROM. Nothing happens. The "new" ROMS installs just OK but it keeps forever in the Bootscreen logo
-The script mentioned by daveid in entry #5 neither seems to work for me, same bootloop
Any ideas??
Many thanks in advance, this is a very annoying issue for me
Anyone can help me with this issue?
Many thanks in advance
Rgds
iamarock said:
Sorry guys but nothing seems to work for me...
-I have tried to disable a2sd editing the user.conf file and re-building the ROM. Nothing happens. The "new" ROMS installs just OK but it keeps forever in the Bootscreen logo
-The script mentioned by daveid in entry #5 neither seems to work for me, same bootloop
Any ideas??
Many thanks in advance, this is a very annoying issue for me
Click to expand...
Click to collapse
Please, please, anyone can help me with this request? I tried to install the amazing Kink's Droid Eris port without sucesss, i guess that again due the a2sd issue
Is there any way to remove a2sd or to skip ext2 requirements when installing a rom?
Many thanks in advance
Best regards
Hi guys.
I know that the z4mod can successfully patch a Tab kernel, without any problems (I did it myself, flashed it, and ran it just fine for a few days).
But when I tried to run one of the zip files to switch the file system, everything went nuts and I had to reflash my Tab from scratch.
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
So if anyone around here knows anything about this sort of business, please take a look at it and let me/us all know, cuz it would be GREAT to get z4mod working on the Tab.
Here's the web site if anyone's interested;
http://www.sgscompilebox.dreamhosters.com/
Hi, did you tell ryanZA what results you got? I'm sure he'll be interested to help.
However, thank you for trying, I was about to do the same.
Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?
knightnz said:
Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?
Click to expand...
Click to collapse
RFS is Samsung's partition format (FAT + journal) that is supposed to be better for flash devices. Apparently it is not so good, and very laggy. Therefore people are switching partitions to ext2/3 or moving and linking stuff to SD card with ext2/3 or jffs2 partition.
jeebspawnshop said:
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
Click to expand...
Click to collapse
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Fyi: http://forum.xda-developers.com/showthread.php?p=9629477#post9629477
doloop said:
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Click to expand...
Click to collapse
It has been tested by many Galaxy S users. Go to their forum and you will know
evermick said:
It has been tested by many Galaxy S users. Go to their forum and you will know
Click to expand...
Click to collapse
I'm really newb on linux, but i've read a little since last post.
What if we:
1 - dump mount list from a working SGT (terminal or adb shell -> mount ?)
2 - apply Z4mod then SGT won't boot (i assume it creates /etc/.fstab)
3 - edit /etc/fstab to match the dump in step 1
But, how do we read/write /etc/fstab once the sgt is locked ? using some kind of update.zip, or is there some shell service we could connect to, even if some mounts aren't in the right place ?
Unfortunately, everything I could contribute to this idea was in my first post. I know absolutely nothing about Android development, sadly...
But after reading what Deodexed said about volumes not mounting properly during recovery (he's the guy trying to get CWM to work for our Tabs) it seems that maybe that's the reason that z4mod may not work... If the volumes aren't mounted correctly, it can't convert the filesystems.
Maybe what doloop said might work? I hope so. An SGT running on ext2 would rock the socks off anything else out there. God I want it
still on kitkat 4.4.4 here!
Hi guys im searching for a way to start a mount-script BEFORE my user apps load up on boot ?
I already got the install-recovery.sh method to work , but its not good , it loads after boot and after other apps have started.
Scriptmanager method is the same , runs after all other apps have started.
the problem i have is that right now im using the app "folder-mount"which is good for some folders like "dcim" BUT it also starts a good time(5 seconds) after the homescreen.
until then another app which i want to write its folder to the sdcard2 has started before it and has already written its new logfile to the internal emulated sdcard, the "foldermount" mounts afterwards and the app can´t see its own log anymore
this is a major suckage , so i search for a way to mount the folders BEFORE all my user apps load up !
please help me thanx !
OHH sorry guys ! i probably made a fault , in fact the install-recovery.sh method runs scripts before apps get started.
i used this method now as i couldn´t get the init.d to work for me.(im a n00b)
boot buddy - run boot scripts from sd card
http://forum.xda-developers.com/showthread.php?t=2378274
to make it compatible with z3c you need to edit the file /data/boot-buddy.sh after the installation
and replace both
/boot_buddy_scripts/
with
/storage/emulated/legacy/boot_buddy_scripts/
or
/storage/sdcard1/boot_buddy_scripts/
then make a new folder boot_buddy_scripts in the location.
puzzle solved, finally lol