Hi guys,
i try rooting my z5c with this tutorial.
I'm stuck on 5.7 (Flash your patched Kernel to your phone with this command: fastboot flash boot kernel-patched.elf)
The Process always stops at " <waiting for device> "
fastboot devices has no output
flashtool output:
05/044/2016 20:44:55 - INFO - Starting phone detection
05/044/2016 20:44:59 - INFO - Device connected in fastboot mode
05/045/2016 20:45:08 - INFO - List of connected devices (Device Id) :
05/045/2016 20:45:08 - INFO - - USB\VID_0FCE&PID_0DDE\CB5A2B7F8N Driver installed : true
05/045/2016 20:45:08 - INFO - List of ADB devices :
05/045/2016 20:45:08 - INFO - - none
05/045/2016 20:45:08 - INFO - List of fastboot devices :
05/045/2016 20:45:08 - INFO - - CB5A2B7F8N
OS: Win10
Flashtool drivers installed: Fastboot, Flashmode, Xperia Z5c
I installed them skipping the untrusted driver signature warning, ohterwise it would have failed.
The devicemanagement says: Android Device > Sony Fastboot Interface
Would be nice if someone could help
Edit: It worked now but I have absolutely now idea why. I was away for a few hours and simply tried again. OS not rebooted and phone off during this time. Just turned it into fastboot mode again but i did this several times earlier without any effect.
Nice to see you solved, in my experience it's usually driver problems looking in Device Management.
Related
All -
I cant seem to post to the development forum due to my lack of post counts. So here's the issue.
My Xperia S doesnt boot. what I did was I tried to flash it with the recently released ICS. When trying to flash using flashtool 0.8.6.0, it says, Drivers need to be installed for connected device. I did install the drivers from the driver directory on that came with flashtool.
I did some digging and found out that my computer isnt recognizing a device on the device manager. it is called QHSUSB_DLOAD. I searched the internet for a driver for this qualcom device but it wont let me update the driver. it seems that it isn't compatible.
I'm on Win7. anyone else having this issue?
Here is the log from flashtool
22/042/2012 08:42:40 - ERROR - Drivers need to be installed for connected device.
22/042/2012 08:42:40 - ERROR - You can find them in the drivers folder of Flashtool.
22/057/2012 08:57:07 - INFO - List of connected devices (Device Id) :
22/057/2012 08:57:07 - INFO - - USB\VID_0FCE&PID_3DDE\6&DF2EE03&0&4 Driver installed : false
22/057/2012 08:57:07 - INFO - List of ADB devices :
22/057/2012 08:57:08 - INFO - - none
22/057/2012 08:57:08 - INFO - List of fastboot devices :
22/057/2012 08:57:08 - INFO - - none
b3rx said:
Here is the log from flashtool
22/042/2012 08:42:40 - ERROR - Drivers need to be installed for connected device.
22/042/2012 08:42:40 - ERROR - You can find them in the drivers folder of Flashtool.
22/057/2012 08:57:07 - INFO - List of connected devices (Device Id) :
22/057/2012 08:57:07 - INFO - - USB\VID_0FCE&PID_3DDE\6&DF2EE03&0&4 Driver installed : false
22/057/2012 08:57:07 - INFO - List of ADB devices :
22/057/2012 08:57:08 - INFO - - none
22/057/2012 08:57:08 - INFO - List of fastboot devices :
22/057/2012 08:57:08 - INFO - - none
Click to expand...
Click to collapse
err... i think u've already found the answers. it's just jumbled..
b3rx said:
Here is the log from flashtool
USB\VID_0FCE&PID_3DDE\6&DF2EE03&0&4 Driver installed : false
22/042/2012 08:42:40 - ERROR - Drivers need to be installed for connected device.
22/042/2012 08:42:40 - ERROR - You can find them in the drivers folder of Flashtool.
Click to expand...
Click to collapse
gud luck!
Fixed!!
Thank God for Linux.
@m1st3r1: as previously stated on my OP, I did update and installed the drivers but it wasn't recognizing it. Using FlashTool for Linux fixed the problem.
Hi,
i tried to enter fastboot mode via flashtool.
I get this log when i enter the unlock mode:
22/055/2012 19:55:23 - INFO - Device connected with USB debugging on
22/055/2012 19:55:23 - INFO - Connected device : U20
22/055/2012 19:55:23 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
22/055/2012 19:55:23 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.A.0.6
22/055/2012 19:55:26 - INFO - Root Access Allowed
22/055/2012 19:55:33 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
22/055/2012 19:55:33 - INFO - Device Status: ADB mode
22/055/2012 19:55:35 - INFO - Device Status: ADB mode
22/055/2012 19:55:36 - ERROR - This action can be done only if the connected phone has fastboot mode
22/055/2012 19:55:38 - INFO - Finished Fastboot Toolbox
22/004/2012 20:04:44 - INFO - Please connect your device into flashmode.
22/004/2012 20:04:48 - INFO - Device disconnected
22/005/2012 20:05:11 - INFO - Device connected in flash mode
22/005/2012 20:05:11 - INFO - Opening device for R/W
22/005/2012 20:05:11 - INFO - Reading device information
22/005/2012 20:05:11 - INFO - Phone ready for flashmode operations.
22/005/2012 20:05:11 - INFO - Processing loader
22/005/2012 20:05:11 - INFO - Checking header
22/005/2012 20:05:11 - INFO - Flashing data
22/005/2012 20:05:13 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : ROOTED
22/005/2012 20:05:13 - INFO - Phone already unlocked
22/005/2012 20:05:13 - INFO - You can safely reboot in normal mode
22/005/2012 20:05:13 - INFO - Ending flash session
22/005/2012 20:05:13 - WARN - Cancelled
22/005/2012 20:05:13 - INFO - Device connected in flash mode
22/005/2012 20:05:15 - INFO - Device disconnected
22/005/2012 20:05:17 - INFO - Device connected in flash mode
So the phone is allready unlocked.
I have the Google Android ADB drivers installed.
But i can not kick the phone into fastboot via ADB.
Also i can not enter fastboot with any key while plugging the usb into the phone.
Any suggestions?
thx
A19183
are you sure you are entering fastboot mode in a proper way? power off the phone, hold vol down button and connect to pc, if the led turns blue you are in fastboot mode.
edit:
it seems you are trying this on x8 or similar phone, hold menu and connect the device
Think so......
n0b0dy666 said:
are you sure you are entering fastboot mode in a proper way? power off the phone, hold vol down button and connect to pc, if the led turns blue you are in fastboot mode.
Click to expand...
Click to collapse
Yes, i tried that several times.
The Blue light does not come on.
But i should be able to Kick it from ADB into fastboot via Flashtool, shouldn't i?
Greets
A19183
Edit:
Phone: xperia x10 Mini pro
System: Win xp in Parallels Desktop for Mac
a19183 said:
Yes, i tried that several times.
The Blue light does not come on.
But i should be able to Kick it from ADB into fastboot via Flashtool, shouldn't i?
Greets
A19183
Edit:
Phone: xperia x10 Mini pro
System: Win xp in Parallels Desktop for Mac
Click to expand...
Click to collapse
Okay, there are 2 things:
1. This is xperia mini pro sk17i forum and not x10 mini pro, so better ask there
2. On our phone it's volume up to enter fastboot and please install all drivers for all devices/modes from flashtool folder -> drivers, too...
Sent from my SK17i running Jelly Bean via CM10
Oooops
mihahn said:
Okay, there are 2 things:
1. This is xperia mini pro sk17i forum and not x10 mini pro, so better ask there
2. On our phone it's volume up to enter fastboot and please install all drivers for all devices/modes from flashtool folder -> drivers, too...
Sent from my SK17i running Jelly Bean via CM10
Click to expand...
Click to collapse
Sorry,
My Bad.
Could someone move the thread or close it?
As Far as i understand the x10 does Not have fastboot..
Shame on me..........
:silly:
I tried everything i see on web to root my phone. But it does not detect in adb mode while the phone is swithed on. i ticked usb debugging and install latest sdk, pdanet+ , drivers & every thing but no use. when i execute adb devies. it just shows:
c:\user\adb devies
List of devices attached
c:\user
what shall i do? But it gets connected to pc in adb mode when the phone is in fastboot mode(volume up+usb insert). at that time my pc shows Android adb interface. but not shown when the phone is switched on.
i need to root my phone urgently. somebody plsssss help me
Thanks in advance
Reinstall all drivers. I heard pcc installs them all for you.
Sent from my LT22i using xda app-developers app
Maybe Install flashtool and install the drives that come with it?
I am not sure, but I think that is what is working for me.
installed flash tool
23/022/2013 13:22:41 - INFO - Device connected with USB debugging off
23/022/2013 13:22:41 - INFO - For 2011 devices line, be sure you are not in MTP mode
23/022/2013 13:22:51 - INFO - List of connected devices (Device Id) :
23/022/2013 13:22:51 - INFO - - USB\VID_0FCE&PID_5172\CB511Z2FJ2 Driver installed : true
23/022/2013 13:22:51 - INFO - List of ADB devices :
23/022/2013 13:22:51 - INFO - - none
23/022/2013 13:22:51 - INFO - List of fastboot devices :
23/022/2013 13:22:51 - INFO - - none
actually i have enabled debugging mode. What to do???
As i said, REINSTALL ALL DRIVERS
Sent from my LT22i using xda app-developers app
gibintgeorge said:
23/022/2013 13:22:41 - INFO - Device connected with USB debugging off
23/022/2013 13:22:41 - INFO - For 2011 devices line, be sure you are not in MTP mode
23/022/2013 13:22:51 - INFO - List of connected devices (Device Id) :
23/022/2013 13:22:51 - INFO - - USB\VID_0FCE&PID_5172\CB511Z2FJ2 Driver installed : true
23/022/2013 13:22:51 - INFO - List of ADB devices :
23/022/2013 13:22:51 - INFO - - none
23/022/2013 13:22:51 - INFO - List of fastboot devices :
23/022/2013 13:22:51 - INFO - - none
actually i have enabled debugging mode. What to do???
Click to expand...
Click to collapse
Remove the drivers first, then reinstall Flashtool drivers, report back when you have done that.
When my phone is in fastboot mode (blue LED) FlashTool log prints message "INFO - Device connected in fastboot mode" but this is all what I can get. Nothing else works in this mode. FlashTool wants me to set device into fastboot mode but it is in this mode at the moment.
Open your phone at fastboot mode when it asks. I mean a window will open when you click the bolt, select fastboot and select the thing you wanna do. And do what it says.
vurucumiller said:
Open your phone at fastboot mode when it asks. I mean a window will open when you click the bolt, select fastboot and select the thing you wanna do. And do what it says.
Click to expand...
Click to collapse
I'm doing averything but nothing happens
I'm do not know much too, i suggest you to send it to service
Log from FlashTool:
02/007/2015 01:07:38 - INFO - Device connected in fastboot mode
02/007/2015 01:07:46 - INFO - List of connected devices (Device Id) :
02/007/2015 01:07:46 - INFO - - VID_0FCE&PID_0DDE\ Driver installed : true
02/007/2015 01:07:46 - INFO - List of ADB devices :
02/007/2015 01:07:46 - INFO - - none
02/007/2015 01:07:46 - INFO - List of fastboot devices :
02/007/2015 01:07:46 - INFO - - none
vurucumiller said:
I'm do not know much too, i suggest you to send it to service
Click to expand...
Click to collapse
on what basis?
You can say you tried to flash sth. and you failed, i think.
Hello everyone; I need your help and assistance.
I am having trouble unlocking the bootloader of a Sony Xperia M4 Aqua E2303 device; the Service Menu (*#*#7378423#*#*) reveals Rooting Status: Bootloader unlock allowed - Yes.
Device Details
Android version: 5.0
Build number: 26.1.A.3.111
I have downloaded and installed the corresponding driver from https://developer.sony.com/develop/drivers/, downloaded and installed the Google USB Driver (https://developer.android.com/studio/run/win-usb), and availed an unlock code from https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
From hereon, I downloaded and extracted the SDK Platform-Tools for Windows (https://developer.android.com/studio/releases/platform-tools), but utilising the code
Code:
fastboot -i 0x0fce oem unlock 0x<myunlockcode>
(referred from https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/) only yielded within Command Prompt the message: fastboot: unknown option -i.
Since the above procedure did not yield the desired result, I attempted the alternative: Flashtool method, using the [Guides][Root][FlashTool][Drivers][Memory Problems][Unlock Bootloader] [TA Backup] (https://forum.xda-developers.com/m4-aqua/general/guide-t3130092) as a reference guide. I downloaded and installed Flashtool 0.9.18.6, and the Flashtool Drivers; albeit the installation directory on my computer is set C:\Flashtool, inside C:\Users\<myusername>\.flashTool\registeredDevices, I created a folder titled mydevices, within it another folder having the device code as its title, and within the latter folder I created a text file titled ulcode, having the unlock code as data entry.
However, post flash mode and fastboot mode processes, Flashtool concludes ....INFO - FAILED (remote: Command not allowed). I have furnished the narrative of the Flashtool process' log below.
08/024/2018 02:24:04 - INFO - Flashtool Version 0.9.18.6 built on 30-05-2015 22:30:00
08/024/2018 02:24:04 - INFO - Executing search strategies to find proxy selector
08/024/2018 02:24:04 - INFO - No proxy found for IE. Trying next one
08/024/2018 02:24:04 - INFO - Strategy firefox failed trying next one : No Firefox installation found
08/024/2018 02:24:04 - INFO - No proxy found for java. Trying next one
08/024/2018 02:24:04 - INFO - Syncing devices from github
08/024/2018 02:24:04 - INFO - Scanning devices folder for changes.
08/024/2018 02:24:11 - INFO - Pulling changes from github.
08/024/2018 02:24:11 - INFO - Devices sync finished.
08/024/2018 02:24:12 - INFO - Device disconnected
08/024/2018 02:24:22 - INFO - Device connected with USB debugging off
08/024/2018 02:24:22 - INFO - For 2011 devices line, be sure you are not in MTP mode
08/024/2018 02:24:22 - INFO - Device connected with USB debugging on
08/024/2018 02:24:22 - ERROR - root : this bundle is not valid
08/024/2018 02:24:23 - INFO - Connected device : Sony Xperia M4 Aqua
08/024/2018 02:24:23 - INFO - Installed version of busybox : N/A
08/024/2018 02:24:23 - INFO - Android version : 5.0 / kernel version : 3.10.49-perf-gc6d4e64 / Build number : 26.1.A.3.111
08/024/2018 02:24:31 - INFO - Please connect your device into flashmode.
08/024/2018 02:24:36 - INFO - Device disconnected
08/025/2018 02:25:22 - INFO - Device connected in flash mode
08/025/2018 02:25:22 - INFO - Opening device for R/W
08/025/2018 02:25:22 - INFO - Reading device information
08/025/2018 02:25:22 - INFO - Phone ready for flashmode operations.
08/025/2018 02:25:22 - INFO - Current device : E2303 - YT9114QVLK - 1293-9369_R16A - 1291-5963_26.1.A.3.111 - GENERIC_26.1.A.3.111
08/025/2018 02:25:22 - ERROR - root : this bundle is not valid
08/025/2018 02:25:22 - INFO - Processing loader.sin
08/025/2018 02:25:22 - INFO - Checking header
08/025/2018 02:25:22 - INFO - Flashing data
08/025/2018 02:25:22 - INFO - Processing of loader.sin finished.
08/025/2018 02:25:23 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_37 / Bootloader status : ROOTABLE
08/025/2018 02:25:23 - INFO - Start Reading unit 000008B2
08/025/2018 02:25:23 - INFO - Reading TA finished.
08/025/2018 02:25:23 - INFO - Ending flash session
08/025/2018 02:25:23 - INFO - Now unplug your device and restart it into fastbootmode
08/025/2018 02:25:23 - INFO - Device connected in flash mode
08/025/2018 02:25:24 - INFO - Device disconnected
08/025/2018 02:25:27 - INFO - Device connected in flash mode
08/025/2018 02:25:33 - INFO - Device disconnected
08/025/2018 02:25:51 - INFO - Device connected in fastboot mode
08/029/2018 02:29:20 - INFO - Unlocking phone using key XXXXXXXXXXXXXXXX
08/029/2018 02:29:20 - INFO - ...
08/029/2018 02:29:20 - INFO - FAILED (remote: Command not allowed)
08/029/2018 02:29:20 - INFO - finished. total time: 0.005s
I await your valuable replies, correcting whatever mistake(s) I may have very likely committed.
Having done almost all of the important leg work, I overlooked the most fundamental dynamic: Enable OEM unlock within Developer options; I was unaware of the said feature due to lack of sustained experience with Sony Xperia devices!
:silly:
The bootloader has been successfully unlocked, subsequently, custom recovery (TWRP) was successfully flashed, and the device was successfully rooted.
:good: