Database Info

[Q] Why not tar for backups?

Ok, I'll admit it, for a lot of things, especially system administration, I prefer the command line.
Is there a reason why I would not use tar to do "full backup" of data (as opposed to TiBackup or the like)?
One advantage is that I can extract a tar on another box and, for example, check it in to a VC system.
Admittedly, busybox tar isn't the most full-featured implementation (no one-file-system option, for example), but I believe it does have an exclude-from-file option that works.

I may be wrong, but I don't think tar on our phones can save ownership and permissions (too lazy to try it out right now). I suppose it wouldn't be too hard to write a script to save any info that tar would not preserve into a properties file and then have a restore script that would read the properties file and chown and chmod every file after extracting.

xviiivx said:
I may be wrong, but I don't think tar on our phones can save ownership and permissions
Click to expand...
Click to collapse
busybox tar appears to work like "any" tar, at least for non-extended attributes (I don't know if the kernel supports xattrs )
Code:
$ tar tvf test.tar | head -n 10
drwxr-xr-x 0/0 0 2011-02-07 20:58 system/etc/
-rw-r--r-- 0/0 15346 2011-02-07 20:58 system/etc/apns-conf.xml
-rw-r--r-- 0/0 25 2011-02-07 20:58 system/etc/hosts
-rw-r--r-- 0/0 99026 2011-02-07 20:58 system/etc/NOTICE.html.gz
-r-xr-x--- 0/2000 1200 2011-02-07 20:58 system/etc/init.goldfish.sh
-rw-r--r-- 0/0 1707 2011-02-07 20:58 system/etc/vold.fstab
-rw-r--r-- 0/0 195 2011-02-07 20:58 system/etc/gps.conf
drwxr-xr-x 0/0 0 2011-02-07 20:58 system/etc/security/
-rw-r--r-- 0/0 91755 2011-02-07 20:58 system/etc/security/cacerts.bks
drwxr-xr-x 0/0 0 2011-02-07 20:58 system/etc/security/drm/
and does appear to preserve links as well
Code:
$ tar tvf test2.tar | head -n 10
lrwxrwxrwx 0/0 0 2011-03-15 12:09 etc -> /system/etc
These were created using busybox tar from /system/etc and of /etc, adb pull-ed, and extracted on another system (Cygwin, in this case).

If you look in the TitaniumBackup directory on the sdcard, each app has 3 files:
appname.apk.gz- I didn't check, but obviously is probably just a backup of the apk
appname.tar.gz (looks like a tar of the /data/data/app dir)
appname.properties- looks like it includes a huge chuck of data for the icon and some misc information, a lot of which appears to be... market information?
I don't know how important the third file is, but it looks like Titanium is using tar. You could download a junk app and try it with that app and see if it works.
Just a guess, but I bet untarring may not be enough, you'll probably have to run the command "pm install" on each apk.

Thanks Fubuya!
That leads me to two useful "conclusions"
tar probably works just fine
TiBackup files are likely extractable on a POSIX box

Yeah, on linux, one is just text and I extracted the other two just fine (tar -zxvf for one and gunzip for the other). It's probably just a matter of finding out if there are any extra tricks you need to know about. Looks like Tibackup has a forum here, if you run into problems maybe they'd be nice enough to translate what's happening on the backend of their backup process.

Building vocpcm.c into kernel current HTC Sensation kernel source

Hi (Posting here as I am not yet permitted to in dev section)
I need to get access to the /dev/voc* devices which come from the vocpcm.c code from olher HTC kernel releases.
It looks like it was meant to work with qdsp5 DSP and I am not sure whether I should assume it works
So, I added it to the kernel and once running, I can see the devices
ls -al /dev/voc*
crw-rw-rw- 1 root root 10, 49 Jul 28 21:18 /dev/voc_rx_playback
crw-rw-rw- 1 root root 10, 50 Jul 28 21:18 /dev/voc_rx_record
crw-rw-rw- 1 root root 10, 47 Jul 28 21:18 /dev/voc_tx_playback
crw-rw-rw- 1 root root 10, 48 Jul 28 21:18 /dev/voc_tx_record
But it looks like they really aren't mapping to the DSP as I get no audio from and when i try and tail the file, I get
[email protected]:/dev # tail voc_rx_playback
tail voc_rx_playback
tail: can't open 'voc_rx_playback': No such device
tail: no files
Which is a different result than on my working HTC Tattoo.
Any ideas here as to whether I might need to do something more to get it working with qdsp6 or whether I need a different handset etc
As far as I know, these devices are completely different (and different concept) from the voice uplink and voice downlink that comes with the 2 way recording patch. Is that right ?
cheers
Mark

ROOT without adb driver?

everthing I read refers to load adb driver.
what do you do if you dont have the driver?
adb drivers == nothing found
any attempt with adb
error: device not found
trying to root Audiosonic 7"
every program refers to loading the adb driver no adb driver to load
I've rooted other devices the easy way, someone advises howto
I WOULD like to learn how to root the device, without a know adb driver.
can someone point me to the RIGHT information to read or do please
android 4.0.4
Kernal version :
3.0.36 +
[email protected] #76
Build number :
RK292X_ANDROID4.0.4-SDK-v1.00.00
rk2926sdk-eng 4.0.4 IMM760 20121215.042649 release-keys

There is a way to make your device compatible with adb, even if you can't find driver for it. Below is how I made my old Creative Ziio compatible with adb:
- download and install Google USB driver
- open file android_winusb.inf from the driver's directory. Find section [Google.NTx86] (if you have 32-bit Windows) or [Google.NTamd64] (for 64-bit). At the end of the section, add the following lines:
; Creative Ziio 7"
%SingleAdbInterface% = USB_Install, USB\VID_2350&PID_0102
%CompositeAdbInterface% = USB_Install, USB\VID_2350&PID_0102&MI_01
- find the device in Device Manager and update driver using previously installed USB driver
- add the folowing line to %HOME/.android/adb_usb.ini:
0x2350
- restart adb server
You can get vid&pid from the DeviceManager.

knutson said:
There is a way to make your device compatible with adb, even if you can't find driver for it. Below is how I made my old Creative Ziio compatible with adb:
- download and install Google USB driver
- open file android_winusb.inf from the driver's directory. Find section [Google.NTx86] (if you have 32-bit Windows) or [Google.NTamd64] (for 64-bit). At the end of the section, add the following lines:
; Creative Ziio 7"
%SingleAdbInterface% = USB_Install, USB\VID_2350&PID_0102
%CompositeAdbInterface% = USB_Install, USB\VID_2350&PID_0102&MI_01
- find the device in Device Manager and update driver using previously installed USB driver
- add the folowing line to %HOME/.android/adb_usb.ini:
0x2350
- restart adb server
You can get vid&pid from the DeviceManager.
Click to expand...
Click to collapse
Very informative post. That's what we like to see

well the audiosonic in normal mode shows up as T-07B in recovery it shows as rk2928sdk
added the vid/pid I got from each (different)
unmerged/merged
nomal mode adb devices finds nothing
recovery mode adb devices finds 0123456789ABCDEF RECOVERY
tried adb shell in recovery and got exec '/system/bin/sh' folder or file not found
ok need a break and try attacking this again
singleadbinterface
compositeinterface
best to use both? 1? looking through android_winusb.ini seem like a mixed bag some both, one etc

Yes, both singleadbinterface and compositeinterface are needed. Also do not forget to modify adb_usb.ini.
Also, make sure that USB debugging is enabled on your device, note that this option should be changed only when device is disconnected from USB.
To check that adb is working,try to install something with
adb install ./some_application.apk

knutson said:
Yes, both singleadbinterface and compositeinterface are needed. Also do not forget to modify adb_usb.ini.
Also, make sure that USB debugging is enabled on your device, note that this option should be changed only when device is disconnected from USB.
To check that adb is working,try to install something with
adb install ./some_application.apk
Click to expand...
Click to collapse
so, just to be specific, and not presuming
to root the device I should be in normal mode or recovery? (last 2 roots I did was in normal mode but they where design root methods)
if normal mode, how can you install if the device not found (which device)
device set and confirmed in debugging mode
thanks for the help, even just confirming things for me

just to advised
I tried installing an app
in normal mode error device not found---- waiting on device
in recovery mode seemd to load but got exec '/system/bin/sh' folder or file not found (interestingly enough, got twice)
so either still a driver problem or need to solve the error (god i've been at this for a few days now)

wolfbite.aus said:
just to advised
I tried installing an app
in normal mode error device not found---- waiting on device
in recovery mode seemd to load but got exec '/system/bin/sh' folder or file not found (interestingly enough, got twice)
so either still a driver problem or need to solve the error (god i've been at this for a few days now)
Click to expand...
Click to collapse
Are you mounting /system partition with ADB prior to trying to push files to the partition?

cant mount /system
# adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
is there a sh file somewhere I can push and try???
but adb pull /system gave me bin/busybox
adb pull /data gave me
But each clue you give me gives new ideas (mount got me looking into push/pull
seems I can
adb push so found a su and did adb push /system/bin/su
seemed to work
# adb push su /system/bin/
4576 KB/s (91980 bytes in 0.019s)
then tried
# adb pull /system/
pull: building file list...
pull: /system/bin/busybox -> ./bin/busybox
pull: /system/bin/su -> ./bin/su
2 files pulled. 0 files skipped.
2443 KB/s (1899036 bytes in 0.758s)
adb pull /
pull: building file list...
skipping special file 'rknand_sys_storage'
skipping special file 'ppp'
skipping special file 'network_throughput'
skipping special file 'network_latency'
skipping special file 'cpu_dma_latency'
skipping special file 'rk29-ipp'
skipping special file 'xt_qtaguid'
skipping special file 'galcore'
skipping special file 'binder'
skipping special file 'device-mapper'
skipping special file 'i2c-dev'
skipping special file 'alarm'
skipping special file 'uinput'
skipping special file 'keychord'
skipping special file 'usb_accessory'
skipping special file 'mtp_usb'
skipping special file 'android_adb'
skipping special file 'pmem'
skipping special file 'ion'
skipping special file 'fuse'
skipping special file 'ashmem'
skipping special file 'verifyid'
skipping special file 'vcsa1'
skipping special file 'vcs1'
skipping special file 'vcsa'
skipping special file 'vcs'
skipping special file 'ptmx'
skipping special file 'tty63'
skipping special file 'tty62'
skipping special file 'tty61'
skipping special file 'tty60'
skipping special file 'tty59'
skipping special file 'tty58'
skipping special file 'tty57'
skipping special file 'tty56'
skipping special file 'tty55'
skipping special file 'tty54'
skipping special file 'tty53'
skipping special file 'tty52'
skipping special file 'tty51'
skipping special file 'tty50'
skipping special file 'tty49'
skipping special file 'tty48'
skipping special file 'tty47'
skipping special file 'tty46'
skipping special file 'tty45'
skipping special file 'tty44'
skipping special file 'tty43'
skipping special file 'tty42'
skipping special file 'tty41'
skipping special file 'tty40'
skipping special file 'tty39'
skipping special file 'tty38'
skipping special file 'tty37'
skipping special file 'tty36'
skipping special file 'tty35'
skipping special file 'tty34'
skipping special file 'tty33'
skipping special file 'tty32'
skipping special file 'tty31'
skipping special file 'tty30'
skipping special file 'tty29'
skipping special file 'tty28'
skipping special file 'tty27'
skipping special file 'tty26'
skipping special file 'tty25'
skipping special file 'tty24'
skipping special file 'tty23'
skipping special file 'tty22'
skipping special file 'tty21'
skipping special file 'tty20'
skipping special file 'tty19'
skipping special file 'tty18'
skipping special file 'tty17'
skipping special file 'tty16'
skipping special file 'tty15'
skipping special file 'tty14'
skipping special file 'tty13'
skipping special file 'tty12'
skipping special file 'tty11'
skipping special file 'tty10'
skipping special file 'tty9'
skipping special file 'tty8'
skipping special file 'tty7'
skipping special file 'tty6'
skipping special file 'tty5'
skipping special file 'tty4'
skipping special file 'tty3'
skipping special file 'tty2'
skipping special file 'tty1'
skipping special file 'tty0'
skipping special file 'console'
skipping special file 'tty'
skipping special file 'kmsg'
skipping special file 'urandom'
skipping special file 'random'
skipping special file 'full'
skipping special file 'zero'
skipping special file 'null'
skipping special file 'kmem'
skipping special file 'mem'
skipping special file 'ttyGS3'
skipping special file 'ttyGS2'
skipping special file 'ttyGS1'
skipping special file 'ttyGS0'
skipping special file 'video0'
skipping special file 'rtc0'
skipping special file 'mma8452_daemon'
skipping special file 'ttyS2'
skipping special file 'ttyS0'
skipping special file 'ttyS1'
skipping special file 'property_service'
skipping special file 'event2'
skipping special file 'event0'
skipping special file 'event1'
skipping special file 'fb1'
skipping special file 'fb0'
skipping special file '001'
skipping special file '001'
skipping special file 'timer'
skipping special file 'controlC0'
skipping special file 'pcmC0D0c'
skipping special file 'pcmC0D0p'
skipping special file 'system'
skipping special file 'radio'
skipping special file 'events'
skipping special file 'main'
skipping special file 'mtdblock10'
skipping special file 'mtdblock9'
skipping special file 'mtdblock8'
skipping special file 'mtdblock7'
skipping special file 'mtdblock6'
skipping special file 'mtdblock5'
skipping special file 'mtdblock4'
skipping special file 'mtdblock3'
skipping special file 'mtdblock2'
skipping special file 'mtdblock1'
skipping special file 'mtdblock0'
skipping special file 'loop7'
skipping special file 'loop6'
skipping special file 'loop5'
skipping special file 'loop4'
skipping special file 'loop3'
skipping special file 'loop2'
skipping special file 'loop1'
skipping special file 'loop0'
skipping special file 'mtd10ro'
skipping special file 'mtd10'
skipping special file 'mtd9ro'
skipping special file 'mtd9'
skipping special file 'mtd8ro'
skipping special file 'mtd8'
skipping special file 'mtd7ro'
skipping special file 'mtd7'
skipping special file 'mtd6ro'
skipping special file 'mtd6'
skipping special file 'mtd5ro'
skipping special file 'mtd5'
skipping special file 'mtd4ro'
skipping special file 'mtd4'
skipping special file 'mtd3ro'
skipping special file 'mtd3'
skipping special file 'mtd2ro'
skipping special file 'mtd2'
skipping special file 'mtd1ro'
skipping special file 'mtd1'
skipping special file 'mtd0ro'
skipping special file 'mtd0'
^C
# adb pull /system
pull: building file list...
pull: /system/bin/busybox -> ./bin/busybox
1 file pulled. 0 files skipped.
2736 KB/s (1807056 bytes in 0.644s)
# ls
bin
# ls bin
busybox

adb ls /
still no sh
any ideas?
what about
000081a4 0001e9ff 00000000 rk29xxnand_ko.ko.3.0.8+
000081a4 0001e995 00000000 rk29xxnand_ko.ko.2.6.32.27
# adb ls /
000041ed 00000000 51470583 .
000041ed 00000000 51470583 ..
000041ed 00000000 51470583 cache
000041ed 00000000 51470583 mnt
000081a4 000006f9 00000000 ueventd.rk29board.rc
000081a4 00000f71 00000000 ueventd.rc
000081a4 00000110 00000000 ueventd.goldfish.rc
000041ed 00000000 51470585 tmp
000041ed 00000000 00000000 system
000041ed 00000000 51470583 sys
000041e8 00000000 00000000 sbin
000081a4 0001e9ff 00000000 rk29xxnand_ko.ko.3.0.8+
000081a4 0001e995 00000000 rk29xxnand_ko.ko.2.6.32.27
000041ed 00000000 00000000 res
0000416d 00000000 00000000 proc
000081e8 00000626 00000000 init.rc
000081e8 000191ac 00000000 init
000041ed 00000000 00000000 etc
000081a4 00000908 00000000 default.prop
000041ed 00000000 51470d4e data
000081e8 0003abe4 00000000 charger
000041c0 00000000 4fd5637e root
000041ed 000009b0 51470585 dev
# adb ls /sys
000041ed 00000000 51470583 .
000041ed 00000000 51470583 ..
000041ed 00000000 514718d3 fs
000041ed 00000000 51470583 devices
000041ed 00000000 514718d3 dev
000041ed 00000000 514718d3 bus
000041ed 00000000 51470583 class
000041ed 00000000 514718d3 firmware
000041ed 00000000 514718d3 kernel
000041ed 00000000 514718d3 power
000041ed 00000000 514718d3 module
000041ed 00000000 51470583 block
000041ed 00000000 514718d3 android_gsensor
000041ed 00000000 514718d3 sd-sdio
# adb ls /sbin
000041e8 00000000 00000000 .
000041ed 00000000 51470583 ..
0000a1ff 00000007 00000000 ueventd
000081e8 0001dd74 00000000 resize2fs
000081e8 00046330 00000000 recovery
000081e8 0002da68 00000000 mke2fs
000081e8 00012700 00000000 mkdosfs
000081e8 0004345c 00000000 e2fsck
000081e8 00022d40 00000000 adbd

.s

tried copying over the sh from second android
pushed to 1st android
# adb ls /system/bin/
000041ed 00000000 514722b2 .
000041ed 00000000 00000000 ..
000081ff 00025744 514721d6 sh
000081b6 0001674c 4ffd3b72 su
000081ed 001b92d0 00000000 busybox
# adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
still fails
wonder if file permission thing, if so howto chage without shell capability
# adb root
adbd is already running as root

wolfbite.aus said:
tried copying over the sh from second android
pushed to 1st android
# adb ls /system/bin/
000041ed 00000000 514722b2 .
000041ed 00000000 00000000 ..
000081ff 00025744 514721d6 sh
000081b6 0001674c 4ffd3b72 su
000081ed 001b92d0 00000000 busybox
# adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
still fails
wonder if file permission thing, if so howto chage without shell capability
# adb root
adbd is already running as root
Click to expand...
Click to collapse
As for the sh script, there isn't one that I know of. Sorry.
You must also apply file permissions with chmod for each file that you push to the device. Most file permissions are going to be 0644 or 0755.
All the Linux commands you are using are actually symlinked to busybox in your /system/bin folder. I would recommend updating your busybox installation while you are in the process of rooting with this method.
You should also update the SuperUser.apk in /system/app since you updated/replaced the su binary in /system/bin. A wise precautionary measure is to also install a copy of the su binary in /system/xbin.

the adb command seems to work push, pull, /
adb shell still gives me
- exec '/system/bin/sh' failed: No such file or directory (2) -
tried pushing busybox (succesful)
but getting same error with shell
how do you apply chmod without shell?
can you break down what the hexidecimal values mean (tried searching)
# adb ls /system/bin/
000041ed 00000000 514722b2 .
000041ed 00000000 00000000 ..
000081ff 00025744 514721d6 sh
000081b6 0001674c 4ffd3b72 su
000081ed 001b92d0 00000000 busybox
tried setting file permissions befor pushing, didnt work
tried upgrading img but got signature verification errors no matter what I through at it
(not worried about bricking this one, slight kid damaged screen and another to use for final results
theres probably mor i can do with adb but its learn as we go

wolfbite.aus said:
the adb command seems to work push, pull, /
adb shell still gives me
- exec '/system/bin/sh' failed: No such file or directory (2) -
tried pushing busybox (succesful)
but getting same error with shell
how do you apply chmod without shell?
can you break down what the hexidecimal values mean (tried searching)
# adb ls /system/bin/
000041ed 00000000 514722b2 .
000041ed 00000000 00000000 ..
000081ff 00025744 514721d6 sh
000081b6 0001674c 4ffd3b72 su
000081ed 001b92d0 00000000 busybox
tried setting file permissions befor pushing, didnt work
tried upgrading img but got signature verification errors no matter what I through at it
(not worried about bricking this one, slight kid damaged screen and another to use for final results
theres probably mor i can do with adb but its learn as we go
Click to expand...
Click to collapse
Permissions must be set after pushing to the device.

guess thats it then
if I cant get a shell, then nothing else to do

[Failed] ROOT without adb driver?
close thread

useful post
but afraid of the codes

What i Did
I took the google usb driver, then downloaded the (supposed) usb drivers from my manufactuer. The maker of my phone, totally screwed up their usb drivers, they didn't have the right vid/pid 's for it( checked the drivers in a linux distro) . Opened the manufactuer's driver, changed the vid/pid's to what was supposed to be there, in it, and the google driver too. Opened the device manager(windows) and ran the "have disk" option, to get the right recognition, and all of the (ADB interface, Bootloader Interface, Composite..) intalled correctly.SDK, eclipse, QtAdb, run great, the only problem is not recognizing what bootloader is in phone( it's locked). I think you're doing a little too much, for your problem.

wolfbite.aus said:
guess thats it then
if I cant get a shell, then nothing else to do
Click to expand...
Click to collapse
hang in there brah i rooted my 2 days ago. i got the a/sonic 10.1 rk2928 chip
how i did it? hrmm i downloaded the rk29 root tool its some where on xda forums. find it.! once i plugged the usb cable into my tablet from pc all drivers installed only one didn't that one t-22b i think. so i used my samsung s2 drivers that was already installed. and walla! adb started working the rest i left for the root kit runme.bat hope that helped good luck!

[Q] Overlay Error

Hello,
I'm trying to port Ubuntu Touch for Photon Q. I'm posting in this section, because the error I get is generic. My phone fails to boot. The display flickers several times and last_kmsg contains the following message multiple times (the number is consistent with the number of flickers):
Code:
[ 13.802716,0] mdp4_calc_req_mdp_clk: src_h is zero!
[ 13.807477,0] mdp4_overlay_borderfill_stage_down: no base layer at mixer=1
Can someone please tell me what might be causing this error?
Thank you!

Some more information from the log:
Code:
E/Adreno200-GSL( 1138): <ioctl_kgsl_driver_entry:402>: open(/dev/kgsl-3d0) failed: errno 2. No such file or directory
But the device is there:
Code:
ls -l /dev/kgsl*
crw-rw-rw- 1 root root 241, 1 Nov 26 01:08 /dev/kgsl-2d0
crw-rw-rw- 1 root root 241, 2 Nov 26 01:08 /dev/kgsl-2d1
crw-rw-rw- 1 root root 241, 0 Nov 26 01:08 /dev/kgsl-3d0

[Recovery][OFFICIAL][UBL] TWRP 3.1.1 Touch Recovery for Xperia L

{
"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"
}
TWRP 3.1.x - Based upon Android 7.1 :
* Whole new TWRP 3 interface
* Flashable to FOTA for permanent recovery
* Bootable recovery image if required
OFFICIAL DOWNLOADS FOR TAOSHAN :
https://twrp.me/sony/sonyxperial.html
twrp-3.x.x-x-taoshan.img : Official TWRP image
How to install : All informations available on TWRP.me
You can download the recovery via Official TWRP App as well :
https://play.google.com/store/apps/details?id=me.twrp.twrpapp&hl=en
DEVELOPMENT DOWNLOADS FOR TAOSHAN :
https://mega.nz/#F!vYwXRRRa!PQgFIpUqjEjJoHVkwTWe0w
twrp-3.x.x-x-fota-taoshan.zip : Flashable TWRP 3 to FOTA installer [Flash this zip if you already have older TWRP installed]
twrp-3.x.x-x-boot-taoshan.img : Fastboot bootable TWRP 3 image
twrp-3.x.x-x-secondary-multirom-taoshan.zip : As secondary MultiROM (optional)
cleaner-fota-taoshan.zip : Flashable FOTA formatter (optional)
HOW TO INSTALL EASILY TO FOTA :
* Boot to recovery : Enter the existing recovery as usual
* Flash to FOTA : Install the TWRP FOTA zip to upgrade to latest TWRP
* (Optional) : Flash the ROM you want
HOW TO INSTALL MANUALLY TO FOTA :
* Bootimage : Download the TWRP bootimage you want to flash
* File storage : Adapt the path and push the file to the device this way :
Code:
adb root
adb wait-for-device
adb push FullPathToTheRecovery.img /tmp/twrp.img
* Flash : Extract the TWRP image to the FOTA partition
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
* Reboot to recovery : adb reboot recovery
INFORMATIONS ABOUT TWRP 3 :
* Installation : Simply flash the zip with a working TWRP or CyanogenRecovery
* Known issues : No major issue remaining, but sources open to improvements
* Usage : Built for Nougat, works for Marshmallow, Lollipop based ROMs too
* More here : http://www.xda-developers.com/twrp-3-0-0-has-arrived/
ADDITIONAL LINKS :
* Easy ADB and Fastboot for unexperienced users :
http://forum.xda-developers.com/showthread.php?p=48915118
Thanks to @AdrianDC for big help in bring-up and thread template
Thanks to the TWRP Team for sources
​
Current local manifest of the TWRP build
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://github.com/STRYDER-007/twrp_development_sony -->
XDA:DevDB Information
[Recovery][OFFICIAL][UBL] TWRP 3.1.1 Touch Recovery for Xperia L, Tool/Utility for the Sony Xperia L
Contributors
STRYDER~007
Version Information
Status: Stable
Created 2017-10-02
Last Updated 2017-10-05

Nice work, but where can I download the zip file. Ready for testing. But I mis the link.
Btw nice work.
I was to early. They are here now

paul.coster said:
Nice work, but where can I download the zip file. Ready for testing. But I mis the link.
Btw nice work.
I was to early. They are here now
Click to expand...
Click to collapse
The link is up! Enjoy!

Is it just me, or does this recovery not work? Holding volUp to enter the recovery just turns the screen black; the screen flashes between the sony logo and the said black screen after that, and I have to remove the battery to get the phone working again.
I used both your method of installation, as well as mine, and none of them worked. The older official TWRP recovery (3.0.2-0) works just fine, though.

stuckbootloader said:
Is it just me, or does this recovery not work? Holding volUp to enter the recovery just turns the screen black; the screen flashes between the sony logo and the said black screen after that, and I have to remove the battery to get the phone working again.
I used both your method of installation, as well as mine, and none of them worked. The older official TWRP recovery (3.0.2-0) works just fine, though.
Click to expand...
Click to collapse
Can you mention the steps you performed as well as the scenario in which you're trying to flash it?
Btw you can simply flash twrp-3.x.x-x-fota-taoshan.zip from existing recovery to upgrade TWRP.

STRYDER~007 said:
Can you mention the steps you performed as well as the scenario in which you're trying to flash it?
Btw you can simply flash twrp-3.x.x-x-fota-taoshan.zip from existing recovery to upgrade TWRP.
Click to expand...
Click to collapse
Sorry for the late reply.
I transferred the twrp.img file to the root of the SD card, and ran this command through adb shell
dd if=/storage/36BD-1A02/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel.
That worked with the older releases.
I also tried the commands in the description (pushing twrp.img /tmp/ and then moving it to FOTAKernel), and there was no difference.
Weirdly enough, flashing the .zip worked.

stuckbootloader said:
Sorry for the late reply.
I transferred the twrp.img file to the root of the SD card, and ran this command through adb shell
dd if=/storage/36BD-1A02/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel.
That worked with the older releases.
I also tried the commands in the description (pushing twrp.img /tmp/ and then moving it to FOTAKernel), and there was no difference.
Weirdly enough, flashing the .zip worked.
Click to expand...
Click to collapse
Well there you go! IMO flashing zip to upgrade TWRP is the simplest so I'd always prefer that. Enjoy the new recovery! :highfive:

STRYDER~007 said:
Can you mention the steps you performed as well as the scenario in which you're trying to flash it?
Btw you can simply flash twrp-3.x.x-x-fota-taoshan.zip from existing recovery to upgrade TWRP.
Click to expand...
Click to collapse
Hi,
I have the same issue, on a Xperia L (white, C2105), tried with two possibilities now, using recovery image twrp.3.1.1-0-taoshan.img, two methods:
1) flashing via existing TWRP recovery (v 2.8.7.0): according to your description I selected install, image, with the aforementioned TWRP recovery image.
2) using the recovery installer app from corphish/StdBarbarossa (version 1.4 - dated 18 May 2016): selecting the menu option to install a custom recovery, to install the aforementioned TWRP recovery image.
Please note that the same recovery installer app from corphish/StdBarbarossa works perfectly to install the TWRP 2.8.7.0.
Therefore I would suggest that the latest TWRP image might need to be reviewed for side-effects by implemented changes. I will try with older versions, to identify if it works with older versions.
Please let me know in case you need any further details, either of the device or of the steps that I performed.
Cheers, Henning
---------- Post added at 10:39 PM ---------- Previous post was at 10:30 PM ----------
xleng said:
Hi,
I have the same issue, on a Xperia L (white, C2105), tried with two possibilities now, using recovery image twrp.3.1.1-0-taoshan.img, two methods:
1) flashing via existing TWRP recovery (v 2.8.7.0): according to your description I selected install, image, with the aforementioned TWRP recovery image.
2) using the recovery installer app from corphish/StdBarbarossa (version 1.4 - dated 18 May 2016): selecting the menu option to install a custom recovery, to install the aforementioned TWRP recovery image.
Please note that the same recovery installer app from corphish/StdBarbarossa works perfectly to install the TWRP 2.8.7.0.
Therefore I would suggest that the latest TWRP image might need to be reviewed for side-effects by implemented changes. I will try with older versions, to identify if it works with older versions.
Please let me know in case you need any further details, either of the device or of the steps that I performed.
Cheers, Henning
Click to expand...
Click to collapse
OK
Using the method to install TWRP v3 via the existing TWRP recovery version 2.8.7.0 (actually I'm not quite sure about the version, since the splash screen reported version 2.8.7.2, but the main application header reports 2.8.7.0, probably the latter version number was just not updated), finally was SUCCESSFUL with twrp-3.0.2-0-taoshan.img!
I didn't try the earlier ones, since I identified a TWRP version which should be functional.
I think probably something went wrong with the most recent update!?
Please let me know in case I could support troubleshooting somehow.
I have actually two Xperia L's, one as my primary smartphone, the second as spare, which I typically use to try out new things prior to messing around with the primary one.
Cheers
---------- Post added at 10:50 PM ---------- Previous post was at 10:39 PM ----------
STRYDER~007 said:
Well there you go! IMO flashing zip to upgrade TWRP is the simplest so I'd always prefer that. Enjoy the new recovery! :highfive:
Click to expand...
Click to collapse
Just noted that I should have read the thread more carefully first .... *doh*
Actually, where can I get the zip file? I only could download the img from the TWRP website.
Eventually I would also be interested to take a look to the sources, if possible (just out of curiosity).
Thanks in advance!
---------- Post added at 11:15 PM ---------- Previous post was at 10:50 PM ----------
xleng said:
Hi,
I have the same issue, on a Xperia L (white, C2105), tried with two possibilities now, using recovery image twrp.3.1.1-0-taoshan.img, two methods:
1) flashing via existing TWRP recovery (v 2.8.7.0): according to your description I selected install, image, with the aforementioned TWRP recovery image.
2) using the recovery installer app from corphish/StdBarbarossa (version 1.4 - dated 18 May 2016): selecting the menu option to install a custom recovery, to install the aforementioned TWRP recovery image.
Please note that the same recovery installer app from corphish/StdBarbarossa works perfectly to install the TWRP 2.8.7.0.
Therefore I would suggest that the latest TWRP image might need to be reviewed for side-effects by implemented changes. I will try with older versions, to identify if it works with older versions.
Please let me know in case you need any further details, either of the device or of the steps that I performed.
Cheers, Henning
---------- Post added at 10:39 PM ---------- Previous post was at 10:30 PM ----------
OK
Using the method to install TWRP v3 via the existing TWRP recovery version 2.8.7.0 (actually I'm not quite sure about the version, since the splash screen reported version 2.8.7.2, but the main application header reports 2.8.7.0, probably the latter version number was just not updated), finally was SUCCESSFUL with twrp-3.0.2-0-taoshan.img!
I didn't try the earlier ones, since I identified a TWRP version which should be functional.
I think probably something went wrong with the most recent update!?
Please let me know in case I could support troubleshooting somehow.
I have actually two Xperia L's, one as my primary smartphone, the second as spare, which I typically use to try out new things prior to messing around with the primary one.
Cheers
---------- Post added at 10:50 PM ---------- Previous post was at 10:39 PM ----------
Just noted that I should have read the thread more carefully first .... *doh*
Actually, where can I get the zip file? I only could download the img from the TWRP website.
Eventually I would also be interested to take a look to the sources, if possible (just out of curiosity).
Thanks in advance!
Click to expand...
Click to collapse
I found the zip file now. But actually it didn't work either.
I extracted the twrp.img from the twrp-3.1.1-20171005-fota-taoshan.zip.
Then I applied the following commands :
adb root
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
The result is a boot loop, looping between the SONY logo and a black screen.
Afterwards I successfully installed back TWRP-3.0.2-0 using the recovery installer app from corphish.
Cheers

xleng said:
The result is a boot loop, looping between the SONY logo and a black screen.
Afterwards I successfully installed back TWRP-3.0.2-0 using the recovery installer app from corphish.
Cheers
Click to expand...
Click to collapse
Flash that .zip through the 3.0.2-0 recovery now, it ought to work. I had the same flashing issue. Both the app and the .zip should work now, so it doesn't really matter which method you use.

xleng said:
Hi,
I have the same issue, on a Xperia L (white, C2105), tried with two possibilities now, using recovery image twrp.3.1.1-0-taoshan.img, two methods:
1) flashing via existing TWRP recovery (v 2.8.7.0): according to your description I selected install, image, with the aforementioned TWRP recovery image.
2) using the recovery installer app from corphish/StdBarbarossa (version 1.4 - dated 18 May 2016): selecting the menu option to install a custom recovery, to install the aforementioned TWRP recovery image.
Please note that the same recovery installer app from corphish/StdBarbarossa works perfectly to install the TWRP 2.8.7.0.
Therefore I would suggest that the latest TWRP image might need to be reviewed for side-effects by implemented changes. I will try with older versions, to identify if it works with older versions.
Please let me know in case you need any further details, either of the device or of the steps that I performed.
Cheers, Henning
---------- Post added at 10:39 PM ---------- Previous post was at 10:30 PM ----------
OK
Using the method to install TWRP v3 via the existing TWRP recovery version 2.8.7.0 (actually I'm not quite sure about the version, since the splash screen reported version 2.8.7.2, but the main application header reports 2.8.7.0, probably the latter version number was just not updated), finally was SUCCESSFUL with twrp-3.0.2-0-taoshan.img!
I didn't try the earlier ones, since I identified a TWRP version which should be functional.
I think probably something went wrong with the most recent update!?
Please let me know in case I could support troubleshooting somehow.
I have actually two Xperia L's, one as my primary smartphone, the second as spare, which I typically use to try out new things prior to messing around with the primary one.
Cheers
---------- Post added at 10:50 PM ---------- Previous post was at 10:39 PM ----------
Just noted that I should have read the thread more carefully first .... *doh*
Actually, where can I get the zip file? I only could download the img from the TWRP website.
Eventually I would also be interested to take a look to the sources, if possible (just out of curiosity).
Thanks in advance!
---------- Post added at 11:15 PM ---------- Previous post was at 10:50 PM ----------
I found the zip file now. But actually it didn't work either.
I extracted the twrp.img from the twrp-3.1.1-20171005-fota-taoshan.zip.
Then I applied the following commands :
adb root
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
The result is a boot loop, looping between the SONY logo and a black screen.
Afterwards I successfully installed back TWRP-3.0.2-0 using the recovery installer app from corphish.
Cheers
Click to expand...
Click to collapse
You can use official TWRP app from play store OR simply flash the twrp-3.1.1-DATE-fota-taoshan.zip using any existing recovery from HERE. That's all, simple!

stuckbootloader said:
Flash that .zip through the 3.0.2-0 recovery now, it ought to work. I had the same flashing issue. Both the app and the .zip should work now, so it doesn't really matter which method you use.
Click to expand...
Click to collapse
Hi!
Unfortunately it doesn't work for me.
I tried to flash the zip via the recovery, but ended in another boot loop after reboot with attempt to enter the recovery again.
Sent from my Xperia L using XDA-Developers Legacy app

Hi again,
I just installed the official twrp app (version 1.15, build 28) and tried to flash the twrp image 3.1.1-0.
Twrp reported successful flashing, butafter reboot the recovery was not entered, but instead I had a bootloop again.
Prior to flashing, I did a backup of the existing recovery (containing twrp-3.0.2), after re-flashing the recovery backup resulted in a functional installation of twrp3.0.2 again.
Any recommendation? I'm using the XperiaL, C2105, white version.
The device actually was returned from Sony, eg was shipped without any provider branding, because the initial phone (which did have provider branding) had issues with the camera, which therefore has been sent to Sony within the guarantee period. Sony however did not repair the phone, but rather sent back a new and original Sony device.
In case any other information might be of interest, please let me know.
Would be great to be able to install twrp3.1.1 + LineageOS 14.1!
Actually it's not clear to me if LOS14.1 could be flashed with twrp3.0.2, since errors have been reported?
Sent from my Xperia L using XDA-Developers Legacy app

xleng said:
Actually it's not clear to me if LOS14.1 could be flashed with twrp3.0.2, since errors have been reported?
Click to expand...
Click to collapse
I am not sure about your device, in my Xperia M, I use lineage 14.1 with twrp 3.0.2 with no problems. Even I tried cwm recovery, there was no problem again. So yeah you can try it.

xleng said:
Hi!
Unfortunately it doesn't work for me.
I tried to flash the zip via the recovery, but ended in another boot loop after reboot with attempt to enter the recovery again.
Sent from my Xperia L using XDA-Developers Legacy app
Click to expand...
Click to collapse
Make sure you're following the steps properly.
xleng said:
Hi again,
I just installed the official twrp app (version 1.15, build 28) and tried to flash the twrp image 3.1.1-0.
Twrp reported successful flashing, butafter reboot the recovery was not entered, but instead I had a bootloop again.
Prior to flashing, I did a backup of the existing recovery (containing twrp-3.0.2), after re-flashing the recovery backup resulted in a functional installation of twrp3.0.2 again.
Any recommendation? I'm using the XperiaL, C2105, white version.
The device actually was returned from Sony, eg was shipped without any provider branding, because the initial phone (which did have provider branding) had issues with the camera, which therefore has been sent to Sony within the guarantee period. Sony however did not repair the phone, but rather sent back a new and original Sony device.
In case any other information might be of interest, please let me know.
Would be great to be able to install twrp3.1.1 + LineageOS 14.1!
Actually it's not clear to me if LOS14.1 could be flashed with twrp3.0.2, since errors have been reported?
Sent from my Xperia L using XDA-Developers Legacy app
Click to expand...
Click to collapse
If you have working TWRP 3.0.2, you can simply flash the twrp-3.1.1-20171005-fota-taoshan.zip from HERE.

Hi again,
I try now another attempt. I take the "twrp-3.1.1-20171005-fota-taoshan.zip", saved in the SD card of the phone, which contains two items:
- folder "META-INF"
- file "twrp.img"
Using TWRP, version 3.0.2-0:
1) Menu Install
2) Select Storage -> Micro SDCard
3) Select twrp-3.1.1-20171005-fota-taoshan.zip
4) Swipe to confirm Flash
5) Adrian DC - TWRP Installer reports the following : "Flashing TWRP Recovery to FOTA... Done. Update Completed. script succeeded: result was [1.000000]; Update partition details...done"
6) Reboot system
7) Hit the vol-up during boot (especially during SONY logo)
8) Boot loop is entered.
I don't think that I have missed anything, did I?
Sorry to be a pain ....

xleng said:
Hi again,
I try now another attempt. I take the "twrp-3.1.1-20171005-fota-taoshan.zip", saved in the SD card of the phone, which contains two items:
- folder "META-INF"
- file "twrp.img"
Using TWRP, version 3.0.2-0:
1) Menu Install
2) Select Storage -> Micro SDCard
3) Select twrp-3.1.1-20171005-fota-taoshan.zip
4) Swipe to confirm Flash
5) Adrian DC - TWRP Installer reports the following : "Flashing TWRP Recovery to FOTA... Done. Update Completed. script succeeded: result was [1.000000]; Update partition details...done"
6) Reboot system
7) Hit the vol-up during boot (especially during SONY logo)
8) Boot loop is entered.
I don't think that I have missed anything, did I?
Sorry to be a pain ....
Click to expand...
Click to collapse
When you flash the zip, recovery log is generated. Can you give me that log? You can find it in "Advanced" tab.

If I read the log correctly, the dd command fails, because the ZIP is by 1 record too long for the partition.
At least the input record count is different than the output record count, which is strange.
I'm just thinking aloud if there could be a dependency with the host Maschine (at least with the ZIP file), so that the bit pattern might slightly differ due to differences in the file system types?
I believe this is the relevant part oft the log, though I can also send the complete log by PM:
==============================
==============================
| Adrian DC - TWRP Installer |
| Adrian DC - TWRP Installer |
==============================
==============================
- Flashing TWRP Recovery to FOTA...
- Flashing TWRP Recovery to FOTA...
about to run program [/sbin/dd] with 3 args
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel': No space left on device
32769+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 2.417855 seconds, 6.6MB/s
run_program: child exited with status 1
Done.
Done.
Update Completed.
Update Completed.
script succeeded: result was [1.000000]I:Updater process ended with RC=0
I:Legacy property environment disabled.
Updating partition details...
...done
I:Set page: 'flash_done'
Iperation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
Iperation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /external_sd/recovery.log

xleng said:
If I read the log correctly, the dd command fails, because the ZIP is by 1 record too long for the partition.
At least the input record count is different than the output record count, which is strange.
I'm just thinking aloud if there could be a dependency with the host Maschine (at least with the ZIP file), so that the bit pattern might slightly differ due to differences in the file system types?
I believe this is the relevant part oft the log, though I can also send the complete log by PM:
==============================
==============================
| Adrian DC - TWRP Installer |
| Adrian DC - TWRP Installer |
==============================
==============================
- Flashing TWRP Recovery to FOTA...
- Flashing TWRP Recovery to FOTA...
about to run program [/sbin/dd] with 3 args
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel': No space left on device
32769+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 2.417855 seconds, 6.6MB/s
run_program: child exited with status 1
Done.
Done.
Update Completed.
Update Completed.
script succeeded: result was [1.000000]I:Updater process ended with RC=0
I:Legacy property environment disabled.
Updating partition details...
...done
I:Set page: 'flash_done'
Iperation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
Iperation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /external_sd/recovery.log
Click to expand...
Click to collapse
Hi,
Thanks for the logs.
Something is not right here..
PHP:
16777216 bytes (16.0MB) copied, 2.417855 seconds, 6.6MB/s
Why 16 MB is getting copied while the recovery size is just 11.5-12 MB? This doesn't seem right.
If possible, can you run these command in device terminal? I need the output of these-
Code:
cat /proc/partitions
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
You can upload the output on hastebin.com
Thanks and regards,
STRYDER~007

cat /proc/partitions:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
254 0 262144 zram0
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 256 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 3456 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 65536 mmcblk0p23
179 24 19456 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 16384 mmcblk0p27
179 28 1228800 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 262144 mmcblk0p30
179 31 1671168 mmcblk0p31
179 32 4210671 mmcblk0p32
179 64 31472640 mmcblk1
179 65 31471616 mmcblk1p1
ls -al /dev/block/platform/msm_sdcc.1/by-name:
[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name
total 0
drwxr-xr-x 2 system root 680 2017-11-12 00:46 .
drwxr-xr-x 4 root root 740 2017-11-12 00:46 ..
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 FOTAKernel -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 LTALabel -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 alt_aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 alt_rpm -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 alt_s1sbl2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 alt_sbl2 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 alt_sbl3 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 apps_log -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 boot -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 cache -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 ftma -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 ftmd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 modem -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 ramdump -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 rsv -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 sdcard -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 system -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 userdata -> /dev/block/mmcblk0p31
I think the partition layout is normal. I did not previously try any modifications to the partition scheme, e.g. as suggested by some "hacks" to provide more storage to user data. I consider these as high risk (also many hard bricks have ben reported), and modify "only" the recovery and ROM area.
Best regards

xleng said:
cat /proc/partitions:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
254 0 262144 zram0
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 256 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 3456 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 65536 mmcblk0p23
179 24 19456 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 16384 mmcblk0p27
179 28 1228800 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 262144 mmcblk0p30
179 31 1671168 mmcblk0p31
179 32 4210671 mmcblk0p32
179 64 31472640 mmcblk1
179 65 31471616 mmcblk1p1
ls -al /dev/block/platform/msm_sdcc.1/by-name:
[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name
total 0
drwxr-xr-x 2 system root 680 2017-11-12 00:46 .
drwxr-xr-x 4 root root 740 2017-11-12 00:46 ..
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 FOTAKernel -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 LTALabel -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 alt_aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 alt_rpm -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 alt_s1sbl2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 alt_sbl2 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 alt_sbl3 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 apps_log -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 boot -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 cache -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 ftma -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 ftmd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 modem -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 ramdump -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 rsv -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 sdcard -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 system -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2017-11-12 00:46 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2017-11-12 00:46 userdata -> /dev/block/mmcblk0p31
I think the partition layout is normal. I did not previously try any modifications to the partition scheme, e.g. as suggested by some "hacks" to provide more storage to user data. I consider these as high risk (also many hard bricks have ben reported), and modify "only" the recovery and ROM area.
Best regards
Click to expand...
Click to collapse
Yes I was suspicious about that. It seems partitions are all fine. Okay, one last thing, can you follow these steps mentioned on official TWRP site and see if recovery installs properly?
https://dl.twrp.me/taoshan/twrp-3.1.1-0-taoshan.img.html
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Click to expand...
Click to collapse