I'm not sure if this is where I need to post this but I need some help with my XA2. I used sonys tool Emma to flash stock firmware to my xa2 and now I am in a boot loop. The device will not show up in Fastboot mode (it did before flash). I tried to update the driver of the device in windows and it now gives me error 10. I then loaded up the sony mobile flasher by androxyde and it tells me after USB debugging is off and it was on before. Also when I boot to the bootloader the top led is now green and not blue. If someone on here has any advice I would be very grateful.
akaacp said:
I'm not sure if this is where I need to post this but I need some help with my XA2. I used sonys tool Emma to flash stock firmware to my xa2 and now I am in a boot loop. The device will not show up in Fastboot mode (it did before flash). I tried to update the driver of the device in windows and it now gives me error 10. I then loaded up the sony mobile flasher by androxyde and it tells me after USB debugging is off and it was on before. Also when I boot to the bootloader the top led is now green and not blue. If someone on here has any advice I would be very grateful.
Click to expand...
Click to collapse
look here:
https://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614
Related
Having the same problem as this
but no solution was posted.
Using the latest flashtool and installed the gordons gate drivers.
Put Xperia Play in flahs mode, green light.
Have tried arc and x10 since play not in list.
click on flash
picked the relock bootloader file
comes up root access allowed
hangs on 'preparing files for flashing'
phone then comes out of flash mode on its own and powers off??
please help?
Hello friends, i have a problem with an old Sony LT18i from a cousin, he brought it to me because he has the China Mobile variant with no GApps and android version was 2.3.4, i thought it might be solved with a simple flash via FLashtool, but when i've completed the downloading of the ftf file and went to flashtool to flash it, when the flashtool ask me to put it in flashmode pressing the back button and connecting to usb the phone led only blinks of 0.5 sec and then boots into normal mode.
Tried the same with fastboot and then i got the same blink for 0.5s with no detection at all. That surprised me as well i've have flashed succesfully other Xperia devices with no problems of led blinks at all. Now my problem is that later i tried to root the phone and installing CWM to flash another ROM or GApps package, and when i finished to install the recovery now the phone is bootlooping and never gets to boot normally.
I've tried with 4SE dongle to flash it via Testpoint and it doesn't work as the phone manufacture model is 12W13 (new security) which the dongle doesn't support, tried with S1 Tool with version 28II215 and 080714 and i only get PHONE NOT SUPPORTED IN THIS MODE when i try to flash and when trying to unlock the bootloader it gives me NOT SUPPORTED MCU REVISION.
The phone was working well until the CWM installation except for the flashmode and fastboot mode, now i really need to flash it and i can't find a way to do it, i also have RIFF JTAG and Z3X Easy JTAG box but no JTAG available for this model except for Medusa Box which only supports phones with manufacture date less than 12W10, i was wondering if there´s a way to access via QHUSB_DLOAD mode doing the testpoint to manually flash partitions to device or something like that. If you might have a workaround or a solution to at least let the phone in the way it was it will help me a lot. Thanks in advance, sorry if my english isn't so great.
Short blink usually means bad USB cable (at least it did for me). Simply try using another cable.
Thats happen when i unlocked my bootloader with Sony method.
When i try run flashtool ftf Flash.
My PC with Windows XP SP3. Give me Blue Screen of death. Same is when i try Flash cwm recovery from fastboot.
How can i fix this?
I dont have a Access to other PC with other Windows. 7 or newest.
Now i can only charge my phone.
This picture show an error which appear when i connect my Xperia M when flashtool told me.
I reinstalled Windows XP. And this issue is still here.
I dont know what to do now
Anyone please help me. Or i smash this phone on floor
PC detect Xperia M in fastboot and flashmode
Solved. I flashed stock Android with flashtool. On Windows 10
My Mobile of Xperia XA1 Died while trying to downgrade firmware via Xperia Flashtool.
it shows Red light only while usb connected or being charged. (Hard Bricked as i know).
Mobile is recognized as USB Serial Device in Device manager.
i Read somewhere that if i can get a SP Flash tool compatible Firmware Image and Scatter file, i can try to reflash.
i tried to find it over internet but no luck with Firmware or Rom and Scatter file.
While these many threads in XDA Community i hope that someone can make it for me if possible and i can try that.
Any Help or suggestion is welcome.
(Nearby Sony Service center says they don't do this mobile anymore and i will have to go to a city far far away for next center)
Phone is out of warranty. Bootloader was untempered (still locked i suppose) , not rooted , not customized, no custom recovery.
Phone's camera stopped working and even factory reset didn't helped so was trying to flash the factory stock rom. and it didn't go well.
Tried: Xperia Flash tool, Xperia Companion ( Can't boot to Fastboot via Vol down)
i Don't have any Box to proceed with.
Model: Sony Xperia XA1 G3116 (India)
Jarnail362 said:
My Mobile of Xperia XA1 Died while trying to downgrade firmware via Xperia Flashtool.
it shows Red light only while usb connected or being charged. (Hard Bricked as i know).
Mobile is recognized as USB Serial Device in Device manager.
i Read somewhere that if i can get a SP Flash tool compatible Firmware Image and Scatter file, i can try to reflash.
i tried to find it over internet but no luck with Firmware or Rom and Scatter file.
While these many threads in XDA Community i hope that someone can make it for me if possible and i can try that.
Any Help or suggestion is welcome.
(Nearby Sony Service center says they don't do this mobile anymore and i will have to go to a city far far away for next center)
Phone is out of warranty. Bootloader was untempered (still locked i suppose) , not rooted , not customized, no custom recovery.
Phone's camera stopped working and even factory reset didn't helped so was trying to flash the factory stock rom. and it didn't go well.
Tried: Xperia Flash tool, Xperia Companion ( Can't boot to Fastboot via Vol down)
i Don't have any Box to proceed with.
Model: Sony Xperia XA1 G3116 (India)[/QUOTE
Click to expand...
Click to collapse
i thought there was an answer..
Before u connect usb press volume down and power button at a same time If it showed green button then u good to go with Xperia champion
If u can't under stand contact me on instagram
( ti.p.u) its my instagram name or whatsapp me 7620353604
You guys are beautiful!
I had an old Xperia S stuck on the Sony logo and was able to recover it. So I decided to document here what worked for me. Maybe it can help the next one which may have a similar problem.
What finally worked for me was begin by uninstalling everything: PC Companion / Flashtool / sa0103 drivers I installed via Device Manager / etc...
- Then I installed Flashtool 0.9.18.6.
- After that I disabled the driver enforcement via the Advanced Startup method. Command line method I did before did not work.
- Installed the drivers from Flashtool. I checked Flashmode / Fastboot and all Xperia S I could find
- Then I was able to flash the 6.2.B.1.96 rom I found somewhere. I tried a 6.1.A.2.55 that I downloaded but that didn't work
- After ~20 minutes it was flashed.
I don't know if the ADB driver I downloaded from Android developer website made a difference or not. What I know it made a difference was using the old Flashtool because I did this exact process with the latest version and I didn't work.
I'm attaching my last log from Flashtool so maybe you guys can compare to yours.
That's it! I spent around 3 days reading not only the Xperia S subsection here but searching for all the errors on other device's subsections.
Hope it can help someone.
Thanks a lot guys