Develop Bugs

DamageControl 3.2.2.1 Apps2SD

Hello All,
I have a rooted Evo with DamageControl's 3.2.2.1 rom. I know it has apps2sd built into the OS, yet I cannot seem to get this working at all. Would anyone be kind enough who has this OS and a2sd working to make a quick and dirty guide? Ihave tried partitioning via Rom Manager and then turning it on...tried a few things. Any help is appreciated.

I would like some help with this as well. Have tried all the same steps, just can't seem to figure it out.
Sent from Ye olde Evo

Im sure someone out there knows how to do this!

Got this from another forum:
Did you patition it on the phone? Did you upgrade EXT2 to EXT3? If the answer to either or both of these, that could be the problem.
Type this in order:
cd c:\android-sdk-windows\tools (or wherever you have installed the sdk)
adb remount
adb shell
busybox --install /system/xbin
mkdir /system/sd
a2sd
exit (wait until its done doing its thing, you should see # when its done)
restart your phone after the prompt is done spewing and you're all set.
Click to expand...
Click to collapse
Personally I don't think there's any need for this since the EVO has hugeee internal memory. This was used mostly on older phones.

Thanks I'll try it when I get home

correct, most roms using this will only use app2sd if you have the ext partition on the sdcard, otherwise it defaults to the normal app storage

[Q][S-ON] screwing around with Wildfire S

I posted this here - http://forum.xda-developers.com/showpost.php?p=18647176&postcount=14 - but never got an answer so I'm posting it to its own thread. I would post to the development section but apparently until I clutter up the place with 10 posts I'm considered a drooling idiot.
I was playing around and I noticed that the problem is with s-on I cannot write to /system meaning no superuser etc. So I remembered from way back when I started linux you could mount over a mounted folder. So I made a small file, put ext3 on on it, transferred it to the sdcard and mounted over /system with
mount -t ext3 -o rw,loop /mnt/sdcard/test.dump /system
it worked and then of course I lost all commands (ls, reboot...) in the shell.
Would it be possible to dump /system with "cat /dev/mtd/mtd3 > /mnt/sdcard/system.img", extract it, put it in an ext3 file, mount it as readable over system and just go to town?
Somebody MUST have tried this in the past. Before I go any further can anyone tell me why this wouldn't work and save me a few hours noodling around lol

baconbacon said:
I posted this here - http://forum.xda-developers.com/showpost.php?p=18647176&postcount=14 - but never got an answer so I'm posting it to its own thread. I would post to the development section but apparently until I clutter up the place with 10 posts I'm considered a drooling idiot.
I was playing around and I noticed that the problem is with s-on I cannot write to /system meaning no superuser etc. So I remembered from way back when I started linux you could mount over a mounted folder. So I made a small file, put ext3 on on it, transferred it to the sdcard and mounted over /system with
mount -t ext3 -o rw,loop /mnt/sdcard/test.dump /system
it worked and then of course I lost all commands (ls, reboot...) in the shell.
Would it be possible to dump /system with "cat /dev/mtd/mtd3 > /mnt/sdcard/system.img", extract it, put it in an ext3 file, mount it as readable over system and just go to town?
Somebody MUST have tried this in the past. Before I go any further can anyone tell me why this wouldn't work and save me a few hours noodling around lol
Click to expand...
Click to collapse
S-on itself got nothing to do with rooting. It just means you can't flash unsigned images as much as I know.
That system is mounted as ro is also at rooted phones the standard behaviour, you have to remount it as rw, but without root it won't accomplish I think.
Cat is for text files not for binaries or whole partitions, to extract the image use the dd command.
Do you have an /dev/mtd folder? My partitions are at /dev/block and there is no /dev/mtd present.
Swyped from my HTC Desire S

Tectas said:
S-on itself got nothing to do with rooting. It just means you can't flash unsigned images as much as I know.
That system is mounted as ro is also at rooted phones the standard behaviour, you have to remount it as rw, but without root it won't accomplish I think.
Cat is for text files not for binaries or whole partitions, to extract the image use the dd command.
Do you have an /dev/mtd folder? My partitions are at /dev/block and there is no /dev/mtd present.
Swyped from my HTC Desire S
Click to expand...
Click to collapse
This issue is that when you remount it as rw you cannot write to it. I want to know if I make my own partitions and mount them after boot if that will work, probably slower but work. This is so lojack I doubt it will work, I just want to know if anyone tried it.
Also "Cat is for text files not for binaries or whole partitions" is wrong, it works fine.

baconbacon said:
This issue is that when you remount it as rw you cannot write to it. I want to know if I make my own partitions and mount them after boot if that will work, probably slower but work. This is so lojack I doubt it will work, I just want to know if anyone tried it.
Also "Cat is for text files not for binaries or whole partitions" is wrong, it works fine.
Click to expand...
Click to collapse
Then it's not rw, because rw stands for read write, but like I said without root...
And no I think no one tried it before, because using an xtc-clip is compared to your solution much less work
But if you want to try it, do it and share your experiences, maybe it helps others
That cat works doesn't mean that it's made for it, you can also hunt for birds with a bazooka
Take a look at cat and dd and choose yourself.

Tectas said:
Then it's not rw, because rw stands for read write, but like I said without root...
And no I think no one tried it before, because using an xtc-clip is compared to your solution much less work
But if you want to try it, do it and share your experiences, maybe it helps others
That cat works doesn't mean that it's made for it, you can also hunt for birds with a bazooka
Take a look at cat and dd and choose yourself.
Click to expand...
Click to collapse
is xtc-clip better? yes, not arguing that. is cat is better then dd? no, I said cat works in this instance the same as dd, the results will be the identical.
I didn't ask this question to argue unrelated linux 101. I'm just going to look into this myself. iow screw you guys, im going home...

Dude, I use Linux too though I'm probably not a guru. I think I understand what you're saying... but if I do, aren't you just talking about editing a copy of /system? How would you mount your edited partition at boot?
Time permitting, I could try a few tricks but I'm not willing to risk bricking my phone though. I'd be stranded without it.
Sent from my HTC Wildfire S A510e using XDA App

First don't blame others, because of things I wrote.
I never said it couldn't work, I just wanted to show you that there are better ways to do it, cause cat also tries to interpret the file and not only copies it, what could mess up your image in some cases.
Also be aware that if your using the same data and cache partition with both of your systems, it could be easy bricked, if you change to much at your 2. system and remember that there aren't many ways left to get it working again cause your still s-on.
I think he wants to mount it himself every time after boot.
If he can root his 2. system (but all by hand, I think) he maybe can mount his 1. system as rw and also root it, but the chance that something goes wrong is pretty high, even mounting itself could freeze the device, cause the first system is still in memory.
I'm also not even close to be a Linux guru.
Swyped from my HTC Desire S

Link to bash

Hey-
I've been playing around with the shell, installed bash 3.2 according to this:
forum.xda-developers.com/showthread.php?t=537827
aaaand I was trying to make a link from /system/bin/sh to /sdcard/bash but it didn't take. The reason I want to do that is because I'm experimenting with bash 4.1 and it hasn't quite worked. But when my shell breaks I have to wait for a restore because I can't get write access to the dang /system folder (I guess you need the shell for that).
I know it's not that huge of a deal to have it all in the /system folder once it's how I want it, but I'm going to be playing with other stuff too (bash_profile, etc) and it's a bit of a pain doing the whole trial/error thing. Well, at least with how long it takes. I'm doing trial/error anyway.
So my question is why wouldn't that link work? I know I'd set the link up correctly, tried it several times in case I had a typo. Maybe I just don't understand symlinks like I think I do. I tested also something where I tried to make a link within only the /sdcard folder (always writeable no matter what, thinking that had something to do with it) and just got "operation not permitted". But on my linux box a link between directories is totally cool. Not sure what the difference is. Any help appreciated.

Something else I'm seeing that I really don't understand is that I can create links just not that have to do with my /sdcard partition. I can't even change permissions in /sdcard. From ADB. I run as root:
chmod 0644 filename
and it's as if it accepts the command, but perms stay the same. I did it not as root but it said operation denied. Why if I've got root can't I do some of these operations in /sdcard?

Scooterx3 said:
Hey-
I've been playing around with the shell, installed bash 3.2 according to this:
forum.xda-developers.com/showthread.php?t=537827
aaaand I was trying to make a link from /system/bin/sh to /sdcard/bash but it didn't take. The reason I want to do that is because I'm experimenting with bash 4.1 and it hasn't quite worked. But when my shell breaks I have to wait for a restore because I can't get write access to the dang /system folder (I guess you need the shell for that).
I know it's not that huge of a deal to have it all in the /system folder once it's how I want it, but I'm going to be playing with other stuff too (bash_profile, etc) and it's a bit of a pain doing the whole trial/error thing. Well, at least with how long it takes. I'm doing trial/error anyway.
So my question is why wouldn't that link work? I know I'd set the link up correctly, tried it several times in case I had a typo. Maybe I just don't understand symlinks like I think I do. I tested also something where I tried to make a link within only the /sdcard folder (always writeable no matter what, thinking that had something to do with it) and just got "operation not permitted". But on my linux box a link between directories is totally cool. Not sure what the difference is. Any help appreciated.
Click to expand...
Click to collapse
it's about a fat32 part? then will not work
You should post a log

Thanks, I was poking around somewhere and saw that other people have had problems if it's using a windows format. However, I'm burning my brains out trying to figure out how to see what format it uses and how to then change the format. It's the Samsung Galaxy S, and it's an internal memory card. I wouldn't think I could format it from my computer, it's not removable. Or else I'd have found out already using gparted or something (in fact I tried, said 'unallocated' is all). I *perhaps* could use gparted to format it as ext4 or whatever though, but I'm not sure the effect that'll have. I'd have to do some research.
In any case, I'd love to post a log but I'm not sure what log that is that you're referring to, would you mind telling me how to get that?

Scooterx3 said:
Thanks, I was poking around somewhere and saw that other people have had problems if it's using a windows format. However, I'm burning my brains out trying to figure out how to see what format it uses and how to then change the format. It's the Samsung Galaxy S, and it's an internal memory card. I wouldn't think I could format it from my computer, it's not removable. Or else I'd have found out already using gparted or something (in fact I tried, said 'unallocated' is all). I *perhaps* could use gparted to format it as ext4 or whatever though, but I'm not sure the effect that'll have. I'd have to do some research.
In any case, I'd love to post a log but I'm not sure what log that is that you're referring to, would you mind telling me how to get that?
Click to expand...
Click to collapse
If you work in adb post console output the same if you made that symlink from phone shell
do not forget to switch to root ("su" command )
by this you get part info
Code:
cat /proc/mtd
or system log here
Code:
adb logcat -d > logcat.txt
- it's saved to adb folder
(do not blame me if you already know these things)
also here is an interesting thread
maybe that part is mounted as read-only ?
make things simple as possible use Root Explorer/ES File Explorer (just tap screen to mount r-w)

Thanks, I liked that article you'd mentioned. Though I also tried the suggestion that was provided when I realized that /sdcard/ is really just /mnt/sdcard/ but still no dice.
I checked those logs, didn't see anything relevant. They're attached so if I just don't know what I'm looking for then someone would see it?
The /sdcard isn't read only, I'm able to write files to it.
I'm thinking really that it's just a windows format, but I still haven't an idea how to actually prove that, nor do I know how to format it for linux. Again- it's not removable. Anyway, if there's something that I need to see in the log, it'd be appreciated if you could point it out to me, thanks.

Scooterx3 said:
I'm thinking really that it's just a windows format, but I still haven't an idea how to actually prove that, nor do I know how to format it for linux. Again- it's not removable. Anyway, if there's something that I need to see in the log, it'd be appreciated if you could point it out to me, thanks.
Click to expand...
Click to collapse
-nothing interesting in log file
(a mount/df output is better here)
-also post this problem in Galaxy S I9000 sub-forum
I think your internal sdcard is vfat-type then try to format as ext4-type
here is a good article on this problem

Can't write to sdcard

Okay, I'm freaking out a little bit.
The one app I use more than any other is Doggcatcher. It been my most-used app since my first G1. Well, I recently flashed the AOKP Jelly Bean ROM on my VZW GN, and now it seems that Doggcatcher can no longer save anything to the sdcard directory (either sdcard or storage/sdcard0).
What did I do wrong? I had Jelly Bean working on my phone for a while, but my GN's charge port broke and I received a replacement. I believe I restored a nandroid backup of my previous Jelly Bean install (which was a different ROM), and that's when my problems started. When I installed the AOKP ROM I wiped everything, but I still can't get Doggcatcher to save a single file. It seems other apps have trouble storing anything on the phone too, which is clearly a huge problem.
So what do I do? Please help! I'll offer any information I can.

Seems like permission is bit messed up. Have you don't anything that might've changed the permission?
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

kyokeun1234 said:
Seems like permission is bit messed up. Have you don't anything that might've changed the permission?
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
Certainly nothing on purpose. I just flashed these ROMs in the way I would have thought I was supposed to. I loaded ClockworkMod and flashed the zip file from AOKP.
I really have no idea what I might have done or what to do now. I'm completely fine with wiping my phone, I just need to know how to start over!

If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *

danger-rat said:
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
My friend, you are a genius. THANK YOU SO DAMN MUCH!! Seriously, you rock like crazy.
I followed your instructions (I had to learn how to get into the adb shell but that wasn't too tough), restarted the phone, and immediately tried downloading a podcast episode. I then pumped my fist in the air when I saw it successfully downloading.
Again, thank you so much. You rock.

Just passing on info from others...

danger-rat said:
Just passing on info from others...
Click to expand...
Click to collapse
Still, you helped, solved my problem, and fixed a problem for me in a week that's been filled with nothing BUT problems in other parts of my life, so I can't tell you how much I appreciate that.

FYI, I also posted your answer, along with a link to this thread, on the Doggcatcher forums where I also asked for help on this issue, when I thought it was just a problem with that app. I quoted your answer and gave you the credit, in case there's ever a future breakdown in the link I used

danger-rat said:
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
thanks, you saved me too

johnz said:
thanks, you saved me too
Click to expand...
Click to collapse
Dude, this thread was dead, all you needed to do was press the thanks button, no need to revive this.
Sent from my i9250

danger-rat said:
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
thanks so much for this!
I was struggeling with this problem, because I couldn't create backups anymore.
before I executed your command I had a look at the current permissions for the files.. some folders were owned by root:root instead of media_rw:media_rw. No wonder apps couldn't create files in those folders..
Too bad this was only shown in the shell when in recovery. While the phone was in Android the permissions showed correctly as root:sdcard_rw .. that's why it never occured to me this was a real problem.

[Q] Rooted phone, now what?

I finished the process of rooting my phone yesterday and now would like to dive into editing a custom theme. On my journey to search how just to do that I've hit a road block.
Anyway, I don't know where to look to find the .apk's or the stylesheets. I tried remounting the /system partition with "mount -o remount,rw -t extb4 /dev/block/mmcblk0p25/system" in Android Terminal Emulator, but all that came of it was the parameters for the mount command. Afterwards I tried the Mount /system (rw / ro) app to no avail. So yes, wall reached and I'm not sure where to go.
Also, I'm pretty sure I would find the /system folder in the update.rar folder when I connect my phone to my PC via USB, but correct me if I'm wrong
Oh btw its United States Virgin Mobile so I believe that is CDMA.

TopHatMan said:
I finished the process of rooting my phone yesterday and now would like to dive into editing a custom theme. On my journey to search how just to do that I've hit a road block.
Anyway, I don't know where to look to find the .apk's or the stylesheets. I tried remounting the /system partition with "mount -o remount,rw -t extb4 /dev/block/mmcblk0p25/system" in Android Terminal Emulator, but all that came of it was the parameters for the mount command. Afterwards I tried the Mount /system (rw / ro) app to no avail. So yes, wall reached and I'm not sure where to go.
Also, I'm pretty sure I would find the /system folder in the update.rar folder when I connect my phone to my PC via USB, but correct me if I'm wrong
Oh btw its United States Virgin Mobile so I believe that is CDMA.
Click to expand...
Click to collapse
Can you specify exactly what you are trying to do? Title and body is misleading.

Wtf are you talking about?
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round

now just flash roms and enjoy !!
now just flash roms and enjoy !!

That's the problem, I dont know what to do now. Sorry the title was misleading, but what I really want to do is figure out how to make my own android themes, like this person did > imgur DOT com/YLpFi.png"
How would I go about switching images in my phone and editing style sheets?
Thank you
PS Sorry I can't hyperlink yet :/

TopHatMan said:
That's the problem, I dont know what to do now. Sorry the title was misleading, but what I really want to do is figure out how to make my own android themes, like this person did > imgur DOT com/YLpFi.png"
How would I go about switching images in my phone and editing style sheets?
Thank you
PS Sorry I can't hyperlink yet :/
Click to expand...
Click to collapse
Well, start reading threads... :silly:
Like that one: http://forum.xda-developers.com/showthread.php?t=2136407
There are many more around in XDA, just go through all...

Thank you all for replying

After you root it, you plan the new baby roots in another pot, to grow a new Android.
But honestly, WTF are you rooting, and don't know why.
Flash a custom ROM, so you can enjoy free Wi-Fi tethering, and many other nice features that would take all day to list.
Gratz on successfully rooting your phone though!

R: [Q] Rooted phone, now what?
I suggest you try to make some cool Widgets with uccw, you can find it in google play. Also take a look in themes and apps section at "show us your home screen", there's some very cool stuff
Sent from my One V using xda app-developers app

mr_nooby said:
I suggest you try to make some cool Widgets with uccw, you can find it in google play. Also take a look in themes and apps section at "show us your home screen", there's some very cool stuff
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Thats awesome. I haven't seen that before. Sweet app thx bro