Hey, I'm having trouble getting my phone recognised in Fastboot mode. I can get to the bootloader, but Windows 7 64 bit doesn't recognise it. And -- I think this is important -- I don't see the USB Control Init/USB Control Init End messages which usually appear when it's connected. Added to that, the Vol Up/Down keys don't work in Fastboot, but they do work in recovery and when ICS is running.
I've tried most, if not all, of the guides on Fastboot with Windows 7 64 bit. Yes, I've tried using the PdaNet drivers and all that. It used to work before, even without the PdaNet drivers.
All the symptoms are:
- Vol Up/Vol Down don't work in the bootloader. They do work in stock recovery and when the OS, ICS, is running.
- No USB Init messages appear at the bottom of the bootloader screen when the phone is connected to the PC (Win7 x64).
- Not recognised even PDANet drivers. adb devices lists the device, fastboot devices doesn't list the device, and fastboot flash recovery recovery.img says <Waiting for Device>
- i9020T with ICS 4.0.3 (Stock)
Any help would be great, thanks guys/gals.
Related:
My phone fell from a desk about waist height and now the Power Button doesn't work. Trying to get Fastboot working so I can install a ROM with Volume Wake since I'm running stock.
I'm having this EXACT same problem. Someone please help!
I'm also have this issue. Any help would be great
Tom Foolery said:
I'm also have this issue. Any help would be great
Click to expand...
Click to collapse
Same issue here.
Has someone solved?
Sorry guys/gals, I didn't manage to get it resolved. I ended up getting a Galaxy Nexus.
Related
hi there.
maybe I am using wrong words but I cannot find any post similar to my subject.
I am on stock ICS but it is not working well - I wanted to downgrade, but it looks like it is not possible to downgrade on stock recovery. I know I have to change the recovery to sth else like ClockWork.
I know about fastboot way - and here my problems starts.
I have all the drivers, phone is visible in Device Manager while it is booten into Android. I can go into Fastboot mode BUT
when phone is in fastboot mode it is not visible in Windows Device Manager at all.
It is not a driver problem. There is no new device I can use the driver for.
I tried different computers. Win7 64bit and 32bit and WinXP 32bit
My phone does not show up on any of them.
I think it ia a problem with the bootloader - my current version is XXKL1 - as when I am in the fastboot mode my volume keys are not working, while they work perfectly well in recovery or in the OS.
Any ideas appreciated.
Cheers
My phone wasn't showing in w7 i had turn on usb debugging in settings -> developer options. I m not sure if this helps but might be worth a try
Sent from my Nexus S using Tapatalk
Thx gm'
It is not an issue for me to connect to Windows when I am booten into android.
Only when I am in fastboot mode the phone is not discovered by windows - and in fastboot mode thre is no USB debbuging - but thx anyway
..
vstar said:
Thx gm'
It is not an issue for me to connect to Windows when I am booten into android.
Only when I am in fastboot mode the phone is not discovered by windows - and in fastboot mode thre is no USB debbuging - but thx anyway
Click to expand...
Click to collapse
Know what u mean.
Windows finds u phone but not in recovery mode.
Download pdanet for android and this will solve ur problem buddy.
http://junefabrics.com
I just realize that what I done a while ago.
You don't need install pdanet app on ur phone as long u have drivers u might get some errors if u press not install but will work anyway.
Hope this will help.
Sent from my Nexus S using Tapatalk
XXK1 sounds like the baseband/radio to me. Granted I never actually looked in the bootloader for a model number. You sure that's not the radio?
What rom is on the phone now? Does it work? Are you rooted? If you got working phone with root you can flash custom recovery from inside the os. Boot directly into it via terminal or adb or any app that does it.
The volume buttons not working sounds odd and does worry me though
did you try to boot into bootloader/fastboot without being connected to any machine (holding vol up + power) to check if your volume keys work or not?
your issue might not be driver related, but you can always try if the test above was ok.
http://forum.xda-developers.com/showthread.php?t=1138755
best of luck
OK guys. I am on 4.0.3 stock. Works almost fine. This phone is unlocked but not rooted. So no chance for any other recovery but the stock one as far as I know. So I am not able to downgrade easily. Yes I can boot into fast boot without being attached to USB. Volume keys still not working here. But working in recovery mode no problem. GM no drivers will help if phone does not show in windows device menadzer at all. I have tried Linux approach but it looks phone is not being discovered there in fast boot mode as well. I have tried unbrick software - does not discover the phone.
And yes it says on fast boot screen boot loader : I9020XXK1
I have run out of ideas.
Downgrade would be best but how to put any recovery manager without root privileges
Sent from my Nexus S using XDA App
you can use ROM manager to jump back to 2.3.x
..
I am not rooted so I cannot use from manager and I do have stock recovery not clockwork so I cannot install superuser.zip
Sent from my Nexus S using XDA App
And for SuperOneClick phone needs to be visible in fastboot mode.
Sent from my Nexus S using XDA App
vstar said:
And for SuperOneClick phone needs to be visible in fastboot mode.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
for SuperOneClick phone needs to be visible in usb debugging mode.
Sorry mate but it only starts in USB Debug/Android mode - then it reboots the phone to fastboot shell and then same issue - phone is not discovered by windows hence nothing else happens.
Is there no other way of gaining root access instead of fastboot option - this would solve all my pains
Thx everyone for input
..
i suggest just follow zedomax tutorial on how to root your ics phone. He also have the download links for all the files that you will need. once your phone is rooted then you can download the old stock version of your phone.
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
Looks like a driver issue, when phone isn't discovered by windows in fast boot mode. (You are booting with vol up+power, right?)
Forget about any one-click-stuff etc - unlocking and cwm is the way to go. Everything else just makes troubles.
What I don't get is how you unlocked your phone without fastboot working?! That's not possible... for the moment forget about rooting - superuser isn't needed to flash stuff via fastboot/cwm.
Concentrate on getting fastboot to work. After that it's a piece of cake. Check you have drivers and fastboot set up properly on your PC.
Edit:
By this I mean following the sticky-guides, using the sdk from Google (not any downloads pretending to make it quick'n'easy. Go the official way!)
You should also give the 4.0.4-stockrom (ported from ns4g-leak) a try - it's way better than 4.0.3!
Edit: talking about this one: http://forum.xda-developers.com/showthread.php?t=1474878
OK guys - I have no idea how should I say it in different way - this is not a matter of a driver - the phone is physically not visible to the computer. There is no unknown device of anykind so I have nothing to use a driver for. It is not that fastboot command does not recognize the phone - the phone does not exists in Windows Device Manager. Looks like when phone is in fastboot mode the usb port is dead. So no chance of rooting in standard way.
And I have unlocked it as it was working before. I did realize it is not working when I tried to downgrade recently.
Election Day: I have tried 3 different cables, couple of computers and 3 different operating systems - ubuntu included. How this trick with hairdrier works? If it is a flash why does it work for everything else but not fastboot mode? Should I heat it up without cover and battery? Any specific area? Should I plug in while hot?
Thx guys.
usb working with sys booted up, but broken on bootloader?! makes no sense at all, i hope you can see that for yourself. can't be a hw-failure (then it would be broken everywhere).
have you reinstalled the driver from the sdk? the problem is on your pc, not the phone...
and forget about rooting for the moment, you don't need that to flash a rom. or are you mixing things up?!
that nonsense about heating up the phone with a hair drier was a joke, right?
..
Hi guys,
i have a tricky problem.
I bought a used nexus S, without any hope to recover it.
This is the state at the moment (after installed SDK and drivers).
I think the device is in his standard state (all locked up, never rooted, stock rom)
It boot up and ask for a password to encrypt device (works : volume and emergency call).
If i connect usb, he tries to mount USB storage but he dosen't success.
I connect to pc and pc see an Android ADB device in the devices list.
BUT if i lauch 'adb devices' i dont see anything.
I start it in bootloader mode (Vol Up + Power) ... it starts.
BUT Vol Up and Vol down didn't work. I can only press power and return again in bootloader. (volume work if i normally boot)
In bootloader state i tried 'fastboot devices' and i didn't see any device.
So the state is :
Bootloader i think "broken" (volumes dosen't work and fastboot dosen't see device)
Debug usb disabled (adb don't see my device)
Device encrypted
Any idea ?
I think is a nice problem to let your brain works on :laugh::laugh:
Thanks in advice.
Daniele
Hey guys, there is anybody out there ?
I dont think that no one could try to solve this problem.
Thanks
Do you have the drivers installed onto your PC? You will need to get the adb drivers and fastboot drivers. Download Samsung Kies and that will take care of your ADB drivers. Click here: http://www.mediafire.com/download/5a7gou9droidi53/drivers.rar for your fastboot drivers. Hope this helps.
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
sirhaplo said:
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
Click to expand...
Click to collapse
I'd suggest just booting Linux and doing whatever you need to do in there.
The kernel already supports communicating with the Nexus S, no need to mess with drivers like on Windows.
Similar questions to this have been asked before but got no replies so, in desparation, am asking again.
Bought my phone second hand. On starting, it shows the Vodafone logo so assume it's branded.
About Phone -> Software Information shows:
Android Version: 2.3.5HTC Sense version: 3.0Software number: 2.10.161.5
HBOOT shows:
*** UNLOCKED ***SAGA PUT SHIP S-ON RHHBOOT-2.00.0002
Now for the problem:
I'm trying to set S-OFF and root the phone but my PC, running Windows 10, is unable to communicate with the phone when it's in Recovery mode.
The entry for My HTC under Android USB Devices in Device Manager disappears once I start the phone in Recovery mode and connect it to my PC via a USB cable.
At this point Device manager on my PC shows under USB Controllers an entry for an unknown USB Device (Device failed enumeration) and the Hardware Ids show as USB\UNKNOWN.
I'd really appreciate someone familiar with this area throwing some light on what could be going on here and perhaps giving me some pointers on how to resolve this.
there is one quick fix http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337 (for me it worked with the old win 10)
if it doesnt work: the fastest way is to seek a friend with windows 7 and s-off the bootloader
if its s-off you dont need the "fastboot" mode
here is an tutorial http://forum.xda-developers.com/htc-desire-s/general/installing-cm13-untouched-htc-desire-s-t3456585 if you have luck it works with your win 10 too
IMPORTANT: DO NOT UPDATE TO ANDROID 4.0.4 IT KILLS THE POSSIBILITY TO S-OFF YOUR PHONE
Layer_DE said:
there is one quick fix http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337 (for me it worked with the old win 10)
if it doesnt work: the fastest way is to seek a friend with windows 7 and s-off the bootloader
if its s-off you dont need the "fastboot" mode
here is an tutorial http://forum.xda-developers.com/htc-desire-s/general/installing-cm13-untouched-htc-desire-s-t3456585 if you have luck it works with your win 10 too
IMPORTANT: DO NOT UPDATE TO ANDROID 4.0.4 IT KILLS THE POSSIBILITY TO S-OFF YOUR PHONE
Click to expand...
Click to collapse
Thanks for replying but, following the links you gave they all ended with a brick wall. Using VirtualBox I tried using Window 7 and even Windows XP. All attemprt failed miserably.
In all cases Device Manager showed the MyHTC driver installed under Androis USB Devices and working normally. Running command 'adb devices', when the phone was running normally, worked fine but USB connection is lost every time when booting into HBOOT, making fastboot etc impossible.
I've reached the point where I can't waste any more time on this having wasted far too much already. I don't like giving up but this has got me.
bacoms said:
Thanks for replying but, following the links you gave they all ended with a brick wall. Using VirtualBox I tried using Window 7 and even Windows XP. All attemprt failed miserably.
In all cases Device Manager showed the MyHTC driver installed under Androis USB Devices and working normally. Running command 'adb devices', when the phone was running normally, worked fine but USB connection is lost every time when booting into HBOOT, making fastboot etc impossible.
I've reached the point where I can't waste any more time on this having wasted far too much already. I don't like giving up but this has got me.
Click to expand...
Click to collapse
the problem is simple on a windows hosted vm usb passthrought doesnt work with unknown devices
Layer_DE said:
the problem is simple on a windows hosted vm usb passthrought doesnt work with unknown devices
Click to expand...
Click to collapse
If I can drum up any enthusiasm to continue, I'll try and borrow a PC running Windows 7 and try again.
Hello
I need help with my TF700.
I had this tablet for some time. It was unlocked with TWRP and ZOMBI-POP.
Last week I wanted to upgrade it for KIT-Kass 7.1
I wanted to update my TWRP for kang wersion ( 2.8.7.4) through TWRP and during the process it rebooted.
Then I've got a bootloop on normal starting. I can't get into recovery mode through power + vol up - tablet has no respond for that
I can only go to fastboot through power + vol down but when I connect it to windows with adb drivers or to linux(FWUL) it sees no device and no respond for any command.
Do You have any idea what to do ?
Thank You in advance
Sorry to say this but, if you can't send it commands then you are most likely hard bricked. What OS are you running on the computer with fastboot on it? - NP
Nektopoli said:
Sorry to say this but, if you can't send it commands then you are most likely hard bricked. What OS are you running on the computer with fastboot on it? - NP
Click to expand...
Click to collapse
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
marmacapp said:
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
Click to expand...
Click to collapse
Do you have access to a Windows 7 computer/laptop. There's an issue with Windows 10 and the fastboot drivers not working together, and causing a problem like yours. - NP
marmacapp said:
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
Click to expand...
Click to collapse
Found this in another thread, windows 10 fix. - NP
"I used Windows 10 and had to disable driver signature enforcement. Once I did this the PC recognized the tab without issue. "
To disable;
http://www.thewindowsclub.com/disable-driver-signature-enforcement-windows
Thank You for the info, but I have laptop with Windows7 and still the same.
But if I have text on screen like this Starting fastboot USB download protocol can the device still be hard-bricked ?
Maybe I am missing some drivers ?
I would d/l Minimal ADB and Fastboot from here;
https://forum.xda-developers.com/showthread.php?t=2317790
and Universal_Naked_Driver_0.72 here; - NP
https://forum.xda-developers.com/showthread.php?t=2263822
For now the problem is I can not install the "naked driver" because devices manager can not see TF700 when it is connected, so I can't update the driver
Have you tried sending the [fastboot reboot] command to see if the tablet will reboot. When I bricked my TF201t my laptop didn't see it but it still took the commands allowing me to wipe the recovery partition and install the correct TWRP. - NP
Dear Guys
I know that this topic is quite old, but I am still fighting with this problem.
I tryied different drivers, 3 different computers ( two with windows 10 one with windows 7) and I can;t connect to fastboot.
The tablet is in this mode, but when I will use adb and type any command like fastboot reboot - it displays "waiting for device"
Do You have any idea what else can I try ?
Best regards
Hi,
me too! I was using it at lunch - no problem. Got home and turned it on and unrecoverable bootloader error.
if this has been asked before, i'm sorry, i have searched all over and no one seems to have my problem.
tablet boots to twrp splash, vol down and power does not work. i cant get it into any other modes because windows 10 does not see that it is connected.
i found a guide to inturupt twrp, but windows cant see my device.
tried dual booting windows 7, still cant see device
tried linux distro, adb still says no device found.
even with drivers installed in guessing that while in twrp splash it doesn't show up that there is a device connected.
is there anything i can do? or is it curtains for the ol' transformer?
thanks in advance.
Try booting to the fastboot screen before you boot into TWRP and see if the Windows 7 system can see the tablet, also what program are you using on the PC to access/flash the tablet? - NP
power and vol up don't do anything sadly, it still goes to the twrp splash screen.
I was using ADB on 10, 7 , and on the linux distro.
Try d/ling this Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790 on a Windows 7 system and see if that will pick it up. - NP
still says no devices found. I think i really messed it up this time
kingkoopa85 said:
still says no devices found. I think i really messed it up this time
Click to expand...
Click to collapse
With it hooked up try sending it the reboot command and see if it responds. - NP
fastboot reboot
or fastboot reboot-bootloader
no luck, it says waiting for devices and it just sits there. i miss this tablet.
i think the problem is still that when stuck in twrp the computer doesnt recognize that its there, so I cant get the drivers installed to be able to run any commands.