Related
I just recently got into modding my N1 a few weeks ago and finally hit my first snag:
Original root was through superoneclick, so bootloader is still locked. I flashed over to stock GRI40 OTA without realizing (stupidly) that flashing
it would also flash over my RA recovery and unroot my phone. Now, superoneclick is incompatible with GRI40, so I can't re-root through that, and I'm having trouble
with unlocking the bootloader through fastboot.
I get no response from ADB or fastboot in windows cmd prompt when I boot phone to FASTBOOT.
the command "fastboot devices" gives me a repeat of the same prompt with no error. (I can't get fastboot to work in normal debugging mode either, and I don't know if it usually will, because this is the first time I've used it.)
the command "adb devices" gives me response-- "list of devices attached" with nothing below (ADB works fine in debugging mode though).
I thought it might be a driver problem, but "Android bootloader Interface" driver is on the device manager list while phone is in fastboot, and seems to be properly
installed; I can't seem to find another suitable driver to update it to anyways.
Beyond that, there don't seem to be any other drivers running in the device manager either.
It's to the point where I'm considering taking the long way around and re-rooting through passimg, but that may not work anyways from what I've been reading, and that still won't fix my fastboot issue.
Any ideas on why I can't get fastboot to work?
my devise manager lists it as 'Android 1.0' when connected with fast boot..
if the drivers were installed on their own, then uninstal them.. and manually update the drivers (download them yourself)
that might help.. idk..
Sent from my nexus one
I think that may be part of the problem because I'm not seeing Android 1.0 on the device manager list. I do have an unknown device on there, but I can't update the driver with any of the Google USB drivers. Also, I'm pretty sure it's not my N1 because I'll unplug the N1, delete the unknown device, and scan for hardware changes and it will pop up again, so I don't think it has anything to do with my phone.
Put your phone in to fast boot, plug the phone in to a different port on your computer. If you have been plugging it in to the front, plug it in to the back. If you have been plugging it in to the back, plug it in to the front.
This should force windows to re-detect your device and it will hopefully install the missing drivers you're needing...
That was a good idea, but I had no luck with that one either. Thanks though.
Alright, shreyas said device is "Android 1.0" from windows device manager when the phone is in fastboot. Why does mine say "Android Bootloader Interface" and is this the case for everyone else?
Even more interestingly, I'll uninstall it, manually install whatever driver I chose for it, and that installation will fail. Then, I'll uninstall it again and have 'puter automatically scan for hardware, "android 1.0" pops up as one of the unknown devices but then gets reassigned as "android Bootloader Interface" after automatically installing drivers.
Oh yeah, I'm running Windows 7 64.
The drivers mentioned here didn't help either
http://forum.xda-developers.com/showthread.php?t=702927
stratmn5105571 said:
Oh yeah, I'm running Windows 7 64.
Click to expand...
Click to collapse
i am on win7 32!
btw umm try this link
http://android.modaco.com/content/z...com/319156/winxp-7-zte-blade-drivers-and-adb/
another umm stupid thing mayb, did you try out adb wireless..?
Have you tried using the PDANet drivers? Those are the ones that I've had the best luck with on my Win7 x64 laptop.
EDIT: Seems you have...
I'd recommed using an application called USBDeView (I think?) to manually uninstall all USB drivers for Android/HTC/ADB/NexusOne/etc, and THEN installing the PDANet drivers.
Thanks for your help. I ended up downloading "superboot," which has fastboot on it, and it works just fine. I don't know what the deal is with the fastboot that came with the SDK but my computer just doesn't seem to like it. I checked and rechecked all commands and file directories, and I just don't get it...oh well, I hope this helps others.
Thanks again.
My PC and phone setup works as expected but gives error when booting in flash mode. PC Companion and other tools (Flashtools) can recognize device but holding back button while connecting to usb (when it is already OFF) makes "Device driver failed" error and makes yellow exclamation mark on device manager for "SEMC FLASH ...."
Win7 XP 64 Bit
Sony Experia X8
Latest PC Companion app.
What I tried:
- Disabled antivirus from beginning.
- Gordon's Gate Driver "ggsetup-2.2.0.10" and "ggsetup-2.2.0.11".
- Flashtools/Drivers/ "X8 ADB Driver"
- Another Win7 64 Bit Computer with disabled antivirus
It fails only when detecting the sim lock type with S1Tool. My phone led turns green as expected. I follow this guide http://forum.xda-developers.com/showthread.php?t=1693308
Now I get "Access Denied" error
I' ve copied "X8 ADB drivers" to somewhere and tried to update drivers by "Update Drivers" on device manager by choosing X8 ADB Drivers.
And now "S1 Tool" freezes or says
PLEASE ATTACH TURNED OFF PHONE NOW
llbug:[\\?\USB#VID_0FCE&PID_ADDE#5&30124de0&0&5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}] open error: "Access is denied"
Elapsed:70 secs.
on the flashing screen.
I tried when AV is Off with no luck
I will try flashing in the safe mode as suggested on another post.
How to get X8 ADB Driver: When installing drivers from flashtool it will temporarily copy the driver files to "C:\Users\...\AppData\Local\..." (ass seen on the install screen) . Copy the files from there before installation complete.
SuperOneClick
SuperOneClick was the correct way to unlock my bootloader. But know I can't install custom kernel. Because this time flashtool can't recognize my device in flash screen.
I will try with Flashtool 6.9.1 instead of 0.9
turkert said:
SuperOneClick was the correct way to unlock my bootloader. But know I can't install custom kernel. Because this time flashtool can't recognize my device in flash screen.
I will try with Flashtool 6.9.1 instead of 0.9
Click to expand...
Click to collapse
SuperOneClick won't unlock your BL, it will just root your phone...
Hi guys, got a slight problem with entering fastboot mode. I hold the volume-up key and connect me USB cable but rather than getting the noise verifying it's been connected ok, I get that dull sound it makes when it hasn't worked. It won't even let me install the drivers and in device manager it comes up as "S1boot Fastboot" for a few seconds before then going into battery charging mode. I downloaded the Android SDK latest and replaced the USB driver INF file with the one sony give you but it didn't work so reversed back to the other driver the SDK manager installs and that didn't work either.
I've been through the tutorials and even tried to update the driver in device manager in the few seconds it stays there but that didn't work either! USB debugging is enabled too!
Please help, I'm not a noob and have done fastboot booting before and yes for those who may ask have already checked to make sure the bootloader can be unlocked and yes it can also the phone is NOT branded and is unlocked to all networks.
Any help will be appreciated, thanks!
Dave.
Are you on Windows 8? Using USB 3.0?
"As your flesh bears the sigil....your name is that....of a recusant."
First be sure you're using a 2.0 usb port, if this is ok maybe it's a windows 8 driver problem, so you should try this http://forum.xda-developers.com/showthread.php?t=2170114. It works for me
For also fastboot and flashmode come for 5 Sec. So Make sure you prepare the file and attach the device to fastboot or flashmode when it is asked.
Still problems
I'm still working on a 2012 laptop with Windows 7 Premium installed. It's fully up to date and all the drivers are installed properly I just don't get it, I've tried everything and it's still making the noise as if it won't connect. I don't know what to do to be honest. Also yes it is USB 2.0.
darkdemon32 said:
I'm still working on a 2012 laptop with Windows 7 Premium installed. It's fully up to date and all the drivers are installed properly I just don't get it, I've tried everything and it's still making the noise as if it won't connect. I don't know what to do to be honest. Also yes it is USB 2.0.
Click to expand...
Click to collapse
Hmm...how many USB ports are being used when you're flashing the phone?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Fastboot with Xperia XP
I have the same problem, can't get it to fastboot mode.
Tried the Windows 8 zith USB 2, and also on XP machine where I was succesfully used it for a Xperia U.
Dump Windows..
Opensource rules!!! I switch on a VM with Windows only when I need Photohshop. Otw, Ubuntu and openSUSE FTW!!
sarkar1990 said:
Dump Windows..
Opensource rules!!! I switch on a VM with Windows only when I need Photohshop. Otw, Ubuntu and openSUSE FTW!!
Click to expand...
Click to collapse
Opensource forever)))
Sent from my ME371MG using xda app-developers app
same problem...
m having same kind of problem i was trying to flash boot img from cm 11 but fast boot isnt recognizing my device any more.my sp is rooted bootloader unlocked.fast boot was recognizing it yesterday.please tell me what to do
What I did was use a Windows XP machine.
Couldn't get it to work on my Windows 7/8, because of the restrictions in driver signatures.
Sent from my C5303 using Tapatalk
fastboot
darkdemon32 said:
Hi guys, got a slight problem with entering fastboot mode. I hold the volume-up key and connect me USB cable but rather than getting the noise verifying it's been connected ok, I get that dull sound it makes when it hasn't worked. It won't even let me install the drivers and in device manager it comes up as "S1boot Fastboot" for a few seconds before then going into battery charging mode. .
Click to expand...
Click to collapse
I have a similar problem. the power light lights up blue then passes into the phone starts loading mode
Sorry for bad English
The updated version (09.14) don't work properly. It doesn't enable me to go to Flashmode. Uninstalled and used the previous version and it worked as it should, no issues entering Flashmode.
i might have actually found the solution. im on the 4.3fw build version 12.1.a.1.201... in my case, my pc will automatically install the drivers for mass storage giving me no chance to update the driver to the one from sony.
you need to do step 9. and 10. if you havent done so from http://unlockbootloader.sonymobile.com/instructions
what i did was allow developer settings and allow debugging via usb.
plug in and attempt to go in to fastboot and obviously it'll fail.
go to device manager. (control panel->hardware and sound->device manager) quickly scroll down go to other devices. you will see s1fastboot (or something like that) if you're quick enough, if not, in my case, the phone will go in to charging mode.
what i did was to disable xperia sp mass storage from disk drives category too.
right click on it and select update driver software and you will select the file you've unzipped (following step 9 and 10 sony's instructions).
after it has finished updating, unplug your usb and attempt to enter fastboot, it should work.
PS: im no expert, this solution might be out there somewhere already or it could just be a great coincidence. some of these steps might not be useful even.
Had this problem and found a funny solution: I switched my cable and the port I was using. Both Ubuntu and Windoze 7 failed on both fastboot and flash mode, even though in both the phone would charge. I grabbed a spare micro USB cable and plugged it into the front of the PC; voila. Now the phone is rooted and running the latest CM.
Need a final solution for this problem
I don't know what to do!!! The problem is this, very similar to the others mentioned above,: When i conect my xperia sp to fastboot mode, pressing volume up while plugging in usb cable, the phone led turns to blue for few seconds and than it just turns to red showing on the screen the battery image( normal charging mode)...... I' m using windows xp and a rooted xperia sp whit cm11 (for locked bootloader obviously). Just two last things:
the phone can be unlocked( I checked it) and fastboot worked the same as now with stock xperia sp firmware.
Please i need a final and a certain solution for this problem!!!
i'll be very thankful to anyone who give me a hand!!!!
TheTras said:
I don't know what to do!!! The problem is this, very similar to the others mentioned above,: When i conect my xperia sp to fastboot mode, pressing volume up while plugging in usb cable, the phone led turns to blue for few seconds and than it just turns to red showing on the screen the battery image( normal charging mode)...... I' m using windows xp and a rooted xperia sp whit cm11 (for locked bootloader obviously). Just two last things:
the phone can be unlocked( I checked it) and fastboot worked the same as now with stock xperia sp firmware.
Please i need a final and a certain solution for this problem!!!
i'll be very thankful to anyone who give me a hand!!!!
Click to expand...
Click to collapse
Are you trying to unlock your phone?
Have you installed device specific/fastboot/flashmode drivers via FlashTool? If you are on Windows 8/8.1, you need to disable driver verification to get it done.
Alternatively if you just wanna unlock your bootloader, you can use the BLU option in FlashTool. Again all drivers will need to be properly installed for your phone to be detected correctly.
You say you had the same problem with stock firmware which means you probably haven't setup adb/fastboot properly on your PC. Does your phone get detected correctly in Device Manager? Have you tried installing drivers via Device Manager?
....
So the solution is installing flashtool and installato drivers via Emma?? Thanks forma the attention!!
TheTras said:
So the solution is installing flashtool and installato drivers via Emma?? Thanks forma the attention!!
Click to expand...
Click to collapse
I meant install drivers via FlashTool. Go to C:\Flashtool\drivers or wherever you have installed Flashtool and run the Flashtool-drivers.exe.
Select flashmode drivers, fastboot drivers and common drivers viskan board (SP drivers) and install them. Like I said if you are on Win 8/8.1, you will have to disable driver signature enforcement. Just look it up in YouTube and follow a tutorial.
from this instruction
http://unlockbootloader.sonymobile.com/instructions
I;m stuck at 13.On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file. I cant install the driver eventhough I think I've done everything correctly
I've try both manually and automatically can someone help me please?I'm stuck for many hours now
Edit: My phone is XperiaTX (Lt29i) rooted lock bootloader JB4.1 with official rom and kernel
My PC in win8 x64
zzz017 said:
from this instruction
http://unlockbootloader.sonymobile.com/instructions
I;m stuck at 13.On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file. I cant install the driver eventhough I think I've done everything correctly
I've try both manually and automatically can someone help me please?I'm stuck for many hours now
Edit: My phone is XperiaTX (Lt29i) rooted lock bootloader JB4.1 with official rom and kernel
My PC in win8 x64
Click to expand...
Click to collapse
I recomend you to install flashtool and unlock the bootloader with it ("BLU") it is easier and faster,
To install the usb drivers I also got problems, do one thing this is how I got it to work.
connect the phone with fastboot button pressed, the PC will ask for drivers and will open the "new hardware assistant" do not allow it to install them automatically, do it manually and sellect the folder where you downloaded the drivers, in some point the phone will power off as it doesn´t get any response from PC (this is why it was not installing them properly in may case) just before pressing ok connect again in fastboot (and close the new prompt of "new hardware assistant" let the old one install the drivers and will do it properly.
Still have a problem with drivrer installation
I've try to install driver from.exefile in C:/flashtool/drivers
And I've done it with no error but I still cant install the"S1 Fastboot driver"
I dont know what to do so I try Unlock through Flashtool and I got this message(see the attached picture)
zzz017 said:
Still have a problem with drivrer installation
I've try to install driver from.exefile in C:/flashtool/drivers
And I've done it with no error but I still cant install the"S1 Fastboot driver"
I dont know what to do so I try Unlock through Flashtool and I got this message(see the attached picture)
Click to expand...
Click to collapse
You need to install the drivers after disabling driver signature enforcement in Windows 8. If I remember correctly, I got it working by just installing the Fastboot and TX drivers from Flashtool. I did it about a year ago, so I'm not sure if Flashtool can correctly unlock bootloader already (it couldn't when I did it), so I would suggest just using fastboot.exe the way it is described in the official Sony page.
By the way: are you sure your bootloader can be unlocked?
Mad Marty said:
You need to install the drivers after disabling driver signature enforcement in Windows 8. If I remember correctly, I got it working by just installing the Fastboot and TX drivers from Flashtool. I did it about a year ago, so I'm not sure if Flashtool can correctly unlock bootloader already (it couldn't when I did it), so I would suggest just using fastboot.exe the way it is described in the official Sony page.
By the way: are you sure your bootloader can be unlocked?
Click to expand...
Click to collapse
Sure:good:
Already unlocking the bootloader
from this thread >> http://forum.xda-developers.com/showthread.php?t=2095087
I recognize that I just forgot to tick the "Flashmode driver"and"Fastboot driver"
Hi guys,
I accidentally formatted /system on my T with UB.
Now it won't start (it says "Sony", then nothing happens). It now has no recovery and if I connect the phone in fastboot or flashmode, the usual PC I use to flash says me that "Sony ADB interface" is connected, but it can't find any driver.
What can I do now?
Thanks in advance for the reply.
DS-1 said:
Hi guys,
I accidentally formatted /system on my T with UB.
Now it won't start (it says "Sony", then nothing happens). It now has no recovery and if I connect the phone in fastboot or flashmode, the usual PC I use to flash says me that "Sony ADB interface" is connected, but it can't find any driver.
What can I do now?
Thanks in advance for the reply.
Click to expand...
Click to collapse
If it says "Sony ADB interface" when you connect it, then you don't need a driver, it's already installed (you can confirm this if you open Device Manager in Windows and check if it's listed as an "ADB interface" and there are no "Unknown Devices" and/or devices named in relation to your phone that have a yellow exclamation mark.
Just flash a stock FTF, or download one of the kernels for T that have a recovery, and flash any ROM you like.
First of all, thanks for the reply.
The strange thing about this time brick is that my pc doesn't recognize the phone. Other times, infact, I used it with the same phone to relive the Xperia T, after strange things happened.
Instead, this time the phone is recognized as "Sony ADB interface" and the pc says there's no driver in it. And it can't find in the system (I'm using an old laptop with Windows XP on it).
That's the reason why the system (and Flashtool, too: it says, in red, that I need to install the drivers for my phone) doesn't recognize the phone.
Now I'm trying the T into another Windows XP old laptop system...I hope it works (and I hope USB 1.1 will be fine, too...).
EDIT: this "new" pc see my phone, connected in fastboot mode, as "SEMC Flash Device" and it is installing the drivers. I've already installed fastboot/flashmode drivers from Flashtool Drivers folder.
RE-EDIT: PC can see the Xperia T, but Flashtool always says that it is connected in "flash mode", even if I connect it in fastboot mode. What should I do, now?
RE-RE-EDIT: The phone is recognized only in flashmode, even if I installed all the drivers. I'm trying to flash .141 and it seems to work. Let's see what happens.
Antiga Prime said:
If it says "Sony ADB interface" when you connect it, then you don't need a driver, it's already installed (you can confirm this if you open Device Manager in Windows and check if it's listed as an "ADB interface" and there are no "Unknown Devices" and/or devices named in relation to your phone that have a yellow exclamation mark.
Just flash a stock FTF, or download one of the kernels for T that have a recovery, and flash any ROM you like.
Click to expand...
Click to collapse
DS-1 said:
First of all, thanks for the reply.
The strange thing about this time brick is that my pc doesn't recognize the phone. Other times, infact, I used it with the same phone to relive the Xperia T, after strange things happened.
Instead, this time the phone is recognized as "Sony ADB interface" and the pc says there's no driver in it. And it can't find in the system (I'm using an old laptop with Windows XP on it).
That's the reason why the system (and Flashtool, too: it says, in red, that I need to install the drivers for my phone) doesn't recognize the phone.
Now I'm trying the T into another Windows XP old laptop system...I hope it works (and I hope USB 1.1 will be fine, too...).
EDIT: this "new" pc see my phone, connected in fastboot mode, as "SEMC Flash Device" and it is installing the drivers. I've already installed fastboot/flashmode drivers from Flashtool Drivers folder.
RE-EDIT: PC can see the Xperia T, but Flashtool always says that it is connected in "flash mode", even if I connect it in fastboot mode. What should I do, now?
Click to expand...
Click to collapse
Ok, well, no idea about it being stuck in flash mode, but, isn't that exactly what you want? To flash a stock FTF you need to be in flash mode. As a matter of fact, you can even flash only the kernel of an FTF in flash mode, it wouldn't have a recovery, since it would be a stock kernel, but at least you could get a working kernel, if that were the issue, which it is not.
What are you doing to put your phone into fastboot mode?
I wanted to use fastboot to flash a kernel with recovery and then flash the backup of my old ROM.
However, it doesn't worked. Only flashmode worked. So I flashed (really slowly, because of USB 1.1 ports of this old IBM laptop!) .141 and now the phone is living again.
Dunno why fastboot didn't work. Maybe because there wasn't any firmware on?
Antiga Prime said:
Ok, well, no idea about it being stuck in flash mode, but, isn't that exactly what you want? To flash a stock FTF you need to be in flash mode. As a matter of fact, you can even flash only the kernel of an FTF in flash mode, it wouldn't have a recovery, since it would be a stock kernel, but at least you could get a working kernel, if that were the issue, which it is not.
What are you doing to put your phone into fastboot mode?
Click to expand...
Click to collapse
DS-1 said:
Dunno why fastboot didn't work. Maybe because there wasn't any firmware on?
Click to expand...
Click to collapse
No because the whole point of fastboot mode is to be able to flash firmware related files. Fastboot mode, just as Flash mode, starts before the Android OS starts. If they depended on there being an OS installed it would defeat the whole point.
So I really dunno why it didn't work. Later I'll try to see if now fastboot is working again.
Antiga Prime said:
No because the whole point of fastboot mode is to be able to flash firmware related files. Fastboot mode, just as Flash mode, starts before the Android OS starts. If they depended on there being an OS installed it would defeat the whole point.
Click to expand...
Click to collapse
When you don't have a ROM installed,stock kernels recovery won't work. Flash CM 11s Kernel, you'll have recovery then restore you're backup