Database Develop

[HOW-TO] Have it all - Enomther's 1.5/6.1+Himem+Apps2SD

Tools you'll need:
1. Rooted Nexus
2. sdcard with 2 primary partitions 1. fat32 2. ext2/3 (I did 500mb)---class 6 card highly recommended
3.Enomther's 1.6.1 found here or Enomther's 1.5.1 found here (placed at root of sdcard)
4. Himem 1.6.1 kernel update found here or Himem 1.51 kernel update found here (placed at root of sdcard)
5. Titanium backup (available in the Market...donation key recommended)
6. Be open to frustration (and possibly, but not likely, damage your device) and not hold me responsible!
Steps to take:
If you are already running EM1.5/6.1 WITHOUT the memory kernel hack, you should be able to skip the titanium and wipe part, and skip straight to step #5, however...MAKE SURE YOU NANDROID!!! first.
1. Backup!! (nandroid <most important>/Titanium <recommend donation key, as I don't know free functionality)
2. Wipe
3. Flash 1.5.1 or 1.6.1 (or reflash if already running with himem)
4. Reboot WITHOUT enabling Google backup
5. Lucid in adb shell or terminal emulator (dalvik2sd <lucid -dc -a> optional)
Code:
su
lucid -a -sd
lucid -dc -sd
reboot
6. After full boot, reboot to recovery console
8. Once in recovery, flash Himem, reboot again
7. Install Titanium app from the market
8. Restore Titanium backup made in step 1 (in batch>all apps+data option)
9. Reboot one final time
11. Check everything worked by typing "free" in terminal and verify internal storage in settings (mine says 395332 total memory and 174 free internal memory)
12. <optional> Flash/apply theme or morph
EDIT: Beware!!! This is my 666th post!!!

The basic scenario is to set up apps2sd before flashing the himem kernel...I was getting bootloops performing it any other way than this. Your results may vary.
If you get bootloops and skipped anything, you may need to perform complete process.
Also, if in bootloop (stuck at the X splash screen),
Code:
adb shell reboot recovery
saves having to pull the battery.

Little more info needed for the android newbies out there, e.g. ext partition ect
but overall nice how to, and thanks for the info ill giv it whirl soon

After flashing the highmem it got's stuck at the X splash screen.

lolittle said:
Little more info needed for the android newbies out there, e.g. ext partition ect
but overall nice how to, and thanks for the info ill giv it whirl soon
Click to expand...
Click to collapse
Ahh, yes...sdcard partitions...Post #1 updated. Good looking out.
Breakthecycle2 said:
After flashing the highmem it got's stuck at the X splash screen.
Click to expand...
Click to collapse
Happened to me a couple times in my experiments. Make sure you are not skipping any steps and are not using a different/older copy of the himem...download a fresh copy from the link in the OP as the file has changed in the last few days.
While stuck at the X splash screen (A.K.A. bootloop) do this.
Code:
adb shell reboot recovery
start over from step #2 above.
2. wipe
3. flash 1.5.1...etc.

What is the command to reverse the davlik back to the phone memory?
What wouyld the command be in adb to check if apps2sd and davlik2sd or vice versa actually worked correctly before preceding?

Should be
Code:
su
lucid -dc -g1
reboot
Mikey1022 said:
What is the command to reverse the davlik back to the phone memory?
What wouyld the command be in adb to check if apps2sd and davlik2sd or vice versa actually worked correctly before preceding?
Click to expand...
Click to collapse

Code:
# lucid -a -sd
lucid -a -sd
Nothing was done. /system/sd/app is FOLDER.
Please rm -r /system/sd/app first.
Nothing was done. /system/sd/app-private is FOLDER.
Please rm -r /system/sd/app-private first.
Hmmm doesnt seem like it quit worked out lol
Did what it suggested for mt to remove the two folders and reapplied, worked.
lucid -s confirmed it

Mikey1022 said:
Code:
# lucid -a -sd
lucid -a -sd
Nothing was done. /system/sd/app is FOLDER.
Please rm -r /system/sd/app first.
Nothing was done. /system/sd/app-private is FOLDER.
Please rm -r /system/sd/app-private first.
Hmmm doesnt seem like it quit worked out lol
Did what it suggested for mt to remove the two folders and reapplied, worked.
lucid -s confirmed it
Click to expand...
Click to collapse
So, you got it working?
If not:
Code:
su
lucid -c
will clear your ext partition of app, app-private and dalvik-cache folders. Then you can run lucid -a -sd without issue. You may have to reboot in between, maybe not.
Oh, and thanks for fixing my quote...posted it while driving.

All good now

[Q] FRG83D Update Problems

I have a rooted (rage) N1 that I loaded the G2 Launcher2.apk on to. Doing this caused the N1 to fail the update when it tried to apply FRG83D.
Stupidly, I decided that deleting the /system/app/launcher2.apk file was the right idea. And then rebooted.
Now the phone hangs on the boot animation. Attempting to apply with NO launcher2.apk results in the same error.
I have ADB installed, and I can adb shell into the phone and su. I have the old, original N1 launcher backed up on my SD card, but I can't figure out how to:
1) Mount the sdcard while ADB shell'd in from just the boot animation screen so that I can browse the card
2) Move the launcher2.apk backup file into the /system/app directory without getting a "Cross-device link" error when I use mv.
Can someone provide me with the exact commands to get the /sdcard/launcher2 backup/launcher2.apk file on to /system/app while ADB'd in only from the boot animation?
Thanks so much, I'm digging through the forums in the mean time, but it's tricky to track down exactly what to do.

I appear to have fixed everything. I wasn't able to access the SD card through ADB, but I *was* able to mount it using the:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
method.
From there, I copied my backup to my desktop, and I found I was able to ADB push to just the /data/local/tmp directory. Don't know if I could've gone anywhere else, but that worked.
From there, I was about to:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount/make writable the /system/app directory,
and then:
Code:
cat /data/local/tmp/launcher2.apk > /system/app/launcher2.apk
So there's that. All to restore the Launcher to a version that would allow for a somewhat pointless update. Woo!

Deodex failure, need help please.

Hi guys
I'm new to deodexing, following a guide for XUltimate.
I copied my system\app dir to a folder called origi_app, and my system\framework to a folder called origi_frame on my int SD card, then copied these two folders to my PC XUltimate dir.
Ran option 3, then 4, both finished with sucessful.
This gave me two new folders in the XUltimate dir...
done_app & done_frame
I copied these back to my int SD card, then following the guide, ran ADB from cmd prompt..
Typed: ADB Shell
Got a $
Typed: SU
This gave me a Permission Denied ??
So as per the guide, I tried Root Explorer...
Selected All the .apps in done_App, selected copy and then tried to paste into the system\app dir.... this then gave me a failed to copy due to lack of space error and the phone started to vibrate and com.android force closing repeatedly...
Were did I go wrong, why did I get permission denied trying to get the SU cmd?
The full adb guide was as follows:
adb shell
su
stop
mount -o rw,remount /dev/block/mmcblk1p21 /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
mount -o ro,remount /dev/block/mmcblk1p21 /system
reboot
As above, got as far as SU then got permission denied!
So thankfully I did a nandroid backup before and am currently restoring it...
EDIT: My Backup has just finished restoring from CWM... rebooted but it is now on original startup setup and getting force closes for lots of apps???
Had to re add my APN settings to re download MY Backup and am currently restoring apps and data from it now! Fingers crossed. I thought the whole point of a cwm back up was to create an exact image of the whole system, files, date and settings etc?

Well, restored via My Backup, but rom manager and Sky news kept force closing, so wiped the whole thing and flash a custom js8 from from Doc's kitchen... glad I did... just miss the cirlce battery mod I had before.

Merge updated system apps

When a system app is updated seems to store the old version on the systems folder and the new version on the SD card. Is there a way to merge the new version onto the system? Once merged there is only the system version like it was when the ROM first was installed. I thought I did this once before but don't remember how or what I used to do it.

you would need to remove the app from the system partition and then install the newer one in its place, if it wasnt this way when your phone got corrupt by a bad update and you had to do a factory reset then you would be stuck with the same corrupt apk. so unless you absolutely need dont bother, and if you do the easiest way would probably be through root explore or similar file manager.

Titanium pro does it but not worth the $5 or $6. Used to do it for free just not remember the apps name.
Sent from my HTC Magic using XDA App

you can always copy the apk over using terminal
put it at the root of your sdcard and type
Code:
su
mount /system -o remount,rw
cp /sdcard/updatedapp.apk /system/app/appyouwanttoreplace.apk
mount /system -o remount,ro
Careful though, you don't want to accidentally brick
Make sure the app works and if it's an important app you might want to do it from recovery because it may be running
in recovery you type the following in console (Amon_RA Recovery):
Code:
mount sdcard
mount system
cp /sdcard/updatedapp.apk /system/app/appyouwanttoreplace.apk
Make sure the app update works though, or else you'll get force closes
also may be a good idea to backup the original app with something like:
Code:
cp /system/app/blah.apk /sdcard/blah.apk.backup
Then if anything and you need to restore do this from recovery console:
Code:
cp /sdcard/blah.apk.backup /system/app/blah.apk
yes i really love console

cannot root S5830

Model Number - GT-S5830
Android Version - 2.3.6
Baseband version - S5830XWKT3
Kernel Version - 2.6.35.7-perf-CL787041 [email protected] #1
Build Number - GINGERBREAD.XWKT7
Virgin Galaxy Ace S5830.... i cannot root it.
so far i've tried..( This Guide )
universal_gb_root_v25.zip / universal_gb_unroot_v9.zip
and...
upd_1.zip / unroot.zip
and.....
AceGingerRoot.zip
also tried superoneclick which cannot root it on any setting.
what have I overlooked ?
i had planned to root it, install CWM recovery and make backup of the Optus carrier rom, then instal custom rom.... maybe i should download australian rom from sammobile and flash that replacing the current optus carrier one.
also when i load into the default android system recovery (Pwr + home key), down the bottom there is a message in yellow saying...
-- Appling Muti-CSC --
Can't access to '/system/csc/OPP/system'.
i have no idea what that means.

simmo2302 said:
Model Number - GT-S5830
Android Version - 2.3.6
Baseband version - S5830XWKT3
Kernel Version - 2.6.35.7-perf-CL787041 [email protected] #1
Build Number - GINGERBREAD.XWKT7
Virgin Galaxy Ace S5830.... i cannot root it.
so far i've tried..( This Guide )
universal_gb_root_v25.zip / universal_gb_unroot_v9.zip
and...
upd_1.zip / unroot.zip
and.....
AceGingerRoot.zip
also tried superoneclick which cannot root it on any setting.
what have I overlooked ?
i had planned to root it, install CWM recovery and make backup of the Optus carrier rom, then instal custom rom.... maybe i should download australian rom from sammobile and flash that replacing the current optus carrier one.
also when i load into the default android system recovery (Pwr + home key), down the bottom there is a message in yellow saying...
-- Appling Muti-CSC --
Can't access to '/system/csc/OPP/system'.
i have no idea what that means.
Click to expand...
Click to collapse
If your phone is unlocked try to flash a fresh stock rom via Odin, maybe you don't have enought free space in your system patition

cheers i'll try that. freeing up some space.
also i dont know if it is locked to Optus (the carrier) or not, does it matter if it is ?
if so i might have to look into that....

simmo2302 said:
cheers i'll try that. freeing up some space.
also i dont know if it is locked to Optus (the carrier) or not, does it matter if it is ?
if so i might have to look into that....
Click to expand...
Click to collapse
hmmm... well aparently it IS locked to the carrier Optus network. - i dont kno how/if that effects it being rooted or not.
i tried to root the device with the gb_universal_v25.zip again, and then without rebooting installing CWM 5.0.26.
the CWM is there now. but still no root.

simmo2302 said:
hmmm... well aparently it IS locked to the carrier Optus network. - i dont kno how/if that effects it being rooted or not.
i tried to root the device with the gb_universal_v25.zip again, and then without rebooting installing CWM 5.0.26.
the CWM is there now. but still no root.
Click to expand...
Click to collapse
Do you have thinkdroid installed?

Viper The Ripper said:
Do you have thinkdroid installed?
Click to expand...
Click to collapse
OK, just had a terrible time with this, but i may have got it now..... (have tried to do as much research myself, so i dont be a noob and ask every noob question under the sun)
i ended up getting the crappers with it, so in the menu settings i did a factory reset.
and... got stuck in a boot loop.....
rebooted into recovery.. wiped data/factory reset, wiped cache, wiped davlik aswell.
rebooted, and still boot loop.
put Ace into download mode (Pwr +vol dwn + home), ran Odin multidownloader 4.38 and used proper firmware (one package) from sammobile and coopers_v1.0.ops, and reflashed stock FW onto the Ace.
successfully passed Odin, rebooted.. (cant remember if it worked right away or if i had to do another wipe session).... but got it working again...
went back into recovery (reverted back to stock now)... tried rooting with universal_gb_root_v25... didnt work... unrooted with universal_gb_unroot_v9.
tried for ages to find universal_gb_root_v26 but couldnt find a site that didnt want me to do a survey and give my mobile number... so i found (somewhere) a universal_gb_root_v25b.
rooted with that.... rebooted.. and checked with 3 different SU / root checkers... and each one says Root is Good ! Yay !
so now i'm going to go back and put on ClockworkMod Recovery 5.0.2.6 and then try some custom roms
still undecided which one to use. (ideally looking for one, lean, fast and stable considering how restricted the Ace is)
cheers for all your help.

simmo2302 said:
OK, just had a terrible time with this, but i may have got it now..... (have tried to do as much research myself, so i dont be a noob and ask every noob question under the sun)
i ended up getting the crappers with it, so in the menu settings i did a factory reset.
and... got stuck in a boot loop.....
rebooted into recovery.. wiped data/factory reset, wiped cache, wiped davlik aswell.
rebooted, and still boot loop.
put Ace into download mode (Pwr +vol dwn + home), ran Odin multidownloader 4.38 and used proper firmware (one package) from sammobile and coopers_v1.0.ops, and reflashed stock FW onto the Ace.
successfully passed Odin, rebooted.. (cant remember if it worked right away or if i had to do another wipe session).... but got it working again...
went back into recovery (reverted back to stock now)... tried rooting with universal_gb_root_v25... didnt work... unrooted with universal_gb_unroot_v9.
tried for ages to find universal_gb_root_v26 but couldnt find a site that didnt want me to do a survey and give my mobile number... so i found (somewhere) a universal_gb_root_v25b.
rooted with that.... rebooted.. and checked with 3 different SU / root checkers... and each one says Root is Good ! Yay !
so now i'm going to go back and put on ClockworkMod Recovery 5.0.2.6 and then try some custom roms
still undecided which one to use. (ideally looking for one, lean, fast and stable considering how restricted the Ace is)
cheers for all your help.
Click to expand...
Click to collapse
I'd tell you that if you didn't have enough space on the system partition, maybe you could try flashing THIS before rooting your device and then you'll try flashing root again so...

Try The Ultimatum
Sent From my GT-S5830.
Current Rom-The Ultimatum
Kernel-Fire OC Kernel
Audio Manager-BEATS
Hit Thanks you unthankful $*%$&. Its There For A Reason.

Samsung Galaxy Ace [GT-S5830] root method (Optus branded units and possibly others)
I tried many methods, and none would work with my Optus branded S5830. I assume it was partly due to having less than 1MB available on the /system partition. After some perseverance, it now has root, here was my method, hopefully it can help others.
Some files mentioned in this are available here: http://goo.gl/6XlwEx
1. Install Samsung USB drivers: SAMSUNG_USB_Driver_for_Mobile_Phones.exe
2. Install and setup (for atleast your android version) the SDK from Google (http://developer.android.com/sdk/index.html)
3. Ensure that the platform-tools (or which ever folder contains adb.exe) is in your system path variable (google it).
4. Put custom recovery image on sdcard: recovery-clockwork-5.0.2.6-galaxyace.zip
5. Turn off device, and boot to recovery (home + power)
6. Flash recovery-clockwork-5.0.2.6-galaxyace.zip and reboot
7. Turn off device, and boot to recovery again (home + power)
8. From a command prompt, run 'adb shell' it should drop you to a shell with root privileges (#).
Code:
> adb shell
#
9. Mount the '/system' partition from the custom recovery (mount partitions)
10. Make some room on your '/system' partition, delete Skype, Think Office, etc. You will need to do this as the bloatware has left no room for the su binary and SuperUser.apk
11. To get rid of skype or Think Office, from the command line type the following and then press enter.
Code:
# rm /system/app/Skype.apk
# rm /system/app/thinkdroid.apk
12. Extract universal_gb_root_v25.zip to a folder, and open another command prompt at .\universal_gb_root_v25\system\xbin and type the following commands:
Code:
> adb push busybox /system/xbin/
> adb push sqlite3 /system/xbin/
> adb push ssh /system/xbin/
> adb push su /system/xbin/
> adb push ..\app\Rootvalidator.apk /system/app/
> adb push ..\app\Supersu.apk /system/app/
13. Go Back to you 'adb shell' command prompt, and type the following to confirm the files have been pushed (you should not get a 'No such file or directory' message)
Code:
# ls /system/xbin/su
# ls /system/app/Supersu.apk
14. Set file access permissions (change mode) with the chmod command
Code:
# cd /system/xbin
# chmod 6755 su
# chmod 755 busybox
# chmod 755 sqlite3
# chmod 755 ssh
# chmod 644 /system/app/Supersu.apk
15. Now also copy the files you pushed to /system/xbin to /system/bin
Code:
# cp su /system/bin/
# cp ssh /system/bin/
# cp busybox /system/bin/
# cp sqlite3 /system/bin/
Code:
# reboot
The phone should reboot as normal,
17. Once in turn on USB debugging (google it). Go Back to you 'adb shell' command prompt (which will have quit the shell after the reboot) and type:
Code:
> adb shell
$
18. Note that this time there is likely a $ prompt, if so, enter the command 'su' and hit enter. SuperSU should pop up on your device asking for su rights, say yes. If you get the # prompt, you are now rooted.
Code:
$ su
#
19. As an alternative to steps 17 and 18, (after the reboot, before turning on USB debugging), you can just open Rootvalidator from your app drawer to test for root privileges. You will also notice the SuperSU and cwm_recovery apps now in the app drawer too.
If it hasn't worked, make sure you've followed the steps correctly, you can safely repeat them, or play with the file's (busybox, sqlite3, ssh and su) user owner/group owners so they match most of the the other files in '/system/bin' and see if it helps. USe 'ls -l', 'chown' and 'chgrp' (again, google their usage)
ie. as an example, below shows that 'busybox' is owned by user 'root' and group 'shell', to change the group ownership to root, i would type 'chgrp root busybox' at a root (#) prompt.
Code:
# ls -l
-rwxr-xr-x root shell 2007456 2008-08-01 22:00 busybox
-rwsr-sr-x root root 311872 2013-12-08 09:09 su
- The End -

I think you should you should flash a stock rom via odin.