Related
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
So, i havent been modding Android phones in a long time and when I wanted to flash MM on my Z5, i forgot that i dont have the Z5 drivers. Now, based on what i know, i did have SONY PC COMPANION installed prior to soft bricking my device, so i would assume the drivers are installed. My current situation is as follows:
-Device wont turn on, switches between RED/GREEN led with error message of "update failed, please connect to PC etc..."
-Sony pc companion doesnt seem to recognize the phone as i cant repair it
-Cannot flash FTF through as it keeps failing to flash at different points, do not know if not having the Z5 drivers play a factor here. I got the drivers from there but i do not know what to do with it as it is not .exe file, i also have the latest flashtool installed.
-I backed up my files prior to this, so i am willing to wipe everything.
Thank you, i would appreciate if i can get some assistant on this. Stupid me for making this mistake in the first place.
Regards,
Litoni
Use PC Companion repair option (marked with a red box on my screenshot).
LitoNi said:
So, i havent been modding Android phones in a long time and when I wanted to flash MM on my Z5, i forgot that i dont have the Z5 drivers. Now, based on what i know, i did have SONY PC COMPANION installed prior to soft bricking my device, so i would assume the drivers are installed. My current situation is as follows:
-Device wont turn on, switches between RED/GREEN led with error message of "update failed, please connect to PC etc..."
-Sony pc companion doesnt seem to recognize the phone as i cant repair it
-Cannot flash FTF through as it keeps failing to flash at different points, do not know if not having the Z5 drivers play a factor here. I got the drivers from there but i do not know what to do with it as it is not .exe file, i also have the latest flashtool installed.
-I backed up my files prior to this, so i am willing to wipe everything.
Thank you, i would appreciate if i can get some assistant on this. Stupid me for making this mistake in the first place.
Regards,
Litoni
Click to expand...
Click to collapse
What Windows version ?
Follow
# STEP 1 - GENERAL GUIDE
INSTALL / CHECK DRIVERS
of
http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
and (re-)boot into (newer) Windows by disabling the driver signature verification.
Log in with administrator rights,
Extract the zip-file,
there you have inf files
https://en.wikipedia.org/wiki/INF_file
https://msdn.microsoft.com/en-us/library/windows/hardware/ff549520(v=vs.85).aspx
right-click on those and choose install - so that the device drivers are installed.
Reboot (of Windows) shouldn't be necessary.
Entering Fastboot mode should still be possible, check whether it's being recognized now (via Minimal ADB and Fastboot).
Remember: in case the device goes crazy because it's not being detected upon connection - you can still turn it off via
Emergency off
(listed under "#FASTBOOT / FLASHMODE / RECOVERY / etc.")
Install the drivers that are inside flashtool.
Mr_Bartek said:
Use PC Companion repair option (marked with a red box on my screenshot).
Click to expand...
Click to collapse
As mentioned, SPCC doesn't recognize my phone. It somewhat does but doesn't give me the option to repair. There are these other screens which i think are prior to the repair page (hopefully) but i was stuck at the page when it asks me to remove the battery or skip if built in. It asks me to press ok to skip but hitting the ok button didn't do anything.
zacharias.maladroit said:
What Windows version ?
Follow
# STEP 1 - GENERAL GUIDE
INSTALL / CHECK DRIVERS
of
http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
and (re-)boot into (newer) Windows by disabling the driver signature verification.
Log in with administrator rights,
Extract the zip-file,
there you have inf files
https://en.wikipedia.org/wiki/INF_file
https://msdn.microsoft.com/en-us/library/windows/hardware/ff549520(v=vs.85).aspx
right-click on those and choose install - so that the device drivers are installed.
Reboot (of Windows) shouldn't be necessary.
Entering Fastboot mode should still be possible, check whether it's being recognized now (via Minimal ADB and Fastboot).
Remember: in case the device goes crazy because it's not being detected upon connection - you can still turn it off via
Emergency off
(listed under "#FASTBOOT / FLASHMODE / RECOVERY / etc.")
Click to expand...
Click to collapse
Thanks my desktop is running windows 10 and i know theres so many issues with it.
gm007 said:
Install the drivers that are inside flashtool.
Click to expand...
Click to collapse
The drivers from flashtool does not include any xperia Z5 series.
Thank you guys for the quick responses, I managed to reflash the .200 through flashtool without any hiccups. which is weird that it didn't work for .163 earlier. I didn't wipe anything, so after flashing .200 i updated the SDK stuff from Google SDK.exe which i think it solved some, from there I flashed .163 (MM) again and it worked. Kept all data intact, even my encrypted Class 10 SD card worked without any issues. So far so good, haven't really encountered any errors, fingers crossed :fingers-crossed: once again thank you for the quick responses.
Hi Friends, is the title says I have a problem getting into the custom rom think on my old z3 6603 .291? 6.0.1 i think android...
now whats my problem?
I am despered already! spent almost 2 full days trying around without luck.
little off topic:
I did custom roms a few years ago and it worked pretty well with a step by step tutorial.
now i started to read around and try to update the Z3 to android 7Nougat or at least GoogleStylev1 because the standard/stock rom is sooo full with s**t i never really used and pure clean 5.1 from my mothers 60€ Chinamobile is fast and has all i need...
the z3 is much slower than it could i belive and the batterylife should be longer(new replaced battery >3000mAh, its almost like my new s7edge, wich i have to recharge every 3 days, the sony almost every night...)
back to topic:
i read so many different ways to do the update and everything is super complicated and at some point it doesn´t work out like in the tutorials. stupiiiid..
for example: hold power+vol down to enter recoverymode utility, i tried it so many times but my z3 is booting as usual. somone mentioned to let power button go as soon the led blinks or the vibration appers. sad: my screen is replaced and as i replaced it by myself i disconnected the vibration and glued the backplate on ... sh**
maybe someone can tell me how many secods to wait until let the power button go or other ways of erasing the system before i continue with linage install.
what i have:
win7 pc ( lack of updates and stuff but i already got the insane big android studio and somehow installed the usb driveds as it seems but thats all i still have missing drivers as i connect the phone trough flash-tool for example. xperia companion detects the phone most of the time..
so i went to my mac mini os x..
similar but little better: i can detect the device when i connect flashtool it says device connected in flash mode, good!?
i downloaded:
flashtool-driver
android tools
flashtool 0.92.1mac
lineage14.1 xkeita
twrp 3.1.1 xkierta
sr1 super su v2.82
D6603 23.5.A.0.291_kernel.zip
D6603 23.5.A.0.575_kernel.zip
root.rar
I guess i first have to get a little XDA developer university degree to update a sony mobile device hummmm???
sorry i am stressed out, please could somebody take a newb like me by hand and guide trough this piece of complicated labyrinth?
I want to give this phone to my gf for the next few years and i whink a clean slim and stable system would be much more pleasure in future than what i have now.
its a nice phone...
thanks
forgot to mention, usb debugging and developer mode are activated on the phone.. when i type in the *#7384whatever code it says: bootload activation: yes does it mean its ready to be activated or is it already active?
please its so many steps and tutorials i tried i am comletely confused
HI, glad to hear you're trying to install my rom
Since you're already on 6.0.1 all you need to do is unlock your bootloader before flashing the custom rom. To do so please refer to this page which will provide all the help you need for this step https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ (before doing this, make a backup of your internal storage because it will be wiped after unlocking the bootloader)
After unlocking your bootloader, let's proceed to installing the recovery. To do this unpack the contents from the TWRP zip and copy recovery.img to the folder where you have fastboot.exe and run this command from Windows command line
Code:
fastboot flash FOTAKernel recovery.img
Now for our final step, boot into recovery by using the power on+volume down combo, connect your phone to the computer and copy the LineageOS zip to your internal storage. Before flashing the rom remember to wipe system/data/cache/dalvik. And you're all good to go.
thanks for replying xkeita,
i did this step until the point where i got a code for bootloader.
after this they tell me to go to connect my phone to the pc and to do what?
A. Install the Android SDK and the device drivers (what drivers? i have mac) i have android studio on my mac, but i have no clue how it works.
b. If you’re running OSX or Linux, you are not required to install any additional drivers. (check!)
2. On your device, turn on USB debugging by going to Settings > Developer options and click to enable USB debugging. (check!)
B. Connect to Fastboot
1. Turn off your Xperia™ Z3.
2. Connect a USB-cable to your computer.
3. On your Xperia™ Z3, press the Volume up button at the same time as you connect the other end of the USB-cable.
(check!) i did it...
4. When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder.
5. Enter the following command: fastboot devices
here i am struggeling... how to do this on mac? i have no directories and no idea how to proceed, please help me!
xdan00b#1 said:
thanks for replying xkeita,
i did this step until the point where i got a code for bootloader.
after this they tell me to go to connect my phone to the pc and to do what?
A. Install the Android SDK and the device drivers (what drivers? i have mac) i have android studio on my mac, but i have no clue how it works.
b. If you’re running OSX or Linux, you are not required to install any additional drivers. (check!)
2. On your device, turn on USB debugging by going to Settings > Developer options and click to enable USB debugging. (check!)
B. Connect to Fastboot
1. Turn off your Xperia™ Z3.
2. Connect a USB-cable to your computer.
3. On your Xperia™ Z3, press the Volume up button at the same time as you connect the other end of the USB-cable.
(check!) i did it...
4. When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder.
5. Enter the following command: fastboot devices
here i am struggeling... how to do this on mac? i have no directories and no idea how to proceed, please help me!
Click to expand...
Click to collapse
Extract this zip https://forum.xda-developers.com/attachment.php?attachmentid=1396782&d=1350078941 and open terminal in the directory where you have unpacked the zip, then you can run the command directly
Mac-mini:android "XXXXX"$ fastboot devices
-bash: fastboot: command not found
should any software run in the background like xperiacompanion or flash-tool? i managed to open the terminal in the android directory but no luck...
this z3 is a tough piece...
thanks again for your effort to help me out, maybe you or somebody else can help me trough this. I have the feeling that we can crack this device together, it cant be that compliceted, can it?
nobody has Ideas as what could be going wrong in my case?
i was thinking XdaDevelopers is a big international site, and z3 is a mainstream phone, why the heck is there nobody to guide me trough this
remember how it was when you did your first Rom experiances, difficult, many different new steps, after foing it couple of times its getting easier, like everything in life.
please somebody sacrifice a litte time on me and my priject, it wont be my last for sure but i need a little help in the beginning, xperia z3 seems to be much more complicated than my old (p880LG 4xhd or xpezia z from 2012)
xkeita said:
Extract this zip https://forum.xda-developers.com/attachment.php?attachmentid=1396782&d=1350078941 and open terminal in the directory where you have unpacked the zip, then you can run the command directly
Click to expand...
Click to collapse
do i have to extract on my mac, or onto the phone? i extracted into my desktop and it didnt work ether in desktop/android/
i am going to try out to extract onto the cellphones memory and to run fastboot line from there
should i record a video how i do all my steps and somebody can tell me what im doing wrong?
eeehh.. official sony webpage is so flapsy and unprecise when it comes to bootloader...
bump
did i say something wrong or..?
...
You should use windows instead of mac it's better for unlocking your bootloader then follow the sony unlock bootloader website exactly don't skip any steps
hello omar, and thanks for reply!
my problem is to unlock the bootlocker on this phone.. i cant get my phone bpptloader unlocked and i dont know why.. its the staps on this website that dont work. i will take time on weekend maybe and try again..
piece of crap phone , replaced screed and back and my girlfriend drops it once and everything is broken again many years ago sony was better. they should make walkmans again.. casette walkmans
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.