So my i9000 has a broken internal memory chip and I fixed the situation with a tutorial and an 8gb memory card and the phone works again BUT it says I have no internal or external sd card. In the video, the man shows how to fix this, but he does it for ICS which has a diferent vold.fstab file and he also does it very quickly.
I need someone who can help me for the fstab.aries text modification in 4.3 android. Thank you.
These are the links I used
http://forum.xda-developers.com/showpost.php?p=35915484
http://www.youtube.com/watch?v=zdMhYYdMB08
UPDATE:
So currently I have Cyanogenmod 10.2 installed, these are the two files fstab.aries and fstab.goldfish (I read that vold.fstab which was previously found in system/etc has been deleted)
fstab.aries code
# Android fstab file.
# <src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
recovery /recovery mtd defaults recoveryonly
boot /boot mtd defaults recoveryonly
radio /radio mtd defaults recoveryonly
cache /cache yaffs2 defaults recoveryonly
datadata /datadata yaffs2 defaults recoveryonly
/dev/block/mmcblk0p1 /sdcard vfat defaults recoveryonly,lun=/sys/devices/platform/s3c-usbgadget/gadget/lun0/file
/dev/block/mmcblk1p1 /external_sd vfat defaults recoveryonly,lun=/sys/devices/platform/s3c-usbgadget/gadget/lun1/file
# LVM Volumes
/dev/lvpool/system /system ext4 ro wait
/dev/lvpool/userdata /data ext4 noatime,nodev,nosuid,nomblk_io_submit,errors=panic wait,encryptable=footer,length=-16384
/devices/platform/s3c-sdhci.0/mmc_host/mmc0 /storage/sdcard0 auto defaults voldmanaged=sdcard0:1,nonremovable
/devices/platform/s3c-sdhci.2/mmc_host/mmc2 /storage/sdcard1 auto defaults voldmanaged=sdcard1:auto
Click to expand...
Click to collapse
fstab.goldifsh code
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mtdblock0 /system ext4 ro,barrier=1 wait
/dev/block/mtdblock1 /data ext4 noatime,nosuid,nodev,barrier=1,nomblk_io_submit wait,check
/dev/block/mtdblock2 /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check
/devices/platform/goldfish_mmc.0 /storage/sdcard vfat defaults voldmanaged=sdcard:auto
Click to expand...
Click to collapse
samidoi said:
fstab.aries code
Click to expand...
Click to collapse
try switch these two lines (after you have backed up original as .bak file)
/devices/platform/s3c-sdhci.0/mmc_host/mmc0 /storage/sdcard0 auto defaults voldmanaged=sdcard0:1,nonremovable
/devices/platform/s3c-sdhci.2/mmc_host/mmc2 /storage/sdcard1 auto defaults voldmanaged=sdcard1:auto
Highlighted Blue part goes up
Highlighted red part comes down
also test this app and let me know if it works, without altering the fstab
Thank you so much mister, it worked!! Sorry for the delayed the response, I didn't have time to install 4.3 again but I finally did it now; I owe you a lot!!
So don't forget to hit his Thanks-Button
samidoi said:
Thank you so much mister, it worked!! Sorry for the delayed the response, I didn't have time to install 4.3 again but I finally did it now; I owe you a lot!!
Click to expand...
Click to collapse
samidoi said:
Thank you so much mister, it worked!! Sorry for the delayed the response, I didn't have time to install 4.3 again but I finally did it now; I owe you a lot!!
Click to expand...
Click to collapse
please, describe to me the detailed procedure. I did for CM10.1, CM10.2 but not.
I make the changes, but when I restart, returns to its original state. (I am root)
ethansetan said:
please, describe to me the detailed procedure. I did for CM10.1, CM10.2 but not.
I make the changes, but when I restart, returns to its original state. (I am root)
Click to expand...
Click to collapse
Same here... can't upgrade to CM10.2 until I figure this out. Any changes to the new fstab files are reverted when I reboot.
Ok so I found a different/interim solution using an init.d script. This is specifically for my Galaxy S2 Skyrocket (with broken internal memory), but can be modified for other phones.
Create a script file in your /system/etc/init.d/ directory called something like 11sd_remount:
Code:
sleep 2
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /storage/sdcard0
mount -t vfat -o umask=0000 /dev/block/vold/179:28 /storage/sdcard1
Then chmod 755 the script file. Upon reboot, the internal/external sdcards should be swapped. I've attached an update.zip which sets up the script automatically, and can be used after updating CM.
To get this to work on other devices, you really just need to figure out the mount points for your internal and external sdcards. To do this, type mount in adb shell (from within CM, not recovery), and you'll see a list of mount points. Somewhere towards the end will be the lines for /storage/sdcard0 and /storage/sdcard1, looking something like /dev/block/vold/179:97. Simply modify the script using these points, and you should be good to go.
srnoth said:
Simply modify the script using these points, and you should be good to go.
Click to expand...
Click to collapse
was this done in addition to switching mounts in fstab or only this?
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
xsenman said:
was this done in addition to switching mounts in fstab or only this?
Click to expand...
Click to collapse
This works without switching mounts in any fstab files, since that method no longer works in 4.3/CM10.2.
srnoth said:
This works without switching mounts in any fstab files, since that method no longer works in 4.3/CM10.2.
Click to expand...
Click to collapse
Hi All,
Regading the problems in fstab files, I have been facing some problem, the famous "No External Storage Available" when I try to open the camera or gallery.
I tried to update fstab.aries, but after reboot, it was replaced to original file. Btw, I tried to update init.aries.rc also, but the same thing, it was recovered to the original one.
Anyone have some idea?
japzjapz said:
Hi All,
Regading the problems in fstab files, I have been facing some problem, the famous "No External Storage Available" when I try to open the camera or gallery.
I tried to update fstab.aries, but after reboot, it was replaced to original file. Btw, I tried to update init.aries.rc also, but the same thing, it was recovered to the original one.
Anyone have some idea?
Click to expand...
Click to collapse
Your Internal SD card may be corrupted, try to fix that first, try reading this and links in it
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
hey, thanks for the work
your File includes
System/Etc/init.d > 11sd_remount
and also:
META-INF > CERT.RSA
META-INF > CERT.SF
META-INF > MANIFEST.MF
META-INF/com/android > metadata
META-INF/com/google/android > update-binary & updater-script
and those are all required.. right? and where do we put the META-INF folder? on the Devices top folder, in the same location as "system"?
and then on the script, we put our current physical sdcard1 onto the current sdcard0's mount point, & vice versa?
so 179:97 is typically where sdcard1 is by default, so we just change 179:97 to be the point for sdcard0 instead, and point sdcard1 to the default mount point for sdcard0?
i guess I got that right?
and when you say "CHMOD 755" (verb) the file, you mean:
Owner= Read, Write, Execute
Group= Read, Execute
Others=Read Execute
is that right? and is that ONLY for the file found at System/Etc/init.d > 11sd_remount??
and can I just change those permissions for that file in ES File Explorer?
thanks
chinarabbit said:
hey, thanks for the work
your File includes
System/Etc/init.d > 11sd_remount
and also:
META-INF > CERT.RSA
META-INF > CERT.SF
META-INF > MANIFEST.MF
META-INF/com/android > metadata
META-INF/com/google/android > update-binary & updater-script
and those are all required.. right? and where do we put the META-INF folder? on the Devices top folder, in the same location as "system"?
and then on the script, we put our current physical sdcard1 onto the current sdcard0's mount point, & vice versa?
so 179:97 is typically where sdcard1 is by default, so we just change 179:97 to be the point for sdcard0 instead, and point sdcard1 to the default mount point for sdcard0?
i guess I got that right?
and when you say "CHMOD 755" (verb) the file, you mean:
Owner= Read, Write, Execute
Group= Read, Execute
Others=Read Execute
is that right? and is that ONLY for the file found at System/Etc/init.d > 11sd_remount??
and can I just change those permissions for that file in ES File Explorer?
thanks
Click to expand...
Click to collapse
The only file you actually need is the 11sd_remount. The other files in the .zip are just part of the flashing process for your recovery.
So either you can:
Edit the .zip file to match your device, then flash, or
Simply edit the 11sd_remount file, copy it to /system/init.d/ and then "chmod 755 11sd_remount"
You can change the file permissions with ES Explorer, but it's simpler to use terminal emulator or adb shell to navigate to the correct folder and then chmod the script. The main thing you're doing is setting the permissions for the script to be executable.
Regarding the actual mount points, the best thing to do is, with your phone on & connected to a computer, run adb shell and type "mounts". This will give you a list of the current, default mount points, including both the internal and external sd cards. Use that info to enter the correct points in the 11sd_remount script.
OK, i copied the 11sd_remount file to the init.d folder, then set permissions to rwx r-x r-x, then Rebooted the device, and it didnt work.. actually I think my SD card disappeared, then I booted to recovery and cleared cache and rebooted and now things seem back to normal.. addresses didnt change, its as if nothing has been done.
except, now i think i'm missing the following mount point from my list of Android System Info:
- /mnt/asec/net.dinglisch.android.appfactory-1
/dev/block/dm-0 ext4 ro,dirsync,nosuid,nodev,noatime
which was the last thing on the list.. but I dont know if its related..
also, the original info says it: "can be used after updating CM." I dont have CyanogenMod
thoughts?
well I got Internal 2 External to work after reboot
after copying everything from the internal SD to a freshly formatted SD card
launched the app, clicked the green arrow, clicked ASUS,
clicked "Use per default"
set my original internal to /mnt/sdcard and external to /mnt/sdcard1
then hit "Show other devices" scrolled down and clicked the 2nd to the last, and went up to make the sure that "The ext. sdcard device access" was set to the same number
then clicked External 2 Internal to return to the top page
then I unchecked "Apply at boot" and clicked "External2 Internal", waited a few minutes, clicked it again, then checked "apply at boot", clicked "External2 Internal" again, waited, did it again, then again..
then clicked the "init.d" button once, waited, then rebooted, then waited a few minutes after booting, then checked storage and everything was working.. except my internal sd card is the same as my external sd card now.. there is a repeat of the 32GB card, which is fine with me, so long as everything worked
that'll work
xsenman said:
Your Internal SD card may be corrupted, try to fix that first, try reading this and links in it
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Click to expand...
Click to collapse
hey i have the same problem, i copied the new fstab.aries file to root direction but always when i start up my phone it is replaced by the original file and the switch doesnt works ...
i also have read the threader you give us, but i dont understand what i have to do ...
can you please help me my explaining what i have to do.
i'm sorry my english is not so good and i try my best.
jojo895 said:
hey i have the same problem, i copied the new fstab.aries file to root direction but always when i start up my phone it is replaced by the original file and the switch doesnt works ...
i also have read the threader you give us, but i dont understand what i have to do ...
can you please help me my explaining what i have to do.
i'm sorry my english is not so good and i try my best.
Click to expand...
Click to collapse
look here and you can use the i9000 swap kernels ( depends on ROM) or other methods mentioned in post No. 3, when it does not stick
Check this out! Links to useful Guides and " Banned " Documentaries Merry Christmas everyone
xsenman said:
look here and you can use the i9000 swap kernels ( depends on ROM) or other methods mentioned in post No. 3, when it does not stick
Check this out! Links to useful Guides and " Banned " Documentaries Merry Christmas everyone
Click to expand...
Click to collapse
hey, thank you for the fast answere but when i flash the other kernel or use the methode from post n.3 my smartphone cant boot anymore ...
i use cyanogenmod 10.2 stable version
jojo895 said:
hey, thank you for the fast answere but when i flash the other kernel or use the methode from post n.3 my smartphone cant boot anymore ...
i use cyanogenmod 10.2 stable version
Click to expand...
Click to collapse
I remember reading that for kernel, it works once you flash the Rom again, but did you check Settings >Mackay Settings? Vold methods read Post 1 and Post 2 , here or attach your vold fstab.aries file
Check this out! Links to useful Guides and " Banned " Documentaries
I have another way to fix a corrupted Internal memory at CM11 (KitKat).
My approach is make a symlink (/storage/sdcard0 -> /storage/sdcard1/scard/0) from /etc/init.d script.
After flashing CM11, I have mounted external memory to /storage/sdcard1 and clean folder for internal memory /storage/sdcard0.
We'll be fixing it..
To start, create a directory for "internal memory":
Code:
mkdir /storage/sdcard1/sdcard/0
and create an empty file .nomedia in /storage/sdcard1/sdcard directory:
Code:
touch /storage/sdcard1/sdcard/.nomedia
Then create the /etc/init.d/99intmem file with the contents:
Code:
#!/system/bin/sh
mount -o remount,rw /
rm -r /storage/sdcard0
ln -s /storage/sdcard1/sdcard/0 /storage/sdcard0
mount -o remount,ro /
and make it executable:
Code:
chmod +x /etc/init.d/99intmem
and reboot now!
That's all!
Related
Hi Everyone,
Has anyone gotten A2SD from this thread:
http://forum.xda-developers.com/showthread.php?t=670087
To work on an Aria.
Please let me know.
I would love to know too. I'm tempted to try it, worst case scenario, I have to restore a backup.
It won't work with the stock kernel. Unless you can build a kernel to support it which I do not know how to it will not work for you.
this would be great, thinking of toying around with it myself.
I just go gave it a quick run through to no avail using rom manager to format the sd card into the proper partitions and then flashing the zip file in clock work as directed. I will try it again tomorrow when I'm not so damn tired. Apparently it works on the stock sprint hero 2.1 rom so maybe I'll research more into how that was accomplished as there is no reason this method needs a specialized kernel.
Sent from my HTC Liberty using XDA App
I've been playing with it a little this morning. It appears it is having trouble initializing a mount point in /system/SD. I will try a symlink from /sdcard to a created sir named /syste/SD until I figure out why the userland differs so much from the other ''stock'' 2.1 roms this appears to run on.
Sent from my HTC Liberty using XDA App
It won't work, the stock htc kernel does not support it.
Quit being a naysayer and read the list of stock based roms that support this particular method. There are several app2sd methods and there is no reason this one shouldn't support the stock kernel unlike the cyanogen style methods. I may not be able to do it yet but I defer the possibility of figuring it out to users who may be more skilled than myself rather than regurgitating the same thing over and over without research.
Sent from my HTC Liberty using XDA App
I have a2sd working on attn's liberated_aria b005
step 1: download Rom Manager from the Market
step 2: select partition sd card; select whichever size ext partition you desire (you can also create larger ext partitions doing this manually on a linux box but I won't cover it.
step 3: reboot phone into clockwork recovery; select partitions menu and mount /system.
step 4 (borrowed from Semigon at SmartQ MID forums):
Create a file called install-recovery.sh at <your android SDK installation>/tools/ on your PC with this code (MAKE SURE YOU CAN SAVE IT AS UNIX, ANSI TEXT , I use TextPad to do this [or TextWrangler for OS X] ) :
*
*
Code:
#!/system/bin/sh
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
Step 5:
Plugin your cable and connect your aria to your computer so ready to use ADB
at prompt type:
"adb push install-recovery.sh /system/etc/install-recovery.sh" <-- push file to your aria
"adb shell" <-- shell to your phone.
*
*
Code:
* * #cd /system/etc/
* * #chmod 555 install-recovery.sh* * * * * *
* * #mkdir /system/sd
* * #mount -t ext2 /dev/block/mmcblk0p2 /system/sd* * * * *
* * #mount* * * * * * * *
( if everything is ok, you should see something like this:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0 )
now type #exit
Step 6: Test to make sure that it will be automounted after reboot.
on your PC, from command prompt you can type: "adb reboot"
Step 7: After rebooted, you can either use adb or use "Terminal Emulator" to see if your SD EXT2 partition is mounted.
Connect as in step 1)
On your PC, from command prompt: "adb shell"
# mount
"/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0" means you EXT2 partition is mounted after reboot.
Step 8: download Darktremor Apps2SD 2.7 Update 3r1 and place it at the root of your sd card.
Step 9: boot into recovery and select flash zip from sdcard
Step 10: In flash zip from sdcard, select the a2sd package file you downloaded earlier. Press home to flash; now reboot your phone
Step 11: now reconnect to your phone through adb.
#su
#a2sd install
Don't panic-- your phone will reboot as the script finishes
Step 12: adb back to your phone and type ls -l /data
You should see
lrwxrwxrwx root root 2010-07-27 14:56 app-private -> /system/sd/app-private
lrwxrwxrwx root root 2010-07-27 14:56 app -> /system/sd/app
Now check your phone storage. You should see that you have significantly more available then you did before. If you see it slowly decrease this is because the dalvik cache is still on the internal memory. This too, however, can be moved to the sd.
The following is from tkirton's main set of instructions found at hxxp://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
If you want to move the dalvik-cache to the sd card, type:
a2sd cachesd (move dalvik to sd card)
a2sd cachepart (move dalvik to cache partition)
Now you should have even more internal space left. Enjoy.
Note: moving dalvik to sd card may produce instability in certain apps or force quits. If it isn't working for you just pull up "adb nocache" to move it back to internal storage while still installing apps to the ext partition on your sd card.
Credits to semigod, tkirton and thanks to attn1 (for making good stuff for us)
mosamjc
mosamjc said:
step 1: download Rom Manager from the Market
step 2: select partition sd card; select whichever size ext partition you desire (you can also create larger ext partitions doing this manually on a linux box but I won't cover it.
step 3: reboot phone into clockwork recovery; select partitions menu and mount /system.
step 4 (borrowed from Semigon at SmartQ MID forums):
Create a file called install-recovery.sh at <your android SDK installation>/tools/ on your PC with this code (MAKE SURE YOU CAN SAVE IT AS UNIX, ANSI TEXT , I use TextPad to do this ) :
*
*
Code:
#!/system/bin/sh
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
Step 5:
Plugin your cable and connect your aria to your computer so ready to use ADB
at prompt type:
"adb push install-recovery.sh /system/etc/install-recovery.sh" <-- push file to your SmartQ
"adb shell" <-- shell to your SmartQ. Now you are at your SmartQ shell
*
*
Code:
* * #cd /system/etc/
* * #chmod 555 install-recovery.sh* * * * * *
* * #mkdir /system/sd
* * #mount -t ext2 /dev/block/mmcblk0p2 /system/sd* * * * *
* * #mount* * * * * * * *
( if everything is ok, you should see something like this:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0 )
now type #exit
Step 6: Test to make sure that it will be automounted after reboot.
on your PC, from command prompt you can type: "adb reboot"
Step 7: After rebooted, you can either use adb or use "Terminal Emulator" to see if your SD EXT2 partition is mounted.
Connect as in step 1)
On your PC, from command prompt: "adb shell"
# mount
"/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0" means you EXT2 partition is mounted after reboot.
Step 8: download Darktremor Apps2SD 2.7 Update 3r1 and place it at the root of your sd card.
Step 9: boot into recovery and select flash zip from sdcard
Step 10: In flash zip from sdcard, select the a2sd package file you downloaded earlier. Press home to flash; now reboot your phone
Step 11: now reconnect to your phone through adb.
#su
#a2sd install
Don't panic-- your phone will reboot as the script finishes
Step 12: dab back to your phone and type ls -l /data
You should see
lrwxrwxrwx root root 2010-07-27 14:56 app-private -> /system/sd/app-private
lrwxrwxrwx root root 2010-07-27 14:56 app -> /system/sd/app
Now check your phone storage. You should see that you have significantly more available then you did before. If you see it slowly decrease this is because the dalvik cache is still on the internal memory. This too, however, can be moved to the sd.
The following is from tkirton's main set of instructions found at hxxp://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
If you want to move the dalvik-cache to the sd card, type:
a2sd cachesd (move dalvik to sd card)
a2sd cachepart (move dalvik to cache partition)
Now you should have even more internal space left. Enjoy.
Credits to semigod, tkirton and thanks to attn1 (for making good for us)
mosamjc
Click to expand...
Click to collapse
way to stick to your guns, ill try this later after i return from dinner
Please do. I'd like to know if it works for others as well. I can wait for a fully fleshed cm6 port with all working features (or a legitimate froyo for that matter), but additional space for applications is something that I desperately needed now (and now I do).
mosamjc said:
Please do. I'd like to know if it works for others as well. I can wait for a fully fleshed cm6 port with all working features (or a legitimate froyo for that matter), but additional space for applications is something that I desperately needed now (and now I do).
Click to expand...
Click to collapse
Just so happens this is the same day that CM6 from attn1 came out so i jumped the gun and ended up playing with his alpha Rom. So i have not validated this, BUT I can confirm apps2sd work on Attn1's new rom
Ha. I picked a hell of a day to try get creative. Hopefully it will be of use to someone until the cm6 build gets all its bugs ironed out.
Sent from my HTC Liberty using XDA App
dalvik cache issue
All of this worked fine, except for the dalvik cache part which had an error about not enough space while copying files.
How can moving dalvik cache be undone? It doesn't seem that "adb nocache" is a valid command.
Edit: Oh it should be "a2sd nocache" that seems to have fixed it
Well, I'm glad I have at least one happy customer. The cache transfered over fine for me but caused highly irregular behavior in 90% of the apps that cleared up the second I transfered it back. Could be a permissions issue or simply one that could be solved by reinstalling all your apps into the new sd environment. I'm not terribly concerned as installing the apps on the sd leaves plenty of space free for the caches to do their thing.
I am not very linux or android savy, but I will have to give this a try. It was the only thing missing from the Liberated rom. Now all is well. Thanks!
Hopefully, next we can get a Froyo w/ Sense UI! And our Arias can keep on rocking.
You may try the 2.7.5 RC1 and see if that helps the issue. There were fixes regarding copying files (permission issue...didn't tell it to retain permissions...didn't see that until 2.7.5 PF4A).
Glad to see you guys progressing on this. If someone knows the boot image base address for the Aria, I will modify a stock boot image for apps2sd.
Need any help, feel free to ask me. Any help I can give you to getting this program working on your rom I will be happy to do.
mosamjc said:
Well, I'm glad I have at least one happy customer. The cache transfered over fine for me but caused highly irregular behavior in 90% of the apps that cleared up the second I transfered it back. Could be a permissions issue or simply one that could be solved by reinstalling all your apps into the new sd environment. I'm not terribly concerned as installing the apps on the sd leaves plenty of space free for the caches to do their thing.
Click to expand...
Click to collapse
Here is a slightly modified version, mainly just changed formatting and fixed a few typos. Also my phone didn't automatically reboot after step 11. Thanks for the great guide!
Step 1: Download Rom Manager from the Market
Step 2: Select partition sd card; select whichever size ext partition you desire (you can also create larger ext partitions doing this manually on a linux box but I won't cover it.
Step 3: Reboot phone into clockwork recovery; select partitions menu and mount /system.
Step 4 (borrowed from Semigon at SmartQ MID forums):
Create a file called install-recovery.sh at <your android SDK installation>/tools/ on your PC with this code (MAKE SURE YOU CAN SAVE IT AS UNIX, ANSI TEXT , I use TextPad to do this ) :
Code:
Code:
#!/system/bin/sh
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
Step 5:
Plug in your cable and connect your Aria to your computer so it is ready to use ADB. At prompt type:
Code:
adb push install-recovery.sh /system/etc/install-recovery.sh # push file to your Aria
adb shell # shell to your Aria. Now you are at your Aria shell
Code:
Code:
cd /system/etc/
chmod 555 install-recovery.sh
mkdir /system/sd
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount
If everything is ok, you should see something like this:
Code:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
Now type:
Code:
exit
Step 6: Test to make sure that it will be automounted after reboot. On your PC, from command prompt you can type:
Code:
adb reboot
Step 7: After rebooting, you can either use adb or use "Terminal Emulator" to see if your SD EXT2 partition is mounted.
Connect as in step 1)
On your PC, from command prompt:
Code:
adb shell
mount
If your EXT2 partition has been mounted after reboot you will see:
Code:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
Step 8: Download Darktremor Apps2SD 2.7 Update 3r1 and place it in the root of your sd card.
Step 9: Boot into recovery and select "install zip from sdcard"
Step 10: Select the a2sd package file you downloaded earlier. Press power button to flash; now reboot your phone
Step 11: Now reconnect to your phone through adb:
Code:
adb shell
su
a2sd install
Don't panic-- your phone may reboot as the script finishes
Step 12: Connect with adb back to your phone:
Code:
adb shell
Then type:
Code:
ls -l /data
You should see
Code:
lrwxrwxrwx root root 2010-07-27 14:56 app-private -> /system/sd/app-private
lrwxrwxrwx root root 2010-07-27 14:56 app -> /system/sd/app
Now check your phone storage. You should see that you have significantly more available then you did before. If you see it slowly decrease this is because the dalvik cache is still on the internal memory. This too, however, can be moved to the sd.
The following is from tkirton's main set of instructions found at hxxp://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
If you want to move the dalvik-cache to the sd card, type:
Code:
a2sd cachesd # move dalvik to sd card
a2sd cachepart # move dalvik to cache partition
Now you should have even more internal space left. Enjoy.
Note: moving dalvik to sd card may produce instability in certain app or force quits. If it isn't working for you then move it back to internal storage while still installing apps to the ext partition on your sd card with:
Code:
a2sd nocache
Credits to semigod, tkirton and thanks to attn1 (for making good for us)
mosamjc
Click to expand...
Click to collapse
mosamjc said:
Well, I'm glad I have at least one happy customer. The cache transfered over fine for me but caused highly irregular behavior in 90% of the apps that cleared up the second I transfered it back. Could be a permissions issue or simply one that could be solved by reinstalling all your apps into the new sd environment. I'm not terribly concerned as installing the apps on the sd leaves plenty of space free for the caches to do their thing.
Click to expand...
Click to collapse
Sounds very similar to what happened for me. The script completed even with a few copy errors, but then many applications had FC after reboot. There is more than enough space from moving the apps, so it was not a big problem.
tkirton said:
You may try the 2.7.5 RC1 and see if that helps the issue. There were fixes regarding copying files (permission issue...didn't tell it to retain permissions...didn't see that until 2.7.5 PF4A).
Glad to see you guys progressing on this. If someone knows the boot image base address for the Aria, I will modify a stock boot image for apps2sd.
Need any help, feel free to ask me. Any help I can give you to getting this program working on your rom I will be happy to do.
Click to expand...
Click to collapse
Will give the the newer version a try, by installing the new zip then running the cachesd and cachepart commands again. Thanks!
@MikeChelen Way to polish the tutorial. Looking good! I hammered that out in in only a few minutes originally after pulling together all the parts that made it tick for me. I just wanted to release it to the masses quickly to prove jznomoney wrong (am I a bad sport? Probably).
@Tkirton I will give the new version a go after lunch and see what happens. As far as the boot image address, I believe it is the same as the Legend, as almost all legend roms flash and boot successfully on the Aria. So I would give 0x12c00000 a try on Attn1's Liberated_Aria.
mosamjc said:
@MikeChelen Way to polish the tutorial. Looking good! I hammered that out in in only a few minutes originally after pulling together all the parts that made it tick for me. I just wanted to release it to the masses quickly to prove jznomoney wrong (am I a bad sport? Probably).
@Tkirton I will give the new version a go after lunch and see what happens. As far as the boot image address, I believe it is the same as the Legend, as almost all legend roms flash and boot successfully on the Aria. So I would give 0x12c00000 a try on Attn1's Liberated_Aria.
Click to expand...
Click to collapse
Haha, well I am glad you did! It meant the guide was available for me a little sooner. Score another point for stubborn resolve
It was more than clear enough for me to follow, hopefully the edits will help newer users though.
It might also be worth noting that ANSI is not an encoding itself, but a set of encodings? The normal Linux text editors seem to use US-ASCII or UTF-8 and these should probably both work.
Assuming other users don't have any problems, hope this gets added to the Aria sticky topic ^_^
Thanks again everyone!
App2SD Optimus
Use At Your Own Risk !!
Tutorial version by mohicanrat and App2SD file from joe.stone
Risk :
* Lost Your Memory Card
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Follow The Instruction Below to get App2SD in your LG optimus
Requirements :
* Rooted
* Superuser
* Android 2.1 Eclair
Click to expand...
Click to collapse
How To Do It :
1. Before Install app2sd. Don't forget is partition your sd card. use paragon partition manager portable (u can look everywhere)
2. Release your microSD card from the phone and insert into card reader on the Computer
3. Backup all of the data in microSD card
4. Open The paragon manager and choose Partition Manager 9.0
5. After partition manager 9.0 Opened, find the HDD diagram below and locate the picture diagrams to sdcard. (Be careful, which is a diagram on select microSD card)
6. Delete partition and create another partition like this :
* First Partition is 70% of The Size of microSD card And The Filesystem is FAT32
* Second Partition is 25% of The Size of microSD card And The Filesystem is linux ext2
* Third, create a new partition in the same place and same way but the file type is swap.
Click to expand...
Click to collapse
After it successfully Partitioning your microSD its mean your microSD cannot readed by the Computer/Windows. But don't worry, just insert the card into your phone and it can be readed again.
The next is to follow the step below to app2sd:
1.Download the file here app2sd_new
2.Extract zip file it and produces 3 folders.
3.Copy all folders to the SDCard. (Remember its three folders directly copied to SDCard)
4.OpenAndroid Market, and download application called GScript.
5.After GScript finish downloaded, open the application GScript in you Optimus
6.in GScript, click the Menu button on the phone, then select Add Script
7.Click Load File button and select the file on top, namely app2sd.sh
8. after the scripts GScript appear in the application, then push the Save button.
9.so you will see the name of the save and script was added in the list GScript.
10. Repeat step 6 until all the script was loaded in GScript.
11. if those all the step are finished, now is the time to do Optimus app2sd.
12.in existing scripts in Application GScript, choose a distinguished name a2sd_data and wait until the script execute and complete. (if finished script back to the List2 view more)
13. Turn off the HP and restart.
14. after HP flame back, Please to the settings menu hp, sdcard & phone storage agan, how tough the internal phone storage ?
Click to expand...
Click to collapse
Enjoy
this source app2sd have a bug. please change a source app2sd.
mohicanrat said:
this source app2sd have a bug. please change a source app2sd.
Click to expand...
Click to collapse
yes i have post the fixed one
Nice simple tut.
There is a simpler one-click auto install method, but I guess this is simple enough too
sorry for bad english
after my phone restart, it dont see sdcard, "unavailable", and it cant be seen on my computer too. I want to re-flash my phone but USB debugging not working. I ticked up it already, but my computer cant see it, I had tried factory reset but nothing happen.Does anyone can repair it?
this is my tutorial. all ....
please put my name in this tutor.
mohicanrat said:
this is my tutorial. all ....
please put my name in this tutor.
Click to expand...
Click to collapse
you make the indonesian and i make the english one
wtf?
if you copy tutor from someone, please put author name. this is a ethic.
hmms
mohicanrat said:
wtf?
if you copy tutor from someone, please put author name. this is a ethic.
Click to expand...
Click to collapse
idd, thanks for the english version but mohicanrat is right, u have to add the original source, thats rule nr 1.
if i need to do a school project and rip it from for example an indonesian person, and translate it to english, and say its mine. I would get a 0 and get banned from university....
(just to make a point)
your image says follow the rules, etc ,etc ,etc, RESPECT OTHER MEMBERS,
khakha258 said:
sorry for bad english
after my phone restart, it dont see sdcard, "unavailable", and it cant be seen on my computer too. I want to re-flash my phone but USB debugging not working. I ticked up it already, but my computer cant see it, I had tried factory reset but nothing happen.Does anyone can repair it?
Click to expand...
Click to collapse
u try to reflash your phone with firmware 2.1 of GT540 (France ). Next,Hardreset your phone and flash phone again with firmware (Baltic).It was successful with me.
Hope it is useful with you
Hello!
I want to ask the author of the post.
And from what considerations you used to mount mtdblock4?
I apologize for my English.
ehhm...
dont get this part
The next is to follow the step below to app2sd:
1. Download The App2SD File From here :
h*tp://www.mediafire.com/file/ih0dyjy4bxy5m9m/app2sdgt540_2_1.en_.zip
2. Install Via Adb Shell, and type like this :
- Adb shell
- Su (when the superuser appear, click allow)
- Sh /sdcard/app2sd/app2sd.sh
3. Wait till it restart itself
Enjoy
you download the stuff the app2sd folder where to place it lol
RDilus said:
ehhm...
dont get this part
The next is to follow the step below to app2sd:
1. Download The App2SD File From here :
h*tp://www.mediafire.com/file/ih0dyjy4bxy5m9m/app2sdgt540_2_1.en_.zip
2. Install Via Adb Shell, and type like this :
- Adb shell
- Su (when the superuser appear, click allow)
- Sh /sdcard/app2sd/app2sd.sh
3. Wait till it restart itself
Enjoy
you download the stuff the app2sd folder where to place it lol
Click to expand...
Click to collapse
Place The APP2sd Folder to the root of the MicroSD
When I typed
Sh /sdcard/app2sd/app2sd.sh
I get - not found. Then I seach in google and typed another code:
# sh /sdcard/gscript/a2sd.sh
sh /sdcard/gscript/a2sd.sh
mount: No such file or directory
/sdcard/gscript/a2sd.sh: cannot create /system/bin/busybox: read-only file system
: not found
failed.
: not found
mkdir failed for /system/sdcard, Read-only file system
: not found
mount: No such file or directory
/sdcard/gscript/a2sd.sh: 22: Syntax error: end of file unexpected (expecting "th
en")
Now I get read-only file system. How to fix it?
Thank you
gdavidkov said:
When I typed
Sh /sdcard/app2sd/app2sd.sh
I get - not found. Then I seach in google and typed another code:
# sh /sdcard/gscript/a2sd.sh
sh /sdcard/gscript/a2sd.sh
mount: No such file or directory
/sdcard/gscript/a2sd.sh: cannot create /system/bin/busybox: read-only file system
: not found
failed.
: not found
mkdir failed for /system/sdcard, Read-only file system
: not found
mount: No such file or directory
/sdcard/gscript/a2sd.sh: 22: Syntax error: end of file unexpected (expecting "th
en")
Now I get read-only file system. How to fix it?
Thank you
Click to expand...
Click to collapse
first: your phone must by rooted
second: connect your phone to PC withe USB debug mod, make "adb shell" command, make "su" command, confirm access on your phone... enjoy.
TheGiga said:
Place The APP2sd Folder to the root of the MicroSD
Click to expand...
Click to collapse
something else...
app2sd.sh is in gscript folder why is that?
write a proper guide or fix the files pls
I have no luck then tried run this from adb.. But when I used gscrit to run a2sd.sh everithing go fine.. Thank you.
Sent from my GT540 using XDA App
Is there any way to do this without using PC and card reader?
Cuz I unfortunatly have a desktop PC. not a laptop, and I dont have card reader.
ok i tried alot of times but this isnt just working everytime same damn errors
not a good tut
seirous fix the files!
did u ever get it fixed??
ALL TWEAKS AND MOD FOR E405 WILL BE ADDED HERE TIME TO TIME
SO PLEASE SUBSCRIBE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
all these mods are tested by me and/or others. still if any of them bricked ur phone, that will be only ur fault. test or use any of them at ur own risk.
Rooting-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Working-tested by me.
PLEASE CHARGE YOUR PHONE AT LEAST 60% BEFORE DOING THIS
No. of steps-10
1. Download and install LG United Drivers From Official Site
Link-http://www.lg.com/in/support-mobile/lg-E405
(see pic to know what to download)
2. Download SuperOneClickv1.7-ShortFuse.zip
Link-http://www.mediafire.com/?6f1sttgi1rc1q72
3. Disable your antivirus as it can block or can delete any file without your permission between the completion of whole process leaving you a soft bricked phone. SuperOneClick will run an exploit, your antivirus can show it as a virus or infection but after the process you can do a full system scan and there will be no virus in your system.
4.Extract SuperOneClick to desktop or any drive.
5. Connect your device to PC through data cable and connect in PC Software Mode.
6. Now go to Settings-> Applications-> Development-> Enable USB Debugging (in your phone)
7. Go to the folder where you have extracted SuperOneClick and run SuperOneClick.exe (see pic) (1)
8. Now select rageagainstthecage (2) as you can see in the pic and click on ROOT (3).
9. Wait for a while till you can see rooted and it will ask you to run a superuser command, say yes or no its up to you. yes is preferred.
10. Close SuperOneClick, Disconnect your Device. You can see a new app in there 'Super User', run it. If it starts.
Congrats, you are rooted but if it get force closed, then just connect device with usb debug enable and run superoneclick again with rageagainstthecage as mentioned above, this time you'l be rooted.
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
My Work:
Mods For Lg L3 E405 Dual
Micromax Canvas Music Kernel Development Thread
How to mod lewa os PIM.apk (sms)
Multi Boot MTK Devices
Custom recoveries for Canvas Music A88 and Canvas 2 A110
Micromax Canvas Music Custom Rom's Patches
MT6577 Auto Focus Fix
CWM Recovery
Credits to dansh for build the first version of CWM Recovery for E405, all below versons are mine with changes
(See video tutorial if having any problem, links below)
1. Download terminal emulator from given links and install it to your E405.
(google play)-https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
(apk)-http://www.papktop.com/android-terminal-emulator-1-0-32.html
2. Download the Recovery file from the link.
CWM (normal version for user's not using link2sd and 3 partition system)
http://www.4shared.com/file/PSf8-KOF/cwmrecovery.html?
Stock Recovery
http://www.4shared.com/file/V0-hm93J/recoverystock.html?
3. Connect your E405 to pc in mass storage mode and move/copy 'cwmrecovery.img' to Internal SD (1GB)
4. Run the Terminal Emulator (see video tutorial for ease, links below)
Now, type the following commands-
after $ type
su (press enter) (terminal'll ask for superuser permission, grant it)
you'll see this
#
now type after #
dd(single space here)if=/sdcard/cwmrecovery.img(single space here)of=/dev/block/mmcblk0p17 (press enter)
above command should look like this in terminal-
$ su
# dd if=/sdcard/cwmrecovery.img of=/dev/block/mmcblk0p17
you'll see 'some records in some records out etc etc'
press the back soft-key to exit the terminal.
you can use 'recoverystock.img' by just replacing 'cwmrecovery.img' in all commands.
You can reboot to recovery by pressing and holding volume up (or down, hard reset gone, you can use recovery to reset your phone now) when the device is powering on.
See the images to know how to make a back up using CWM Recovery.
Videos-
Old Recovery Wroking-
http://www.youtube.com/watch?v=y7vckwBHWyY&feature=youtu.be
VIDEO TUTORIAL-
http://www.youtube.com/watch?v=8r8YpHQJTeo&feature=youtu.be
UPDATE:
New CWM Recovery for link2sd and 3 partition system users.
Flash using old CWM Recovery and reboot to recovery.
http://www.mediafire.com/?s1bgcmf80a87xbd
Features of link2sd version-
This will mount and backup in third partition of ur sd card instead of first
1st-fat (smallest size) <--------- Previous recovery backup and mount location
2nd-EXT4/3/2 1gb
3rd-Fat32 (rest of the space) <--------- this recovery mount and backup in this partition.
this version will make backup of
system, data, cache, recovery, boot and also .android-secure
Another version is under testing
Features-
will backup sd-ext (all apps linked by link2sd)
wipe option added for sd-ext
complete backup of the phone (nothing left)
test backup was of size 1.5 gb
will be out soon.
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
Link2SD
1. Download and install Link2D from any given link.
2. Root your phone (if not rooted) (guide is previously posted on the page).
3. Download a Partition manager (Link given).
4. Insert your card in card reader and back up all your files to the computer because partitioning will wipe your data.
5. Open Mini Tool (partition manager's name) in your computer. Locate your SD card (be careful in choosing and make sure not to choose the drive of your computer).
6. Right click and choose Delete.
7. Again Right click and create a FAT (not fat32) PRIMARY partition and choose the smallest size possible.
8. Then create a EXT2 PRIMARY partition of 1 GB (not bigger) which will be used with Link2SD.
9. Create a FAT32 partition for the remaining space left on the SD card, by the same way you created EXT2.
10. Click the “Apply” button on the top left corner and wait for it to finish the process. Done.
11. Put back your SD card to your phone and switch it on.
12. Open Link2sd. You will be prompted to choose between ext2, ext3, ext4 and FAT32. Select ext2. (ext4 is also working in my case, try if working for u)
13. It will say mount script created. Reboot your phone now.
14. Open link2sd and if the message doesn’t show up, you succeded.
15. Go to Link2sd>Settings>check the autolink (to automatically move apps upon installation) (Optional).
16. If you already have some apps, select “move to phone” then after moving select “Create Link” (be sure to check the three files: app, dalvic-cache and library files).
Links:-
Partition manager- http://download.cnet.com/MiniTool-Partition-Wizard-Home-Edition/3000-2094_4-10962200.html
Link2SD (google play)- https://play.google.com/store/apps/details?id=com.buak.Link2SD
Link2SD (APK)- http://dl.apktops.com/app/201208/Link2SD_2.2.1.apk
Note: EXT2 is old, EXT4 is the fastest among 3 (EXT2,EXT3,EXT4) but not compatible in all ROMS and often requires kernel that supports EXT4.
So you can/should try all of them and keep the best one that works with your rom.
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
Move All Existing Apps to the SD Card (internal sd) WITHOUT ROOTING
NOTE:don't move launchers, widgets and all the apps that you want to keep running when your phone is mounted or when you just switched it on, till external memory prepares. u can not use widgets if the are moved to sd
Tools required-
1. Drivers of your phone
2. Oracle’s Java JDK
3. Android SDk
# As in this tutorial, you have to connect your phone to pc in ‘pc software’ mode, so you have to install all the drivers in your pc, required by your phone. Look on official site of your phone to download the drivers or search for a cd/memory card in the phone box.
For LG Drivers, download and install in pc from here (around 10mb file, see image to know what to download)
Link-http://www.lg.com/in/support-mobile/lg-E405
(see bottom half of the image to know what to download)
1. Enable USB Debugging
Open the Settings screen, tap Applications, and select Development.
Tap the USB Debugging checkbox to enable it.
You may want to disable debug mode after completing this process.
#if USB Debug is grayed and u are not able to tick it, just in case, then plug your device to pc via data cable and connect in 'pc software' mode. now go to above said location in you phone and enable usb debug now.
# (If you don’t already have Oracle’s Java JDK installed on your computer, you’ll have to download and install it before installing the Android SDK ie mentioned in next step)
link for Oracle’s Java JDK-http://www.oracle.com/technetwork/java/javase/downloads/jdk7u9-downloads-1859576.html
(check " Accept License Agreemen" and click "jdk-7u9-windows-i586.exe" on this page)
2. Install the Android SDK
link-http://developer.android.com/sdk/index.html
(click "Download the SDK for Windows")
#note the path of installation, you'll need it later OR change the location of android sdk to a simpler path like root directory (C: or D: etc) for ease.
3. After you’ve installed both, JDK first and then Android SDK,
launch the SDK Manager from your Start menu.
Click on Start-> All Programs-> Android SDK Tools-> SDK Manager
Android SDK will open.
4. Now uncheck all check boxes (if checked by default) and select "Android SDK Platform-tools" and click the Install button to download and install it.
5. After the process completes, connect your Android device to your computer with USB cable (if not connected in step 1 or removed after it, you may have to enable usb debug again, plz refer to step 1 now).
Windows should locate the device and install the appropriate drivers automatically. If it doesn’t, you may have to download and install the appropriate drivers from your Android device’s manufacturer. Do not mount the device after connecting it – just plug it in. Use "PC Software" instead.
6. Open a Windows Explorer window and navigate to the android-sdk\platform-tools folder.
On x64 Windows, you’ll find this folder at C:\Program Files (x86)\Android\android-sdk\platform-tools by default.
Check C:\Program Files\Android\android-sdk\platform-tools if you’re using a 32-bit version of Windows.
#This will be the path where you have Android SDK in step 2.
i've told u to note it.
now plz look where u've installed it.
7. Launch a Command Prompt window (CMD) in this folder.
For this, press and hold shift key, right or left shift doesn't matters
right click anywhere (holding the shift) in empty space and select "Open command window here".
CMD will open.
8. Now type "adb devices" and press Enter.
You should see your connected Android device.
9. Now at last, type the following and press enter to set the default install location to your SD card:
ALL THE COMMANDS ARE CASE SENSITIVE
adb shell pm setInstallLocation 2
If you want to revert this change later and install apps to the internal storage by default, run this command:
adb shell pm setInstallLocation 0
code meanings-
0-auto
1-internal storage
2-external storage
(optional)
to know where the apps will be stored now run the following command
adb shell pm getInstallLocation
the result will be 2, ie external storage.
10. Now close CMD, disconnect your Device and start moving apps to sd without root
In you device, open the Settings screen, tap Applications, and select Manage Applications. Select the app you want to move and tap the Move button on its details screen.
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
UNBRICK YOUR LG OPTIMUS L3 E405 and E400 WITH KDZ UPDATER
No. of steps-15
LET THE PHONE CHARGE OR AN HOUR OR TWO OR MORE
DISABLE YOUR ANTIVIRUS TEMPORARILY
1. Download LG Optimus L3 USB Driver
2. Download LG Optimus L3 stock firmware/rom from the page given at the end. (according to your network provider and country)
3. Download and extract KDZ updater on desktop or in any directory.
4. Install Microsoft XML parser (by running msxml.msi in the extracted folder)
5. Restart your computer.
6. Now, switch off your phone (ignore this, as assumed you can't even switch it on kidding)
7. Remove the battery and reinsert it. Press and hold Volume Up button and Volume Down button together. While you are pressing both buttons, press the Power/Lock button. DON'T LEAVE VOLUME UP DOWN BUTTONS TILL YOU GET TO EMERGENCY MODE (yellow screen with Emergency mode written on it). ALSO DON'T REMOVE THE BATTERY ONCE YOU REACHED EMERGENCY MODE.
8. Connect your phone to the computer via the USB Cable.
9. Run KDZ updater as Administrator.
10. Choose the following options in KDZ Updater (also see image):
Type: 3GQCT
Phone Mode: DIAG
KDZ file is the one you downloaded in step 2
CHOOSE CORRECT OPTIONS & RECHECK THEM TWICE OR THRICE!!
(these settings are for l3 only don't try on any other random phone)
11. Click 'Launch Software Update' and pray to god.
12. Go for a walk or talk to the mirror as it will take a while for the rom to be flashed.
13. At last you will se 'Finished'. Your phone will be switched off, switch it on normally. (or it can restart by itself, wait for about half minute before trying to switch it on)
14. It will take more time in switching on once, after that you can use it normally.
15. It is preferable to do a hard reset after flashing by this method.
LG Optimus L3 USB Driver
Link-http://www.lg.com/in/support-mobile/lg-E405
LG Optimus L3 stock firmware/rom
Link-http://lg/-phone-firmware.com/index.php?id_mod=11
KDZ updater
Link-http://www.unclenet.de/files/KDZ_FW_UPD_EN.7z
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
How to use game gardian
Wanna cheat in any game???
download game gardian and follow the instructions (pics)
apk:
http://www.mediafire.com/?lumaz3036caain0
mirror:
http://www.mediafire.com/?sdh57bfv9krk559
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
MOUNT LINK2SD PARTITION (i.e. EXT PARTITION) AS SYSTEM MEMORY (i.e. 157 mb default)
this is for the partition structure created to use with link2sd (ie fat, ext, fat32)
REMOVE ALL SCRIPTS U ARE USING TO MOUNT EXT PARTITION AND MAKE A TITANIUM BACKUP OF ALL APPS
FLASH THE ATTACHED BOOTINT.IMG USING CWM (DO A NANDROID BACKUP FIRST AND RESTORE DATA ONLY AFTER FLASHING)
OR
extract init.rc of boot.img and edit it. (for extracting u need Cygwin for windows and dsixda-Android-Kitchen or kernel kitchen, google about them)
do the following in init.rc
1. search 'on fs'
on fs
comment out 'mount yaffs2 [email protected] /data nosuid nodev' with #
like this
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 [email protected] /system
#mount yaffs2 [email protected] /system ro remount
#mount yaffs2 [email protected] /data nosuid nodev
mount yaffs2 [email protected] /persist nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
mount yaffs2 [email protected] /persist nosuid nodev
now on 'on emmc-fs'
replace
wait /dev/block/mmcblk0p21
exec /system/bin/demigod_make_ext4fs -l 160M /dev/block/mmcblk0p21 /data
exec /system/bin/e2fsck -y /dev/block/mmcblk0p21
mount ext4 /dev/block/mmcblk0p21 /data nosuid nodev noatime barrier=1 data=ordered noauto_da_alloc errors=continue
with
wait /dev/block/mmcblk1p2
wait /dev/block/mmcblk1p2
wait /dev/block/mmcblk1p2
exec /system/bin/demigod_make_ext4fs -e /dev/block/mmcblk1p2 /data
exec /system/bin/e2fsck -y /dev/block/mmcblk1p2
mount ext4 /dev/block/mmcblk1p2 /data nosuid nodev noatime barrier=1 data=ordered noauto_da_alloc errors=continue
save it
pack the boot.img and flash it using cwm
if u have any cwm flashable package with u then extract 'META-INF>com>google>android>updater-script' and edit it with notepad++
delete everithing it it and paste this
run_program("/sbin/busybox", "mount", "/system");
package_extract_file("boot.img", "/tmp/boot.img");
assert(run_program("/system/bin/dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk0p9")=="0");
run_program("/sbin/busybox", "umount", "/system");
save it and drag and drop it to it's location, i.e. 'META-INF>com>google>android> here'
now drag and drop boot.img in the zip (no folder, the zip itself)
make a nandroid backup and flash this.
now, advance restore ONLY data using cwm recovery and reboot
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
MOUNT EXTERNALSD AS INTERNALSD
THIS MOD IS UNDER TESTING, PLEASE DON'T REPORT BUGS
edit init.rc and do search this
#exec /system/bin/resize2fs /dev/block/mmcblk0p20
now remove all # from
# [START] LGE_USE_INTERNAL_FAT
#wait /dev/block/mmcblk0p20
#exec /system/bin/resize2fs /dev/block/mmcblk0p20
#exec /system/bin/e2fsck -y /dev/block/mmcblk0p20
#mount vfat /dev/block/mmcblk0p20 /mnt/sdcard
# [END] LGE_USE_INTERNAL_FAT
to make it like to like like this
# [START] LGE_USE_INTERNAL_FAT
wait /dev/block/mmcblk1p3
exec /system/bin/resize2fs /dev/block/mmcblk1p3
exec /system/bin/e2fsck -y /dev/block/mmcblk1p3
mount vfat /dev/block/mmcblk1p3 /mnt/sdcard
# [END] LGE_USE_INTERNAL_FAT
add this above "mount vfat /dev/block/mmcblk1p3 /mnt/sdcard" if not mounting
unmount /dev/block/mmcblk0p20
OR FLASH THE ZIP
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
ICS THEME FOR STOCK ROM (see images)
THIS IS FOR TESTING ONLY. IF WORKING, PLEASE COMMENT. THEN I'LL UPDATE THE THEME WITH MORE THEMED APP (only UI is themed in this version)
Flashing this is simple as 1, 2 and 3.
1. download and move/copy both zips to internal/external sd card
2. reboot to recovery and make a nandroid backup.
3. flash "1.zip" (from where u've placed it in step 1)
4. reboot.
if there is no bootloops and the phone starts up normally the proceed, otherwise restore cwm backup from recovery.
5. reboot to recovery and flash "2.zip"
6. reboot.
Enjoy
Zips:-
http://www.mediafire.com/?s5jv658c6ujoj4x
http://www.mediafire.com/?a5nr8m75k453ars
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
thanks mate .
this is exact what I want!
needs to test some of them
there is one question
are you done all this things on your lg e 405 dual sim and is your phone work still normally? )
and is there any bug after rooting the phone I means some ppl says get buged in wifi or something like that...
thanks
x625 said:
thanks mate .
this is exact what I want!
needs to test some of them
there is one question
are you done all this things on your lg e 405 dual sim and is your phone work still normally? )
and is there any bug after rooting the phone I means some ppl says get buged in wifi or something like that...
thanks
Click to expand...
Click to collapse
i've tested all of them and rotting doesn't caused any bug in my case.
Im very glad to see you support here .
I newly bought a L3 E405 dual and had some trouble with it.
1)
firstly I must thank you for your rooting method (post #1) it worked for me and I my biggest problem solved.. millions of thanks to you my bro.
2)
But after a wile I encountered another major trouble . the phone extremely rapidly get fulled (internal system usable memory is only 157 mb!!! wtf!
although i have bought and installed an external sd card it is completely useless and even using app2sd apps on market many apps leave half of size on system memory some other apps dont support app2sd feat. and in result after installing 10-15 little routine apps (not games just needed essential apps) the phone get notification of low size and hangs and stop wifi and ... I installed external sd card on this phone but it is completely useless coz even app2sd moved apps take size on internal sd card not external!!! why !!!
now how could I overcome this problem with best and simple revertable steps? I know you posted some solution before but I want to know which method you personally recommend duo to you said some method still in test mod and im noob in android & adb & programming and dont want to breik my phone.
my phone has 2 year exchanging guaranty and dont want to void it i Know I already voided it because successfully rooted it with your method before but i think I can unroot it with that button on superoneclick software again.
3)
I only rooted my phone but still having fear to instal CWM on it . is that ok also to install CWM also? I just have low system memory problem and dont want any tweaks on my phone if they aren't necessary for it. my other season of fear is I didnt find my installed firmware county code . my phone is on V10G version sw but there are many E405 V10G firmware in here I dont know which is mine . and my living country in not listed there ( how could i find my firmware locale on my E405??
and more Q
what is the difference & benefit and advantages of link2sd over app2sd apps? I mean why we must use complicated steps of link2sd (partitioning & needs roots and ... when there is simple app2sd feat of our native android phone enhanced with app2sd apps on market? I dont got that ??
in your post #7 line #3 you said :
FLASH THE ATTACHED BOOTINT.IMG
and in end of post #8 you said:
OR FLASH THE ZIP
I cant see any attached ZiP files on that posts where could I find them?
in recovery mod tweak post you said you are preparing another new version of recovery soon . is there any new news ? i m so exited approximate date of release
thank you so so much for your helps
U already helped me so much for rooting my phone
million million tanks!!
and sory for such long story
x625 said:
Im very glad to see you support here .
I newly bought a L3 E405 dual and had some trouble with it.
1)
firstly I must thank you for your rooting method (post #1) it worked for me and I my biggest problem solved.. millions of thanks to you my bro.
2)
But after a wile I encountered another major trouble . the phone extremely rapidly get fulled (internal system usable memory is only 157 mb!!! wtf!
although i have bought and installed an external sd card it is completely useless and even using app2sd apps on market many apps leave half of size on system memory some other apps dont support app2sd feat. and in result after installing 10-15 little routine apps (not games just needed essential apps) the phone get notification of low size and hangs and stop wifi and ... I installed external sd card on this phone but it is completely useless coz even app2sd moved apps take size on internal sd card not external!!! why !!!
now how could I overcome this problem with best and simple revertable steps? I know you posted some solution before but I want to know which method you personally recommend duo to you said some method still in test mod and im noob in android & adb & programming and dont want to breik my phone.
my phone has 2 year exchanging guaranty and dont want to void it i Know I already voided it because successfully rooted it with your method before but i think I can unroot it with that button on superoneclick software again.
3)
I only rooted my phone but still having fear to instal CWM on it . is that ok also to install CWM also? I just have low system memory problem and dont want any tweaks on my phone if they aren't necessary for it. my other season of fear is I didnt find my installed firmware county code . my phone is on V10G version sw but there are many E405 V10G firmware in here I dont know which is mine . and my living country in not listed there ( how could i find my firmware locale on my E405??
and more Q
what is the difference & benefit and advantages of link2sd over app2sd apps? I mean why we must use complicated steps of link2sd (partitioning & needs roots and ... when there is simple app2sd feat of our native android phone enhanced with app2sd apps on market? I dont got that ??
in your post #7 line #3 you said :
FLASH THE ATTACHED BOOTINT.IMG
and in end of post #8 you said:
OR FLASH THE ZIP
I cant see any attached ZiP files on that posts where could I find them?
in recovery mod tweak post you said you are preparing another new version of recovery soon . is there any new news ? i m so exited approximate date of release
thank you so so much for your helps
U already helped me so much for rooting my phone
million million tanks!!
and sory for such long story
Click to expand...
Click to collapse
u can use lik2sd as you are not much familiar with android. i'll recommend to mount a EXT4 partition as your /data as this is better than link2sd (my personal opinion) but link2sd is fine and simple. and mounting EXT4 as /data will also give you large space for application's data also, which is not possible with link2sd. try using link2sd, you'll get to know what i am talking about.
which country do you belong?
CWM is must. as in any case, if you are unable to boot your phone than there is only kdz method to recovery, other then restoring CWM backup. and cwm backup restoration is much easier, better and safe than using kdz. also for flashing/installing .zip, you'll need CWM Recovery.
in any case you want to go back to stock recovery, u r free to do so.
app2sd will only move your apps to internal sd but link2sd will link them on your external sd. in app2sd apps will take a small amount of storage of your system memory while in link2sd only data will remain in system memory.
sorry about the zips. zips of recovery and boot are ready and uploaded on mediafire and on my blog, will add them here if few days.
thanks for quick reply.
you helped me a lot.
idont know how to appriciate you.
I done it (link2sd tweak) . I created ext2 partition on sd with pc partition manager (step1). and then on my phone I run link2sd app and run ext2 scrip (step2). and worked good.
you mentioned I can also use ext4. you meanthat I replace any ext2 with ext4 format in step1 or step 2 only ?? or in both steps must use ext4 choice??
and what is the pros and cons of using ext4 instead of normal ext2 . and is the stock kernel support this format officially?
Im on 2.3.6 with build number GRK39F sofware version V10g 15 nov -2012 . and my country is IRAN .and my phone firmware handle persian (farsi) languge characters (not only arabic) in menu and keyboard and dont want too loose that after update or installing new firmware for this reson I need to find my own phone firmware version but in lg-phone-firmware.com there is no any iran country ?
could you please tell me what is the exact step by step method of reinstalling stock firmware after I mesed up somethig ? you said it is better and safer flash firmware with CWM but i dont know how do that . is that possible to explain more this TWO different ways separately (kdz way and recovery way) . thank a lot .
yes stock kernel support EXT4, you can replace EXT4 in every step your've done with EXT2.
how to flash kdz has been already posted. and for cwm recovery. once you are in cwm recovery, you can see backup and restore. select it to backup to external or internal sd, similarly, use it to restore an old backup.
you can make a backup of current rom, can do anything you want and if anything wrong happens, just restore your backup.
Wow!
Finally i have done it?
Now i have cwm with supported backup to external sd. + link2sd with ext4 . script.
You are my hero sudeep!
Now im waiting for more and more SIMPLE FLASHABE tweaks from you not just working with terminal command.
Maye be you release your final version of your custom rom !!
Anyway i always checks this topic and thanks so so much to you
Sent from my LG-E405 using Tapatalk 2
Another good tweak for gaming
Try using Chainfire3D (Gingerbread)....It improves GPU a lot
Best Regards
Has anyone heard of any other tweaks improving L3 performance on CM9?
Will Chainfire 3D be working on ICS ?
nice
i've rooted my phone like in thread, and i can use apps that needs root perms (like link2sd)
but when i use Android Commander, i get Root Acess: NO
what to do?
Alright.. I wanted the Note 8 version of gallery and i went into system/app folder and deleted the SecGallery2_Galaxy.apk but before deleting i saw that its size was 0.00 kb lol ..
But when i tried tried to copy and pasted in the extsd it pasted and showed 13mb..
Now i deleted the file and copied the Note 8 Galley and pasted in the system/app folder only to get an error " Operation failed " and i realized only 7 mb free space is there in the partition by going into the android emulator!
Now i also found out that, full size SecGallery2_Galaxy.apk was in the preload partition and i instead of replacing that i deleted the file in system/app..
Now how do i get back that file in system/app?.. is that what they call deodexed file?.. Please help..
Thanks a lot in advance
Just copy it from other rom, that You can explore with winrar.
Sent from galaxy n7105
The actual apk was in preload and was symlinked to system partition. Thats why it showed 0 KB in system.
You can get it back by typing in shell
Code:
$ su
# ln -s "Path of apk in preload" /system/app/
And this is not called deodexing.
nokiamodeln91 said:
The actual apk was in preload and was symlinked to system partition. Thats why it showed 0 KB in system.
You can get it back by typing in shell
Code:
$ su
# ln -s "Path of apk in preload" /system/app/
And this is not called deodexing.
Click to expand...
Click to collapse
Thanks but i dont know the path.. the name of the file is SecGallery2_Galaxy.apk, so whats the path of the file?..
can u please type and show?..
Thanks in advance
CustomRomAddicts said:
Thanks but i dont know the path.. the name of the file is SecGallery2_Galaxy.apk, so whats the path of the file?..
can u please type and show?..
Thanks in advance
Click to expand...
Click to collapse
I dont remember... but something like
/preload/symlink/system/app/SecGallery2_Galaxy.apk
but double check.
nokiamodeln91 said:
I dont remember... but something like
/preload/symlink/system/app/SecGallery2_Galaxy.apk
but double check.
Click to expand...
Click to collapse
It says read only file system
I even changed the permission of the file in preload to 644 ( rw-r--r-- )
still the same message?.. any idea what it might be?.
Thanks in advance
use adb shell
then mount the preload partition as rw
# mount -o remount rw /preload
# mount -o remount rw /system
the use the codes written above.
nokiamodeln91 said:
use adb shell
then mount the preload partition as rw
# mount -o remount rw /preload
# mount -o remount rw /system
the use the codes written above.
Click to expand...
Click to collapse
Honestly i just now searched in google for adb shell and it says to run windows but when i download and double click the adb.exe it runs and exits!.. Please help..
Will mounting the preload and system in recovery and rebooting the device and running the script again in android emulator work?..
Keep in recovery and mount both.. Then run....
nokiamodeln91 said:
Keep in recovery and mount both.. Then run....
Click to expand...
Click to collapse
I tried in adb shell too.. but its not working
Do u guys have the symlink file?.. can u share with me?.. will it work?..
Thanks in advance
Oh Yeah! SOLVED IT!!
I installed Root explorer and created symlink via that and Voila it worked!
Although i dont know why when i open a photo in gallery i experience FC!
Hi everyone, I modified the stock uRamDisk for CM11 by decompressing it, editing the fstab.encore.rc file, and switching up the part with sdcard0 and sdcard1.
P.S. I removed the zram (compressed RAM) option in the fstab because the Nook Color has a crappy enough CPU as is, so it wont help with zram. Use a swap partition on SDcard if needed.
P.S.2. This ramdisk is from the most recent nightly build (Jan 11, 2015). It may or may not work with older CM11 builds.
It's attached here. It wont let me upload the file as is, so I renamed it to uRamDisk.7z; rename it back to uRamDisk. After that, follow these steps:
0. MAKE A BACKUP OF THE /boot PARTITION IN YOUR RECOVERY JUST IN CASE. If anything happens, restore the /boot partition's backup.
1. Mount /boot partition at /root (it's an unused mountpoint in Android)
adb root && adb shell
# mount -t vfat /dev/block/mmcblk0p1 /root
2. Change directory to /root, rename the original ramdisk
# cd /root && mv uRamDisk uRamdisk.orig
3. Copy over the new ramdisk
adb push uRamDisk /root/
4. Reboot and profit
The internal sdcard will now be seen as external. You no longer need to have an SD card inside to have many apps like Kodi (XBMC), Firefox, etc, asking for external SD.
If it doesn't work for you for some reason, remount the /boot partition again, and copy over the original uRamDisk ( # cp -f uRamDisk.orig uRamDisk ).
I used parts of this script to figure out how to mod the ramdisk: https://gist.github.com/aperezdc/6533546
Any feedback on this one?
les02jen17 said:
Any feedback on this one?
Click to expand...
Click to collapse
Huh, what do you mean? If you have feedback for me, please do post it.
hi,could you compile a flasheable zip file?because many people like me dont know how to use adb or you can explain these steps a bit better, other thing is that i cant change the name to uramdisk(i cant delete .7z) windows 7 and winrar wont let me
btw good work!!
omars44 said:
hi,could you compile a flasheable zip file?because many people like me dont know how to use adb or you can explain these steps a bit better, other thing is that i cant change the name to uramdisk(i cant delete .7z) windows 7 and winrar wont let me
btw good work!!
Click to expand...
Click to collapse
1. Do you have adb installed for Windows? If not, do that first.
2. I don't know how to make a flashable zip. Someone else might. Anyone wanna do that? I don't have time atm since college started. Sorry for the late reply.
3. The instructions are about as simple as they get. You should study the "mount," "cp," and "mv" commands. They are, respectively, for mounting partitions, copying files/folders, and moving/renaming files/folders.
4. You can't rename the file because by default, Windows doesn't show file types' endings (like .exe, .zip, .rar, etc). You need to enable that. Google it.
hello, maybe you still have this nigtly cm11 system of 11Jan, 2015? thank's