Database Develop

[Q] Promblem on Flashing nAa Kernel

Hello Friends!
I have been trying to flash a customs kernel. However, it was not successfully althoug my X8 connected in Flash mode. Below is the error message:
02/023/2012 14:23:08 - INFO - Device connected in flash mode
02/023/2012 14:23:09 - INFO - Searching Xperia....
02/023/2012 14:23:09 - ERROR - USB\VID_0FCE&PID_ADDE\5&81DC10E&0&2
02/023/2012 14:23:10 - INFO - Searching Xperia....
02/023/2012 14:23:10 - ERROR - USB\VID_0FCE&PID_ADDE\5&81DC10E&0&2
02/023/2012 14:23:11 - INFO - Searching Xperia....
02/023/2012 14:23:11 - ERROR - USB\VID_0FCE&PID_ADDE\5&81DC10E&0&2
02/023/2012 14:23:12 - INFO - Searching Xperia....
02/023/2012 14:23:12 - ERROR - USB\VID_0FCE&PID_ADDE\5&81DC10E&0&2
Please guide me how to solve this error. Thanks.
Nicolas

Nicolas-PNH said:
Hello Friends!
I have been trying to flash a customs kernel. However, it was not successfully althoug my X8 connected in Flash mode. Below is the error message:
02/023/2012 14:23:08 - INFO - Device connected in flash mode
02/023/2012 14:23:09 - INFO - Searching Xperia....
02/023/2012 14:23:09 - ERROR - USB\VID_0FCE&PID_ADDE\5&81DC10E&0&2
02/023/2012 14:23:10 - INFO - Searching Xperia....
02/023/2012 14:23:10 - ERROR - USB\VID_0FCE&PID_ADDE\5&81DC10E&0&2
02/023/2012 14:23:11 - INFO - Searching Xperia....
02/023/2012 14:23:11 - ERROR - USB\VID_0FCE&PID_ADDE\5&81DC10E&0&2
02/023/2012 14:23:12 - INFO - Searching Xperia....
02/023/2012 14:23:12 - ERROR - USB\VID_0FCE&PID_ADDE\5&81DC10E&0&2
Please guide me how to solve this error. Thanks.
Nicolas
Click to expand...
Click to collapse
Have you unlocked your bootloader? for aNa kernel to work, you need to have your bootloader unlocked!

saintckk said:
Have you unlocked your bootloader? for aNa kernel to work, you need to have your bootloader unlocked!
Click to expand...
Click to collapse
Thanks for your feedback. No, i have yet unlock bootloader my X8.
I also tried to unlock bootloader as well, but, I was fail again. I have followed the step of how to unlock bootloader. However, it was not successfully.
The error symptons i had are:
- I cannot get message from S1tool whether my phone is XXXX Simlocked
- I could not identify which cmd file to be used to unlock.
- When I tried via flash tool, it appeared the same error message as "ERROR - USB\VID_0FCE&PID_ADDE\5&81DC10E&0&2"
Appreciate for your kindly advise what i should do next to unlock bootloader my X8. Thz in advanced.
Nicolas

Nicolas-PNH said:
Thanks for your feedback. No, i have yet unlock bootloader my X8.
I also tried to unlock bootloader as well, but, I was fail again. I have followed the step of how to unlock bootloader. However, it was not successfully.
The error symptons i had are:
- I cannot get message from S1tool whether my phone is XXXX Simlocked
- I could not identify which cmd file to be used to unlock.
- When I tried via flash tool, it appeared the same error message as "ERROR - USB\VID_0FCE&PID_ADDE\5&81DC10E&0&2"
Appreciate for your kindly advise what i should do next to unlock bootloader my X8. Thz in advanced.
Nicolas
Click to expand...
Click to collapse
so stop playing with bootloader first, untill u really know what are u doing..
because it will brick your phone..I mean your phone can totally dead and your can't repair by your self (hard brick)

nelikp said:
so stop playing with bootloader first, untill u really know what are u doing..
because it will brick your phone..I mean your phone can totally dead and your can't repair by your self (hard brick)
Click to expand...
Click to collapse
If you don't unlock the bootloader, then aNa Kernel is out of question! In unlocking your X8, check the date of manufacturing, and READ, UNDERSTAND AND FOLLOW the instructions to the dot! Then you are safe!

nelikp said:
so stop playing with bootloader first, untill u really know what are u doing..
because it will brick your phone..I mean your phone can totally dead and your can't repair by your self (hard brick)
Click to expand...
Click to collapse
I fully know what I am doing. it is I want to unlock bootloader on my x8, but I cannot do successfully. Do you have any idea to help me unlock successfully?
Nicolas.

saintckk said:
If you don't unlock the bootloader, then aNa Kernel is out of question! In unlocking your X8, check the date of manufacturing, and READ, UNDERSTAND AND FOLLOW the instructions to the dot! Then you are safe!
Click to expand...
Click to collapse
Thanks for your advise. my x8 made date is 11w11. is it feasible for my fone being unlocked? if yes, how to do it? (fyi, I had tried to follow the steps how to unlock, but I was fail without any reason. hope you can help me on this. thanks
Nicolas.

Nicolas-PNH said:
I fully know what I am doing.
Click to expand...
Click to collapse
Nicolas-PNH said:
if yes, how to do it?
Click to expand...
Click to collapse
You just contradicted yourself.
Nicolas-PNH said:
it is I want to unlock bootloader on my x8, but I cannot do successfully. Do you have any idea to help me unlock successfully?
Click to expand...
Click to collapse
Nicolas-PNH said:
my x8 made date is 11w11. is it feasible for my fone being unlocked? if yes, how to do it? (fyi, I had tried to follow the steps how to unlock, but I was fail without any reason. hope you can help me on this. thanks.
Click to expand...
Click to collapse
Well, you could try to be a wee bit more specific - let me remind you that we don't possess crystal balls to read your mind or read the error messages you got.
It would be nice to know WHAT error message you actually get when connecting the X8 in flash mode to unlock the bootloader.
Also, for as long as you didn't manage to hard brick your device ... restore the STOCK ROM through PCC or Flashtool (search this forum - there have been trillions of threads about it in the past few weeks) before attempting a bootloader unlock.
Of course you need to root your phone after you restored back to Stock so that bootloader unlock or recovery injection works.
EDIT: Once you successfully unlocked the bootloader while being on the Stock ROM you may then proceed to flashing miniCM AND the required kernel to make it boot (if you fail the kernel installation you need to restart from "restore Stock ROM" as there's no way out of the "Sony Ericsson" logo bootloop).

Nicolas-PNH said:
I fully know what I am doing. it is I want to unlock bootloader on my x8, but I cannot do successfully. Do you have any idea to help me unlock successfully?
Nicolas.
Click to expand...
Click to collapse
i think u got ur problem with ur brain....dont ask if u dont want to accept...u want to brick ur phone, go ahead bro

phoenix883 said:
i think u got ur problem with ur brain....dont ask if u dont want to accept...u want to brick ur phone, go ahead bro
Click to expand...
Click to collapse
agreed it's up 2 u
yeah..after this we will see one more people crying and screaming....
"help....my phone bricked...help me please...!!!"

He doesn't really understand, he ask for help, we help, then he said 'I fully know what I am doing'.......are u making fun???

he can said anything..
but better stop playing with bootloader for newbie..
if u r lucky u'll success..but if u r not..it'll totally brick your phone..
just install other rom...too many rom for x8/w8 here..!!
i would like to recoment GDXv21 or stormixv2.2.0
but if u stubborn still like playing with kernel?
don't screamming if your phone bricked
you can see the link on my signature..
thread from our senior

B.Jay said:
You just contradicted yourself.
Well, you could try to be a wee bit more specific - let me remind you that we don't possess crystal balls to read your mind or read the error messages you got.
It would be nice to know WHAT error message you actually get when connecting the X8 in flash mode to unlock the bootloader.
Also, for as long as you didn't manage to hard brick your device ... restore the STOCK ROM through PCC or Flashtool (search this forum - there have been trillions of threads about it in the past few weeks) before attempting a bootloader unlock.
Of course you need to root your phone after you restored back to Stock so that bootloader unlock or recovery injection works.
EDIT: Once you successfully unlocked the bootloader while being on the Stock ROM you may then proceed to flashing miniCM AND the required kernel to make it boot (if you fail the kernel installation you need to restart from "restore Stock ROM" as there's no way out of the "Sony Ericsson" logo bootloop).
Click to expand...
Click to collapse
Thanks for your comment. I think i found the person as you understanding my error: To response to your points:
1: When i connected my phone as Flash mode to unlock bootloader, error message is "ERROR - USB\VID_0FCE&PID_ADDE\5&81DC10E&0&2". How to fix this error?
From this end, I will search how to restore Stock Rom.

On a somewhat related note ... please ignore the ill-mannered trolls who posted after my reply ... it seems to be a fact that the MODERATOR OF THIS SECTION STILL FAILS HIS JOB TO ENFORCE PROPER BEHAVIOR (like treat each other with respect and keep the language at a civil level)!
Anyway ...
Nicolas-PNH said:
Thanks for your comment. I think i found the person as you understanding my error: To response to your points:
1: When i connected my phone as Flash mode to unlock bootloader, error message is "ERROR - USB\VID_0FCE&PID_ADDE\5&81DC10E&0&2". How to fix this error?
From this end, I will search how to restore Stock Rom.
Click to expand...
Click to collapse
Let us investigate the error output in detail...
You launch Flashtool, you select to the unlock the boot loader and then you connect the USB cable of your X8 to the computer while HOLDING the back button and KEEPING it pressed?
If yes, and you get the error message ...
Ignore the error output for a moment and open the "Device Manager" (START -> "Computer" -> Right-click -> "Manage" ... in the window that opens now select "Device Manager" on the left).
Do you have the "SEMC Flash Device" showing up in the list of devices on the right WITHOUT a yellow or red warning sign (or is it even missing entirely)?
If you are missing any signs of the "SEMC Flash Device" in Device Manager your computer was unable to install the required driver. In this case you try to either install the Android drivers through "Gordon's Gate" (ggsetup-<version>.exe - comes with Flashtool) or you can download and install PC Companion which would also install the SEMC Android drivers.
As a further troubleshoot measure: Try another USB port OR another computer entirely. We already observed Windows installations giving troubles for unknown reasons - where it then worked out by using another computer/laptop.
Now let's see what your reply will be.

B.Jay said:
On a somewhat related note ... please ignore the ill-mannered trolls who posted after my reply ... it seems to be a fact that the MODERATOR OF THIS SECTION STILL FAILS HIS JOB TO ENFORCE PROPER BEHAVIOR (like treat each other with respect and keep the language at a civil level)!
Anyway ...
Let us investigate the error output in detail...
You launch Flashtool, you select to the unlock the boot loader and then you connect the USB cable of your X8 to the computer while HOLDING the back button and KEEPING it pressed?
If yes, and you get the error message ...
Ignore the error output for a moment and open the "Device Manager" (START -> "Computer" -> Right-click -> "Manage" ... in the window that opens now select "Device Manager" on the left).
Do you have the "SEMC Flash Device" showing up in the list of devices on the right WITHOUT a yellow or red warning sign (or is it even missing entirely)?
If you are missing any signs of the "SEMC Flash Device" in Device Manager your computer was unable to install the required driver. In this case you try to either install the Android drivers through "Gordon's Gate" (ggsetup-<version>.exe - comes with Flashtool) or you can download and install PC Companion which would also install the SEMC Android drivers.
As a further troubleshoot measure: Try another USB port OR another computer entirely. We already observed Windows installations giving troubles for unknown reasons - where it then worked out by using another computer/laptop.
Now let's see what your reply will be.
Click to expand...
Click to collapse
Hi B.Jay,
That's fantastic having your initiative idea and willing to investigate my problem. I really appreciate it. Please refer to below for my response:
- I have checked in "Device Manager", it is absolutely as you said there is a yellow sign near by "SEMC Flash Device". Then, I have follow your step to install both ggsetup-2.2.0.11 and PC Companion. However, the result seems no change.
In order to keep on track for your further finding what my problem really is, I would like to share you on my current x8 specification as below:
- Firmware version: 2.1 -update 1
- Basedband version: M76xx-TSNCJOLYM-53404015
- Kernel version: 2.6.29 [email protected]#1
- Build number: 2.1.1.A.0.6
- My X8 is rooted and has xRecovery
With above info, does it help you to identify how can/should I be able to unlock bootloader in order to flash kernel later? I believe you can HELP me on this.
Thanks.
Best regards,
Roatha

Nicolas-PNH said:
Hi B.Jay,
That's fantastic having your initiative idea and willing to investigate my problem. I really appreciate it. Please refer to below for my response:
- I have checked in "Device Manager", it is absolutely as you said there is a yellow sign near by "SEMC Flash Device". Then, I have follow your step to install both ggsetup-2.2.0.11 and PC Companion. However, the result seems no change.
In order to keep on track for your further finding what my problem really is, I would like to share you on my current x8 specification as below:
- Firmware version: 2.1 -update 1
- Basedband version: M76xx-TSNCJOLYM-53404015
- Kernel version: 2.6.29 [email protected]#1
- Build number: 2.1.1.A.0.6
- My X8 is rooted and has xRecovery
With above info, does it help you to identify how can/should I be able to unlock bootloader in order to flash kernel later? I believe you can HELP me on this.
Thanks.
Best regards,
Roatha
Click to expand...
Click to collapse
Hi there , I currently having problem with my x10i but the problem is very similar to yours , i think its the drivers fault.Anyway , do you have the solution for your problem, maybe i can apply it to my phone .Thank you

Nicolas-PNH said:
Hi B.Jay,
That's fantastic having your initiative idea and willing to investigate my problem. I really appreciate it. Please refer to below for my response:
- I have checked in "Device Manager", it is absolutely as you said there is a yellow sign near by "SEMC Flash Device". Then, I have follow your step to install both ggsetup-2.2.0.11 and PC Companion. However, the result seems no change.
In order to keep on track for your further finding what my problem really is, I would like to share you on my current x8 specification as below:
- Firmware version: 2.1 -update 1
- Basedband version: M76xx-TSNCJOLYM-53404015
- Kernel version: 2.6.29 [email protected]#1
- Build number: 2.1.1.A.0.6
- My X8 is rooted and has xRecovery
With above info, does it help you to identify how can/should I be able to unlock bootloader in order to flash kernel later? I believe you can HELP me on this.
Thanks.
Best regards,
Roatha
Click to expand...
Click to collapse
Try inserting your USB on a working phone i.e. Mass storage device..
if it is a windows 7 pc .. it will automatically install your drivers ..

goudaniket said:
Try inserting your USB on a working phone i.e. Mass storage device..
if it is a windows 7 pc .. it will automatically install your drivers ..
Click to expand...
Click to collapse
Hey.. That post is already outdated..

ryanperez said:
Hey.. That post is already outdated..
Click to expand...
Click to collapse
No, there is a recent commentor

[Q] Flash with stock rom

Hi and thanks for reading my question,
I have an xperia z with french network (SFR) customing. When I'm turning on my phone, there is an SFR's logo appears. How can I flash my phone with original rom ?
Thanks a lot for your help and sorry for my english.

AW: [Q] Flash with stock rom
Grab Flashtool, an unbranded original rom in FTF format and flash it using flashtool.
If youre familiar with Samsung, its the same as flashing tar.md5 with Odin.

Thx, I'm not familiar with Samsung :silly: lol. So if I debrand my phone, don't need to unlock bootloader or root the phone ? I don't want to loose official updates and Bravia Engine 2.
Thx for your help and I extract my original rom for french people who want "SFR" rom.

No, unlocking is not needed. Official FTF's can be crossflashed on branded devices to unbrand them.
You may pull a backup of your current firmware to have it ready to make your phone look like factory fresh. There's tutorials all over the place how to do that, you may ask Google. It basically involves telling PC Companion to "repair" your phone, it will then download the branded firmware from Sony and this file you copy from the download directory and safe it for later. Piece of cake

Superb ! The post could be close. Thx a lot !

I may have to add, I tried to pull a "backup" FTF for my still locked and brand new Z. PC Companion said there is no update available (yet). I find this peculiar as how am I supposed to "repair" my phone if I already ****ed my device up for real? I'll have to have an eye on the topic, hope FTF's will go online in the next couple days.

Has anyone uploaded a stock ROM yet? Couldn't find one.

There's at least one here http://forum.xda-developers.com/showthread.php?t=2135948
Don't know if it's FTF though and the search is down, I can't search the thread.
Edit: I was wrong. No boyscout-flashable release yet it seems
Edit 2: The one who searches shall find: http://icxperia.com/doomlord/xperia_z/10.1.A.1.350/ I took it from the last post in the above linked thread. Posted by doomlord.

Thanks a lot but is this the proper retail dump or demo build? I read that thread but they said it was demo.
Have you flashed yet? Any solution on how to grab a backup of the vanilla firmware?

Alright, to clone your current firmware:
1. Connect phone while in PC Companion.
2. Where it says at the top "latest version installed", click on that text.
3. In the small message box that pops up, click "repair my phone".
4. You are now in the flashing steps as usual.
5. Proceed until you are given the option to back up.
6. Do as usual.

AW: [Q] Flash with stock rom
lloydbf said:
Thanks a lot but is this the proper retail dump or demo build? I read that thread but they said it was demo.
Have you flashed yet? Any solution on how to grab a backup of the vanilla firmware?
Click to expand...
Click to collapse
I dont have it from inside the thread, I browsed the directories Doom linked to and found that FTF in the process. I take it from the build 10.1.A.1.350 that we are talking release, don't know. Doesn't really matter either, unbranded is unbranded.
And I won't flash it, my free device came unbranded. I pay a lot of attention to only getting free, unlockable, unbranded devices.
lloydbf said:
*snip* 3. In the small message box that pops up, click "repair my phone".*snip*
Click to expand...
Click to collapse
As I wrote further up or in another thread (dunno), if I do that, I get a message that no firmware is available for download.

Problem flashing stock rom
Hi,
I'm trying to flash the stock rom. But It doesn't work... (my bootloader is unlocked)
When I try to flash the stock rom with flashtool it gets stuck with:
28/059/2013 14:59:14 - INFO - Current device : C6603 - CB5A1P70CZ - 1270-8440_R12A - 1269-5309_10.1.A.1.350 - VODAFONE1-LTE_10.1.A.1.350
28/059/2013 14:59:14 - INFO - Start Flashing
28/059/2013 14:59:14 - INFO - Processing loader
28/059/2013 14:59:14 - INFO - Checking header
28/059/2013 14:59:14 - INFO - Ending flash session
28/059/2013 14:59:14 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x80060011 ";
28/059/2013 14:59:14 - ERROR - Error flashing. Aborted
Click to expand...
Click to collapse
The Log in debug-mode says: (see attachment)
When trying to flash something directly with fastboot I get this:
writing 'cache'...
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
What can I do now?
(Repair via PC Companion doesn't work, because it says the software on the phone is modified)

Are you connecting in USB debug mode when first plugging it in?
Otherwise, no idea.

lloydbf said:
Are you connecting in USB debug mode when first plugging it in?
Otherwise, no idea.
Click to expand...
Click to collapse
adb and fastboot should work fine.

[Q] Xperia T soft brick - HELP GREATLY APPRECIATED

Hi there
I am encountering an issue with my Sony Xperia T (FW: 9.1.A.1.141) which I am certain can be resolved with the correct tools and knowhow, but having spent the last week following what feels like every related link on the internet, I am no further forward - sleeping badly as a result - and very much in need of some help.
I'd prefer to avoid a torrent of potential fixes that I may already have tried at length so please forgive me if I go into too much detail. I just want to be very clear exactly where I am and what I have done so far to try and fix the issue. My PC is running Windows 7 64-bit (no issues).
This is my first proper smartphone so after a few months getting to grips with the underlying nature of the Android OS, I decided it was now time to root the phone and try out different ROMs etc. After reading what I could about the process, I finally used DooMLoRD's Easy Rooting Toolkit 17 (For Sony Xperia Devices) and was amazed by how easy it was to unroot my device. After installing Titanium Backup and fully backing up my files, I then installed ClockWorkMod Recovery 6.0.4.6 (For Sony Xperia Devices), and was able to boot into the recovery environment without issue (I also made an additional backup of the system at this point). So far, so good.
I then copied two ROMS to my SD card - Android 4.4.2 (KitKat) For Sony Xperia T (AOKP Build) & CyanogenMod 11.20140127 (Nightly) For Sony Xperia T - and tried to flash the CyanogenMod ROM from within the ClockWorkMod Recovery Environment, however I received a Status 7 Error, preventing me from flashing the ROM, then tried the same with Android 4.4.2 (KitKat) ROM, but again I received a Status 7 Error. As I attempted to leave the recovery environment to research the Status 7 Error, the program flashed a popup saying the phone was not rooted and would I like to root it. At this point, I assumed I had lost root as a result of the Status 7 Error, but didn't want to make any more changes, so chose no to the root option and restarted my Xperia T.
At this point the Sony logo went into a loop and despite restarting the phone using power and volume up many times, I was unable to boot back into the ClockWorkMod Recovery Environment nor connect the phone to my PC, although I could see the drivers appear for a few seconds in Windows before disappearing. It took me a good couple of days to realise that I had to fully charge my phone, so when I began the operation again with a fully charged phone I was able to update the driver in Device Manager from Sony Ericsson Seehcri Control Device (yellow exclamation mark) to Sony ADB Device (although the Sony Ericsson Seehcri Control Device with exclamation mark later returned so I am unable to assess how successful this actually was).
From here, I tried to update the phone using the already installed and up to date PC Companion, but the phone will not connect in flash mode, so it is not possible to connect the phone. I also tried the latest Sony Update Service (2.13.4.16), then Sony Emma Flash Tool (For Sony Xperia Devices), but none of these recognise the phone because I cannot get the phone into flash mode. Using the Android Flash Tool 0.9.13.0 (For Sony Xperia Devices), I am able to connect to the phone in fastboot mode, but when I try to install a stock kernel or any other variant, the Flash Tool states that I can't make any changes because the phone is not rooted.
Thinking I could root my phone again with DooMLoRD's Easy Rooting Toolkit 17, this time it no longer works, I assume because my phone cannot enter flash mode, even though it is recognised in Android Flash Tool 0.9.13.0 in fastboot mode (blue light).
Now, it is conceivable since my phone is no longer rooted that I may well be able to have my phone fixed under warranty and returned to me, however I would thereafter be scared to try and install a custom ROM, and would never really feel comfortable with the phone again, so I would much prefer to learn how to fix the problem myself. I am convinced the phone is salvageable because I have no issue recharging the phone, the screen is lighting up to display the Sony logo without issue and I am able to connect to my PC so that Sony ADB Device is recognised in Device Manager and via the Android Flash Tool 0.9.13.0, but can make no other changes.
My suspicion is that it has something to do with the ADB drivers, (which I linked to my Android Developer Tools Bundle 20131030 64-bit via the Windows Environment Variables), since no devices are recognised when I connect the phone and run the ADB Devices command in the Windows Command Prompt even when Windows is otherwise able to identify the device in Device Manager.
If anyone would be willing to talk me through this, I would be most grateful and would follow up all advice up so this information might be useful to others in the future as I can't see this being an isolated case. Likewise, if I am simply wasting my time and need to get the phone replaced or repaired, at least it would be good to know that I have exhausted all other options.
FYI Prior to the soft brick, I had USB debugging enabled and was in Mass Storage Mode (since this was more stable than Media Transfer Mode).

Hi. I don't see any mention of bootloader status. Did you go through the process of unlocking your bootloader? Or have you checked to see if your phone is "bootloader unlock allowed: yes"? The reason I ask is because the 2 roms you want to try seem to be AOSP-based / Cyanogen, which run on custom kernels. If your bootloader is locked, you are not allowed to flash custom kernels. That might explain the failure code you say in CWM - or it might not (since my bootloader cannot be unlocked, I don't have much experience with those kinds of ROMs).
Moving on to the recovery you flashed - Which recovery did you install? I have been reading that Clockworkmod recovery (v9) is quite buggy. You can get v8 in this thread: http://forum.xda-developers.com/showthread.php?t=2609997
The peeps in this forum are pretty good problem solvers (and creators ;D) - we'll get you going again hopefully!

is your bootloader unlocked dude?i mean if you have a locked bootlader you are not supposed to install custom roms. and if your boot loader is unlocked sony update engine and pc companion wont solve the issue. you have to try with flashtool .firstly you gotta install the flashtool drivers fot xt .and then run flashtool x64. hold the vol down button and connect it using usb. i had this problem many times. and that above procedure may solve your issue

Hi there
First of all thank you so much for replying. These forums are quite daunting at times and it is good to know someone with some clout is listening. Apologies again for going into yet more detail, but it should help me reach a resolution sooner rather than later.
As re the bootloader, I was under the impression that DooMLoRD's Easy Rooting Toolkit 17 would root my stock Xperia T while leaving the bootloader untouched - that is to say locked (as far as I am aware) - should I wish to revert the rooting process at a later date. Now, I obviously lost root somewhere along the line, but has the bootloader also been changed to unlocked? I don't know, but I wouldn't imagine so, so I can only assume it is still locked.
I have recharged my phone ready to make some fresh attempts at this, but to confirm the current state of my Windows 7 connection, I can only connect to the PC in fastboot (with the blue light turned on after connecting to the machine while pressing volume down). There is definitely an issue with some aspect of the drivers since the Sony ADB Device is recognised as working in Device Manager as soon as I connect the phone, however the bothersome Sony Ericsson Seehcri Control Device is also present with a yellow exclamation mark indicating a problem.
Now, whether this is actually affecting my use of the Android Flash Tool 0.9.13.0 and the other flash tools, I can't actually say. When I open the Android Flash Tool with the phone connected, the two options available to me are flashmode or fast boot mode. When I try to use the flashmode with the (as far as I am aware) Xperia T stock firmware LT30P_9.1.A.1.141_PL.ftf, I simply cannot connect in flashmode when prompted. I am asked to remove the phone then reattach it, but no green light ever shows indicating flashmode, only the blue light indicating fast boot mode. When I try to use fast boot mode on the other hand, firstly I am not sure which of the various methods to use - I have of course tried them all, and also I should say both the 32-bit and 64-bit versions of the Flash Tool - but when I do, I am always told that the device needs to be rooted first.
Now, this may have something to do with the kernels/firmware/ROMs that I am using (there's no question all the variations confuse me a little) as I assumed it simply wasn't possible to flash via fastboot yet further reading suggests that it should be possible to flash a stock kernel without root access. The kernels/firmware I have tried are: stock-7.0.A.3.223-twrp-2.3.3.0.elf; 15102012.img; Sony Xperia T Kernel (Stock) With CWM602; Sony Xperia T Kernel (Stock) With TWRP2500. So perhaps I am not using the correct firmware or kernel (I would like to try the LT30P_9.1.A.1.141_PL.ftf, but cannot see an option to do so via fast boot mode). If this is the case and I am able to identify the correct kernel, then perhaps this "device must be rooted first" notification would no longer happen and the state of the ADB drivers would be largely irrelevant.
On the other hand if the flash tool in fast boot mode is always going to ask me to root first, wouldn't it make more sense to focus my attention on being able to connect to DooMLoRD's Easy Rooting Toolkit 17 in order to root the device so I can then use the Flash Tool in fast boot mode without any further issues. But that being the case, perhaps I should focus on working out what is happening with the problem Sony Ericsson Seehcri Control Device in Device Manager. Perhaps when that is resolved I will be able to connect to any of the available flash tools.
As far as ROMs and Recovery Environments are concerned, I truly appreciate your advice - and believe me when I resolve this problem I will be sure to run through my rooting plans BEFORE executing them on these very forums - but for now I need to focus on flashing the phone back to stock or somehow connecting the phone to one of the Sony Flash Tools.
Thanks again for your patience and assistance so far and I look forward any more ideas now I have provided a bit more detail.
My sanity hangs in the balance!

BTW, I imagine you are both quite right about what went went wrong in the first instance - I did not appreciate you couldn't flash any ROM once the Xperia T had been rooted. Again, when I resolve this issue, I will describe my exact plans before proceeding. Thanks for clearing that up. I'm learning all the time.

pfhastie said:
BTW, I imagine you are both quite right about what went went wrong in the first instance - I did not appreciate you couldn't flash any ROM once the Xperia T had been rooted. Again, when I resolve this issue, I will describe my exact plans before proceeding. Thanks for clearing that up. I'm learning all the time.
Click to expand...
Click to collapse
Try unlocking bootloader, fastboot flashing boot.img of the rom you want. (before hand get the rom you want on sd or something) And then you should flash without error.

First of all thank you so much for replying. These forums are quite daunting at times and it is good to know someone with some clout is listening. Apologies again for going into yet more detail, but it should help me reach a resolution sooner rather than later.
Click to expand...
Click to collapse
Detail is always good - much better than a "i rooted my phone and now it doesn't work" post. I agree, information is in many different places - very easy for that to happen.
As re the bootloader, I was under the impression that DooMLoRD's Easy Rooting Toolkit 17 would root my stock Xperia T while leaving the bootloader untouched - that is to say locked (as far as I am aware)
Click to expand...
Click to collapse
Yes - that is, if your bootloader was Locked when you started this whole adventure.
Now, I obviously lost root somewhere along the line
Click to expand...
Click to collapse
- Maybe but maybe not!,
but has the bootloader also been changed to unlocked? I don't know, but I wouldn't imagine so, so I can only assume it is still locked.
Click to expand...
Click to collapse
No - the bootloader unlock is a whole process in itself. DoomLord's (fantastic) root kit will root your phone - meaning, it will root your phone's current system, to allow read/write access to the system's files. When you unlock the bootloader, that allows you to write to partitions (kernel aka boot, radio/baseband? etc.)
I have recharged my phone ready to make some fresh attempts at this, but to confirm the current state of my Windows 7 connection, I can only connect to the PC in fastboot (with the blue light turned on after connecting to the machine while pressing volume down). There is definitely an issue with some aspect of the drivers since the Sony ADB Device is recognised as working in Device Manager as soon as I connect the phone, however the bothersome Sony Ericsson Seehcri Control Device is also present with a yellow exclamation mark indicating a problem.
Click to expand...
Click to collapse
Since right now, what you need to be able to do is flash a stock FTF (to get your phone working again), make sure your phone is disconnected from the PC. Drivers --- all you should need is Sony PC Companion installed (which installs base drivers for the phone), and Flashtool (http://forum.xda-developers.com/showthread.php?t=1943886). After you install Flashtool, you will need to go into its folder - inside of there is a "drivers" folder. go in there and run the EXE. On the left side, make sure to click/check the driver for your phone (xperia T or TL or LT30p or whatever), plus the Fastboot driver, plus the Flashmode driver. Let it do the install. **NOTE** i dont know if Win7 has "driver signature enforcement" - if you notice the drivers are failing to install, that could be why. Look into how to temporarily disable driver signature enforcement and try these 3 drivers again. You will need them!!
Now, whether this is actually affecting my use of the Android Flash Tool 0.9.13.0 and the other flash tools, I can't actually say. When I open the Android Flash Tool with the phone connected, the two options available to me are flashmode or fast boot mode.
Click to expand...
Click to collapse
Stop here for a second - For the purpose of flashing an FTF (i.e. getting your phone back to working state), do not connect the phone yet.
When I try to use the flashmode with the (as far as I am aware) Xperia T stock firmware LT30P_9.1.A.1.141_PL.ftf, I simply cannot connect in flashmode when prompted. I am asked to remove the phone then reattach it, but no green light ever shows indicating flashmode, only the blue light indicating fast boot mode.
Click to expand...
Click to collapse
When using Flashmode, don't connect the phone at all - Choose flashmode, then choose the FTF, then wait for it to process the files, then it will pop up to tell you when to connect the phone. And this is very important - make sure the phone is fully OFF, then, hold the VOLDOWN button, then plug the usb cable in - when you see Flashmode start moving along, you can let go of the VOLDOWN button... and put the phone down gently .. you dont want to distrub this delicate process .
When I try to use fast boot mode on the other hand, firstly I am not sure which of the various methods to use - I have of course tried them all, and also I should say both the 32-bit and 64-bit versions of the Flash Tool - but when I do, I am always told that the device needs to be rooted first.
Click to expand...
Click to collapse
This may all depend on your bootloader - if your bootloader is locked, you likely cannot get the phone into Fastboot mode.
Now, this may have something to do with the kernels/firmware/ROMs that I am using (there's no question all the variations confuse me a little) as I assumed it simply wasn't possible to flash via fastboot yet further reading suggests that it should be possible to flash a stock kernel without root access.
Click to expand...
Click to collapse
Right - flashing via fastboot may not be possible right now if your bootloader is locked.
The kernels/firmware I have tried are: stock-7.0.A.3.223-twrp-2.3.3.0.elf; 15102012.img; Sony Xperia T Kernel (Stock) With CWM602; Sony Xperia T Kernel (Stock) With TWRP2500. So perhaps I am not using the correct firmware or kernel (I would like to try the LT30P_9.1.A.1.141_PL.ftf, but cannot see an option to do so via fast boot mode). If this is the case and I am able to identify the correct kernel, then perhaps this "device must be rooted first" notification would no longer happen and the state of the ADB drivers would be largely irrelevant.
Click to expand...
Click to collapse
Yes - let's skip the kernels for now - and get you flashing a fresh FTF so you can start over. I suggest that once the FTF is flashed, and the phone can boot normally, you dial the Service Menu number and look to see if your phone has "Bootloader Unlock Allowed: Yes" or "Bootloader Unlock Allowed: No". -If it says NO, it means NO! There is currently (as of Feb3/2014) no way to get around this. This means your bootloader cannot be unlocked, which means no custom kernels, and no fastboot! Custom ROMS can still be flashed - just those that are Locked Bootloader-friendly (meaning, the custom rom operates just fine/is based on the Stock kernel - whatever version is preferred will be mentioned in the dev's first post of the thread). There are a few.. like XperimenT and T-Hybrid. I like those.
I'm going to be safe and assume yours says No (like mine, because everyone should suffer with me!! ) You can then ROOT the system like you did, then install CWM Recovery for locked bootloaders (v8!! dont use v9 for now), then you can flash a rom or do whatever. If the custom rom you're installing is based on a stock kernel whose version number is different from your phone's base, then you may be able to find kernel zips that are flashable via CWM - since they are stock kernels, the flash will be allowed because they are signed or whatever. Example: Since you're going for LT30p .141 FTF, you're on the 141 kernel. If the rom you're installing says it recommends the .145 kernel, find the LT30P .145 kernel zip. You can flash that right after flashing the ROM. I think that the 141/145 kernels are similar to each other so in this case, you may not even have to flash from 141 to 145. But you will - because you will become addicted to flashing like the rest of us and you will want to observe/compare how the ROM behaves on each.
On the other hand if the flash tool in fast boot mode is always going to ask me to root first, wouldn't it make more sense to focus my attention on being able to connect to DooMLoRD's Easy Rooting Toolkit 17 in order to root the device so I can then use the Flash Tool in fast boot mode without any further issues.
Click to expand...
Click to collapse
I think what it's really asking you is to Unlock Your Bootloader. Unlocking the bootloader is kind of considered a global root (because it allows writing to any partition on the phone.
But that being the case, perhaps I should focus on working out what is happening with the problem Sony Ericsson Seehcri Control Device in Device Manager. Perhaps when that is resolved I will be able to connect to any of the available flash tools.
Click to expand...
Click to collapse
Yes - hopefully above we have tackled that.
As far as ROMs and Recovery Environments are concerned, I truly appreciate your advice - and believe me when I resolve this problem I will be sure to run through my rooting plans BEFORE executing them on these very forums - but for now I need to focus on flashing the phone back to stock or somehow connecting the phone to one of the Sony Flash Tools.
Thanks again for your patience and assistance so far and I look forward any more ideas now I have provided a bit more detail.
My sanity hangs in the balance!
Click to expand...
Click to collapse
Agreed!! Good luck!

Thanks for the considered responses. hhamzah49, I have tried to use the bootloader unlock in the flash tool, but it simply waits for me to connect in flash mode, which is what I am unable to do. There is not even an opportunity of using a SD card since I cannot start the phone either normally or in a recovery environment.
LaZiODROID, you're the man for going into so much detail, and yes I am looking forward to trying out loads of ROMs if possible, however I can't consider such luxuries until I've flashed the phone back to stock! It seems the bootloader probably has a lot to do with it, and I wish I could confirm one way or another if it is locked or not, but I don't see a way to do that in the phone's current state. I bought it from Amazon UK in October or thereabouts, so perhaps that might give you a clue - I would assume it is locked for now, but happy to try the process working on the assumption that it is unlocked if that is likely to help.
I am already using the Flash Tool you suggested and have OKed the drivers signature on Windows 7. I understand about not connecting the phone prior to preparing the flash tool (in flashmode) - and making sure it is fully off by pressing power and volume down until I feel the three vibrations indicating the phone is fully off - but all this seems to be immaterial as I am never able to connect in flash mode. Only the blue light ever appears, never the green one.
You say it is likely that I will not be able to connect the phone in fast boot mode because my bootloader is locked, however I am ONLY able to connect in fast boot mode so if I am not able to flash via fast boot, I am not sure what other course of action to take.
I think I understand now about the unlocked bootloader and having to source suitable ROMs when the time comes, but not quite there yet.
I have uploaded several images of my current connection via Command Prompt, Device Manager, Android Flash Tool 0.9.13.0 & DooMLoRD's Easy Rooting Toolkit 17. I also noticed that when I start DooMLoRD's Easy Rooting Toolkit 17 with no ADB drivers running in Windows Task Manager Processes, two instances of the ADB driver appear, each leading back to DooMLoRD's Easy Rooting Toolkit 17 and each a slightly different size. When I try to run the Rooting Toolkit, the command prompt simply says "daemon started successfully", but nothing happens after this. If I kill one of the two ADB processes, this seems to start the program off, but to no avail since "device not found" is displayed repeatedly.
Anyway, my comatose phone and I remain on standby ready to try whatever it takes.

LaZiODROID said:
Detail is always good - much better than a "i rooted my phone and now it doesn't work" post. I agree, information is in many different places - very easy for that to happen.
Yes - that is, if your bootloader was Locked when you started this whole adventure. - Maybe but maybe not!, No - the bootloader unlock is a whole process in itself. DoomLord's (fantastic) root kit will root your phone - meaning, it will root your phone's current system, to allow read/write access to the system's files. When you unlock the bootloader, that allows you to write to partitions (kernel aka boot, radio/baseband? etc.)
Since right now, what you need to be able to do is flash a stock FTF (to get your phone working again), make sure your phone is disconnected from the PC. Drivers --- all you should need is Sony PC Companion installed (which installs base drivers for the phone), and Flashtool (http://forum.xda-developers.com/showthread.php?t=1943886). After you install Flashtool, you will need to go into its folder - inside of there is a "drivers" folder. go in there and run the EXE. On the left side, make sure to click/check the driver for your phone (xperia T or TL or LT30p or whatever), plus the Fastboot driver, plus the Flashmode driver. Let it do the install. **NOTE** i dont know if Win7 has "driver signature enforcement" - if you notice the drivers are failing to install, that could be why. Look into how to temporarily disable driver signature enforcement and try these 3 drivers again. You will need them!!
Stop here for a second - For the purpose of flashing an FTF (i.e. getting your phone back to working state), do not connect the phone yet.
When using Flashmode, don't connect the phone at all - Choose flashmode, then choose the FTF, then wait for it to process the files, then it will pop up to tell you when to connect the phone. And this is very important - make sure the phone is fully OFF, then, hold the VOLDOWN button, then plug the usb cable in - when you see Flashmode start moving along, you can let go of the VOLDOWN button... and put the phone down gently .. you dont want to distrub this delicate process .
This may all depend on your bootloader - if your bootloader is locked, you likely cannot get the phone into Fastboot mode.
Right - flashing via fastboot may not be possible right now if your bootloader is locked.
Yes - let's skip the kernels for now - and get you flashing a fresh FTF so you can start over. I suggest that once the FTF is flashed, and the phone can boot normally, you dial the Service Menu number and look to see if your phone has "Bootloader Unlock Allowed: Yes" or "Bootloader Unlock Allowed: No". -If it says NO, it means NO! There is currently (as of Feb3/2014) no way to get around this. This means your bootloader cannot be unlocked, which means no custom kernels, and no fastboot! Custom ROMS can still be flashed - just those that are Locked Bootloader-friendly (meaning, the custom rom operates just fine/is based on the Stock kernel - whatever version is preferred will be mentioned in the dev's first post of the thread). There are a few.. like XperimenT and T-Hybrid. I like those.
I'm going to be safe and assume yours says No (like mine, because everyone should suffer with me!! ) You can then ROOT the system like you did, then install CWM Recovery for locked bootloaders (v8!! dont use v9 for now), then you can flash a rom or do whatever. If the custom rom you're installing is based on a stock kernel whose version number is different from your phone's base, then you may be able to find kernel zips that are flashable via CWM - since they are stock kernels, the flash will be allowed because they are signed or whatever. Example: Since you're going for LT30p .141 FTF, you're on the 141 kernel. If the rom you're installing says it recommends the .145 kernel, find the LT30P .145 kernel zip. You can flash that right after flashing the ROM. I think that the 141/145 kernels are similar to each other so in this case, you may not even have to flash from 141 to 145. But you will - because you will become addicted to flashing like the rest of us and you will want to observe/compare how the ROM behaves on each.
I think what it's really asking you is to Unlock Your Bootloader. Unlocking the bootloader is kind of considered a global root (because it allows writing to any partition on the phone.
Yes - hopefully above we have tackled that.
Agreed!! Good luck!
Click to expand...
Click to collapse
man . you got some real patience to write all those. its just what i wrote in twoo lines :silly:
---------- Post added at 01:48 AM ---------- Previous post was at 01:41 AM ----------
pfhastie said:
Thanks for the considered responses. hhamzah49, I have tried to use the bootloader unlock in the flash tool, but it simply waits for me to connect in flash mode, which is what I am unable to do. There is not even an opportunity of using a SD card since I cannot start the phone either normally or in a recovery environment.
LaZiODROID, you're the man for going into so much detail, and yes I am looking forward to trying out loads of ROMs if possible, however I can't consider such luxuries until I've flashed the phone back to stock! It seems the bootloader probably has a lot to do with it, and I wish I could confirm one way or another if it is locked or not, but I don't see a way to do that in the phone's current state. I bought it from Amazon UK in October or thereabouts, so perhaps that might give you a clue - I would assume it is locked for now, but happy to try the process working on the assumption that it is unlocked if that is likely to help.
I am already using the Flash Tool you suggested and have OKed the drivers signature on Windows 7. I understand about not connecting the phone prior to preparing the flash tool (in flashmode) - and making sure it is fully off by pressing power and volume down until I feel the three vibrations indicating the phone is fully off - but all this seems to be immaterial as I am never able to connect in flash mode. Only the blue light ever appears, never the green one.
You say it is likely that I will not be able to connect the phone in fast boot mode because my bootloader is locked, however I am ONLY able to connect in fast boot mode so if I am not able to flash via fast boot, I am not sure what other course of action to take.
I think I understand now about the unlocked bootloader and having to source suitable ROMs when the time comes, but not quite there yet.
I have uploaded several images of my current connection via Command Prompt, Device Manager, Android Flash Tool 0.9.13.0 & DooMLoRD's Easy Rooting Toolkit 17. I also noticed that when I start DooMLoRD's Easy Rooting Toolkit 17 with no ADB drivers running in Windows Task Manager Processes, two instances of the ADB driver appear, each leading back to DooMLoRD's Easy Rooting Toolkit 17 and each a slightly different size. When I try to run the Rooting Toolkit, the command prompt simply says "daemon started successfully", but nothing happens after this. If I kill one of the two ADB processes, this seems to start the program off, but to no avail since "device not found" is displayed repeatedly.
Anyway, my comatose phone and I remain on standby ready to try whatever it takes.
Click to expand...
Click to collapse
bro we got two buttons vol up and vol down. while connecting to flashtool ,holding the vol up key enters fastboot mode, and holding vol down key enters flashmode. if even holding vol down key makes u enter fastboot mode!!! try vol up key. i m just not sure about it. just give it a shot

rough map
romeoofair said:
man . you got some real patience to write all those. its just what i wrote in twoo lines :silly:
Click to expand...
Click to collapse
Pretty much. You can tell it's doing my head in surely ("Don't call me Shirley").
Anyway, the devil is in the details. I am convinced this can be done once all the parameters are crystal clear.

pfhastie said:
Pretty much. You can tell it's doing my head in surely ("Don't call me Shirley").
Anyway, the devil is in the details. I am convinced this can be done once all the parameters are crystal clear.
Click to expand...
Click to collapse
anyway flashtool is the best sol for your issue bro. hope your device gets back on track soon. sorry i was too lazy to write a long post. so i gave it roughly

pfhastie said:
Pretty much. You can tell it's doing my head in surely ("Don't call me Shirley").
Anyway, the devil is in the details. I am convinced this can be done once all the parameters are crystal clear.
Click to expand...
Click to collapse
try to do a hard reset; (while NOT connected via usb or something) hold power+vol up, it will vibrate 1 time, and then 3 times quick. After that try to connect the usb (NOT while pressing any buttons) and press vol down+power
That should connect it into flashmode.

romeoofair said:
man . you got some real patience to write all those. its just what i wrote in twoo lines :silly:
---------- Post added at 01:48 AM ---------- Previous post was at 01:41 AM ----------
bro we got two buttons vol up and vol down. while connecting to flashtool ,holding the vol up key enters fastboot mode, and holding vol down key enters flashmode. if even holding vol down key makes u enter fastboot mode!!! try vol up key. i m just not sure about it. just give it a shot
Click to expand...
Click to collapse
OK, I'm totally aware that this seems to be the main clincher, if I can somehow get it into flash mode (with green light), but I have tried connecting it pressing every combination of button I can think of, but it only ever connects in fast boot (with blue light). I'm just gonna grab a bite just now, but will try this some more right after and let you know (turning the phone off with one vibration, then three, up and down buttons etc). Thanks again for now.

romeoofair said:
man . you got some real patience to write all those.
Click to expand...
Click to collapse
Thank you. A patient attitude and thorough reply from others is what has kept me coming back to this forum.
its just what i wrote in twoo lines :silly:
Click to expand...
Click to collapse
I disagree.
pfhastie said:
You say it is likely that I will not be able to connect the phone in fast boot mode because my bootloader is locked,
Click to expand...
Click to collapse
I believe I said "if", not "because". The status was unknown to me. I couldn't say anything certain about your device.
I have uploaded several images of my current connection via Command Prompt, Device Manager, Android Flash Tool 0.9.13.0 & DooMLoRD's Easy Rooting Toolkit 17. I also noticed that when I start DooMLoRD's Easy Rooting Toolkit 17 with no ADB drivers running in Windows Task Manager Processes, two instances of the ADB driver appear, each leading back to DooMLoRD's Easy Rooting Toolkit 17 and each a slightly different size. When I try to run the Rooting Toolkit, the command prompt simply says "daemon started successfully", but nothing happens after this. If I kill one of the two ADB processes, this seems to start the program off, but to no avail since "device not found" is displayed repeatedly.
Click to expand...
Click to collapse
Since your phone doesn't boot into a system, I'm not sure if DoomLord's rooting kit will help you. What is there to root? There's no Android system running yet for it to root (right?).

Great news
You beautiful, beautiful people!
I managed to get the phone into flash mode by following your exact instructions to turn the phone fully off when disconnected from the PC (by pressing power & volume up until I felt three vibrations following a single vibration), then connected the phone again WITHOUT pressing the volume down button (as I had always been doing before), then, after the red light came on and the Sony logo appeared, pressing power & volume up again until suddenly the beautiful green light lit up and I was able to flash the phone back to stock firmware (LT30P_9.1.A.1.141_PL.ftf). I lost flashmode the first time because I was so shocked, and there doesn't seem to be time to hang around, but the second time I connected it again the firmware flashed immediately, fairly quickly and without any issues and I am now looking at my freshly started phone and the virgin Sony Android screen.
I have to say this process is unquestionably difficult to explain over the internet, probably because there is no universal implementation of the buttons, but at least once you know how, you are sorted for future problems (of this type at least).
I swear to god, I feel about a stone lighter as this was really hanging over me - not only am I too skint to be worrying about dead phones and warranty issues, but now I feel more secure testing things out, and might even be able to help others in the same predicament in future. I'm not sure if all the excessive detail was warranted, but better to err on the side of caution as a general principle I believe.
My sincere thanks to everyone for helping me out! You have given me a great introduction to the site and I look forward to any and all future communications.
Sadly, I have a pile of crap to attend to, now I know the phone is working, so I will regather my strength for a fresh attempt at rooting the phone (with DooMLoRD Easy Rooting Toolkit 18 For Sony Xperia Devices), installing a recovery environment (CWM v8 as opposed to v9), then flashing a suitable ROM tomorrow evening. I checked my service menu and it states, "Rooting status: Bootloader unlock allowed: Yes," which I trust opens my options a bit more. The two ROMs I am initially wishing to try are CyanogenMod and KitKat, but would be nice to know I could try others without more problems. I am now also aware to backup the TA Partition via the Android Flash Tool 0.9.13.0 before rooting the phone and assume I should hold off reinstalling my Titanium Backups until I am happy with a particular ROM.
I expect this isn't the place to go over these things (although I am quite happy to do so), so I will start a new thread tomorrow to go over my best plan of action.
Thanks again, and I hope this helps out someone else in the same position!

Wicked! Happy flashing. I'm jealous of your unlockable bootloader!

LaZiODROID said:
Wicked! Happy flashing. I'm jealous of your unlockable bootloader!
Click to expand...
Click to collapse
Thank you, LaZiODROID. You've been more than helpful so I trust you don't mind my quickly confirming what I now understand about the bootloader now you have so succinctly brought it to my attention.
I previously hadn't taken into account the state of the bootloader when I tried to flash a ROM, so my failure (Status 7 Error) probably suggests that the bootloader must currently be locked, although it is possible to unlock it on my particular handset (but not yours), is that correct?
All I knew when I used Doomlord's Rooting Kit was that the bootloader would not be affected thus preserving my warranty status, however it would be advisable for me to unlock the bootloader using the Android Flash Tool 0.9.13.0 so I can install custom ROMs without having to worry about special packages like XperimenT & T-Hybrid, is that also correct?
The only final query I have is, if I do unlock the bootloader (using the Android Flash Tool) in order to flash custom ROMs, can I then lock it again for the purposes of my warranty?
I shall assume the bootloader should be unlocked AFTER rooting the device, but BEFORE installing the CWM Recovery Environment.
Thanks again! I will rest easier tonight.

I think hhamzah49 is the hero who got you going with that nice trick (to get you into flashmode)! I guess it turned out that you didn't have driver issues after all.
pfhastie said:
I previously hadn't taken into account the state of the bootloader when I tried to flash a ROM, so my failure (Status 7 Error) probably suggests that the bootloader must currently be locked, although it is possible to unlock it on my particular handset (but not yours), is that correct?
Click to expand...
Click to collapse
Yes. If you're gonna do it, read up (re: backing up your TA, etc.) I have read with bootloader unlocking, you also lose DRM apps like TrackID and the Bravia engine? If you dont use those then you probably won't mind.
All I knew when I used Doomlord's Rooting Kit was that the bootloader would not be affected thus preserving my warranty status
Click to expand...
Click to collapse
Right.
however it would be advisable for me to unlock the bootloader using the Android Flash Tool 0.9.13.0 so I can install custom ROMs without having to worry about special packages like XperimenT & T-Hybrid, is that also correct?
Click to expand...
Click to collapse
There is also the official Sony method of unlocking your bootloader (see the all-in-one thread). Re: ROMS... I guess it's not so much "worrying" about roms like XperimenT/T-Hybrid - they are good roms and they install via CWM recovery just like any other custom ROM, and they will run on an unlocked bootloader. You just have more ROM selection with an unlocked bootloader because you can use the kernels that ROMS like Cyaongen needs.
The only final query I have is, if I do unlock the bootloader (using the Android Flash Tool) in order to flash custom ROMs, can I then lock it again for the purposes of my warranty?
Click to expand...
Click to collapse
Read up to be sure - but I see in Flashtool that there is an FTF for bootloader re-locking (but more importantly it is linked in the all-in-one thread also)... so it sounds like it won't be too hard to re-lock if you need to.
I shall assume the bootloader should be unlocked AFTER rooting the device,
Click to expand...
Click to collapse
Yes so you can back up your TA after rooting?
but BEFORE installing the CWM Recovery Environment.
Click to expand...
Click to collapse
That I'm not certain of. I think that recovery can be installed whether your bootloader is locked or unlocked. For unlocked bootloaders, there are kernels that have recovery built in so you can just fastboot flash one of them.

pfhastie said:
You beautiful, beautiful people!
I managed to get the phone into flash mode by following your exact instructions to turn the phone fully off when disconnected from the PC (by pressing power & volume up until I felt three vibrations following a single vibration), then connected the phone again WITHOUT pressing the volume down button (as I had always been doing before), then, after the red light came on and the Sony logo appeared, pressing power & volume up again until suddenly the beautiful green light lit up and I was able to flash the phone back to stock firmware (LT30P_9.1.A.1.141_PL.ftf). I lost flashmode the first time because I was so shocked, and there doesn't seem to be time to hang around, but the second time I connected it again the firmware flashed immediately, fairly quickly and without any issues and I am now looking at my freshly started phone and the virgin Sony Android screen.
I have to say this process is unquestionably difficult to explain over the internet, probably because there is no universal implementation of the buttons, but at least once you know how, you are sorted for future problems (of this type at least).
I swear to god, I feel about a stone lighter as this was really hanging over me - not only am I too skint to be worrying about dead phones and warranty issues, but now I feel more secure testing things out, and might even be able to help others in the same predicament in future. I'm not sure if all the excessive detail was warranted, but better to err on the side of caution as a general principle I believe.
My sincere thanks to everyone for helping me out! You have given me a great introduction to the site and I look forward to any and all future communications.
Sadly, I have a pile of crap to attend to, now I know the phone is working, so I will regather my strength for a fresh attempt at rooting the phone (with DooMLoRD Easy Rooting Toolkit 18 For Sony Xperia Devices), installing a recovery environment (CWM v8 as opposed to v9), then flashing a suitable ROM tomorrow evening. I checked my service menu and it states, "Rooting status: Bootloader unlock allowed: Yes," which I trust opens my options a bit more. The two ROMs I am initially wishing to try are CyanogenMod and KitKat, but would be nice to know I could try others without more problems. I am now also aware to backup the TA Partition via the Android Flash Tool 0.9.13.0 before rooting the phone and assume I should hold off reinstalling my Titanium Backups until I am happy with a particular ROM.
I expect this isn't the place to go over these things (although I am quite happy to do so), so I will start a new thread tomorrow to go over my best plan of action.
Thanks again, and I hope this helps out someone else in the same position!
Click to expand...
Click to collapse
so my idea about vol up button instead of vol down button worked !!!!!!!! . its usually for entering fastboot mode. i just gave a try :silly:

LaZiODROID said:
I think hhamzah49 is the hero who got you going with that nice trick (to get you into flashmode)! I guess it turned out that you didn't have driver issues after all.
Yes. If you're gonna do it, read up (re: backing up your TA, etc.) I have read with bootloader unlocking, you also lose DRM apps like TrackID and the Bravia engine? If you dont use those then you probably won't mind.
Right. There is also the official Sony method of unlocking your bootloader (see the all-in-one thread). Re: ROMS... I guess it's not so much "worrying" about roms like XperimenT/T-Hybrid - they are good roms and they install via CWM recovery just like any other custom ROM, and they will run on an unlocked bootloader. You just have more ROM selection with an unlocked bootloader because you can use the kernels that ROMS like Cyaongen needs.
Read up to be sure - but I see in Flashtool that there is an FTF for bootloader re-locking (but more importantly it is linked in the all-in-one thread also)... so it sounds like it won't be too hard to re-lock if you need to.
Yes so you can back up your TA after rooting? That I'm not certain of. I think that recovery can be installed whether your bootloader is locked or unlocked. For unlocked bootloaders, there are kernels that have recovery built in so you can just fastboot flash one of them.
Click to expand...
Click to collapse
i feel awesome! Good luck trying roms and stuff!

[Q] Sony Xperia Z Patching Problems

Morning all,
First time poster here, I'll try to make this as concise as possible.
Short / TLDR Question: My Sony Xperia Z handset isn't able to install the 10.31.a.2.67 patch either via WiFi or the Sony Companion. Any ideas appreciated.
Longer Version I've recently picked up Sony Xperia Z to replace an older one that I'd damaged in stag do celebrations. Research indicated it would be cheaper to get a new one rather than spring for repairs. The OS version on the replacement is 4.1.2 with build number 10.1.a.1.350. It's a pre-owned one and looks like it's had a soft reset from the settings menu. I've run through and installed the stuff I need, configured it preferred but the last thing I can't do is to install the patch. I'm led to believe that the phone has been developed against as
1 - Plugging it into a desktop via the USB led it to enter debugging mode
2 - There is a root viewer application on the handset
3 - Developer options were turned on
I've tried to get the patch installed a number of times but to no avail. It'll download something (as shown via the GUI) but upon restart all I see is the Xperia logo, a successful boot and then the error message to state it won't install. I don't have access to any log files or error messages to let me take this further.
Because of the above, I'm thinking that a previous developer has possibly something to stop any further patches installing? The fixes I've tried this far: -
1 - Updating the patch from cable doesn't work. The Sony Companion can't detect the phone when connected via the USB
2 - Checking that the default applications are installed.
As such, I'm not sure where to turn next. Any ideas would be appreciated.
Update: I work as an IT professional and as such I'm comfortable with devices and operating systems. I'm not used to development or the sort of development that's involved with android devices.

backpackerd00d said:
Morning all,
First time poster here, I'll try to make this as concise as possible.
Short / TLDR Question: My Sony Xperia Z handset isn't able to install the 10.31.a.2.67 patch either via WiFi or the Sony Companion. Any ideas appreciated.
Longer Version I've recently picked up Sony Xperia Z to replace an older one that I'd damaged in stag do celebrations. Research indicated it would be cheaper to get a new one rather than spring for repairs. The OS version on the replacement is 4.1.2 with build number 10.1.a.1.350. It's a pre-owned one and looks like it's had a soft reset from the settings menu. I've run through and installed the stuff I need, configured it preferred but the last thing I can't do is to install the patch. I'm led to believe that the phone has been developed against as
1 - Plugging it into a desktop via the USB led it to enter debugging mode
2 - There is a root viewer application on the handset
3 - Developer options were turned on
I've tried to get the patch installed a number of times but to no avail. It'll download something (as shown via the GUI) but upon restart all I see is the Xperia logo, a successful boot and then the error message to state it won't install. I don't have access to any log files or error messages to let me take this further.
Because of the above, I'm thinking that a previous developer has possibly something to stop any further patches installing? The fixes I've tried this far: -
1 - Updating the patch from cable doesn't work. The Sony Companion can't detect the phone when connected via the USB
2 - Checking that the default applications are installed.
As such, I'm not sure where to turn next. Any ideas would be appreciated.
Update: I work as an IT professional and as such I'm comfortable with devices and operating systems. I'm not used to development or the sort of development that's involved with android devices.
Click to expand...
Click to collapse
By "patch" are you referring to firmware update?

androidtweaker1 said:
By "patch" are you referring to firmware update?
Click to expand...
Click to collapse
Yes

backpackerd00d said:
Morning all,
First time poster here, I'll try to make this as concise as possible.
Short / TLDR Question: My Sony Xperia Z handset isn't able to install the 10.31.a.2.67 patch either via WiFi or the Sony Companion. Any ideas appreciated.
Longer Version I've recently picked up Sony Xperia Z to replace an older one that I'd damaged in stag do celebrations. Research indicated it would be cheaper to get a new one rather than spring for repairs. The OS version on the replacement is 4.1.2 with build number 10.1.a.1.350. It's a pre-owned one and looks like it's had a soft reset from the settings menu. I've run through and installed the stuff I need, configured it preferred but the last thing I can't do is to install the patch. I'm led to believe that the phone has been developed against as
1 - Plugging it into a desktop via the USB led it to enter debugging mode
2 - There is a root viewer application on the handset
3 - Developer options were turned on
I've tried to get the patch installed a number of times but to no avail. It'll download something (as shown via the GUI) but upon restart all I see is the Xperia logo, a successful boot and then the error message to state it won't install. I don't have access to any log files or error messages to let me take this further.
Because of the above, I'm thinking that a previous developer has possibly something to stop any further patches installing? The fixes I've tried this far: -
1 - Updating the patch from cable doesn't work. The Sony Companion can't detect the phone when connected via the USB
2 - Checking that the default applications are installed.
As such, I'm not sure where to turn next. Any ideas would be appreciated.
Update: I work as an IT professional and as such I'm comfortable with devices and operating systems. I'm not used to development or the sort of development that's involved with android devices.
Click to expand...
Click to collapse
whats your phone model number?

Hi all,
Thanks for looking at this thread.
To answer the questions
1 - yes, I mean the Sony pushed firmware updates
2 - Model number is C6603
Cheers

backpackerd00d said:
Hi all,
Thanks for looking at this thread.
To answer the questions
1 - yes, I mean the Sony pushed firmware updates
2 - Model number is C6603
Cheers
Click to expand...
Click to collapse
download firmware from here
download flashtool from here
flash the firmware using flashtool

Thanks for the links. I'm assuming the flash tool has instructions? I've not flashed a handset before.

backpackerd00d said:
Thanks for the links. I'm assuming the flash tool has instructions? I've not flashed a handset before.
Click to expand...
Click to collapse
Click here for instructions

[Q] sim and screen pin locked i dont know how to unlocked

hi everyone my English not so good
please solve my problem ASAP
i try everything but not working i don't know why
I have an Xperia sp, and tried to root it with Flash tool, but the application doesn't recognize the phone. I already made sure the phone is in the correct mode and installed the phone model drivers that are in /Flashtool/Drivers/ ... but still says "Device connected with USB debugging off"
03/005/2014 22:05:31 - INFO - Flashtool Version 0.9.18.3 built on 10-20-2014 08:00:00
03/005/2014 22:05:31 - INFO - Executing search strategies to find proxy selector
03/005/2014 22:05:32 - INFO - No proxy found for IE. Trying next one
03/005/2014 22:05:32 - INFO - No proxy found for firefox. Trying next one
03/005/2014 22:05:32 - INFO - No proxy found for java. Trying next one
03/005/2014 22:05:33 - INFO - Syncing devices from github
03/005/2014 22:05:33 - INFO - Scanning devices folder for changes.
03/005/2014 22:05:52 - INFO - Pulling changes from github.
03/005/2014 22:05:54 - INFO - Devices sync finished.
03/005/2014 22:05:58 - INFO - Device disconnected
03/006/2014 22:06:17 - INFO - Selected Bundle for Sony Xperia SP (C5303). FW release : 12.1.A.1.207. Customization : AU
03/006/2014 22:06:17 - INFO - Preparing files for flashing
03/006/2014 22:06:56 - INFO - Please connect your device into flashmode.
03/008/2014 22:08:38 - INFO - Flash canceled
m using flash-tools with full charging
When I press the FASTBOOT button
Volume down with USB connect
first on blue led and then RED led appear and standby then phone standby in charging mode. when my finger gets hurt after 2mins off holding down Volume Up button there is no response.
what can i do now?

Amz47 said:
hi everyone my English not so good
please solve my problem ASAP
i try everything but not working i don't know why
I have an Xperia sp, and tried to root it with Flash tool, but the application doesn't recognize the phone. I already made sure the phone is in the correct mode and installed the phone model drivers that are in /Flashtool/Drivers/ ... but still says "Device connected with USB debugging off"
03/005/2014 22:05:31 - INFO - Flashtool Version 0.9.18.3 built on 10-20-2014 08:00:00
03/005/2014 22:05:31 - INFO - Executing search strategies to find proxy selector
03/005/2014 22:05:32 - INFO - No proxy found for IE. Trying next one
03/005/2014 22:05:32 - INFO - No proxy found for firefox. Trying next one
03/005/2014 22:05:32 - INFO - No proxy found for java. Trying next one
03/005/2014 22:05:33 - INFO - Syncing devices from github
03/005/2014 22:05:33 - INFO - Scanning devices folder for changes.
03/005/2014 22:05:52 - INFO - Pulling changes from github.
03/005/2014 22:05:54 - INFO - Devices sync finished.
03/005/2014 22:05:58 - INFO - Device disconnected
03/006/2014 22:06:17 - INFO - Selected Bundle for Sony Xperia SP (C5303). FW release : 12.1.A.1.207. Customization : AU
03/006/2014 22:06:17 - INFO - Preparing files for flashing
03/006/2014 22:06:56 - INFO - Please connect your device into flashmode.
03/008/2014 22:08:38 - INFO - Flash canceled
m using flash-tools with full charging
When I press the FASTBOOT button
Volume down with USB connect
first on blue led and then RED led appear and standby then phone standby in charging mode. when my finger gets hurt after 2mins off holding down Volume Up button there is no response.
what can i do now?
Click to expand...
Click to collapse
If you want to root, just be relaxed and follow this guide. You don't need flashtool at all.
TIP: You can actually leave the volume buttons once the phone is detected on the flashtool.

and solendat
TechnoSparks said:
If you want to root, just be relaxed and follow this guide. You don't need flashtool at all.
TIP: You can actually leave the volume buttons once the phone is detected on the flashtool.
Click to expand...
Click to collapse
bro my phone islock how i install app towelroot in my phone ?

Amz47 said:
bro my phone islock how i install app towelroot in my phone ?
Click to expand...
Click to collapse
Lol why didn't you mentioned that in the OP? Anyways, can I know, does your phone currently rooted or not?
If it isn't, I am sad to announce, you'll have to wipe the data on your phone. This could be prevented, by entering your gmail address when requested.

TechnoSparks said:
Lol why didn't you mentioned that in the OP? Anyways, can I know, does your phone currently rooted or not?
If it isn't, I am sad to announce, you'll have to wipe the data on your phone. This could be prevented, by entering your gmail address when requested.
Click to expand...
Click to collapse
no its not rooted yet and its screen locked also sim locked thats why am in problem and this is second hand phone m not the first owner

Amz47 said:
no its not rooted yet and its screen locked also sim locked thats why am in problem and this is second hand phone m not the first owner
Click to expand...
Click to collapse
To recover is easy but do understand that this will wipe your data that reside in the internal memory (apps etc)
I am assuming you are on a stock ROM, follow this tutorial: http://forum.xda-developers.com/showthread.php?t=2476938

TechnoSparks said:
To recover is easy but do understand that this will wipe your data that reside in the internal memory (apps etc)
I am assuming you are on a stock ROM, follow this tutorial: http://forum.xda-developers.com/showthread.php?t=2476938
Click to expand...
Click to collapse
i tried but still not working bro do something for me

Amz47 said:
i tried but still not working bro do something for me
Click to expand...
Click to collapse
It should work! But as I already said, you'll need to flash again the stock ROM through the tutorial, in which will wipe your data definitely.

TechnoSparks said:
It should work! But as I already said, you'll need to flash again the stock ROM through the tutorial, in which will wipe your data definitely.
Click to expand...
Click to collapse
i try PC companion while updating there's error show your screen locked and i don't know my screen lock code
but still no happening
m also try flash tools at the the time of connect the phone was red led on then phone go on charge mode i don't know what the happening with my phone i tried every method

Amz47 said:
i try PC companion while updating there's error show your screen locked and i don't know my screen lock code
but still no happening
m also try flash tools at the the time of connect the phone was red led on then phone go on charge mode i don't know what the happening with my phone i tried every method
Click to expand...
Click to collapse
Please describe what happened when you tried to use the PC Companion. A reply with no explanation doesn't help at me on determining the problem. Also, could you confirm if you really followed every bit of the tutorial?
For your information, flashing through PC Companion is too easy I didn't expect that you didn't make it

TechnoSparks said:
Please describe what happened when you tried to use the PC Companion. A reply with no explanation doesn't help at me on determining the problem. Also, could you confirm if you really followed every bit of the tutorial?
For your information, flashing through PC Companion is too easy I didn't expect that you didn't make it
Click to expand...
Click to collapse
ok let me try again then i'll explain you

Amz47 said:
ok let me try again then i'll explain you
Click to expand...
Click to collapse
Okay, I am waiting. Please explain verbosely when you are done.

TechnoSparks said:
Okay, I am waiting. Please explain verbosely when you are done.
Click to expand...
Click to collapse
check this i tried but not happening because my sim and screen both locked
now what i do

Amz47 said:
check this i tried but not happening because my sim and screen both locked
now what i do
Click to expand...
Click to collapse
Remove your SIM card, and try again in PC Companion.

TechnoSparks said:
Remove your SIM card, and try again in PC Companion.
Click to expand...
Click to collapse
i m not using any sim in my mobile because of country code locked

Amz47 said:
i m not using any sim in my mobile because of country code locked
Click to expand...
Click to collapse
Oh I see. I am now assuming you are not installing complete drivers (based on how flashtool reacts), and you also have a 4.3 .207 ftf beforehand.
Please do so by navigating to C:\Flashtool (that's the default installation path, unless yours are different, navigate to yours instead) and then go into the "drivers" folder and run the .exe in it.
Tick "flashmode drivers", "fastboot drivers" and scroll down a bit; find "Common drivers for Viskan board" and tick it as well. Continue the installation. Restart is recommended when complete, and then retry with Flashtool on flashing the same firmware. I hope this one works, otherwise, I may not be able to help you.

i already install the drivers but its not working for me
by the way thank you for your help

i already install the drivers but its not working for me
by the way thank you for your help
TechnoSparks said:
Oh I see. I am now assuming you are not installing complete drivers (based on how flashtool reacts), and you also have a 4.3 .207 ftf beforehand.
Please do so by navigating to C:\Flashtool (that's the default installation path, unless yours are different, navigate to yours instead) and then go into the "drivers" folder and run the .exe in it.
Tick "flashmode drivers", "fastboot drivers" and scroll down a bit; find "Common drivers for Viskan board" and tick it as well. Continue the installation. Restart is recommended when complete, and then retry with Flashtool on flashing the same firmware. I hope this one works, otherwise, I may not be able to help you.
Click to expand...
Click to collapse
i already install the drivers but its not working for me
by the way thank you for your help