Hello, first off all I will thank all the help you can provide,
My problem, My urbane was running AW 2.0 but it made it laggy I unlock the bootloader and flash it with the 4 cores boot.img from this thread (I did not root or install twrp) then I realize OTA wont get into my urbane so I flash the stock boot.img from the same thread above, then uptade via OTA, all fife until here.
Then I try to reload the 4cores boot.img and my problems started. after this the watch wont start anymore and stay boot animation. but was responsive to adb reboot bootloader commands so I then flash stock boot.img but also didnt boot (even waiting over 20 mins) then as I had img files (BOOT, RECOVERY and SYSTEM to restore it to original AW v1.5 i tried flashing that boot.img from this thread the MM-boot.img flashed didnt help either. then I pressed the button for 20 secs and watch reload and even when it sounds how to is detected as USB on my computer and it is shown as "Android Bootloader Interface" on the device manager it never ever is shown under adb devices command. whatever I do it does not shown under devices attached so I can flash back factory boot, recovery and system images.
So if I start the watch stays forever on the boot animation, and if I swipe my finger at start to boot into bootloader is detected by windows as "Android Bootloader Interface" but "adb devices" command wont show the watch.
Help Please!!!!
Ale.
If manually start my device in bootloader it is detected by windows device manager, but when I type "adb devices" have nothing but if I set manually to bootloader then to recovery mode and then I select apply update from ADB, then watch is again detected by device manager, in this case and ONLY this case adb devices shows my watch but only as sideload ("my serial number" sideload) what can I do there? I cant use fastboot commands.
The things is that I think I wipe data and factory reset the watch and now I dont have adb debugging enable and cant so fastboot commands what can I do, please? is tehre a way to enable adb debugging without being able to boot the watch? can I sideload (as is the only way adb see my watch) the full "NXH19X_full_factory.zip" I tried "adb sideload NXH19X_full_factory.zip" but strat to write into the watch but gives error 21 and close after few seconds.
Please Help.
Ale.
**UPDATE**
Even when adb devices wont show my watch I was still able to flash factory images and is all working now.
This issue is over, close thread please and thanks.
I'm expecting the same simptoms and issues over here. All happens after to flash the 4 core img. Sudelly stucks. Please let me know if you have any news about
Related
I'm not sure what I've done wrong/what I should do.
I'm using the process I've seen outlined a million places where you unlock the boot loader, flash a recovery image then run the SU package from the SD card.
Initially I'm trying just to get stock Gingerbread to work.
I managed to get the bootloader unlocked, but now, whatever I do, I can't flash a recovery image. Every time it says "waiting for device", and any other adb commands either indicate a blank line (requesting devices of usb) or say there is no device.
I've tried the latest SDK drivers as well as the ones here (http://forum.xda-developers.com/showthread.php?t=613217)
I half think this is a USB problem, but I'm just not sure.
In USB it shows up as "Android Phone" and then things like "Android Bootloader Interface" or "Android ADB Interface"
Booting into the OS, it works fine for file transfer, and I don't get any USB Error in Debug mode.
If I try and run the recovery, I get the triangle with an exclamation point, so I assume I've at least altered recovery.
If I try and re-run the unlock boot loader, it tells me its unlocked, so it can, at least, the see the phone.
I'm on 7x64, running the command prompt as Administrator. The phone is in Fastboot (Red Fastboot USB on screen) and it says Unlocked in Pink at the top.
Thanks for any ideas you guys have,
Scott
Ok, this goes in the "would be nice to understand, but no longer a problem" bucket. I was able to use fastboot-windows to flash the recovery and I managed to load the SU file. This other Fastboot came from a file called paul/fastboot.zip. I'm not sure why it works and the one in the SDK doesn't...
Scott
Ok I have an issue, I tried to install a ROM using TWRP and after it finished installing I rebooted and got stuck in a boot loop on the bootloader screen (the screen you get to when you hold down the power button and down on the volume). I read online somewhere that I have to relock and unlock my phone which I proceeded to do, but as you may know that deletes everything off of your SD card. Then I went into cmd and used the code
fastboot wipe cache
fastboot flash recovery recovery.img
I can now get into TWRP but I have no rom to restore to, no back up and when I go to Advanced Adb Sideload, then swipe to download it says
"Adb Sideload Complete" (at the top)
"Failed" (in red right below it)
I know I have to do something with adb or fastboot, but when I type Abd Devices into cmd I get the picture below which says:
List of devices attached
FA34PS901853 recovery
I cant adb push or install and I have NO clue what to do
But im pretty sure that I somehow have to reinstall Superuser so some help with that would be much appreciated as well
PLEASE O PLEASE can someone help me with this
Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic
Hello,
I tried to install the new andoird wear 5.1.1 from this guide: http://forum.xda-developers.com/g-watch-r/general/install-android-wear-5-1-1-to-lg-g-t3114528
and after step 4 i close the "fastboot flash system system_gwr_5.1.1.img" before the install is done (i wait an hour and nothing append).
And now i stuck on the LG logo.
I tried to install again by the guide, but i cant use fastboot, it's write "wating for device".
What to do?
Thanks!
Edit: now the watch reach to the Android system but I have problem with the touch screen that not response. And because of that I can reach to the bootloader and the recovery mode...
Try to hardreset the watch. When you start your watch up and see the LG logo wipe fron 11 to 4 accros the screen.
Genna7 said:
Try to hardreset the watch. When you start your watch up and see the LG logo wipe fron 11 to 4 accros the screen.
Click to expand...
Click to collapse
The touch screen doesn't work after I tried to update the Android wear.. So I can't go to the bootloader...
Someone? Please help!
I am willing to pay to the person that will help me find a solution.
Please help!
Have you figured this out yet?
Spyderekz said:
Have you figured this out yet?
Click to expand...
Click to collapse
No. You also have this problem?
There is a lot of people with this problem in this forum...
Someone know a place that specializes in android wear watches? (please send me, no one knows how to solve this problem here )
try the adb command "adb devices" and "fastboot devices"
I don't think the first one would work (because you are in fastboot mode), but the second should tell if the pc "sees" the watch!
I had to manually install the "android adb composite" device driver in the win device manager...
TML1504 said:
try the adb command "adb devices" and "fastboot devices"
I don't think the first one would work (because you are in fastboot mode), but the second should tell if the pc "sees" the watch!
I had to manually install the "android adb composite" device driver in the win device manager...
Click to expand...
Click to collapse
The computer does not recognize the watch at all...
same here
well, same here: no touch screen, device is not recognized (but boots up to welcome screen) => not able to get into bootloader. Guess, I have to activate developer/debugging mode in the Wear-settings to get it recognized. But how, without touch? Any ideas?
So do you think there is hope for unbricking the watch R from that state ? (mine is the same)
Maybe LGFlashtool will work ? maybe TOT firmware file will be available ?
I am having the same issue after trying to install the stock rom, probably a wrong rom. The watch boots onto a lg logo, stays for a minute or so and reboots into a a boot loop. There is no way to access bootloader or fastboot. Swipe to enter bootloader does not work, tried hundred times, it is like the screen were unresponsive. I have no idea what to do, seems it is bricked.
If I keep pressed the physical button then reboots but lg logo again after a long vibration. Drained the battery, put it on the cradle and then boots onto the lg logo.
anyone?
anyone here has found a solution for this issue?
I am also in the same situation. LG logo stuck after installing a new rom, unresponsive screen no mather if connected to the charger or not. Tried with different computers and OSses, the watch is not recognised.
had this problem as wrong I used the wrong kernel, but I managed to make it work again. this is what you have to do is boot it to bootloader mode, then go to recovery mode and use the "apply update from adb" function (sideload in other words) to install the Android 6.0.1 again.
Link to download Android 6.0.1.
To put the watch in bootloader mode, follow the instruction in my youtube video here.
As soon as it is in bootloader mode, your computer should see the watch as an android device now.
In Bootloader mode, go to recovery mode (use the virtual buttons on screen), then go to the "apply update from adb" option.
Now, at this step, you need to open command line on your computer and type "adb sideload <android file>", where the <android file> is the one you download earlier. You can just type "adb sildeload" then leave a space and drag the file to the running Cmd window.
Now just wait for it to complete and restart itself.
Hope this help.
johnnyle7 said:
had this problem as wrong I used the wrong kernel, but I managed to make it work again. this is what you have to do is boot it to bootloader mode, then go to recovery mode and use the "apply update from adb" function (sideload in other words) to install the Android 6.0.1 again.
["h**ps: //android. googleapis.com/packages/ota/lge_bass_bass/7252d535d6a18047daaf3bfd4745f1c86ef7e7f1.signed-bass-ota-2576000.zip"] to download Android 6.0.1.
To put the watch in bootloader mode, follow the instruction in my youtube video ["h**ps: //w*w. youtube.com/watch?v=ZmBY9KM1NE8"].
As soon as it is in bootloader mode, your computer should see the watch as an android device now.
In Bootloader mode, go to recovery mode (use the virtual buttons on screen), then go to the "apply update from adb" option.
Now, at this step, you need to open command line on your computer and type "adb sideload <android file>", where the <android file> is the one you download earlier. You can just type "adb sildeload" then leave a space and drag the file to the running Cmd window.
Now just wait for it to complete and restart itself.
Hope this help.
Click to expand...
Click to collapse
There is no way to put watch into bootloader mode since screen does not respond.
jogo said:
There is no way to put watch into bootloader mode since screen does not respond.
Click to expand...
Click to collapse
did u watch the video in one of the posts above?
johnnyle7 said:
did u watch the video in one of the posts above?
Click to expand...
Click to collapse
I did. The screen does no respond to touch so 11 to 4 does not work either. I hace tried hundred times and even tapping with 2 fingers which I have seen working in any other vídeo around
same over here.
And this happened without tryng to hack anything (for once in my life)
any update?
I have not received the OTA update to Marshmallow yet and getting impatient so I'm attempting to sideload the update myself. I've installed the SDK and drivers. The device is listed when I use 'adb devices' at the command prompt and it allows me to boot into the bootloader. But from there it disconnects from my computer and I'm not able to push the update to the device. I get "error: device '(null)' not found". Any advice?
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Didgeridoohan said:
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Click to expand...
Click to collapse
Ok, but all the instructions I'm finding online to sideload the OTA say to type "adb sideload [the full name of the file].zip". This is after enter Recovery Mode and select "apply update from adb"
I typed "fastboot devices" and my device came up in the bootloader. I click into Recovery Mode and the computer makes the disconnect sound. That's where I'm cut off.
Have you tried unplugging and plugging in the usb again after entering recovery?
Didgeridoohan said:
Have you tried unplugging and plugging in the usb again after entering recovery?
Click to expand...
Click to collapse
I ended up trying NRT and caused even more problems at first, so I ended up just flashing the update instead of sideloading it. I was freaked out for a while because it was stuck in the boot sequence but as of right now, it's working and I have 6.0.
Yay!
ok, sideloading is for twrp recovery. but thats not needed anymore as you can just move files in and out of twrp without adb. flashing factory images is only via fastboot while you are in bootloader. adb and fastboot are different.