Welcome to egingell’s SGS2 info page

You’re here because you’re curious about what I have done to my phone, otherwise you wouldn’t have clicked. Well, read on.

• Use Link2SD Without a Second Partition – E4GT
• Clean up Link2SD’s Trail.
• Copy Multi DPI Google Play Store and Google Services Framework
  apps to system compensating for the /preload partition.
• Delete Bloatware – SGS2

• My ROM: Stock Rooted Jelly Bean 4.1.2-GB27 – I’m sticking with stock until Samsung allows one-click toggling of WiMAX.
• Recovery: Stock GB27 – I have no need or desire to flash a custom Recovery. You can do everything a Recovery can do from a live boot.
  That’s right, kids, one can clear the dalvik cache, clear all app data, clear the cache, and push files to /system or /preload without using
  a custom recovery. You can even flash a modem, recovery, or kernel. I use
  Root Explorer. The latest version incorporates a SMB client, so I can get files from my PC easily and paste them directy to whichever
  protected directory I want and set appropriate permissions. I use ADB only when I don’t want to type out shell commands on the phone’s
  tiny keyboard or “oops” emergencies.
• I have enabled init.d boot up scripts by renaming ‘/system/bin/debuggerd’ to ‘/system/bin/debuggerd.bin’ and I’m using ‘/system/bin/debuggerd’
  as a middle-man script for the debugger daemon to use busybox’s ‘run-parts’ to execute the scripts in ‘/data/local/init.d’
  as well as do the mounting and binding and then execute ‘/system/bin/debuggerd.bin’.
• I lifted ‘/system/bin/bootanimation’ from rujelus22’s Blu Kuban – JB ROM
  and replaced the original with it to enable custom boot animations.
• I changed my boot splash screen using Hellcat’s SGS2
  BootScreen Changer.
• My SanDisk 32GB SDHC card is layed out thusly:

  root@android:/ # cat /sdcard/extSdCardInfo.txt
                       Device   Blocks Info
  /dev/block/cyasblkdevblk0p1 30843904 ->/storage/sdcard0
  /dev/block/cyasblkdevblk0p2   320512 x>/storage/extSdCard - not mounted
  root@android:/ #

• My internal SD card is layed out thisly:

  root@android:/ # cat /sdcard/intSdCardInfo.txt
                 Device   Blocks Info
   /dev/block/mmcblk0p1    20480 EFS
   /dev/block/mmcblk0p2     1280 Boot 1
   /dev/block/mmcblk0p3     1280 Boot 2
   /dev/block/mmcblk0p4     8192 Param
   /dev/block/mmcblk0p5     8192 Kernel
   /dev/block/mmcblk0p6     8192 Recovery
   /dev/block/mmcblk0p7   307200 ->/cache
   /dev/block/mmcblk0p8    16384 Modem
   /dev/block/mmcblk0p9   524288 ->/system
  /dev/block/mmcblk0p10  2097152 ->/data
  /dev/block/mmcblk0p11 12066816 ->/data/sdext2 - reformated as EXT4.
  /dev/block/mmcblk0p12   319488 ->/preload
  root@android:/ #

• I have a bootup script in /data/local/init.d that scans /data/sdext2/data for directories to bind to matching directories in
  ‘/data/data’.
• My ‘/system/bin/debuggerd’.

  root@android:/ # cat /system/bin/debuggerd
  #!/system/bin/sh
  #added by link2sd
  LOG=/data/link2sd-debuggerd.log
  echo "$(date) mounting..." > $LOG
  
  mount -t ext4 -o rw,noatime,barrier=0,nobh,errors=continue /dev/block/mmcblk0p11 /data/sdext2 1>>$LOG 2>>$LOG
  
  echo "" >> $LOG
  echo "init.d" >> $LOG
  
  /system/xbin/busybox run-parts /data/local/init.d 1>>$LOG 2>>$LOG
  
  echo "" >> $LOG
  
  mount >> $LOG
  echo "$(date) mount finished" >> $LOG
  echo debuggerd.bin launched >> $LOG
  exec /system/bin/debuggerd.bin
  root@android:/ #

• My ‘/system/etc/vold.fstab’.

  root@android:/ # cat /system/etc/vold.fstab
  ## Vold 2.0 Generic fstab
  ## - San Mehat (san@android.com)
  ##
  
  #######################
  ## Regular device mount
  ##
  ## Format: dev_mount  <mount_point><sysfs_path1...>
  ## label        - Label for the volume
  ## mount_point  - Where the volume will be mounted
  ## part         - Partition # (1 based), or 'auto' for first usable partition.
  ## <sysfs_path> - List of sysfs paths to source devices
  ## storage_struct - ex) series, "/mnt/sdcard/extStorages" / parallel
  ######################
  # internal sdcard
  {
          ums_sys_path = /sys/class/android_usb/f_mass_storage/lun0/file
          secure_format = enable
          discard = enable
  }
  #dev_mount sdcard /storage/sdcard0 11 /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 encryptable_nonremovable
  dev_mount sdcard /storage/sdcard0 1 /devices/virtual/block/cyasblkdevblk0
  
  # external sdcard
  {
          ums_sys_path = /sys/class/android_usb/f_mass_storage/lun1/file
          android_secure_containers = enable
  }
  dev_mount sdcard1 /storage/extSdCard 2 /devices/virtual/block/cyasblkdevblk0
  
  
  #usb host device
  {
          media_type = usb
  }
  dev_mount sda /storage/UsbDriveA auto /devices/platform/s3c_otghcd/usb
  
  #usb host device
  {
          media_type = usb
  }
  dev_mount sdb /storage/UsbDriveB auto /devices/platform/s3c_otghcd/usb
  
  #usb host device
  {
          media_type = usb
  }
  dev_mount sdc /storage/UsbDriveC auto /devices/platform/s3c_otghcd/usb
  
  #usb host device
  {
          media_type = usb
  }
  dev_mount sdd /storage/UsbDriveD auto /devices/platform/s3c_otghcd/usb
  
  #usb host device
  {
          media_type = usb
  }
  dev_mount sde /storage/UsbDriveE auto /devices/platform/s3c_otghcd/usb
  
  #usb host device
  {
          media_type = usb
  }
  dev_mount sdf /storage/UsbDriveF auto /devices/platform/s3c_otghcd/usb
  #EOF
  root@android:/ #
  

• My binding script.

  root@android:/ # cat /data/local/init.d/12symlink
  #!/system/bin/sh
  LOG=/data/symlink.log;
  echo "Symlink" > $LOG
  
  busybox mount -o rw,remount /system
  
  cd /data/sdext2/data/
  
  for APP in *; do
          mount -o bind "/data/sdext2/data/$APP" "/data/data/$APP" 1>>$LOG 2>>$LOG;
  done
  
  busybox mount -o ro,remount /system
  root@android:/ #

Disclaimer: I don’t have an iPhone, so I can’t confirm whether these work on its version of Draw Something.

Exit the game and start it again for the following:* Get new words without using a bomb. This works even if you’re in the process of drawing something.
* Watch your friend draw from the beginning.
* Hide your guesses if you haven’t guessed correctly, yet.
* Get new letters from which to use to guess the picture.

Drawing:* Don’t be too abstract, the point of the game is for your “opponent” to guess correctly.
* If you need more colors, tap the [+] to the right of the color bar.
* The color bar scrolls horizontally (left and right).

Download:* Google Play Store
* iTunes

What I’ve done:

• Flashed a rooted stock ROM – JB 4.2.2-MF9 using an Odin One-Click provided by Rwilco12 at XDA.
• Enabled custom boot animations.
• Enabled init.d scripts.

FAQ:

• Q: Are you going to remount the SanDisk to /sdcard and the internal SD card to /data/sdext2 like I did with my S2?
  A: Assuming the data partition is still severely gimped, you bet! Just as soon as I figure out how JB 4.2.2 mounts the internal SD card… and I will figure it out.
  A: Turns out I don’t need to /data and /sdcard share the same partition.
• Q: How did you enable custom boot animations?
  A: I replaced /system/bin/bootanimation with one from a custom ROM (Blu Kuban S4) and fixed its user/group (root/shell) and permissions (755).
• Q: How did you enable init.d scripts.
  A: I added /system/etc/install-recovery.sh that executes the init.d scripts.
• Q: How did you get an Android Weather widget on your PIN lock screen?
  A: Xposed with the module Samsung Multiple Widgets.

Random Boot Sound Using Notification SoundsPreboot requires init.d. See the OP for enabling it if you are on a stock rooted ROM and requires the file to be readable and executable (“chmod 755” works fine).
Postboot requires an app such as Scripter (ROM Toolbox) or Script Manager to execute the script at boot.

Requires the variable $RANDOM. You can make sure it’s available from the command line (“echo $RANDOM”).

Use this script at your own risk. I provide no warranties or guarantees.

What does this script do?

1. Check for carrier boot up sounds (sub folders in the “/system/media/audio/ui” folder) and copies them to “/system/media/audio/notifications” renaming them as needed.
2. Create symlinks in the above folders to “/system/media/audio/ui/PowerOn.ogg”.
3. Check if “/system/media/audio/notifications/PowerOn.ogg” is present and copies “/system/media/audio/ui/PowerOn.ogg” there if it’s not.
4. Count the number of files in “/system/media/audio/notifications”.
5. Grab a random number between 1 and the number of files found inclusive (math notation: “[1, numFiles]”).
6. Go through “/system/media/audio/notifications” and copy the file at index random to “/system/media/audio/ui/PowerOn.ogg”.

Notes:

• The stock file is included. If you want a different sound in its place, you can either comment out that line in the script and delete the “/system/media/audio/notifications/_PowerOn.ogg” files from “/system/media/audio/notifications” or just replace “/system/media/audio/notifications/PowerOn.ogg” with some other sound file and still delete the “/system/media/audio/notifications/_PowerOn.ogg” files from “/system/media/audio/notifications”.
• If you want more sounds, just copy them to “/system/media/audio/notifications” (OGG files only).
• The script does not check for valid files and blindly renames the destination file to “PowerOn.ogg”.
• It does not look in “/sdcard/media/audio/notifications” or anywhere else for audio files.
• I do not recommend using alarms or ringtones files as they are usually looped which can cause the media scanner to get stuck and overheat your phone or tablet – those files may continue to play even if you can’t hear them.
• If you can’t hear a sound on boot, it is likely that the file is either invalid or has no audio (ex: my /system/media/audio/ui/BST/PowerOn.ogg has no audio).
• It was tested and works on a Samsung Galaxy S2 (stock JB 4.1.2) and a Samsung Galaxy S4 (stock JB 4.2.2) both from Sprint and using stock kernels.
• There’s no obvious reason it won’t work on other phones and tablets with other ROMs from other carriers.

#!/system/bin/sh

mount -o remount,rw /system

cd /system/media/audio/ui
for X in "BST" "SPR" "VMU" "XAS"; do
 if [ $(realpath "/system/media/audio/ui/$X/PowerOn.ogg") = "/system/media/audio/ui/$X/PowerOn.ogg" ]; then
  mv "/system/media/audio/ui/$X/PowerOn.ogg" "/system/media/audio/notifications/${X}_PowerOn.ogg"
  ln -s "/system/media/audio/ui/PowerOn.ogg" "/system/media/audio/ui/$X/PowerOn.ogg"
 fi
done

if [ ! -f "/system/media/audio/notifications/PowerOn.ogg" ]; then
 cp "/system/media/audio/ui/PowerOn.ogg" "/system/media/audio/notifications/PowerOn.ogg";
 chmod 644 "/system/media/audio/notifications/PowerOn.ogg"
fi

cd /system/media/audio/notifications
FILES=0
for Y in *; do
 let FILES=$FILES+1;
done

let X=$RANDOM%$FILES
let X=$X+1

FILES=0
for Y in *; do
 let FILES=$FILES+1;
 if [ $FILES = $X ]; then
  cp "/system/media/audio/notifications/$Y" "/system/media/audio/ui/PowerOn.ogg";
  chmod 644 "/system/media/audio/ui/PowerOn.ogg"
 fi
done

mount -o remount,ro /system

Little Known Jelly Bean Features

Here are some features in Jelly Bean 4.1.2 and up that I’ve discovered that you may or may not be aware of:

• Two-finger swipe down on a notification: If it’s expandable it will expand giving you more options. Two-finger swipe up will collapse it.
• Swip a notification left or right to dismiss it. This does not work on persistent notifications.
• Long-tap a notification to get a link to “App info” which takes you directly to the app’s info screen where you can uninstall, force-stop, or clear its cache, data, or defaults. Also handy for determining which app put it there.
• Long-tap the app on the “Recent apps” dialog for the same “App info” link.
• You can turn off notifications for spammy apps (or any app) from its app info screen. You cannot turn off notifications for some system apps.
• Long-tap a toggle on the top of the notification pull-down for direct access to that item’s settings screen.
• Press either volume button to show the volume scale and tap the grey gear to expand it.
• Tap the grey gear above the toggles on the notification pull-down to access the system settings.
• Tap the grey clock above the toggles on the notification pull-down to access the world clock.
• If you have no Search soft-key, you You can long-tap the Menu soft-key to access Search. This only works from the home/launcher screen. May not work in all apps.
• You can add contacts to the Emergency Dialer by adding them to the “ICE – emergency contacts” contacts group then tap the “+” on the Emergency Dialer. You can add as many contacts as you want to the group; however, you can only add four to the Emergency Dialer at a time (only JB 4.2.2 and up).
• Easter egg: Jelly Bean Bag. Execute the following from the command line. Root required. This is actually one of the Daydream modes (BeanFlinger) – still cool, though.

  su -c am start com.android.systemui.BeanBag

Note: I have not confirmed that these features are not available on older Android OS’s, they could very well be.

Make ADB localhost Work on Your Jelly Bean 4.2.2 DeviceIn Jelly Bean 4.2.2, ADB now uses RSA keys to explicitly allow certain clients. This poses a problem when attempting to use ADB on your phone locally and the ADB daemon won’t write its RSA key to disk due to the file system being read-only. This is the easiest way to make it work.

Disclaimer: I am not responsible for you doing this wrong and breaking your phone.

This will not work on Android 4.1.2 or older.

1. Make /data/.android.
2. Do one of the following:
   1. If you’re using a custom ROM with init.d, put the following into an init.d script.

      #!/system/bin/sh
      if [ ! -e "/.android" ]; then
          busybox mount -o rw,remount /
          mkdir /.android
          mount -o bind /data/.android /.android
          busybox mount -o ro,remount /
      fi

   2. If you have hacked in init.d support by hooking the debuggerd binary, add the script above to your debuggerd script *or* an init.d script.
3. Reboot the device (if you used option 2 in the previous step, restart the debugger (“stop debuggerd; start debuggerd“)).
4. After the phone boots completely, check /.android for contents. If it’s empty, restart usb debugging (either from Developer Options (toggle USB Debugging off and back on) or via the command line (“stop adbd; start adbd“)). There should now be stuff in /.android.
5. Append the contents of /.android/adbkey.pub to /data/misc/adb/adb_keys (“cat /.android/adbkey.pub >> /data/misc/adb/adb_keys; echo “” >> /data/misc/adb/adb_keys“).
6. Start the ADB server on the phone from the command line using ADB on your PC or a terminal emulator.

   root@android:/ # adb start-server

7. The phone should pop the authentication dialog – click OK. If the authentication dialog doesn’t pop, follow the striked out steps above.

Edit [08/02/2014]: Turns out two of the above steps aren’t required. Steps amended above.

Notes:

• Don’t delete /data/.android or the contents therein.
• Tested on my SGS4 with hacked-in init.d support.
• You can also find the abdkey.pub file on your Windows’ PC here, C:\Users\[user name]\.android\abdkey.pub. Copy it to your device, then append it to /data/misc/adb/adb_keys and you won’t need to initially use the USB to allow the PC connection.

Before:

root@android:/ # adb shell ls
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device offline
255|root@android:/ #

After:

root@android:/ # adb shell ls
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
MSM8960_lpm.rc
acct
cache
carrier
charger
config
d
data
data_1
data_2
data_3
default.prop
dev
efs
etc
extSdCard
file_contexts
firmware
firmware-mdm
fstab.qcom
init
init.carrier.rc
init.goldfish.rc
init.qcom.class_core.sh
init.qcom.class_main.sh
init.qcom.early_boot.sh
init.qcom.lpm_boot.sh
init.qcom.rc
init.qcom.ril.sh
init.qcom.sh
init.qcom.syspart_fixup.sh
init.qcom.usb.rc
init.qcom.usb.sh
init.rc
init.target.rc
init.trace.rc
init.usb.rc
mnt
mnt_1
persdata
preload
proc
property_contexts
res
root
sbin
sdcard
seapp_contexts
sepolicy
storage
sys
system
tombstones
ueventd.goldfish.rc
ueventd.qcom.rc
ueventd.rc
vendor
root@android:/ #