Database Develop

[Q] Xperia T LT30at is stuck at Sony screen.[SOLVED]

The problem.
When I boot the device it just stays at the Sony screen and does not progress any further. I am still able to turn off the device by holding the power button and the volume up button, I can reset it by holding the button longer waiting for the vibration, and I can hard reset by waiting till the three vibrations.
What I was doing up to the point it happened.
I was trying to get a custom ROM on my device, I had it previously rooted so I thought I would go further. I installed CWM on my phone I wiped data, cache, and dalvick then I went to install the ROM from SD card. During the attempt at installation I got some symlink errors with a status of 7. Not sure what to do turned off the device when I decided to put back its previous I turned it back on and arrived at the problem.
What I have done to try and fix it.
I have done the soft and hard resets, I tried using the PC companions repair tool. When it asks me to turn the device off hold down the power button then plug in the device nothing happens(I have tried this several times.) I downloaded the flashtool and the correct ftf and tried using that, but it doesn't detect my device when I hold down the volume button and plug it in. So it seems that the flashboot is not working on my phone.
Any suggestions on what to try would be much appreciated and thanks in advanced.

tabersays said:
The problem.
When I boot the device it just stays at the Sony screen and does not progress any further. I am still able to turn off the device by holding the power button and the volume up button, I can reset it by holding the button longer waiting for the vibration, and I can hard reset by waiting till the three vibrations.
What I was doing up to the point it happened.
I was trying to get a custom ROM on my device, I had it previously rooted so I thought I would go further. I installed CWM on my phone I wiped data, cache, and dalvick then I went to install the ROM from SD card. During the attempt at installation I got some symlink errors with a status of 7. Not sure what to do turned off the device when I decided to put back its previous I turned it back on and arrived at the problem.
What I have done to try and fix it.
I have done the soft and hard resets, I tried using the PC companions repair tool. When it asks me to turn the device off hold down the power button then plug in the device nothing happens(I have tried this several times.) I downloaded the flashtool and the correct ftf and tried using that, but it doesn't detect my device when I hold down the volume button and plug it in. So it seems that the flashboot is not working on my phone.
Any suggestions on what to try would be much appreciated and thanks in advanced.
Click to expand...
Click to collapse
You probably didn't install the ADB drivers. Install them from the Flashtool folder (use the ones for TX) and then try flashing your stock FTF again. Remember to put the device into Flashmode.
Basically what happened was that while flashing your ROM the script that flashes everything deletes everything from the /system partition, then you got an error and the installation was incomplete, therefore there is no proper system to boot into. You could have easily avoided what happened by flashing a different ROM had you not powered off.

Antiga Prime said:
You probably didn't install the ADB drivers. Install them from the Flashtool folder (use the ones for TX) and then try flashing your stock FTF again. Remember to put the device into Flashmode.
Basically what happened was that while flashing your ROM the script that flashes everything deletes everything from the /system partition, then you got an error and the installation was incomplete, therefore there is no proper system to boot into. You could have easily avoided what happened by flashing a different ROM had you not powered off.
Click to expand...
Click to collapse
Thank you for response, I went and used the Flashtool-driver.exe and installed the Flashmode drivers, Fastboot drivers and the TX drivers. But it does not seem to have changed anything. To enter flash mode on the phone one has to hold down the volume down button while plugging the phone into the usb when it is powered off, right? Flash tool just sits at the instruction animation titled Wait for Flashmode. When I try to enter flashmode I do not get a response from either the program or the phone. Any more suggestions would be welcomed.
Thank you for taking the time to help.

tabersays said:
To enter flash mode on the phone one has to hold down the volume down button while plugging the phone into the usb when it is powered off, right? Flash tool just sits at the instruction animation titled Wait for Flashmode. When I try to enter flashmode I do not get a response from either the program or the phone. Any more suggestions would be welcomed.
Thank you for taking the time to help.
Click to expand...
Click to collapse
Yes, that is how you enter flashmode. Turn off phone, and keep volume down button pressed while you connect the USB cable; the LED light should turn on with a green light. If you're phone is not entering Flashmode, then you might have a faulty USB cable, or there might be problems with your USB ports, either on your computer or your phone (try with different cables/computers).
Also, check your Device Manager (while phone is connected) to make sure the drivers are properly installed. If you have Windows 8, you should have had to turn of Driver Signature Checking in order for the drivers to install properly.

Antiga Prime said:
Also, check your Device Manager (while phone is connected) to make sure the drivers are properly installed. If you have Windows 8, you should have had to turn of Driver Signature Checking in order for the drivers to install properly.
Click to expand...
Click to collapse
Yes, it's better to work on Windows 7 or lower....

Antiga Prime said:
Yes, that is how you enter flashmode. Turn off phone, and keep volume down button pressed while you connect the USB cable; the LED light should turn on with a green light. If you're phone is not entering Flashmode, then you might have a faulty USB cable, or there might be problems with your USB ports, either on your computer or your phone (try with different cables/computers).
Also, check your Device Manager (while phone is connected) to make sure the drivers are properly installed. If you have Windows 8, you should have had to turn of Driver Signature Checking in order for the drivers to install properly.
Click to expand...
Click to collapse
Yeah I turned off the Driver signature checking on my computer when I did it. I'll go buy a new cable and try a friends windows 7 computer. Hopefully there is nothing wrong with the USB port in my phone. Thank you for your help I'll let you know how it goes.

Thank you everybody for your support. My phone is now working. After my phones battery died I was able to get it charging, when it had enough energy it booted itself to the Sony screen so I turned it off and grabbed my new micro USB cable and was able to get it into flash mode. Everything is now working great. I wish a special thanks to Antiga Prime for taking the time to help me.

Have I hard-bricked my device?

Please excuse me if I'm repeating a prior question but it seems far too specific to trawl through pages of related threads to make sure.
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
3. All was going swimmingly, I entered fastboot mode absolutely fine, flashed CWM using fastboot which all loaded up absolutely fine.
3. At this stage ADB was not picking up my device at all, tried different cables, ports, all of the usual. What I didn't do was make a backup, and then I wiped all of the things that it's possible to wipe thinking to myself that I was going to get Cyanogenmod on there so all would be fine...
4. Finally I (quite stupidly) restored from memory card (which had already been wiped) from inside CWM, the device restarted and now I am getting no response AT ALL.
5. Sometimes it will load the Sony 'splash' logo that first appears but sometimes not, when plugged in the device is recognised and ADB actually sees the device but lists it as offline... Interestingly at this stage windows device installer actually installs Sony ADB driver for me automatically.
6. All I'm getting at the moment is a red flashing LED although when I plug in via USB the device is again recognised when I type adb devices but again is offline...
If any more information is needed please, I will be more than happy to give a quick reply.
Thank you in advance

JJrmc said:
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
Click to expand...
Click to collapse
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.

AkiraProject said:
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
Click to expand...
Click to collapse
I was trying to end up with a rooted device running Cyanogenmod, I've been putting it off and off looking into the whole rooting scene and mistakenly dived in a little too quick without knowing what I was doing.

after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.

AkiraProject said:
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
Click to expand...
Click to collapse
Firstly AkiraProject thank you for your time on this.
I do realise that in my stupidity I could have loaded the cm-11-20141112-SNAPSHOT-M12-honami.zip to my SD card (if I'd had one or waited and gotten one).
What I did however was wipe everything I possibly could, and then hit restore from sdcard/0/ I believe - it may have been a different directory.
I believe what I have done is restored to a blank image......
WHen not plugged into usb I get a red blinking LED when just pressing the power button once.
When holding volume-up + Power the phone vibrates as if it is trying to boot but is unable to
If I leave it plugged into USB AND then press , the device shows the sony Logo and then proceeds to display a backlit but plain black screen, Sony PC Companion recognises the device as connected but is unable to interact with it. The output of "adb devices" shows my device but says "unauthorized" and windows is attempting to install MTB driver....
The behaviour doesnt seem to be quite the same every time.
I believe the device is soft bricked.... is this likely to be a case of a wiped partition table? Or at least loss of the boot partition?
If I leave the device plugged in via USB it periodically reboots itself, shows the Sony logo, remains on a bank screen then shuts itself down.
Shows in device manager as "USB Input Device" on win 7 x64 pro
Thanks in advance

Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app

D33KK said:
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
Click to expand...
Click to collapse
I have done quite a lot of reading etc on the subject....
according to This thread, Sony Xperias have the bootloader in non-writable mask ROM... so you should always be able to access Fastboot or Flash Mode?
The problem I am having is that I don't seem to be able to activate EITHER Fastboot OR Flash mode in order to flash some new firmware onto my device....
My device is recognized as a "USB Input Device" on Device Manager and windows tries to install MTP driver. I'm going to have a go at the process with a fresh install of windows 7 x64 and 'windows auto-install drivers' turned off.
What is the maximum damage I could have done here?
Thanks

Update
Hard reset (red button inside of the sim-card slot) resets the phone with three vibrates and it restarts.
The phone powers on and displays Sony splash screen and then displays a back-lit black screen.
The phone gets much hotter than normal and powers on to the blank back-lit screen when on charge.
I have NO ACCESS to flash mode or fast boot. Any combination of buttons leads to the same outcome: single vibrate, red LED and the phone shows the Sony splash screen then blank screen, as if the button combinations are just ignored...
Flashtool DOES NOT recognize the device, although it is recognized as C6903 in device manager (I have Sony adb driver installed and have disabled the MTP driver that windows recommends).
Flashtool gives me the red error text about making sure drivers are installed and making sure the device isn't in MTP mode.
I'm at an absolute loss as to what to try next, can somebody shed any light on this? There are plenty of guides but they all seem to rely on EITHER fastboot or flash mode and I can access neither although the phone powers on!
Thanks in advance!

Maybe the partition was corrupted when you flash "blank" image..........
So....JTAG....or send to Sony service....

Shutdown with power+vol up (will vibrate thrice) and see if it doesn't turn on automatically.
If it didn't turn on now check your task manager on windows, go to process tab, kill adb.exe (every adb.exe)
Back on phone connect usb holding down the vol down button (phone have to be off before you connect usb), if green led turns on and doesn't turn off you are on flashmode.
Check on flashtool or flashtool64 (for 64bits) and see if flashtool detects your device. If it detects and recognizes your phone flash the FTF for your device and let it do its job.
As you messed the phone Sony will charge for repairs.

Can' access bootloader nor recovery...

Hi,
I have a major issue since the update to CM13.0-20160524-NIGHTLY-huashan. I litteraly spent the whole week trying everything I found on internet in order to solve it without success.
My problem is the following one: I uninstalled the gapps to manually update it for the latest version of Android (Android 6.0.1), when I tried to boot to the recovery nothing happened the phone just restart, same when trying to boot to the bootloader. I tried everything adb reboot recovery adb reboot bootloader, I tried flashtool, I used the developper options to reboot to recovery, I tried manually by holding the volume button while restarting, I tried the flashify application. Nothing, I am not able in anyway to access neither the recovery nor the bootloader. The phone is just restarting, the led is first blue then goes red then green then red and restart. However, I have a root shell on the phone with adb shell.
If anyone have a solution, can help me please do it. An Android phone without the gapps is quite useless.
Thank you very much,

same problem,my phone is now without working android (after i tried instal CyanogenMod 13.0 Unofficial SaberMod.....still loading cyanogenmod logo) and without working fastboot and recovery so im lost :/

Hello, since the LED bar lights up this means your device is soft bricked, in which, mostly are recoverable.
What interests me is that you tried to, quote, "uninstall gapps".. If you previously have gapps, you don't need to "uninstall" gapps in order to update to the next build. Just flash the new build zip and gapps will be preserved. Also I am quite skeptical about what you did, as I never heard of a way to actually uninstall gapps. Basically if someone wants to remove gapps, he needs to format the System partition and then flash the ROM zip again..
Are you sure you failed to boot into flashmode? the correct procedure to do so is
Make sure the device is turned off
Make sure the USB cable is connected to your PC
Hold the volume DOWN button
Still holding the button, insert the USB cable to the XSP
LED will light up green, indicating flashmode
But even so, since you are on an unlocked bootloader, recovering from this brick is rather easy.
Get yourself a TWRP img file from the TWRP basketbuild folder
Open flashtool
Make sure the device is turned off
Make sure the USB cable is connected to your PC
Hold the volume UP button
Still holding the button, insert the USB cable to the XSP
LED will light up blue, indicating fastboot mode
On flashtool, click the lightning icon and select fastboot mode
On the right of the new window that appears, select "Select kernel to flash"
Navigate to your TWRP img file and select it
When flash completes, unplug your XSP from the USB cable
This will flash TWRP into /boot partition. So when you start your device, it will go straight to recovery.
Now, flash the ROM zip

Thanks for your help TechnoSparks, however, as I told you and expected even following your exact procedure my phone just restart. The led brights up bleu for few seconds then the phone put itself in charging mode. And when I said I delete the gapps, I meant that I deleted the google play store from my phone (this app was anyway not working after update). I tried to use flashtool but it is the same, can't get into fastboot mode, the phone just normally starts or put itself in charge. Isn't a manual solution on how to flash a recovery only using adb shell?

AresS31 said:
Thanks for your help TechnoSparks, however, as I told you and expected even following your exact procedure my phone just restart. The led brights up bleu for few seconds then the phone put itself in charging mode. And when I said I delete the gapps, I meant that I deleted the google play store from my phone (this app was anyway not working after update). I tried to use flashtool but it is the same, can't get into fastboot mode, the phone just normally starts or put itself in charge. Isn't a manual solution on how to flash a recovery only using adb shell?
Click to expand...
Click to collapse
That seems to be related to your USB cable (since that is the famous issue). Can you try to charge your phone WITHOUT it stop charging (i mean suddenly the LED disappears and when you tap the screen the charging icon doesnt show)?
If it so does happens that your device doesnt want to charge, it seems to me that you are having a loose USB port which possibly from your XSP, or, your USB cable is no longer up for the challenge
You will need to find another reliable USB cable for you to try. Try to charge your XSP to see if that particular USB cable is reliable for you. Try to wiggle the wire a little bit, moving the XSP from different directions and see if it would still charge. If it still charge, then this is the USB cable for you to use. Do the mentioned steps above again.
If you insist and want to use the same USB cable, you will need to find a "sweet spot" so that the connection between your XSP and the USB cable will remain reliable.

I think I bricked my phone. Update: fixed

UPDATE:
Please disregard this. I installed flashtool propery from flashtool.net and it was able to flash stock firmware. Also it looks like battery was fully drained, not sure how.
Now the phone is working. I lost root, but it's OK.
---old post---
I installed pre-rooted Android 6.0.1 image, everything was working. But, then I tried to install Magisk using this guide: http://www.droidopinions.com/magisk-pokemon-go/ because it was the first I found and it was simple.
After I flashed Magisk.zip, SuperSu.zip and rebooted, phone screen is black and nothing happens. If I hold power button, phone vibrates once, but only if not connected to power.
PC (Windows 7) showed phone as S1 service device with no drivers. I downloaded Flashtool from here https://github.com/Androxyde/Flashtool, installed drivers, now PC sees it as SOMC Flash device.
When I connect phone to PC LED light blinks red, then green once, then everything is black. And, neither fastboot nor adb see it. D5803.
What else can I do?
Thanks

Bricked Huawei P9 ( EvaL-09)

Hello everybody, :cyclops:__ sorry for my bad English __ :cyclops:
I have a big problem in my huawei p9 after soft update, i leave it for a night to complete the process of download, is updated but stay reboot again and again, i tired to install another firmware but nothing happened :crying: :crying: , so i googled for howa to install firmware via pc, i found by adb fastboot, and i flashed, but (Developer options, Screen lock & password, Camera, torch ...) Not working, i downloaded many firmware nothing works fine, i don't have a Box to repair this big problem.
Any help please please, any tool to update from pc
:crying: :crying:
:crying:
:crying: :crying: :crying:
:crying:
:crying:

Been there before, but recovering it is rather easy, first of all you have to install TWRP, you can do this by connecting the USB to your phone and PC and holding volume down to get to the white download mode screen, next use ADB, put the TWRP image in the ADB folder and type this: "fastboot flash recovery <twrp image name>.img" (without the "") from there remove the USB cable and reboot holding power and volume up until the Huawei logo appears, boot into TWRP and connect the USB cable back again. On your PC download a firmware for the phone and use Huawei Update Extractor to unzip it, find UPDATE.APP and keep it on the desktop. With your phone connected to your PC make a folder on the phone named "dload" and copy the UPDATE.APP file into it.
Shut the phone down and disconnect the USB cable, next hold volume up, down and power (yes, all three) and the phone should automatically force install the firmware and it should be fine from then on.
Hope this helps.

gamr13 said:
Been there before, but recovering it is rather easy, first of all you have to install TWRP, you can do this by connecting the USB to your phone and PC and holding volume down to get to the white download mode screen, next use ADB, put the TWRP image in the ADB folder and type this: "fastboot flash recovery <twrp image name>.img" (without the "") from there remove the USB cable and reboot holding power and volume up until the Huawei logo appears, boot into TWRP and connect the USB cable back again. On your PC download a firmware for the phone and use Huawei Update Extractor to unzip it, find UPDATE.APP and keep it on the desktop. With your phone connected to your PC make a folder on the phone named "dload" and copy the UPDATE.APP file into it.
Shut the phone down and disconnect the USB cable, next hold volume up, down and power (yes, all three) and the phone should automatically force install the firmware and it should be fine from then on.
Hope this helps.
Click to expand...
Click to collapse
Nop a tried all of the solution, i flashed recovery,system,boot (.img) through adb fast boot, nothing works fine, after turning up the phone ( Bluetooth not working, camera not found, security& password not woking, i cant access to Developer options)...., I think i flashed a bad firmware

just signed up to try to fix this problem myself, never used a forum before haha but i was a idiot.
im hoping that im just being an idiot and putting the wrong update in the dload folder, but ive also tried to do all of the steps above. then tried to upload a custom rom but none of them seem to want to work either. been trying to fix this for the last 2 days with no luck.