My C6903 in LP 5.1.1 doesn't take photos (or videos) when the app tries to focus. Without focus enabled (using other app) it goes perfectly. I've tried with 14.6.A.1.236 Customized BAL, 15.5.A.0.242 Movistar AR and a few more, all obtained from XperiFirm.
I tried pushing that "4k and timeshift" .zip which I read could fix the camera but no luck.
Curious thing is that Rooting Status shows "Unknown", I don't know if this could be related or not. I bought the phone on eBay (used) and I couldn't tell you if it's been unlocked or not.
But I know that everything can't be messed up because in JB 4.3 (14.2.A.1.136 Generic BAL from XperiFirm) camera works well, and Rooting Status shows "Bootloader Unlock Allowed: Yes"; And in KK 4.4 (updated via OTA from mentioned JB firmware) camera stops working in the same way but Rooting Status keeps on "Bootloader Unlock Allowed: Yes".
What could I try? I think I've already read everything related to the Rooting Status Unknown and Camera freeze problems in this forum and still have no clue (even in other Xperias forums too).
Thanks by the way
PS: Yet I didn't tried unlocking bootloader just because it may bring more problems, but if needed I would do it in a blink
matidx said:
PS: Yes I didn't tried unlocking bootloader just because it may bring more problems, but if needed I would do it in a blink
Click to expand...
Click to collapse
This is definitely a bad way to troubleshoot your problem, but go ahead and make yourself a backup of your phone's TA partition and unlock the bootloader of your phone. As long as you made a backup of the partition, the DRM keys will stay intact when you re-lock the bootloader; thus, you won't lose any exclusive Sony features upon restore. Make sure you have the proper adb and fastboot drivers before you begin.
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598
Unlock bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Flash any custom ROM (don't flash the Marshmallow ROMs) found in either the Android Development or Original Development page for Z1. You can also flash a modified Sony ROM in the Android Development section that has mostly all of the features in Sony's stock ROM plus some additional ones picked from CM/AOSP ROMs. Either way, if your problem is fixed, then it's a problem with the FTFs you flashed. If not, restore your TA/DRM keys (it'll re-lock your phone's bootloader) and report back.
Good luck fixing your problem!
kentexcitebot said:
This is definitely a bad way to troubleshoot your problem, but go ahead and make yourself a backup of your phone's TA partition and unlock the bootloader of your phone. As long as you made a backup of the partition, the DRM keys will stay intact when you re-lock the bootloader; thus, you won't lose any exclusive Sony features upon restore. Make sure you have the proper adb and fastboot drivers before you begin.
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598
Unlock bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Flash any custom ROM (don't flash the Marshmallow ROMs) found in either the Android Development or Original Development page for Z1. You can also flash a modified Sony ROM in the Android Development section that has mostly all of the features in Sony's stock ROM plus some additional ones picked from CM/AOSP ROMs. Either way, if your problem is fixed, then it's a problem with the FTFs you flashed. If not, restore your TA/DRM keys (it'll re-lock your phone's bootloader) and report back.
Good luck fixing your problem!
Click to expand...
Click to collapse
Tried that but it looks like the volume up button isn't recognized when booting or something like that. What really matters is I can't enter to fastboot mode, tried everything. Any ideas?
matidx said:
Tried that but it looks like the volume up button isn't recognized when booting or something like that. What really matters is I can't enter to fastboot mode, tried everything. Any ideas?
Click to expand...
Click to collapse
Install proper drivers for fastboot. Power the phone off completely, then while plugging your phone into the computer, hold the top volume button. You should be able to enter fastboot if fastboot drivers are properly set up.
kentexcitebot said:
Install proper drivers for fastboot. Power the phone off completely, then while plugging your phone into the computer, hold the top volume button. You should be able to enter fastboot if fastboot drivers are properly set up.
Click to expand...
Click to collapse
Is there a way to know if fastboot drivers are properly installed? I've checked and reinstalled them about 5 times, but I'll try again tomorrow just to be sure I'm not missing anything.
I don't know if there are different drivers but always installed the flashtool ones. By the way I'm running Win10 but also tried in Win7 and no luck.
matidx said:
Is there a way to know if fastboot drivers are properly installed? I've checked and reinstalled them about 5 times, but I'll try again tomorrow just to be sure I'm not missing anything.
Click to expand...
Click to collapse
If your computer can successfully detect the device and output it's serial number when you input through command prompt:
Code:
fastboot.exe devices
you'll know that fastboot is working and drivers are set up correctly. If you look at your device LED, the LED will be lit blue. Remember: you need to already have downloaded and installed the applications through the executabe in the adt folder to get the fastboot and adb applications.
matidx said:
I don't know if there are different drivers but always installed the flashtool ones. By the way I'm running Win10 but also tried in Win7 and no luck.
Click to expand...
Click to collapse
Go here to download the correct fastboot driver files: http://doomlord.xperia-files.com/download.php?dlid=Rmxhc2h0b29sLWRyaXZlcnMtMS4zLTIwMTQwMjA5
If your computer can successfully detect the device and output it's serial number when you input through command prompt:
Click to expand...
Click to collapse
Right, I know what that command line does, but that will work only when drivers are properly installed AND phone is detected. What I believe is that there are some kind of problems with the phone to not go into fastboot mode, so it wont be detected at fastboot, always in flashmode.
Is there a way to know if drivers are properly installed even if the phone isn't recognized?
Remember: you need to already have downloaded and installed the applications through the executabe in the adt folder to get the fastboot and adb applications.
Click to expand...
Click to collapse
What is the adt folder? You mean adb or the obsolete Android Development Tools (now Android Studio)?
By the way, I'm also having this issue... http://forum.xda-developers.com/xperia-z1/help/baseband-lost-reboot-t3352858
Maybe it could be related someway (like motherboard going bad or something else).
matidx said:
What is the adt folder? You mean adb or the obsolete Android Development Tools (now Android Studio)?
Click to expand...
Click to collapse
My apologies, I should've been more clear and double-checked the information!
They apparently renamed the file. I was referring "adt" to my folder that's dated all the way back to 2013, so....whoops!
You can grab the download from here: http://developer.android.com/sdk/index.html. If you don't want the entire bundle, search for "Get just the command line tools" and click on the links for your platform.
matidx said:
Right, I know what that command line does, but that will work only when drivers are properly installed AND phone is detected. What I believe is that there are some kind of problems with the phone to not go into fastboot mode, so it wont be detected at fastboot, always in flashmode.
Is there a way to know if drivers are properly installed even if the phone isn't recognized?
Click to expand...
Click to collapse
Just download the S1 driver file through the link I provided earlier, install, reboot computer, then run the same command as I told you from my previous post: if it outputs the serial number of your phone, then you're fine; but if it doesn't, post back. As long as your computer can establish a basic connection to your Z1 (PC can see it in flash mode, could access it somehow), your phone is capable of fastboot.
kentexcitebot said:
My apologies, I should've been more clear and double-checked the information!
They apparently renamed the file. I was referring "adt" to my folder that's dated all the way back to 2013, so....whoops!
You can grab the download from here: http://developer.android.com/sdk/index.html. If you don't want the entire bundle, search for "Get just the command line tools" and click on the links for your platform.
Just download the S1 driver file through the link I provided earlier, install, reboot computer, then run the same command as I told you from my previous post: if it outputs the serial number of your phone, then you're fine; but if it doesn't, post back. As long as your computer can establish a basic connection to your Z1 (PC can see it in flash mode, could access it somehow), your phone is capable of fastboot.
Click to expand...
Click to collapse
I think I've followed everything right but to be clear I'm gonna explain what I've done so far:
- Installed Android Studio (I believe it comes with those "just the command line tools").
- Installed Flashtool's driver (same as the DoomLord link you provided, even a later update than that link), also did that thing about "Disable Driver Signature Enforcement" because I'm on Win10 64bit.
- Always checked by cmd command line "fastboot.exe devices", I've never get any error (so cmd always detected it as a valid command line) or any other cmd print.
- I have a TA backup but after I made it tried to unlock bootloader but no luck. Anyway, just restored the backup and only sign I got is "Upgrading NFC firmware" or something like that after booting, the "NFC upgrade" went well but still no fastboot access.
---
- When I plug the usb + press volume up button to try get fastboot mode, phone's led goes red then green then it goes off and in flashtool I get flashmode with no led on.
---
By the way, I have an Xperia SP and already unlocked bootloader so I pretty know how it should go. Having no problem with it accessing fastboot or even locking or unlocking on the XSP.
Because of this and baseband problem, I can't stop thinking motherboard is messed up.. But anyway, whatever you think I could try just let me know.
Related
I read through many threads and have followed the official Sony bootloader unlocking instructions. I have requested and received the unlock code from Sony via email. I have downloaded the inf file and placed it in the correct folder in Android SDK (which I also updated). But I am cannot access fastboot mode, I hold down Vol + and plug in the USB cable but the device shows a red led and goes into charging mode. Also the PC never prompts me to install fastboot driver it simply loads the SP as Sony mass storage device (in device manager).
I have read that some people seem to think that the SIM lock affects the ability to access fastboot but this SP is SIM unlocked. Sony's official guide to unlocking the bootloader says I need to access fastboot mode to enter the unlock code but how can I unlock the bootloader if I can't get into fastboot mode?
hmmm... don't know really... i once entered fastboot mode by mistake, while trying to root stock rom. wasn't reading instructions and put device in a fsatboot mode instead of debugging... was on stock rom so don't know if custom rom would let me do that. should check myself... if anything i know it is possible to get me that blue light shining.
To enter fastboot mode in Xperia SP just power down the phone and hold down the volume up key while pluging your phone into your pc
If you need flashmode do the same thing but with the volume DOWN button held down.
I´ve got the same problem. I can´t enter in flashmode neither in fastboot mode. I´m on windows 8 32bits and I installed the .245 Deodexed ROM with a problem on root and without CWM. I don´t know what to do now, please help me.
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
jackaros said:
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
Click to expand...
Click to collapse
Thanks for trying to help, but I understand that flashmode and fastboot are accessed using the phone. Actually the phone needs a piece of software like flashtool to keep it in flashmode otherwise it drops into charging mode. I didn't mention my computer so I don't know where you got that from.
As I explained, I am unable to access fastboot with stock ROM (1.257) and a custom ROM (based on 2.245) so it can't be a ROM bug or the flashing process having gone wrong.
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Ze Tolas said:
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Click to expand...
Click to collapse
It may be a flashtool problem you are right because 2 incidents with different Roms that both use flashtool to flash those roms.....
its pretty much self explenatory.
skojevac said:
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Click to expand...
Click to collapse
Interesting. Ok, I've read up on the process. So I use the various stock .ftf files and flashtool with the phone in flash mode? Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. If I do it, I will nandroid backup first, of course, but I think I remember reading in one thread that someone managed to soft brick their XSP doing this very thing.
Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. [/QUOTE said:
that's why you need to complete rooting procedure. root stock 1.257 kernel, than back to stock 2.245 with root preserved, and before you would install CWM try to put device in a fastboot mode, this assuming you still have a UB.
Click to expand...
Click to collapse
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
SuicideFlasher said:
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
Click to expand...
Click to collapse
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
skojevac said:
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
Click to expand...
Click to collapse
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
gandalf_grey91 said:
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
Click to expand...
Click to collapse
I said before, it's new firmware (maybe RU) with a Windows Flashtool issue. Today i did flash kernel to my SP using Linux client.
Same issues
gandalf_grey91 said:
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
Click to expand...
Click to collapse
Hi, I have some similar issues. I've also been flashing some stuff and whenever I try to go to fastboot it just boots into CWM. Very annoying to say the least. The dark blue light goes on when i hold down volume up and for a short moment I see the fastboot driver installing on my computer. But before it completes it's already in CWM.
Not sure what to do from here on wards, maybe some advice on which kernel to flash? I am pretty sure the latest kernel I flashed is the .254 root kernel from doomlord.
Ps. I really would like to flash CM when it becomes available as nightly :angel:
Thanks in advance!
Fast boot mode for xperia ion hspa???
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
I had already installed cm10.1 jb for my xperia ion.
Now i tried to install cm11 kitkat for my xperia ion.
Every thing is gone good.
But now got stuck up with a problem.
fast boot mode is active only for 5 seconds while connecting my xperia ion to System with flash tool.
help me to do the need ful.
Guide me to download compatible drivers and flash tool for fast booting process.
If you have UNLOCKABLE bootloader, then you dont have a FASTBOOT mode on your phone. Its just pure luck. some phones dont have it... kind of a sony crap... I also happen to be one of those LUCKY ppl. no unlock, so stuck with Stock kernel forever.
When you connect your phone to Flashtools in FLASHMODE...
See for a string BOOTLOADER: NOT_ROOTABLE.... it means you belong in the lucky group...
If it says rootable, then you're doing something wrong.
Pardon me if i read something incorrect. i skimmed through all the posts before posting.
Hello All,
I have following issue and hope that - if possible - someone can help me. I also would like to mention that I am not an
Android expert but did read a lot of articles here in the forum to find out - or better - to get an idea how things are working.
My Z3C had a water damage. Now I only get fastboot mode. Display is broken and does not show anything. I installed Android-SDK
to get ADB and Fastboot. I installed also drivers.
When I connect the device while pushing the "volume down" button the device manager show me a somc flash device with the "volume up" button I see an Android ADB Interface device. However ADB is not working (no device found) only Fastboot does.
I flashed the "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" with Flashtool via fastboot in the hope that I can somehow access
to "sdcard" by blindly navigating to "mount storage" but nothing seem to work.
On my linux device I see that the usb device is recognized but that it is not an mtp device.
Before I continue to spent hours without really knowing what I am doing I thought that if there is a solution I would find it here.
So if there is any way to get access to my files / pics on the device I would be really glad if someone can let me know how or
at least bring me to the right direction.
Thanks a lot in advance!
Is your bootloader unlocked?
clouds5 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Thanks for your reply clouds5.
I followed the process to unlock the bootloader (got code from sony side and unlocked via fastboot with
"fastboot.exe -i 0x0fce oem unlock 0xKEY").
In Flashtool, when I click on the "BLU" Icon I get a window with with my IMEI and my Unlock Code and a
Relock Button. So I assume that the bootloader is unlocked.
If there is another way to verify please let me know and I will do.
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
evildog1 said:
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
Click to expand...
Click to collapse
I flashed "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" from doomlord.xperia-files.com/download.php?dlid=WjNjX0Rvb01Mb1JEX0FkdlN0a0tlcm5lbF92MDFfRlctMTA1 with
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
in the hope that it is possible but after rebooting it immediately goes into fastboot again. As I do not have
a screen I can not see anything - so I can not really confirm if it works or not - and in windows I do not see
anything either..
Galbasib said:
I flashed "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" from doomlord.xperia-files.com/download.php?dlid=WjNjX0Rvb01Mb1JEX0FkdlN0a0tlcm5lbF92MDFfRlctMTA1 with
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
in the hope that it is possible but after rebooting it immediately goes into fastboot again. As I do not have
a screen I can not see anything - so I can not really confirm if it works or not - and in windows I do not see
anything either..
Click to expand...
Click to collapse
hmm you better send it to repair.
evildog1 said:
hmm you better send it to repair.
Click to expand...
Click to collapse
That's unfortunately not an option as I had to disassemble the device
evildog1 said:
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
Click to expand...
Click to collapse
Should sdcard appear automatically when booting into recovery or are there any specific steps I would need to complete?
I’m also having an issue regarding my XZ1 Compact and Xperifix. I purchased Xperifix and I tried to use it with my XZ1 Compact (G8441, 47.1.A.12.179) yesterday. Unfortunately, it did not work.
Unlike the online video which demonstrates the process, when my phone boots during the process, the white Sony intro screen remains visible for a long time. Then I get a message saying: “It appears that TWRP is not booting. Please do it manually…” followed by instructions on how to do so. I follow these, eventually pressing volume down until TWRP appears, and then reconnecting the USB and pressing OK.
Although Xperifix indicates that it is continuing the process, TWRP remains on screen and nothing further happens. Eventually, I get the same “It appears that TWRP is not booting. Please do it manually…” message for a second time. Again, I follow there instructions. As before, Xperifix seems to indicate that it is performing normally. I then get a message telling me to check my phone to check that all has worked correctly. Unfortunately, it has not.
I have now completed this process perhaps six or seven times and the same thing happens every time. Can anybody please advise as to what I may be doing wrong or what I need to do in order for the software to run as intended?
Prior to running Xperifix, I unlocked my bootlaoder, resulting in green pictures from the camera. I was aware that this would happen, but I did so with a reasonable level of confidence that Xperifix would then resolve this issue for me. Obviously, it has not. So, even if there is no advice out there on how to get Xperifix to run successfully on my device, any advice on other methods of getting around this DRM issue would also be much appreciated.
Thank you in advance
Free25 said:
I’m also having an issue regarding my XZ1 Compact and Xperifix. I purchased Xperifix and I tried to use it with my XZ1 Compact (G8441, 47.1.A.12.179) yesterday. Unfortunately, it did not work.
Unlike the online video which demonstrates the process, when my phone boots during the process, the white Sony intro screen remains visible for a long time. Then I get a message saying: “It appears that TWRP is not booting. Please do it manually…” followed by instructions on how to do so. I follow these, eventually pressing volume down until TWRP appears, and then reconnecting the USB and pressing OK.
Although Xperifix indicates that it is continuing the process, TWRP remains on screen and nothing further happens. Eventually, I get the same “It appears that TWRP is not booting. Please do it manually…” message for a second time. Again, I follow there instructions. As before, Xperifix seems to indicate that it is performing normally. I then get a message telling me to check my phone to check that all has worked correctly. Unfortunately, it has not.
I have now completed this process perhaps six or seven times and the same thing happens every time. Can anybody please advise as to what I may be doing wrong or what I need to do in order for the software to run as intended?
Prior to running Xperifix, I unlocked my bootlaoder, resulting in green pictures from the camera. I was aware that this would happen, but I did so with a reasonable level of confidence that Xperifix would then resolve this issue for me. Obviously, it has not. So, even if there is no advice out there on how to get Xperifix to run successfully on my device, any advice on other methods of getting around this DRM issue would also be much appreciated.
Thank you in advance
Click to expand...
Click to collapse
Just a wild guess, as I have zero experience with Xperifix: make sure you are on the latest TWRP version (posted yesterday) to get data partition decryption to work for sure (independent on which security patch level you are on).
I advice you to use the official support you purchased with Xperifix.
4rz0 said:
I advice you to use the official support you purchased with Xperifix.
Click to expand...
Click to collapse
Good point I didn't realize it was paid-for software.
Free25 said:
what I need to do in order for the software to run as intended?
Click to expand...
Click to collapse
It sounds like you don't have the right drivers installed. You need Google USB drivers to be registered when you plug the phone in while running TWRP. This is tricky because by default Windows chooses the wrong drivers and you have to manually add/change them while TWRP is running. If you start the Xperia fix, manually start TWRP, set system as writable then plug it back in, you will see Xperiafix take control of the phone and reboot it. The fact it doesn't makes me think it's drivers.
Don't forget that Windows10 lies to you when it says it's installed the ADB drivers and you have to go into safe mode and 'disable signature checking' on the driver install
Xperiafix works, I used it, but getting the drivers right took me a couple of days..
You could read through the original app thread to find out a little bit more about how it works and there are even links to the drivers
you have to install at first the USB drivers for XZ1c.
if use use Windows 8+ you have to boot into the deactivated driver signature mode and install the driver.
On xperifix I can tell you, it downloads every time an old TWRP for XZ1C, which won't work with new firmware versions.
download the new TWRP version from our TWRP thread. then download portable minimal adb and fastboot, extract it on a place.
next step, start cmd.exe from start menu, enter the following command to switch in cmd into the path:
cd <path you have extracted minimal adb and fastboot >
enter the following command and don't execute it:
fastboot flash recovery <path were your downloaded TWRP is>
don't execute it!
reboot your phone into fastboot.
now start xperifix, click on fix device, and when you have a white Sony logo, plug out phone and reboot again into fastboot.
now switch to cmd.exe and execute the command.
press the key "up" to get the command again and replace the words "flash recovery" with "boot" and execute it again.
now your phone will boot into correct TWRP and let xperifix finish it's progress.
after restart, all should work.
you have at least to install the magisk manager and you will have working cam and magisk.
Thanks for all the advice thus far. I had already contacted the guys at Xperifix but am awaiting a response from them.
Within TWRP, the box marking the system read-only was already unchecked.
I had already visited https://developer.sony.com/develop/drivers/ and downloaded the ZX1 Compact drivers.
When in fastboot mode, my phone is recognised in device manager as Android Device – Sony ADB Interface. And, if I open a command prompt window from the Minimal ADB and Fastboot folder and enter “fastboot devices”, my phone is recognised.
Would this – the fact that my device is being recognised in fastboot mode - indicate that I have the correct drivers installed?
Sorry for all the newbie questions – I’d rooted a phone previously but it was years back, I’ve forgotten more than I remember, and I’m in a bit over my head. My own fault but, again, any further help in resolving this gratefully received. As you said Didgesteve, it works, I just need to figure out where I’m going wrong
if you test fastboot devices and you get a serial number, the driver is correct working.
test it with my method to replace TWRP after xperifix is started.
Raz0Rfail, just saw your post after my last response. Will take a look over that now. Thank you.
Free25 said:
I just need to figure out where I’m going wrong
Click to expand...
Click to collapse
Check out the link to the drivers I posted above, there's a how to video that's helpful
On the TWRP download list, I don’t see an option for the XZ1 Compact; only for the XZ or XZ premium. For both of these options, the most recent TWRP version listed is 3.2.1-0, and this is the version that Xperifix installed on my device. Would this indicate that Xperifix is giving me the most recent version?
Free25 said:
On the TWRP download list, I don’t see an option for the XZ1 Compact; only for the XZ or XZ premium. For both of these options, the most recent TWRP version listed is 3.2.1-0, and this is the version that Xperifix installed on my device. Would this indicate that Xperifix is giving me the most recent version?
Click to expand...
Click to collapse
Here you get the correct twrp for XZ1C:
https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
Didgesteve said:
Check out the link to the drivers I posted above, there's a how to video that's helpful
Click to expand...
Click to collapse
Thanks, I did have a look at that, but from what I'm seeing and reading (unless I'm missing something), it seems like this mightn't be a driver issue.
Free25 said:
Thanks, I did have a look at that, but from what I'm seeing and reading (unless I'm missing something), it seems like this mightn't be a driver issue.
Click to expand...
Click to collapse
The driver you use works.
What else is your problem?
I suspect that it’s TWRP, as you suggested. I downloaded ‘twrp-3.2.1-0-lilac-14’ and ‘twrp-3.2.1-0-lilac-14.img.asc’ (thank you for the link). I already had Minimal ADB and Fastboot installed.
I changed cmd directory to C:\Program Files (x86)\Minimal ADB and Fastboot, then entered ‘fastboot flash recovery C:\Users\25D\Downloads\TWRP\twrp-3.2.1-0-lilac-14’ (to where I had extracted the .img file)
I rebooted the phone into fastboot, activated Xperifix, waited for the white Sony screen, plugged out the phone, turned it off, plugged it back in in fastboot and executed the command. I erred somewhere however, as I received the response that the command is not recognised.
Probably a very elementary mistake on my part. Can you see where I went wrong?
the twrp filename has to be twrp-3.2.1-0-lilac-14.img with tab key you can do autocomplete
Tried it a few times now, got the
fastboot flash recovery C:\Users\25D\Downloads\TWRP\twrp-3.2.1-0-lilac-14.img
and
fastboot boot C:\Users\25D\Downloads\TWRP\twrp-3.2.1-0-lilac-14.img
to run successfully after rebooting in fastboot during the Xperifix process.
Still no joy though
The idea for correct path is, press shift + right mouse click on image file, then click copy path in contextmenu.
In cmd right mouse click and click on insert.
Thanks, I got the right path in the end and the flash recovery and boot seemed to run fine but it didn't seem to have any effect on the results from Xperifix
Free25 said:
Thanks, I got the right path in the end and the flash recovery and boot seemed to run fine but it didn't seem to have any effect on the results from Xperifix
Click to expand...
Click to collapse
Post the log files from C:\Xperiafix
This will show what's happening
Drivers is still my top guess
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
blkair445 said:
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
Click to expand...
Click to collapse
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
blkair446 said:
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
Click to expand...
Click to collapse
The blue light is fastboot mode. There is no ui interface in fastboot for sony devices. Just a blue light and black screen.
R800x_user said:
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Click to expand...
Click to collapse
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
blkair446 said:
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
Click to expand...
Click to collapse
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
jepher said:
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in ?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
Click to expand...
Click to collapse
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
blkair446 said:
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
Click to expand...
Click to collapse
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
jepher said:
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
Click to expand...
Click to collapse
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
blkair446 said:
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
Click to expand...
Click to collapse
Yes I am using w10. Will try linux later. I have searched everywhere and stucked at the same step. Thank you.
I have managed to unlock the bootloader and root the phone. But problem is. I can't write on the root folder.
More to this I think I might have located the boot file boot_X-flash-all-2396.sin but using magisk it returns no boot image found. I see the guide says use the canary built but that seems to have been shut down, so at an impasse here and am still reaching out for help - damn op phone were never this funky
I might as well put this one out there then -- Is there anyway to flash a op 8 pro in2025 to dual sim - it's the cause of this painful trip
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
jepher said:
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
Click to expand...
Click to collapse
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
cd993 said:
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
Click to expand...
Click to collapse
Yes. Relock it using fastboot command.
I use ubuntu to do it. If you can run fastboot commands in windows10 lucky you.
Developer option shows bootloader as locked but after reboot bootloader shows as unlocked . twrp working but Fastboot not working so I'm afraid I might brick my device as I can't flash fastboot rom. Please help.
I wanna know what you mean by 'Fastboot not working'. Does it mean you can't boot into fastboot mode, or does it mean you can't access fastboot commands on your pc?
Also i wanna know, while unlocking Bootloader. Did you used commands
Code:
fastboot oem unlock
and
Code:
fastboot oem unlock_critical
?
The device does boot into fastboot but doesnt respond to any fastboot command
It doesn't even show up on typing fastboot device
I unlocked the bootloader using miunlocktool
But the device doesnt even show up in the tool
pythonner said:
The device does boot into fastboot but doesnt respond to any fastboot command
It doesn't even show up on typing fastboot device
I unlocked the bootloader using miunlocktool
But the device doesnt even show up in the tool
Click to expand...
Click to collapse
If it's not responding to fastboot commands I worry that if correct drivers are installed on your pc.
Plug-in ur device while in fastboot mode to your pc.
Open Mi Unlock tool(this works very first time, you don't even have to install this tool). There's a setting icon on top right corner.
A dialogue box will appear, displaying to install drivers.
Install 'em. It will ask you to remove and plug-in your device again.
Now, download the platform tools file.
Open cmd in the platform tools folder.
Now try using fastboot commands.
It's same for me.
You can ignore that safely.
eleven.co said:
If it's not responding to fastboot commands I worry that if correct drivers are installed on your pc.
Plug-in ur device while in fastboot mode to your pc.
Open Mi Unlock tool(this works very first time, you don't even have to install this tool). There's a setting icon on top right corner.
A dialogue box will appear, displaying to install drivers.
Install 'em. It will ask you to remove and plug-in your device again.
Now, download the platform tools file.
Open cmd in the platform tools folder.
Now try using fastboot commands.
Click to expand...
Click to collapse
I updated the usb driver but unlock tool can't even detect the devices and when I type fastboot devices in platform tools the device is also not detected
I'm afraid of installing custom roms because if I brick it I will not be able to even flash the official fastboot rom
VD171 said:
It's same for me.
You can ignore that safely.
Click to expand...
Click to collapse
Actually when I type fastboot devices in platform tools the device is not even detected. So I'm afraid that if I flash custom rom and brick it I will be unable to flash even the official fastboot rom.
pythonner said:
I updated the usb driver but unlock tool can't even detect the devices and when I type fastboot devices in platform tools the device is also not detected
I'm afraid of installing custom roms because if I brick it I will not be able to even flash the official fastboot rom
Click to expand...
Click to collapse
Boot your phone, connect through USB to PC. Now check in Windows File Explorer. Is your device visible there?
If not, open Device Manager and you'll find something with the name adb (You can go through this guide). In my case it was under Acer. Just update those drivers manually and see if your device is visible now.
eleven.co said:
Boot your phone, connect through USB to PC. Now check in Windows File Explorer. Is your device visible there?
If not, open Device Manager and you'll find something with the name adb (You can go through this guide). In my case it was under Acer. Just update those drivers manually and see if your device is visible now.
Click to expand...
Click to collapse
the devices shows up in file explorer and device manger when its turned on but after putting in fastboot mode the platform tools cant detect the device
pythonner said:
the devices shows up in file explorer and device manger when its turned on but after putting in fastboot mode the platform tools cant detect the device
Click to expand...
Click to collapse
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
Now developer options is showing as unlocked and adb is also working good
but fastboot is still not working when I type fastboot devices It returns nothing
eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
What could be possible explanation to adb working but fastboot not working. The usb cable is tight and bootloader is unlocked even in developer options
eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
I just realised that I flashed twrp using the root app flashify. Could that be the reason for root not working
VD171 said:
It's same for me.
You can ignore that safely.
Click to expand...
Click to collapse
If you're rooted and have magisk hide enabled, it's normal, Magisk spoofs locked bootloader to pass safetynet in MIUI