Develop Bugs

[Q] Help with ADB....Question

I am trying to get ADB to work so I can do the unlock bootloader. ADB recognizes my phone while booted up with usb debugging enabled, but when I reboot to fastboot, it does not recognize it.
I've tried different drivers, uninstalling and reinstalling.... no luck.....
Is there anyone that is knowledgeable in this area to assist me? Is there any kind of IRC channel available to get real-time answers?
Please help,
Thanks,
Bob

i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.

diablonyc2 said:
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
Click to expand...
Click to collapse
Yeah, im on 7 64 bit also..... i've tried disabling digital driver thing at bootup...
device manager see its just fine.... I can access it with adb while the phone is booted up.... as soon as I reboot to fastboot screen the phone cannot be seen by adb devices..... still shows up just fine with no ! in device manager....
... is there anyway to push a stock image and load a factory stock image from the stock recovery? says it needs to be in /cache folder.... i tried pushing a stock image there but it tells me access is denied.... i tried enabling root.... says root not available on production builds..... im lost....

I just tried it on my xp machine and it worked just fine..... weird.. something with 7 64 bit? i tried pda net drivers, samsung, samsung naked 1.7.... all said they were working fine....

adb is for android or recovery
fastboot is for bootloader
adb won't recognise the device when it's in fastboot mode.
Try:
Code:
fastboot devices
And you don't need adb to unlock the bootloader, the command is:
Code:
fastboot oem unlock
So not entirely sure why you're chasing adb...

I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit

j1mmyg88 said:
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
Click to expand...
Click to collapse
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.

copkay said:
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
Click to expand...
Click to collapse
fyi - this is what I did, with 64 bit windows 7 - the driver install didn't complete 'til I actually connected the GN in fastboot mode, then win7 installed the driver and I was able to run fastboot successfully.

help did I brick my phone?

All,
I have a big problem. When I try to start my phone I get the black screen with google and the unlocked padloack, after which the screen goes dark and nothing happens anymore.
What I did before this are two things. I had been mukking around with the screen resolution (I had it set at 240 and 280, as some apps did not show up in the market) also downloaded LCD density to solve the market issue.
I then rebooted the device and entered CWM to do a backup which as far as I knew succeeded. unfortunately after rebooting, see the above.
I have tried a couple of reboots, tried restoring the nandroid (the above was the only one I had). that didn't work, so tried to connect to the PC to load a new ICS rom (original 4.0.4 by google), unfortunately my device can not go into USB mode in CMW (it comes up with UMS lunfile missing....)
so I am woring in circles. can't start the device to download a rom, can't open USM to load a ROM to start the device again.....
any help would be appriciated
thanks
Patrick

hey
flash a new ROM via fastboot then, there are enough guides
-Syn
Edit: Alternatively, flash the stock Google ROM via GNex toolkit and go from scratch.

as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?

pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
Click to expand...
Click to collapse
To flash stock images the files are on your PC, not the phone.
If you can get the phone to boot into fastboot (via vol up + vol dn + power) and get your PC to recognize it you're good to go.

thats the issue. pc cannot recognize the phone, so cannot get any files from the PC to the phone (ie. cannot get a rom file to the phone...)

pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
Either directly from Samsung or download the GNex Toolkit (You might want to use it anyways to flash the stock image), the drivers come with it.
After you installed the drivers and have you phone plugged in, go to the device manager to check if it is connected properly.

pwvandeursen said:
[snip]
thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.

pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
I had a similar issue with regard to my PC recognizing the drivers. I googled around and found that people were having success with installing the PdaNet drivers, so maybe you can try that too. I had installed the Android SDK as well as the PdaNet drivers, and I eventually got mine to work.
I would probably follow Efrant's links first though - if that doesn't work for you, then maybe you can try PdaNet drivers and/or installing the SDK.
Good luck.

Why not just do a factory reset from within recovery?
¢ £®0π π€XU$ |||

the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.

pwvandeursen said:
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
Click to expand...
Click to collapse
Good to hear you got it.

Fastboot does not work but ADB does

Hey guys,
The power button on my phone stopped working this morning (without water damage). I'm preparing the phone to return to Samsung warranty, and in the process of reseting to stock and re-locking the OEM I noted that the phone does not respond to fastboot commands in the bootloader despite this working on the same system a week ago, no change in drivers or anything else. I installed PDAnet, still broken on Win 7 although I can reboot with adb.
I then tried this on OSX, again I can reboot with ADB, but the phone is unresponsive in fastboot.
I have three working hypotheses and I'm hoping someone can help me:
a) in some process of flashing my phone and being an uninformed n00b maybe I flashed something I shouldn't have or used some combination of partial fastboot flashes I shouldn't have. has this happened to anyone else?
b) whatever hardware damage knocked out the power button might have partially knocked out the bootloader
c) I just have really bad luck with driver set up and I just happened to mess up two different computer driver configurations but the phone is fine. to this end, I am setting up another Win 7 system fresh on a virtual drive as I'm typing, though I have little faith it will be different

update: fastboot commands didn't work on the other windows 7 virtual system, although adb reboot bootloader did
freaking a this is annoying.
i have a fully stock ROM and radio, anybody to know how to flash a new recovery image and lock the bootloader without accessing fastboot? Just have to get this ready to go back to Samsung so they can fix their own hardware mess ups.

they are 2 different drivers.

As much as I don't like using/recommending the Galaxy Nexus Toolkit (only because I feel it's better to actually learn everything you're doing), it's the easiest way I've found to get the Fastboot drivers installed.
http://forum.xda-developers.com/showthread.php?t=1392310

Thanks guys for your comments.
I've tried Android SDK drivers, PDANet, Universal Naked Driver, and now the one click toolkit mentioned above, some on three different operating systems (Win 7, Win 8, OSx) on 32 and 64 bit.
The wierdest part is that under device manager, no device shows up when the phone is in fastboot, no is there any noise or any recognition of the device being connected at all. It is completely, 100% silent. (again, ADB works when the phone is booted).
I recognize that this may not be possible, but does anyone know how to flash a recovery image without being in the bootloader mode?

If fastboot isnt working like it should, and you are sure it isnt user error, then take it for warranty.
Sent from my i9250

yeah fastboot + the power button (which was defunk in clockwork mod) are back online again, dunno for how long. agreed seems like a hardware/warranty issue.

Recoveries can be flashed with ROM Manager assuming you have SuperUser permissions, but otherwise you or the toolkit need fastboot working.
Sent from my Galaxy Nexus using xda app-developers app

[Q] Gnex Soft brick recovery

Ok I think my samsung galaxy nexus maguro is soft bricked. I can get to the odin screen, I can get to the TWRP screen, and I can get to the bootloader screen, but for the life of me I can not get it to talk over the usb. I have downloaded the Samsung USB Drivers, Ive tried Kies, I ve tried them both separately installed, I've tried them installed toether. I've even tried running it on another computer. I've tried the Universal Nexus Linux Toolkit on Ubuntu. I've gone through 6 different cables, and although I do not have the actual cable that came with this phone, I have tried an actual samsung mobile phone data cable and I can not get the computer to recognize the device.
Does anyone have any ideas?:fingers-crossed:

I'd even be willing to hear off the wall ideas at this point. It is not useable in the state that its in.

bump

bump

gnsoftbrick said:
bump
Click to expand...
Click to collapse
use adb sideload or flash from recovery.
set up correctly adb & fastboot in pc. boot to recovery first, command ~ adb devices * to check your devices is connected or not.
should be no problem if u still have custom recovery installed.
are u using ubuntu or window??
or use odin here~
http://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470

gnsoftbrick said:
Ok I think my samsung galaxy nexus maguro is soft bricked. I can get to the odin screen, I can get to the TWRP screen, and I can get to the bootloader screen, but for the life of me I can not get it to talk over the usb. I have downloaded the Samsung USB Drivers, Ive tried Kies, I ve tried them both separately installed, I've tried them installed toether. I've even tried running it on another computer. I've tried the Universal Nexus Linux Toolkit on Ubuntu. I've gone through 6 different cables, and although I do not have the actual cable that came with this phone, I have tried an actual samsung mobile phone data cable and I can not get the computer to recognize the device.
Does anyone have any ideas?:fingers-crossed:
Click to expand...
Click to collapse
You can factory reset your phone and if this does not solve your problem the use wugfresh nexus root toolkit

a) If you can still get the device into fastboot mode try to flash the partitions with fastboot (grab the stock images from the google developers page and flash them partition by partition). You can also flash the recovery with fastboot.
b) There is an open source odin implementation called heimdall. But you should be extremly cautious before trying that one. You may also find original odin copies. But YMMV and those tools come with some risk.
Make sure you've got a reliable usb connection to your phone. Charge your phone if possible (or charge the battery with a working phone / external charger first).

[Q] Soft Briked Nexus 7 2013 (WiFi) I'm at a Total Loss, Please Help!

I'm totally lost, I have tried everything in the world to get my Nexus 7 2ed gen to get out of a self inflicted boot loop. It all started when I wanted to upgrade it from 4.4.4 to 5.0.2. It was rooted and I have TWRP recovery installed, I wiped the data and chose the wrong thing to do. I instead of a simple wipe, wiped the entire OS and everything.... So now i'm stuck with a rather nice paperweight.... I can boot into recovery (TWRP) and Fastboot. But regardless of what i do I cant get the damn thing to be seen on my computer via ADB or fastboot, so I can't install the stock OS onto it. I've tried re-installing the drivers for The tablet and ADB/fastboot, a countless number of times and nothing works. I've tried it on other computers, that doesn't work, and from how I see it It should.... Anyone out there know what I did to screw this up and how to fix it?

Get an OTG cable and load a ROM onto a flash drive. Then flash the ROM and your choice of gapps.
Sent from my LG-D850 using XDA Free mobile app

^That would be the easiest but still why would fastboot not work?
If adb can't see it in twrp or fastboot on the bootloader screen it's gotta be a driver or connection issue right?
You've probably done it but try different cables/make sure the usb ports are clean.
I'm guessing you flashed twrp with fastboot and know how to use fastboot. If not make sure you're in the fastboot directory before typing the commands in the command prompt.
Only thing left that you already tried is reinstalling everything. Uninstall any fastboot/adb/drivers anything related to android really.
Install the sdk. Install the google usb driver from the sdk manage in the sdk folder.
Boot the tablet to the bootloader screen and plug it in, driver should install automatically. Open a command prompt in the platform-tools folder in the sdk folder and type fastboot devices.
If that doesn't work I have no idea. Oh you could try reinstalling java.

Ok I went ahead and ordered an OTG cable. I also tried installing all the drivers and such another time, but this time when I plugged it in, while it was in bootloader mode, the driver didn't install? I tried several cords, could it be that the tablets port itself is the issue?