Database Develop

How to revert back to NAA/stock kernel

rigt now im using alf CM7 v8 kernel, and now i want to flash back to Naa kernel, somehow my device is not recognizeable.
flash tool keep showing error that
error flashing aborted.
device connected in flash mode.
somehow i check that my adb and device id is not recognizeable by the flash tool after i use alf cm7 kernel, right now im stuck on ginger zaraki ROM.
please help.

Enable usb debugging,install drivers!

2010matej said:
Enable usb debugging,install drivers!
Click to expand...
Click to collapse
already on, driver also installed.
previously i usually switched from naa to stock, to naa ics or whatever, but after installed alfs v8 icant switched to others kernel, even now icannot isstall the alfs v8 either

03/024/2012 14:24:55 - INFO - <- This level is successfully initialized
03/024/2012 14:24:55 - INFO - Flashtool Version 0.9.0.0 built on 2012-07-19 22:57:15
03/024/2012 14:24:55 - INFO - You can drag and drop ftf files here to start flashing them
03/025/2012 14:25:00 - INFO - Device connected with USB debugging on
03/025/2012 14:25:00 - INFO - Connected device : E15
03/025/2012 14:25:00 - INFO - Installed version of busybox : BusyBox v1.20.2-cm7 bionic (2012-07-17 15:18 +0200) multi-call binary.
03/025/2012 14:25:00 - INFO - Android version : 2.3.7 / kernel version : 2.6.29.6-Alfs
03/025/2012 14:25:00 - INFO - Remounting system read-write
03/025/2012 14:25:01 - INFO - Installing toolbox to device...
03/025/2012 14:25:01 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
03/025/2012 14:25:01 - INFO - Running installftkit as root thru sysrun
03/025/2012 14:25:01 - INFO - Root Access Allowed
03/025/2012 14:25:15 - INFO - Reboot canceled
03/025/2012 14:25:24 - INFO - Flash canceled
03/025/2012 14:25:44 - INFO - Device disconnected
03/025/2012 14:25:52 - INFO - Selected E15_nAa-13_2.6.29.6-nAa-13.ftf
03/025/2012 14:25:52 - INFO - Preparing files for flashing
03/025/2012 14:25:52 - INFO - Please connect your device into flashmode.
03/025/2012 14:25:57 - INFO - Device connected in flash mode
03/025/2012 14:25:58 - INFO - Opening device for R/W
03/025/2012 14:25:58 - INFO - Start Flashing
03/025/2012 14:25:58 - INFO - Flashing loader
03/025/2012 14:25:58 - INFO - Ending flash session
03/025/2012 14:25:58 - ERROR -
03/025/2012 14:25:58 - ERROR - Error flashing. Aborted
03/025/2012 14:25:58 - INFO - Device connected in flash mode

try to use a different cable.....this could be it.....
Sent from my GT-S5570 using xda premium

reinstalling driver (all driver selected), changing cable also, after 5 times of try, finally work by itself.
still confuse, how the hell it works suddenly....but thanks for the suggestion all

Disable your antivirus
Sent from my X8 using xda premium

stepanucs said:
reinstalling driver (all driver selected), changing cable also, after 5 times of try, finally work by itself.
still confuse, how the hell it works suddenly....but thanks for the suggestion all
Click to expand...
Click to collapse
I sometimes get error,because usb cable lost connection. Same is when I charge,I connect cable to phone but there's no led light,I must to move cable left,right,up and down and it charge!

Downgrading 257 to 534

Hello, I've recently got my phone fix, and they updated my firmware to the latest one, I tried to downgrade it by flashing the 534 tft, but When i try to flash the official TFT, i get this error, which never happen before. Please help.
26/035/2013 13:35:56 - INFO - <- This level is successfully initialized
26/035/2013 13:35:56 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
26/036/2013 13:36:00 - INFO - Device connected in flash mode
26/036/2013 13:36:20 - INFO - Selected C6903 / 14.1.G.1.534 / Generic AU (1277-0078_R3A)
26/036/2013 13:36:20 - INFO - Preparing files for flashing
26/036/2013 13:36:20 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
26/036/2013 13:36:20 - INFO - Cannot open bundle. Flash operation canceled
26/036/2013 13:36:40 - INFO - Device disconnected
26/036/2013 13:36:49 - ERROR - Drivers need to be installed for connected device.
26/036/2013 13:36:49 - ERROR - You can find them in the drivers folder of Flashtool.
26/036/2013 13:36:51 - INFO - Device connected with USB debugging on
26/036/2013 13:36:52 - INFO - Connected device : Sony Xperia Z1
26/036/2013 13:36:52 - INFO - Installed version of busybox : N/A
26/036/2013 13:36:52 - INFO - Android version : 4.2.2 / kernel version : 3.4.0-perf-g66807d4-02450-g9a218f1 / Build number : 14.1.G.2.257
26/037/2013 13:37:40 - INFO - Device disconnected
26/037/2013 13:37:43 - INFO - Device connected in flash mode
26/038/2013 13:38:04 - INFO - Selected C6903 / 14.1.G.1.534 / Generic AU (1277-0078_R3A)
26/038/2013 13:38:04 - INFO - Preparing files for flashing
26/038/2013 13:38:04 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
26/038/2013 13:38:04 - INFO - Cannot open bundle. Flash operation canceled

Somehow it keep saying that i need to install driver, but i already done that...

What version of flastool are you using
Sent from my C6903 using XDA Premium 4 mobile app
EDIT
D'oh

gregbradley said:
What version of flastool are you using
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
26/035/2013 13:35:56 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
I had major problems with flashtool in the beginning, the only way I solved it was reinstall it a couple times changing version etc, finally version 0.9.12.0 worked.

Bell C6906 - Flashtool fails with error

Hello,
I am trying to flash my Bell Mobile C6906 Xperia Z1 which is currently on 4.2 - 14.1.G.1.534 to C6906 14.1.G.2.257 Generic CA 1276-7484_R7A with a md5sum of 'eb6570c22572a9c0151a768b05ce9f54' which is available from the thread titled '[FTF] C6902 & C6903 & C6906 & C6943 FTF Mega Collection' in the General section using Flashtool 0.9.13.0.
I have attempted this on a Windows 8, Windows 7 and a OpenSUSE install and all have failed with the exact same error. I have installed the drivers, loaded the rom in flashboot mode, connected the Xperia Z1 and held down the volume button and had it flash green/red (I believe, I am colourblind) and it has prepared the file and attempted to flash but fails with the following error which was created on a Windows 7 Starter - 32bit machine.
Code:
21/016/2013 11:16:23 - INFO - <- This level is successfully initialized
21/016/2013 11:16:23 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
21/016/2013 11:16:29 - INFO - Device connected with USB debugging on
21/016/2013 11:16:30 - INFO - Connected device : Sony Xperia Z1
21/016/2013 11:16:31 - INFO - Installed version of busybox : N/A
21/016/2013 11:16:31 - INFO - Android version : 4.2.2 / kernel version : 3.4.0-perf-gde8296d-02200-g6e85970 / Build number : 14.1.G.1.534
21/016/2013 11:16:31 - INFO - Checking root access
21/016/2013 11:16:31 - INFO - Root Access Allowed
21/016/2013 11:16:32 - INFO - Stopping ric service
21/016/2013 11:16:32 - INFO - ric service stopped successfully
21/016/2013 11:16:35 - INFO - List of connected devices (Device Id) :
21/016/2013 11:16:35 - INFO - - USB\VID_0FCE&PID_519E\BH900Z1B08 Driver installed : true
21/016/2013 11:16:35 - INFO - - USB\VID_0FCE&PID_519E&MI_01\6&1487FCA0&0&0001 Driver installed : true
21/016/2013 11:16:35 - INFO - - USB\VID_0FCE&PID_519E&MI_00\6&1487FCA0&0&0000 Driver installed : true
21/016/2013 11:16:35 - INFO - List of ADB devices :
21/016/2013 11:16:35 - INFO - - BH900Z1B08
21/016/2013 11:16:35 - INFO - List of fastboot devices :
21/016/2013 11:16:35 - INFO - - none
21/016/2013 11:16:51 - INFO - Selected C6906 / 14.1.G.2.257 / Generic CA
21/016/2013 11:16:52 - INFO - Preparing files for flashing
21/019/2013 11:19:04 - INFO - Please connect your device into flashmode.
21/021/2013 11:21:04 - INFO - Device disconnected
21/021/2013 11:21:48 - INFO - Opening device for R/W
21/021/2013 11:21:49 - INFO - Device disconnected
21/021/2013 11:21:49 - INFO - Start Flashing
21/021/2013 11:21:49 - INFO - Processing loader.sin
21/021/2013 11:21:49 - INFO - Checking header
21/021/2013 11:21:49 - INFO - Ending flash session
21/021/2013 11:21:49 - ERROR -
21/021/2013 11:21:49 - ERROR - Error flashing. Aborted
I have ran this with Administrative privileges on Windows and as root under Linux, I am currently at a loss as to how to fix this. I would really like to get off the Bell branded version and have an unbranded generic that I can keep updated to the newest version. (Which is the best I can do since sadly my bootloader cannot be unlocked)

I assume that you can root your Z1 as you are still on the 534 firmware.
Root your device and then follow this great GUIDE by Apollo89 (and be sure to hit him a thanks) to change the customization number to 1276-7484 then use SUS to get the latest firmware.
So basically what I'm telling you to do is to change the customization number to the one that you tried flashing it's ftf (1276-7484_R7A) and then get it on your device using SUS.
I can't confirm that it will work but hopefully it will.
Regards,
~J2C

I downloaded Build Props and allowed it root then changed my 'ro.semc.version.cust' to '1276-7484' and ro.semc.version.cus_revision to 'R1A' (from R11A) and then rebooted, on reboot it reset it back to 1276-3533 and R11A, tried again without changing cus_revision and still it reverted back.
It is most likely some issue with /system being read/writable, however I have set it so in root explorer and have multiple applications reporting that it is r/o (chmod 777) and do not appear to be having any errors with editing the build props, but they continue to revert when rebooting.

I found this C6906 Android 4.3 ftf
And I found this .257 firmware, but you need to send SMS or something to be able to download.
And I found this. it has 3 ftf's for C6906
Hope you find a working ftf.
Regards,
~J2C

Just2Cause said:
I found this C6906 Android 4.3 ftf
And I found this .257 firmware, but you need to send SMS or something to be able to download.
And I found this. it has 3 ftf's for C6906
Hope you find a working ftf.
Regards,
~J2C
Click to expand...
Click to collapse
Thanks, but according to this thread I can't update directly to 4.3 by using the ftf, it'll brick I don't use the 4.2 upgrade and then use PC Companion or similar to upgrade.

Well, flash the 257 from the other links...

Just2Cause said:
Well, flash the 257 from the other links...
Click to expand...
Click to collapse
The .257 from your links are identical to the one I was trying before, the exact same md5sum as before.

magwart said:
Thanks, but according to this thread I can't update directly to 4.3 by using the ftf, it'll brick I don't use the 4.2 upgrade and then use PC Companion or similar to upgrade.
Click to expand...
Click to collapse
I had the Bell branded 4.2 firmware installed on my 6906 and flashed the generic 4.3 firmware and have had no issues. Not sure if that post is 100% accurate. I also wiped my phone when I upgraded just so I could make sure I wouldn't run into any compatibility issues when I moved over.
After looking at your logs, it looks like the phone is not in flashboot. The flashtool is recognizing the phone in USB debug mode. Make sure you put the phone in flashboot before connecting to flashtool.
Here is a sample of my log.
Code:
16/047/2013 17:47:34 - INFO - <- This level is successfully initialized
16/047/2013 17:47:34 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
16/047/2013 17:47:39 - INFO - Device connected in flash mode
16/047/2013 17:47:48 - INFO - Selected C6906 / 14.2.A.0.290 / Generic CA
16/047/2013 17:47:49 - INFO - Preparing files for flashing
16/048/2013 17:48:01 - INFO - Please connect your device into flashmode.
16/048/2013 17:48:02 - INFO - Opening device for R/W
16/048/2013 17:48:03 - INFO - Reading device information
16/048/2013 17:48:03 - INFO - Phone ready for flashmode operations.
16/048/2013 17:48:03 - INFO - Current device : C6906 - BH90062B08 - 1276-3533_R11A - 1272-6084_14.1.G.1.534 - BELL-LTE_14.1.G.1.534
16/048/2013 17:48:03 - INFO - Start Flashing

mfreema said:
I had the Bell branded 4.2 firmware installed on my 6906 and flashed the generic 4.3 firmware and have had no issues. Not sure if that post is 100% accurate. I also wiped my phone when I upgraded just so I could make sure I wouldn't run into any compatibility issues when I moved over.
Also, when flashing, which version of the flashtool are you running? 32bit or 64bit?
Click to expand...
Click to collapse
I have ran 32bit on Windows 7 and 64bit on Windows 8. Both have had the same problem, and I can't figure out what the error is since it is blank. I suppose it has something to do with even a rooted system the /system partition remains not fully r/w on a locked bootloader.

magwart said:
I have ran 32bit on Windows 7 and 64bit on Windows 8. Both have had the same problem, and I can't figure out what the error is since it is blank. I suppose it has something to do with even a rooted system the /system partition remains not fully r/w on a locked bootloader.
Click to expand...
Click to collapse
Please see my updated post above.

magwart said:
I have ran 32bit on Windows 7 and 64bit on Windows 8. Both have had the same problem, and I can't figure out what the error is since it is blank. I suppose it has something to do with even a rooted system the /system partition remains not fully r/w on a locked bootloader.
Click to expand...
Click to collapse
Just try to flash the Android 4.3! I have done it many times on my phone from 534 to 290 and had 0 problems!
Regards,
~J2C

mfreema said:
Please see my updated post above.
Click to expand...
Click to collapse
I noticed that and got it to work in Flashmode, seems there was a driver issue - still causing an error:
Code:
21/029/2013 22:29:02 - INFO - Device connected in flash mode
21/029/2013 22:29:03 - INFO - Opening device for R/W
21/029/2013 22:29:03 - INFO - Reading device information
21/029/2013 22:29:03 - INFO - Unable to read from phone after having opened it.
21/029/2013 22:29:03 - INFO - trying to continue anyway
21/029/2013 22:29:03 - INFO - Start Flashing
21/029/2013 22:29:03 - INFO - Processing loader.sin
21/029/2013 22:29:03 - INFO - Checking header
21/029/2013 22:29:03 - INFO - Ending flash session
21/029/2013 22:29:03 - ERROR - Error in processHeader : 22 : The device does not recognize the command.
21/029/2013 22:29:03 - ERROR - Error flashing. Aborted
21/029/2013 22:29:03 - INFO - Device disconnected
Is the updated error.

maybe you are doing wrong steps?
Open flashtool > click on the flashing icon > select flashmode > navigate to where you have saved the ftf > Select the ftf you want to flash > then click on ok (or something like that, im in school right now so I cant tell) > wait till it finish preparing files > power off the phone, hold the VOL down and connect it to PC then wait till it finishes.
Regards,
~J2C

Just2Cause said:
maybe you are doing wrong steps?
Open flashtool > click on the flashing icon > select flashmode > navigate to where you have saved the ftf > Select the ftf you want to flash > then click on ok (or something like that, im in school right now so I cant tell) > wait till it finish preparing files > power off the phone, hold the VOL down and connect it to PC then wait till it finishes.
Regards,
~J2C
Click to expand...
Click to collapse
Thanks, I got it working! Currently using the Sony Update Service to .90 and 4.3. Now that I know that its possible to do this, I need to find a ROM that is compatible with working root.
Thanks again!

magwart said:
Thanks, I got it working! Currently using the Sony Update Service to .90 and 4.3. Now that I know that its possible to do this, I need to find a ROM that is compatible with working root.
Thanks again!
Click to expand...
Click to collapse
Finally :fingers-crossed:
EDIT: any .534 ftf is rootable, but you have to find one that has OTA update to .257 firmware. but it is not possible to root android 4.3 without unlocking bootloader (currently) so if you want root you should stick to 14.2.G.2.257 Android 4.2 till there is a way to root android 4.3.
Regards,
~J2C

flashtool problem xperia t

hello
Few minutes ago ive been trying to install new FW for xperia t suddenly flashtool says that i dont have drivers for my phone. So ive installed drivers for flashmode,fastboot and xperia t /tx from flashtool folder. however problem still exists. does anyone have solution for it.
thanks in advance

oh damn, not a single word about your running OS
let me guess? win8, 8.1? if you have linux/ubuntu based available, i would suggest you to use flashtool,fastboot,adb on linux. if you only have win8/8.1. then you should search our xperia T forums, there are several posts about problems. there are problems with driver certification or other stuff like that since win8. if i remember right somehow i got all working on win8, but since i have win8.1, i switched to linux for android stuff^^
if i find the way i got it working on win8, then i edit my post.
best for the average pc user would be to use win7. my opinion.

Oh sorry i forgot about OS. So im running on Win XP SP 3.

misiex2212 said:
Oh sorry i forgot about OS. So im running on Win XP SP 3.
Click to expand...
Click to collapse
Try a older version of Flash Tool,see if that helps. Also close any running processes you don't need before you install Flash Tool.

can someone provide link for older ver of flashtool. and about processes running in background i have only those needed by windows

Logs from flashtool. i get same error everytime im trying to flash it
16/027/2014 14:27:28 - INFO - <- This level is successfully initialized
16/027/2014 14:27:28 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
16/027/2014 14:27:36 - INFO - Device disconnected
16/027/2014 14:27:40 - INFO - Selected Bundle for Xperia T (LT30P). FW release : 9.2.A.0.295. Customization : Vodafone UK
16/027/2014 14:27:40 - INFO - Preparing files for flashing
16/029/2014 14:29:17 - INFO - Please connect your device into flashmode.
16/029/2014 14:29:25 - INFO - Opening device for R/W
16/029/2014 14:29:26 - INFO - Start Flashing
16/029/2014 14:29:26 - INFO - Processing loader.sin
16/029/2014 14:29:26 - INFO - Checking header
16/029/2014 14:29:26 - INFO - Ending flash session
16/029/2014 14:29:26 - ERROR -
16/029/2014 14:29:26 - ERROR - Error flashing. Aborted
16/029/2014 14:29:26 - ERROR - Drivers need to be installed for connected device.
16/029/2014 14:29:26 - ERROR - You can find them in the drivers folder of Flashtool.

Install the Flashmode, Fastboot and TX drivers from the flashtool/drivers directory

Mad Marty said:
Install the Flashmode, Fastboot and TX drivers from the flashtool/drivers directory
Click to expand...
Click to collapse
i have installed them already. ive tried with several usb cables and nothing.

I've had some issues with the .14 version of Flashtool that you seem to be using
I wasn't able to flash anything.
Worked like a charm though when using my brothers laptop, that is running an older version of Flashtool
So maybe using you should try an older version of it

problem solved.
ive used flashtool 0.9.9.0 however problem seems to be with busybox as ive installed it again and now is flashing without problems

(Closed) Strange error while trying to unlock bootloader

Oke so i finally got araund to do my daily driver sony xz1 compact and when i tried to unlock the bootloader using flashtool also know as sony mobile flasher by androyxde.
I get the following error
ERROR - Cannot invoke “String.split(String)” because the return value of “java.util.Properties.getProperty(String)” is null
Now i looked everywhere on the internet literally and i could not find a awnser to my problem but i did find multiple people with this problem but no defenitive awnser…
but i kept looking and i found that my computer can not find my phone exactlly because when i use command and try adb devices it cant see it but fastboot mode it can.
So i looked for an awnser and said probally need to update your drivers so i downloaded drivers from the sony site installed them then got the message that i have to restart computer before it can go into effect and i do that and then nothing stil does not work i see no adb devices in the list.
oh and i selected the allow unknow drivers from the security option in windos 10 so that should be oke.
I think this might be the problem that adb devices cant be read seeing as it has to be in that mode when trying to unlock the bootloader in flashtool.
This is what it shows in the program
01/048/2021 22:48:26 - INFO - Flashtool 0.9.33.0
01/048/2021 22:48:26 - INFO - Searching for a web proxy
01/048/2021 22:48:26 - INFO - No proxy found, using direct connection
01/048/2021 22:48:27 - INFO - Syncing devices from github
01/048/2021 22:48:27 - INFO - Opening devices repository.
01/048/2021 22:48:28 - INFO - Scanning devices folder for changes.
01/048/2021 22:48:36 - INFO - Pulling changes from github.
01/048/2021 22:48:37 - INFO - Devices sync finished.
01/048/2021 22:48:39 - INFO - Loading devices database
01/048/2021 22:48:39 - INFO - Loaded 131 devices
01/048/2021 22:48:39 - INFO - Starting phone detection
01/048/2021 22:48:58 - INFO - Device connected with USB debugging on
01/049/2021 22:49:01 - INFO - Connected device : Sony Xperia XZ1 Compact
01/049/2021 22:49:01 - INFO - Installed version of busybox : N/A
01/049/2021 22:49:01 - INFO - Android version : 9 / kernel version : 4.4.148-perf+ / Platform : 64bits / Build number : 47.2.A.11.228
01/049/2021 22:49:01 - INFO - Root access denied
After that i try ubl option
01/051/2021 22:51:20 - INFO - Please connect your device into flashmode.
01/051/2021 22:51:57 - INFO - Using Gordon gate drivers version 3.2.0.0
01/051/2021 22:51:58 - INFO - Opening device for R/W
01/051/2021 22:51:58 - INFO - Device ready for R/W.
01/051/2021 22:51:58 - INFO - Reading device information
01/051/2021 22:51:58 - INFO - Reading phone properties
01/051/2021 22:51:58 - INFO - Sending getvarroduct
01/051/2021 22:51:58 - INFO - getvar status : OKAY
01/051/2021 22:51:58 - INFO - Sending Read-TA:2:2202
01/051/2021 22:51:58 - INFO - Read-TA status : OKAY
01/051/2021 22:51:58 - INFO - Sending Read-TA:2:2205
01/051/2021 22:51:58 - INFO - Read-TA status : OKAY
01/051/2021 22:51:58 - INFO - Sending Read-TA:2:2210
01/051/2021 22:51:58 - INFO - Read-TA status : OKAY
01/051/2021 22:51:58 - INFO - Sending Read-TA:2:4900
01/051/2021 22:51:58 - INFO - Read-TA status : OKAY
01/051/2021 22:51:58 - INFO - Sending Read-TA:2:10021
01/051/2021 22:51:58 - INFO - Read-TA status : OKAY
01/051/2021 22:51:58 - INFO - Sending Get-root-key-hash
01/051/2021 22:51:58 - INFO - Get-root-key-hash status : OKAY
01/051/2021 22:51:59 - INFO - Connected device : G8441 / SW release 1307-7511_47.2.A.11.228 / Customization 1310-8075_R4C
01/051/2021 22:51:59 - INFO - Last flash date : 2018-11-19 23:19:03
01/051/2021 22:51:59 - INFO - Phone ready for flashmode operations.
01/051/2021 22:51:59 - ERROR - Cannot invoke "String.split(String)" because the return value of "java.util.Properties.getProperty(String)" is null
C:\Users\n>adb devices
List of devices attached
adb server is out of date. killing…
daemon started successfully *
C:\Users\n>adb reboot bootloader
error: device ‘(null)’ not found
C:\Users\n>

It's been a while since I've done it but I think you need the Google USB drivers and the 15sec ADB driver. If I remember, the Sony driver doesn't work for ADB/Fastboot. You'll need to update/assign one driver while it's connected in normal mode and do the other while it's in fastboot mode.

Thank you for your fast reply
I already had 15 sec adbdriver and for the assigning driver i dont quite understand but i tried it in difrent modes and it tells it already has the most up to date drivers.
stil doesnt work
what am i missing ?

mstrnemo said:
Thank you for your fast reply
I already had 15 sec adbdriver and for the assigning driver i dont quite understand but i tried it in difrent modes and it tells it already has the most up to date drivers.
stil doesnt work
what am i missing ?
Click to expand...
Click to collapse
Did you assign the drivers manually? Windows will almost always tell you that you have the most up-to-date drivers and leave it at that. You need to go to device manager, right click update driver and then select browse my computer for drivers. It'll give you the option to search a location on your computer but you want the 2nd option that says Let Me Pick from a List of Available Drivers on my Computer.
I also reread your OP and saw you're using sony mobile flasher by androyxde. I don't remember ever using that. It was several years ago but I only used newflasher, renoroot and adb/fastboot. I used newflasher to downgrade to Oreo, renoroot to back up TA and adb/fastboot to unlock the bootloader. Then I did the process in reverse to have an unlocked BL and the latest Pie version.

AlexKarimov said:
Did you assign the drivers manually? Windows will almost always tell you that you have the most up-to-date drivers and leave it at that. You need to go to device manager, right click update driver and then select browse my computer for drivers. It'll give you the option to search a location on your computer but you want the 2nd option that says Let Me Pick from a List of Available Drivers on my Computer.
I also reread your OP and saw you're using sony mobile flasher by androyxde. I don't remember ever using that. It was several years ago but I only used newflasher, renoroot and adb/fastboot. I used newflasher to downgrade to Oreo, renoroot to back up TA and adb/fastboot to unlock the bootloader. Then I did the process in reverse to have an unlocked BL and the latest Pie version.
Click to expand...
Click to collapse
Newflasher ? is just to flash firmware i dont need to i already have latest firmware.
I did that first manuelly install drivers i downloaded from the sony site but i do not know about the adb driver ? is that the 15 sec adb driver installer
I cant unlock bootloader using adb/fastboot because when using command adb devices it cant see my phone?
so wether it is flashtool or adb/fastboot it doesnt work theres gotta be something i am missing?
see below what it says in command
(c) Microsoft Corporation. All rights reserved.
C:\Users\n>adb devices
List of devices attached
C:\Users\n>adb reboot bootloader
error: no devices/emulators found
C:\Users\n>

mstrnemo said:
Newflasher ? is just to flash firmware i dont need to i already have latest firmware.
I did that first manuelly install drivers i downloaded from the sony site but i do not know about the adb driver ? is that the 15 sec adb driver installer
I cant unlock bootloader using adb/fastboot because when using command adb devices it cant see my phone?
so wether it is flashtool or adb/fastboot it doesnt work theres gotta be something i am missing?
see below what it says in command
(c) Microsoft Corporation. All rights reserved.
C:\Users\n>adb devices
List of devices attached
C:\Users\n>adb reboot bootloader
error: no devices/emulators found
C:\Users\n>
Click to expand...
Click to collapse
You need newflasher to downgrade to oreo so you can unlock bootloader.
If you have the ADB driver, then you need the Google USB driver.
If none of this helps, I'm sorry but I can't offer any more.

i need to downgrade to oreo so i can unlock bootloader ?
i didnt know that what is the reason for this ?
hmmm is there a how to on the site or somewhere that i may have missed somehowe ? seems weird to me there isnt alot of info about this doesnt have everyone had the same problem at some point?
Anyway thank you for your help

when on my computer can see it so it works
when in fastboot mode it can be seen so it has the right driver (can also be seen in command)
however android adb interface has a ! mark and gives me a code 10 error ?
Edit: i deleted the one with the ! so no more code 10 error but i then tried literally every single one in the list but noone works ? with that i mean it shows the device works but i can not use command adb devices and adb reboot bootloader does stil not work

I ****ed up i had it ... it worked i dont know what i did but it worked so i go back to flashtool thinking to get this over with now suddenlly i get error missing driver? and that i should go to the driver folder and i go there and install al of them just in case i then try it again but now i get the same error i had in the beginning ? adb doesnt work anymore and now i try to install adb driver but it wont work ??? damn 2 steps front 3 steps back

Anyone willing to help me install drivers i just cant seem to get it to work?

I ended up reinstalling windows 10 and then tried again and then it worked.
/Closed/