Hi
I have got a hero on the cheap currently using an iPhone boot looking to move over.
The hero has a custom rom on it, I would liketo try others. Holding down the home button and powering on just leaves it with the G2 boot screen. Holding down back button and power brings me into fastboot USB. When connected to the mac I am unable to see the device / list it using adb devices. If I boot into the os and connect to the mac not mounting the sdcard I can see the device with adv devices.
I'm trying to install a recovery image, this is proving dificult with not seeing the device in fastboot.
Has anyone any thought/suggestions on to resolve? Or point me in the direction of some threads to read.
Tia
deano
use fastboot devices when in fastboot...
HI,
thanks for the reply, when in fastboot on the device I use fastboot which i have downloaded from the andriod site and put in my "tools" folder when trying to lash a recovery image it just comes back with a prompt saying "waiting for device"
thanks
just to make sure: you turn off the phone, then turn it on again while holding down BACK. this brings you to a screen with a white background and fastboot written somewhere. then you plug in the usb cable and execute "fastboot devices". if it still doesn't recognize your device then you got a problem somewhere, no idea where though. not sure if windows needs drivers or anything for fastboot to work correctly...
Yes that's correct.
Phone is recognize in everything other than when connected by fastboot.
Thanks for your input
I was having some SD card issues, as far as not being able to delete files from my sd via root apps, getting errors when trying to make back ups via my back-up pro/titanium so i was point to this thread http://forum.xda-developers.com/showthread.php?t=1670824. I read all instructions(as always) and already had a working ADB in recovery and fastboot, so i flashed that zip and my Windows7 pc no longer recognises my Prime.
So no im stuck with no OS on my prime, Only twrp-Touch recovery and no access to push any files to prime via fastboot or ADB.
i have the naked drivers and all.
so i was thinking that i would try to use Ubuntu,, but i need to aet up adb/sdk on this prior to that.
But i was reaching out to see if anyone had some fix/help to get my prime running??? i have never bricked a device, but im starting to feel like this is a sort of "soft" brick... lol
http://forum.xda-developers.com/showthread.php?t=1670824
Just the same thing
jyarborough said:
I was having some SD card issues, as far as not being able to delete files from my sd via root apps, getting errors when trying to make back ups via my back-up pro/titanium so i was point to this thread http://forum.xda-developers.com/showthread.php?t=1670824. I read all instructions(as always) and already had a working ADB in recovery and fastboot, so i flashed that zip and my Windows7 pc no longer recognises my Prime.
So no im stuck with no OS on my prime, Only twrp-Touch recovery and no access to push any files to prime via fastboot or ADB.
i have the naked drivers and all.
so i was thinking that i would try to use Ubuntu,, but i need to aet up adb/sdk on this prior to that.
But i was reaching out to see if anyone had some fix/help to get my prime running??? i have never bricked a device, but im starting to feel like this is a sort of "soft" brick... lol
http://forum.xda-developers.com/showthread.php?t=1670824
Click to expand...
Click to collapse
Hey man, exactly the same thing happend to my tf201 a couple of days ago. Since then i've been trying everything found on different treads and forums with no luck.
Actual State:
-Able to boot to TWR and to fastboot
-I can connect via ADB in Recovery mode and push small files but not large files (like a ROM)
-When connected via ADB in Fastboot mode my device is detected by windows7 but when adb devices is issued returns Error: device not found
At this point a little hand would be appreciated..
L-MachO said:
Hey man, exactly the same thing happend to my tf201 a couple of days ago. Since then i've been trying everything found on different treads and forums with no luck.
Actual State:
-Able to boot to TWR and to fastboot
-I can connect via ADB in Recovery mode and push small files but not large files (like a ROM)
-When connected via ADB in Fastboot mode my device is detected by windows7 but when adb devices is issued returns Error: device not found
At this point a little hand would be appreciated..
Click to expand...
Click to collapse
When you're in fastboot, you can't access your device with ADB. Try "fastboot devices" and it should show up there.
These are the steps I took when I was stuck at the splash screen with only access to fastboot. If you have access to fastboot (by holding volume down + powering on, then choosing fastboot/usb icon) then you should be able to fix it.
geo.z said:
When you're in fastboot, you can't access your device with ADB. Try "fastboot devices" and it should show up there.
These are the steps I took when I was stuck at the splash screen with only access to fastboot. If you have access to fastboot (by holding volume down + powering on, then choosing fastboot/usb icon) then you should be able to fix it.
Click to expand...
Click to collapse
thanks for that. i was able to get into fast boot,, but since my pc would not see my tab,, no commands can be given. so i am now setting up adb on ubuntu 12.4, and seeing if i get a fresh start can i get access. i amd following Xsmagical on this on over here
http://forums.team-nocturnal.com/showthread.php/773
geo.z said:
When you're in fastboot, you can't access your device with ADB. Try "fastboot devices" and it should show up there.
These are the steps I took when I was stuck at the splash screen with only access to fastboot. If you have access to fastboot (by holding volume down + powering on, then choosing fastboot/usb icon) then you should be able to fix it.
Click to expand...
Click to collapse
That's right geo.z but now I'm trying "fastboot devices" and it returns nothing, not even an error, my windows device manager keeps recognizing the device as "ASUS Android Bootloader Interface" and I'm using the Naked Driver.
L-ManchO, that's weird. Try uninstalling the drivers, disconnect the device and then reconnect and reinstall the naked drivers.
jyarborough, have you tried using the Universal Naked Drivers? I also had the problem of not being able to see the device, but uninstalling drivers and installing the new ones worked for me.
geo.z said:
L-ManchO, that's weird. Try uninstalling the drivers, disconnect the device and then reconnect and reinstall the naked drivers.
jyarborough, have you tried using the Universal Naked Drivers? I also had the problem of not being able to see the device, but uninstalling drivers and installing the new ones worked for me.
Click to expand...
Click to collapse
I just did as you suggested and now windows sees the device as "ASUS Fastboot Interface", anyways the "fastboot devices" returns nothing as before, I tried the "fastboot -i 0x0b05 flash recovery twrp.blob" and I get the following message:
On the computer side:
sending `recovery` (5876 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5.054s
At the same time On the TF201 I get:
Failed to process command download:005bd068 error(0x120003)
L-MachO said:
I just did as you suggested and now windows sees the device as "ASUS Fastboot Interface", anyways the "fastboot devices" returns nothing as before, I tried the "fastboot -i 0x0b05 flash recovery twrp.blob" and I get the following message:
On the computer side:
sending `recovery` (5876 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5.054s
At the same time On the TF201 I get:
Failed to process command download:005bd068 error(0x120003)
Click to expand...
Click to collapse
Try a different USB port? Maybe a different computer? It's possible that this is a hardware problem, hopefully it isn't the cable or the port on the TF201.
geo.z said:
L-ManchO, that's weird. Try uninstalling the drivers, disconnect the device and then reconnect and reinstall the naked drivers.
jyarborough, have you tried using the Universal Naked Drivers? I also had the problem of not being able to see the device, but uninstalling drivers and installing the new ones worked for me.
Click to expand...
Click to collapse
i have . i am starting fresh with ubuntu,, not window,, and so far im ok..well on my way. fast boot can see my tab
L-MachO said:
I just did as you suggested and now windows sees the device as "ASUS Fastboot Interface", anyways the "fastboot devices" returns nothing as before, I tried the "fastboot -i 0x0b05 flash recovery twrp.blob" and I get the following message:
On the computer side:
sending `recovery` (5876 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5.054s
At the same time On the TF201 I get:
Failed to process command download:005bd068 error(0x120003)
Click to expand...
Click to collapse
are you putting this " -i 0x0b05 " after you type fastboot?
L-MachO said:
I just did as you suggested and now windows sees the device as "ASUS Fastboot Interface", anyways the "fastboot devices" returns nothing as before, I tried the "fastboot -i 0x0b05 flash recovery twrp.blob" and I get the following message:
On the computer side:
sending `recovery` (5876 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5.054s
At the same time On the TF201 I get:
Failed to process command download:005bd068 error(0x120003)
Click to expand...
Click to collapse
Any luck
Sent from my ice cream sandwich
geo.z said:
Try a different USB port? Maybe a different computer? It's possible that this is a hardware problem, hopefully it isn't the cable or the port on the TF201.
Click to expand...
Click to collapse
Tried on a different computer (desktop) running win7 x64, used the Naked Drivers, device reported as "ASUS Fastboot Interface", after running "fastboot devices" nothing came up and for the "fastboot -i 0x0b05 flash recovery" got the same message as before.
Now I'm really worried
Interesting thread in case you're still facing issues:
http://forum.xda-developers.com/showthread.php?t=478820
The people there solved using different methods:
1. USB cable with ferrite core on both ends
2. different USB port
3. using USB deview to uninstall all usb drivers, and install one by one, as Windows is notorious for installing drivers over and over for each USB hub, eventually causing conflicts
4. plugging in the usb only after issuing the fastboot command, and having the command prompt say "waiting for phone"
I hope you get things working.
kokopuphz said:
Interesting thread in case you're still facing issues:
http://forum.xda-developers.com/showthread.php?t=478820
The people there solved using different methods:
1. USB cable with ferrite core on both ends
2. different USB port
3. using USB deview to uninstall all usb drivers, and install one by one, as Windows is notorious for installing drivers over and over for each USB hub, eventually causing conflicts
4. plugging in the usb only after issuing the fastboot command, and having the command prompt say "waiting for phone"
I hope you get things working.
Click to expand...
Click to collapse
Great suggestions kokopuphz, here's the summary of each step:
1. USB cable with ferrite core on both ends
I used ferrite cores adapters (from a local electronics shop) on both ends of the USB cable to reduce transmission noise, but got the same message when sending the recovery
2. different USB port
I even used a different PC with a brand new installation of windows 7 (same situation)
3. using USB deview to uninstall all usb drivers, and install one by one, as Windows is notorious for installing drivers over and over for each USB hub, eventually causing conflicts
I assume step (2) would cover this one.
4. plugging in the usb only after issuing the fastboot command, and having the command prompt say "waiting for phone"
Same messages received with after this step.
I'm thinking of a USB cable issue here, what do you think guys?
Sounds likely. Got a spare microUSB cable?
Yeah, the only common denominator would be the usb cable and tfp, thus likeliness of the cable being an issue could be high. I take it you've tried both docked and undocked?
Sent from my SO-01C using xda app-developers app
kokopuphz said:
Yeah, the only common denominator would be the usb cable and tfp, thus likeliness of the cable being an issue could be high. I take it you've tried both docked and undocked?
Sent from my SO-01C using xda app-developers app
Click to expand...
Click to collapse
Well I only have the tablet not the docking, so I'm stock with the USB cable probability at this point. I'm ordering one on Amazon, I guess an original one is my best be.
:crying: OMG how I miss my TF.
OK.. so I'm back up and running. What I had to do was to put the. Blob file in the same folder as adb to shortened the path. Once I got the path command right this is what I types
Adb push /your rom.blob /data /media /
At first I was pushing to /sdcard/ and the prime did not see it. I read through the op and saw the suggestion to push it to data media so I did.. did a manual reboot into twrp recovery and navigated to SD card where I saw my rom waiting there for me
Fastboot method would not work for me so I updated my drivers and did it all adb
Sent from my Transformer Prime TF201 using Tapatalk 2
It's Alive!!!!!
jyarborough said:
OK.. so I'm back up and running. What I had to do was to put the. Blob file in the same folder as adb to shortened the path. Once I got the path command right this is what I types
Adb push /your rom.blob /data /media /
At first I was pushing to /sdcard/ and the prime did not see it. I read through the op and saw the suggestion to push it to data media so I did.. did a manual reboot into twrp recovery and navigated to SD card where I saw my rom waiting there for me
Fastboot method would not work for me so I updated my drivers and did it all adb
Sent from my Transformer Prime TF201 using Tapatalk 2
Click to expand...
Click to collapse
Guys, I just received a new USB cable yesterday and tried once again, guess what? It WORKED..now I have my TF running like a charm once again.
Definitely the stock USB cable is a little too fragile and of course it's unbelievable all the error codes and messages I got because of a damaged cable.
Thanks a lot guys for your support and suggestions.
Kind of off topic but has anyone used Goo Manager to flash twrp over CWM?
Sent from my SCH-I535 using xda premium
Downloaded and installed ADB. Following tutorial here:
https://www.xda-developers.com/nexus-6p-bootloop-fix/
Specifically:
- Connect your smartphone or tablet to your computer with a USB cable. Change the USB mode to “file transfer (MTP)” mode. Some OEMs may or may not require this, but it’s best to just leave it in this mode for general compatibility.
- In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices
- On your phone’s screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you never want to see that prompt again).install adb
- Finally, re-enter the command from step #6. If everything was successful, you should now see your device’s serial number in the command prompt. Yay! You can now run any ADB command on your device! Now go forth and start modding your phone by following our extensive list of tutorials!
https://www.xda-developers.com/install-adb-windows-macos-linux/
I did all the above. But don't see anything from:
C:\ADB>fastboot devices
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
Nexus 6P was plugged into the USB cable on Win10 machine. Am in MTP mode. Most recent Google USB drivers installed.
I have done OEM Unlock in setup|Developer options. I have also turned on USB debugging in same options.
I am [obviously] lost. Anyone know what else I might try?
OK, I have made a little progress messing around on my own. It seems that running from the CMD line in Win 10, ADB command works but Fastboot does not. WHY? Bith are in the same directory.
If I type Fastboot by itself, then I get a list of the associated parameters, which means that the CMD system DOES recognize the Fastboot command.
Now, if I run CMD====> "ADB devices", it looks like my device is recognized and attached (that is my serial# below).
But if I try CMD=====> "Fastboot devices", as the instructions require, I get nothing. And if I try to run the flash job via Fastboot, that does not work either.
==================
C:\ADB>adb devices
List of devices attached
8XV5Txxxxxxxxxxx device
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
===================
Wondering if I need to install the Android SDK on Windows for this process to work?
I Think You need to Redo The process from Step One.
I Heard about This and Never Did An OTA.
If it Persists Try Using A Different PC and If After That It doesn't work Then Yes Android SDK is The last Option.
Sent from my Nexus 6P using Tapatalk
Solved. I needed to add the ADB install directory to the environmental path. Don't quite understand why, but doing so allowed me to get the problem fixed.