Hi guys,
I have decided to make this thread to help the people who are not sure how to fix their brick. We get a lot of threads with people panicking because their phone is bricked. I wanted to avoid this, by making this general guide to get rid of that awful brick. I know that there is already a thread like this available, but it faded away and I wanted to be more clear. It can be found here: http://forum.xda-developers.com/showthread.php?t=1849170. I find it a bit messy... If I'm offending someone, please say so! I'm not trying to bash Toledo_JAB!
Ok, now that has been made clear we can start
First of all, I want to give you a few tips to avoid a brick and how to prepare for it.
1. Make sure to have your phone’s battery charged 100%. Just to be sure.
2. Always make a back-up of your data. Just root your phone, download Titanium Backup and back up those precious apps! When rooting is too much for you, use Helium(formerly Carbon) or Mobile GO. Both work fine. If you have a custom recovery installed, make a Nandroid. This is a copy of your whole phone in the state before the brick, and recovering this will get your phone back to the land of the living.
3. Just avoid the ‘’vold.fstab trick’’. It is dangerous and can cause hard bricks(yes, hard bricks!)
4. Always be prepared that it could happen. When unlocking the bootloader, it can happen. When giving incorrect permissions to a system app, it can happen. BE PREPARED, AND JUST MAKE A FRIGGIN’ BACK-UP!
What is a brick?
A brick(on an Android device) is when there are uncorrectly modified system files that cause your Android device not to boot. Your device will refuse to boot completely, because it can’t simply load some stuff that are vital for the eventual boot-up. Something you don’t want, right?
Before we can begin, you have to know there are two kinds of bricks. Soft bricks and hard bricks. The most important difference between these two is that a soft brick can be fixed, and a hard brick can’t be fixed!
The most common sign of a soft brick will be that when you boot your phone the bootanimation will play, then freeze and then start all over again. This is also known as a ‘’bootloop’’. Sometimes the phone won’t reboot automatically, but just keep booting and booting without loading Android correctly. You can let it boot for a day, but it won’t work and your battery will die. Don't worry, we can fix this!
The most common sign of a hard brick is that your phone won’t do anything. No, really. Nothing. Try not to panick when you see this, but keep calm. If you have your warranty, you can laugh like a maniac because Sony will send you a new one. If not, still try to follow the steps listed below.
Let’s start. There is a difference between people who have a custom recovery, and people who don’t have a custom recovery.
People with a custom recovery can restore their Nandroid(if you have made one, ofcourse…).
People without a custom recovery will have to follow my humble steps.
Method 1: use Androxyde’s mighty Flashtool to flash a stock .ftf.
For extra info, use this extremely detailed guide: http://forum.xda-developers.com/showthread.php?t=2240614 . It says Xperia Z, but it is the same for the E.
1. Download Flashtool from here: http://www.flashtool.net/index.php
2. Install it. Now locate the folder where you installed it(probably C:/Flashtool). Open the drivers folder, and run the file inside it.
3. In the huge list, scroll down to the bottom and tick the ‘’flashmode’’ and ‘’fastboot’’ drivers. A common misunderstood problem is that you need the specific phone drivers, and that the drivers for the Tipo(dual), Miro, J and E(dual) are missing. But this isn’t a problem, I can assure you. Those have been automatically be installled when you plugged your phone in your computer the first time.
4. When installed, make sure to download a stock .ftf firmware for your device. These are the Android images that have been released by Sony, which have been manually pulled of the phones.
For Tipo, see here: http://forum.xda-developers.com/showthread.php?t=2001567
For Miro, see here: http://forum.xda-developers.com/showthread.php?t=1998277
For J, see here: http://forum.xda-developers.com/showthread.php?t=2385526
For E, see here: http://forum.xda-developers.com/showthread.php?t=2553609
Pick one you like . It doesn’ actually matter. Download it, and put it in the C:/Flashtool/firmwares folder.
5. Open Flashtool. If you’re on a 64bit computer, pick the 64bit version.
6. Click the thunder icon in the upper left corner.
7. Tick ‘’flashmode’’.
8. Select your .ftf. You can try to untick ‘’data’’ and ‘’cache’’, and then flash. Perhaps your apps will still be there! If this doesn’t work, you can tick them.
9. Hit ‘’flash’’. Flashtool will prepare the files.
10. A popup window will appear. Now, listen carefully: be sure that your phone is off, and get your micro USB cable. First: put it in the computer. Now, what you have to do is press(and hold) the volume down button and plug the cable in your phone. A green led will apppear.
11. Let Flashtool flash! After it’s finished, boot your phone and see the magic happen .
Note: sometimes you get an error with system.sin. To fix this, pick another firmware or redownload the same and delete the ‘’prepared’’ folder in C:/Flashtool.
This should work! If not, try the methods listed below, and otherwise don’t be shy to ask. If the led turns green you are completely safe. Try another computer and avoid Windows 8.
Method 2: even simpler than method 1, but it should work fine. We will be using Sony Update Service.
1. Download the SUS from here: http://www.sonymobile.com/global-en/tools/update-service/
2. Run, and accept the license agreement.
3. Locate your device, click it and hit ‘’next’’.
4. Now follow the instructions. It’s as simple as that.
5. Your data will definitely be erased, but your phone will be fixed again!
Note: Sony Update Service will refuse to work for devices with an unlocked bootloader. If your bootloader is unlocked you have no other choice than to use the Flashtool method.
This should work fine!
Method 3: my least favorite method. It didn’t work for me, but perhaps it will for you. Just try. We will be using the Sony PC Companion software… If you haven’t already installed it, do it from here: http://www.sonymobile.com/global-en/tools/pc-companion/
Make sure that your phone is powered off!
1. Disregard any instructions to connect the phone until you complete step 9
2. In the welcome screen you will see the different modules available for you including the "support zone" option. Click on "Start" below it.
3. On the next page Click on "Start" under "Phone/Tablet Software update"
At this point if you get an error stating that "unable to install update components" or "server is bussy" Please proceed to step 12. If you not see that error then continue with step 4.
4. The program will show a window saying "Could not find phone/tablet". Click on the option below that reads: "Repair my phone/tablet" the program will issue you a warning on the content that you will lose during the update
5. Choose the option to continue.
6. The program will issue a final message warning you of possible data lost during the update. Click on the checkmark and then on "Next/Continue".
7. After that, the program will download the necessary information (5 to 6 minutes) and it will present you with a list of phones.
8. Choose the Phone from the list then click on "next" then you will see a new section telling you how to connect the phone. (don't connect it yet)
At this point the phone must be off and disconnected from the PC.
9. Connect the cable to the PC not to the phone, then wile pressing and holding the volume down button, connect the cable to the phone and keep holding the volume button until the program says "the update of your phone has started..." (in some cases a message of "Installing drivers" will appear before the message of "the update of your phone has started..." is shown.)
10. If you failed to follow the steps correctly the phone will turn on and it will request that you "Proceed with the following steps, slide down the notification bar", If this happens disconnect the phone from the cable, turn it off and repeat from step 9).
11. If the phone is connected properly, PC Companion will proceed with the update ( It will tell you to let go of the back key) then wait for the update to finish and follow instructions on screen to disconnect the unit.
This tutorial doesn’t belong to me. It is fully copied from here: http://talk.sonymobile.com/t5/Xperi...ctions-using-Pc-Companion-Windows/td-p/249946
I do not own any rights, I just want to share to make it easier to use. Full credits go to Francis .
These methods should have helped you! If not, don’t hesitate to ask!
Hard bricked users, I can’t help you, sorry . If this doesn’t work, I am sorry.
Allright! That's it!
Just a few requests
1. If you seek help, don't quote the whole original post(OP). Please!
2. Don't make useless posts! If you want to thank me, press that button. If not, that's fine too. I don't mind.
3. Be polite and try to be as clear as possible in english. I know some of you don't speak it very well, but please, try your best!
Have a nice day, and I hope this helps!
hi!
i tried all 3 methods (on win 8)
none work
method 1
says
Code:
05/029/2014 18:29:56 - INFO - <- This level is successfully initialized
05/029/2014 18:29:56 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
05/029/2014 18:29:56 - INFO - You can drag and drop ftf files here to start flashing them
05/030/2014 18:30:04 - INFO - Device disconnected
05/030/2014 18:30:10 - INFO - Selected ST23i_4_0_4_xperia.ftf
05/030/2014 18:30:10 - INFO - Preparing files for flashing
05/030/2014 18:30:42 - INFO - Please connect your device into flashmode.
05/030/2014 18:30:57 - INFO - Device connected in flash mode
05/030/2014 18:30:57 - INFO - Opening device for R/W
05/030/2014 18:30:57 - INFO - Reading device information
05/030/2014 18:30:57 - INFO - Phone ready for flashmode operations.
05/030/2014 18:30:57 - INFO - Current device : ST23i - YT9100P9HP - 1265-6133_R4D - 1261-5091_11.0.A.5.5 - WORLD-i_11.0.A.5.5
05/030/2014 18:30:58 - INFO - Start Flashing
05/030/2014 18:30:58 - INFO - Processing loader
05/030/2014 18:30:58 - INFO - Checking header
05/030/2014 18:30:58 - INFO - Ending flash session
05/030/2014 18:30:58 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0019";ERR_DYNAMIC="SIN header verification failed";
05/030/2014 18:30:58 - ERROR - Error flashing. Aborted
05/030/2014 18:30:58 - INFO - Device connected in flash mode
05/030/2014 18:30:59 - INFO - Device disconnected
05/031/2014 18:31:01 - INFO - Device connected in flash mode
method 2 dont have miro in devices offered
method 3
wont start at all
ok i fixxed it with ST23i_11.0.A.2.10_Generic and help from this post
messmeww said:
you can try push this file >>> http://www.mediafire.com/?j27mk33p62pb60k to your FTF file using 7zip, and flash your ftf file again after do that ^_^
Click to expand...
Click to collapse
if mediafire link don't work try here
Loader.sin
for Androxyde’s mighty Flashtool to flash a stock .ftf. METHOD,
is there risk of bricking your phone????///
mine is currently in bootloop now... its in there since I was trying to unlock bootloader ..cmd says its successfully done but as I plugged it out its not starting since then - only bootloop
Nikhil_android said:
for Androxyde’s mighty Flashtool to flash a stock .ftf. METHOD,
is there risk of bricking your phone????///
mine is currently in bootloop now... its in there since I was trying to unlock bootloader ..cmd says its successfully done but as I plugged it out its not starting since then - only bootloop
Click to expand...
Click to collapse
No. Flashtool will only fix the bootloop, not cause a new one.
Mats
IMP- About drivers automatically getting installed (fastboot & flashmode drivers have to be manually installed)
1)works on Win7, Win8 not on XP
2)you must be connected to the internet for automatic driver install (& also it must be enabled in settings somewhere[if you get "serching for drivers" its enabled])
3)Win8 not reliable as windows 7 so......... 7 recommended
---------- Post added at 11:49 AM ---------- Previous post was at 11:46 AM ----------
Nikhil_android said:
for Androxyde’s mighty Flashtool to flash a stock .ftf. METHOD,
is there risk of bricking your phone????///
mine is currently in bootloop now... its in there since I was trying to unlock bootloader ..cmd says its successfully done but as I plugged it out its not starting since then - only bootloop
Click to expand...
Click to collapse
if you got bootloop you did it correctly .....flash stock ftf after that, you are ready
it worked
I used the first method (as that was the only option available for me) and it indeed solve the problem of bootloop.
here is what happened exactly:
I used Windows 7 32 bit pc as guide asks to avoid w8 -8.1.
followed steps exactly as said in guide but after connecting the phone (xperai E dual c 1605) there was error and flashing process was aborted but meanwhile some driver got installed. Its strange because I remember that I had installed all necessary driver (had connected my phone quite few times on this pc and had connected phone by vol down and connect to pc to get green light way as well ) and had also installed driver through flashtool as said in steps in tutorial..
anyway I rebooted my pc because I thought that would complete driver installation process and tried again but it did not worked and again some driver got installed but then this time instead of rebooting I tried again immediately and it worked this time.
So if u get error and instead some driver get installed just try again and most probably it will work
tip : use right click Run as admin on any exe file
PS : quote: . In the huge list, scroll down to the bottom and tick the ‘’flashmode’’ and ‘’fastboot’’ drivers. in latest flashtool version those options are right at top :silly:
---------- Post added at 10:39 PM ---------- Previous post was at 10:20 PM ----------
if you got bootloop you did it correctly .....flash stock ftf after that, you are ready
Click to expand...
Click to collapse
I have flashed it and everything is fine but now I am not sure whether my bootloader is locked or unlocked .. I searched but there is no definate way to tell .. in xperia Z forum some asked to flash a kernel and if you get error it means its bootloader is locked (though I am not sure if it will harm phone and again cause bootloop or not ( off cou2rse I wont flash xperia Z kernel on xperia E dual ))
Nikhil_android said:
I have flashed it and everything is fine but now I am not sure whether my bootloader is locked or unlocked .. I searched but there is no definate way to tell .. in xperia Z forum some asked to flash a kernel and if you get error it means its bootloader is locked (though I am not sure if it will harm phone and again cause bootloop or not ( off cou2rse I wont flash xperia Z kernel on xperia E dual ))
Click to expand...
Click to collapse
type *#*#7378423#*#* in dialer (only on stock rom/ftf)
go to Service info > Configuration >
If "Bootloader unlock allowed" says "yes" its still locked
or
If Bootloader Unlocked says "yes" SUCCESS!!
or
If "Bootloader Unlock Status" says "yes" SUCCESS!!
xperia
hey my xperia miro flashing is nt starting only please help
awesomesal said:
hey my xperia miro flashing is nt starting only please help
Click to expand...
Click to collapse
This forum exists to help you, but we can't do that with this information!
Please answer this questions:
-Can you get into flashmode? Phone off, USB in computer then hold volume down button while inserting USB in phone. A green LED will show.
-When you start the phone, does it vibrate?
-Is there a red LED blinking when you start the phone?
-What have you done with your phone that it became bricked like this?
That should give us the information we need.'
Mats
xperia
yes i can go in flashmode , it vibrate while on simply and no red led while simply on the phone.
I off ma alarm n wen i tried to open the patren it got stuck n nw stuck at sony logo.
I dint unlock bootloader neither its rooted
Thank u
You forgot Sony's flashtool method and of course for UBLs flashing kernel to get cwm
awesomesal said:
yes i can go in flashmode , it vibrate while on simply and no red led while simply on the phone.
I off ma alarm n wen i tried to open the patren it got stuck n nw stuck at sony logo.
I dint unlock bootloader neither its rooted
Thank u
Click to expand...
Click to collapse
I don't see the problem then. Yes, you are in a boot loop. OK, use flashtool to flash a stock .ftf. Method 1 of the tutorial.
Mats
Sent from my Xperia E using XDA Premium 4 mobile app
xperia
whch al driver r needed n how much tym it wl take to flash.
ok.
So I got similiar problem - I bought bricked phone to fix and sell further , I don't know what was happen to it.
1. ...---> When I turn on it vibrate once and blink green led
2. I can get flashmode - I flash soft via flashtool and vias SUS - both with succes - but when I turn on it vibrates ....--> goto1.
Is there any suggestion? Or sell it further as is it is just to retrieve money :laugh:
Miro ST23i
LindaCento said:
ok.
So I got similiar problem - I bought bricked phone to fix and sell further , I don't know what was happen to it.
1. ...---> When I turn on it vibrate once and blink green led
2. I can get flashmode - I flash soft via flashtool and vias SUS - both with succes - but when I turn on it vibrates ....--> goto1.
Is there any suggestion? Or sell it further as is it is just to retrieve money :laugh:
Miro ST23i
Click to expand...
Click to collapse
Try using flashtool. It always works for me.
I rooted mobile a while ago so suddenly one day it went in bootloop. So i tried to factory reset it after that still it didn't work out. After that i decided to just go for other rom so i unlocked my bootloader and tried to install cm 12.1. But wifi doesn't work on it also also it doesn't detect sim card.
Can anyone tell me how to set it to old device. I don't want any fashionable thing no root no recovery nothing i just want a phone back with wifi working and not rebooting like hell. I tried to download the original .ftf file but that also not flashing showing session ending error and please don't tell me to reinstall drivers i tried it already. my xperia L model is c2014. I also tried emma and those how don't know emma doesn't support some models and sadly one of which is my device. Plz anyone can tell me a easy process or something hopefull that i can try to get my phone back.And is sony service center will be able to help me if i give them my phone to service?
nisarg007 said:
I rooted mobile a while ago so suddenly one day it went in bootloop. So i tried to factory reset it after that still it didn't work out. After that i decided to just go for other rom so i unlocked my bootloader and tried to install cm 12.1. But wifi doesn't work on it also also it doesn't detect sim card.
Can anyone tell me how to set it to old device. I don't want any fashionable thing no root no recovery nothing i just want a phone back with wifi working and not rebooting like hell. I tried to download the original .ftf file but that also not flashing showing session ending error and please don't tell me to reinstall drivers i tried it already. my xperia L model is c2014. I also tried emma and those how don't know emma doesn't support some models and sadly one of which is my device. Plz anyone can tell me a easy process or something hopefull that i can try to get my phone back.And is sony service center will be able to help me if i give them my phone to service?
Click to expand...
Click to collapse
It is indeed a driver issue. If WiFi isn't working, you can flash stock ftf and then install whichever rom you were installing. Firstly, to get back to stock and relock your bootloader you need your TA. If you didn't backup your TA before unlocking your bootloader, You'll have to live with some functions of the stock rom lost. Restoring the TA locks your bootloader.
Okay so, if you have the stock ftf, head over to your flashtool folder, navigate to drivers and open Flashtool-drivers.exe.
For Xperia L, the drivers you need - "Flashmode Drivers", "Fastboot drivers", "Common drivers for Taoshan".
If install fails, you may need to disable driver signature check. Just google that, it's pretty simple.
If you don't see such a file, just get it from here - [Drivers] FlashTool Xperia Driver Pack (v1.5) [20140318]
Then connect your phone in FLASHmode. Not Fastboot. Fastboot has a blue LED and Flashmode has no LED (You'll see red and green flash before the no LED). Your device should be listed under Universal Serial Bus Controllers as SEMC Flash Device or Generic Flash device. If it says S1 Service or something similar, right click and update Driver Software, "Browse my computer for driver software", and let me pick from a list. Uncheck Show compatible Hardware, scroll to Sony Ericsson Mobile Communications, and select SEMC Flash device. Reconnect your device to check if it detects it as SEMC or Generic Flash Device. If yes, try to install your ftf.
If you were already on this driver, try switching to the S1 Service. (Not sure where to find that but it never worked for me. Your mileage may vary. Give it a search).
Also, if you take it to a service center, they'll probably charge you some money and probably replace the whole board. Thus, Hakuna Matata. Keep calm, your phone is absolutely fine. Never tried Emma though. Flashtool ftw!
Agent_fabulous said:
It is indeed a driver issue. If WiFi isn't working, you can flash stock ftf and then install whichever rom you were installing. Firstly, to get back to stock and relock your bootloader you need your TA. If you didn't backup your TA before unlocking your bootloader, You'll have to live with some lost functions of the stock rom lost. Restoring the TA locks your bootloader.
Okay so, if you have the stock ftf, head over to your flashtool folder, navigate to drivers and open Flashtool-drivers.exe.
For Xperia L, the drivers you need - "Flashmode Drivers", "Fastboot drivers", "Common drivers for Taoshan".
If install fails, you may need to disable driver signature check. Just google that, it's pretty simple.
If you don't see such a file, just get it from here - [Drivers] FlashTool Xperia Driver Pack (v1.5) [20140318]
Then connect your phone in FLASHmode. Not Fastboot. Fastboot has a blue LED and Flashmode has no LED (You'll see red and green flash before the no LED). Your device should be listed under Universal Serial Bus Controllers as SEMC Flash Device or Generic Flash device. If it says S1 Service or something similar, right click and update Driver Software, "Browse my computer for driver software", and let me pick from a list. Uncheck Show compatible Hardware, scroll to Sony Ericsson Mobile Communications, and select SEMC Flash device. Reconnect your device to check if it detects it as SEMC or Generic Flash Device. If yes, try to install your ftf.
If you were already on this driver, try switching to the S1 Service. (Not sure where to find that but it never worked for me. Your mileage may vary. Give it a search).
Also, if you take it to a service center, they'll probably charge you some money and probably replace the whole board. Thus, Hakuna Matata. Keep calm, your phone is absolutely fine. Never tried Emma though. Flashtool ftw!
Click to expand...
Click to collapse
Thanks will try. Changing board costs like 4-5 k and my phone is 2 year old so not replacing board rather i will go for a new device. I will surely try what u suggested. Thanks for help bro thanks a lot
So, i havent been modding Android phones in a long time and when I wanted to flash MM on my Z5, i forgot that i dont have the Z5 drivers. Now, based on what i know, i did have SONY PC COMPANION installed prior to soft bricking my device, so i would assume the drivers are installed. My current situation is as follows:
-Device wont turn on, switches between RED/GREEN led with error message of "update failed, please connect to PC etc..."
-Sony pc companion doesnt seem to recognize the phone as i cant repair it
-Cannot flash FTF through as it keeps failing to flash at different points, do not know if not having the Z5 drivers play a factor here. I got the drivers from there but i do not know what to do with it as it is not .exe file, i also have the latest flashtool installed.
-I backed up my files prior to this, so i am willing to wipe everything.
Thank you, i would appreciate if i can get some assistant on this. Stupid me for making this mistake in the first place.
Regards,
Litoni
Use PC Companion repair option (marked with a red box on my screenshot).
LitoNi said:
So, i havent been modding Android phones in a long time and when I wanted to flash MM on my Z5, i forgot that i dont have the Z5 drivers. Now, based on what i know, i did have SONY PC COMPANION installed prior to soft bricking my device, so i would assume the drivers are installed. My current situation is as follows:
-Device wont turn on, switches between RED/GREEN led with error message of "update failed, please connect to PC etc..."
-Sony pc companion doesnt seem to recognize the phone as i cant repair it
-Cannot flash FTF through as it keeps failing to flash at different points, do not know if not having the Z5 drivers play a factor here. I got the drivers from there but i do not know what to do with it as it is not .exe file, i also have the latest flashtool installed.
-I backed up my files prior to this, so i am willing to wipe everything.
Thank you, i would appreciate if i can get some assistant on this. Stupid me for making this mistake in the first place.
Regards,
Litoni
Click to expand...
Click to collapse
What Windows version ?
Follow
# STEP 1 - GENERAL GUIDE
INSTALL / CHECK DRIVERS
of
http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
and (re-)boot into (newer) Windows by disabling the driver signature verification.
Log in with administrator rights,
Extract the zip-file,
there you have inf files
https://en.wikipedia.org/wiki/INF_file
https://msdn.microsoft.com/en-us/library/windows/hardware/ff549520(v=vs.85).aspx
right-click on those and choose install - so that the device drivers are installed.
Reboot (of Windows) shouldn't be necessary.
Entering Fastboot mode should still be possible, check whether it's being recognized now (via Minimal ADB and Fastboot).
Remember: in case the device goes crazy because it's not being detected upon connection - you can still turn it off via
Emergency off
(listed under "#FASTBOOT / FLASHMODE / RECOVERY / etc.")
Install the drivers that are inside flashtool.
Mr_Bartek said:
Use PC Companion repair option (marked with a red box on my screenshot).
Click to expand...
Click to collapse
As mentioned, SPCC doesn't recognize my phone. It somewhat does but doesn't give me the option to repair. There are these other screens which i think are prior to the repair page (hopefully) but i was stuck at the page when it asks me to remove the battery or skip if built in. It asks me to press ok to skip but hitting the ok button didn't do anything.
zacharias.maladroit said:
What Windows version ?
Follow
# STEP 1 - GENERAL GUIDE
INSTALL / CHECK DRIVERS
of
http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
and (re-)boot into (newer) Windows by disabling the driver signature verification.
Log in with administrator rights,
Extract the zip-file,
there you have inf files
https://en.wikipedia.org/wiki/INF_file
https://msdn.microsoft.com/en-us/library/windows/hardware/ff549520(v=vs.85).aspx
right-click on those and choose install - so that the device drivers are installed.
Reboot (of Windows) shouldn't be necessary.
Entering Fastboot mode should still be possible, check whether it's being recognized now (via Minimal ADB and Fastboot).
Remember: in case the device goes crazy because it's not being detected upon connection - you can still turn it off via
Emergency off
(listed under "#FASTBOOT / FLASHMODE / RECOVERY / etc.")
Click to expand...
Click to collapse
Thanks my desktop is running windows 10 and i know theres so many issues with it.
gm007 said:
Install the drivers that are inside flashtool.
Click to expand...
Click to collapse
The drivers from flashtool does not include any xperia Z5 series.
Thank you guys for the quick responses, I managed to reflash the .200 through flashtool without any hiccups. which is weird that it didn't work for .163 earlier. I didn't wipe anything, so after flashing .200 i updated the SDK stuff from Google SDK.exe which i think it solved some, from there I flashed .163 (MM) again and it worked. Kept all data intact, even my encrypted Class 10 SD card worked without any issues. So far so good, haven't really encountered any errors, fingers crossed :fingers-crossed: once again thank you for the quick responses.
Hi! So I'm new in this forum and I'm trying to flash Xperia xa2 Ultra H3223 but had two problems, first I try flashing with Flashtool but no matter what it said "no partition delivery" or something "yes to continue", found some forum and said something about copying file 50.2.fsc and manually sync but again, clicked and nothing happened. Then I installed Emma but the only firmware was from the US (I'm from Mexico) and was a custom old version 50.1 with no other option. Finally, I just installed Newflasher, follow the instructions and nothing, just this:
"ERROR: TIMEOUT: failed with error code 997 as follows:
Se estß ejecutando la operaci¾n de E/S superpuesta.
- Error write! Need nBytes: 0x18 but done: 0x0
nBytes[0x0]:
- Error writing command getvar:max-download-size!
End. You can disconnect your device when you close newflasher.exe"
I've done everything, followed every tutorial and nothing seems to work.
By the way, I'm trying to flash firmware 50.2A.3.22, last year my phone bricked and the only thing I found was firmware Commercial and Journalists wich worked well but now I want to try other version and then LineageOs but guess I'll have to wait.
Don't know what I'm doing wrong, if I turn on my phone works perfect and nothing been erased.
My device is bootloader unlocked and no root.
Please let me know if you need to know something else, I'm not desperate but was kind of excited to try Lineage
Thanks!
I had the same problem with my H3113.
While I had installed flashtool and the drivers that come with it, it seems like they are too old for the XA2. They are from 2014.
What I had to do was get flashtool from the Sony website and open up the .exe with 7-Zip:
https://developer.sony.com/develop/open-devices/get-started/flash-tool
Inside of that is the file Sony_Mobile_Software_Update_Drivers_x64_Setup.exe - this one installs a driver from 2017.
After a reboot, flashing with Newflasher worked. What a damn pain!
I had the same problem and can confirm it works. I wish I saw this comment earlier.
If you flash with flashtool will it relock bootloader?
I am running Windows 10 Pro v. 21H1 and also have a Sony H3223.
I am trying to install the latest plain LineageOS on the phone for which is still supported. The H3223 is unlocked so there are a variety of guides for different flashing projects.
LineageOS wiki suggests installing a universal ADB driver which sadly does not apply for this phone. So I then took a peek at SailfishOS and their flashing guide... incidentally, they specify the use of Sony's Xperia X driver. This forum has a thread suggesting the use of Sony's Xperia XZ2 driver.
SailfishOS was specifying the XZ2 driver as well until they updated their guide for Windows 21H1.
I have tried to install both drivers in alteration—both times I uninstalled everything Android via safe mode—and both drivers will not properly install. I get the icon with the yellow triangle badge in my Device Manager list for 5 seconds but then it changes immediately to the questions mark badge and is only visible after showing hidden devices. This is true even while the phone is plugged in.
The phone is being connected via the included USB cable and is being plugged into a USB 2.0 port on my PC.
The phone when connected does get picked up by Windows and I get listings in other places under Device Manager. ADB sees my phone when I run any adb commands but booting into fastboot mode makes the above happen every time.
In other words, when I connect the phone to my PC, Windows installs some driver from who knows where. At this point, adb commands work but fastboot commands don't work. After this, I uninstall the stuff Windows sets up and I boot the phone into fastboot mode only. When this happens, Windows only shows an Android listing under Device Manager for hidden devices. This is the same device that is designated for the driver update in any guide I find... so at this point I have tried updating this object with the Xperia X and Xperia XZ2 drivers. The Sony object that's supposed to get added to the device tree is never added an instead it's as if nothing happened.
I have followed both the LineageOS guide and SailfishOS guide and I have no clue why Windows will not update the driver. There is nothing complicated about either guides... as I said, adb commands work but that is without me installing any driver and Windows does stuff. The only time I see what I'm supposed to see is when all drivers are uninstalled and I connect the phone to my PC while it's going into fastboot mode. However, Windows will not properly see the phone in fastboot mode due to the driver not being applied.
Hello!
I have tried to upgraded my phone to Lineage 18.1 but it did not work.
This is what I did so far:
1) Installed the NEWEST TWRP and unfortunately I have deleted the OS. After that, the USB connection worked fine and I was able to see all files on my phone.
2) I've found a stock recovery.img that I have used and then the problem started. After installing that recovery.img file now I have TWRP (older version) 2.7.0.0 and:
a) when connected through USB , my computer does make sound, but it does NOT recognize my phone any more. Yes, I do have the newest USB drivers installed
b) when connected through USB and when I run this command: fastboot devices, then it DOES shows my device number, but it DOES NOT any devices using adb command.
c) when booting into fastboot, the phone shows just the black screen with the android faded icon.
d) I can boot into TWRP but there is no system or recovery files in there and it look like it's just useless.
I'm not sure what to do next. It looks like the phone is soft-bricked.
Any help will be appreciated.
Thank you
the first thing i would try is flashing twrp 3.6 (the newest) using fastboot. not sure why you would flash an old recovery version. if data recovery is not an issue then the opo is even fixable after a hardbrick (i used to have it). i used the color os method but that was ages ago. now there is a slightly easier way somewhere here on xda if you want the opo to in out of the box condition.
maybe try the whole thing using a secondary old laptop (if possible) or a virtual machine. otherwise i have no idea. sounds like a lot of trial and error might be needed. good luck.