1

As stated in the title I want to be able to mount my SD cards 3rd Partition, this is because that is were all my files are and I would like to be able to backup to this partition.

Phone: LG e400f

Rooted: Yes

Recovery: CWM

ROM: Stock

I am using Link2SD becuse my phone doesn't have much memory for apps and as such I had to partion my sd card, and for some reason my phone would only mount the last partion Not the First Partion so to combat this problem I partition my SD card the way shown below

SD Card Partion Layout:

1st: 7mb fat

2nd: 1.45GB Ext2

3rd: 13.45GB(around that) Fat (My main area were i want to backup my phone and were my music and photos go)

The Problem arises when I try to do a NANDroid Backup as CWM mounts the first partition and since it is so small it can not backup the phone. I would like to be able to backup on the 3rd partition so

a) Is there a recovery that could do this

OR

b) If Not how can I modifiy my recovery so I can

Improve this question
15
  • Matt it just looks complicated, just pay attention to detail and process and, always triple check. Here is LG Optimus L3 forum at XDA forum.xda-developers.com/optimus-l3-l5-l7
    – moonbutt74
    Aug 14, 2015 at 0:45
  • @moonbutt74 I have already checked on XDA for this problem and have come up unsuccessful. The problem is that I want to do a NANDroid backup to my SD card but as told above I am unable to as I need the backup go to the second partition.
    – Matt07211
    Aug 14, 2015 at 0:51
  • You have root and a custom recovery don't you? Dump the recovery.img , unpack it, make the edits, repack it.
    – moonbutt74
    Aug 14, 2015 at 1:41
  • Matt, how old is this phone? I am looking at the device=tree in cyanogenmod git and kernel source as well. I'll make a try at a philz build but we need to move to xda, stack isn't the place for this. Oh and the answer below does work, an upvote would be helpful. M xD
    – moonbutt74
    Aug 14, 2015 at 1:57
  • 1
    Matt , when you dump an image, unless specifying count the entire block get's dumped, so for example my boot.img is 8.9mb roughly but if i dump it using dd with specifying the proper count, I end up with a 10.1mb image, roughly, which is padding. When i unpack it and repack it i lose the padding and the image is again 8.9mb roughly , depending on modifications. You are certainly welcome to do as i suggested for yourself. If you have some question about my work, goto XDA. That being said, i did make it a point to tell you to keep your working img handy just in case. M.
    – moonbutt74
    Aug 16, 2015 at 22:19

1 Answer 1

Reset to default
1

The answer is yes,no,maybe. You might hit a snag with the fat/ext/fat scheme on your card but here goes,

I have a debian chroot <ext4> set up in

  • /dev/block/mmcblk1p2 --> my extSdCard 2nd partition.

So i edit the following in my recovery ramdisk --> Philz Adv CWM

  • init.rc --> add a directory export

under the on init section

export DEBIAN_ROOT /debian

  • in etc/recovery.fstab of recovery ramdisk

    /dev/block/platform/msm_sdcc.2/by-num/p2 /debian ext4 rw,errors=panic wait

Remember this is cwm fstab format, adjust for twrp if needed! Your own device in regular operation will show you the right layout. Remember to set correct <type>for partition.

After you have all that done and have repacked and reflashed your recovery,

root@kali:/storage/tempus# adb reboot recovery
root@kali:/storage/tempus# adb shell mount /debian && adb shell mount | grep debian
/dev/block/platform/msm_sdcc.2/by-num/p2 on /debian type ext4 (rw,seclabel,relatime,data=ordered)


    root@kali:/storage/tempus# adb shell
    ~ # uname -a
    Linux localhost 3.4.0-Carmilla-mb74- #1 SMP PREEMPT Sat Dec 27 22:41:40 EST 2014 armv7l GNU/Linux
    ~ # ls /debian
    AIK         etc         lost+found  policy-k    sbin        t-src
    bin         home        media       proc        selinux     tmp
    boot        images      mnt         root        srv         usr
    dev         lib         opt         run         sys         var
    ~ #

I won't be going into the unpacking/repacking part of the procedure as i am sure that is covered elsewhere.

For a treat, i am still in recovery but exit back out to linux term because it's easier to mount system, 

root@kali:/storage/tempus# adb shell mount /system
root@kali:/storage/tempus# adb shell
~ # go-deb
root@localhost:/# ls
AIK   dev   images      media  policy-k  run      srv    tmp
bin   etc   lib         mnt    proc      sbin     sys    usr
boot  home  lost+found  opt    root      selinux  t-src  var
root@localhost:/#

And after running my go-deb script after mounting /system i am now in my chroot while in recovery. No wifi though, i forgot to square away the modules.

Improve this answer
1
  • This looks a little bit complicated but I will give it a try, but before that, your using PhilZ Touch and doing it with the terminal emulator right? But my problem is I think there is no PhilZ Touch that can work on my Lg e400f unless you know were I can find it.
    – Matt07211
    Aug 14, 2015 at 0:38

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .