Database Develop

[Q] Unlock Bootloader Problem

Hi guys, I have a problem.
I want to flash my N1 with the Cyanogenmod, but I have a problem with Bootloader unlocking. I do exactly what here is written (in the N1 guide from wiki.cyanogenmod), but when I open CMD (win XP) and write "fastboot oem unlock", it just doesn't works, but "adb devices" works and shows my phone. What can I do ? Any ideas ?

You need to boot into bootloader to work with fastboot. And if "adb devices" shows your phone - you obviously didn't boot.
adb reboot bootloader
Click to expand...
Click to collapse
Also, for a more comprehensive guide, please read the Wiki.

Code:
C:\fastboot>fastboot oem unlock
'fastboot' is not recognized as a
operable program or batch file.
This is what it shows in bootloader mode.
P.S. I have already re-installed my drivers. I have to notice that when I try to reinstall the drivers (in fastboot mode), they always auto-install themselves and when I try to update them, they say that there isn't newer version.

Fastboot executable isn't in the same directory as ADB executable, and isn't in the path you're executing it from (which is C:\fastboot).
Check, what is the actual executable you're trying to run, and if you have one. It might be called fastboot-windows.exe, if you didn't get it from downloading the Android SDK.

There is a executable file named "fastboot-windows.exe", but when I try to run it, it just open and close for 1 second. Any ideas ?

I thought the message would be clear by now... Oh well.
Open command prompt.
Run:
fastboot-windows oem unlock
Click to expand...
Click to collapse

I think It's done but my computer shows this message (see attached) 5 mins and I don't know it's ready or not ? Could I turn on the phone ? (Sry for the easy questions but I'm a real noob, because that's my 1st Android phone.)

The "too many links" message doesn't look good.
Reboot your computer.
Reboot the phone.
Use different USB port in your computer.

Ok well if you want my input try "fastboot devices" this should return your S/N (starting with "HT") if it gives you the same error then I would reinstall the SDK.

[Q] adb returning "error: closed"

Hi,
I'm currently trying to use adb to push some data into my phone but i always get "error: closed". I'm using windows 7 x64 and im running it from cmd.
Almost everything i tried using adb (push, shell, remount) returns this. I've searched over the forums and tried "adb devices" as well to see if my phone is connected, but what is different from the others is i am getting
List of devices attached
XXXXXX host
instead of what most other people got
List of devices attached
XXXXXX device
Is this a problem? What am i missing? Thanks a lot for ur time in reading this

Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices

Guich said:
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Click to expand...
Click to collapse
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip

Did you update the SDK Manager??? Try updating that, my ADB problem were gone after i updated them.....

xlxcrossing said:
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Click to expand...
Click to collapse
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?

jflora1 said:
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
Click to expand...
Click to collapse
Try to download this, un-zip and try the tips with this

Guich said:
Try to download this, un-zip and try the tips with this
Click to expand...
Click to collapse
I downloaded the zip but haven't had any success, still getting an error:closed message

ozo012 said:
I downloaded the zip but haven't had any success, still getting an error:closed message
Click to expand...
Click to collapse
which recovery are you on? (name and version number please)

nkk71 said:
which recovery are you on? (name and version number please)
Click to expand...
Click to collapse
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.

ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
isnt "error closed" something to do with out of date adb?

ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
nkk71 said:
isnt "error closed" something to do with out of date adb?
Click to expand...
Click to collapse
Umh, no, i don' think

Guich said:
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
Umh, no, i don' think
Click to expand...
Click to collapse
I haven't tried rebooting the device seems to be the only thing I left out.

I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.

worked for me
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload

morheb said:
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
Click to expand...
Click to collapse
Yay. That Just worked for me using Crunchbang Debian. Thanks morheb that little tweak of using 'sideload' was the key

Can anyone help me push vold.fstab file with adb?
Stock Recovery on mediatek platform. with adb i got same error as this thread. Error:closed

KoolAidBigMan said:
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
Click to expand...
Click to collapse
Perfect - worked for me - exact same issue - adb wasnt recognising my phone was in sideload and sideload command wouldnt work but push would - plus getting error closed message on adb usb command. Googled the above adb file, downloaded, 15 second install and now sideloading is working on my SG2 with CWM recovery 6.0.2.9 (kitkat). I was obviously using an outdated ADB driver (1.0.29).
Thanks a lot KoolAidBigMan !! Big up...
Jimbo
EDIT : Spoke too soon - now getting another error when trying to sideload.. will google it.. failed to write data 'protocol fault (no status)'
EDIT : Sorted. Ended up getting round it by pushing the files instead - found instructions on Cyanogenmod forums. Thanks once again.

http://forum.xda-developers.com/sho...wQFjAA&usg=AFQjCNGgPmMne0aYCd9RojZZhy89cQjnCw
Try this
Sent from my C6916 using XDA Free mobile app

Link not working?? Im ok now anyway.. Time to test my screen casting to my Chromecast.. :fingers-crossed:

mtk6572 have same error
I have same error.. but I know that my phone's usb debugging is not enable.. so I got this error:close..
My phone is on bootloop so I can't enable the usb debugging.. Is there any way to enable the usb debugging using adb commands? I trying to push the framework-res.apk on my phone.. because it is the cause of the bootloop.
i'm a nood

[Q] Please help! Formatted phone and cannot load O/S! (rooted)

Ok so on my HTC One I loaded TWRP recovery and had a rom installed. I wanted to wipe it out and reinstall a newer version of the rom, and in the process I thought I had a "virtual SD" that wouldn't be wiped out. Boy was I wrong. Now I can get into TWRP and I am reading about "adb sideload" to load a rom zip file to the phone.
I have Windows 8 and I used the trick of installing Windows 7 drivers, but now for some reason the computer shows "Android Device" with an exclamation point. I google'd and found a Windows 8 HTC driver, and now the device shows up "Android USB Devices - MyHTC". So it appears I have drivers installed.
Now I read tutorials and have been searching for hours and I cannot get this to work. I have the ADB Fastboot folder on my desktop and the rom I want to load in that folder. I bring up the command prompt and type in "adb devices". It returns with this:
List of devices attached
FA34PS904380 host
I type in (without quotes) "adb sideload rom.zip" which is in the same directory. It returns with all the possible commands (like a help menu) of how you can use adb.
I'm stuck. Any ideas?
Thanks

Nurmi_CEO said:
Ok so on my HTC One I loaded TWRP recovery and had a rom installed. I wanted to wipe it out and reinstall a newer version of the rom, and in the process I thought I had a "virtual SD" that wouldn't be wiped out. Boy was I wrong. Now I can get into TWRP and I am reading about "adb sideload" to load a rom zip file to the phone.
I have Windows 8 and I used the trick of installing Windows 7 drivers, but now for some reason the computer shows "Android Device" with an exclamation point. I google'd and found a Windows 8 HTC driver, and now the device shows up "Android USB Devices - MyHTC". So it appears I have drivers installed.
Now I read tutorials and have been searching for hours and I cannot get this to work. I have the ADB Fastboot folder on my desktop and the rom I want to load in that folder. I bring up the command prompt and type in "adb devices". It returns with this:
List of devices attached
FA34PS904380 host
I type in (without quotes) "adb sideload rom.zip" which is in the same directory. It returns with all the possible commands (like a help menu) of how you can use adb.
I'm stuck. Any ideas?
Thanks
Click to expand...
Click to collapse
Try moving the files to your Android-SDK/platform-tools folder

bigdaddy619 said:
Try moving the files to your Android-SDK/platform-tools folder
Click to expand...
Click to collapse
PERFECT! Thanks a ton!

download Hassoon's tool and side load if you are having issues
thread : http://forum.xda-developers.com/showthread.php?t=2236814
and the thread that would have saved you from making this one... http://forum.xda-developers.com/showthread.php?t=2258809

Nurmi_CEO said:
PERFECT! Thanks a ton!
Click to expand...
Click to collapse
I'm guessing that worked?

bigdaddy619 said:
I'm guessing that worked?
Click to expand...
Click to collapse
Yes it did. Instantly after that. I was searching and trying stuff for hours, gave up and decided to post. Thanks for the help.

Nurmi_CEO said:
Yes it did. Instantly after that. I was searching and trying stuff for hours, gave up and decided to post. Thanks for the help.
Click to expand...
Click to collapse
No worries glad you got it

Nurmi_CEO said:
PERFECT! Thanks a ton!
Click to expand...
Click to collapse
Hitting the thanks button for someone who helps is proper etiquette
IMHO anyways :good:

budeone said:
Hitting the thanks button for someone who helps is proper etiquette
IMHO anyways :good:
Click to expand...
Click to collapse
No worries I don't do it for the thanks I do it because I enjoy helping when I can
Sent from my Liquid Smooth Nexus 7

[Q] boot loader issues

I'm trying to unlock my htc one so I can root it but am running into the issue of every time I enter fast boot mode and plug into the PC that my phone won't get read by pc. When phone is on and in normal mode it is loading up just fine. I also tried to open a command window when in fast boot folder by hitting shift and right clicking and nothing. What am I doing wrong? I'm following the directions to a t and still am getting no where. Any help would be greatly appreciated. Thanks

dcm1200 said:
I'm trying to unlock my htc one so I can root it but am running into the issue of every time I enter fast boot mode and plug into the PC that my phone won't get read by pc. When phone is on and in normal mode it is loading up just fine. I also tried to open a command window when in fast boot folder by hitting shift and right clicking and nothing. What am I doing wrong? I'm following the directions to a t and still am getting no where. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
which instructions are you following?
you can try THESE drivers; uninstall HTC Sync or any other HTC Drives you installed
install those drivers and restart your PC and try again

drivers are working but command prompt still not opening
kamilmirza said:
which instructions are you following?
you can try THESE drivers; uninstall HTC Sync or any other HTC Drives you installed
install those drivers and restart your PC and try again
Click to expand...
Click to collapse
Downloaded the drivers, restarted but command window still will not open when I press and hold shift and right click

dcm1200 said:
Downloaded the drivers, restarted but command window still will not open when I press and hold shift and right click
Click to expand...
Click to collapse
Google "minimal adb fastboot xda" and use it
Sent from my One using Tapatalk

progress
kamilmirza said:
Google "minimal adb fastboot xda" and use it
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Got unlock code sent to email account. downloaded unlock code. went back to HTC dev site and opened command prompt that you suggested and entered the command that htc said to use and got the following message.
C:\Program Files\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1526722560 bytes
error: cannot load 'Unlock_code.bin': Unknown error
C:\Program Files\Minimal ADB and Fastboot>
dont know what to do now???? any help will still be greatly appreciated

google glass stuck on "glass" text screen

Okay I know I need to wipe the device and/or reinstall the update
But I have no clue how to use android SDK or adb.
I have them both downloaded, not sure if they are installed for google glass access.
I'm using the command prompt and I search for adb or fastboot but no devices come up?
I downloaded the XE22 (latest firmware) but when I open that it asks me to burn a cd?
I'm lost and glass support won't help. Anybody?

phild22 said:
Okay I know I need to wipe the device and/or reinstall the update
But I have no clue how to use android SDK or adb.
I have them both downloaded, not sure if they are installed for google glass access.
I'm using the command prompt and I search for adb or fastboot but no devices come up?
I downloaded the XE22 (latest firmware) but when I open that it asks me to burn a cd?
I'm lost and glass support won't help. Anybody?
Click to expand...
Click to collapse
I just went through this to get to XE23. Did you ever get to the answer? Very similar process to flashing any other android device; identical really. LMK if you're still charging and using or want to.
GH

greddy91 said:
I just went through this to get to XE23. Did you ever get to the answer? Very similar process to flashing any other android device; identical really. LMK if you're still charging and using or want to.
GH
Click to expand...
Click to collapse
Ok... As I am new to the Glass game.... Last night, when I got the unit fully charged (Sitting at SW version XE12), I connected it to the network to update.... This morning, I have a bootloop issue.
I want to flash XE 12 back to the device and try to let it update again.... I have yet to find a clear breakdown on how to falsh this... SDK is installed.... But it appears that I don't have a the proper USB drivetr and have know idea how to install it...
Really could use some help with the entire process...

So, sharing files used on Google drive:
https://drive.google.com/drive/folders/0B3-nca6GSfX1R2h1eDNDUjZwRVk?usp=sharing
Installed Minimal ADB and hit yes all the way through - in the google drive above.
This gives ADB commands functionality anywhere in CMD
I plugged in the glass and it came up as a USB drive - AWESOME.
Enter Command Prompt
Navigate to the directory where I had the Glass EX23 unzipped
Entered "adb devices" to make sure ADB was seeing the Glass (make sure no other android goodies are plugged in)
It was there so...
Enter "adb reboot bootloader"
My glass went blank.
Entered "fastboot devices" ... and nothing.
So opened "Device Manager"
There was a flagged driver standing out for when I flashed an old Note 2. There's the problem...
Right click and chose "Update driver" and pointed it to the "usb driver" directory extracted from the zip file in the google drive above.
Chose Android Composite ADB Interface - Skipped past the unsigned driver warning
Voila - the device is now seen in device manager
I then entered the command in cmd "fastboot devices" - and still blank
Unplugged glass and rebooted.
After it came up, plugged it back in - seen as USB drive again. Still good!
Entered "adb devices" to make sure ADB was seeing the Glass
It was there again so...
Enter "adb reboot bootloader"
My glass went blank again.
Entered "fastboot devices" ... and there it is!!! The Gates of Valhalla are in sight!!!
Assure you're in the directory where the google image has been unzipped...
Now begin by entering:
"fastboot flash boot boot.img"
let it complete
Now "fastboot flash system system.img"
let it complete (this is the longest one... be patient)
Now "fastboot flash recovery recovery.img"
Now "fastboot flash userdata userdata.img"
Now "fastboot erase cache" - takes a bit of time for cleanup
Now "fastboot reboot"
The moment of glory has arrived... watch your glass go through boot - yes the Glass screen turns on and off a few times and flashes some odd colors... again, be patient... took like 5 minutes and ate up 40% of my full battery, but there it was XE23 and full stability.
Note - NONE of these utilities are mine, they were borrowed after researching in hundreds of other threads on how to get this done.
Of note... I came from XE10 straight to XE23 with no issues.

Legobricke said:
Ok... As I am new to the Glass game.... Last night, when I got the unit fully charged (Sitting at SW version XE12), I connected it to the network to update.... This morning, I have a bootloop issue.
I want to flash XE 12 back to the device and try to let it update again.... I have yet to find a clear breakdown on how to falsh this... SDK is installed.... But it appears that I don't have a the proper USB drivetr and have know idea how to install it...
Really could use some help with the entire process...
Click to expand...
Click to collapse
What version of Glass is it? And there is a thread under development about modifying your android_winusb.ini file so you can manually select the driver.

Muskeman16 said:
What version of Glass is it? And there is a thread under development about modifying your android_winusb.ini file so you can manually select the driver.
Click to expand...
Click to collapse
It is model XE-C running version XE-12...

Legobricke said:
It is model XE-C running version XE-12...
Click to expand...
Click to collapse
Have you attempted to re-flash it at all?

Muskeman16 said:
Have you attempted to re-flash it at all?
Click to expand...
Click to collapse
That is was I'm attempting to do.... But I'm not having much luck....
I am sure that USB debugging was not turned on.... When I put the Glass in to fastboot mode (holding down camera button and turning on which gives me short fast bursts from the power light) it doesn't seem to recognize it on the desktop. I get 3 low tones when I plug it in and ADB doesn't see it...
I guess I need a direct breakdown of the process... I have searched the net and forum, but the ones I find seem to drop a process or imply something that I'm not understanding.
I have flashed devices before and I'm familiar with the process, but I'm missing something when it comes to the Glass....
When I power up (normal power up) and the plug it, device manager lists it as Android Device. When I open that, just shows ADB Device Interface... I have tried to update the entry with the USB driver, it is claims the drivers are up to date.
I am using Windows 7.... But it is clear that ADB is not seeing the device... So, I'm stuck until I can findout how to get the device to be recongized.... What is strange is that when I plug the Glass in, it does see it in the tray below... It even allows me the "eject Glass_1... but for the life me, I can't get ADB to see it...
Any help is appreciated!

Ok.... I can finally see the Glass in ADB.... But only if I put the Glass in Fastboot mode prior to plugging in to USB.... I adb "fastboot device" and get a serial number.... Then I adb "fastboot flash boot boot.img and get FAILED (remote failure)...
What am I doing wrong?

I have even tried to unlock the device, but it hangs at erasing userdata.
The very interesting thing is on a few occasions, I have gotten GLASS to work....
I re-set it up.... and then it works fine until I have to charge it again and then it goes back to the freezing on the GLASS screen.
Every time I try to flash Boot/system/ etc image... it fails.... Not sure why....

Ok....
Finally nailed it.... No more GLASS looping....
I took this unit that was experiencing GLASS loop at firmware X12 to X23... What a journey....
To start.... I downloaded the "minimal adb fastboot" and installed....
Then I downloaded the new firmware from google
I dragged the zip folder to my desktop and extracted it....
At this point, I put GLASS in fastboot mode (Hold camera button down then press the power button. Once power light come on, let go of the power button but keep camera pressed. One the light starts to flash (slowly, not fading), you are in fastboot mode).
I then attached the glass via usb cable to computer (I was operating Windows 10).
Open device manager and look for "android devices" and open it. You should see "Android ADB Interface" - Right click on it and select Update Driver Software". Then select Browse my computer for driver software. The select "Let me pick from a list of device drivers on my computer". Look for "Android ADB Interface". Select it and then update it.
Once this is done, got to your icon tray (should be down in the bottom right of your scree) and right click on "Safetly Remove Hardware or Eject Media". It should open a window up. Confirm that glass is there.
Then go to the desktop where you extracted the firmware and open the folder. Once open, Hold shift and right click. This should give you a menu. You are looking for "Open command window here". select it and it should open a command window.
Then follow the instructions listed on the google firmware page.
I didn't follow all the instructions.... The ones I did were enough to fix my boot looping GLASS -
1.) fastboot devices (This should comeback with a serial number. If it doesn't, be sure you have the glass in fastboot mode)
2.) fastboot oem unlock ( I had to do this because the device would fail when I tried flashing to the device. This was the only way I could get it to take the flashing). It will make you type this twice to confirm you wish to unlock.... This will erase all the data (cache and user data) on the device and you have to be patient.... It does take some time... If you think it has hung up (which I did), I just hit a key on my keyboard and then pressed enter.... It then confirmed that the unit had been unlocked.
3.) After I unlocked the unit, I then typed fastboot devices again just to be sure that it was still reading the GLASS.
4.) fastboot flash boot boot.img - This will fail if you don't have the unit unlocked.... The first time I did this, the glass unit went down and I had to start the process again. The second time I did the process, it worked.
5.) fastboot flash system system.img - This did take a few minutes
6.) fastboot flash recovery recovery.img
Once done, I closed the command window and ejected the glass unit from the computer..... I pressed the power button and BOOM! I was back to a working glass...
One key element I must point out.... allot of this process requires allot of patience....
The pages that are linked above will help you through the process.... I took a week of researching.... But it was worth it...
There are risks involved - bricking/etc.... But this is the process that worked for me...
Good luck!

Legobricke said:
Ok.... I can finally see the Glass in ADB.... But only if I put the Glass in Fastboot mode prior to plugging in to USB.... I adb "fastboot device" and get a serial number.... Then I adb "fastboot flash boot boot.img and get FAILED (remote failure)...
What am I doing wrong?
Click to expand...
Click to collapse
Just for clarity - I associate adb and fastboot as two seperate commands.
"adb devices" gives you your android attached devices inventory
"fastboot devices" gives you your attached devices in fastboot
The "adb reboot bootloader" changes the device seen in adb to a device that can be seen in fastboot.
Not sure if that was clear before, but it may help here.

greddy91 said:
Just for clarity - I associate adb and fastboot as two seperate commands.
"adb devices" gives you your android attached devices inventory
"fastboot devices" gives you your attached devices in fastboot
The "adb reboot bootloader" changes the device seen in adb to a device that can be seen in fastboot.
Not sure if that was clear before, but it may help here.
Click to expand...
Click to collapse
Thanks for the clarify....
I attempted to go the adb route, but could never get the system to see the GLASS in adb... and because the GLASS was looping on the GLASS screen, I couldn't activate USB Debugging..
So, I found out in researching that I could manually put the GLASS in fast boot mode....
Once it was unlocked, everything took...

not a tech guy -_-
Hi thanks for clearifying But could you explain step by step and like i know nothing about commad prompt. Im just tring to work my glass but at turkey i cant find any coder who understands this. (sorry for bad english)