Related
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 tried to put AOSP 5.1 from FXP in my phone, and my cellphone bricked. It wont turn on, it keeps the Sony Logo 2 seconds. It haven't connection with flashtool. Please Help me.
Hi. Can you give me more information what you did exactly step by step. So maybe i can help you. My E3 was bricked too. I found a solution. But i need more information.
Flash stock rom it'll unbrick it
#4
Thank you answer back! I did exactly the following:
The model is my Xperia E3 D2212 dual sim.
- Unlocked the bootloader, :laugh:
- CWM installed a custom recovery, :laugh:
- I reinstalled the original rom, :laugh:
- I made a backup of the entire system using CWM.
And everything went super normal way, without complications.
The mistake was when he wanted to installing a custom ROM called "AOSP_L_MR1_150718_flamingo" because I found out later that he had not read that it was for ANOTHER XPERIA as follow the you tube tutorial . The ROM's for another Xperia, if I remember correctly.
After doing the installation process of the new AOSP ROM, the phone is less than a minute on the logo of SONY XPERIA down with, looped, can not enter the bootloader, and no longer recognizes the PC. I can not recognize it at FlashTool. I think that's all. :crying:
I greatly appreciate your attention.
I ended up editing this text in the google translator, then I'm sorry, if you are not very good.
Thank you
Matteus Maximo Felisberto said:
I tried to put AOSP 5.1 from FXP in my phone, and my cellphone bricked. It wont turn on, it keeps the Sony Logo 2 seconds. It haven't connection with flashtool. Please Help me.
Click to expand...
Click to collapse
Someone can help me please?
nibeal said:
Hi. Can you give me more information what you did exactly step by step. So maybe i can help you. My E3 was bricked too. I found a solution. But i need more information.
Click to expand...
Click to collapse
Could you help me? I can not make the pc recognize him ... He barely turns on and off since. The PC Companion software tells recognize it, but when you are installing the software says "it is not possible for this phone is changed." I can not scessar the bootloader does not give time and it shuts down.
Thanks, my error was with the fastboot driver and adb in flashtool. The Windows drivers wasn't been recognized, I've to install the drivers, all of they. After this, I Flashed the Stcok ROM, installed SuperSU and Restored the backup, everything works fine and fluid now. Thanks, anyway, for encouraging me.
I flashed my D2203 back to factory rom yesterday using Flashtool (flashtool.net/downloads.php) on Windows 7 PC.
How did I do it:
1) Install flashtool
2) Install Flashtool-drivers.exe from flashtool subfolder /drivers and select flashmode and fastboot drivers.
3) Run Flashtool and open XperiFirm (letters XF on logo)
4) Select Xperia E3 Flamingo -> proper D22** you have -> Market -> and select latest release below PayPal logo
5) Press "Download" and wait for download and unpacking
6) Switch off phone (if power on/off button does not respond then open back cover and push "OFF" by using pen)
7) Press and hold volume down button and connect phone to PC using original USB cable
8) Using Flashmode flash device
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
Kindly Help me,
I was Flashing my Z3 by Flash Tool , i accidently select D6646 ftf file instead *of D6616 ftf , during flashing Flash Tool gives error at Kernal.sin and Phone goes Down,
No Soft or Hard Reset Work,
NO Flashmood / Fastboot Mood work ,
Flash Tool only Show
'Device connected with USB debugging off
19/021/2017 07:21:01 - INFO *- For 2011 devices line, be sure you are not in MTP mode
and Device Manager Shows SOMC Flash Drive,
When Connect By press Vol Down button and Attach USB Cable, USB not Recognized Error Shows*on Windows 7
I have TA backup from Flash Tool ( ie T1 and T2 ) before flashing in case of Partition break, where as
I realize its kernel brokeup
Kindly Plese Guide me what can I do to live my phone back
are you sure fastboot mode doesnt work? just power off and press vol+ and power if led is blue then you are is fastboot mode. then try to flash kernel.sin in adb command with pc . cheers
Yes sir sureonly red led show just for 2 3 sec n then goes off flash tool shows debugging mode off .. i disconnect battery to completly shut off phone after that i connect n same probelm
https://forum.xda-developers.com/showthread.php?t=2646405
xkeita said:
https://forum.xda-developers.com/showthread.php?t=2646405
Click to expand...
Click to collapse
ihad used that trick after whole day research , I can conclude S1tools does not support 2012 upgrade model, I received error as ID HASH IS NOT SUPPORTED,
however my bootloder is unlocked, and I hav unlocked code also, and also phone is rooted ,
Yes this could work for us as we still doesn't have the preloader dump.
AFAIK there is not unbricking way for now.
Somewhere I read that pc companion could work with Q9008. Also worth to try with emma.
I want working on this to finalize the unbricking guide but will not be soon as I need my device for the rom port. When done I will work on this unbricking.
Also it is not a kernel problem. Your flash replaced s1 bootloader with a wrong one.
Good luck a be patient
What about this: https://forum.xda-developers.com/showthread.php?t=1849170 ?
nailyk said:
Yes this could work for us as we still doesn't have the preloader dump.
AFAIK there is not unbricking way for now.
Somewhere I read that pc companion could work with Q9008. Also worth to try with emma.
I want working on this to finalize the unbricking guide but will not be soon as I need my device for the rom port. When done I will work on this unbricking.
Also it is not a kernel problem. Your flash replaced s1 bootloader with a wrong one.
Good luck a be patient
What about this: https://forum.xda-developers.com/showthread.php?t=1849170 ?
Click to expand...
Click to collapse
Thankq sir, for your reply so if its s1 bootloader then is it possible to bring my phone again live will u guide me what the next thing should i do
talharais said:
Thankq sir, for your reply so if its s1 bootloader then is it possible to bring my phone again live will u guide me what the next thing should i do
Click to expand...
Click to collapse
Sorry for confusing :s
I think, today, there is no way.
You can try with the official emma flash tool or pc companion but I really doubt.
nailyk said:
Sorry for confusing :s
I think, today, there is no way.
You can try with the official emma flash tool or pc companion but I really doubt.
Click to expand...
Click to collapse
Ohhh , sir i have TA backup still cant do anything and also charging also doesnot solve problem as mention in one of the xda thread
https://forum.xda-developers.com/showthread.php?t=1849170&page=1
talharais said:
Ohhh , sir i have TA backup still cant do anything and also charging also doesnot solve problem as mention in one of the xda thread
https://forum.xda-developers.com/showthread.php?t=1849170&page=1
Click to expand...
Click to collapse
Not related with TA backup for now. You change your bootloader with a wrong one.
It is almost like if you flash the wrong bios on your mother board. You can't flash it again until someone find an 'electronic' way.
Give a try with pc companion or emma.
nailyk said:
Not related with TA backup for now. You change your bootloader with a wrong one.
It is almost like if you flash the wrong bios on your mother board. You can't flash it again until someone find an 'electronic' way.
Give a try with pc companion or emma.
Click to expand...
Click to collapse
Pc companion is not reconize the fevice actually i explain what i idid,
I was flashing d6616 by flash tool
Firstly i unlock bootloder by sony , through unlock code they email then i rooted the device by kingo root n then flash accidently i chosse d6646 rom instead of d6616 rom then during flashing flashtool gives error at kernal.sin and after that device goesoff
When i plug into the pc it reconize my device as SOMC Flash device andflash tool gives dubugging off
Thats was the whole senrio by which my device brick so after whole story i really disappointed to know that my device is just use for paper weight... :crying:
I downloaded the emma after install it desnot show any usb device
You own a d6616? It have unlockable bootloader :s
Send it to repair center. No other choice.
And yes it is confusing, it say bootloader unlock after the fastboot command but it is not true.
@blackhawk_LA made some posts about D6616. Maybe he could help you.
I just post here to announce you the bad new your device is hardly softbricked.
nailyk said:
You own a d6616? It have unlockable bootloader :s
Send it to repair center. No other choice.
And yes it is confusing, it say bootloader unlock after the fastboot command but it is not true.
@blackhawk_LA made some posts about D6616. Maybe he could help you.
I just post here to announce you the bad new your device is hardly softbricked.
Click to expand...
Click to collapse
Service status shows unlock bootloader to yes.. well very thankful for you reply means there is no way to unbrick my phone
talharais said:
Service status shows unlock bootloader to yes.. well very thankful for you reply means there is no way to unbrick my phone
Click to expand...
Click to collapse
Keep an eye on https://forum.xda-developers.com/z3/devs-only/unbricking-d6603-t3365262
I just brick my device too so will try to make some progress on it
nailyk said:
Keep an eye on https://forum.xda-developers.com/z3/devs-only/unbricking-d6603-t3365262
I just brick my device too so will try to make some progress on it
Click to expand...
Click to collapse
Tanks buddy I am watching your thread, and also let me know when done,
Hi, I decided to post it here because it seems that anything I post on Xperia Ion forum is not read, it is inactive.
I already searched everywhere and I'm loosing my hopes. I'm trying to revive an Xperia Ion and this is what I get:
When I plug the phone in the wall charger the red led turns on for some minutes and then turns off.
The same happens when I plug on PC, when the led turns off it is detected as "Somc flash device" in windows device manager and this shows in flashtool:
INFO - Device connected with USB debugging off
INFO - For 2011 devices line, be sure you are not in MTP mode
Nothing changes if I plug in pc with volume + or - pressed, it don't goes into fastboot or flashmode.
I hope you could help me. Thanks
dude i have the same problem as yours i have a z3 d6643 and i made a mistake when downloading the kernal the device loads normal flash mode and flashtools working! power button + volume down runs twrp but it no longer starts at sony black screen someone please help!
evilhedrox said:
Hi, I decided to post it here because it seems that anything I post on Xperia Ion forum is not read, it is inactive.
I already searched everywhere and I'm loosing my hopes. I'm trying to revive an Xperia Ion and this is what I get:
When I plug the phone in the wall charger the red led turns on for some minutes and then turns off.
The same happens when I plug on PC, when the led turns off it is detected as "Somc flash device" in windows device manager and this shows in flashtool:
INFO - Device connected with USB debugging off
INFO - For 2011 devices line, be sure you are not in MTP mode
Nothing changes if I plug in pc with volume + or - pressed, it don't goes into fastboot or flashmode.
I hope you could help me. Thanks
Click to expand...
Click to collapse
Same problem with an XZ, someone has a solution?
sometime Win recognize the device as QUSB_BULK
Looks like I killed my Z5. The model is 6683 (Z5 dual), and I flashed with E6533 (Z3+ dual).
The phone is completely dead, cannot turn on, not vibrating on power button etc.
When I connect to my laptop, it says "unable to recognize USB device", in detail VID_0000&PID_0000.
But if I disconnect the battery, it recognized as "SOMC Flash device", VID_0FCE&PID_DDDE
Is it possible to resurrect it?
I hope if I can flash with correct bootloader in this state, it will enought to boot up and able to flash with the right firmware.
Macs1209 said:
Looks like I killed my Z5. The model is 6683 (Z5 dual), and I flashed with E6533 (Z3+ dual).
The phone is completely dead, cannot turn on, not vibrating on power button etc.
When I connect to my laptop, it says "unable to recognize USB device", in detail VID_0000&PID_0000.
But if I disconnect the battery, it recognized as "SOMC Flash device", VID_0FCE&PID_DDDE
Is it possible to resurrect it?
I hope if I can flash with correct bootloader in this state, it will enought to boot up and able to flash with the right firmware.
Click to expand...
Click to collapse
Are you able to connect it in flashmode and fastboot ?
With battery, no.
Without battery, my laptop recognize as "SOMC Flash device", but no tool can connect to it (like FlashTool).
(I think then different PID is the reason)
Macs1209 said:
With battery, no.
Without battery, my laptop recognize as "SOMC Flash device", but no tool can connect to it (like FlashTool).
(I think then different PID is the reason)
Click to expand...
Click to collapse
it seems to me that you are an advanced person in playing with your mobile, this kind of issues is beyond of my knowledge but I was replying to your thread hopefully someone here can help, I'm fearing that you have messed up with your mobile
Well, you could try to flash it from Ubuntu (NOT inside Windows 10 !) via FlashTool,
under windows there are limitations with different device IDs that separate drivers would be needed (and if only "wrong" ID is detected under Linux it doesn't really matter, since it's detected anyway),
perhaps under Linux operating systems you have more luck
Thank you for idea, but not working.
Finally I found an old SETool3 box , and successfully flashed with it without battery
Somehow it can fixed it.
Macs1209 said:
Thank you for idea, but not working.
Finally I found an old SETool3 box , and successfully flashed with it without battery
Somehow it can fixed it.
Click to expand...
Click to collapse
I am facing a similar situation, can you help me by telling me what exactly did you do to solve the issue step by step?
Same Problem With Me PLZ HELP
Dear Bro Ive same problem with my Xperia e6683 Total Dead After Wrong Flash with Xperia Z3+ File... SO Plz help me how to fit step by step guide plz....
As on 20 Jan 2017
I've Flash Successfully It With Setool fusion Box Without Battery Use Test Pin Method. Now My My Phone Again Alive..
[email protected] said:
Dear Bro Ive same problem with my Xperia e6683 Total Dead After Wrong Flash with Xperia Z3+ File... SO Plz help me how to fit step by step guide plz....
As on 20 Jan 2017
I've Flash Successfully It With Setool fusion Box Without Battery Use Test Pin Method. Now My My Phone Again Alive..
Click to expand...
Click to collapse
Dear Bro Ive same problem with my Xperia x Total Dead After Wrong Flash
The phone is completely dead, cannot turn on, not vibrating on power button etc.
When I connect to my laptop, it says "unable to recognize USB device"
using test pin method it is recognized as "SOMC Flash device"
i have backup ta partition and ftf firmware of my xperia i can't find any tool to flash
can you guide me please
Flashtool Doesn't Recognise This Device. U can use Setool/ Setool Fusion Box to Repai
bma1973 said:
Dear Bro Ive same problem with my Xperia x Total Dead After Wrong Flash
The phone is completely dead, cannot turn on, not vibrating on power button etc.
When I connect to my laptop, it says "unable to recognize USB device"
using test pin method it is recognized as "SOMC Flash device"
i have backup ta partition and ftf firmware of my xperia i can't find any tool to flash
can you guide me please
Click to expand...
Click to collapse
Bro
In this Condition Flashtool Not Recognised Ur Device. There is only a best solution U Can Use SETOOL/SETOOL FUSION BOX To Repair/ Flash Ur Device.
[email protected] said:
Dear Bro Ive same problem with my Xperia e6683 Total Dead After Wrong Flash with Xperia Z3+ File... SO Plz help me how to fit step by step guide plz....
As on 20 Jan 2017
I've Flash Successfully It With Setool fusion Box Without Battery Use Test Pin Method. Now My My Phone Again Alive..
Click to expand...
Click to collapse
bma1973 said:
Dear Bro Ive same problem with my Xperia x Total Dead After Wrong Flash
The phone is completely dead, cannot turn on, not vibrating on power button etc.
When I connect to my laptop, it says "unable to recognize USB device"
using test pin method it is recognized as "SOMC Flash device"
i have backup ta partition and ftf firmware of my xperia i can't find any tool to flash
can you guide me please
Click to expand...
Click to collapse
wrong flash means wrong kernel!
you might be stuck on black screen when you frist switchon device! the device is running! but since its stuck on bootloops no interface is open!
press power and volume up button for 15+ seconds and let it JERK 3 times , this if force shutdown. the device should get connected now in flashmode