Database Info

Recovery no longer allows me to select files from memory (twrp)

I updated now I can't do anything. Im able to book ROM and to boot into recovery but am no longer able to select anything while in recovery.. basically if i want to changes roms or whipe data and etc.. i can't do that anymore..
Is there a way to revert back to stock? ( bootloader is unlocked before this happened and rom is rooted)
Is there a way to fix this? same thing happens when i install clockworkmod recovery..
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4

let it boot and set for 30 min then reflash twrp and it works same thing happened to me

toolhas4degrees said:
let it boot and set for 30 min then reflash twrp and it works same thing happened to me
Click to expand...
Click to collapse
Can you recommend which version of twrp to use ? Link?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 4

I"m still trying to fix this issue.. any help would be great

dilfatx said:
I"m still trying to fix this issue.. any help would be great
Click to expand...
Click to collapse
twrp 2.5 is the only one that has no issues as of now.

FIXED!
After doing some more extensive reading and trials and errors.. these two threads where helpful
[UNLOCKED BL] Method 2: Update using fastboot
Notes:
You will keep all your data
This is the best method to update your tablet if you want to keep all your data, and the safest one
Ensure you have the correct drivers for the tablet installed on your computer, or you will have a "waiting for device" error
To update using fastboot, follow this steps:
If you don't have fastboot yet, download it from here an unpack it somewhere on your computer
Extract the Asus firmware file and put the blob file inside fastboot folder
Open a command line on fastboot folder (write "cmd" on Windows search bar at the Start menu, and then
Code:
cd "FOLDER WHERE YOU EXTRACTED FASTBOOT"
, or you can just use SHIFT + RIGHT CLICK on the folder and select "Open command line window here" or something like that)
Reboot the tablet holding the volume down key until you see some icons. Use the volume down key to select the USB icon and then volume up to select it
Connect the tablet to the computer if you didn't do so
Write
Code:
fastboot -i 0x0B05 flash staging blob
, hit enter and wait until it completes
Hold the power button for 10 seconds to reboot the tablet
You are now updated to Android 4.2
Click to expand...
Click to collapse
and to install recovery I used this step from the same thread
[UNLOCKED BL]-- Installing TWRP (Recovery) --
Since this new update brings a new bootloader, older recovery versions from 4.1 won't work at all. Don't try to flash one!
This guide will give you a recovery that works just fine on the new bootloader. And yes, it can read/write to an external SD just fine. Follow this steps to install the new recovery on your device:
Connect the tablet to the computer
Reboot the tablet using the proper button on the power menu, holding Volume down until you see three icons (RCK, Android and Wipe Data)
Download this file and unpack it (it contains fastboot and a version of TWRP 2.5.0.0 that works with the new bootloader)
Open a command line on the extracted folder (you can use the instructions I wrote in Method 2 if you don't know how to do this) and type
Code:
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for the script to complete. Once it is done, reboot the tablet by holding volume down and power button for 10 seconds or using
Code:
fastboot reboot
on the command line. Don't enter recovery directly!
You have now the new recovery for Android 4.2 .
Click to expand...
Click to collapse
from [GUIDE][14/09]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices and it was successful using this specific method :laugh:

dilfatx said:
After doing some more extensive reading and trials and errors.. these two threads where helpful
and to install recovery I used this step from the same thread
from [GUIDE][14/09]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices and it was successful using this specific method :laugh:
Click to expand...
Click to collapse
Thank you for this, I have had to go back to 2.4.4 because it was the only working one, going to try this when I'm home.
Got it working (updated from 2.4.4 to 2.5.0 finally made it work thanks and now my external SD can finally be used going to buy one only for backups

frankgreimes said:
Thank you for this, I have had to go back to 2.4.4 because it was the only working one, going to try this when I'm home.
Got it working (updated from 2.4.4 to 2.5.0 finally made it work thanks and now my external SD can finally be used going to buy one only for backups
Click to expand...
Click to collapse
no problem

[Q] Nexus 5 Bricked! HELP!!! URGENT!

I'm kind of screwed and It's not even my mistake, I guess.
I clean flashed the Mahdi Update 25/04 yesterday earlier I had 03/03. In the morning I experienced 2 -3 random reboots and later only one random reboot after which my phone won't boot (bootloop). When i enter bootloader, it automatically selects "start" and boots into system and then reboots.
Once i got the chance and my phone booted fully. But then when I selected reboot into recovery so that i can restore a NAND. IT reboots, the team win logo shows up and then the cycle repeats.
Basically, i don't have access to recovery, my bootloader isn't stable (i.e. it automatically boots without selecting) so I'm unable to flash a stock img as of now. If and when my Nexus fully boots into system it stays the same for about 1 hr if i have any luck. PLz help.
From India. Unlocked Bootloader and custom Rom "Mahdi".

Have you tried using add to boot into recovery? If not also try to getting a logcat when it reboots, those will give us a little more of a general idea of what is actually happening.

First thing don't panic. You can't brick a nexus. You should be able to get into bootloader (volume down + power button) use Wugs Nexus Root toolkit from XDA forum. reload stock ROM in fastboot mode. I have done this lots of time. It's a draw back to being a tinkerer just can't leave well enough alone.

It sounds like your power bottom might be stuck to be honest.
Sent from my Nexus 5 using Tapatalk

nyterage said:
Have you tried using add to boot into recovery? If not also try to getting a logcat when it reboots, those will give us a little more of a general idea of what is actually happening.
Click to expand...
Click to collapse
I managed to somehow get into my bootloader and flashed the following
1. bootloader.img
2. radio.img
3. system.img
4. stock kernel (boot.img)
5. twrp recovery.img
I skipped userdata,img as i need to save my data.
I then went into recovery and did a factory wipe (not including internal storage)
My stock rom booted BUT the setup screen showed up and during the setup process it rebooted again and I couldn't mount my storage to backup.
MY MAIN PRIORITY IS TO COPY THE CONTENTS OF MY SD CARD Before flashing the whole stock image (including userdata)
Now when I type "adb version" in cmd I get Android Debug Bridge Version 1.0.31 but when I type "adb devices" whilst my phone is in fastboot mode, it doesn't list my phone. So i'm unable to "adb pull /mnt/sdcard"
I'm in the same situation with rare access to B/L (based on luck) and Recovery.
Plz tell me what to do when I am able to connect in bootloader mode (fastboot)
IF required I can upload a video showing that what problem I am facing.

scuccria said:
I managed to somehow get into my bootloader and flashed the following
1. bootloader.img
2. radio.img
3. system.img
4. stock kernel (boot.img)
5. twrp recovery.img
I skipped userdata,img as i need to save my data.
I then went into recovery and did a factory wipe (not including internal storage)
My stock rom booted BUT the setup screen showed up and during the setup process it rebooted again and I couldn't mount my storage to backup.
MY MAIN PRIORITY IS TO COPY THE CONTENTS OF MY SD CARD Before flashing the whole stock image (including userdata)
Now when I type "adb version" in cmd I get Android Debug Bridge Version 1.0.31 but when I type "adb devices" whilst my phone is in fastboot mode, it doesn't list my phone. So i'm unable to "adb pull /mnt/sdcard"
I'm in the same situation with rare access to B/L (based on luck) and Recovery.
Plz tell me what to do when I am able to connect in bootloader mode (fastboot)
IF required I can upload a video showing that what problem I am facing.
Click to expand...
Click to collapse
To use adb pull you have to enter the recovery. You need universal naked usb driver 0.73 to make adb work in recovery. If you are on windows 8 or 8.1 you have to turn off the driver signiture enforcement befote installing the universal naked usb driver 0.73
Tapatalk-kal küldve az én Nexus 5-el

El Daddy said:
It sounds like your power bottom might be stuck to be honest.
Click to expand...
Click to collapse
I agree. It's a malfunctioning power button due to several reasons (moisture, drops, etc.). I had this on my Nexus S.

Can't Update to 11.0-XNPH38r Incremental (Chinese OPO)

So I bought a Chinese OnePlus One, and it came pre-installed with CM 11 version 11.0-XNPH33r.
Connected to wifi, and got the system update for 11.0-XNPH38r Incremental, so I click download and install.
It reboots phone, then it loads ColorOS recovery looking screen with Chinese written on it and a green loading bar, then The CM splash icons comes back and loads. (alien looking guy with an arrow circling around his head)
After all that, I go to check the version and I'm still stuck at 11.0-XNPH33r!
I tried manually doing it from ColorOS recovery with 11.0-XNPH38r Incremental zip file, it installs about 3/4 of the way and then fails.
My Kernel Version is : 3.4.0-cyanogenmod-g0ad30e5
My ColorOS Recovery Version is : 1.2 (Rooted)
I've been looking around the forums, and I see people manually updating using TWRP which I don't have.
Can someone please help me, and if you have a solution can you please give me a step by step direction since I'm new to flashing/rooting and this phone.

I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
It contains instructions on how to unlock your bootloader and install TWRP recovery (sections 1 and 2). Before doing anything though you should check the status of your bootloader because it might already be unlocked. You'll need to follow the instructions at the top of the guide to install your phone drivers and also adb/fastboot via the Android SDK. Once you have done that you can boot your phone into fastboot mode (hold power + volume up), connect your phone to your PC via usb cable, open a command prompt from your fastboot folder (shift + right click anywhere within the foler, then select open command prompt here), and issue this command:
Code:
fastboot oem device-info
Please post the results here.

Thanks man, I'll try that out.

timmaaa said:
I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
It contains instructions on how to unlock your bootloader and install TWRP recovery (sections 1 and 2). Before doing anything though you should check the status of your bootloader because it might already be unlocked. You'll need to follow the instructions at the top of the guide to install your phone drivers and also adb/fastboot via the Android SDK. Once you have done that you can boot your phone into fastboot mode (hold power + volume up), connect your phone to your PC via usb cable, open a command prompt from your fastboot folder (shift + right click anywhere within the foler, then select open command prompt here), and issue this command:
Code:
fastboot oem device-info
Please post the results here.
Click to expand...
Click to collapse
TY for you help. I manage to get a custom recovery (TWRP), but I still can't update past 33R, when I update I get "E:Error executing updater binary in zip '/cache/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
I also have this phone SuperSU fully rooted I think

TheOneinNeed said:
TY for you help. I manage to get a custom recovery (TWRP), but I still can't update past 33R, when I update I get "E:Error executing updater binary in zip '/cache/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
I also have this phone SuperSU fully rooted I think
Click to expand...
Click to collapse
Go to section 8 of my guide and flash the stock images. Make sure you remove the -w of the last command though or it'll wipe all your user data.
Transmitted via Bacon

timmaaa said:
Go to section 8 of my guide and flash the stock images. Make sure you remove the -w of the last command though or it'll wipe all your user data.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks man. I actually tried the flashing of 44s on the guide you sent me and it worked. Sorry for my last reply. You've been a great help and my phone is up to date.
Two last question if you don't mind. When the new update comes, can I install through Settings> About Phones> System Updates
or do I have to do something similar to the flashing I just did
after flashing my custom recovery is gone (TWRP) and the Cyanogen Mod Recovery took its place. Should I leave it like that or get TWRP and if TWRP is the answer, do I use the same method I did installing the custom recovery?

You should now have no problems receiving automatic updates through the settings menu. You can leave the stock recovery if you want to, or you can flash TWRP again. If you don't intend on flashing any custom ROMs or mods then the stock recovery should suit you just fine. Flashing a recovery is done via fastboot.
Code:
fastboot flash recovery twrp-2.8.4.1.img
(where the recovery filename is twrp-2.8.4.1.img)

timmaaa said:
You should now have no problems receiving automatic updates through the settings menu. You can leave the stock recovery if you want to, or you can flash TWRP again. If you don't intend on flashing any custom ROMs or mods then the stock recovery should suit you just fine. Flashing a recovery is done via fastboot.
Code:
fastboot flash recovery twrp-2.8.4.1.img
(where the recovery filename is twrp-2.8.4.1.img)
Click to expand...
Click to collapse
Thank you for your time and effort to help.
I appreciate it a lot. Thanks again!

Completely stock OnePlus One stuck in bootloop after latest CM OTA update

Hi everyone,
I'm hoping you can help me. I've had a OnePlus One since August 2014, completely stock. Never modded it, never 'flashed' anything, never installed anything outside of the Google Play Store. Always installed the official OTA updates as they pop up on the phone itself. Basically a reeeeealllly boring android user!
So Thursday morning (09/06/2016) I got a notification that a system update was downloaded and ready to install. Clicked install, the process began, phone rebooted as per usual. However, on the install progress screen (the green android with the spinning cogs), about one third of the way through the phone freezes. About 20 seconds later the phone reboots itself and then tries to install the update again. Freezes. Reboots. Tries to install. Freezes. Reboots. Tries to install.... I think you get the idea. It was doing this for a couple of hours before I checked it.
I'm moderately tech-savvy but never really got involved with android modding, rooting or flashing. So I'm a bit confused as to why my completely stock phone is stuck in a bootloop after installing an official CyanogenMod OTA update. The current status of my phone is that I can only boot into Fastboot mode via VolUp + Power. I can get my computer to detect my phone in Fastboot mode, however it informs me that my bootloader is locked. Attempting to boot into recovery mode via VolDown + Power just starts the update install and enters the bootloop.
I've done some research in to flashing a recovery image or manually applying the OTA update. One problem I've noticed is that I have absolutely NO idea what version of Android / CM my device was at before the update, and I have NO idea what version it was trying to update to. I do know that it was some version of Marshmallow before it broke. I've had no issues with the phone before this, aside the occasional self-reboot.
I REALLY want to keep all my data (pictures, contacts etc.) and am very nervous about actually doing anything because I have very little idea as to what I'm really doing.
Can anyone offer any advice on how to get my phone to boot/update/recover through Fastboot with a locked bootloader and without losing any data?
Thanks,
Stormin'
AKA the "HOW DO I PLAY BOOM BEACH NOW?!" guy
Edit: I solved my issue. It might work for you too, permalink to my post (#9) below: http://forum.xda-developers.com/showpost.php?p=67278091&postcount=9

Are you able to get into recovery mode? If so, you should be able to just flash a new ROM. Sideload one using the adb push command, wipe your data (this will clear settings, apps, etc. DO NOT SELECT SD CARD - that will wipe your personal files including your photos). Then install. Hopefully it should all work fine.
If you can't access the recovery can you access the bootloader sceen (the one with the big green bugdroid)? Then I'd suggest using Fastboot to install a new recovery. Then try the above.
If you can't even get to that stage you're screwed, just like me (unless anyone has any ideas). I've had soft bricks many times before but today I can't even get to the bootloader screen. ADB says the phone is offline. The screen is back and flickers on for a split second every now and then. Bloody CM Updater.

As IBM9001 has said, if you can get into recovery - even being stock - you can still clear your cache - don't do a full factory reset, just the cache, this may help, but even if it doesn't it still rules out one option.

I can't access recovery mode, using the key combo it just boots straight into the installer.
I've got a support ticket open with OnePlus and a scheduled remote assistance tomorrow. However from the preparational email it looks like they are going to factory reset the phone and then clean install CM. They've instructed me to make sure that all my files are backed up... I assume this means I will lose them.
Is there ANY way just to access or pull the photos off my phone? That's the most important bit. Dropbox hit its storage limit at the beginning of 2015 and I refused to pay, so now I have 18 months worth of pictures that I have no other copies of on death row
The only thing I can access is Fastboot...
Edit:
ibm9001 said:
If you can't access the recovery can you access the bootloader sceen (the one with the big green bugdroid)? Then I'd suggest using Fastboot to install a new recovery.
Click to expand...
Click to collapse
I can boot into Fastboot mode, and plugging my phone into my PC works i.e. it is recognised. I have the fastboot .exe and USB drivers, and can issue commands to my phone through cmd such as
Code:
fastboot reboot-bootloader
which works.
How do I use a recovery .img through Fastboot? or can I pull the contents of the sd card through Fastboot?

Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..

Hi guys,
I have the same issue!
If I flash a new recovery from fast boot will I lose my data on sdcard?
Thanks.
Sent from my iPad using Tapatalk

masterjigar said:
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Click to expand...
Click to collapse
I cannot boot into recovery mode, unfortunately

masterjigar said:
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Click to expand...
Click to collapse
I'm currently having a very similar issue, but my phone completed the update. It's just stuck in a reboot/"optimizing apps" loop. I can boot into recovery and I tried to clear cache, but It's still just optimizing apps then rebooting and optimizing again over and over. Do you think your suggestion would help me too?

Wooooo, I've fixed it! I don't know why what I did fixed the issue (probably bypassed something) but my phone is up and running again! First thing I'm doing is making a freakin' backup!
So I was just trying everything in desperation. So that others can attempt to fix the same problem, here's what I did:
1. State of phone was either boots normally and crashes when installing update, or boots into fastboot. Would NOT boot into recovery!
2. Booted into fastboot using key combo (hold Volume Up, then Power Button)
3. Attached phone to computer via data usb lead
4. Started up cmd console, used command "fastboot devices" to check that device was recognised (note you need the fastboot files and USB drivers etc., Google it if you're not sure)
5. Used command "fastboot continue" to continue with 'autoboot'. This rebooted my phone but skipped the installer and went to the 'optimising apps' stage. Left phone alone for a couple of hours but it got stuck in another bootloop optimising apps, rebooting, optimising apps and so on.
6. Turned phone off, then booted normally with just the power button. This started the update install again except it didn't crash, and completed the update install. Then it optimised the apps again (albeit with a different total app count) and once finished, phone starts up normally.
Thanks for all the suggestions everyone! Happy to have my phone back. Now to go through the half-dozen or so voicemails I've collected over these last few days... great.

Hi guys,
@stormin, congrats!
@masterjigar, so you didn't lose the data like photos etc. doing so?
I can boot to recovery, but can't connect by PC to it.
In fast boot mode my PC sees it as well as in dab sideload mode.
I haven't the boot loader unlocked then I have to do it first, right?
But cyanogen site says that unlocking the boot loader will wipe all the device data.
Is there any way get the photos and other files back?
Thanks.

From the FAQ:
Q4a: Can I flash ROMs or SuperSU or anything else with the stock recovery?
No, the stock recovery can only flash zips that are signed by CM, this means official updates only. You need a custom recovery to flash anything else.​
Click to expand...
Click to collapse
Does it mean I can flash an official CM firmware without unlocking the boot loader?
Thanks.

hibernick said:
Hi guys,
@stormin, congrats!
@masterjigar, so you didn't lose the data like photos etc. doing so?
I can boot to recovery, but can't connect by PC to it.
In fast boot mode my PC sees it as well as in dab sideload mode.
I haven't the boot loader unlocked then I have to do it first, right?
But cyanogen site says that unlocking the boot loader will wipe all the device data.
Is there any way get the photos and other files back?
Thanks.
Click to expand...
Click to collapse
That's what adb sideload is all about. It will give you temporary adb access (which is always after unlocking bootloader and root). So you can also flash xip via sideload. Without losing data and media..

Same problem, Also PC not detecting my phone
Hey Guys, I am Stuck at the same thing at Bootloop. But to do anything further I need to connect my phone to the PC. I haven't been able to connect my phone to PC since the time I have got the phone. I tried all available drivers and even tried different cables. I dont know what has been left out to try.
If any one has a working driver pls share the link. Its been three days now that my phone is dead.
Pls help!!
Thanks in advance.

masterjigar said:
That's what adb sideload is all about. It will give you temporary adb access (which is always after unlocking bootloader and root). So you can also flash xip via sideload. Without losing data and media..
Click to expand...
Click to collapse
can I flash this cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img with the sideload and get adb working over usb?
Thanks

hibernick said:
can I flash this cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img with the sideload and get adb working over usb?
Thanks
Click to expand...
Click to collapse
You can't adb sideload .img or a partition.
You have to use fastboot.
Code:
fastboot flash boot boot_img_name.img
or
Code:
fastboot boot boot_img_name.img

saurav007 said:
You can't adb sideload .img or a partition. You have to use fastboot.
Click to expand...
Click to collapse
Yes but then I have to unlock my bootloader first. And unlocking bootloader erase all the user files....
Is there other way to to run cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img on the devise?

The Ultimate guide to flash and root Xperia L (aka, taoshan)

This thread will guide you to flash a custom recovery, Root the device, flash custom ROMs. Firstly, read the entire post and then start your work.
I am a noob. But I have a little experience of rooting and flashing. This device gave me nightmares which are less than as compared to the Xperia Sola which I bricked some years back.
My device has a problem. It does not help install twrp with the traditional ways we know like we can see in the Official TWRP website using "dd" method, the Cyanogenmod link using fastboot commands, the Flashify method, the RecoveryApp method whose apk I never found and the Recovery Installer Utility.
I came to know that either my phone don't have the recovery partition or the phone is overriding all the commands.
Using fastboot commands would give the error like in this post.
Using Flashify would tell me there's no recovery partition found. Rashr would complete the flash process but after booting to recovery, there was no TWRP, just the stock Android recovery.
If you read carefully on the twrp page of XL, there's a line which caught my attention late enough.
It means that TWRP may not work on your device unless you install other custom software as well.
Click to expand...
Click to collapse
Flashing custom kernels with flashtool is easy and they come with recovery pre-installed and lots of amazing stuff, but they won't do any good with the stock ROM. I've tried the Extended stock kernel, the Phantom Kernel and the Thunderzap 4.15.
After surfing the web and forums of other devices, I found that there is a chance I can fix things by updating/repairing software via PC Companion. But something happened and repair also failed.
I can't tell the reason why this happened. And I didn't store the logs. But with trial and error I found some workarounds.
Actual Methods start here
Rooting the device
If you only want to root your device for various reasons, then you will need nothing but a Rootkit. Check out this post about Rooting Xperia L.
But if you are planning to install custom ROMs for your device, then skip this rooting step. It won't be necessary for this condition.
Flashing custom recovery
*Try this method only if above-mentioned method fails*
1. Download TWRP 3.2.1 img. The 3.2.2 and 3.2.3 versions work perfectly but they caused the screen to flicker like hell on my device. Rename the file to 'twrp.img'
2. Download and install adb and fastboot drivers system-wide.
3. Connect your device to PC via USB cable and enabling USB-debugging mode.
4. Open Windows Powershell/Command Prompt in the twrp download directory by pressing Shift and clicking right mouse button.
5. Use fastboot command on stock ROM without root and Unlocked Bootloader. Instead of flashing twrp image to recovery, flash to boot. Use the code:
Code:
adb devices
adb reboot fastboot
Wait for device to boot into fastboot mode. A blue LED will flash when connected.​
Code:
fastboot flash boot twrp.img
fastboot reboot
After reboot, don't boot to system. Boot to recovery by pressing volume up repeatedly when pink LED glows. Stop when device vibrates and LED color changes
Flashing custom ROMs
Once the recovery is installed, everything becomes easy. you can find different custom ROMs on the device page here on XDA.
My favorite one is The resurrection Remix Nougat. It is stable enough to be your daily driver. You can head to that page and follow their instructions. But I will also provide steps here.
When in TWRP after the last step, move the downloaded zip file of the ROM and GApps you want to install to the storage of the device by simply connecting via USB.
After that, in TWRP click on Wipe->Advanced->Tick on System, Cache, Dalvik cache. Then Do swipe to begin wipe.
After wipe, go back to main menu. Tap on install, select from the list the ROM zip. then tap on Add more zips and select the GApps zip and then Swipe to start flashing.
After flashing, reboot to system. The first boot takes time. Don't panic if it won't boot.
Install TWRP to FOTAKernel
After booting to your new ROM, you can install the TWRP to your FOTAKernel.
This can be done as following:
Get the downloaded TWRP img file and push it to the device using command line. Open command prompt in the TWRP directory and type,
Code:
adb root
adb wait-for-device
adb push twrp.img /tmp/twrp.img
Now extract the TWRP image to the FOTA partition code,
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now reboot to recovery
Code:
adb reboot recovery
Note that custom ROMs often come with Root access inbuilt. If your ROM happened to be not, and your ROM is based on Lollipop or later version of Android, you can root with Magisk. Just read carefully before proceeding.
Comments are welcome!

Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devices​adb reboot fastboot "​
I think my Sony Xperia L C2105 does not have the fastboot mode.
Here's what I did:
Drivers for Xpleria L are installed.
The bootloader is unlocked (I think!)
1 - installed 15-second ADB
2 - open Windows power shell
3 - Command: adb devices
Response is: "List of devices attached: ZH8001ADB3 device"​
4 - Command: adb reboot fastboot
Response is: long pause, phone booted but in normal mode, and light is red ...!​
5 - Command: fastboot flash boot twrp.img;
Response is: "<waiting for device>";
- phone still running in normal mode and the light is red.
- few minutes later, the phone is charging with green light present.​
I think the phone is rooted.
I used the code provided by the Sony website to unlock the bootloader.
Using the Root Checker Basic app, I get the info: "Congratulations! Root access is properly installed on this device!"
But if I type in the dialer *#*#7378423#*#*, and go to Service info > Configuration > Rooting status is "Boootloader unlock allowed" !!
Is that why it does not work?
I tried switching it off and doing Boot into Xperia L Fastboot Mode Using HARDWARE BUTTONS, but the phone is dark, with no picture, and the led turns blue.
Using the command:
PS C: \ adb> adb devices
List of devices attached
PS C: \ adb>
I've been trying to do that for a few days now and I still have not managed it, even using other advice.
Can someone tell me what to do?
Thank you in advance.

Everterra said:
Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devices​adb reboot fastboot "​
I think my Sony Xperia L C2105 does not have the fastboot mode.
.......
Click to expand...
Click to collapse
1. When in fastboot mode, you should type in cmd "fastboot devices" to check the device connectivity. If you can't, then connect using hardware keys.
2. Blue light indicates that you are in fastboot mode. If list of attached devices are blank, that means drivers are not installed (properly). Connect your phone again in fastboot mode and check your drivers page, Win+X > M (I am assuming you must be on windows). There must be a tiny yellow triangle on your device's name. Right click on it and uninstall it and remove device. Try again installing drivers from the flashtool's folder. Disable driver signature enforcement if you are having trouble going the straight way.
3. Your bootloader is still locked because if it had unlocked then the message displayed would have been, "Bootloader Unlocked: Yes" or something like that. Try flashing your stock ROM via Flashtool. Wipe cache and data while flashing. After flashing stock Rom, try unlocking bootloader again. I believe you are using Flashtool.
4. If you are rooted, then you must have any SuperSU app installed on your device. And it's all good even if you are rooted.