…Enter suggestions to improve documentation in this category. Do not raise bugs or issues here…
please add information about when to install TWRP and which guide to follow. Currently, the documentation just says “In TWRP return to main menu” without ever mentioning it before.
Thanks for the suggestion. Will try to add this topic into the documentation.
I had difficulties installing the recovery img from the installation docs. What I did was installing the TWRP from:
and then installed e-dev with adb. It took me a few hours to figure this out. It was the first time I installed a different OS on a phone…
Can it be that the images are only a few megabytes?
From other devices I am used to much bigger image files.
Thank you
Thorsten
My Bad.
Please ignore.
I was visually distracted and just looking at teh *img Files.
Thank you
Throsten
Hi there,
I just installed /e/ on an Xperia 10 Kirin. @Manoj Everything went well but I have a suggestion for the “Unlocking the bootloader” part it’s written this :
- On the device, dial
*#*#7378423#*#*
(*#*#SERVICE#*#*
) to launch the service menu. - Go to
service info
>configuration
and checkrooting status
- you can only continue if it saysBootloader unlock allowed: Yes
. - Connect the device to your PC via USB.
- On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
- Follow the instructions on Sony’s official unlocking website to unlock your bootloader.
- Since the device resets completely, you will need to re-enable USB debugging to continue (Settings->About Phone->Build version, and then you can go to Settings->Developer opptions to enable USB debugging).
It’s missing this line, I think, between step 5 and 6
Use your code to unlock the bootloader of your device:
fastboot oem unlock <your_unlock_code>
Since it’s not my first time installing /e/ on a device, I knew something was missing and I had to do something to unlock the bootloader. Anyway I think it worth putting that on the documentation.
Also I couldn’t get back on the sony after unlocking the bootloader, it got stuck on the booting xperia, so I went back on fastboot mode and continue the installation and it worked. (So I skipped step 6 of unlocking the bootloader)
Thanks a lot for making this possible !!
Thanks for pointing this out. Will have it checked and add the line of code between the steps 5 and 6
Hello.
According to the documentation https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/#tutorial-step-3
fastboot oem unlock 0x<insert your unlock code>
“0x” is missing in eOS documentation
I’ve done it whithout “0x” and it worked
Looks like it’s still not part of the docs.
I followed these steps: https://www.maketecheasier.com/install-twrp-recovery-android-no-root/
which of course “reverted” the step that I did before that of installing the recovery image.
Hi there,
I did’t find any instructions for upgrading /e/, so I had a look at the instructions at lineageOS and figured out myself. All went well. Are there any plans for adding upgrade instructions to the /e/ manuals?
Thanks for your great work!
Hello Xyguma,
I have been trying to load /e/OS to my Sony Xperia 10 (Kirin, I3113) but to date without success so I was very interested when I read that you had managed to do so. I have followed the instructions as far as unlocking the device and now receive a message on the device when booting “Your device software cannot be checked for corruption. Please lock the bootloader.” So far so good and I can boot the device into fastboot mode but then nothing more happens. The device does not boot into recovery mode no matter how I try to do it. With the command “fastboot flash boot recovery-e-2.3-t-20240822427106-dev-kirin.img” nothing happens, neither on the device not the console. I tried the same proceedure with the device specific twrp file but also to no avail. I tried the command “fastboot boot twrp.img” which is suggested on the twrp site and get the message "Sending ‘boot.img’ (33460 KB) " on the console but then nothing happens, neither on the device nor the console. I just don’t seem to be able to boot into recover mode no matter what I do. Would you have any suggestions how I could remedy this? I would be very grateful for any constructive suggestions. For your information, the device has been reset and the most recent software has been loaded. The device is in developer mode with the USB debugging turned on and the mode “file transfer” set. The device is not rooted (I have not found a practical method to do this but it should not be necessary anyway, I think).
Thanks in advance for your comments.
Kind regards,
Paul
Hi everybody,
after quite a lot of searching and trying this and that (I am definitely not a pro in this area and practically everything I do is a case of trial and error) and came to one solution that worked for me with the Xperia 10 (I3113).
As mentioned above, I had unlocked the device, set developer mode, set USB-Debugging and the the Standard USB Mode to Data Transfer. With all this set up I had the problems mentioned above and the flashing just did not work. I went to the Sony developers site and downloaded EMMA, a flashing tool for Sony Xperia devices (only available for Windows, what a pain!) and flashed my device to the newest software version. I disconnected the device and turned it off. Then back to my trusted Linux computer and downloaded the device specific Recovery file ( recovery-e-2.3-t-20240822427106-dev-kirin.img), the for this device necessary Partition file (copy-partitions-20220613-signed.zip), the current system file (e-2.3-t-20240822427106-dev-kirin.zip) and lastly the device spicific TWRP file (twrp-3.7.0_9-0-kirin.img) which I renamed simply twrp.img.
Very important: instead of going through the adb command “adb reboot bootloader” to get the device into fastboot mode, I shut down the mobile and then holding down the “volume down” connected it to the USB cable and the device started into fastboot mode with the light green and not blue. On the computer I entered the “fastboot devices” command and got the following result:
$ fastboot devices
??? XFL
With that, I issued the command “fastboot flash boot Recovery.img” and to my surprise, this worked without a problem and gave me an OK result. I disconnected the device and holding the volume down and the power button, I could boot into the recovery menu. In the recovery menu, I went directly to “ADB Sideload” and chose it. I reconnected the device to the computer and issued the command “adb sideload copy-partitions-20220613-signed.zip”. ADB started up and started the sideload, which went very quickly.
Once this step was compleded, I disconnected the device and turned it off. Once again, holding down the volume down button I connected the device to the computer to get into the fastboot mode (the light is green, not blue) and issued the “fastboot flash boot twrp.img” to install twrp which took a minute but also ended with “OK”. With this done, I disconnected the device.
I restarted the device into recovery mode by holding down the “volume down” and “power” button and the device booted into the twrp recovery and I could follow the instructions starting from point 3 of the “Installing /e/OS from recovery” instructions (the device still not connected to the computer until the point: On the device in TWRP, select Advanced, ADB Sideload, then swipe to begin sideload). At this point I connected the device to the computer and issued the “adb sideload e-2.3-t-20240822427106-dev-kirin.zip” command and the sideload began. It took about 15 min to load and seemed to stall at 27% and then at 45% but in the end was completed. I disconnected the device and restarted it and it booted into the new system.
I hope that this will help somebody who might have run into the same problems as I did and, as I said, I am no expert. It could all have just been that I was not entering fastboot mode correctly in the first place. Maybe if I had shut down the device, held down the volume down button and connected it to the computer from the very beginning instead of always trying the “adb reboot bootloader” method, I would not have had any problems at all. Who knows, not me. In the end, I have /e/OS/ on my Sony Xperia 10 (kirin) and that is all I wanted.