Database Develop

[Q] Unlocking Bootloader issue

I'm trying to install CyanogenMod, unless you can advise me a better ROM?
Doing so, I need to unlock my Bootloader, right? However, after I connect my Sony Xperia T with my laptop via USB-cable while holding the 'Volume up' button, and I attempt to type:
Code:
fastboot devices
into Command Prompt, command prompt says:
Code:
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
So I Google'd it and bumped into this thread.
I'm glad someone found a solution, however I'm stuck.
I unzipped the ADB drivers and tried to install the USB driver windows says:
Windows 8 said:
This program might not have installed correctly
SAMSUNG USB Driver for Mobile Phones.
SAMSUNG Electronics Co., Ltd.
If this program didn't install correctly, you can try installing the
program using compatibulity settings.
-> Install using compatibility settings
-> This program installed correctly
Click to expand...
Click to collapse
When I choose "-> Install using compatibility settings", nothing happens.
When I choose "-> This program installed correctly", well... Nothing happens...
What am I missing? Do I need a Sony equivalent?
Edit: After posting the thread, my PC started installing the SAMSUNG USB Driver for Mobile Phones software. However there is still no progress when i attempt to type in "fastboot device" in CMD...

Bounkass said:
I'm trying to install CyanogenMod, unless you can advise me a better ROM?
Doing so, I need to unlock my Bootloader, right? However, after I connect my Sony Xperia T with my laptop via USB-cable while holding the 'Volume up' button, and I attempt to type:
Code:
fastboot devices
into Command Prompt, command prompt says:
Code:
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Instead of doing it manually, since it doesn't seem to be your thing, why don't you use Flashtool and let it take care of everything for you.
If you want to do it manually, if you're not in the same folder with the fastboot executable then you'll get that error, either change directory into the folder where you have the fastboot executable or add said folder path to your Windows system environment variables.

Antiga Prime said:
Instead of doing it manually, since it doesn't seem to be your thing, why don't you use Flashtool and let it take care of everything for you.
If you want to do it manually, if you're not in the same folder with the fastboot executable then you'll get that error, either change directory into the folder where you have the fastboot executable or add said folder path to your Windows system environment variables.
Click to expand...
Click to collapse
Oh, I didn't know there was some tool that can do it for me. I just Google'd how to install CyanogenMod on my Xperia T, or something like that and their website said do this. So I did.
Say I would do it manually (I'm not, just asking out of curiosity), what do you mean by "if you're not in the same folder with the fastboot executable then you'll get that error". The folder was open everytime I did it? So I don't understand.
Edit: Next problem, I installed Sony Mobile Flasher by Androxyde, it doesn't recognize my phone so I have to install drivers. This thread instructs me to a certain folder withing the Flashtool directory to install the drivers needed (Xperia TX), however, once again, it's not working. This is what Device Driver Installation Wizard says:
Device Driver Installation Wizard said:
X Sony (WinUSB) sa0105AdbDeviceClass (03/07/2012 2.0.0010.30011) -- Install Failed
X Sony Net (02/29/2012 6.0.6000.16493) ------------------------------------------- Install Failed
Click to expand...
Click to collapse

Bounkass said:
Oh, I didn't know there was some tool that can do it for me. I just Google'd how to install CyanogenMod on my Xperia T, or something like that and their website said do this. So I did.
Say I would do it manually (I'm not, just asking out of curiosity), what do you mean by "if you're not in the same folder with the fastboot executable then you'll get that error". The folder was open everytime I did it? So I don't understand.
Edit: Next problem, I installed Sony Mobile Flasher by Androxyde, it doesn't recognize my phone so I have to install drivers. This thread instructs me to a certain folder withing the Flashtool directory to install the drivers needed (Xperia TX), however, once again, it's not working. This is what Device Driver Installation Wizard says:
Click to expand...
Click to collapse
What I mean is that when you type "fastboot" in the command prompt, it's actually looking for a program named "fastboot.exe/bat/cmd, etc.". If you would have been in the same folder you most likely wouldn't have gotten that error message.
Regarding drivers not installing, I'm assuming you're on Windows 8, and you're following a guide for a Samsung phone, which it seems it even directed you to install drivers for a Samsung phone in your first post.
First of all, you need to disable Windows Driver Signature Enforcement before it allows you to install the drivers. You have to do that first, then install drivers, then use Flashtool/or do it manually, by opening the command prompt and changing directories to the folder where the fastboot executable is.
Not trying to sound harsh, but if I were you I'd be a bit careful when following guides and/or dabbling with unlocking your phone, etc.; I think you should either read up very carefully before doing anything, ask questions, or leave it for later when you're a bit more knowledgeable on these types of things, because if you're having problems running a program from a command prompt or are even installing drivers for a different phone and expecting things to work smoothly, chances are you'll mess up while tinkering with your phone, especially considering you're following the CM guide and installing a CM ROM when chances are most people with custom Roms and a T would probably be using a different ROM found here on XDA, though I could be wrong.

Antiga Prime said:
What I mean is that when you type "fastboot" in the command prompt, it's actually looking for a program named "fastboot.exe/bat/cmd, etc.". If you would have been in the same folder you most likely wouldn't have gotten that error message.
Regarding drivers not installing, I'm assuming you're on Windows 8, and you're following a guide for a Samsung phone, which it seems it even directed you to install drivers for a Samsung phone in your first post.
First of all, you need to disable Windows Driver Signature Enforcement before it allows you to install the drivers. You have to do that first, then install drivers, then use Flashtool/or do it manually, by opening the command prompt and changing directories to the folder where the fastboot executable is.
Not trying to sound harsh, but if I were you I'd be a bit careful when following guides and/or dabbling with unlocking your phone, etc.; I think you should either read up very carefully before doing anything, ask questions, or leave it for later when you're a bit more knowledgeable on these types of things, because if you're having problems running a program from a command prompt or are even installing drivers for a different phone and expecting things to work smoothly, chances are you'll mess up while tinkering with your phone, especially considering you're following the CM guide and installing a CM ROM when chances are most people with custom Roms and a T would probably be using a different ROM found here on XDA, though I could be wrong.
Click to expand...
Click to collapse
Thanks for your reply.
I decided to re-install Windows 7. I was planning that anyway.
Now I'm going to start from scratch and see what happens.

"lge android mtp device cannot start code 10". when in download mode

I am trying to flash a customer recovery to my device, but when the phone gets put in download mode i am getting " "lge android mtp device cannot start code 10". " I can not perform any of the essential fastboot commands because the device can't start. I have tried, updating drivers, and trying different mtp drivers available to me, none of which worked. I've tried to do this on 3 pcs running windows 7, 8 , and 10 and they all fail.
Is there a solution to this issue? surely i'm not the only one having this problem. Searching the forum yielded only Samsung results with the same error message. Following the lines of going to the registry and deleting a specific entry, it still didn't work, so please, any help?
PS. reinstalling the drivers for my device does nothing, and windows is already updated.

bump

Did you solved it? I have the same problem

Sunaj1 said:
I am trying to flash a customer recovery to my device, but when the phone gets put in download mode i am getting " "lge android mtp device cannot start code 10". " I can not perform any of the essential fastboot commands because the device can't start. I have tried, updating drivers, and trying different mtp drivers available to me, none of which worked. I've tried to do this on 3 pcs running windows 7, 8 , and 10 and they all fail.
Is there a solution to this issue? surely i'm not the only one having this problem. Searching the forum yielded only Samsung results with the same error message. Following the lines of going to the registry and deleting a specific entry, it still didn't work, so please, any help?
PS. reinstalling the drivers for my device does nothing, and windows is already updated.
Click to expand...
Click to collapse
because flashing twrp.... phone doesnt have to be in download mode..
you turn on phone plug usb. then install minmal adb
copy twrp file into adb folder/ keep pressed SHIFT KEY on empty space in minimal adb.. then right click mouse
then select start command prompt here.
then send command you should see a message on phone .. turn on screen. select ok. then again send command
the twrp files both one in sd card and in minimal adb and the command should be named the same for twrp. example twrp.v.1.1.3 the command has to be the same .. just edit command or both or rename twrp the twrp file.

Bricked Lumia 620

At start sorry for my English.
My phone is totally bricked after my tries to unbrick my phone (Windows Device Recovery)
Phone isn't reacting. No charge vibration, don't turning on, just NOTHING. Lumia is only reacting when i connect it by cable to my laptop. How i can unbrick that phone :x Please help me ;c

feherneoh said:
Could you please give some additional info? What happens when you connect it to PC?
Click to expand...
Click to collapse
PC detect QHSUSB_Bulk and pc makes a "connection info" voice

Download and install Windows device Recovery Tool
Download from Lumiafirmware.com your model's Emergency files and ffu file
Locate thor2.exe and open a command line in that directory
Emergency and SFFU programming for Collins and Alpha:
thor2 -mode emergency -hexfile "{downloaded hexfile, full path!}" -mbnfile "{downloaded mbnfile, full path!}" -ffufile "{downloaded ffufile, full path!}.ffu"
If you copy the files in your thor2.exe subdirectory, you may drop the double quotes.
Look at this Thread:
https://forum.xda-developers.com/wi...nt/fix-dead-phone-bricked-bootloader-t3496232

SOLVED Thor can't emergnecy connect Lumia 920

Hi, so I'm one of those idiots that bricked their phone. The good news (for me at least) is I bought it for $24 to play around with and learn WP. Well I'm learning! What not to do that is. So I wanted to try WP10 and ended up bricking it. After flashing some sketchy ported win 10 rom (the three bin files as opposed to an FFU) it was in an endless reboot loop where it would just show NOKIA and then reboot. I tried to restore it but the sketchy rom had changed the product ID. So I futzed with the boot loader (this is all in WPInternals by the way) and locked it. I can't unlock it because my FFU file doesn't match the product id and I can't re-flash the sketchy rom because WPInternals crashes every time I try. Now the phone just boots to ERROR: Unable to find a bootable option...
So...after a couple of days of reading and trying different things (long story short, the phone has some unknown product id that doesn't match my backup product id (or the ATT 920 FFU).
So I've been trying to start with restoring the boot loader like so:
Code:
thor2 -mode emergency -hexfile FAST8960_PHI_ATT.hex -mbnfile RM820_msimage_v1.0.mbn -orig_gpt
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.1
thor2 -mode emergency -hexfile FAST8960_PHI_ATT.hex -mbnfile RM820_msimage_v1.0.mbn -orig_gpt
Process started Wed May 31 19:53:04 2017
Logging to file thor2_win_20170531195304_ThreadId-3536.log
Debugging enabled for emergency
Initiating emergency download
Operation took about 10.00 seconds.
THOR2_ERROR_CONNECTION_NOT_FOUND
THOR2 1.8.2.18 exited with error code 84000 (0x14820)
So as you can see I can't get thor to communicate in emergency mode with the phone (I can in uefiflash mode). In device manager the phone shows up as "Care Suite USB Connectivity" under USB devices.
This is where I am stuck and very much need your help!

Doug_M said:
Hi, so I'm one of those idiots that bricked their phone. The good news (for me at least) is I bought it for $24 to play around with and learn WP. Well I'm learning! What not to do that is. So I wanted to try WP10 and ended up bricking it. After flashing some sketchy ported win 10 rom (the three bin files as opposed to an FFU) it was in an endless reboot loop where it would just show NOKIA and then reboot. I tried to restore it but the sketchy rom had changed the product ID. So I futzed with the boot loader (this is all in WPInternals by the way) and locked it. I can't unlock it because my FFU file doesn't match the product id and I can't re-flash the sketchy rom because WPInternals crashes every time I try. Now the phone just boots to ERROR: Unable to find a bootable option...
So...after a couple of days of reading and trying different things (long story short, the phone has some unknown product id that doesn't match my backup product id (or the ATT 920 FFU).
So I've been trying to start with restoring the boot loader like so:
Code:
thor2 -mode emergency -hexfile FAST8960_PHI_ATT.hex -mbnfile RM820_msimage_v1.0.mbn -orig_gpt
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.1
thor2 -mode emergency -hexfile FAST8960_PHI_ATT.hex -mbnfile RM820_msimage_v1.0.mbn -orig_gpt
Process started Wed May 31 19:53:04 2017
Logging to file thor2_win_20170531195304_ThreadId-3536.log
Debugging enabled for emergency
Initiating emergency download
Operation took about 10.00 seconds.
THOR2_ERROR_CONNECTION_NOT_FOUND
THOR2 1.8.2.18 exited with error code 84000 (0x14820)
So as you can see I can't get thor to communicate in emergency mode with the phone (I can in uefiflash mode). In device manager the phone shows up as "Care Suite USB Connectivity" under USB devices.
This is where I am stuck and very much need your help!
Click to expand...
Click to collapse
if you have full backup image of your phone(win32Disk image tool). then you put your phone in mass storage mode(keep press and hold camera button on reboot) and write image file.

A AJAY said:
if you have full backup image of your phone(win32Disk image tool). then you put your phone in mass storage mode(keep press and hold camera button on reboot) and write image file.
Click to expand...
Click to collapse
I can't seem to put it in mass storage mode. The phone will turn on if off (not getting past the error mentioned previously of course). And I can force it to reboot by holding vol down and power. But holding vol down, vol up or camera key after the vibration doesn't work as it should. In each case all that happens is the phone vibrates as it should, then the nokia logo is displayed, then the error message (unable to find boot option) displays for less than a second and finally the phone reboots.

Solved! Googling led me to useing vpl mode. That gave me an error which further googling I saw another person who also couldn't flash 059L848 but the developer version of the rom 059R2L5 worked. I tried that and now as I type this my phone is at the Welcome screen! Sweet!

Wow! Congratulations, I sold mine, but if I had not, I would have given it a try.
Best regards,
Joachim

Have a similar problem but I keep getting an error message of "The FFU file is not correctly signed or not signed for this device." I also put W10M on a Lumia 1020 and now have a constant error message of "Unable to find bootable option".
I'm so frustrated over this. Hoping to get it fixed and back to original WP8.1.
Seeking help!
---------- Post added at 06:55 PM ---------- Previous post was at 06:51 PM ----------
Doug_M said:
Solved! Googling led me to useing vpl mode. That gave me an error which further googling I saw another person who also couldn't flash 059L848 but the developer version of the rom 059R2L5 worked. I tried that and now as I type this my phone is at the Welcome screen! Sweet!
Click to expand...
Click to collapse
Can you give me more details on how you solved this? Thanks.

I just thought of something else: when I installed W10M on my Lumia, I changed it to make it appear as a Lumia 950XL. I used InterOP tools and RegEdit. Could this be related to the FFu signature problemas I'm getting today? How would I change these values?
WPInternals info: https://1drv.ms/u/s!Ag-KZVVb9pL6q5pd7wcC32KiUZzfjQ

Lumia 720 brick while unlocking bootloader

People, please help!
I decided to unlock my lumia 720, I did everything according to the instructions. At first everything went fine, but then wpinternels got stuck on flashing done. rebooting. Then the computer just stopped seeing the phone. Now the phone does not turn on and does not charge, generally like a dead one. Even wdrt doesn't see it. Is it a brick or not? Help!

People, please help!
I decided to unlock my lumia 720, I did everything according to the instructions. At first everything went fine, but then wpinternels got stuck on flashing done. rebooting. Then the computer just stopped seeing the phone. Now the phone does not turn on and does not charge, generally like a dead one. Even wdrt doesn't see it. Is it a brick or not? Help!

People, please help!
I decided to unlock my lumia 720, I did everything according to the instructions. At first everything went fine, but then wpinternels got stuck on flashing done. rebooting. Then the computer just stopped seeing the phone. Now the phone does not turn on and does not charge, generally like a dead one. Even wdrt doesn't see it. Is it a brick or not? Help!

Hi,
please have a look into your device manager. If you find something like Qualcomm Boot loader device, proceed with one of those many instructions "unbrick without JTAG". I think your Lumia is in emergency mode.
You may also look for thor2.exe on your computer, it is in the Windows Device Recovery Tool subdirectory. Open a command line window, type thor2>help.txt and open help.txt with a text editor. Look up emergency mode. You will find something like [thor2 -mode emergency -hexfile D:\Packages\Products\RM-994\FAST8930_BATMANROW.hex -mbnfile D:\Packages\Products\RM-994\RM994_msimage_v1.0.mbn]. Notice, that is for my phone, not a 720. File name and directory entries must be changed to your needs, but hopfully you will understand the pattern.
Good luck!
Joachim

I'm found hex and mbn files for my lumia 720, changed your command for my files, but thor2 wrote this log:
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -
mode emergency -hexfile "E:\720\hex.hex" -mbnfile "E:\720\mbn.mbn"
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode emergency -hexfile E:\720\hex.hex -mbnfile E:\720\mbn.mbn
Process started Sat Jun 03 13:32:23 2023
Logging to file C:\Users\pikachu\AppData\Local\Temp\thor2_win_20230603133223_Th
readId-4876.log
Debugging enabled for emergency
Initiating emergency download
Operation took about 20.00 seconds.
THOR2_ERROR_CONNECTION_NOT_FOUND
THOR2 1.8.2.18 exited with error code 84000 (0x14820)
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>

JoachimP said:
Hi,
please have a look into your device manager. If you find something like Qualcomm Boot loader device, proceed with one of those many instructions "unbrick without JTAG". I think your Lumia is in emergency mode.
You may also look for thor2.exe on your computer, it is in the Windows Device Recovery Tool subdirectory. Open a command line window, type thor2>help.txt and open help.txt with a text editor. Look up emergency mode. You will find something like [thor2 -mode emergency -hexfile D:\Packages\Products\RM-994\FAST8930_BATMANROW.hex -mbnfile D:\Packages\Products\RM-994\RM994_msimage_v1.0.mbn]. Notice, that is for my phone, not a 720. File name and directory entries must be changed to your needs, but hopfully you will understand the pattern.
Good luck!
Joachim
Click to expand...
Click to collapse
I'm not have this in device manager. Computer doesn't see my phone.

Did you try a different USB cable, different USB port on your computer (rear side if you have a desktop or tower pc)? Did you pull the battery or press volume down ans power switch at the same time for about 20 seconds to make a power reset?
You might pn me a screenshot of your device manager.

I tried 4 different cables and different usb connectors on my laptop, still doesn't help. I also tried to hold the keys, the phone vibrates and nothing else happens. I can't remove the battery because on the lumia 720 it's not removable and I don't have a screwdriver to remove the back cover.

I am using windows 8.1 64 bit on my laptop. When you connect the phone in the device manager, nothing changes.

I tried 4 different cables and different usb connectors on my laptop, still doesn't help. I also tried to hold the keys, the phone vibrates and nothing else happens. I can't remove the battery because on the lumia 720 it's not removable and I don't have a screwdriver to remove the back cover.
I am using windows 8.1 64 bit on my laptop. When you connect the phone in the device manager, nothing changes.