Swapping back and recent apps buttons in LineageOS 14.1 - LeEco Le Max 2 Questions & Answers

Swapping back and recent apps buttons in LineageOS 14.1 - LeEco Le Max 2 Questions & Answers

Here's how it can be done.
Reboot into TWRP, mount /system in RW mode, fetch(1) /system/usr/keylayout/synaptics_dsx.kl and edit it.
Originally it looks like
Code:
key 158 BACK VIRTUAL
key 172 HOME VIRTUAL
key 580 APP_SWITCH VIRTUAL
You need to change it to
Code:
key 158 APP_SWITCH VIRTUAL
key 172 HOME VIRTUAL
key 580 BACK VIRTUAL
and then upload(2) back to your phone.
Code:
1. adb pull /system/usr/keylayout/synaptics_dsx.kl
2. adb push synaptics_dsx.kl /system/usr/keylayout/
Hopefully this feature will be implemented at the user level.

birdie said:
Here's how it can be done.
Reboot into TWRP, mount /system in RW mode, fetch(1) /system/usr/keylayout/synaptics_dsx.kl and edit it.
Originally it looks like
Code:
key 158 BACK VIRTUAL
key 172 HOME VIRTUAL
key 580 APP_SWITCH VIRTUAL
You need to change it to
Code:
key 158 APP_SWITCH VIRTUAL
key 172 HOME VIRTUAL
key 580 BACK VIRTUAL
and then upload(2) back to your phone.
Code:
1. adb pull /system/usr/keylayout/synaptics_dsx.kl
2. adb push synaptics_dsx.kl /system/usr/keylayout/
Hopefully this feature will be implemented at the user level.
Click to expand...
Click to collapse
Hello. Is it possible to edit this file on Android giving some editor root privileges?

Yes but you'll have to reboot your phone after that.

Registered just to thank you for this! I was trying to get used to the buttons being flipped in comparison to my previous phones, but just couldn't
In case anyone comes here and is as newbie as I am:
If you're unrooted/don't want to root and are worried by the previous post, I did it with an unrooted phone just fine. Just needed twrp and adb. That post is asking about editing directly on the phone, while OP's outlined method has you using your desktop and... I used notepad++ but I assume regular notepad will work too, just right click and "open with..." to edit the .kl file. By RW mode, OP means having system mounted in read/write mode, which twrp will do by default at least in the version I'm using which is 3.1.1-0-x2. Just don't check off the option to make it read only. By the way, it wouldn't over-write for me, so I deleted synaptics_dsx.kl in twrp then pushed the edited file.

Can someone help me do this!
In simpler terms can someone explain this to me?

Clarification of explanation
Dear birdie,
Could you perhaps elaborate on the "mount /system in RW mode, fetch(1) /system/usr/keylayout/synaptics_dsx.kl " instruction?
I am trying to disable the "recent apps" button on the Moto G3 in LineageOS 14.1, and I think if I map Home twice, (once more on `key 580` {or what the number on my type of device will be}), i have obtained that goal.
Any suggestions are appreciated, kind regards.
birdie said:
Here's how it can be done.
Reboot into TWRP, mount /system in RW mode, fetch(1) /system/usr/keylayout/synaptics_dsx.kl and edit it.
Originally it looks like
Code:
key 158 BACK VIRTUAL
key 172 HOME VIRTUAL
key 580 APP_SWITCH VIRTUAL
You need to change it to
Code:
key 158 APP_SWITCH VIRTUAL
key 172 HOME VIRTUAL
key 580 BACK VIRTUAL
and then upload(2) back to your phone.
Code:
1. adb pull /system/usr/keylayout/synaptics_dsx.kl
2. adb push synaptics_dsx.kl /system/usr/keylayout/
Hopefully this feature will be implemented at the user level.
Click to expand...
Click to collapse

Explicit intended steps.
After doing some research I think
mount system in RW (rewritable) mode and fetch(1) $/system/usr/keylayout/synaptics_dsx.kl$ and edit it.
Click to expand...
Click to collapse
can be performed with the following steps:
0. Commanders intend: mount system in RW (rewritable) mode:
1. Download minimal ADB and Fastboot.
2. Install TWRP and root on your phone
3. Steps: open adb on pc. Current location = \url{E:\somefolder\Minimal ADB and Fastboot_techbeasts\py.cmd
4. connect the phone with usb to pc.
5. Select mount in TWRP:
6. select \textbackslash system
7. press mount.
8. source for next step: \url{https://forum.xda-developers.com/xperia-z2/help/help-to-mount-rw-twrp-recovery-t3376485}
9. \url{https://askubuntu.com/questions/175739/how-do-i-remount-a-filesystem-as-read-write}
10. \url{https://stackoverflow.com/questions/28009716/how-can-i-remount-my-android-system-as-read-write-in-a-bash-script-using-adb}
11. finally the last link, the following command sequence appears to solve the issue:
Code:
# Script to mount Android Device as read/write.
# List the Devices.
adb devices;
# Run adb as root (Needs root access).
adb root;
# Since you're running as root su is not required
adb shell mount -o rw,remount /;
12. Commanders intend: fetch(1) $/system/usr/keylayout/synaptics_dsx.kl$ and edit it.
13. Source used to execute commanders intend: \url{https://forum.xda-developers.com/shield-tv/general/change-3rd-party-remote-key-layout-root-t3548871}
14. steps: adb shell \textgreater enter \textless
15. That shows
Code:
~ # <-[6
\end{verbatim}
\item ignore that weird stuff and just immediately after enter:
\begin{verbatim}
cat /proc/bus/input/devices
16. Now you will have a list of connected remote/controller, take a note of the Vendor number and the Product number.
17. ctrl+c to get out of the to me uknown, ~\# thingy
18. adb pull $/system/usr/keylayout$
19. that yielded for my moto G3:
Code:
E:\somefolder\Minimal ADB and Fastboot_techbeasts>adb pull /system/usr/keylayout
pull: building file list...
pull: /system/usr/keylayout/qwerty.kl -> ./qwerty.kl
pull: /system/usr/keylayout/Vendor_2378_Product_100a.kl -> ./Vendor_2378_Product_100a.kl
pull: /system/usr/keylayout/Vendor_2378_Product_1008.kl -> ./Vendor_2378_Product_1008.kl
pull: /system/usr/keylayout/Vendor_22b8_Product_093d.kl -> ./Vendor_22b8_Product_093d.kl
pull: /system/usr/keylayout/Vendor_1d79_Product_0009.kl -> ./Vendor_1d79_Product_0009.kl
pull: /system/usr/keylayout/Vendor_1bad_Product_f036.kl -> ./Vendor_1bad_Product_f036.kl
pull: /system/usr/keylayout/Vendor_1bad_Product_f027.kl -> ./Vendor_1bad_Product_f027.kl
pull: /system/usr/keylayout/Vendor_1bad_Product_f023.kl -> ./Vendor_1bad_Product_f023.kl
pull: /system/usr/keylayout/Vendor_1bad_Product_f016.kl -> ./Vendor_1bad_Product_f016.kl
pull: /system/usr/keylayout/Vendor_1949_Product_0401.kl -> ./Vendor_1949_Product_0401.kl
pull: /system/usr/keylayout/Vendor_18d1_Product_5018.kl -> ./Vendor_18d1_Product_5018.kl
pull: /system/usr/keylayout/Vendor_18d1_Product_2c40.kl -> ./Vendor_18d1_Product_2c40.kl
pull: /system/usr/keylayout/Vendor_1689_Product_fe00.kl -> ./Vendor_1689_Product_fe00.kl
pull: /system/usr/keylayout/Vendor_1689_Product_fd01.kl -> ./Vendor_1689_Product_fd01.kl
pull: /system/usr/keylayout/Vendor_1689_Product_fd00.kl -> ./Vendor_1689_Product_fd00.kl
pull: /system/usr/keylayout/Vendor_1532_Product_0900.kl -> ./Vendor_1532_Product_0900.kl
pull: /system/usr/keylayout/Vendor_12bd_Product_d015.kl -> ./Vendor_12bd_Product_d015.kl
pull: /system/usr/keylayout/Vendor_1038_Product_1412.kl -> ./Vendor_1038_Product_1412.kl
pull: /system/usr/keylayout/Vendor_0b05_Product_4500.kl -> ./Vendor_0b05_Product_4500.kl
pull: /system/usr/keylayout/Vendor_05ac_Product_0239.kl -> ./Vendor_05ac_Product_0239.kl
pull: /system/usr/keylayout/Vendor_0583_Product_2060.kl -> ./Vendor_0583_Product_2060.kl
pull: /system/usr/keylayout/Vendor_054c_Product_0268.kl -> ./Vendor_054c_Product_0268.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c532.kl -> ./Vendor_046d_Product_c532.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c299.kl -> ./Vendor_046d_Product_c299.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c294.kl -> ./Vendor_046d_Product_c294.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c21f.kl -> ./Vendor_046d_Product_c21f.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c21d.kl -> ./Vendor_046d_Product_c21d.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c219.kl -> ./Vendor_046d_Product_c219.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c216.kl -> ./Vendor_046d_Product_c216.kl
pull: /system/usr/keylayout/Vendor_046d_Product_b501.kl -> ./Vendor_046d_Product_b501.kl
pull: /system/usr/keylayout/Vendor_045e_Product_0719.kl -> ./Vendor_045e_Product_0719.kl
pull: /system/usr/keylayout/Vendor_045e_Product_028e.kl -> ./Vendor_045e_Product_028e.kl
pull: /system/usr/keylayout/Vendor_0079_Product_0011.kl -> ./Vendor_0079_Product_0011.kl
pull: /system/usr/keylayout/Generic.kl -> ./Generic.kl
pull: /system/usr/keylayout/AVRCP.kl -> ./AVRCP.kl
35 files pulled. 0 files skipped.
37 KB/s (49818 bytes in 1.285s)
20. All those files are for pre-built in controllers that you can connect the the phone, eg xbox 360 controller, snes controller etc. Except for AVRCP.kl and Generic.kl, these are used for the normal phone.
21. Change Generic.kl as AVRCP.kl says AVRCP.kl is not used anymore.
22. Copy the Generic.kl back:
Code:
adb root
adb disable-verity
adb reboot
(power down, boot into twrp again)
adb root
adb remount
adb push "layout file" /system/usr/keylayout (becomes in this case:)
adb push Generic.kl /system/usr/keylayout
adb reboot

birdie said:
Here's how it can be done.
Reboot into TWRP, mount /system in RW mode, fetch(1) /system/usr/keylayout/synaptics_dsx.kl and edit it.
Originally it looks like
Code:
key 158 BACK VIRTUAL
key 172 HOME VIRTUAL
key 580 APP_SWITCH VIRTUAL
You need to change it to
Code:
key 158 APP_SWITCH VIRTUAL
key 172 HOME VIRTUAL
key 580 BACK VIRTUAL
and then upload(2) back to your phone.
Code:
1. adb pull /system/usr/keylayout/synaptics_dsx.kl
2. adb push synaptics_dsx.kl /system/usr/keylayout/
Hopefully this feature will be implemented at the user level.
Click to expand...
Click to collapse
Thanks. This is the hint I needed to make APP_SWITCH work on a device I'm playing with (SM-T113NU)

Related

[Q] HID Bluetooth keyboard mapping on WB rom.

I want to change the mappings of my Bluetooth keyboard.
As it does not detect that i am using the screen in landscape mode. "annoying for directional keys"
So i tried to edit the system/usr/keylayout/qwerty.kl file
But it seems to knock out the keyboard commands entirely.
It still connects but it does not respond to input.
My question is.
Am i changing the correct file?
How can i make this into a flash-able file?
Please teach me O wise XDA developers.

anyone got any clue?

Bumping for hope..

WOOOO!!! figured it out.
in the folder: /System/usr/keylayout
Code:
adb shell
mkdir /sdcard/keylayout
mkdir /sdcard/keylayoutmodded
cp -f /system/usr/keylayout/* /sdcard/keylayout
2 - We set the memory card, putting the usb mode to "Access to the memory card."
3 - We go to / sdcard / keylayout and we will have to modify all the files there:
qwerty.kl
Important Note:
In these files, the structure is as follows:
Code:
key xxx ACTION EVENT
So ... For example if we change the search button to trigger the dialer instead of the search box, we have to change the lines:
Code:
key 127 SEARCH WAKE_DROPPED
key 217 SEARCH WAKE_DROPPED
For ...
Code:
key 127 CALL WAKE_DROPPED
key 217 CALL WAKE_DROPPED
They will see that beside the keys, or says nothing, or says or WAKE_DROPPED WAKE:
Wake: When the button is pressed while the device is inactive, this key is activated and triggers the application.
WAKE_DROPPED: When the button is pressed while the device is inactive, this is activated and triggers the NO key application.
4 - Once the mod, save the changes to / sdcard / keylayoutmodded (IS IMPORTANT NOT TO TOUCH THE FORMER BACKUP). Through adb (below) or root explorer, then move the files you've modified / system / usr / keylayout again and give the permissions 644 (rwrr), the usual ones, bah.
Code:
adb shell
su
mount -o remount,rw /dev/mtd/mtdblock6 /system
cp -f /sdcard/keylayoutmodded/* /system/usr/keylayout/
chmod 644 /system/usr/keychars/*
chmod 644 /system/usr/keylayout/*
mount -o remount,ro /dev/mtd/mtdblock6 /system
Correct me if this is true or not.

How did you get to connect with the keyboard at all? I cannot get a connection with my bluetooth keyboard. After I pair, it says "paired, but not connected" and from there I cannot connect, only unpair....?!? I'm on WB 4.0.4

REBOOTING: adb /data permission errors - USB debug mode resets

Just two things I've observed with rooting my NT:
the /data folder on my Nook Table resets on reboot, to cause commands like 'adb shell mkdir /data/<somename>' to fail.
To correct, I have to execute 'adb shell' and:
Code:
$ su root
# chmod 777 /data
# exit
$ exit
then resume any adb commands
I have to remove 'Auto Mount' and uncheck-check the 'USB Debbuging' box (top one in list) in Development settings after a reboot/power down.
The 'AppMenu' apk http://suipre.com/AppMenu.apk is great for doing this, but it does need to be done if I power down/reboot
Hope this helps someone!
Extra notes or hints welcome!
@Bharat: If I've posted this in the wrong place - please let me know

"Fake" Root

After dumping my X2 for a month, I came back & found out that they (the ones running 2.3.6) can be rooted now. Before, I had to follow the following instructions for a "Fake" root:
Extract the ADB-Fastboot package and root image to your C:\ Drive under a new folder titled “root”
Put your device into Fastboot mode: – Turn off your device. – Hold down the power button and downward volume button until you see “Fastboot” on your screen – Push the upward volume button
Connect your phone via USB cable. Allow Windows to install the new hardware if this is the first time you have used Fastboot mode.
Open your command prompt (Start >> run “cmd” >> enter)
Type the following commands
cd C:/root
fastboot flash preinstall root.img
fastboot reboot
Enable USB debugging (Settings >> Applications >> Debugging)
Type the following commands
adb shell
/preinstall/su
Allow Superuser access on the phone when prompted
Type the following commands
mount -o rw,remount -t ext3 /dev/block/mmcblk0p12 /system
cp /preinstall/su /system/bin/su
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
My question is, how can I undo what I did in order to root "correctly"?
Thanks.

ReservedOdm listing request

I am creating a list of the reservedodm fuse settings. its a set of numbers that refer to the programmable fuses embedded in moto phones (that i know of) that controls your ability to downgrade to different versions of android and can even list if your phone is currently unlocked.
at the moment this is purely for reference for possible future projects
if your willing to contribute to the thread please list the following in your post
*last sbf used including the version of android
*the newest sbf that has been applied to your phone at any time
*the highest version of android & moto version that has ever been on your phone
*version of android with moto version
*any update.zips used at any time
*specify whether phone is DX2 or MX2
*the print out from the reservedodm file
*system version
*kernel version
*anything else you wish to contribute
how to get reservedodm
Code:
[email protected]:/home/lrs# adb shell
$ su
# cat /sys/firmware/fuse/ReservedOdm
40000000000040006000100000000
you can also send me the contents of the fuse file (compress and upload or email to me)
please include the above information including sbfs, update.zips, system versions, kernel versions
example code to copy the fuses folder
Code:
# cp /sys/firmware/fuse /sdcard-ext/keep/
cp: /sys/firmware/fuse is a directory (not copied).
# cp -r /sys/firmware/fuse /sdcard-ext/keep/
# exit
$ exit
[email protected]:/home/lrs# mkdir fuses
[email protected]:/home/lrs# adb pull /sdcard-ext/keep/fuse /home/lrs/fuses
pull: building file list...
pull: /sdcard-ext/keep/fuse/ReservedOdm -> /home/lrs/fuses/ReservedOdm
pull: /sdcard-ext/keep/fuse/SecBootDeviceSelectRaw -> /home/lrs/fuses/SecBootDeviceSelectRaw
pull: /sdcard-ext/keep/fuse/SkipDevSelStraps -> /home/lrs/fuses/SkipDevSelStraps
pull: /sdcard-ext/keep/fuse/SwReserved -> /home/lrs/fuses/SwReserved
pull: /sdcard-ext/keep/fuse/SpareBits -> /home/lrs/fuses/SpareBits
pull: /sdcard-ext/keep/fuse/sku -> /home/lrs/fuses/sku
pull: /sdcard-ext/keep/fuse/SecureBootKey -> /home/lrs/fuses/SecureBootKey
pull: /sdcard-ext/keep/fuse/SecBootDeviceSelect -> /home/lrs/fuses/SecBootDeviceSelect
pull: /sdcard-ext/keep/fuse/SecBootDeviceConfig -> /home/lrs/fuses/SecBootDeviceConfig
pull: /sdcard-ext/keep/fuse/KeyProgrammed -> /home/lrs/fuses/KeyProgrammed
pull: /sdcard-ext/keep/fuse/JtagDisable -> /home/lrs/fuses/JtagDisable
pull: /sdcard-ext/keep/fuse/DeviceKey -> /home/lrs/fuses/DeviceKey
pull: /sdcard-ext/keep/fuse/kfuse_raw -> /home/lrs/fuses/kfuse_raw
pull: /sdcard-ext/keep/fuse/OdmProduction -> /home/lrs/fuses/OdmProduction
14 files pulled. 0 files skipped.
0 KB/s (633 bytes in 0.972s)
sbf used 2.3.6 ntelos (newest)
update.zip 45.0.23 ntelos (latest)
MX2
system: 45.0.43.MB867.ACG-nTelos.en.US
kernel: 2.6.32.9-00011-gbc368b9 [email protected] #2
reservedodm: 40000000000040006000100000000

Impossible to update xperia s after using prerooted 4.1

Hello,
I used the condi's flasher to get jelly bean a long time ago.
Now I wanted to have the last update from sony (R3 it seems) however the tablet says that there is no new updates (which is false). I have noticed that for my version number (or something like that, last info on the tablet ) I have "UNKNOWN (FR)".
Can you help me to update it?
Thanks

griotte said:
Hello,
I used the condi's flasher to get jelly bean a long time ago.
Now I wanted to have the last update from sony (R3 it seems) however the tablet says that there is no new updates (which is false). I have noticed that for my version number (or something like that, last info on the tablet ) I have "UNKNOWN (FR)".
Can you help me to update it?
Thanks
Click to expand...
Click to collapse
Download the latest version R3 for your region from:
http://forum.xda-developers.com/showthread.php?t=1687429
Copy the update to the root of the external SD card.
Now become the tricky part. To update successfully you will need to create some symlinks.
If this sounds like chinese to you, stop right here.
Use jappaj guide (I don't remember the correct post):
"
So, in order to create this symlink:
- Connect your Xperia to computer
- Start Command Prompt
- Start shell by typing in command "adb shell" (you need Xperia drivers installed and adb.exe from somewhere!)
- Then request root priviledges by typing in "su" - you should get prompt to your Xperia device which you need to accept
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
- Then you need to create this symlink to OTHER system partition if it is missing. To do this you need to figure out what partition is currently mount as /system, type in "mount |grep -i /system", mine:
/dev/block/mmcblk0p3 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
There are two partitions which contains system, /dev/block/mmcblk0p3 and /dev/block/mmcblk0p4. One is currently mounted and used, I refer this as CURRENT and another is unused, I refer this as OTHER. My CURRENT is /dev/block/mmcblk0p3 and OTHER will then be /dev/block/mmcblk0p4. Yours may be reversed.
- So create folder for OTHER system partition, type in "mkdir /data/local/tmp/sysother"
- Them mount OTHER to that folder, type in "mount -t ext4 /dev/block/mmcblk0pX /data/local/tmp/sysother" where X is of course correct number for OTHER
- Go to folder to which OTHER was mounted, type in "cd vendor
"
- Check what you have, type in "ls -l"
- Do you have vendor folder or symlink? I think flasher will create folder (first letter is d) while out-of-the-box we have symlink (first letter is l). At least I had symlink in CURRENT when I got my Xperia back from service. Some kind soul who has not used flasher could check this for us, what do you have in CUR*RENT and OTHER, please! If you do not have vendor folder or symlink, trying to flash OTA from recovery will fail (at least it fails for me)!
- If you do not have anything, just create symlink, type in "ln -s /datapp/vendor/vendor1/FI vendor". Copy region code from symlink within CURRENT partition, mine is FI as Finland, yours will depend on your region! Also use vendor0 for mmcblk0p3 and vendor1 for mmcblk0p4 (other words use vendor0 if your CURRENT had vendor1 and vice versa)!
- Shut down, reboot to recovery and try to flash JB.
"
Then boot to recovery and flash the R3:
"
Volume + (hold it down forever) press power ... when you turn it loose screen when sony logo appears (this is fast) press again and holding down ... if you've done well ... sony logo disappears and leaves as distorted, loose then you press power and repeatedly! Now you should see the recovery menu
"

Thanks for your help bg_man, I will try and update the post is everything is OK.
:good:
bg_man said:
Download the latest version R3 for your region from:
http://forum.xda-developers.com/showthread.php?t=1687429
Copy the update to the root of the external SD card.
Now become the tricky part. To update successfully you will need to create some symlinks.
If this sounds like chinese to you, stop right here.
Use jappaj guide (I don't remember the correct post):
"
So, in order to create this symlink:
- Connect your Xperia to computer
- Start Command Prompt
- Start shell by typing in command "adb shell" (you need Xperia drivers installed and adb.exe from somewhere!)
- Then request root priviledges by typing in "su" - you should get prompt to your Xperia device which you need to accept
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
- Then you need to create this symlink to OTHER system partition if it is missing. To do this you need to figure out what partition is currently mount as /system, type in "mount |grep -i /system", mine:
/dev/block/mmcblk0p3 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
There are two partitions which contains system, /dev/block/mmcblk0p3 and /dev/block/mmcblk0p4. One is currently mounted and used, I refer this as CURRENT and another is unused, I refer this as OTHER. My CURRENT is /dev/block/mmcblk0p3 and OTHER will then be /dev/block/mmcblk0p4. Yours may be reversed.
- So create folder for OTHER system partition, type in "mkdir /data/local/tmp/sysother"
- Them mount OTHER to that folder, type in "mount -t ext4 /dev/block/mmcblk0pX /data/local/tmp/sysother" where X is of course correct number for OTHER
- Go to folder to which OTHER was mounted, type in "cd vendor
"
- Check what you have, type in "ls -l"
- Do you have vendor folder or symlink? I think flasher will create folder (first letter is d) while out-of-the-box we have symlink (first letter is l). At least I had symlink in CURRENT when I got my Xperia back from service. Some kind soul who has not used flasher could check this for us, what do you have in CUR*RENT and OTHER, please! If you do not have vendor folder or symlink, trying to flash OTA from recovery will fail (at least it fails for me)!
- If you do not have anything, just create symlink, type in "ln -s /datapp/vendor/vendor1/FI vendor". Copy region code from symlink within CURRENT partition, mine is FI as Finland, yours will depend on your region! Also use vendor0 for mmcblk0p3 and vendor1 for mmcblk0p4 (other words use vendor0 if your CURRENT had vendor1 and vice versa)!
- Shut down, reboot to recovery and try to flash JB.
"
Then boot to recovery and flash the R3:
"
Volume + (hold it down forever) press power ... when you turn it loose screen when sony logo appears (this is fast) press again and holding down ... if you've done well ... sony logo disappears and leaves as distorted, loose then you press power and repeatedly! Now you should see the recovery menu
"
Click to expand...
Click to collapse

Hi,
In fact I have a strange situation :
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
I don't have this symlink. How can I create it?
Thanks
bg_man said:
Download the latest version R3 for your region from:
http://forum.xda-developers.com/showthread.php?t=1687429
Copy the update to the root of the external SD card.
Now become the tricky part. To update successfully you will need to create some symlinks.
If this sounds like chinese to you, stop right here.
Use jappaj guide (I don't remember the correct post):
"
So, in order to create this symlink:
- Connect your Xperia to computer
- Start Command Prompt
- Start shell by typing in command "adb shell" (you need Xperia drivers installed and adb.exe from somewhere!)
- Then request root priviledges by typing in "su" - you should get prompt to your Xperia device which you need to accept
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
- Then you need to create this symlink to OTHER system partition if it is missing. To do this you need to figure out what partition is currently mount as /system, type in "mount |grep -i /system", mine:
/dev/block/mmcblk0p3 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
There are two partitions which contains system, /dev/block/mmcblk0p3 and /dev/block/mmcblk0p4. One is currently mounted and used, I refer this as CURRENT and another is unused, I refer this as OTHER. My CURRENT is /dev/block/mmcblk0p3 and OTHER will then be /dev/block/mmcblk0p4. Yours may be reversed.
- So create folder for OTHER system partition, type in "mkdir /data/local/tmp/sysother"
- Them mount OTHER to that folder, type in "mount -t ext4 /dev/block/mmcblk0pX /data/local/tmp/sysother" where X is of course correct number for OTHER
- Go to folder to which OTHER was mounted, type in "cd vendor
"
- Check what you have, type in "ls -l"
- Do you have vendor folder or symlink? I think flasher will create folder (first letter is d) while out-of-the-box we have symlink (first letter is l). At least I had symlink in CURRENT when I got my Xperia back from service. Some kind soul who has not used flasher could check this for us, what do you have in CUR*RENT and OTHER, please! If you do not have vendor folder or symlink, trying to flash OTA from recovery will fail (at least it fails for me)!
- If you do not have anything, just create symlink, type in "ln -s /datapp/vendor/vendor1/FI vendor". Copy region code from symlink within CURRENT partition, mine is FI as Finland, yours will depend on your region! Also use vendor0 for mmcblk0p3 and vendor1 for mmcblk0p4 (other words use vendor0 if your CURRENT had vendor1 and vice versa)!
- Shut down, reboot to recovery and try to flash JB.
"
Then boot to recovery and flash the R3:
"
Volume + (hold it down forever) press power ... when you turn it loose screen when sony logo appears (this is fast) press again and holding down ... if you've done well ... sony logo disappears and leaves as distorted, loose then you press power and repeatedly! Now you should see the recovery menu
"
Click to expand...
Click to collapse

griotte said:
Hi,
In fact I have a strange situation :
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
I don't have this symlink. How can I create it?
Thanks
Click to expand...
Click to collapse
You have a directory or a symlink to other folder instead?
Delete it and create symlink to right folder. "FI" stands for Finland. Put a correct one for your location.
Symlinks are remover with "rm", dir with "rmdir". I'd rename if it's a directory, rather remove it.

bg_man said:
You have a directory or a symlink to other folder instead?
Delete it and create symlink to right folder. "FI" stands for Finland. Put a correct one for your location.
Symlinks are remover with "rm", dir with "rmdir". I'd rename if it's a directory, rather remove it.
Click to expand...
Click to collapse
Yes that the point. The symlink is on the OTHER partition.
Thank you for your help, can you help me for the instructions? Especially the symlink is in read-only mode.

griotte said:
Yes that the point. The symlink is on the OTHER partition.
Thank you for your help, can you help me for the instructions? Especially the symlink is in read-only mode.
Click to expand...
Click to collapse
You have to mount system R/W:
/data/local/tmp/busybox mount -o rw,remount /system

Hi,
i have the same problem than Griotte.
Isn't it possible to flash directly the last firmware (downloaded on the SD card ) by using the condy "all in one" ?
In fact i just want to update because i have the Sony sound dock SGP-SPK1, everything work except that the sound don't pass from the tablet to the dock... great Sony !
So i suppose that maybe if i update the tablet, the dock will work...
Sorry for my English and thanks for your help

Better Mobile App

welcome