Database Info

[Q] Stuck on Google logo. Unable to push image file to phone... Please help.

Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.

looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM

Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!

nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.

leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...

leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.

Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......

Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.

You need the drivers.

albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.

Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?

leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782

ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.

leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?

nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".

Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?

kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.

the same issue for me. is there any working solution for that?

I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147

GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing

Not Booting in Bootloader

I buy this phone few days ago and wanted to install cm14.1 and read the procedure all but when i try to use adb and unlock bootloader im not able to or my device not getting detect by adb it dose when i use usb tethering but i tried to reboot bootloader no luck then again i tried to boot in stock recovery and select to reboot bootloader it not getting me to fast boot screeen how i can make things go and unlock the bootloader and install twrp and install cm14.1 sorry im new to this device

vincy009 said:
I buy this phone few days ago and wanted to install cm14.1 and read the procedure all but when i try to use adb and unlock bootloader im not able to or my device not getting detect by adb it dose when i use usb tethering but i tried to reboot bootloader no luck then again i tried to boot in stock recovery and select to reboot bootloader it not getting me to fast boot screeen how i can make things go and unlock the bootloader and install twrp and install cm14.1 sorry im new to this device
Click to expand...
Click to collapse
Why choosing hard method
Install kingroot .
Root your phone.
Install flashify
Download twrp IMG
Flash it using flashify
You r done
Like if helpful

Thanks but I made it work actually the screen was in fastboot I wasn't knowing..
And about rooting kingroot is the worst way to root it dosent gives you the Complete root privilege its something like half rooted go for supersu allways

vincy009 said:
Thanks but I made it work actually the screen was in fastboot I wasn't knowing..
And about rooting kingroot is the worst way to root it dosent gives you the Complete root privilege its something like half rooted go for supersu allways
Click to expand...
Click to collapse
Half rooted like what? Example?

U have to download Universal ADB driver from XDA or Google it.
Firstly install adb drivers then download twrp 3.0.2 from twrp official site.
Put files in C:/adb/
Right Click + Shift on adb folder
Then choose command prompt
Open developer options
Enable OEM Unlocking
Enable USB debugging
Attach cable to phone
Phone will shows option
Tick and press OK
Goto command prompt
Commands
abd devices
It shows your device is connected or not
If device shows then type command
adb reboot bootloader
Device will be restarts and stuck on logo or it will shows fastboot mode
Type command
fastboot devices
Your device will be show here
Type command
device oem unlock
It shows message Okay
Your device is unlocked now
Type command
fastboot flash recovery twrp_jalebi.img ( ur twrp name)
Type command
fastboot reboot
Your device is unlocked now.
Now download supersu.zip and install it with twrp
Note:Flash supersu.zip is only required for lollipop version.
In marshmallow and noughat you don't need to flash supersu. If you do same then you will be got a device with bootloop.
In 6.0.1 and 7.0 the root access is already installed . you can got it from developer mode.
Hit thanks if I give you right instructions.

TWRP recovery menu not showing

hi, im new in this android arena and this is my first time using smartphone so please forgive my noobness.
i want to root my phone Xiaomi Redmi 5A and i follow some tutorial on youtube where he told to use Minimal ADB & fastboot, TWRP, lazyflasher noverity and lastly Magisk.
im flashing my phone using this command on ADB:
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot
i guess this is it so im rebooting my phone to get into twrp recovery mode by pressing volume up+power but it showed xiaomi stock recovery instead not twrp recovery.
so what i do wrong that i cannot get into twrp recovery menu?
please help me

Don't type fastboot reboot command after flashing, reboot to recovery manually

StillrunsKK said:
Don't type fastboot reboot command after flashing, reboot to recovery manually
Click to expand...
Click to collapse
i type that command after the first try not working (without fastboot reboot command)
it still gave me the same problem even not typing fastboot reboot command

Is the TWRP flash successful?
Ensure that your mobile drivers are installed properly on your pc and that you've enabled USB debugging.
Now after connecting your device to the computer :
1)open adb
2)type adb devices, if it shows a serial number then proceed
3)adb reboot bootloader
4)fastboot flash recovery xxxx.img
After this, remove the USB and reboot to recovery by Holding the appropriate combination of keys.
If you reboot your device first, and then power off and reboot to recovery, you will still get stock recovery.

StillrunsKK said:
Is the TWRP flash successful?
Ensure that your mobile drivers are installed properly on your pc and that you've enabled USB debugging.
Now after connecting your device to the computer :
1)open adb
2)type adb devices, if it shows a serial number then proceed
3)adb reboot bootloader
4)fastboot flash recovery xxxx.img
After this, remove the USB and reboot to recovery by Holding the appropriate combination of keys.
If you reboot your device first, and then power off and reboot to recovery, you will still get stock recovery.
Click to expand...
Click to collapse
Ensure that your mobile drivers are installed properly
Click to expand...
Click to collapse
i dont know where to find this drivers
i've enable the usb debugging
and while flashing it didn't gave any error

im using adb from this thread https://forum.xda-developers.com/showthread.php?t=2317790
where it didn't show any devices when typing adb devices but it showed my devices when typing fastboot devices

Micromax Canvas Infinity HS2 twrp and Root Magisk(finnaly root)

First read full steps iam not pro developer just share my experience(if step or missed just say)
Step 1. Download twrp Recovery for Your Device (HS2)From
Step 2. Download adb install.zip and extract From above adb and Fastboot driver Installer
Step 3. Now Install adb and fastboot Driver on Your pc, path(C:\Program Files\Minimal ADB and Fastboot or C:\Program Files (x86)\Minimal ADB and Fastboot)
Step 4. Go to Setting>about Phone>type 7 time Build number > Back>Developer Option and Enable Device Debugging And Oem Unlock
Step 5.Open the command on your PC. To open a command window in the current directory in Windows, press shift + Right Click anywhere on Windows explorer connect device into pc open CMD Here and type command :good:
Then follow Bellow Instructions be Remember Bootloader Must Unlock(open cmd " fastboot oem unlock-go" without qoutes)
Step 6. Unlock bootloader using below Code try first if fail then unlock using second Code
fastboot oem unlock-go
or
fastboot flashing unlock
And one think unlock bootloader if loss data and stoarge:silly:
Step7. Rename twrp into recovery.img and put in adb Folder
Step8.(cmd) fastboot boot recovery recovery.img (dont flash just boot)
Step9. Recovery is Now boot and copy magisk on stoarge
Download Magisk latest yours choice(but i prefer magisk 15.1). copy to Device storage [internatl/ external].
In the twrp Go to backup tab and Create a nadroid backup. Don’t forgot to include NVRAM or imei aka ESF in case any porblem or bootloop
Go to Install tab and Locate Download magisk and confirm Install, wait For Success Done.
[installed] make a System Reboot By this Command
fastboot reboot (if new member search how to recovery boot on android search youtube )
first boot may time pls just wait if sucess press thanks button

Error cannot load recovery.img
Plzzzz help

Hem97 said:
Error cannot load recovery.img
Plzzzz help
Click to expand...
Click to collapse
Screen shot

Hem97 said:
Error cannot load recovery.img
Plzzzz help
Click to expand...
Click to collapse
Unlock bootloder and say wat error

george.simbu said:
Unlock bootloder and say wat error
Click to expand...
Click to collapse
Yes i unlock bootloader...using cmd..
All okay but when i try 'fastboot boot recovery twrp.img'
Then 'permisen denied' shows
I am using xda app ..i dont know why says bad network cant upload screenshots

Hem97 said:
Yes i unlock bootloader...using cmd..
All okay but when i try 'fastboot boot recovery twrp.img'
Then 'permisen denied' shows
I am using xda app ..i dont know why says bad network cant upload screenshots
Click to expand...
Click to collapse
Usb debugging check and start

Hem97 said:
Yes i unlock bootloader...using cmd..
All okay but when i try 'fastboot boot recovery twrp.img'
Then 'permisen denied' shows
I am using xda app ..i dont know why says bad network cant upload screenshots
Click to expand...
Click to collapse
U have dnt unlock bootloder pls check that cmd using at post 2nd cmd

george.simbu said:
U have dnt unlock bootloder pls check that cmd using at post 2nd cmd
Click to expand...
Click to collapse
Bootloder issue

Yes i got it.....?
Factory data reset and then i do this tutorial....and i successfully flashed twrp
---------- Post added at 08:16 PM ---------- Previous post was at 08:11 PM ----------
Please port miui 9 or lineage os 15 for micromax canvas infinity hs2

Make time buddy my previous mobile hs2 but iam use still now mi a1 lets wait

george.simbu said:
Step1. Download twrp Recovery for Your Device (HS2)From
Step 2. Download adb folder From above and Fastboot driver Installer From above
Step 3. Go to Setting>about Phone>type 7 time Build number > Back>Developer Option and Enable Device Debugging And Oem Unlock.
Step 4. then follow Bellow Instructions, BE Remember Bootloader Must Unlock(open cmd " fastboot oem unlock-go" without qoutes)
Step 5. Now Install Correct adb and fastboot Driver on Your pc, Go to adb folder connect device into pc open CMD Here and type command .
tep7. Unlock bootloader using below Code try first if fail then unlock using second Code
fastboot flashing unlock
or
fastboot oem unlock-go
Step8. Rename twrp into recovery.img and put in adb Folder, To flash twrp Type-
fastboot boot recovery recovery.img(dont flash just boot)
Step9. Recovery is Now boot
Root Micromax Canvas Infinity-
Download Magisk latest(but i prefer magisk 15.1). Save it to Device storage [internatl/ external].
In the twrp Go to backup tab and Create a nadroid backup. Don’t forgot to include NVRAM or imei aka ESF.
Go to Install tab and Locate Download magisk and confirm Install, wait For Success Done.
[installed] make a System Reboot By this Command
fastboot reboot
first boot may time pls just wait if sucess press thanks button
thanks you xda
Click to expand...
Click to collapse
Are you sure this is the right recovery for micromax hs2, cuz i flashed this on my device and now its on bootloop, please don't put misleading stuff on xda. And moderators i request please dont allow people to fool others by promoting misleading tech stuff

Sudhangshu said:
Are you sure this is the right recovery for micromax hs2, cuz i flashed this on my device and now its on bootloop, please don't put misleading stuff on xda. And moderators i request please dont allow people to fool others by promoting misleading tech stuff
Click to expand...
Click to collapse
This right recovery and one member also sucess I am not fool mind you words

george.simbu said:
This right recovery and one member also sucess I am not fool mind you words
Click to expand...
Click to collapse
IAM just boot on recovery don't falshed

george.simbu said:
Step1. Download twrp Recovery for Your Device (HS2)From
Step 2. Download adb folder From above and Fastboot driver Installer From above
Step 3. Go to Setting>about Phone>type 7 time Build number > Back>Developer Option and Enable Device Debugging And Oem Unlock.
Step 4. then follow Bellow Instructions, BE Remember Bootloader Must Unlock(open cmd " fastboot oem unlock-go" without qoutes)
Step 5. Now Install Correct adb and fastboot Driver on Your pc, Go to adb folder connect device into pc open CMD Here and type command .
tep7. Unlock bootloader using below Code try first if fail then unlock using second Code
fastboot flashing unlock
or
fastboot oem unlock-go
Step8. Rename twrp into recovery.img and put in adb Folder, To flash twrp Type-
fastboot boot recovery recovery.img(dont flash just boot)
Step9. Recovery is Now boot
Root Micromax Canvas Infinity-
Download Magisk latest(but i prefer magisk 15.1). Save it to Device storage [internatl/ external].
In the twrp Go to backup tab and Create a nadroid backup. Don’t forgot to include NVRAM or imei aka ESF.
Go to Install tab and Locate Download magisk and confirm Install, wait For Success Done.
[installed] make a System Reboot By this Command
fastboot reboot
first boot may time pls just wait if sucess press thanks button
thanks you xda
Click to expand...
Click to collapse
Hello george simbu, actually you missed out couple of steps in this flashing process, when i tried using boot with recovery nothing happens, but when i flashed twrp the mobile goes into bootloop.
So how did i solved it, after flashing twrp i run the boot command in adb i.e. Fastboot boot recovery recovery.img, and then i finally be able to get my device out of bootloop
---------- Post added at 06:27 PM ---------- Previous post was at 06:24 PM ----------
george.simbu said:
This right recovery and one member also sucess I am not fool mind you words
Click to expand...
Click to collapse
And youre not fool, but next time when you try and make a tutorial please try put most of the processes into it, it actually helps the new people whose trying the flashing first time. Even i had a hard time sorting things with adb and fastboot command. It would be much appreciated if i would've got all of those command in just one place rather than going over and searching all of the internet for those commands

Foxhoundalpha said:
Hello george simbu, actually you missed out couple of steps in this flashing process, when i tried using boot with recovery nothing happens, but when i flashed twrp the mobile goes into bootloop.
So how did i solved it, after flashing twrp i run the boot command in adb i.e. Fastboot boot recovery recovery.img, and then i finally be able to get my device out of bootloop
---------- Post added at 06:27 PM ---------- Previous post was at 06:24 PM ----------
And youre not fool, but next time when you try and make a tutorial please try put most of the processes into it, it actually helps the new people whose trying the flashing first time. Even i had a hard time sorting things with adb and fastboot command. It would be much appreciated if i would've got all of those command in just one place rather than going over and searching all of the internet for those commands
Click to expand...
Click to collapse
yes iam re edits step if worng say iam changed

Error this device Micromax hs2

Milkhu said:
Error this device Micromax hs2
Click to expand...
Click to collapse
Factory reset and try again must bootloader unlock

Okay, for all those who are getting errors whatsoever, here i would like to tell you that i followed these steps and flashed twrp and rooted my device with magisk.. as explained by author..
1) unlock bootloader ( make sure to enable developer options, check unlock oem option, check debug option, check unknown sources in security option)
Use "fastboot oem unlock-go" as it worked for me on my canvas infinity hs2.
2) now after your fone is resetted after unlocking, do the initial setup with setting up account etc and once you at home screen go to settings and once again enable developer options, check unlock oem option, check debug option, check unknown sources in security.
Then connect fone to pc, you'll get adb promt on fone screen, allow it and on pc cmd type "adb reboot bootloader"
Then volume up on fone.
And on pc cmd type
Fastboot flash recovery twrp.img
(Well the author told to use boot command instead of flash, but boot didn't work for me so i used fastboot flash recovery twrp.img
Once this is done type
Fastboot reboot
And as the fone is about to reboot, quickly press volume down for twrp to load. Then you can transfer magisk from pc while twrp is on screen. And install magisk provided in the link.
Reboot and you will see your fone rooted. Voila. Done.

George.simbu did u ported any roms like lineage/RR for micromax canvas infinity
---------- Post added at 07:26 PM ---------- Previous post was at 07:25 PM ----------
I am just a noob and dont want to try porting roms on my hs2 as im afraid i might mess up my phone doing so

Foxhoundalpha said:
George.simbu did u ported any roms like lineage/RR for micromax canvas infinity
---------- Post added at 07:26 PM ---------- Previous post was at 07:25 PM ----------
I am just a noob and dont want to try porting roms on my hs2 as im afraid i might mess up my phone doing so
Click to expand...
Click to collapse
No brother

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.