Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Swap internal and external SD patch

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Swap internal and external SD patch

    Hi

    I have re-packed the boot.img file from ROM 1.8 for the Cube Talk 9X (I used the one from dejean ROM). I have changed the fstab files in order to permute sdcard0 with sdcard1.
    I also have included a new line for enabling automounting OTG devices (I tested an USB key and it works).

    It is preferable to instal it on a fresh installation. If you want to install it with already data existing under sdcard0, you should first move them on sdcard1. You need to keep the files permission. Use ES File Manager, enable hidden files, select all the sdcard0 content (upper righ icon), then copy it under sdcard1 (overwrite existing files). Then install the patch.

    To install the patch, in SP Flash tool, select the scrapper file of your current rom, unselect all file, select boot, click on boot line, browse to the new img file, then clic download and plug the device (it shall be powered off, and the mtk driver shall be already installed on the PC)

    file: https://www.sendspace.com/file/umf0g6

    #2
    Originally posted by seb_131 View Post
    Hi

    I have re-packed the boot.img file from ROM 1.8 for the Cube Talk 9X (I used the one from dejean ROM). I have changed the fstab files in order to permute sdcard0 with sdcard1.
    I also have included a new line for enabling automounting OTG devices (I tested an USB key and it works).
    file: https://www.sendspace.com/file/umf0g6

    Hi seb_131,need to know,
    what model of your talk 9x (16GB or 32GB,black or white) ?

    Comment


      #3
      Originally posted by mmrrdd View Post
      Hi seb_131,need to know,
      what model of your talk 9x (16GB or 32GB,black or white) ?
      Hi,

      I have the 16Gb (white) version.
      You can build your own boot.img file if you want to be sure that it will correspond to your ROM (I assume that the boot.img should the same for all ROMs based on the revision 1.8).

      Download pack/unpack tool for mtk from xda (http://forum.xda-developers.com/show....php?t=1587411). Extract it under a linux system.
      Change mkbootimg file permission to rwxrwxrwx (777).
      Copy boot.img in the same directory.
      Unpack the boot.img file of your current ROM: ./unpack-MT65xx.pl boot.img
      Edit the 3 fstab.* files inside the new created directory: replace sdcard0 by sdcard and sdcard1 by sdcard0, in the 2 last lines.
      You can add the following line to enable OTG (optionnal): /devices/platform/msm_hsusb_host/usb2 auto auto defaults voldmanaged=usbdisk0:auto
      Repack a new boot.img file: ./repack-MT65xx.pl -boot boot.img-kernel.img boot.img-ramdisk new-boot.img
      Flash the new-boot.img file on your device (use the same scrapper, and download only the boot)

      Comment


        #4
        Originally posted by seb_131 View Post
        Hi,
        Unpack the boot.img file of your current ROM: ./unpack-MT65xx.pl boot.img
        Edit the 3 fstab.* files inside the new created directory: replace sdcard0 by sdcard and sdcard1 by sdcard0, in the 2 last lines.
        You can add the following line to enable OTG (optionnal): /devices/platform/msm_hsusb_host/usb2 auto auto defaults voldmanaged=usbdisk0:auto
        I use a different tool to unpack boot image,the result is in the attach picture.
        Can you show the picture of "3 fstab.* files inside the new created directory",and detail in the 2 last lines.
        Thanks

        Attached Files

        Comment


          #5
          You have 3 files to edit : fstab, fstab.fat.nand and fstab.nand
          They have exactly the same content.
          The 2 last lines in each file correspond to the mount point of your internal SD storage and your external SD card. Pretty at the end of those lines you can find the label of the mounts (sdcard0 and sdcard1). Just replace sdcard0 by sdcard1 in the before-last line, and sdcard1 by sdcard0 in the last line.

          You can also add this new line at the end of the files for OTG:
          /devices/platform/msm_hsusb_host/usb2 auto auto defaults voldmanaged=usbdisk0:auto

          This is my new fstab content:
          # 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

          /emmc@usrdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check,encryptable=footer
          /emmc@protect_f /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
          /emmc@protect_s /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
          /devices/platform/mtk-msdc.0/mmc_host auto vfat defaults voldmanaged=sdcard1:emmc@fat,noemulatedsd
          /devices/platform/mtk-msdc.1/mmc_host auto vfat defaults voldmanaged=sdcard0:auto
          /devices/platform/msm_hsusb_host/usb2 auto auto defaults voldmanaged=usbdisk0:auto
          Last edited by seb_131; 20 August 2014, 16:57.

          Comment


            #6
            Originally posted by seb_131 View Post
            I cannot check the file content currently, but it is very easy.
            You have 3 files to edit : fstab, fstab.fat.nand and fstab.nand
            They have exactly the same content.
            The 2 last lines in each file correspond to the mount point of your internal SD storage and your external SD card. Pretty at the end of those lines you can find the label of the mounts (sdcard0 and sdcard1). Just replace sdcard0 by sdcard1 in the before-last line, and sdcard1 by sdcard0 in the last line.

            You can also add this new line at the end of the files for OTG:
            /devices/platform/msm_hsusb_host/usb2 auto auto defaults voldmanaged=usbdisk0:auto

            I can provide later an example if you want.
            Yes, 3 files have the same content,
            This picture is capture from you extrac-boot_image.
            Attached Files

            Comment


              #7
              This picture , from original boot.img (V1.6).

              Attached Files

              Comment


                #8
                yes, this is my modified file. It should work to swap on any Cube Talk 9X. The linux fstab doesn't contain any partitioning information, just mount point (if you do a mistake, it will not brick your device, you will have no file system, the app will not work, but nothing which cannot be repaired or rolled-back)

                Comment


                  #9
                  This from 900 supersport.

                  Attached Files

                  Comment


                    #10
                    they are all exactly the same (if you ignore the modifications I made)

                    Comment


                      #11
                      The left side is the end content of file init.rc from you boot_swap_sd.img,
                      The right side is the end content of file init.rc from 900 supersport boot.img.
                      may be your moded boot image is modified from 900 supersport .

                      Attached Files

                      Comment


                        #12
                        you are right, I didn't know this. But I think it is a good thing to start init.d services at startup (I don't know why by default it is not enabled)

                        Comment


                          #13
                          The Tool that I use to open(unpack-repack) boot and recovery image of talk 9x,
                          it work on windows,no need linux command,just only this tool and note pad.




                          Attached Files
                          Last edited by mmrrdd; 23 August 2014, 09:25.

                          Comment


                            #14
                            Originally posted by seb_131 View Post
                            you are right, I didn't know this. But I think it is a good thing to start init.d services at startup (I don't know why by default it is not enabled)
                            May be "dejan rom" had mod from "900 supersport rom".

                            Comment


                              #15
                              Originally posted by mmrrdd View Post
                              May be "dejan rom" had mod from "900 supersport rom".
                              Sorry,"dejan rom" had mod from chinese firmware V1.8
                              Attached Files

                              Comment

                              Working...
                              X