I have a HTC Google Nexus 9 tablet. I recently received the update to Android 6.0.1 via the normal push notification. The update got stuck on ‘optimizing your apps 1 of 74’. It normally moves up in the numbers within minutes but it remained on ‘1 of 74’ for an entire night. So, the next morning I switched off by holding the power button.
The system still booted but soon enough I received error messages like ‘there is an internal error, contact the manufacturer’ and during the boot it says that my system was corrupted.
I decided on a factory reset. It went through with it. But when setting up the cleaned system, there is another problem: I can pick my language and connect to my WIFi without problem. But then it goes to a screen where it says ‘checking connection. This may take a while.’ It gets stuck there for several hours - so it is clearly faulty as I don’t think ‘a while’ means 12 hours and more. I also don’t think that the factory reset solved the problem anyway as I still receive error messages, hinting at a corrupted system, during and after the boot.
So, I decided to try to flash a system image.
I got the Minimal Android Debugging Bridge ADB and Fastboot on Windows 7 and Ubuntu,
Then I followed the Google developers instructions and downloaded Volantis MOB30D from there.
I also got Android drivers for Windows, but I’m not entirely certain if they are right.
When I connect the Nexus 9 to the Windows computer, I now see in Device manager: ASUS Android Devices -> Android ADB Interface
It’s not an ASUS tablet though and I can’t see the Nexus 9 in ‘Computer’ (it used to show up there as ‘Portable Media player’
Is it possible that I got the wronger drivers and if so, how would I install the correct ones?
Then I start the Nexus 9 and hold power and volume up down to get to the bootloader.
It says ‘Fastboot USB’
I also says ‘device state - locked’ . I can’t get to the system settings to do the OEM unlock as I’m stuck on ‘checking connection’ when I boot normally.
Then I opened ‘Minimal ADB and Fastboot’ on Windows and tried the following commands:
Fastboot flashing unlock
… and it says:
FAILED (remote not allowed)
Then …
Fastboot oem unlock
… and it says:
(bootloader) ability is 0
(bootloader) permission denied for this command
Then I tried the same on Ubuntu. The device doesn’t show in the left hand side panel. When I try the above commands it just says
waiting for device
So, I guess Ubuntu doesn’t even recognize the Nexus 9
I then opened ‘Additional Drivers’ but it just says searching for available drivers and then no proprietary drivers are in use on this system
Any advice for Nexus 9 drivers on Ubuntu?
I also tried from the bootloader: Hboot → Recovery → Apply update from ADB
In Ubuntu I went to the directory where the ZIp file of the system image is located
Then I typed in the terminal:
adb sideload image-volantis-mob30d.zip
And it says …
Error: insufficient permission for device
I’m running out of ideas. Can anyone help?
1. You don't have correct drivers for Nexus 9. The Nexus Root Toolkit has a driver instillation guide.
2. You can not sideload factory images.
Try sideloading the failed ota available here
Code:
April 2016 Nexus OTA Updates - Security Level 2016-04-02
Nexus 9 (LTE) [URL="https://android.googleapis.com/packages/ota/google_flounderlte_volantisg/9ae7d85d6433d055a9e4f3049ac86eb0e562bbf1.signed-signed-volantisg-MOB30D-from-MMB29V.zip"]MOB30D from MMB29V[/URL]
Nexus 9 (Wi-Fi) [URL="https://android.googleapis.com/packages/ota/google_flounder_volantis/6a2119f2077022c1ba852f2c613b8ce942c33836.signed-signed-volantis-MOB30D-from-MMB29V.zip"]MOB30D from MMB29V[/URL]
If that doesn't work try sideloading Android N OTA
aeglyss said:
Any advice for Nexus 9 drivers on Ubuntu?
Error: insufficient permission for device
I’m running out of ideas. Can anyone help?
Click to expand...
Click to collapse
I don't know specifically about Ubuntu, but I've done several updates to usb-connected android devices using Debian linux, and I've never needed to add a device-specific driver.
Some additional ideas on the permissions:
(1) Did you enable "USB Debugging" in Settings->Developer Options?
(2) From your Linux machine, did you try to run adb as the root user or use sudo? I have to do this for both adb and fastboot. (Example command line: '$sudo adb devices', without the quotes.)
(3) Finally on the Linux side, did you try to connect first via adb? And, if so, did you look on your Nexus for an "Enable..." approval notification?
Good luck!
cheers,
john
Thanks everyone. I managed to fix it
aeglyss said:
Thanks everyone. I managed to fix it
Click to expand...
Click to collapse
Hi, I am at a similar point, my Google Nexus 9 failed doing the update, I then tried to factory re-set it and now it is trying to check connections...
I have downloaded the bootloader and my Windws 10 pc can see the tablet via explorer. I believe I have also switched the tablet to Fastboot but bootloader doesn't sem to be able to make the connection.
I was wondering if you are able to provide me with instruction as to how to rescue this tablet. I am not an expert, so I would appreciate any instructions to be as simple as possible.
Thank you for your help,
Mike
Related
I've been trying to root with viperboy's Primetime but when I connect my TF201 to my computer it shows up in device manager only as the TF201 and not as any sort of ADB interface. I've tried all the drivers I can find including those included with viperMOD and Asus Sync. I've followed all the other instructions to the letter. Video tutorials aren't helping because they all seem to effortlessly get ADB going. My firmware is 2.13 and yes, I do have USB debugging ticked on (when I toggle it back and forth device manager does refresh but doesn't seem to connect or disconnect any devices). I've also tried adding legacy hardware and under the Android Phone category there are drivers listed from both Asus and Google for ADB interfaces among other things, but when I try any of them the device ends up with a code 10 (cannot start). I've already spent hours trying just to get ADB going, please help me if you can.
Please help!
fezir said:
I've been trying to root with viperboy's Primetime but when I connect my TF201 to my computer it shows up in device manager only as the TF201 and not as any sort of ADB interface. I've tried all the drivers I can find including those included with viperMOD and Asus Sync. I've followed all the other instructions to the letter. Video tutorials aren't helping because they all seem to effortlessly get ADB going. My firmware is 2.13 and yes, I do have USB debugging ticked on (when I toggle it back and forth device manager does refresh but doesn't seem to connect or disconnect any devices). I've also tried adding legacy hardware and under the Android Phone category there are drivers listed from both Asus and Google for ADB interfaces among other things, but when I try any of them the device ends up with a code 10 (cannot start). I've already spent hours trying just to get ADB going, please help me if you can.
Click to expand...
Click to collapse
I hate to sound like a noob, but I am having the same problem!!!!
I went through the developer forum and found a response from "Ciddy", on the matter, this is the link { http://forum.xda-developers.com/showpost.php?p=21049320&postcount=89 } , this seemed to work for several other people, but not me.
This is what happens:
1. Uninstall Asus Sync (BTW Asus Sync does not detect the TP for me either).
2. Hit Win+R, enter "devmgmt.msc" (no quotes), brings up device manager.
3. Connect the prime, when it shows up in device manager, select it and hit Del.
Then search for new hardware and install the supplied drivers.
4. After the first reboot of the prime, check the device manager, it should show Asus MTP device [ THIS IS WHERE THE DEVICE MANAGER DISPLAYS Transformer Prime TF201, NOT Asus MTP device] with a notification; update its driver from the Viper pack.
ADB does not detect the TP in command promt. Windows 7 64x. Everything is updated, I have ADB from rooting HTC's and several other android device's. I have reset the TP to factory default's twice. and I have read and read, and have not found anything, PLEASE HELP!
** PS. I am only able to transfer files with Windows Explorer.
*** Calling Asus Support was pointless, they aren't even familial with ADB.
I have the Android SDK/Eclipse loaded on my machine so ADB is fine for me, of course. So, cannot help in your situation.
I wonder if you have considered downloading the Android Terminal Emulator from the market and just entering your commands directly on the Prime? The first time I rooted a phone, that's the way I did it, since I had no clue what ADB was. Not a permanent solution to your problem, but perhaps it can get you by for now.
Of course, I may be missing something as to why this won't work...
Edit: I read up on the TPSparky root and Viperboy's tool ... pretty sure at this point that what I am saying above will not work.
Resolved
I resolved the issue. There is still something blocking me from ADBing into the tablet with my Windows PC but I tried on an Ubuntu box and it worked perfectly. I am now successfully rooted.
How did you solve it?
yoinjo said:
How did you solve it?
Click to expand...
Click to collapse
I used a computer running Ubuntu. Never got it working with my Windows laptop.
I installed http://forum.xda-developers.com/showthread.php?t=1426502 drivers and now my TF201 shows under Android Devices (Asus Transformer Prime ADB Interfaces). ADB however still returns error: device not found
So I've solved the problem too.
I've used an old 32bit XP computer with 2.0 USB
I had that problem....i sovled it.......it was me...i forgot to go into settings on the TP and under dev options make sure USB debugging is checked.....after i did that everything went smooth
Sent from my Transformer Prime TF201 using Tapatalk
I'm having a similar problem. I've spent the last three days on-and-off trying to get this thing to show up in ADB.
So far, I've tried using both Ubuntu and Windows 7 (both x64), both detect the device and Windows shows it in Device Manager as "Asus Transformer Prime ADB Interface" - using the Univeral Naked Driver Beta 0.6.
Unfortunately, when I do adb devices, all I get is
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
It's probably worth noting that I previously rooted using mempodroid but (like an idiot) didn't install RootKeeper and when I got the OTA from 9.4.2.11 to 9.4.2.14, I lost root, and haven't been able to make it show in adb ever since.
Can anyone shed some light on this issue? I'm rather missing root.
Any update on this?
When having started the tab normally it gets recognised with device id.
When in fastboot mode - nothing
I installed several driver but the tab does not get recognised (2PCs win7)
YodaDaCoda said:
I'm having a similar problem. I've spent the last three days on-and-off trying to get this thing to show up in ADB.
So far, I've tried using both Ubuntu and Windows 7 (both x64), both detect the device and Windows shows it in Device Manager as "Asus Transformer Prime ADB Interface" - using the Univeral Naked Driver Beta 0.6.
Unfortunately, when I do adb devices, all I get is
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
It's probably worth noting that I previously rooted using mempodroid but (like an idiot) didn't install RootKeeper and when I got the OTA from 9.4.2.11 to 9.4.2.14, I lost root, and haven't been able to make it show in adb ever since.
Can anyone shed some light on this issue? I'm rather missing root.
Click to expand...
Click to collapse
i got here same problem, any progress on this one? did you already found a way to fix this issue? thanks.
YodaDaCoda said:
I'm having a similar problem. I've spent the last three days on-and-off trying to get this thing to show up in ADB.
So far, I've tried using both Ubuntu and Windows 7 (both x64), both detect the device and Windows shows it in Device Manager as "Asus Transformer Prime ADB Interface" - using the Univeral Naked Driver Beta 0.6.
Unfortunately, when I do adb devices, all I get is
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
It's probably worth noting that I previously rooted using mempodroid but (like an idiot) didn't install RootKeeper and when I got the OTA from 9.4.2.11 to 9.4.2.14, I lost root, and haven't been able to make it show in adb ever since.
Can anyone shed some light on this issue? I'm rather missing root.
Click to expand...
Click to collapse
Sorry for asking an obvious question but are you in recovery when you are trying to do adb? If you are then download the nvflash file from dev thread, unzip it, open the folder until you see the adb.exe file.
Press and hold shift on the keyboard, right click in the window and select command prompt here.
Now do adb devices it should show up.
I am having the same problem. I have tried all available drivers on internet from number of forums. Still no luck . I have also tried from Windows 8 64 Bit and Windows 32 Bit laptops. From the same laptop, I was able to connect my Xperia U and it showed under "adb devices". What am I missing? I need to install custom ROM. Please help.
Did anyone solved this problem? I have Win 7 64-bit and have been following a thread on installing Crombi-KK
After adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard, Hairybean TWRP was installed and now i need to boot into fastboot
but adb is no longer working.
I tried reinstalling drivers for TF201 but no adb access.
update1:
Ok. I managed to solve the first problem with no ADB access. In recovery I clicked to Reboot, and clicked System. While system was rebooting I was holding Power Down and got into fastboot mode. I lost ADB access but apparently still have fastboot access so I have proceeded with the instructions to flash blob
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob, then
fastboot -i 0x0b05 reboot-bootloader
In recovery the instructions say format next, so now I am currently formatting, so I will update everyone who need this.
I still don't know why I lost ADB access which I had. Some people here suggested ubuntu but I don't have it.
After formatting I will need ADB to push crombi to device, but I twrp recognizes SD card so if I don't get ADB access after formating I will
try to copy crombi-kk to SD card and then flash it from recovery. I will write what happened when formatting is done.
update2:
After format which took 30 minutes I suddenly have ADB access. Wtf??? Anyway I pushed crombi-kk zip on the tablet and flash it. After 5 minutes of flashing everything working great. Will send a donation. Tablet with stock 4.1.1 was slow 4.4 is great. Thanks everyone who made it possible.
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Have you reviewed the jmztaylor method?
Have you reviewed this method?
http://forum.xda-developers.com/showthread.php?t=1905674
Worked for me after I grabbed the drivers from PDAnet.
I have one issue of Android is Updating stuck in loop that some others in that thread have sorted out but I can't quite get working yet!
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
same problem.
I am having the same exact problem. I have reviewed the jmz method and keep getting stuck in cmd saying path not specified. Any solutions. All steps have been followed to the letter.
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
cruise350 said:
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
This thread goes through doing it manually, it is written for Ubuntu(linux) but it can be used in windows as well, you just don't use sudo for the commands. Also the package in the following thread already has the updated gapps package that does away with the "android upgrading" on every boot.
http://forum.xda-developers.com/showthread.php?t=2016463
fast boot won't install
Had ''path not specified'' it gets to the if stuck here drivers aren't installed. A window pops up saying ''installing fast boot'' but then says it failed. Thats where im stuck.
4.1.1 OS
2.4 product version
Thinking the 2.4 update is a problem.
Any suggestions?
I know i'm years late here but I really HATE adb and esp. BAT files that are just suppose to do their thing........I'm hitting a wall with this Nabi 2 Bat file for TWRP / ROOT. I've used PDAnet plenty in the past for internet but never for the purpose of just getting drivers so I have no idea I hate that program too. ANYWHO , I'm getting "cannot find specified path" which I probably could fix if I ****ing knew which ****ing path it was looking for. SO if anyone could please enlighten me here , I've installed and uninstalled PDA net some 10 times now , with Samsung selected , with LG selected with OTHER selected , I cannot get this to work. I can do FASTBOOT devices , and poof it shows up , adb works fine all that , show the device but I cannot get this ****ing BAT all in one installion to work. I'm really just about to flash it all manually through ADB but I'd rather use the installer to make sure I get the random WINGS files removed or whatever. Any help would be great , thanks.
I have a rooted Google Nexus 10 tablet with Clockwork Mod and Android 4.4.2. The Google USB driver worked fine on my Windows 7 laptop and I was able to use adb to push files to my tablet. I foolishly let the automatic 4.4.3 OTA download and install. Now, my tablet is stuck in bootloop AND Windows has completely forgotten my Google USB driver and thus adb can't see the tablet, so I can't transfer over the 4.4.3 image or flash in Clockwork Mod via sideload. Yes, Clockwork Mod works great and I can boot into recovery mode. I've seen a thousand postings that all talk about stuff you do from Android like enabling USB debugging, etc, but this is all worthless when you can't boot Android. In retrospect, I wish I had kept a backup image on my SD card. So three questions:
1. How can I get the update image onto my tablet, either by sideload or adb push?
2. Is the factory image (4.4.3 (KTU84L) ) correct or since I'm rooted, am I supposed to use a modified one?
3. Would the manual update method be as simple as copying over the factory OTA to my SD Card ahead of time, booting into recovery mode and flashing?
Thanks in advance to anyone who can help.
Well, no response from anybody. I just saw this on another post: "Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT. "
This is very informative. I just wonder if "adb devices" ever shows anything if you're in recovery mode. I wonder also if the Windows 7 driver is supposed to work. I have a feeling this driver is based on communicating with Android itself, so of course it won't work. So maybe fastboot is the way to go? That's what I'll try next.
fastboot
This looks relevant - it has a ton of fastboot commands:
http://forum.xda-developers.com/showthread.php?t=2024259&page=3
So I am no stranger too rooting, but i managed to do something wrong when dirty flashing a rom update.
Gapps no longer works, my device is un-rooted and the 'gapps stopped working' notification pops up every 1 second, making my device unusuable.
I'm using the Amazon Fire 7" running SlimLP. To be clear, this was all working at a point.
I could boot TWRP and fix this with a backup I made, but here's the problem: Fastboot commands isn't working.
I can use ADB and boot into fastboot mode, but once there my commands have no effect and the Windows 7 CMD just displays <waiting for device>.
Also, my stock recovery seems to be deleted so I have no recovery whatsoever.
I have all the correct drivers and used the google sdk drivers to no effect. Also, in device manager my device shows up as 'Android Bootloader interface' and shows: This device cannot start. (Code 10).
So to Sumarise
My device needs a backup flashed
Fastboot commands are unresponsive
I have no root.
I have all the drivers installed
I am using a 2015 Kindle fire 7"
With a windows 7 64 bit laptop
Please help!!!
Thanks in advance
If you need any more info, drop me to a comment and I will get back to you ASAP, I'm desperate!
I can use flashfire, and Im open to any workarounds.
amaramar2000 said:
So I am no stranger too rooting, but i managed to do something wrong when dirty flashing a rom update.
Gapps no longer works, my device is un-rooted and the 'gapps stopped working' notification pops up every 1 second, making my device unusuable.
I'm using the Amazon Fire 7" running SlimLP. To be clear, this was all working at a point.
I could boot TWRP and fix this with a backup I made, but here's the problem: Fastboot commands isn't working.
I can use ADB and boot into fastboot mode, but once there my commands have no effect and the Windows 7 CMD just displays <waiting for device>.
Also, my stock recovery seems to be deleted so I have no recovery whatsoever.
I have all the correct drivers and used the google sdk drivers to no effect. Also, in device manager my device shows up as 'Android Bootloader interface' and shows: This device cannot start. (Code 10).
So to Sumarise
My device needs a backup flashed
Fastboot commands are unresponsive
I have no root.
I have all the drivers installed
I am using a 2015 Kindle fire 7"
With a windows 7 64 bit laptop
Please help!!!
Thanks in advance
If you need any more info, drop me to a comment and I will get back to you ASAP, I'm desperate!
I can use flashfire, and Im open to any workarounds.
Click to expand...
Click to collapse
Please don't cross-post; found this exact text in three different threads. My earlier response here. Others have basically said the same thing. You're done.
Hi all,
I need your help. Given what I already (unsuccessfully) tried, I'm not sure if there will be a solution, at all...worst case, my Huawei Smartwatch isn't usable anymore,,,
Given that there is a preview version of WEAR Version 2.0 available, I thought it might be good idea to install and test. In fact, given that I manually/successfully installed the WEAR Version 1.4, some months ago, I was sure that I can manage to do it, with the preview version, as well.
I followed the steps, which you can find here developer.android.com/wear/preview/downloads
The point is, after the update has been done (given the message in ADB) the Smartwatch didn't automatically start to reboot. I was waiting about 30- 40 minutes, but nothing happened. So, I rebooted the watch by my own, via the fastboot menu.
But, the watch was only booting up to the Huawei Logo and nothing more did happen. I was also waiting for 30 - 40 minuntes.
After that, I googled and found a way how to access the fastboot mode (long and shore pressing of the power button of the watch) Here I tried the possible options. But, I would say, the only option which worked was "shutdown". All the other option, except fastboot recovery, brought me to the same result, as described above. Finally, I tried fastboot recovery, which might have made the situation even worse...means, after the Huawei Logo I can see a fallen over "android" with a open flap / a sign with a bang plus some text lines. But, it's so fast disappearing, nobody can read...even this is coming up again and again.
Next what I wanted to try is, to flash the WEAR version 1.4 again. But, it seems to be that ADB doesn't find the Huawei device anymore. (command ADB Devices doesn't show me any device)
Meanwhile, even it is somehow not logical (as it was working before with my "Standard Win 10 PC and the drivers installed) I tried 3 different PC with different combinations of Windows Version (7,8, 10), USB Ports (2.0 and 3.0) and probably almost all Android USB Drivers you can find.on the WEB. I even followed a procedure how to modify the INF file with some HUAWEI specific entries. I also let the watch run, overnight, in the loop mode, so the battery got empty..which really didn't help, as once loaded again, the watch started with the "loop procedure" again. However, I tried all the steps I did before, once again.
Regarding ADB/Fastboot, I'm not using the full Android SDK package, but the minimal version, at first version 1.1.3 and the later 1.4.3. I also followed the hints to open a command line with shift and right click "in" the respective ADB folder.
So, as you can read, I already tried a lot of thinks with no luck. in fact, I wasn't able to find anything more when I googled.
Hope you / some Android "guru's" can help me, now.
Here some of my current thoughts to which you have answers/comments.
1. Could it be, that the watch is totally broken and can't be "repaired" anymore?
2. Could it be, even the watch is in the fastboot mode, that the watch really isn't in a "full" one (...because the upgrade procedure of WAER 2.0 somehow failed) and this might be the reason, why ADB can't find the device anymore?
3. If 2. is really the case, is there any way to force a "full" fastboot mode?
4. Do you have any other idea, what can be done to make ADB aware of the device?
5. Is there meanwhile a specific ADB driver for the HUAWEI watch available? / Can somebody send me a link to a driver which is definitely working with that watch.
6.Whatever you can think of.
I really would appreciate any help to get my problem fixed.
Thanks in advance
Claus
TL;DR
When you used flash-all.bat it wipes your userdata partition. That means all settings are back to default. So no developer options, no adb debugging.
You can only use fastboot.
Code:
fastboot devices -l
needs to show your device.
- Then untargz the factory image.
- unzip the *.zip
- print out the flash-all.bat (or open in an editor)
use these commands:
Code:
fastboot flash bootloader bootloader-sturgeon-nvd36i.img
fastboot reboot-bootloader
sleep 5
and now flash each image in sequence (boot, cache, recovery, system, userdata.img
fastboot's 2nd param is like the basename of the corresponding .img file
Hi ranf,
first of all, THANKS A LOT, my watch is alive, again.
FYI, what I did...both ways are working, but as I saw, that you updated the procedure, I did the flash the watch two times. To add, I flashed the WEAR 2.0 Preview version.
1. The normal flash process by using one IMG and the one ZIP file, following the steps in the flash-all.bat.
2. Your updated "version", means the IMG file, plus all IMGs (extract from the ZIP file) plus the steps you have written, above.
I just finnished number 2 and the watch is synchronizing..looks good so far.
Thanks
Claus
Nice.
I have the suspicion that this "sleep 5" (seconds) sometimes is not enough.
I did All the steps, but my watch is stucked in moving circles screen