Database Develop

[Q] FDCompleteTime and Fastboot loop

Hi there,
after using the RAZR i for a few days, I noticed a high amount of FDCompleteTime on BetterBatteryStats. So I decided to try to disable FD and root my device.
I used this instruction:
http://forum.xda-developers.com/showthread.php?t=1928509
However, I was too fast and forgot to unlock the bootloader, as I mixed up the rooting method with the one without needing to unlock the bootloader (using exploit).
Now I'm stuck in fastboot. Flasing didn't work (pre-validation failed) and I''m not able to boot regularly. Recovery and Normal Mode doesn't work either.
I appreciate any help.
Tobias
PS: I'm sorry for posting to this forum, but as a new forum user I'm not allowed to post to the development section.

If you are in fastboot mode you should still be able to unlock, no?

You're right. I managed to unlock the device and root it.
However, my warranty is void. Rooting my device using an exploit would be more useful.
Anyway, my fault, thanks for your help.

[STEP-BY-STEP INSTRUCTIONS] Unlocking and Rooting a Dev Ed Moto X Running Kit Kat

I posted these step-by-step instructions in another thread but thought others might like to see them in their own thread. This works for Dev Ed Moto X's running either 4.4 or 4.4.2. If you have a non-Dev Ed with an unlockable bootloader, it works for those, too, but of course you void your warranty if you unlock your bootloader if you have a non-Dev Ed.
To unlock and root the developer edition:
1) Get the unlock code from Motorola and unlock the bootloader by following the directions in this link, including downloading the Android SDK and installing Motorola Device Manager:
Unlock Moto X Bootloader
2) Get mfastboot.exe here:
mfastboot.exe
and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
3) Get the TWRP custom recovery for kit kat here:
TWRP for Moto X 4.4
and place it in the same directory as fastboot.
4) On your unlocked Moto X, enable USB debugging and download SuperSU here:
SuperSU 1.93
5) Double check to make sure USB debugging has been enabled! Put your unlocked Moto X into bootloader mode by pressing the Volume Down button and then the Power button. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
6) Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
7) At the command prompt type:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
to flash the custom recovery to your Moto X.
8) After the custom recovery has been flashed to your Moto X, at the command prompt type:
fastboot reboot-bootloader
to reboot into the bootloader.
(I am not sure if this step is necessary but I read somewhere it was necessary and I did it and it worked).
9) Unplug your device from your PC. Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
10) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
If you want to check to see if you successfully rooted, you can download Root Checker Basic from the playstore and it will tell you if you are rooted.
From what I have read you can use the version of TWRP I linked to above to root 4.4.2.
Remember, to take an OTA, you have to revert back to stock!

bumping this.

+1
Sent from my XT1060 using Tapatalk

Thx
Sent from my XT1058 using Tapatalk

I assume this is the same process regardless of Android build # (ie. After updating to 4.4.2) ...
Tapatalked via my moto x

YankInDaSouth said:
I assume this is the same process regardless of Android build # (ie. After updating to 4.4.2) ...
Click to expand...
Click to collapse
It works for both 4.4 and 4.4.2.

Can anyone post the steps to flash stock recovery to accept the OTA TO 4.4.2? Thanks.
Sent from my XT1060 using Tapatalk

ragingd said:
Can anyone post the steps to flash stock recovery to accept the OTA TO 4.4.2? Thanks.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Grab the firmware for your model here: http://sbf.droid-developers.org/phone.php?device=0
Then you can follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images ... Of course if you don't have flash every component, only what you need. Recovery of course and perhaps system...
Tapatalked via my moto x

Assistance
Perhaps someone could shed some light on this for me. I have a T-Mobile (XT1053) with an unlocked bootloader (I'm certain it's unlocked as I get the unlocked bootloader warning). I unlocked via Motorolas site. I then attempted to install TWRP with mfastboot, which it says it has done, but then when I attempt to reboot into recovery, it just ends up at a black screen (off essentially) and I can only power up as normal. Any one have any ideas?

Tuse0708 said:
Perhaps someone could shed some light on this for me. I have a T-Mobile (XT1053) with an unlocked bootloader (I'm certain it's unlocked as I get the unlocked bootloader warning). I unlocked via Motorolas site. I then attempted to install TWRP with mfastboot, which it says it has done, but then when I attempt to reboot into recovery, it just ends up at a black screen (off essentially) and I can only power up as normal. Any one have any ideas?
Click to expand...
Click to collapse
First, with your device disconnected from any power source, boot into bootloader mode and verify that it says Device is UNLOCKED. Status Code: 3. BTW - the bootloader unlocked warning logo stays even if you relock the bootloader unless you flash a new logo.
Then if it does say device is unlocked, hit Volume Down to highlight Recovery and Volume Up to select recovery. Is that when you see a black screen? It takes TWRP a little while to load.

Cozume said:
First, with your device disconnected from any power source, boot into bootloader mode and verify that it says Device is UNLOCKED. Status Code: 3. BTW - the bootloader unlocked warning logo stays even if you relock the bootloader unless you flash a new logo.
Then if it does say device is unlocked, hit Volume Down to highlight Recovery and Volume Up to select recovery. Is that when you see a black screen? It takes TWRP a little while to load.
Click to expand...
Click to collapse
Nevermind....Thanks for the help, got it going.

thanks!

jodaboda said:
thanks!
Click to expand...
Click to collapse
You are welcome!

So I'm getting an unlock code. I am currently on 4.4.2, and if I read the posts right, I don't have to downgrade to 4.4 to root, TWRP will still root 4.4.2 without issue, right?
EDIT
Nevermind. I've slapped my Moto, so I'm going to SBF back to 4.4.2 to make sure there aren't any... issues...

I'm currently rooted on 4.4. I have made changes to /system, so I can't take the OTA. I got an unlock code today. I understand that unlocking the bootloader will induce a Factory Data Reset. Do I need to SBF to stock 4.4 (or 4.2.2) before I do this? Will the FDR clear up the changes I made?
Furthermore, what order should I do these steps in? If I have 4.4 and unlock/root it, I can't take the OTA with non-stock recovery, correct? I would need a flashable ZIP for TWRP/CWM? Would it be better to unlock, FDR, take OTA to 4.4.2, then do TWRP and root?
Hopefully this isn't too silly of a question, I appreciate any advice for the best path to take on this.

Hey all, just ordered a Dev Edition to go along with my N5 and had a question regarding mfastboot. I downloaded mfastboot from one of the stickies, it was only one file and placed it in my sdk platform tools folder. I was reading on Motorola website about flashing factory images and seen this note-"NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility.". First of all, what does it mean included in Windows directory? And I'm guessing about not using the Android fastboot utility, they want you to use "mfastboot flash...." instead of "fastboot flash...."? Just trying to get some research in before I receive the device. I'm used to using fastboot on my Galaxy Nexus and now my N5. I used to have alot of Moto devices before this and using the SBF files in Moto's flashing tool, but never had an unlockable bootloader Moto device that can use some form of fastboot.

t1.8matt said:
Hey all, just ordered a Dev Edition to go along with my N5 and had a question regarding mfastboot. I downloaded mfastboot from one of the stickies, it was only one file and placed it in my sdk platform tools folder. I was reading on Motorola website about flashing factory images and seen this note-"NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility.". First of all, what does it mean included in Windows directory? And I'm guessing about not using the Android fastboot utility, they want you to use "mfastboot flash...." instead of "fastboot flash...."? Just trying to get some research in before I receive the device. I'm used to using fastboot on my Galaxy Nexus and now my N5. I used to have alot of Moto devices before this and using the SBF files in Moto's flashing tool, but never had an unlockable bootloader Moto device that can use some form of fastboot.
Click to expand...
Click to collapse
Fastboot can't handle the file sizes. So Motorola made mfastboot. You have to use it when flashing the Moto x.
Sent from my cell phone telephone....

kj2112 said:
Fastboot can't handle the file sizes. So Motorola made mfastboot. You have to use it when flashing the Moto x.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
Ok, gotcha. And I've been reading a little about people wanting to downgrade from 4.4.2, but if you have a locked bootloader and upgraded to the latest bootloader, they can't without bricking. I assume this won't be an issue with an unlocked bootloader, even though I'm not sure of why you would want to downgrade. Edit: I see, for root reasons, but this shouldn't be an issue if you're flashing SuperSU in TWRP?
Edit again: I should read more. Rooting 4.4.2 with an unlocked bootloader isn't an issue if I follow this guide in this thread. Thanks for your help. Looking forward to getting this device.

t1.8matt said:
Ok, gotcha. And I've been reading a little about people wanting to downgrade from 4.4.2, but if you have a locked bootloader and upgraded to the latest bootloader, they can't without bricking. I assume this won't be an issue with an unlocked bootloader, even though I'm not sure of why you would want to downgrade. Edit: I see, for root reasons, but this shouldn't be an issue if you're flashing SuperSU in TWRP?
Edit again: I should read more. Rooting 4.4.2 with an unlocked bootloader isn't an issue if I follow this guide in this thread. Thanks for your help. Looking forward to getting this device.
Click to expand...
Click to collapse
Root will be easy. Same as a nexus. Unlock bootloader, flash custom recovery....root. install superSU if needed.
As far as what's NOT like a nexus....yes, you can still brick downgrading an unlocked device....even the dev edition...which is no different than any other unlocked Moto x. Without going into all the details, you can read about it all over....there is a specific way to downgrade. And you cannot take an ota after....that MAY brick any Moto x...locked or unlocked. There is tonnes of conflicting opinions on this....so read as much as you can, and decide from there. There's very specific ways to downgrade and upgrade after. In my opinion....there's risk involved in all of it.
Just Google "Moto x brick downgrade xda" to read the stories.
If you find you must downgrade from 4.4.2.....study hard before you do.
Sent from my N5, N7, Moto X,G Tab 3 or S2.....

kj2112 said:
Root will be easy. Same as a nexus. Unlock bootloader, flash custom recovery....root. install superSU if needed.
As far as what's NOT like a nexus....yes, you can still brick downgrading an unlocked device....even the dev edition...which is no different than any other unlocked Moto x. Without going into all the details, you can read about it all over....there is a specific way to downgrade. And you cannot take an ota after....that MAY brick any Moto x...locked or unlocked.
If you find you must downgrade from 4.4.2.....study hard before you do.
Sent from my N5, N7, Moto X,G Tab 3 or S2.....
Click to expand...
Click to collapse
Great info. But the only reason people are downgrading from 4.4.2 is if they have a locked bootloader and want to retain root?

[Q] Moto x 4.4 root for unlocked bootloader

If someone could please post instructions to root moto x 4.4 for people that have unlocked bootloader with unlock code.

Seriously? You can't figure out how to root your phone with an unlocked bootloader yet you were able to find XDA?
Unlock bootloader, download recovery and su.zip, push to /sdcard, flash recovery, boot into recovery, flash su.zip.

nhizzat said:
Seriously? You can't figure out how to root your phone with an unlocked bootloader yet you were able to find XDA?
Unlock bootloader, download recovery and su.zip, push to /sdcard, flash recovery, boot into recovery, flash su.zip.
Click to expand...
Click to collapse
Sir..in that ones defense..not everyone here is experienced with this..and it seems to me, that we all started with this "stuff " sometime..kindness with our words would be a show of honor and a loving attitude..
The instructions in the above post are very true and accurate..but to the untrained eye..one would certainly not understand all that jazz..
sent by my 4.2.2_139.10.53
XT1060 Moto XDEV
http://waynekent.com/page6.html

While I agree with NWKENT, I also favor nhizzat's unspoken intention :
If ttrusty IS having trouble searching for this info that is available, I worry for the day he/she gets stuck in a bad spot...
tapa'd on my moto x

http://forum.xda-developers.com/showthread.php?t=2404256
Questions go in the Q&A section.

KJ said:
http://forum.xda-developers.com/showthread.php?t=2404256
Questions go in the Q&A section.
Click to expand...
Click to collapse
why are you posting that in ever fourm you see on here thats not cool man

All the info you need is in the sticky threads. Here's one: http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
Please read stickies and search if you are looking for an answer to a question. Most likely it has been answered. If you cannot find an answer, then you can create a thread.
Closed.

[Q] Can you root the new Moto X and how?

[Disclaimer-this is my first android device, thus i will be a total newbie at this stuff, second, this is my second time posting on a forum-type website so excuse me if this has already been asked and answered, plz just link the thread then]
So. Is this possible?
Detailed explanations would be much appreciated.
(I am also using a MAC, so if that affects anything....)

How about looking around a little bit. Come on man

uncalex said:
[Disclaimer-this is my first android device, thus i will be a total newbie at this stuff, second, this is my second time posting on a forum-type website so excuse me if this has already been asked and answered, plz just link the thread then]
So. Is this possible?
Detailed explanations would be much appreciated.
(I am also using a MAC, so if that affects anything....)
Click to expand...
Click to collapse
The Moto X have locked bootloader that prevent you from making changes to the "system" partition. So generally you need to unlock the bootloader first, which is a separate process.
Just a note, that generally when you unlock a phone's bootloader, you void the warranty. Some person here claimed that a Motorola manager confirmed with him that you will not void it with the Moto X Pure edition, however, I do not believe it. The best thing to do is read the fine print and warnings when you goes to unlocked your bootloader from Motorola website.
Another warning, is it easier to permanently brick a Motorola than a some other phones if you flash things incorrectly, such as corrupting the CID partition. With the Moto X 2013 it is possible to brick the phone by downgrading the phone to a too old version. I have never tried this with Moto X, but with Nexus devices, you could softbrick the phone if you root it and then do an over the air update, it generally required to use TWRP recovery to apply the over the air update zip for it to work, or reflash the "system" partition of the phone to stock before doing the update. I don't know if this is the same for the Moto X, but I would take the same precaution.
To unlock the bootloader, you can do it at the website here: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Read through this guide to help you: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
For step 2 and 3 from that guide, it linked to files required by Windows. Instead, you can get the Moto X driver for Mac here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
You will also need "fastboot" and "mfastboot" for Mac. Fastboot is the program used to lock/unlock bootloader and flash images for (stock based) Android phones. The ADB/Fastboot link in my signature have the mac/linux/windows version included (adb_fastboot.zip file). I think you only need to use the regular fastboot to unlock the phone, but to flash the phone images you will need mfastboot.
To root the phone, check in the Development sections of this device forum: http://forum.xda-developers.com/moto-x-2014
Also, you DO NOT need to unlock the phone bootloader to reflash the factory images.

eksasol said:
For rooting the Moto X it is a bit difficult compared to the Nexus. You need to realize that the Moto X have locked bootloader that prevent you from making changes to the "system" partition. So generally you need to unlock the bootloader first, which is a separate process.
Just a note, that generally when you unlock a phone's bootloader, you void the warranty. Some person here claimed that a Motorola manager confirmed with him that you will not void it with the Moto X Pure edition, however, I do not believe it. The best thing to do is read the fine print and warnings when you goes to unlocked your bootloader from Motorola website.
Another warning, is it easier to permanently (hardware) brick a Motorola than a some other phones if you flash things incorrectly, such as corrupting the CID partition. When I had the Moto X 2013 version, it is possible to brick the phone by downgrading the phone to an older version. I have never tried this with Moto X, but with Nexus devices, you could softbrick the phone if you root it and then do an over the air update, it generally required to use TWRP recovery to apply the over the air update patch for it to work, or reflash the "system" partition of the phone to stock before doing the update. I don't know if this is the same for the Moto X, but I would take the same precaution.
To unlock the bootloader, you can do it at the website here: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Read through this guide to help you: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
For step 2 and 3 from that guide, it linked to files required by Windows. Instead, you can get the Moto X driver for Mac here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
You will also need "fastboot" and "mfastboot" for Mac. Fastboot is the program used to lock/unlock bootloader and flash images for (stock based) Android phones. The ADB/Fastboot link in my signature have the mac/linux/windows version included (adb_fastboot.zip file). I think you only need to use the regular fastboot to unlock the phone, but to flash the phone image you will need mfastboot.
To root the phone, check in the Development sections of this device forum: http://forum.xda-developers.com/moto-x-2014
Also, you DO NOT need to unlock the phone bootloader to reflash the factory image of the phone.
Click to expand...
Click to collapse
Thank you for being so nice and providing this information

eksasol said:
The Moto X have locked bootloader that prevent you from making changes to the "system" partition. So generally you need to unlock the bootloader first, which is a separate process.
Just a note, that generally when you unlock a phone's bootloader, you void the warranty. Some person here claimed that a Motorola manager confirmed with him that you will not void it with the Moto X Pure edition, however, I do not believe it. The best thing to do is read the fine print and warnings when you goes to unlocked your bootloader from Motorola website.
Another warning, is it easier to permanently brick a Motorola than a some other phones if you flash things incorrectly, such as corrupting the CID partition. With the Moto X 2013 it is possible to brick the phone by downgrading the phone to a too old version. I have never tried this with Moto X, but with Nexus devices, you could softbrick the phone if you root it and then do an over the air update, it generally required to use TWRP recovery to apply the over the air update zip for it to work, or reflash the "system" partition of the phone to stock before doing the update. I don't know if this is the same for the Moto X, but I would take the same precaution.
To unlock the bootloader, you can do it at the website here: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Read through this guide to help you: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
For step 2 and 3 from that guide, it linked to files required by Windows. Instead, you can get the Moto X driver for Mac here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
You will also need "fastboot" and "mfastboot" for Mac. Fastboot is the program used to lock/unlock bootloader and flash images for (stock based) Android phones. The ADB/Fastboot link in my signature have the mac/linux/windows version included (adb_fastboot.zip file). I think you only need to use the regular fastboot to unlock the phone, but to flash the phone images you will need mfastboot.
To root the phone, check in the Development sections of this device forum: http://forum.xda-developers.com/moto-x-2014
Also, you DO NOT need to unlock the phone bootloader to reflash the factory images.
Click to expand...
Click to collapse
Quick question,
I've seen people use towelroot to root any android device. Will towelroot work with the Moto X? I'm just really hesitant now since you said it was easier to permanently brick and Moto device.

uncalex said:
Quick question,
I've seen people use towelroot to root any android device. Will towelroot work with the Moto X? I'm just really hesitant now since you said it was easier to permanently brick and Moto device.
Click to expand...
Click to collapse
I never use that. The safest thing is to do what is tested and available for that device, so use the current available method here:
http://forum.xda-developers.com/mot...e-edition-superboot-style-root-motox-t2889264
Generally. I don't do any of these, because I do the default Nexus root method which is:
1. Unlocking bootloader
2. Flash TWRP recovery: fastboot flash recovery twrp.img (not yet available for this phone, but soon will be, check the development sections.)
3. Then copy the Chainfire's SuperSU.zip (link in my signature) into the phone and flash while in TWRP recovery.
You shouldn't worry about bricking the device provided if you don't mess around, just stick with rooting and flashing factory firmware if you are new. As long as you don't flash a rom / firmware made for a different phone, or mess with the CID partition or something like that. Or downgrading the firmware after you've already update, which should be fine with a Nexus, but it did kill some Moto X when they downgraded to a firmware that is too old.
If you ever run into issues, you can flash the factory firmware, which is not available yet, but will eventually show up here: http://sbf.droid-developers.org/phone.php?device=37
You will have to download the correct version since there are different variations, but flashing incorrect ones should not brick your device. You can use these instruction to flash the firmware, this is for the Moto G, but the steps are the same: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657. After you install stock firmware, depend on if you were having issues, you can access the phone's Recovery and do a factory reset, this will wipe all your data, but also clear all the settings which may be required for the phone to boot correctly.
Normally, if your phone is rooted, when you received an over the air update, the first thing I would do before applying that update is to flash the system.img and recovery.img partition of the device back to stock, this will ensure the OTA gets updated successfully, afterward you can re-root the phone. Some people avoid this and flash the OTA's zip file using TWRP recovery, but it is not the official way and not guarantee to work all the time.

[Q&A] [Tutorial] Xperia SP Bootloader Unlocking/Relocking

Q&A for [Tutorial] Xperia SP Bootloader Unlocking/Relocking
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Tutorial] Xperia SP Bootloader Unlocking/Relocking. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Problem with the blue light disappearing
I am not able to go into fastboot mode , the blue light appears and then disappears after a while .
I have unlocked bootloader on my HTC and MOTO G , but not able to unlock on XPERIA SP .

Can I unlock the bootloader of my Xperia SP if it says: "Bootloader Unlock Allowed: No"? Or can I change it to Yes?

smileyhead said:
Can I unlock the bootloader of my Xperia SP if it says: "Bootloader Unlock Allowed: No"? Or can I change it to Yes?
Click to expand...
Click to collapse
no but some people rported that if u install cm11,cm10.1 for locked bootloader in some case's their bootloader doe's become unlock allowed:yes so give it a try

OK, Hi guys. I want to unlock my Xperia E c1505 with IMEI 35742105476238 , but the developer site doesn't sned me the continuation email. What now? Wait for days or is the some keygen out there? Is there some limitation? I tried mail.com and web.de. Do I have to do this from my mobile browser? I use USB-Tethering. Wat if they just sit and think: "He will not flash anything without this code, haha." ?
EDIT: After trying again with t-online.de address I fanally got email. Never mind.

Is there any way to unlock my bootloader even with "Bootloader unlock allowed: NO"?

edveron92 said:
Is there any way to unlock my bootloader even with "Bootloader unlock allowed: NO"?
Click to expand...
Click to collapse
Sent from my C5303 using XDA Free mobile app

Ha ha, thank you a lot man, totally works

Hey guys,
i tried to unlock my bootloader, but i faced a few problems
1. i'm not sure if this i downloaded is a mirror, but "Extract fastboot_with_Android_USB_file.rar and open fastboot folder" confuses me - i don't have a file with that name. Is tihs the name of the fastboot folder anyway, which in last release is called adb_fastboot?
2. i kinda ignored the one above and typed fastboot.exe -i 0x0fce getvar version, nothing happened, also i skipped that step and typed fastboot.exe -i 0x0fce oem unlock 0x[my key] - also no response
3. after typing *#*#7378423#*#* i got no response from my phone - what if it not meant to be bootloader unlockable?
4. on the flashtool drivers did i have to check only 2 things?

OP, please answer me

@intermezzo
Discuss your bootloader problem in here. This is the Q&A!
Never post questions in the development thread. Most people really really really don't like that...
To your problem:
Has anything worked that requires an unlocked bootloader? It sounds a little bit like it isn't unlocked!
Gesendet von meinem
Sony Xperia SP - Cyanogenmod 12.1

need some help
while doing ta backup it shows me this .( Make sure that you have USB Debugging enabled, you do
allow your computer ADB access by accepting its RSA key
(only needed for Android 4.2.2 or higher) and grant this
ADB process root permissions through superuser.) and says waiting for usb debugging...... but superuser or my mobile prompts nothing like this .. i have waited much time but nothing happens .. can anyone tell me how to solve it .. even it happens when i tried to install recoveries using pc... please help me