Hello,
I've found several howtos dealing with locking back the Nexus S bootloader.
They all say to run the follwing commands :
- adb reboot bootloader
- fastboot oem lock
While the first command indeed reboots my phone into fastboot mode, the second one hangs on "Wating for the device".
I'm running the latest Android SDK on Windows 7.
Any help would be much appreciated.
Cheers
EDIT : Problem solved after I moved the content of the platform-tools folder into the tools folder. I assume the problem was related to the install of the SDK.
Related
A week ago I faced this error for the first time but didn't have the time to take a look at it so I just downloaded Air Droid as a temporary solution. But then more problem appeared. The battery indicator wasn't working so I decided to fix it somehow. To dig on Google. I tried flashing different ROMs and recoveries and on and on. the problem is that I'm now stuck on bootloader. I have no system installed and that crappy TWP won't start. The splash screen just flashes and that's all. So my phone is now a brick and I just don't have any more ideas. I need to lock my bootloader somehow so I can take it back to Samsung establish some kind of USB connection so I can install a new atleast,
Any help would be very much appreciated.
Zunex
anyone?
Zunex95 said:
anyone?
Click to expand...
Click to collapse
Hello,
I assume you are using a windows pc (correct me if i'm wrong)
Use this forum > http://forum.xda-developers.com/showthread.php?t=1901617 to install drivers for your nexus s.
Afterwards, reboot your PC
Do you have adb installed? If so skip this part:
Install minimal adb and fastboot using this forum > http://forum.xda-developers.com/showthread.php?p=42407269
Try inputting fastboot devices into the terminal window and see if your device shows up
Then you can flash everything back to stock. You can do this by following the following steps:
Go to this link and download the appropriate files for your nexus s >https://developers.google.com/android/nexus/images
Use a program such as 7-Zip to open and uncompress the package to a folder of your choosing
Navigate to that folder and try clicking flash-all.bat
Hopefully that will flash your whole phone back to stock. If not you will have to manually flash each part. Do this by typing the following into the terminal, one by one, replacing the file names with the appropriate ones for your nexus s.
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-jzo54k.zip
For example, for the first line of code, I would go into the uncompressed folder and hold down shift while right clicking the bootloader file. I would then select “copy as path”. Then I would go back to the terminal and type “fastboot flash bootloader ” then paste the path I just copied. I would then repeat for the rest of the items.
Feel free to ask questions if it does not work. Ill try to reply as soon as possible. Cheers.
Thanks I solved it. The problem was with my phone's USB port. Atleast the usb module/part of the port. I put a little metal in it then moved it around a couple times.. tried to save it. Somehow I got it working again, so I instantly flash a working recovery then went back stock. I returned my device to Samsung (It was under warranty) and they fixed it.
Cheers
Hello, today I finally received my one plus 6. Been loving the device so far
I was on my way to Chuck a custom recovery and rom unlocked the bootloader no drama
I then hit a Plato of fastboot coming up with no command error as in fastboot isn't working in cmd I have researched heaps about it and I can not find a single thing. I tried to reinstall drivers and all that, and yes I'm running cmd in the fastboot files, only adb seems to be working but I can no longer use fastboot on my PC.
Has anyone come across this error, it seems to be that after installing the one plus drivers it stopped working correctly and fastboot commands no longer register in fastboot...
My phone is detected in fastboot mode so it's not the drivers. What could be causing this, is it the computer at fault?
Currently in the process of unlocking bootloader via following the steps provided in this forum. I'm having trouble with my computer recognizing my device when I boot into bootloader. When the phone is on, it is recognized as "OnePlus", but in Bootloader the computer says "Android" and "Drivers unavailable" I've tried manually assigning them with no luck. Any help would be appreciated
Still no luck on unlocking boot loader. I've installed and reinstalled drivers from OnePlus and Adb and fastboot, tried installing the Android SDK. No luck. I cannot get "fastboot devices" command to show anything in a command prompt
are you writing the command "fasboot devices" on the same directory where you have installed your adb?
Chinaroad said:
are you writing the command "fasboot devices" on the same directory where you have installed your adb?
Click to expand...
Click to collapse
I have tried it on a few different directories. I installed the adb via the exe on the tutorial. I'm not sure which directory that would be
If you already installed adb go to c:/adb in the folder hold shift and click the right mouse button, there should be an option that says open command prompt here or open powershell prompt here, click it. You should see a command prompt, boot into fastboot and connect your phone to your computer and now type "fastboot devices". If it doesn't detect it, it might mean that you haven't enabled USB debugging. And remember to turn on oem unlocking in your phone
I finally figured out my issue. I had to go into the windows device properties, attempt to manually install the drivers while the phone was in bootloader. It would then throw an error about the android bootloader interface and asked if i wanted to search for an update, windows actually found an update to that particular part of the driver. Installed it and that fixed it.
Glad you fixed it
TheBananaz said:
I finally figured out my issue. I had to go into the windows device properties, attempt to manually install the drivers while the phone was in bootloader. It would then throw an error about the android bootloader interface and asked if i wanted to search for an update, windows actually found an update to that particular part of the driver. Installed it and that fixed it.
Click to expand...
Click to collapse
Could you kindly share which specific OnePlus device you were able to unlock the bootloader, e.g. Unlocked OnePlus 6, International Version, etc?
Hello,
I am trying to install CM on my old Android tablet - Lenovo TAB 2 A7-30DC, Android version : 5.0.1 , Kernel version: 3.10.54 . I have downloaded the zip cm-12.1-Tab2A710F-20210102-1707.zip , but I cant install it . I have root on the tablet, installed flashify, twrp, but I cannot unlock the bootloader - I dont have OEM unlocking as an option in Developer Mode menu. Please let me know what should be my next steps. Thank you.
Download "ADB fastboot tools"
Download and Extract the Downloaded ADB fastboot Zip file on your PC.
Now connect your phone to Computer using USB Cable.
When you connect your Phone to Computer, please wait until all the drivers get installed.
In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click Now type the command in your command window:
-----------------------
adb devices
------------------------
If you see a pop up to allow USB Debugging on your phone, Click OK
Now type the command below to reboot your phone to bootloader:
-------------------------------------
adb reboot bootloader
-------------------------------------
Once your phone reboot into bootloader, make sure your phone shows the bootloader locked and then type the command below to make sure fastboot drivers are installed properly.
-------------------------------------
fastboot devices
-------------------------------------
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
(Remember that this step will wipe EVERYTHING off the phone)
-------------------------------------
fastboot oem unlock
-------------------------------------
After the above command has finished executing, run the following:
---------------------------
fastboot reboot
---------------------------
The phone will reboot. Wait until the phone has fully booted up into android, and enjoy.
The link you posted is the only link I found on the internet that is not dead. It is impossible to find some link for custom rom and twrp that works. I have the same tablet. I unlocked the bootloader and that’s all I managed to do.
petko.dimitrov said:
Hello,
I am trying to install CM on my old Android tablet - Lenovo TAB 2 A7-30DC, Android version : 5.0.1 , Kernel version: 3.10.54 . I have downloaded the zip cm-12.1-Tab2A710F-20210102-1707.zip , but I cant install it . I have root on the tablet, installed flashify, twrp, but I cannot unlock the bootloader - I dont have OEM unlocking as an option in Developer Mode menu. Please let me know what should be my next steps. Thank you.
Click to expand...
Click to collapse
I have this problem too. And I have another problem my device recognizes my tab when I type adb devices but it doesn't recognize it in fastboot mode. I have installed all drivers I don't know what else to do.
Hey guys, I need help flashing my Google pixel 2. It was off for a couple of months and now when I am trying to start it, its not booting without putting it on charge and even then it only shows the battery icon then the google icon and restarts (So a bootloop). But when I press and hold the power button and volume down key, it goes in the fastboot mode ( the one where all device information is shown with an Android Logo) (Pic att).
If I select Download mode, it just shows operation denied and if I select recovery mode then it goes to bootloop again. Also as far as I remember when I last used the phone, the usb debugging was turned off so please suggest what to do from here.
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Alekos said:
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Click to expand...
Click to collapse
Hey thanks for the update man. I know I should have kept atleast oem unlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
mayankggrwl said:
Hey thanks for the update man. I know I should have nlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
Click to expand...
Click to collapse
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Alekos said:
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Click to expand...
Click to collapse
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
mayankggrwl said:
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
Click to expand...
Click to collapse
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Alekos said:
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Click to expand...
Click to collapse
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
mayankggrwl said:
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
Click to expand...
Click to collapse
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how the op in that thread above fixed his Pixel 2 with Skipsoft tool. His Device state said Locked in his screenshot on his post.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
edit--try these commands
fastboot erase system
fastboot erase data
fastboot erase cache
Alekos said:
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how those users in the thread flashed the bootloader image since I didn't think you could if the device state is locked, but worth a try.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
Click to expand...
Click to collapse
Okay great !! Thanks for these. Ill go through that thread and will see if any of the listed methods work. Will also try that software. In a rush so will try these later on and then ill update you.