Hi All,
Got myself a new xperia Ray, and I want to flash the generic firmware as posted by DoomLord in the xperia mini forums. I've downloaded the last flashtool (version 0.3.0), but I cannot flash the generic firmware to my phone. The device is not supported. Only the X10 and the 17i are (Ray is 18i). Devices can be added to flashtool, but therefore the build properties file in flashtool needs to be altered; I do not know what parameters to put in that file so that it properly recognises my phone.
The reason I want to flash the generic firmware is because I want to get rid of those T-mobile logo's at startup and some apps that are for t-mobile simcards only. And to root the device eventually.
Any thoughts how to flash the generic firmware?
Seems like I got a step further; when pluggin in the phone when asked, I plug in the phone in flashmode (volume down and plug in usb), I get an error related to drivers of the phone. I have already installed pc companion and drivers for the phone were also installed. System is xp sp3 btw.
Any thoughts again?
Thanks
Allright, i solved it. Additional drivers were needed to recognise the phone in flashtool. The phone is nice and clean now!
can share how u do it? I have already installed the ADB drivers to work with fastboot but it seems flashtools still cannot find my devices
I don't know```
You first have to install pc companion. Pc companion installs drivers for the ray. Make sure that u have successfully communicated with the phone through the program. Thats one.
When flashing with flashtool, the phone needs to enter flashmode. Here lies the problem. When the phone enters flashmode, additional drivers are needed which werent installed by pc companion. Yiu see something with SEMCUSB and windows asks you to point to the drivers. These drivers you have to install when unlocking the bootloader and can be found at sony ericsson bootloader site (link is somewhere at xda). I needed also another driver for the phone to install which i found at xda at a step for step bootloader unlock.
So first unlock the bootloader. Then flash the rom. I will look up some links when i get home
Hi
You can unlock the Ray's bootloader from this link.
Follow the instructions there.(I haven't tested it but so far that works for others)
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
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.
Hello,
I have Xperia Z3 D6603 with android 6.0.1 and wanted to root it, I've looked up the topic and found good guide on XDA.
I've just started to follow instructions in this guide http://forum.xda-developers.com/z3/general/guide-rootrecovery-how-to-root-install-t3017056.
So I used Flashtool and used FW linked in the guide. After succesful flash my phone got in some loop of errors and it's restarting continuously - the video below shows the process.
https://youtu.be/_Pi58MvK4_o
I tried to flash it with other FW (second linked in the guide), it looked like success but phone behaves the same - same errors.
Any suggestions what should I do to fix it? Or which tool use to try? Is there sth I'm doing wrong with the Flashtool, some special option I should use?
Thanks for every help!
Before anything else goes wrong you should try Sony PC Companion.
Get the phone back to a stable state before you root. You might end up sending it under warranty if you still have it.
Use flashtool to flash the ftf for your country / wherever the phone is from. Then even if you still get the same behavior you can use PC Companion which will auto detect and download the correct firmware for the device and flash it. The only reason to flash the ftf for your country is so that PC Companion downloads this also. That way if you do take it for repairs you won't get asked why it's changed (they can check)
That guide works though so you probably did nothing wrong. Either a software error occurred along the way (try reinstalling all the flashtool drivers with signature verification turned off in windows) or you uncovered a hardware fault that Sony needs to fix.
Welcome to Xperia Rooting
Are you sure you selected the options to wipe data and cache in flash tool?
If you don't do this, you can often end in bootloop.
Thank you guys, I'm fresh in this topic so I got pretty confused when sth went wrong.
I've already used Xperia companion, it worked properly, now I'll make second attempt with downgrading and rooting.
Many thanks once again!
Hi XDA,
It's been a while since I've done any work on any phones, I've previously used roms on Galaxy S and SIII. But those are a while ago as you can see. I've got an Xperia XZ, the bootloader is currently unlocked. But I cannot, for the life of me, get any further despite following several guides and programs. So I'm at a loss.
At this exact moment, I have my XZ connected to my pc with the blue light on. CMD in ADB/Fastboot cannot detect the device. My understanding is I need to flash the kernal and recovery first, then I can consider flashing a custom rom.
Would anybody be able to assist me? I dropped this project a few months ago, so I'll need to check what rom I was going to use and update the img files I have.
Thanks
Installed fastboot abd on pc?
Yep, that's been installed. I do have an issue which I thought/think is driver related as the daemon doesn't always start, and doesn't detect the phone correctly either.
What OS is on your computer?
Windows 10, I also tried Linux Mint but didn't get much further.
Have you disable the drivers vetification?
Yep!
Can flashtool detect your device? Sorry for all the questions but got to start somewhere and have you tried changing USB ports and cables?
No, the questions are good. There will be something wrong that I can't find, so we need to work it out somehow.
Flashtool doesn't consistently detect the device. The computer does, flashtool doesn't. I have changed the cables with some success, but that hasn't helped me progress much further.
Hmm, have you install the drivers from Sony developer site? Also try it on another computer..i wonder if you have a bad connection port on your phone thus the reason I asked about another computer.. Try reinstalling fastboot and adb, drivers etc. with your anti-virus disable.. And does Sony companion work? USB debugging turned on?
Sounds silly but sometimes we forget, like redoing doing your phone from scratch and you can't delete some stuff and only to remember later that you forgot to install busybox or mount your system partition.. lol
Thanks Lilbrat,
I'll be doing a fresh install, hopefully this weekend. And will cover what you have mentioned and report back. Thanks!
since this is your first Xperia device, you must first familiarize yourself with the ENVIRONMENT and TOOLS in which SONY Xperias can be played with !
some basics I wrote for X, but applies for XZ also , please read as it will be helpful!
https://forum.xda-developers.com/showpost.php?p=72141176&postcount=7
now
since your boot is already unlocked so I can safely assume that you don't have TA.img file at all!
this leaves you with only two solutions
1. install 3rd part ROMS
2. flash sony STOCKROM and flash MODDED kernel (most of us do this)
your XZ has project name by SONY called KAGURA, your device on xperifirm is recognized by this name, dual/single you have to specify
from flashtool, xperifirm, download latest firmware 41.3.A.2.157 under KAGURA, close xperifirm and FLASHTOOL will start creating FTF file AUTOMATICALLY, click OK to any script question. and let it create ftf for u
flash it on your XZ,
send me kernel for 41.3.A.2.157, i will patch it for u! (patching guide is given in this forum but at this point i think it will be too much for you, so i will fix the kernel for u)
KAGURA twrp can be found at https://dl.twrp.me/kagura/ ( unlike SAMSUNGS, sony Xperias don't have inbuilt RECOVERY )
flashing recovery is MUST!
when device is switched off, connecting USB CABLE to PC and MObile while
1. HOLDING VOLUME UP KEY (blue LED) is FASTBOOT MODE (used mainly for sending twrp and kernels )
2. HODLING VOLUME down KEY (GREEN LED) is FLASHMODE (used mainly to FLASH stock roms using FLASHTOOL
you must install
1. Xperia Companion
2. flashtool ( www.flashtool.net) (after installing goto C:\flasthool\Drivers folder and install the driver.exe select COMMON Fastboot / flashmode drivers + z5/z4/z3 family of all drivers (there is no XZ , as Z5p drivers supports XZ)
3. install minimal adb and fastboot 1.4x from XDA (google it)
4. using these TOOLS you can
a-flash firmwere
b flash recovery
c flash modded kernel
d boot in to recovery (twrp) and flash MAGISK 16.x .zip from twrp + drm patch files! ( i will give you later with modded kernel)
e reboot and your device will wakeup ROOTED having DRM FIX! ---- switch off the SOFTWARE updater using any ROOT APP FREEZE app from playstore!
Currently working through a reinstall of flashtool etc, I can detect the phone using the Sony Companion tool, so thats positive. I haven't seen any notification that drivers have installed, but I do have the XZ drivers unzipped here.
Edit1: It doesn't detect or anything when the blue or green lights are on phone either. Not sure about them at this point.
Edit2: Just going through your guide as well Yasu, I cannot locate "sony Xperia X motherboard drivers (sa0107)" or anything similar to my device. Just throwing that out there. Installing the two common results in Sony Mobile Communications (ggsomc( USB (11/10/14 3.1.0.0) installing, but Google. Inc (WinUSB) AndroidUsbDeviceClass (12/06/10 4.0.0...) failing.
Will continue. Derp, just noticed I have a completely different flash tool. Sony Mobile Flaster by Androxyde, v0.9.25.0 but atleast it detects the connected device more than previously.
21/004/2018 13:04:44 - INFO - List of connected devices (Device Id) :
21/004/2018 13:04:44 - INFO - - USB\VID_0FCE&PID_0DDE\CB512CK84Q Driver installed : false
21/004/2018 13:04:44 - INFO - List of ADB devices :
21/004/2018 13:04:48 - INFO - - none
21/004/2018 13:04:48 - INFO - List of fastboot devices :
21/004/2018 13:04:50 - INFO - - none
Edit 3: Right, forgot to disable Win10's driver signature. Fixed that part again.
Downloaded the wrong firmware, so just working on that again (41.3.A.2.157 / R1E).
I was planning to flash Rudy's AOSP Oreo, but I'll have to go back and see as I chose that several months back.
Edit1: Completed flash. Phone is now 41.3.A.2.157, kernal 3.18.66. Android 8.0.0, bootloader unlocked. Rooted says no. This is certainly a lot more difficult than I remember!
Edit2: Recovery flash completes when command is ran, but adb does not register the device being listed, fastboot does. So I've hit the stump again with being unable to successfully flash twrp-3.2.2-0-kagura.img as recovery.img
Edit3: Last one for today. I can't open recovery from my phone, but can force it with fastboot boot recovery.img which has worked. However, it has loaded to a Mount - Decrypt Data screen and wants a password. I'm not aware of a password being required, and if I recall the device is encrypted. Ouch, should have seen this coming.
AVeers said:
Downloaded the wrong firmware, so just working on that again (41.3.A.2.157 / R1E).
I was planning to flash Rudy's AOSP Oreo, but I'll have to go back and see as I chose that several months back.
Edit1: Completed flash. Phone is now 41.3.A.2.157, kernal 3.18.66. Android 8.0.0, bootloader unlocked. Rooted says no. This is certainly a lot more difficult than I remember!
Edit2: Recovery flash completes when command is ran, but adb does not register the device being listed, fastboot does. So I've hit the stump again with being unable to successfully flash twrp-3.2.2-0-kagura.img as recovery.img
Edit3: Last one for today. I can't open recovery from my phone, but can force it with fastboot boot recovery.img which has worked. However, it has loaded to a Mount - Decrypt Data screen and wants a password. I'm not aware of a password being required, and if I recall the device is encrypted. Ouch, should have seen this coming.
Click to expand...
Click to collapse
1. as i mentioned " (after installing goto C:\flasthool\Drivers folder and install the driver.exe select COMMON Fastboot / flashmode drivers + z5/z4/z3 family of all drivers (there is no XZ , as Z5p drivers supports XZ) "
2. once these drivers are installed, you will get SOMC notification when very first time you connect your XZ in any MODE (volume up / and /or / volume down)
3. while flashing firmware, if you didnt tick WIPE areas, you will get encryption error , you must perform CLEAN FLASHING
4. before booting in to twrp, you must flash MODIFIED KERNEL - you can take modded kernel from my post in this forum
5, boot into twrp, flash drm fix files, flash magisk and wipe delvik cache/ cache and Reboot!
Yep, I see what you mean now. I missed the options on the flash screen, I thought it was odd that the time it took didn't match anything close to the times you described.
That didn't end well, clean flash, flashed kernel, TWRP booted correctly this time from the phone. Except phone now won't boot past the Sony logo.
I was also comparing your instructions against korom42's, and another third party. Which naturally are all similar and straight forward, still didn't help.
AVeers said:
That didn't end well, clean flash, flashed kernel, TWRP booted correctly this time from the phone. Except phone now won't boot past the Sony logo.
I was also comparing your instructions against korom42's, and another third party. Which naturally are all similar and straight forward, still didn't help.
Click to expand...
Click to collapse
did you flash the modded kernel?
if you simply flash magisk on original kernel!
you will be stuck on SONY LOGO
OK, I still following this with some interest, as a bit of clarification seems to be needed.. Now granted for some reason Flashtool doesn't have the XZ drivers even the newest version but there are mb drivers on Sony Developer site.. https://developer.sony.com/develop/drivers/ . (see pic)
@AVeers, more computer questions reason being you said Flashtool is seeing your phone a bit better, which leads me to believe you're still having driver issues.. Are you on a laptop or a desktop? If it's a desktop have you tried plugging your USB into the rear panel, straight into the mb also have you tried disabling your anti-virus when installing your drivers? Oh, and where are you located as your firmware is for the middle east, if I remember correctly..
Hi Mate,
I won't be able to work on this further until the weekend. But I do have those drivers from Sony here. And have been using firmware as per Australia (generic). Which is correct for my location.
The phone is plugged into the mobo via rear panel, and this is a desktop running Win10. I'm in test mode to eliminate the driver signing issue. I have not disabled the anti-virus, but I haven't had issues before.
When I run the flash for the firmware, boot.img or twrp.img, it takes seconds to complete, generally less.