• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [TWRP] [MS323, D320n, D325] Team Win Recovery Pro 3.0

Thanks for the New TWRP release @vm03 , its working flawlessly. I was having issues with this (Screenshot attached) theme before (The "Swipe to Backup" tab wasn't showing) but its working perfectly now.

And if anyone wants to know what steps I took to install the new TWRP. Here it is:
(Rename downloaded TWRP to recovery.img and put it in your fastboot\adb folder in C drive.)
Step 1 : Reboot to download mode (Volume Up + USB Cable to PC).

(In adb\fastboot folder "shift + right-click mouse" and select "Open command window here")
Step 2 : Fastboot erase recovery

Step 3 : Fastboot flash recovery recovery.img

Step 4 : Fastboot Reboot

And all done cheers.
 

Attachments

  • Screenshot_2015-06-29-18-42-07.png
    Screenshot_2015-06-29-18-42-07.png
    40.7 KB · Views: 183
Last edited:
The Goods

Hi. The download link is not working for me. It opens the Yandex webpage for the file, but when I click the download button it does nothing. Can you please send me a working link? I have an MS323 L70, is rooted and I am trying to upgrade android. The only thing I dont have yet is the TWRP. I thank you for the help in advance. Please excuse my poor english.
 
You show vold, no real partition. And backup to same device never be "good idea".
I did as you asked, please be specific in what info you require. I appreciate you trying to help but I can only respond with the info you requested. The whole point of a recovery backup is backing up to the same device. Backing up sd-ext to fat32 is no different to backing up a windows partition to a Linux one. Yes, it's the same sd card, but it's reading from a different partition. This feature is native in cwm and twrp, the option actually exists in philz recovery for l70 but is not enabled. I think you are mistaking fact for opinion tbh. The fact is, with the current recovery, a FULL backup is not possible, when it should be. It was possible for the pulse mini over 4 years ago!
 
u0_a107@w5n:/ $ su
root@w5n:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=469576k,nr_inodes=117394,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=469576k,nr_inodes=117394,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=469576k,nr_inodes=117394,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=469576k,nr_inodes=117394,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/vold/179:66 /data/sdext2 ext4 rw,seclabel,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0/dev/block/platform/msm_sdcc.1/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,nodev,relatime,noauto_da_alloc,data=ordered 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=469576k,nr_inodes=117394,mode=050,gid=1028 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:65 /mnt/media_rw/external_SD vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/external_SD fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
root@w5n:/ #
 
Last edited:
I see only vold for /data/ext2. Need research how link2sd work... Can you find, where it real save data?
 
In /proc/partitions : 179:66 mmcblk1p2
In root Explorer : /data/sdext2

That's all I can find.

There should be a mount script somewhere but I can't find it. We don't seem to have init.d support but there's nothing in install-recovery.sh either!
 
Last edited:
Found it!

echo "$(date) mounting..." > $LOG
/data/data/com.buak.Link2SD/files/link2sd_b . sync 1>>$LOG 2>>$LOG
sleep 2
mount -t ext4 -o rw /dev/block/vold/179:66 /data/sdext2 1>>$LOG 2>>$LOG

mount -t ext4 -o rw /dev/block/mmcblk1p2 /data/sdext2 1>>$LOG 2>>$LOG

mount >> $LOG
echo "$(date) mount finished" >> $LOG
chmod 773 /data/dalvik-cache
 
Found it!

echo "$(date) mounting..." > $LOG
/data/data/com.buak.Link2SD/files/link2sd_b . sync 1>>$LOG 2>>$LOG
sleep 2
mount -t ext4 -o rw /dev/block/vold/179:66 /data/sdext2 1>>$LOG 2>>$LOG

mount -t ext4 -o rw /dev/block/mmcblk1p2 /data/sdext2 1>>$LOG 2>>$LOG

mount >> $LOG
echo "$(date) mount finished" >> $LOG
chmod 773 /data/dalvik-cache
Will try add /dev/block/mmcblk1p2 for backup
 
Found it!

echo "$(date) mounting..." > $LOG
/data/data/com.buak.Link2SD/files/link2sd_b . sync 1>>$LOG 2>>$LOG
sleep 2
mount -t ext4 -o rw /dev/block/vold/179:66 /data/sdext2 1>>$LOG 2>>$LOG

mount -t ext4 -o rw /dev/block/mmcblk1p2 /data/sdext2 1>>$LOG 2>>$LOG

mount >> $LOG
echo "$(date) mount finished" >> $LOG
chmod 773 /data/dalvik-cache

Can you please tell me where the mount script is located. I need to check it and possibly modify it. I installed Paranoid Android ROM and now link2sd wont auto mount at system boot. Any help is appreciated. Please excuse my poor english.
 
Can you please tell me where the mount script is located. I need to check it and possibly modify it. I installed Paranoid Android ROM and now link2sd wont auto mount at system boot. Any help is appreciated. Please excuse my poor english.
I found it in /data/data/com.buak.link2sd/files. I presume it mounts after boot, I did a boot logcat and couldn't find anything related to mount sdext2. Also, I know on cyanogen that it tries to mount sd-ext automatically so link2sd conflicts. Could be the same on paranoid. There's a fix if you Google it.
 
Back
Top Bottom