Database Info

[Q] Nexus s Stuck at fastboot OEM UNlock

My Nexus s is stuck at GOOGLE LOGO
Here is the Boot Loader Details.
Boot Loader version is : I9020XXKA3
baseband : I9020XXKB1
Locked sTate : LOCKEd
I have downloaded the stock nandroid , but not able to put it on the phone memory.
then tried to unlock the BOOT Loader in order to install Clock..Recovery , but there also after selecting Yes while Running Fastboot oem unlock , phone does not do anything.
then tried to load the file using ADB mode, but when i run adb devices , it doesnt show any device. or when i run adb remount it says "Error device not found"
Please help me get out of it.....

The order to unlock bootloader is:
download all drivers for nxs
download sdk tools
unzip sdk tools on your hdd
start a cmd prompt
navigate to the /tools folder inside sdk (if some adb files are missing get them here, they go into the /tools folder)
connect nxs via usb (enable usb debugging)
type "adb devices" in cmd (should return the device number)
type "adb reload bootloader"
after phone rebooted into fastboot mode type "fastboot oem unlock"
[without the ""s and install drivers if needed]

when i run adb devices it just shows this as shown below.. it doesnt give device serial number,although when i type adb remount it says device not found.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
running ADB reboot says "Device not found"
although i can see in device manager as "android bootloader interface"
moreover when i run fastboot devices
it does show me my device serial number.
JUST to Emphasize I Am not able to start the phone so cant enable usb Debugging

Did you install the PDAnet drivers? I don't think your PC detects your phone correctly for this to work.
Install those drivers, hook the NS up to your PC and boot into bootloader. Running the adb and fastboot commands should work then.
Greetz

I did try try to install pdanet but it also fails eventually , and installation aborts .
I wonder when fastboot mode is detecting right it does display the interactive screen for unlocking boot loader on my phone .then could it still be driver issue
Can you confirm if adb needs "USB DEbugging enabled" which i can't do as mentioned

Yes you need USB debugging for adb
Sent from my Nexus S using Tapatalk

is there a way to enable usb debugging without phone getting started.

justsahid said:
is there a way to enable usb debugging without phone getting started.
Click to expand...
Click to collapse
If fastboot devices showed your serial number, you should be fine. Adb is for when android is up and running. You can mount the sdcard in recovery to copy the image files over for nandroid. If that doesn't work you can always flash in fastboot.

Yes but I am with Stock Recovery ,
IN order to mount SD card I need Clock work recovery and clock work recovery needs UNlocked Boot Loader
SO when I run the COmmand "Fastboot OEM Unlock"
My phone shows me one screen to choose Yes or NO
then I choose "YES" and hit the power button to unlock but then it stays there forever and never Unlocks the Boot Loader.

justsahid said:
Yes but I am with Stock Recovery ,
IN order to mount SD card I need Clock work recovery and clock work recovery needs UNlocked Boot Loader
SO when I run the COmmand "Fastboot OEM Unlock"
My phone shows me one screen to choose Yes or NO
then I choose "YES" and hit the power button to unlock but then it stays there forever and never Unlocks the Boot Loader.
Click to expand...
Click to collapse
If you do Fastboot OEM Unlock and then you wait for a while, and pull the battery, then put it back in and hold volume up + power and go back into bootloader mode, does it say LOCKED or UNLOCKED?

I waited for around 15 mins and then pulled out the battery , and then again went to boot loader it still says LOCKED.
IS it possible to execute Nandorid.zip using fastbot mode ?

Use Odin?
Sent from my Nexus S using XDA App

justsahid said:
I waited for around 15 mins and then pulled out the battery , and then again went to boot loader it still says LOCKED.
IS it possible to execute Nandorid.zip using fastbot mode ?
Click to expand...
Click to collapse
Exactly what all did you do before you tried fastboot oem unlock?

I opened the boot loader and run the command Fastboot Devices it did show me my device
then i run fastboot oem unlock , with which my phone showed up one screen confirming boot loader unlock where i chose "Yes" and hit the power button
i waited for 15 mins , tried multiple times and waited even more than an hour
nothing happens in the cmd promt neither on the phone.

Maximilian Mary said:
If fastboot devices showed your serial number, you should be fine. Adb is for when android is up and running. You can mount the sdcard in recovery to copy the image files over for nandroid. If that doesn't work you can always flash in fastboot.
Click to expand...
Click to collapse
Please help me how can i flash using fastboot I tried Fastboot update update.zip(2.3.3 official update)
it gave me following error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt

Justsahid - I'm in the exact same predicament as you (as of this morning). I'm still trying to figure out how to get the phone to unlock. I noticed there isn't any post regarding success or if you still have this issue
To all:
When trying to wipe data/factory reset in the recovery mode I receive the following error message:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/blockplatform/s3c-sdhci.0/by-name/userdata
Formating Cache...
Data wipe complete
Then when I go and try to "apply update from /sdcard" is shows this message:
E:failed to mount /sdcard
I just wanted to know if those messages would indicate that the "Internal memory" is inaccessible and that all attempts to fix this issue is futile. Keep in mind, I'm also getting the same error message as Justsahid when trying to fastboot the update.
Eskaycee

Eskaycee said:
Justsahid - I'm in the exact same predicament as you (as of this morning). I'm still trying to figure out how to get the phone to unlock. I noticed there isn't any post regarding success or if you still have this issue
To all:
When trying to wipe data/factory reset in the recovery mode I receive the following error message:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/blockplatform/s3c-sdhci.0/by-name/userdata
Formating Cache...
Data wipe complete
Then when I go and try to "apply update from /sdcard" is shows this message:
E:failed to mount /sdcard
I just wanted to know if those messages would indicate that the "Internal memory" is inaccessible and that all attempts to fix this issue is futile. Keep in mind, I'm also getting the same error message as Justsahid when trying to fastboot the update.
Eskaycee
Click to expand...
Click to collapse
I tried everything with no success...then finly I sent the phone go samsung ..as per them there was some electrical part malfunctionining so they replaced it... I hope I will get my phone back by Tuesday

Wow. That's good to know. Thanks for sharing.
Sent from my Nexus S 4G using XDA App

Time for a odin flash

I waiting????????????????????

Fastboot Commands Don't Work

I am trying to unroot and re-lock my xoom and everytime I try to use a fastboot command all I get at the command promt is "waiting for device". I have installed the moto drivers and adb is working fine, just no fastboot. Please help... Thanks in advance!

did you reboot your xoom into bootloader mode? (adb reboot bootloader)

does it show any devices when you type
adb devices

Yes,
adb devices returns the attached device with the serial number.
adb reboot bootloader reboots the device and it say starting fastboot protocol at the top. then when I try to use fastboot flash boot boot.img or any other fastboot command all it does is say waiting for device and that's it..

usb debugging is on? should be if you see the device with adb devices
try to flash another cwm - like rogue version
if you do that - same error?
./adb reboot bootloader
./fastboot flash recovery recoveryroguecwm.img (change real filename )

well, usb-debugging has no effect whatsoever on fastboot.
personally, I suspect a problem outside of the xoom. Have you installed the current motorola drivers using driverhelper? If not, please do so. Please make sure any firewall or anti-virus-software on your computer is disabled or uninstalled.
If you have the possibility, you should try fastboot with another computer.
btw: I'd try if fastboot works with the command fastboot devices. This should return a list of connected and detected devices.

Thanks! For some odd reason my driver needed to be re=installed. After I did that a restarted my computer everything works as it hasin the past!

[Q] Help with Fastboot in Windows

So I've done quite a bit of searching and testing before coming here to post.
I've searched far and wide as well and I seem to be the only one having an issue.
I had read about the NVFlash. Read up on that, and said ok cool let's do it.
So I obtain the files, but initially I discovered I was having an issue on my Linux box getting fastboot to work. I initially got a "no permissions fastboot" reported from 'fastboot devices' Added the udev rules, and then I started getting "?????????? fastboot"
Decided for times sake, I would skip all that Linux stuff, grab the Universal Naked Driver ( which I had done previously to root/unlock my tf700)
Installed said Universal Naked Driver, booted into fastboot mode, and in Windows I get the same exact error... just displayed differently.
I get "? fastboot"
Any ideas?!?!
Thanks in advance for anything

'fastboot devices' doesn't work on our tablet (yet).
That said, the other commands should all work fine as long as you remember to pass the vendor ID 0x0B05 to it. For example,
Code:
fastboot -i 0x0B05 reboot
(Those are zeroes, not letters. Zero x Zero B Zero 5)
Try that. It should reboot your device just fine. I have also successfully flashed a couple of recovery images and the JB Bootloader using fastboot.

vsTerminus said:
'fastboot devices' doesn't work on our tablet (yet).
That said, the other commands should all work fine as long as you remember to pass the vendor ID 0x0B05 to it. For example,
Code:
fastboot -i 0x0B05 reboot
(Those are zeroes, not letters. Zero x Zero B Zero 5)
Try that. It should reboot your device just fine. I have also successfully flashed a couple of recovery images and the JB Bootloader using fastboot.
Click to expand...
Click to collapse
This explains it perfectly, I didn't want to move forward until I got that to work, but thanks to you i know now it is just fine.
That reboot command worked perfectly thanks!

vsTerminus said:
'fastboot devices' doesn't work on our tablet (yet).
That said, the other commands should all work fine as long as you remember to pass the vendor ID 0x0B05 to it. For example,
Click to expand...
Click to collapse
Thank you. It worked. This device is "crazy". Hopefully we will get CM10 "stable" in a short time.

Just wanted to clear up that [fastboot devices] works just fine. Not sure why it didn't for you, but I've used it successfully a few times.

Sent from my OGparanoid CM D2tmo

Fastboot not working for me
fastboot is not working for my device at all. Neither of the following commands achieves the desired results:
Code:
C:\>fastboot devices
// nothing
C:\>fastboot -i 0x0B05 reboot
< waiting for device >
// stays like this until I cancel the command
I do see the device when I run
Code:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C6OKAS043713 device
To my knowledge, the device drivers were successfully installed. I'm on Windows 7 64-bit, I have the full SDK and all the platform tools installed, and I've used fastboot many times on my HTC Glacier (so it's definitely a working binary). Can anyone help me?

jdkoren said:
fastboot is not working for my device at all. Neither of the following commands achieves the desired results:
Code:
C:\>fastboot devices
// nothing
C:\>fastboot -i 0x0B05 reboot
< waiting for device >
// stays like this until I cancel the command
I do see the device when I run
Code:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C6OKAS043713 device
To my knowledge, the device drivers were successfully installed. I'm on Windows 7 64-bit, I have the full SDK and all the platform tools installed, and I've used fastboot many times on my HTC Glacier (so it's definitely a working binary). Can anyone help me?
Click to expand...
Click to collapse
Did you boot your device to fastboot mode before you execute fastboot command on your PC?

buhohitr said:
Did you boot your device to fastboot mode before you execute fastboot command on your PC?
Click to expand...
Click to collapse
Hmm, it seems to be working now. Odd that fastboot devices doesn't recognize it, but I guess I can continue without it. Thanks.

No OS ,how do I boot into bootloader

hello guys,,i dont have my os and i only have normal recovery of lenovo vibe shot ,,i want to access bootloader so that i can flash twrp recovery so that i can install new rom,,,but when i try to access boot loader using adb tools in pc it shows
"c:\program files <x86>\Minimal ADB and Fastboot> adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
try 'adb kill-server' if that seems wrong.
Otherwise chech for a confirmation dialog on your device""""
but i dont have os installed and i want to flash New rom by flashing twrp or qcomdloader and qcimdloader does not recognize my phone ,
plzz someone help

BMAX MaxPad_i11 Bootloader Unlock w/ Unisoc T618

All files can be downloaded from the iplay40 tread. MUST use iPlay40 fastboot version or else it will fail using commands.
Download install SpreadTrumTools-20200317.apk
run command -- adb shell getprop ro.serialno
Enter the serial you get from your tablet and HIT generate your own signature.bin file
run command --- adb reboot bootloader
In fastboot mode -
enter command -- fastboot flashing unlock_bootloader signature.bin
Press volume down to confirm bootloader unlocking, all user data will be erased.
wait til done -- success and enjoy
Note - can take up to 5-10 mins to unlock bootloader and earse user data, be patient

After adb reboot bootloader, mine reboots, says it's in fastboot mode and continuously vibrates, non stop. It won't accept the next steps after that.
Only way out is to keep the power button pressed until it reboots.
So can't unlock bootloader.