So, my fire HD has the Android composite ADB interface as the driver.. I can find the tablet on prompt ADB devices but when I put the device into adb reboot recovery I lose it.. The cme can't see the tablet anymore, any thoughts on a solution? Windows 8 x64
Thanks very much
Are you saying "adb reboot recovery" doesn't boot you into recovery or that once in recovery adb commands don't work. If you're booting into stock recovery, that seems to be how it works.
If you can't get into recovery with the generic drivers, I swear by Google Galaxy Nexus from Koush's Universal Android package. Someone recommended the HTC dream driver.
EDIT: I see the prob. Wouldn't be able to issue "adb sideload" would you? Sorry, not much help.
---------- Post added at 10:25 PM ---------- Previous post was at 10:06 PM ----------
Well, this is good to know at this thread too!
limitedxj said:
I fixed my own problem, when in recovery the tablet was acting like a new tablet, wondered if that was true so i checked the managed devices, sure enough, the fire had a new name, added the Adb composite to the new name, boom..
Click to expand...
Click to collapse
Correction
Thanks for pasting that, I originally posted it in the specific thread I was trying to duplicate then realized it was a driver issue and more Q/A related. The fix for my problem was checking the driver setting at each step of Adb on 1st initation. Simple fix but threw me off a bit..
Thanks for the quick reply
So I'm seeing this exact issue. (As you said in other thread, adb devices returns device id, then in recovery it doesn't.) Can you clarify "first initiation"? I've had these drivers installed for months. You just updated, checking driver setting in device mgr? thx
limitedxj said:
The fix for my problem was checking the driver setting at each step of Adb on 1st initation.
Click to expand...
Click to collapse
DoLooper said:
So I'm seeing this exact issue. (As you said in other thread, adb devices returns device id, then in recovery it doesn't.) Can you clarify "first initiation"? I've had these drivers installed for months. You just updated, checking driver setting in device mgr? thx
Click to expand...
Click to collapse
limitedxj said:
Thanks for pasting that, I originally posted it in the specific thread I was trying to duplicate then realized it was a driver issue and more Q/A related. The fix for my problem was checking the driver setting at each step of Adb on 1st initation. Simple fix but threw me off a bit..
Thanks for the quick reply
Click to expand...
Click to collapse
DoLooper said:
Are you saying "adb reboot recovery" doesn't boot you into recovery or that once in recovery adb commands don't work. If you're booting into stock recovery, that seems to be how it works.
If you can't get into recovery with the generic drivers, I swear by Google Galaxy Nexus from Koush's Universal Android package. Someone recommended the HTC dream driver.
EDIT: I see the prob. Wouldn't be able to issue "adb sideload" would you? Sorry, not much help.
---------- Post added at 10:25 PM ---------- Previous post was at 10:06 PM ----------
Well, this is good to know at this thread too!
Click to expand...
Click to collapse
limitedxj said:
So, my fire HD has the Android composite ADB interface as the driver.. I can find the tablet on prompt ADB devices but when I put the device into adb reboot recovery I lose it.. The cme can't see the tablet anymore, any thoughts on a solution? Windows 8 x64
Thanks very much
Click to expand...
Click to collapse
Try this when you are in sideboard mode forum.xda-developers.com/showthread.php?p=36523572#post36523572
Sent from my Nexus 7 using Tapatalk
powerpoint45 said:
Try this when you are in sideboard mode forum.xda-developers.com/showthread.php?p=36523572#post36523572
Click to expand...
Click to collapse
ok, by "sideboard," I'm guessing you mean sideload, but figure you must mean recovery Anyway, thanks!
I think I see problem. I saw this post over here in Q&A, not as part of your upgrade to 5/downgrade to 4.5.3 guide. So, I'm trying this on 4.5.3(!) which doesn't have any "Apply update from ADB" option. When OP said he was able to fix drivers so he could give adb command from recovery, I thought he meant on 4.5.3 and wondered why I couldn't do that.
Makes perfect sense that adb wouldn't recognize a 4.5.3 device in recovery, where it's basically turned off while waiting for a manual reboot or reset. (Eagerly awaiting method to preserve root through 5.0 upgrade ) Ah, well . . .
DoLooper said:
ok, by "sideboard," I'm guessing you mean sideload, but figure you must mean recovery Anyway, thanks!
I think I see problem. I saw this post over here in Q&A, not as part of your upgrade to 5/downgrade to 4.5.3 guide. So, I'm trying this on 4.5.3(!) which doesn't have any "Apply update from ADB" option. When OP said he was able to fix drivers so he could give adb command from recovery, I thought he meant on 4.5.3 and wondered why I couldn't do that.
Makes perfect sense that adb wouldn't recognize a 4.5.3 device in recovery, where it's basically turned off while waiting for a manual reboot or reset. (Eagerly awaiting method to preserve root through 5.0 upgrade ) Ah, well . . .
Click to expand...
Click to collapse
Lol yes I mean sideload. Dumb auto correct. I say sideload instead of recovery because recovery alone has no adb access. Adb is only activated whenever you put it in sideload mode
Sent from my Nexus 7 using Tapatalk
Ah. . . now i get it. Thanks!
Looper,
In cme, using adb devices I was able to see the fire, when typing adb reboot recovery, then adb devices I could no longer cme find the tablet. Well sideload was not going to happen till I could see it again, even tho the tablet was on the recovery prompts. The fix was just checking the driver in device manager after doing the reboot recovery prompt.. Added adb composite to that and then I could find the tablet again, I then sideloaded fine.
Related
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Hi, have you installed adb succesfully in your pc previously?
If yes then the next thing you need is fastboot.exe file, if not then start with that first then fastboot.
You can find what you need here, also if you search in my threads (link in my signature) you can find a tutorial about how to install and use ADB.
~ Veronica
Acclaim
I have the same challenge. I have ADB working successfully (and have used Veronica's guide to repartition my NT - thanks again). Yet when I use Cyanoboot and start Fastboot my device shows up in Other Devices as Acclaim and none of the USB drivers I have pointed to get installed. It isn't mission critical that I solve this but it would be nice from a knowledge base to understand what I am missing in case I ever need to use Fastboot. It seems to be a much easier tool to change the installed Recovery image than ADB. Any help would be appreciated.
adb works for me. i currently have cyanoboot, when i try to go to start fastboot to install a new recovery, i notice in my device manager there is an uninstalled driver called "Acclaim". Already tried the NT drivers for it and it didn't work. Any ideas? I recently flashed succulent's cm7 image which had a cwm v5.0.x and i want to flash cwm v 5.5.x. Already tried using indirect's NT recovery flasher and no go on that...
ShinnAsuka said:
adb works for me. i currently have cyanoboot, when i try to go to start fastboot to install a new recovery, i notice in my device manager there is an uninstalled driver called "Acclaim". Already tried the NT drivers for it and it didn't work. Any ideas? I recently flashed succulent's cm7 image which had a cwm v5.0.x and i want to flash cwm v 5.5.x. Already tried using indirect's NT recovery flasher and no go on that...
Click to expand...
Click to collapse
+1
Can someone upload fastboot mode driver for NT for me? I turn my NT into bootloader but my PC can't "see" NT so I can't fastboot recovery.img.
Thanks.
Sorry for my bad English.
bingoz said:
Can someone upload fastboot mode driver for NT for me? I turn my NT into bootloader but my PC can't "see" NT so I can't fastboot recovery.img.
Thanks.
Sorry for my bad English.
Click to expand...
Click to collapse
when doing fastboot do you see "acclaim" under other devices in device manager? I had to install another set of drivers in order for fastboot to work.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
when doing fastboot do you see "acclaim" under other devices in device manager? I had to install another set of drivers in order for fastboot to work.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
My PC search for driver but I can't install. Would you please send me link to "set of drivers in order for fastboot to work"? Thank you very much
bingoz said:
My PC search for driver but I can't install. Would you please send me link to "set of drivers in order for fastboot to work"? Thank you very much
Click to expand...
Click to collapse
you need to find the id of the nook under other devices acclaim. then you modify the android_winusb.inf file with those new id's and install the drivers
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
you need to find the id of the nook under other devices acclaim. then you modify the android_winusb.inf file with those new id's and install the drivers
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Can you explain more or upload the file already edit for me? Thank you
bingoz said:
Can you explain more or upload the file already edit for me? Thank you
Click to expand...
Click to collapse
each product id is different so uploading the file isn't going to do you much good. sorey
Sent from my Nook Tablet CM7 BETA using xda premium app
mamifsidtect said:
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Click to expand...
Click to collapse
I don't have windows so I won't comment on that. There is one thing that I never see mentioned when talking of adb access problems.
On custom roms (your case cm9 0.05.1) in settings, developer options, Android debugging should be checked to allow adb access. If not checked that may be your issue.
If I'm having adb issues and it was working previously I'll boot to cwm (5.5.0.4 version not 5.0.2 or whatever) and go from there.
You should get adb working properly, but to flash recovery you can use one of the flashable zip files while in cwm. They work for me!
Got a few minutes on a windows 7 pc (people should take their breaks at their desk). If you are using Veronicas thread http://forum.xda-developers.com/showpost.php?p=22049356&postcount=1 you will find a file runmefirst.bat if you run it and follow instructions about unplugging and replugging nook it will create and setup the previously mentioned file. Do not run zergy as suggested. When it pulls device manager your exclamation should say nook. Right click it, update driver software, browse my computer, let me pick, and then choose the directory with your usbdrivers, tell it yes to use them. Do not worry about anything else from runmefirst.bat including anything else to run. You just want it to set the codes for your nt and then it is of on use.
I had adb working for my nt quickly on that windows 7 pc. It had no previous adb or usb drivers installed.
Good Luck
I got nook tablet drivers installed and it works for adb however fastboot still has acclaim!
anyone have steps how to fix this?
fastboot has no devices
nba1341 said:
I got nook tablet drivers installed and it works for adb however fastboot still has acclaim!
anyone have steps how to fix this?
fastboot has no devices
Click to expand...
Click to collapse
like i said in a previous post, right click the acclaim item under other devices and look for the product id and edit the android_winusb.inf accordingly.
after that right click acclaim, update driver software, and browse for the drivers yourself. if all goes well fastboot should work. this is how i did it. not that i ever really use fastboot but its good to have just in case.
Is there any step-by-step tutorial on how to flash NT with fastboot? I have tried to search, but still could not get it work.
Thanks.
mamifsidtect said:
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Click to expand...
Click to collapse
Check your android_winusb.inf to see if you have the right entry for the NT -- see http://forum.xda-developers.com/showpost.php?p=35971559&postcount=13.
---------- Post added at 12:19 AM ---------- Previous post was at 12:15 AM ----------
Penguin101 said:
Is there any step-by-step tutorial on how to flash NT with fastboot? I have tried to search, but still could not get it work.
Thanks.
Click to expand...
Click to collapse
Why not flash your NT using SD-based CWM Recovery (e.g., see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31)?
The easiest way under windows, is just choose the driver on your own, use the driver from the Android SDK (sdk\extras\google), and you will be presented with a couple of options, choose Android Composite ADB Interface.
So not sure exactly what happened while running the lastest paranoid build. Everything was fine until a random reboot happened, said proccess stopped working and rebooted once more except for im on white screen. went to wipe data and reflash the rom but sd card has been wiped. I am s-on and cant get adb to recognize my device. Any advice please.
IceAzures said:
So not sure exactly what happened while running the lastest paranoid build. Everything was fine until a random reboot happened, said proccess stopped working and rebooted once more except for im on white screen. went to wipe data and reflash the rom but sd card has been wiped. I am s-on and cant get adb to recognize my device. Any advice please.
Click to expand...
Click to collapse
go into recovery and try turning adb sideload on then off and see if adb recognizes your device after that.
failed to open driver control: no such file or directory
when i start adb, it zooms really fast through codes and then exits.
IceAzures said:
failed to open driver control: no such file or directory
when i start adb, it zooms really fast through codes and then exits.
Click to expand...
Click to collapse
Then you didn't set adb up correctly
Edit: now that I think of it you may be typing in the command incorrectly.
Sent from my HTC6435LVW using xda app-developers app
Ill reinstall the sdk and drivers and ill report back.
This is the correct way right?
http://forum.xda-developers.com/showthread.php?t=2131284
edit1: so to use adb im using the windows vista cmd promt correct?
edit 2: okay so we are somewhere. Adb now works. I just need to get the dna to be able to be detected. Any way i can do this?
(double post accident)
IceAzures said:
(double post accident)
Click to expand...
Click to collapse
Get into twrp
Find to sideload option.
Select it.
Plug your phone into your computer, make sure to use usb 2.0 not 3.0.
Open up a command prompt where the rom is located.
Type adb sideload rom.zip
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Get into twrp
Find to sideload option.
Select it.
Plug your phone into your computer, make sure to use usb 2.0 not 3.0.
Open up a command prompt where the rom is located.
Type adb sideload rom.zip
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
So i was getting help from another member and I feel like he is getting frustrated as I am. Im running CWM 6.0.2.1 and this is what im dealing with
Device is not recognized even though i have the drivers for it. I heard USB debugging is enabled regardless in recovery I just don't know why I cant push or sideload anything even if im on install zip from sideload.
IceAzures said:
So i was getting help from another member and I feel like he is getting frustrated as I am. Im running CWM 6.0.2.1 and this is what im dealing with
Device is not recognized even though i have the drivers for it. I heard USB debugging is enabled regardless in recovery I just don't know why I cant push or sideload anything even if im on install zip from sideload.
Click to expand...
Click to collapse
CWR has some issues with adb. flash latest version of twrp here:
http://techerrata.com/browse/twrp2/dlx
beaups said:
CWR has some issues with adb. flash latest version of twrp here:
http://techerrata.com/browse/twrp2/dlx
Click to expand...
Click to collapse
Do you think vista might be an interference? Im currently on waiting on device while trying to flash the recovery in fastboot
IceAzures said:
Do you think vista might be an interference? Im currently on waiting on device while trying to flash the recovery in fastboot
Click to expand...
Click to collapse
nope. Vista sucks and all, but it isn't the problem here.
IceAzures said:
Do you think vista might be an interference?
Click to expand...
Click to collapse
There's your problem. "Vista"
Sent from my Galaxy Nexus using xda app-developers app
beaups said:
nope. Vista sucks and all, but it isn't the problem here.
Click to expand...
Click to collapse
So what would you recommend at this point? Because at this rate im surprised my phone is not dead yet. Although i do see the led light in recovery mode
AGoogleUser said:
There's your problem. "Vista"
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yeah and unfortunately its all i got
IceAzures said:
So what would you recommend at this point? Because at this rate im surprised my phone is not dead yet. Although i do see the led light in recovery mode
Yeah and unfortunately its all i got
Click to expand...
Click to collapse
I'd recommend you flash twrp then adb push your rom, then flash it
Okay im going to post the steps and maybe this will be easier for all of us.
1- Flashed Paranoid
2- Flashed crpalmers boot.img in flashgui
3- Phone was good for a solid day, then rebooted.
4- After reboot phone said a lot of the services are force closing and then rebooted into the white htc screen
5- http://forum.xda-developers.com/showthread.php?t=2131284 and followed it to the T
6- phone is not being recognized in adb
7- went to flash the recovery but its waiting on device even though its in fastboot usb
Maybe im missing a driver or a step I am not sure about but hopefully that helps a bit more than posting little by little.
IceAzures said:
Okay im going to post the steps and maybe this will be easier for all of us.
1- Flashed Paranoid
2- Flashed crpalmers boot.img in flashgui
3- Phone was good for a solid day, then rebooted.
4- After reboot phone said a lot of the services are force closing and then rebooted into the white htc screen
5- http://forum.xda-developers.com/showthread.php?t=2131284 and followed it to the T
6- phone is not being recognized in adb
7- went to flash the recovery but its waiting on device even though its in fastboot usb
Maybe im missing a driver or a step I am not sure about but hopefully that helps a bit more than posting little by little.
Click to expand...
Click to collapse
Do you htc's adb drivers installed? Not just the sdk.
Sent from my VIPER DNA
reaverclan said:
Do you htc's adb drivers installed? Not just the sdk.
Sent from my VIPER DNA
Click to expand...
Click to collapse
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot <devices> but still having issues pushing or flashing rom
IceAzures said:
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot <devices> but still having issues pushing or flashing rom
Click to expand...
Click to collapse
When in device manager , how is the unit listed? Does the listing have an yellow exclamation point in front of it?
IceAzures said:
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot but still having issues pushing or flashing rom
Click to expand...
Click to collapse
Might want to unplug from the net when installing them so it doesn't look for others which driver version you installing? EDIT: also if you have a otg cable then you can put the rom on a flash drive and flash it from that.
Sent from my VIPER DNA
IceAzures said:
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot <devices> but still having issues pushing or flashing rom
Click to expand...
Click to collapse
What error is it giving you when you try to push a rom.
Sent from my HTC6435LVW using xda app-developers app
SOLVED- SEE POST #6
Please forgive me if this has been answered- but I have searched through all the posts here on the LG G3 and ADB and can not find a solution.
I have got this far following the guide on ADB Mac- but as you can see from the pic is says that my phone is offline. Changed the MTP to Ethernet to modem- and nada. Is this a facepalm and I am missing something here? many thanks in advance.
rwcasto said:
Please forgive me if this has been answered- but I have searched through all the posts here on the LG G3 and ADB and can not find a solution.
I have got this far following the guide on ADB Mac- but as you can see from the pic is says that my phone is offline. Changed the MTP to Ethernet to modem- and nada. Is this a facepalm and I am missing something here? many thanks in advance.
Click to expand...
Click to collapse
If you look closely, you can tell that the problem is that your not using a pc.
Chilidog said:
If you look closely, you can tell that the problem is that your not using a pc.
Click to expand...
Click to collapse
ahhh... thanks.. I think
Chilidog said:
If you look closely, you can tell that the problem is that your not using a pc.
Click to expand...
Click to collapse
Not even close.
Using ADB on my Mac, is a non issue.
OP make sure you are running the latest version of ADB.
A security feature was added to Android and it will ask you if you want to have that computer authenticated or some such.
If your phone didn't ask you probably have an old version of ADB.
tech_head said:
Not even close.
Using ADB on my Mac, is a non issue.
OP make sure you are running the latest version of ADB.
A security feature was added to Android and it will ask you if you want to have that computer authenticated or some such.
If your phone didn't ask you probably have an old version of ADB.
Click to expand...
Click to collapse
Right on! Thanks man! updating right now!
ADB Working Mac!
follow the guide here http://forum.xda-developers.com/showthread.php?t=1917237
with one addendum- use the attached zip file with latest ADB/Fastboot files and you now have a working solution for ADB on MAC
rwcasto said:
follow the guide here http://forum.xda-developers.com/showthread.php?t=1917237
with one addendum- use the attached zip file with latest ADB/Fastboot files and you now have a working solution for ADB on MAC
Click to expand...
Click to collapse
Glad you got it working.
If I helped don't forget the thanks button.
tech_head said:
Glad you got it working.
If I helped don't forget the thanks button.
Click to expand...
Click to collapse
Humm. Using a Mac with 10.10 Yosemite, I have a D850 on LP 5.01 and have followed the lead in the link given above, and used the dab and fast boot file in the zip just above. My Oneplus's in the house (3), work great. My G3, with new drivers, seen but "offline". It does have USB debugging selected. I have tried toggling that, using the MTP or PTP choices, and both get the same result. I have installed the newest android SDK as well.
frustrating. Any thought would be appreciated.
Solved the issue by uploading another newest ADB file set. G3 is not ween, however, when I run the command "su
restorecon -FR /data/media/0/", adb tells me "command not found"
I do have the newest Android SDK 23.02 tools installed.
Hi there guys,
I'm new to the forum so apologies if this has been posted in the wrong place.
So I was directed to this forum to attempt to solve a different problem but in my hast, I have caused an even bigger problem!
So initially I was having problems with the new Android Wear update with regards to rooting, so I wanted to find a way to roll the software back or restore the device to stock.
I came across this post http://forum.xda-developers.com/g-watch/development/tool-lg-g-watch-return-to-stock-t3158349 and attempt to do as advised, but half way through the process, the program froze. I then tried to reset the watch from the button at the back, but the watch is now stuck on the fastboot menu. I used ADB to see if I could still connect to the device but no devices can be found.
I have checked the device manager and can see the device as "Android Bootloader Interface" but can't seem to get it past the fastboot menu.
Any help would be much appreciated.
Thanks in advance.
just do it again, as long you can get fastboot, you are safe.
Jaocagomez said:
just do it again, as long you can get fastboot, you are safe.
Click to expand...
Click to collapse
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Montezz1 said:
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Click to expand...
Click to collapse
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Xmaster24 said:
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Click to expand...
Click to collapse
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Montezz1 said:
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Click to expand...
Click to collapse
Check the bootloader lock status and report back
Xmaster24 said:
Check the bootloader lock status and report back
Click to expand...
Click to collapse
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Montezz1 said:
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Click to expand...
Click to collapse
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Xmaster24 said:
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Click to expand...
Click to collapse
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Montezz1 said:
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Click to expand...
Click to collapse
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Xmaster24 said:
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Click to expand...
Click to collapse
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Montezz1 said:
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Click to expand...
Click to collapse
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Xmaster24 said:
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Click to expand...
Click to collapse
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Montezz1 said:
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Click to expand...
Click to collapse
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Xmaster24 said:
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Click to expand...
Click to collapse
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Montezz1 said:
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Click to expand...
Click to collapse
This device I just want to know if you ever actually successfully flashed anything to this device
Xmaster24 said:
This device I just want to know if you ever actually successfully flashed anything to this device
Click to expand...
Click to collapse
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Montezz1 said:
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Click to expand...
Click to collapse
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Montezz1 said:
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Click to expand...
Click to collapse
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Xmaster24 said:
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Click to expand...
Click to collapse
I do not believe it...
After all of this, it was the drivers...
I don't get it though!! I tried to reinstall them before and nothing changed!
It's only when I completely deleted them and reinstalled that it worked.
Honestly dude, thank you so much for your help and patience. My watch is now working and paired with my phone.
I'm waiting for it to sync but hopefully I will be able to run ADB and all will be well again
Thanks you so much again.
I am trying to flash a custom ROM on my OPX because the MM builds of OOS have been giving me strange bugs which apparently no one else seems to be experiencing.
So when trying to unlock my bootloader, when I enter the "Fastboot Devices" command, nothing happens. My device isn't showing up no matter what.
I have all the prerequisite drivers installed so I don't know what is causing this.
Any help would be much appreciated.
Mr. Viscous said:
I am trying to flash a custom ROM on my OPX because the MM builds of OOS have been giving me strange bugs which apparently no one else seems to be experiencing.
So when trying to unlock my bootloader, when I enter the "Fastboot Devices" command, nothing happens. My device isn't showing up no matter what.
I have all the prerequisite drivers installed so I don't know what is causing this.
Any help would be much appreciated.
Click to expand...
Click to collapse
Assuming your putting the phone in bootloader mode what version of windows?
Using Windows 10 and yes, when I boot into bootloader mode still there is no device listed under fastboot devices command.
Mr. Viscous said:
Using Windows 10 and yes, when I boot into bootloader mode still there is no device listed under fastboot devices command.
Click to expand...
Click to collapse
Same Here
ADB also won't work
Fixed adb after installing Google usb driver
But fastboot still not detected
Sher1234 said:
Same Here
ADB also won't work
Fixed adb after installing Google usb driver
But fastboot still not detected
Click to expand...
Click to collapse
Yeah mate do me a favor and let me know if you find a solution for this, alright?
Mr. Viscous said:
Yeah mate do me a favor and let me know if you find a solution for this, alright?
Click to expand...
Click to collapse
No success till yet but hopefully someone would help us soon
Mr. Viscous said:
Yeah mate do me a favor and let me know if you find a solution for this, alright?
Click to expand...
Click to collapse
I'm pretty sure it has something to do with Windows 10. And I read somewhere a fix just can't remember. Something to do with rolling back the driver or uninstalling. I believe its written in the hardbrick guide take a look there.
Install USB drivers and 15 second ADB and fastboot drivers then you are good to go. I am also using windows 10 without any problem.adb and fastboot working nicely..even in Linux adb and fastboot working perfectly.
farooque7508 said:
Install USB drivers and 15 second ADB and fastboot drivers then you are good to go. I am also using windows 10 without any problem.adb and fastboot working nicely..even in Linux adb and fastboot working perfectly.
Click to expand...
Click to collapse
Ok I'll try it & let u know
farooque7508 said:
Install USB drivers and 15 second ADB and fastboot drivers then you are good to go. I am also using windows 10 without any problem.adb and fastboot working nicely..even in Linux adb and fastboot working perfectly.
Click to expand...
Click to collapse
This didn't worked I tried this but afterwards doing this I wasn't able to use adb anymore & no luck for fastboot even
I think it's a driver issue but my other device is working so can't say what's exactly happening
Any other idea or method to use fastboot
Sher1234 said:
This didn't worked I tried this but afterwards doing this I wasn't able to use adb anymore & no luck for fastboot even
I think it's a driver issue but my other device is working so can't say what's exactly happening
Any other idea or method to use fastboot
Click to expand...
Click to collapse
Try on an old fashion Win7 computer...
Or a flash drive booting linux distro
Did you try
Install Qualcomm USB driver and check
faap25 said:
Install Qualcomm USB driver and check
Click to expand...
Click to collapse
Can I have the link for this please
@Sher1234 use this and try
http://www.androidbrick.com/download/qdloader-hs-usb-driver/
farooque7508 said:
@Sher1234 use this and try
http://www.androidbrick.com/download/qdloader-hs-usb-driver/
Click to expand...
Click to collapse
I'll surely give it a try tomorrow & let you know if this worked or not
& Thanks for your help
farooque7508 said:
@Sher1234 use this and try
http://www.androidbrick.com/download/qdloader-hs-usb-driver/
Click to expand...
Click to collapse
Not Worked
But I'll try installing Windows 7 and perform the same process this weekend
If you done with installing windows 7
Install OnePlus X drivers you can find it in OnePlus forum
Install 15 sec ADB and fastboot
And check it should work.
farooque7508 said:
If you done with installing windows 7
Install OnePlus X drivers you can find it in OnePlus forum
Install 15 sec ADB and fastboot
And check it should work.
Click to expand...
Click to collapse
Thanks for info I'll install Windows 7 this weekend due to college work
I'll will do it as you said and it will be stepwise
And will inform you if this work or not
Thanks Anyways
Sher1234 said:
Thanks for info I'll install Windows 7 this weekend due to college work
I'll will do it as you said and it will be stepwise
And will inform you if this work or not
Thanks Anyways
Click to expand...
Click to collapse
Don't install Win7 just for that. Find someone who have one.
Or try with a USB booting Linux Distro it will be quicker and easier.
Kéno40 said:
Don't install Win7 just for that. Find someone who have one.
Or try with a USB booting Linux Distro it will be quicker and easier.
Click to expand...
Click to collapse
Ok I'll try it and will report if this works for me or not
---------- Post added at 12:19 PM ---------- Previous post was at 12:13 PM ----------
Kéno40 said:
Don't install Win7 just for that. Find someone who have one.
Or try with a USB booting Linux Distro it will be quicker and easier.
Click to expand...
Click to collapse
But can you tell which Linux OS should I try???
I tried Ubuntu it doesn't install fastboot drivers on live boot so can't use fastboot or adb commands