Develop Bugs

[GUIDE] Setting Up and Activating SWAP Partition Without Breaking USB Mass Storage

Okay, many of you complain about USB MASS STORAGE not working with swap enabled. So heres a guide, using CWM (latest version) to set it up with working USB.
NEEDED:
MicroSD (i use class 4 sandisk 8gb)
Root+Busybox
CWM Recovery* (see post 2 for reasons of the *)
Terminal Emulator/ADB
Download this file http://dl.dropbox.com/u/1169731/swap_enabler.sh and place it IN THE ROOT OF YOUR SD!!!
Precautionary:BACKUP EVERYTHING ON MICRO SD CARD.
Steps:
Making the partition
Make sure you have everything backed up, as this WILL wipe your SD.
Boot into clockworkmod recovery.
Go to Advanced->Partition SD Card->EXT and Swap. I chose 128mb for EXT and 256 for SWAP.
Activating Through ADB
Make sure you downloaded that file earlier.
Type this into the CMD:
Code:
adb shell
chmod 755 /mnt/sdcard/swap_enabler.sh
sh /mnt/sdcard/swap_enabler.sh
And reboot
When your phone has rebooted, go back into ADB, and type:
Code:
adb shell
free
and if you didnt not get 0's next to SWAP, it worked.
Activating through Terminal Emulator
Load up Terminal Emulator
Type in this:
Code:
su
chmod 755 /mnt/sdcard/swap_enabler.sh
sh /mnt/sdcard/swap_enabler.sh
reboot. when your phones has booted back up, load terminal emulator once more, and type:
Code:
su
free
and if there isnt a bunch of 0's next to SWAP, it worked
And thats that!
Enjoy
TO DISABLE THROUGH ADB:
adb shell (skip if you're already in adb shell)
sh /mnt/sdcard/swap_enabler.sh disable
Click to expand...
Click to collapse
TO DISABLE THROUGH TERMINAL EMUALTOR
su
sh /mnt/sdcard/swap_enabler.sh disable
Click to expand...
Click to collapse
NEW QUICK EASY WAY (HIT AND MISS)
1) download script manager from the market
2) run swap_enabler.sh with script manager
3) reboot
SPECIAL THANKS TO: Nv for the script, and cimer for the original guide.
also, thanks to cjward for reminding me to put in the thanks ;D

* this guide is for CWM recovery, as the steps for 4EXT may be different. Also, when i tried to do it with 4EXT, it never activated the swap partition correctly.

Man, I've been trying to get this right. Think I messed up because I did not restart after running the script, so when I did the free command I got them zeros.

enserio said:
Man, I've been trying to get this right. Think I messed up because I did not restart after running the script, so when I did the free command I got them zeros.
Click to expand...
Click to collapse
what SD card you have? also, i have noticed it does not work on some roms, but most it does.

I used this method to set swap up to use with virtuous 3.5 and work great for me on my first try. It definately helps out.
Sent from my HTC Vision using xda premium

xT4Z1N4TRx said:
what SD card you have? also, i have noticed it does not work on some roms, but most it does.
Click to expand...
Click to collapse
The 8GB one that came standard with the G2 in the US, Dec 2010. If you need me to take it out and confirm what kind, I will, because this something I want to learn how to do. Also, I tried it with the ILWT Rom. I was trying to get to to work because I wanted to flash that Virtuous 3.5
PS - Anyone have a better method for backing up the SD card besides creating a folder on the desktop and dragging everything in there?

when i type su in terminal emulator I get
"[1] + Stopped (signal)"

I'm now getting a +2 error.
This is mildly frustrating because it seems so easy. I've learned several other processes to do to my phone, and THIS is the one that I get hung up on?
Latest debacle:
I wipe using G2+Superwipe. Make partitions of 128 and 256. Sdcard goes completely blank, so I have to mount it in recovery, and load up a nandroid. I figure, its still all good, go through with it. So I run the commands in Terminal Emulator and get the +2 error. damn damn damn

enserio said:
I'm now getting a +2 error.
This is mildly frustrating because it seems so easy. I've learned several other processes to do to my phone, and THIS is the one that I get hung up on?
Latest debacle:
I wipe using G2+Superwipe. Make partitions of 128 and 256. Sdcard goes completely blank, so I have to mount it in recovery, and load up a nandroid. I figure, its still all good, go through with it. So I run the commands in Terminal Emulator and get the +2 error. damn damn damn
Click to expand...
Click to collapse
Have you tried with ADB?
Sent from my Desire Z running @ 2GHZ

now on terminal emu i get: arith: syntax error: "65 on +2"
I'd try adb but i dont know much about adb

Hi everybody
I was asking myself, before doing it, do I really need it ?
I mean, I'm on Cyanogen Nightly and I've seen it's needed on virtuous (awesome) roms. But on CM, will it change something to activate swap ?
Thanks in advance

xT4Z1N4TRx said:
Have you tried with ADB?
Sent from my Desire Z running @ 2GHZ
Click to expand...
Click to collapse
well, new SDK is giving me problems setting up on my mac. Now you have to use SDK manager, which says to run 'android' file, and when I do it gives me an error just as its about to finish setting up.
Ugh, I want this to happen.
EDIT: got ADB fixed. gonna gee it a go this way.

KeitaroSenpai said:
Hi everybody
I was asking myself, before doing it, do I really need it ?
I mean, I'm on Cyanogen Nightly and I've seen it's needed on virtuous (awesome) roms. But on CM, will it change something to activate swap ?
Thanks in advance
Click to expand...
Click to collapse
This I would also like to know! Thx!

While I can't be 100%, I would say that it wouldn't help you much at all, on any CM based ROMs. Just the ones that are RAM intensive (i.e., sense roms). I know that I only want it to run the Virtuous 3.5 ROM.

Can anyone tell me is there a difference between doing it this way, or just using the app "swapper for root" from the app market..?
Thanks

Thought I would pop in. Doing it via terminal does not normally work you need to do it via ADB. If you're unfamiliar with ADB please go to here: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ and learn about it. It can be such a useful tool. You do not need swap for CM7,MIUI, or Sense 2.1. It can be needed for Sense 3.0 or Sense 3.5 because Sense is such a memory hog at those version levels.

fredcorp6 said:
Can anyone tell me is there a difference between doing it this way, or just using the app "swapper for root" from the app market..?
Thanks
Click to expand...
Click to collapse
Yes, using this way restricts it to one partition, whereas using swapper allows it to use the FAT partition. This means, with this only your swap part will get corrupted over time, whereas with swapper your FAT will, losing your data.
Sent from my Desire Z running @ 2GHZ

Ah ok I see.. cheers

Anyone able to overcome the +2 error? Using Umaro kernal on EliteMod CM7.
Code:
# sh /mnt/sdcard/swap_enabler.sh
sh /mnt/sdcard/swap_enabler.sh
* Some tests.
/mnt/sdcard/swap_enabler.sh: arith: syntax error: "65 on +2"
EDIT:
Probably something not being compatible either busybox or CM7 but I got it to work by doing the following after looking at the code in the swap_enabler.sh file.
Since it was "65 on + 2" I figured that the cut commands weren't being executed properly somewhere and that it should have been 65 + 2 = 67..... =)
in shell i typed swapon /dev/block/vold/179:67
and it worked. Of course I had to manually make an entry in init.d and test it =)....
Maybe this can help OP edit the code.

Nshih422 said:
Anyone able to overcome the +2 error? Using Umaro kernal on EliteMod CM7.
Code:
# sh /mnt/sdcard/swap_enabler.sh
sh /mnt/sdcard/swap_enabler.sh
* Some tests.
/mnt/sdcard/swap_enabler.sh: arith: syntax error: "65 on +2"
EDIT:
Probably something not being compatible either busybox or CM7 but I got it to work by doing the following after looking at the code in the swap_enabler.sh file.
Since it was "65 on + 2" I figured that the cut commands weren't being executed properly somewhere and that it should have been 65 + 2 = 67..... =)
in shell i typed swapon /dev/block/vold/179:67
and it worked. Of course I had to manually make an entry in init.d and test it =)....
Maybe this can help OP edit the code.
Click to expand...
Click to collapse
Why do you want to use swap on cm7. There are zero benefits. But there are disadvantages, it could affect battery life, performance and wear your sdcard out faster
Sent from my HTC Vision using Tapatalk

[FIX] Permissions Work Around for ICS

Script to flash via CWM to fix fix perms has been done by minotauri (sorry if miss spelled will fix when on a computer) he deserves credit for the edify:
To Run Fix Perms While in Recovery Flash this file each and every time you need it run [for now]:
http://goo.gl/hrL7E
The Next Script is one you can flash via CWM and it will replace the file ROM Manager uses so this will remain between restarts and you can use it via ROM Manager or Script Manager anytime you want!:
Thank Minotauri again for another beautiful Edify!
http://goo.gl/qPpC3
Flash via CWM and it well work for that flash just flash anytime you need to run it via recovery until I see about permanently copying it over existing script or still can run manually with this guide if you choose [scroll down below the additional update on how to fix the script to run using ROM Manager while in OS!].
I posted this in a couple ROM threads and was asked to throw it out here as folks from different ROMs are all affected. I can only speak for TMobile Galaxy S2 as that is what I own, drive and work on...
I will be cleaning up the post a bit when I get time just want it posted so others can use the information add it really seems to help clean up small issues (even some report fixing multiple FCs after running fix perms this way!)
NEWEST UPDATE 2012.04.19
OK FIX FOR RUNNING FIX PERMS INSIDE OS VIA ROM MANAGER
If you adjust first line in script to #!/system/xbin/sh viola ROM Manager does not freeze [finally]
I did this with Ghost Commander [don't forget settings> check auto root] and long press fix_permissions and choose edit tapping it will have GC try to execute it.
I also moved down to set variables piece and placed 1s instead of 0s next to mount system, mount data, and remove (as in REMOVE stale data ) [should be all caps in /data/data/com.koushidutta.rommanger/files/fix_permissions
I am still working on finding a way of making those changes permanent in /sbin under recovery boots
Fix Permissions Work Around ICS
Run Fix Permissions via ADB Shell with Phone in Recovery
I have taken the time to document what should be a complete guide to running fix permissions while the phone is in the Recovery menu using adb.
I am posting the quick steps right after this, but if you scroll below that this is an extended step-by-step guide.
Code:
Running Fix Permissions
On Phone: go in to Mounts and Storage Menu from Main Menu and choose to mount /data and /system
On Computer: type adb shell
This should give you a ~# prompt
Now type "sh /sbin/fix_permissions -l -r" [without quotes]
and now you should see a bunch of text scroll by and then it will say fix permissions completed blah when done.
that's it type exit and hit enter about 3x [one will change ~# to ~$ then it will drop back to C:\blah and then one more time will close that window as well
Supplies [Phone, USB Cable and Android SDK (http://developer.android.com/sdk/index.html)
Follow the link to install Android SDK [they have directions on site]
first time installing adb? [Skip otherwise]
To Add ADB to your computers path [to run it from any directory]
Windows:
Open Command Prompt [Click Start, Click Run, Type in cmd and hit Enter [XP]]
Open Command Prompt [Click Start, type cmd in whitebox and hit Enter [Vista and 7]]
type set PATH=%PATH%;C:\android-sdk\platform-tools [or wherever you put android sdk just add platform-tools to the end [it is a hidden folder]
Linux [OSX should be same]:
PATH=$PATH:/home/user/android-sdk/platform-tools [or adjust for where you saved it]
export PATH
Now That You Have ADB and path set, time for good stuff
Opening a Command Processor
Open a Command Prompt [Windows] or Terminal [Linux or OSX]
Windows: Click Start, Click Run, Type cmd and hit enter [XP]
Click Start, type in to Whitebox cmd and hit Enter [Vista and 7]
Linux: Hold alt and hit F2 on keyboard [should see a run box now]
Type in xfce4-terminal and hit Enter [or substitute your terminal command this is xubuntus]
Once a Black and White Screen Opens...
Gaining Elevated [Admin or Root Privileges]
Ok, some further testing shows me you should have root or admin access to command processor before running ADB.
In Windows
Type The Following in to the command prompt window already open...
runas /user:%computername%\administrator cmd
hit enter when done
[yes just like that including %computername% windows will fill it in with proper info copy/paste if needed right clicking in command window should paste text for you [if not right click on the icon in left hand corner of title bar choose properties and place checks in the quick edit and insert mode boxes under Options tab]
now it will ask for a password if you have not set one you need to go to control panel users and set a password on admin account before this will work
Once you enter the password and hit enter a second command window will open and will have Administrator in the title
Now You can continue on
In Linux
With Terminal window open type:
gksudo xfce4-terminal& [sub your terminal command if not using xubuntu]
once you hit enter it may take a second but you will get a password prompt enter in your password and a new terminal will open and it will have [email protected] in the title
Now you can continue on...
Checking USB Connection
type in adb devices and hit enter
[if you get a command not found you will have to use cd to move to directory with adb [ie cd c:\android-sdk\platform-tools]
If it comes back with ?????? as serial number it is not connecting correctly follow the next steps otherwise skip the next bit if you didnt get all ?
I get ?????, what gives?
This seems due to not running command prompt or terminal as administrator or root user [Windows / Linux Respectively]
You will need to do the following in order
Disconnect USB from phone
On Phone: In Advanced menu choose restart recovery
On Computer: type in adb kill-server and hit enter
Reconnect USB cable
Be Sure To Follow Section above labeled: Gaining Elevated [Admin or Root Privileges] and then continue on
On Computer: type adb devices and you should see a mix of letters and numbers
and that means we are good to go on
Running Fix Permissions
On Phone: go in to Mounts and Storage Menu from Main Menu and choose to mount /data and /system
On Computer: type adb shell
This should give you a ~# prompt
Now type "sh /sbin/fix_permissions -l -r" [without quotes]
and now you should see a bunch of text scroll by and then it will say fix permissions completed blah when done.
that's it type exit and hit enter about 3x [one will change ~# to ~$ then it will drop back to C:\blah and then one more time will close that window as well
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]

Known Issues:
-------
Issue: My computer does not connect when I use adb shell [or I get ????? when I use adb devices]
Resolution:
I have found that i have to connect my phone 2x to computer to get it to work correctly most of the time, do the following
Disconnect USB from phone
In advanced menu on phone choose Restart Recovery
on computer: adb kill-server
Reconnect USB cable
on computer: adb devices
and you should now see a mix of numbers and letters and not ????? and now adb shell should connect
Issue when I try sh fix_permissions it says it can not find the file
Resolution: This is normally caused when you have not mounted /system [via phone]
or you did not use sh /sbin/fix_permissions [or be sure to do cd /sbin before sh fix_permissions
Issue: I get UID Read-only variable error and fix permissions does not run
Resolution: This is normally caused by either not mounting /system [via phone]
or not using sh fix_permissions.
Issue: Some of my apps are listed as /data/blah and it says it can not find the file
Resolution: This is normally caused by not mounting /data [via phone]
Issue: CWM will not mount /system or /data saying it can not find or read them
Resolution: I have found CWM does not like to load mounts once they are encrypted. If you have encrypted your device /system and /data are affected, try unencrypting your phone and trying again.
(this is a good thing it shows third parties tools trying to get around booting OS to read data will not be able to get at the information in your phone)
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]

SEE This post for the current script
http://forum.xda-developers.com/showpost.php?p=25023284&postcount=22
Sent from my SAMSUNG-SGH-T989 using xda premium

Well judging by the title that you have there referred to running the script via recovery adb to begin with.
A lot of users don't realize if fix perms says complete in 2 secs it had a problem so I didn't know of that thread, but hope this will be a catch all for fix perms and not just for those who already tried via recovery and adb shell and got that specific error.
Thanks for looking out though
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]

jangst123 said:
This is already and has been in the Q & A section.... Not development, but I wish the developers would look at it and figure out why we have issue on ICS
http://forum.xda-developers.com/showthread.php?t=1595806[Q] Problem with Fix Permissions (line 64: UID readonly variable) [WORK AROUND FOUND]
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I think posting this in Dev section is perfect sense. Also, thanks for the fix. This has stumped me for a while trying to figure out what to do.

When trying this, I get the message:
cat: can't open '/data/system/packages.xml': No such file or directory.
It says that twice and concludes with fix permissions ended at yada yada. I followed every command and instruction to the letter, what could be the issue?

Hey I got idea,, lets make another thread in the general section and Themes,,
Sorry don't think this belongs here, IMO
MOD,, please delete 1 of the threads,, or merge them or something,, no point in having 2
Not that I'm not happy a work around has been found!
Hopefully now the developers will figure out the source of the problem

would it be possible to bake this into a rom, or to create a CWMR zip file to make the needed changes?

Dougshell said:
would it be possible to bake this into a rom, or to create a CWMR zip file to make the needed changes?
Click to expand...
Click to collapse
+1 I'm completely stumped!

I can't get adb to even reconize the damn phone im on ravers remix to ics

peppersu812 said:
I can't get adb to even reconize the damn phone im on ravers remix to ics
Click to expand...
Click to collapse
turn on debugging

RaverX3X said:
turn on debugging
Click to expand...
Click to collapse
Raverx3x any idea why we are having this problem!?
Should we be running a different fix_permissions on ICS?
Also see..
http://forum.xda-developers.com/showthread.php?t=1595806
being that we seem to be determined to have this discussion in 2 different threads

l-levit said:
Hey I got idea,, lets make another thread in the general section and Themes,,
Sorry don't think this belongs here, IMO
MOD,, please delete 1 of the threads,, or merge them or something,, no point in having 2
Not that I'm not happy a work around has been found!
Hopefully now the developers will figure out the source of the problem
Click to expand...
Click to collapse
Or you could have devs talk here and keep users in QA so this doesn't get flooded with chatter.
Our should we delete all those ROM threads in Dev that exist in QA as well?
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]

OGWisdom said:
When trying this, I get the message:
cat: can't open '/data/system/packages.xml': No such file or directory.
It says that twice and concludes with fix permissions ended at yada yada. I followed every command and instruction to the letter, what could be the issue?
Click to expand...
Click to collapse
Did you forget to mount /data in mounts and storage (on phone) before running?
Did you encrypt your device? I have CWM fail to load mounts after encryption
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]

Oh and other thread just ganked my fix which is cool but I did this on my own not in response to anything so seeing as how I had to put in 2 hours of actual research, scratching my head, trying many different ways and seeing as how this is more of a process then simply loading a script I wanted to maintain it here until I can edit script or another Dev does making it cleaner and easier to manage and thus ready for more casual users found in QA threads.
Sheesh, sorry I figured this out maybe next time I won't pass on the info for fear of debating where it should be posted rather than the content and how to make it better going forward.
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]

u mad bro
Interesting,, the other thread was started 12th April 2012, 10:35 AM,
plus it looks like he quoted your original post from BlackEdition, and gave you credit,, before you even chose to make another thread in a section that is normally reserved for developers and their ROM's, scripts, or mods. All while u r over here bashing the other thread! Thanks for helping, but grow up and follow the rules
anyway make sure you are setting the path to adb
see http://forum.xda-developers.com/showthread.php?t=1161776 for more information

peppersu812 said:
I can't get adb to even reconize the damn phone im on ravers remix to ics
Click to expand...
Click to collapse
I have instructions on that issue on post.
Did you run adb devices and get ????? unknown device?
I had to run terminal as administrator, then I issued adb kill-server and reconnected phone and then did adb devices again and then it will say starting adb blah blah blah and then I got 6f7y88 [made up it should be a series of numbers and letters and no ?]
make sure adb devices gives you a valid response and not ????? I have found I almost always have to connect phone twice and at least do the above [with regular terminal I only used admin on first run but there in case it does make a difference].
So everytime I conect [or just about] I have to connect the phone
run adb devices get ????? and then
Disconnect USB
on phone in advanced menu choose restart recovery
on computer adb kill-server
Reconnect USB
Run adb devices and get a good serial number listed
I have to do actual work for a couple hours and then will be cleaning up main post on top and adding that bit in a place it get noticed more easily bear with me as I make my boss happy [he is wondering why things aren't getting done round here now ut-oh LoL] then I will clean up the information.

l-levit said:
u mad bro
Interesting,, the other thread was started 12th April 2012, 10:35 AM,
plus it looks like he quoted your original post from BlackEdition, and gave you credit,, before you even chose to make another thread in a section that is normally reserved for developers and their ROM's, scripts, or mods. All while u r over here bashing the other thread! Thanks for helping, but grow up and follow the rules
anyway make sure you are setting the path to adb
see http://forum.xda-developers.com/showthread.php?t=1161776 for more information
Click to expand...
Click to collapse
Um, actually I just noted they used my solution and said it was cool to do so, it appears you have an axe to grind with me and are just nit picking anything I say. I am sorry if yoyu do not feel my work is not to the same level as other folks, but since I put in work and this is more of a manual fix you have to work at rather than an easy to use script [yet], I did not want to post it in QA and all until I have something better for general release.
Also, I am not mad, just wondering why you would rather start silly arguments over placement of usable useful information rather than helping to make said information better and more stable for release to others.
Are you mad I figured this out and posted it before you or something as I have never talked with you and given you no reason to troll my threads?
When I do have a stable script [well at least semi stable for release to dev then more stable for QA]. The way I view QA is for general users questions and answers and since I was going to work on DEVELOPING a script that does work I was holding off on a QA thread, once I do get a script together I will be releasing it. In the meantime I was hoping to have more advanced users and devs dissect my process here and give me feedback towards a full script.
ALSO, by using sh /sbin/fix_permission OR doing cd /sbin and then fix_permissions you negate any need to do any path variable adjustments BUT if you rather then here is how...
when in adb shell before anything
PATH=$PATH:/sbin
export PATH
will then make it so you can just fix_permissions regardless of where you are in directory tree [but so will sh /sbin/fix_permissions so either way is up to you]
or if you are reffereing to adb on the computer
in Windows with command prompt open
set path=%path%;C:\android-sdk\platform-tools [or adjust for where you saved adb]
so if setting a batch program you could use the following to copy/paste [just adjust directories if you saved files differently]
The following is off the cuff until I begin writing the full script and automate things but it is a very basic start
Code:
@Echo Off
Set Path=%PATH%;C:\android-sdk\platform-tools
adb devices
Echo If you see ????? then restart recovery and reconnect the phone
Echo and run adb kill-server and re-run this batch script
pause
Echo when you hit any key this will start adb and put you in the shell you
Echo Will have to run fix_permissions -l -r manually
Echo Be sure to mount /storage /data via phone first
adb shell
or in Linux [OSX should be similiar if not the same]:
from terminal
PATH=$PATH:/home/user/android-sdk/platform-tools [or adjust for where you saved adb
export PATH

No it just bothers me when people ignore the rules and the Developers! Raver even told you were it belonged, and you chose to ignore Raver and the rules!
The fix will be to modify recovery for use with ICS on our devices or a modified fix-permishions script baked into the ROMS

RaverX3X said:
turn on debugging
Click to expand...
Click to collapse
I did bro just having trouble getting the cmd to recognize adb I have it downloaded I changed it still nothing don't know what the hell is wrong with it but IM fixing to improve on my golf swing on this damn vista desk top !
Sent from my SAMSUNG-SGH-T989 using xda premium

[REQ] NOTEorious Prime RC1.5 please post your 'ps' output (Noobsafe :) step-by-step)

I do not have dev permissions, so I can't post to the following thread:
[ROM] NOTEorious Prime RC1.5 JB 4.1.2 AOSP/TW Mash-up N7105 base 12/7/21012
http://forum.xda-developers.com/showthread.php?t=1984546
I'm trying to troubleshoot a phone having problems booting. I've identified potential problem processes, but I think it may help if I can get the ps output.
Since this isn't the DEV board, I've included instructions so hopefully anyone (ahem: noobs) running the NOTEorious RC1.5 ROM should be able to get me this info.
There are two options, 1a. from the phone using a terminal app or 1b. adb if you have that installed.
1a. From phone
Reboot phone in normal mode
Open or install terminal app from Google Play
Type each line (or copy-paste), then press enter/return:
uname -a >> /sdcard/Download/ps.txt
ps >> /sdcard/Download/ps.txt
(NOOBs: if you need help identifying the spaces...)
uname[space]-a[space]>>[space]/sdcard/Download/ps.txt
ps[space]>>[space]/sdcard/Download/ps.txt
This saves the file to "ps.txt" to the internal SD card in the Downloads folder
1b. From PC
Note: You must have android-sdk installed and connect your phone to the computer via USB
Reboot phone
Wait until @ lockscreen
Attach phone to the PC w/ adb installed via USB
[On PC, open a terminal prompt]
WinKey+R -> type "cmd" -> Enter or OK
[On PC, at terminal prompt, copy paste the following lines one at a time]
C:\android-sdk\platform-tools\adb.exe shell uname -a >> C:\ps.txt
C:\android-sdk\platform-tools\adb.exe shell ps >> C:\ps.txt
(NOOBs: if you need help identifying the spaces...)
C:\android-sdk\platform-tools\adb.exe[space]shell[space]uname[spac]-a[space]>>[space]C:\ps.txt
C:\android-sdk\platform-tools\adb.exe[space]shell[space]ps[space]>>[space]C:\ps.txt
ps.txt is saved in your root C:\ directory
2.
Attach the "ps.txt" file here
OR
Post text of "ps.txt" to a site like http://pastebin.com/ & post temporary URL provided by that site here
3.
Please also let me know roughly how many apps you've installed since you flashed it
No apps 0
Few apps 1-5
Some apps 6-10
Lot of apps 11-15
More 16+
Thanks for anyone who can help me!

anotherguy19 said:
I do not have dev permissions, so I can't post to the following thread:
[ROM] NOTEorious Prime RC1.5 JB 4.1.2 AOSP/TW Mash-up N7105 base 12/7/21012
http://forum.xda-developers.com/showthread.php?t=1984546
I'm trying to troubleshoot a phone having problems booting. I've identified potential problem processes, but I think it may help if I can get the ps output.
Since this isn't the DEV board, I've included instructions so hopefully anyone (ahem: noobs) running the NOTEorious RC1.5 ROM should be able to get me this info.
There are two options, 1a. from the phone using a terminal app or 1b. adb if you have that installed.
1a. From phone
Reboot phone in normal mode
Open or install terminal app from Google Play
Type each line (or copy-paste), then press enter/return:
uname -a >> /sdcard/Download/ps.txt
ps >> /sdcard/Download/ps.txt
(NOOBs: if you need help identifying the spaces...)
uname[space]-a[space]>>[space]/sdcard/Download/ps.txt
ps[space]>>[space]/sdcard/Download/ps.txt
This saves the file to "ps.txt" to the internal SD card in the Downloads folder
1b. From PC
Note: You must have android-sdk installed and connect your phone to the computer via USB
Reboot phone
Wait until @ lockscreen
Attach phone to the PC w/ adb installed via USB
[On PC, open a terminal prompt]
WinKey+R -> type "cmd" -> Enter or OK
[On PC, at terminal prompt, copy paste the following lines one at a time]
C:\android-sdk\platform-tools\adb.exe shell uname -a >> C:\ps.txt
C:\android-sdk\platform-tools\adb.exe shell ps >> C:\ps.txt
(NOOBs: if you need help identifying the spaces...)
C:\android-sdk\platform-tools\adb.exe[space]shell[space]uname[spac]-a[space]>>[space]C:\ps.txt
C:\android-sdk\platform-tools\adb.exe[space]shell[space]ps[space]>>[space]C:\ps.txt
ps.txt is saved in your root C:\ directory
2.
Attach the "ps.txt" file here
OR
Post text of "ps.txt" to a site like http://pastebin.com/ & post temporary URL provided by that site here
3.
Please also let me know roughly how many apps you've installed since you flashed it
No apps 0
Few apps 1-5
Some apps 6-10
Lot of apps 11-15
More 16+
Thanks for anyone who can help me!
Click to expand...
Click to collapse
What is the problem your having exactly?
Sent from my Nexus 7 using xda premium

cjsspape said:
What is the problem your having exactly?
Click to expand...
Click to collapse
Fails to reach lockscreen.
What is perceived on the display:
1. Normal boot
2. proceeds to "Samsung" bootlogo,
3. advances to "Boot animation"
4. Step 3 continually loops ad finitum [edit: for clarification I should say, boot animation plays continuously with no obvious break, that is, it doesn't go back to Samsung bootlogo screen]
I can actually adb the device so I can debug.
This means I can see what processes are running.
mediaserver and netd run and kill themselves continually
debuggered follows
By looking at the process list, of a working ROM flash, I could see if any process fails and does not restart causing
Previously I was trying to debug via CWM w/ adb but couldn't get dmesg output. I'm looking at various logs created now to see what when wrong and where. I'm seeing A LOT of things going wrong, but it must be stemming from a root cause. Because of that, I figured mediaserver and netd were initially responsible, I could have been wrong though.

How about a logcat? Anyone?

anotherguy19 said:
Fails to reach lockscreen.
What is perceived on the display:
1. Normal boot
2. proceeds to "Samsung" bootlogo,
3. advances to "Boot animation"
4. Step 3 continually loops ad finitum [edit: for clarification I should say, boot animation plays continuously with no obvious break, that is, it doesn't go back to Samsung bootlogo screen]
I can actually adb the device so I can debug.
This means I can see what processes are running.
mediaserver and netd run and kill themselves continually
debuggered follows
By looking at the process list, of a working ROM flash, I could see if any process fails and does not restart causing
Previously I was trying to debug via CWM w/ adb but couldn't get dmesg output. I'm looking at various logs created now to see what when wrong and where. I'm seeing A LOT of things going wrong, but it must be stemming from a root cause. Because of that, I figured mediaserver and netd were initially responsible, I could have been wrong though.
Click to expand...
Click to collapse
Hmm have you tried to full wipe your system and reflash the ROM?
Sent from my Nexus 7 using xda premium

cjsspape said:
Hmm have you tried to full wipe your system and reflash the ROM?
Click to expand...
Click to collapse
But that would solve all my problems without learning anything ... what fun is that?

anotherguy19 said:
But that would solve all my problems without learning anything ... what fun is that?
Click to expand...
Click to collapse
Haha I gotcha. Just gotta make sure ya know how to ultimately fix the problem. I'd help ya out with the logs and stuff but I don't have the device anymore.
Sent from my Nexus 7 using xda premium

[GUIDE]Swap Internal Memory to External & Vice Versa

The Xperia M sure packs a lot in such a small device, but then, does it pack enough internal memory to install a huge number of applications? It does not. With just a little over 2 GB, it is very cumbersome to find that you cannot download data for large games. This guide aims to resolve that issue. Although it is not very user friendly at the moment (it requires you to type a few lines on the phone), I will get back to creating a script that you can execute this weekend.
Note: This guide requires you to be rooted. For rooting, you can follow this guide.
Step 1: Setting up stuff
Find and download a suitable file explorer that allows you to modify and browse system files. I recommend Root Explorer. (Optional)
Download and install Terminal Explorer from the Google Play Store.
Download and install Script Manager from the Google Play Store. (Optional)
Step 2: Walking the path
Open Terminal Emulator and type in
Code:
su
Your root manager should request you for permission. Grant the app superuser permission.
Type in
Code:
vold
Press enter
Type in
Code:
mount -t vfat -o umask:0000,uid=1000,gid=1023 /dev/block/vold/179:33 /storage/sdcard0
Press enter.
Type in
Code:
mount -o bind /data/media /storage/sdcard1
Press enter.
Click to expand...
Click to collapse
And, that's it! You're almost done. Go to Settings > Storage and check the internal and external storage to see that they have been mounted. You can now install huge games and enjoy them on your M. This is a temporary workaround until this weekend as I will write a script to automate this once my exams are over. If anyone else wants to do it, they're welcome to!
Note: You will have to type this again every time you reboot the device. A bit cumbersome, but I hope you can hold on till the weekend.
Credits:
 @darz
 @raw235
 @mattiadj
 @Ace King 34

not work in FW XM Dual
how to swap internal and external in FW XMD ?

@gadgetroid , will it work in Xperia M Dual 4.2 ?

It Worked!!!
gadgetroid said:
The Xperia M sure packs a lot in such a small device, but then, does it pack enough internal memory to install a huge number of applications? It does not. With just a little over 2 GB, it is very cumbersome to find that you cannot download data for large games. This guide aims to resolve that issue. Although it is not very user friendly at the moment (it requires you to type a few lines on the phone), I will get back to creating a script that you can execute this weekend.
Note: This guide requires you to be rooted. For rooting, you can follow this guide.
And, that's it! You're almost done. Go to Settings > Storage and check the internal and external storage to see that they have been mounted. You can now install huge games and enjoy them on your M. This is a temporary workaround until this weekend as I will write a script to automate this once my exams are over. If anyone else wants to do it, they're welcome to!
Note: You will have to type this again every time you reboot the device. A bit cumbersome, but I hope you can hold on till the weekend.
Credits:
@darz
@raw235
@mattiadj
@Ace King 34
Click to expand...
Click to collapse
Worked for me
13 GB internal storage

aerialus said:
not work in FW XM Dual
how to swap internal and external in FW XMD ?
Click to expand...
Click to collapse
I will need your help for that. If you can use ADB and pull these files for me and zip and upload here, it would certainly be very helpful.
Pull the folder "/dev/block/vold"
Open Terminal Emulator that you downloaded and run these scripts
Code:
cat /proc/partitions > partitions
Press enter
Code:
mount > mount
Then, on the computer, open a command prompt window (or terminal on Linux) and type in
Code:
adb pull /partitions
Code:
adb pull /mount
Put these two files in the zip along with the vold folder and post them here. I will look into it and provide you the guide.
jereMarfil24 said:
@gadgetroid , will it work in Xperia M Dual 4.2 ?
Click to expand...
Click to collapse
Since it runs 4.2, I can't be very sure, as Sony may have changed device names. Once the above user submits the files, I will look into it and post the guide.

gadgetroid said:
I will need your help for that. If you can use ADB and pull these files for me and zip and upload here, it would certainly be very helpful.
Pull the folder "/dev/block/vold"
Open Terminal Emulator that you downloaded and run these scripts
Code:
cat /proc/partitions > partitions
Press enter
Click to expand...
Click to collapse
i never use ADB ,, but i will try,,
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?

Did u written su above?
Sent from my C1904 using Tapatalk 4

aerialus said:
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?
Click to expand...
Click to collapse
Perhaps you aren't rooted. That is why the script in the OP didn't work for you either.
When you type in su in the terminal, do you get any prompt on your phone?
Or perhaps it could be that you haven't rooted the device completely. You need busybox for making any operations on the ~/ partition.

gadgetroid said:
Perhaps you aren't rooted. That is why the script in the OP didn't work for you either.
When you type in su in the terminal, do you get any prompt on your phone?
Or perhaps it could be that you haven't rooted the device completely. You need busybox for making any operations on the ~/ partition.
Click to expand...
Click to collapse
my device is already rooted and have Busybox installed,,
please look at my attachment

aerialus said:
my device is already rooted and have Busybox installed,,
please look at my attachment
Click to expand...
Click to collapse
Have you used root fixer? As mentioned by the OP of the root thread? If you have ES File Explorer, just try mounting the system partition as r/w over there. If it reboots immediately, then you aren't rooted properly yet.

aerialus said:
i never use ADB ,, but i will try,,
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?
Click to expand...
Click to collapse
If I understand right the command will create the files "partitions" and "mount" directly into the root path that's why it claims "r/o file system"
try
Code:
cat /proc/partitions > [COLOR="Red"]/sdcard/[/COLOR]partitions
and pull it on your computer then with
Code:
adb pull [COLOR="red"]/sdcard/[/COLOR]partitions
same with "mount"
this should create those files into the sdcard which is not read only.

gadgetroid said:
Have you used root fixer? As mentioned by the OP of the root thread? If you have ES File Explorer, just try mounting the system partition as r/w over there. If it reboots immediately, then you aren't rooted properly yet.
Click to expand...
Click to collapse
in XM Dual no need use rootfixer anymore,,
just root with tools and success full root,,
magicw said:
If I understand right the command will create the files "partitions" and "mount" directly into the root path that's why it claims "r/o file system"
try
Code:
cat /proc/partitions > [COLOR="Red"]/sdcard/[/COLOR]partitions
and pull it on your computer then with
Code:
adb pull [COLOR="red"]/sdcard/[/COLOR]partitions
same with "mount"
this should create those files into the sdcard which is not read only.
Click to expand...
Click to collapse
ok i will try :fingers-crossed:

Yes. That is exactly what it does. It works if you put in sdcard

Script
I have created a script for this. If OP gives me permission i can publish it.

pull partitions and mounts success,,
but when i try to pull folder "/dev/block/vold"
the result is " 0 files pulled, 0 files skipped"
see my attachment

icoolguy1995 said:
I have created a script for this. If OP gives me permission i can publish it.
Click to expand...
Click to collapse
Sure, go ahead. Publish it. Are you sure its working? Cause when I created a script, it used to give me errors. That is why I posted this huge tutorial.

gadgetroid said:
Sure, go ahead. Publish it. Are you sure its working? Cause when I created a script, it used to give me errors. That is why I posted this huge tutorial.
Click to expand...
Click to collapse
I have attached the script in attachments.
STEPS TO EXECUTE
1) Download script
2) place it in SD card and open any Explorer in which you can change permissions.
3) Go where you have placed script and change its permission (Thick all the boxes)
4) Execute it.
But it will last till a reboot only
Simple Way
1) Download script manager from play store
2) Execute script with it and tick the boot,su option and tick it is executable.
Your memory is swapped

icoolguy1995 said:
I have attached the script in attachments.
STEPS TO EXECUTE
1) Download script
2) place it in SD card and open any Explorer in which you can change permissions.
3) Go where you have placed script and change its permission (Thick all the boxes)
4) Execute it.
But it will last till a reboot only
Simple Way
1) Download script manager from play store
2) Execute script with it and tick the boot,su option and tick it is executable.
Your memory is swapped
Click to expand...
Click to collapse
I'll add it to the op soon. BTW, if you place the script in /data folder and set it to rw-r--r--, it will be easier. That way, the script won't be in the wrong drive after it's been switched.

No it will not work unless all the options are ticked on permission setting.

icoolguy1995 said:
No it will not work unless all the options are ticked on permission setting.
Click to expand...
Click to collapse
It works for me with rw-r--r--
This message was brought to you by my Sony Xperia M (C1905), using the XDA app.

[FIX] Internal Memory Read-Only Issue for Apps

If your apps can't write files to your internal memory, or having problems saving images from IMGR/Chrome, this fix is for you.
I'm not sure how many had this issue after rooting their phones but it had been driving me crazy since I rooted my phone. I tried editing my build.prop securestorage=false, with no positive results.
I then came across a fix someone had for their Note 3, using terminal to fix this error, without having to reflash your rom.
Notes-
1. Read all the steps before attempting this
2. I have used this method to successfully fix my sdcard and make it usable
Prerequisites-
1. You will need root
2. You will need terminal emulator on your phone
3. You will need some reading skills and glasses if your eyes are weak..
Steps-
1. Open terminal emulator
2. Type "su"
Your screen should look like this
Code:
su
Now press enter
3. Now type this command, "restorecon -v -R /data/media"
Your screen should look like this now
Code:
su
restorecon -v -R /data/media
Now press enter
It will run several lines of code as it restores your system entries
4. Reboot
5.Now you can use your internal sdcard without any issues
Credit

Dude. I've been searching for this for like 2 hours. I was about to wipe my phone. You're awesome!

Didnt work for me. im using ES File Manager to edit the file but it wont let me. reboot like 3 times already.
Never mind, i think is a ES File Manager issue, i got Build.pro editor and that fixed.

didn't work for me

Lookie here
http://forum.xda-developers.com/showthread.php?t=2906384
And this is pretty much what the app does
Go to page 4 & post #35 in this thread.
http://forum.xda-developers.com/showthread.php?t=1810294&page=4
sent from nowhere

Thanks so much!! Works for me too, and I was about to ODIN flash,.