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.
Hey,
I've got a serious problem with my Xperia U and I'm after twelve hours of trying to gifure it out, so I think I've passed more obvious solutions.
OK, so... I tried to unlock bootload (which I did) and root my phone via flashtool using some .tft file from xda. I think I've checked if this system is for mu phone and it was certainly for my soft version (6.1.1.B.10). So, I load this .tft file into flashtool, connect my phone as it tells me, the file uploads just fine, I plug out my phone, try to boot it and it doesn't respont. Since then I've tried to upload few .tft files (.10, .100, .54), to some of them my phone would respond at all (when booted it only vibrated), to some of them the phone would boot, but the touchscreen wouldn't work. In this case I'd have "POWER OFF" and "USE PHONE" on my screen and my side buttons would work (I could block my phone and take photos for example).
So, I've tried:
- flashing several times
- using official software from Sony (PC Companion and EMMA)
- using cmd to fastboot recovery.img - I failed to find recovery.img though.
Any suggestions?
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
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.