I attempted to install the custom OS, Asteroid, to my Zenwatch 2 (Sparrow) I followed the directions and now the watch will not boot, it is stuck at the Asus screen in a loop. I downloaded the recovery image, but I can not flash it do to Windows not recognizing the watch is connected. ADB gives me the error Device '(null)' not found. I have checked the device manager and there is nothing showing as an error (yellow !). Is there anyway I can recover from this?
jnelsoninjax said:
I attempted to install the custom OS, Asteroid, to my Zenwatch 2 (Sparrow) I followed the directions and now the watch will not boot, it is stuck at the Asus screen in a loop. I downloaded the recovery image, but I can not flash it do to Windows not recognizing the watch is connected. ADB gives me the error Device '(null)' not found. I have checked the device manager and there is nothing showing as an error (yellow !). Is there anyway I can recover from this?
Click to expand...
Click to collapse
go into fastboot mode and reflash your system.
dont work with fastboot / adb / root when you have no idea what youre doing!
matze19999 said:
go into fastboot mode and reflash your system.
dont work with fastboot / adb / root when you have no idea what youre doing!
Click to expand...
Click to collapse
The problem is that the watch is not being detected by Windows, therefore I am unable to reflash it, I clearly stated this in my original post.
jnelsoninjax said:
The problem is that the watch is not being detected by Windows, therefore I am unable to reflash it, I clearly stated this in my original post.
Click to expand...
Click to collapse
You said windows can't detect the watch in adb mode? What about the fastboot mode?
matze19999 said:
You said windows can't detect the watch in adb mode? What about the fastboot mode?
Click to expand...
Click to collapse
No, issuing the command: Fastboot devices shows nothing connected at all(the same goes for adb). It also does not show up in the windows device manager.
jnelsoninjax said:
No, issuing the command: Fastboot devices shows nothing connected at all(the same goes for adb). It also does not show up in the windows device manager.
Click to expand...
Click to collapse
Did you enter the fastboot mode?
matze19999 said:
Did you enter the fastboot mode?
Click to expand...
Click to collapse
The watch is showing CSC Fastboot Mode! So I would assume that it is in Fastboot mode
Were you able to get this fixed?
No, I have but been able to resolve this issue. It is not being recognized by Windows, therefore I can't flash the original os back to it.
Did you have TWRP installed prior to the failed flash?
CVertigo1 said:
Did you have TWRP installed prior to the failed flash?
Click to expand...
Click to collapse
No
I may have a way to get it working. I've had issues where Windows would not recognize a device, until I installed a cocktail of random drivers that eventually worked. What version of Windows are you running?
CVertigo1 said:
I may have a way to get it working. I've had issues where Windows would not recognize a device, until I installed a cocktail of random drivers that eventually worked. What version of Windows are you running?
Click to expand...
Click to collapse
I am running Windows 10 X64 build 1803
If you have the space, follow this: https://docs.microsoft.com/en-us/windows/wsl/install-win10
It allows you to run non-graphical Ubuntu on top of Windows. I've found sometimes my Windows 10 PC won't recognize things with adb or fastboot, but it works great in Ubuntu Bash. If you're familiar with Ubuntu at all, then it'll be a breeze to figure it out. If not, it's a pretty straight forward learning curve. It's also child's play to get adb and fastboot working right in Ubuntu, whereas it can be finicky in Windows.
Another alternative is to make a Linux Live CD using a USB drive, but that is a much more temporary solution.
---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------
If none of those sound appealing, then I'd suggest deleting all drivers having to do with adb or fastboot, and start fresh by installing everything with this https://forum.xda-developers.com/showthread.php?t=2588979
CVertigo1 said:
If you have the space, follow this: https://docs.microsoft.com/en-us/windows/wsl/install-win10
It allows you to run non-graphical Ubuntu on top of Windows. I've found sometimes my Windows 10 PC won't recognize things with adb or fastboot, but it works great in Ubuntu Bash. If you're familiar with Ubuntu at all, then it'll be a breeze to figure it out. If not, it's a pretty straight forward learning curve. It's also child's play to get adb and fastboot working right in Ubuntu, whereas it can be finicky in Windows.
Another alternative is to make a Linux Live CD using a USB drive, but that is a much more temporary solution.
---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------
If none of those sound appealing, then I'd suggest deleting all drivers having to do with adb or fastboot, and start fresh by installing everything with this https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
OK, I will mess around and see what happens! I will have to do it tomorrow, but I will play around and see what happens!
Let me know how it goes and I'll walk you through it some more.
Any luck?
Sorry for the long time to reply. I installed ubuntu in window and installed the appropriate packages, however both ADB and Fastboot show nothing connected, even though the device is in CSC Recovery mode. Is there anything else I can try?
I actually tried playing with a few things on one of my computers the other day to try tracking this down. I was running into an issue where adb worked normally when the watch booted, but it would not work in recovery, and fastboot did not work either. Here is how I fixed it. Open up device manager in Windows and delete any driver pertaining to Android phones or adb. In my example, an Asus driver was causing the problem. I deleted that and reinstalled the generic Google drivers using the 15 second adb/fastboot installer that I posted in this thread. After restarting the computer, adb works perfect in Android and recovery, and fastboot works perfect as well.
TL/DR Delete all Android adb drivers in Windows, then run the 15 second adb installer that I posted in this thread, restart, and get your watch back to normal.
Assuming your bootloader is unlocked, you can flash everything I have posted here to get it running. https://forum.xda-developers.com/zenwatch-2/development/sparrow7-1-1debloat-rom-t3800067 If the bootloader is not unlocked, fastboot oem unlock will do it.
CVertigo1 said:
I actually tried playing with a few things on one of my computers the other day to try tracking this down. I was running into an issue where adb worked normally when the watch booted, but it would not work in recovery, and fastboot did not work either. Here is how I fixed it. Open up device manager in Windows and delete any driver pertaining to Android phones or adb. In my example, an Asus driver was causing the problem. I deleted that and reinstalled the generic Google drivers using the 15 second adb/fastboot installer that I posted in this thread. After restarting the computer, adb works perfect in Android and recovery, and fastboot works perfect as well.
TL/DR Delete all Android adb drivers in Windows, then run the 15 second adb installer that I posted in this thread, restart, and get your watch back to normal.
Assuming your bootloader is unlocked, you can flash everything I have posted here to get it running. https://forum.xda-developers.com/zenwatch-2/development/sparrow7-1-1debloat-rom-t3800067 If the bootloader is not unlocked, fastboot oem unlock will do it.
Click to expand...
Click to collapse
OK, I got windows to see the watch via fastboot and I downloaded the image that you posted (bloat free) now the watch started to boot, but so far it is just showing spinning dots, and has been for ~5 minutes or so, is this normal?
Related
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
TjPhysicist said:
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
Click to expand...
Click to collapse
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
osikiri said:
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
Click to expand...
Click to collapse
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
TjPhysicist said:
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
Click to expand...
Click to collapse
Ok, does anyone know how to get my computer to recognise my watch in recovery mode? It's not about 'driver' the computer plain doesn't recognise that anything is plugged in at all.
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Wikiwix said:
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Click to expand...
Click to collapse
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
mrkrabs said:
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
The problem, as @osikiri stated, is that the device does not get recognized at all (no unknown devices in devicemanager and the sound that comes on plugging in a device does not come as well). Furthermore, afaik Linux does not even need any drivers
Had the same issue today... and the only way out way battery death and recharge
JaceAlvejetti said:
Had the same issue today... and the only way out way battery death and recharge
Click to expand...
Click to collapse
If this really helps (seems weird): I guess the exact setting could be necassary:
You simply ran out of battery while the watch was running(not recovery or fastboot) and then plugged it in and went directly (or not?) to the recovery?
Thanks in advance, would be really great to fix this!
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
MSigler said:
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
Click to expand...
Click to collapse
I'm doing the same thing and having the same issues!
Yeah, same issue for me as described.
Windows (Win7 x64 for me) doesn't even realise that the device is connected when it is in recovery mode. Although it will connected properly when booted normally.
+1 Any ideas?
Same issue for me. I've tried removing and replacing it on the cradle, killing and restarting the adb server, entering recovery by the touchscreen or by the adb/fastboot commands, clearing debugging keys, etc... Anybody have any other ideas?
---------- Post added at 07:25 PM ---------- Previous post was at 06:46 PM ----------
Ok, so it appears that the recovery img on 4.4w2 broke adb support or something. There are a few threads that suggest you can root and flash it or just wait for the OTA. We'll see whether I get the OTA before I have time to try this out.
Lollipop OTA Update: Download and How-To (Root Required)
I made a script that roots and updates your watch to 5.0.1 in a click.
[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool
My way of doing it
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
fi thought it was finally the solution, but fastboot oem unlock bricked my sony smartwatch3. I see tomorrow if with my windows pc i can fix with sony companion, otherwise i'll have to use the warranty
willisc said:
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
Click to expand...
Click to collapse
I just got this thing and also my first LG as I've left samsung and I am a bit confused at this point. Normally not seeing it in fastboot was just go install the drivers which I did but still not getting anything. Suggestions?
Never mind hit it with a hammer and it's working now. Just had to fix it the old way to get it to show up.
I'm running into what sounds like the same issue as you. ADB found my device and Windows found the device drivers and showed the device properly in my Device Manager. Once rebooting into the bootloader Windows no longer found a driver that it was able to use hence when running "fastboot devices" nothing was listed. Once you get into the bootloader does your phone in the device manager show up as a usable device or a device with no drivers? I'm betting you're in the same boat as me.
I've trying different drivers but I've tried:
- LGMobileDriver_WHQL_Ver_4.0.3
- LGUnitedMobileDriver_S51MAN313AP22_ML_WHQL_Ver_3.13.2
- LGUnitedMobileDriver_S498MA22_WHQL_ML_Ver_2.2
- LG-Mobile-Driver_v3.14.1
- adb-setup-1.4.3
- Google USB drivers in the Android SDK Manager
---------- Post added at 10:20 PM ---------- Previous post was at 09:30 PM ----------
Hey I got mine figured out. Hopefully yours is the same issue so here's what I did. The drivers that worked for me was "LG-Mobile-Driver_v3.14.1" which you can find by googling. After installing that Windows should see your device in the device manager which should allow you to run the adb command "adb reboot bootload." This will reboot the phone in the bootloader. When I checked my device manager, the phone only showed up as "Android." I had to update the drivers and then choose "show me a list..." and then choose ADB device. What's weird for me is that it showed me "Samsung ADB." I said eff it and went with it and it loaded and then I was able to run the unlock my phone with the fastboot oem unlock command.
I have no idea if that should have worked or not. Give it a go at your own risk tho. I'm by far not an expert so beyond what I've done, not sure if I could help you if you ran into any other issues.
Which Windows version are you using? Mine is Windows 10 and my device (V10 961N) still doesn't show up in device manager after downloading your recommended driver version?
I still have XP on my work laptop. While the phone was being recognized by ADB I couldn't get fastboot working either. It kept telling me that it was missing a couple dll files. Once I installed those it was smooth sailing. They're on a flash drive at work or else I'd tell you what they were.
Sent from my LG-H901 using Tapatalk
0dBu said:
I still have XP on my work laptop. While the phone was being recognized by ADB I couldn't get fastboot working either. It kept telling me that it was missing a couple dll files. Once I installed those it was smooth sailing. They're on a flash drive at work or else I'd tell you what they were.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Thanks. Would appreciate to get your help. I can see the device via the 'adb devices' command if I am in normal mode on my phone. Installed driver seems to work there. Doesn't tell me that I am missing any dll files. When going into download mode and seeing the Firmware Update screen the device does not show up in Windows. So am unable to go into fastboot.
RiffyDivine said:
I just got this thing and also my first LG as I've left samsung and I am a bit confused at this point. Normally not seeing it in fastboot was just go install the drivers which I did but still not getting anything. Suggestions?
Never mind hit it with a hammer and it's working now. Just had to fix it the old way to get it to show up.
Click to expand...
Click to collapse
Please, how did you fix this Issue ??? I'm having exactly the same problem with my LG V10 (H901)... I cant use fastboot commands, it just freezes and say waiting for any device... Fastboot doesn't see it but ADB does. Please Help!
I cannot get my h901 to get recognized in Fastboot Mode.
Aywhy93 said:
Please, how did you fix this Issue ??? I'm having exactly the same problem with my LG V10 (H901)... I cant use fastboot commands, it just freezes and say waiting for any device... Fastboot doesn't see it but ADB does. Please Help!
Click to expand...
Click to collapse
I am facing the exact same issue.
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Download mfastboot and redownload the recovery img
hetor99 said:
Download mfastboot and redownload the recovery img
Click to expand...
Click to collapse
Thanks.
Decided to install it on my desktop. While trying various files, my laptop accidentally got hit with Chromium virus. It looked like all required files were there, but kept having problems with a couple of those sdk files (tools/platform tools).
I'm still getting the following error:
( bootloader) has-slot :recovery: not found
And once again the Android SDK Tools and Android SKD Platform-tools that are under Tools (preview channel) are unchecked. Not sure if they are needed.
Follow the instructions of how to install on the general section
hetor99 said:
Follow the instructions of how to install on the general section
Click to expand...
Click to collapse
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
L8Show said:
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
Click to expand...
Click to collapse
How to Install TWRP Recovery and Root MOTO E
https://www.youtube.com/watch?v=9Jh-O2LGL3Y
OK, it is done.
Took a couple days with several hours of clicking, and checking settings, and reading and researching, and watching videos, and downloading, and installing/uninstalling, and restarting, but it's now rooted! Way too much time wasted even though it was raining and the gf and I were just watching movies for a lot of it. She kept asking me why I'd waste so much time and remind me I had a perfectly fine iphone nearby. Today I finally got to the point where I had given up. I figured something was screwed up with the phone after that reset on my computer.
Some highlights that may or may not be helpful for the next moto e rooter:
USB debugging was somehow switched to off a few times after I turned it on. Might have been after resetting phone, but who knows exactly.
I set screen to stay while connected via USB.
I removed all the apps I could and took out the sd card.
Kingoroot stuck at 66% many, many times, and then phone would restart. Research showed it may be accessing the wrong ADB instance or something. So I uninstalled SDK, fastboot, Minimal, etc. Anywhere it could have been hiding. Even did a system restore to last week the day I reinstalled windows. Didn't help one bit. Which is to also say... there are a half dozen or more legit options. Try different ones if you are relatively confident you followed directions the 1st 10 times.
Ministro didn't have moto e in their data base.
Finally back to XDA after checking a dozen videos (I have to admit I was completely dumbfounded and was mad at the whole process). I found XDA Kingroot and right away it worked, but it needed permission to allow apps that were not certified or some thing. I can see how people would think this is so easy. If I had started with this, I'd never have had to ask for help here. Btw, was this my problem all along? Did I miss that in the instructions or was it something else possibly? I don't remember if I did that before since it was 3 days ago.
So far I am thoroughly impressed with the this moto e. I paid $40 for it on a whim and now that I can remove a bunch of bloatware and customize it a bit, I think it may be a good gateway into android devices.
Thanks for looking and all your suggestions.
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
faheyd said:
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
Click to expand...
Click to collapse
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
L8Show said:
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
Click to expand...
Click to collapse
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
-z3r0- said:
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
Click to expand...
Click to collapse
Thanks for that information. I thought I saw adb devices command working in fastboot mode in one of the videos so I thought that was the problem. I thought adb needed to root the phone.
In order of what I've done with the phone so far:
Sent/got codes and unlocked moto e.
Turned on developer options and USB debugging.
Was then unable to get TWRP or the other cw something to work using the command fastboot flash recovery (file name) or fastboot boot... commands.
Gave up and installed Kingroot and everything worked fine.
Decided to try to install TWRP and superSU since kingroot had worked. I read that the phone needed to be flashed back to stock to do this and watched/read a couple of guides. http://forum.xda-developers.com/showthread.php?t=2759495
I used the following named file:
SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC
The phone was changed back, but data doesn't work. I can't access wifi because as soon as I switch it on, it switches back off. 4G, etc is not working either. So after trying to figure that out I decided to just proceed and put TWRP/superSU on the phone.
I powered off the phone. Powered into fastboot mode connected the phone to my computer.
I opened Minimal fastboot folder and shift/right click to bring up the command prompt.
In the command promt i typed fastboot devices and it shows my phone.
I then type fastboot flash recovery (file name or renamed to recovery or renamed to TWRP or I click the actual file and drag it to the command prompt) and then hit enter.
It says it's doing stuff in so many seconds, but after nothing happens. The phone doesn't reset like some of the videos. If I reset it, it powers on, but not into the TWRP screen.
After that I did more reading and found out that adb doesn't always play nice with windows 8.1 and that you might need to force other drivers to make it work right. I did this next and was going to try all the available options from universal naked driver later, but there were no motorola drivers.
Then I came here and learned something new. ADB devices command doesn't work when the phone is in fastboot mode so that has no effect on installing twrp...
Right now I am considering trying to install the other stock files I have access to:
SURNIA_ACG_LTE_5.1_LPI23.29-20_cid9_subsidy-DEFAULT_CFC (20 instead of 30).
After that I am out of ideas if it's not the adb problem. Might kingroot again and go from there.
Ok after researching, it seems that LTE file may not work on sprint and there was success using the boost file from
http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
(2 hour dl make that 5+ lol)
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'll try that next to get the wifi working and then figure out why it won't root.
Thx!
L8Show said:
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Click to expand...
Click to collapse
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
rakeshwipr said:
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
Click to expand...
Click to collapse
and open the command prompt with admin rights
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
d
Thanks! The devices shows up when on as ADB and in fastboot too. I had to take a break when the kernel download took 8 hours, but I think I got the file that will work to fix the wifi issue. I can't mess with it til I get home tomorrow, but I will read and follow all advice.
For the previous poster, I did do the admin rights and did rename TWRP file to recovery... I aslo tried many other combinations, but will keep it in mind for all further attempts.
Appreciate the help so far. I almost left it with the kingroot, but it was bugging me that I couldn't get it to go. Hopefully I'll have good new tomorrow.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
Device shows up in both instances.
It's stock now and the wifi works. Flashed it back to stock by following Mdkcheatz guide here:
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'm stuck where I was when I first started this thread. I've set my account up as administrator. Developer is enabled and so is USB debugging. I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
I confirmed the connection:
fastboot devices
I try to flash it with the:
fastboot flash recovery recovery.img
It says:
target reported max download size of 268435456 bytes
sending 'recovery' (6928 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.359s]
finished total time: 0.578s
C: |Program Files (x86)\Minial ADB and Fastboot>
I'm running windows 8.1 (64 bit). I read that some people had had problems with windows 8. Kingroot worked through the app store. It has been flashed with various stock kernels and that usually takes a few minutes so I don't think it's doing much in half a second. I'll research a bit more, but I think it just a bad combination of this version phone and windows 8.1.
I started the phone after this last attempt. Are there any files in internal storage that I should look for?
L8Show said:
I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
Click to expand...
Click to collapse
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
-z3r0- said:
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
Click to expand...
Click to collapse
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
L8Show said:
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
Click to expand...
Click to collapse
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
-z3r0- said:
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
I am on v2.65. Should I use this version? I checked root and it's rooted, but I needed to use no bloat app (instead of free titanium) to remove some apps. Is that normal? I thought once rooted and set up, I would have complete control. Some apps seem very invasive so I haven't grabbed many yet. I have some questions about apps, etc., but will probably research and ask in another forum if needed.
Thx again for all the help and pointing out my mistake.
So I recently pulled my G Watch back out and installed the most recent OTA 6.0.1, installed TWRP, the custom kernel, and rooted it. Obviously all of that required ADB to function correctly. It did perfectly. I installed ADB using the 15 Second ADB Installer, and used WinDroid Toolkit to flash TWRP and get into recovery and do the rest, that by default installed the ClockworkMod ADB drivers, all of this on my Windows 10 PC.
Those drivers worked perfectly. Until today.
I did a fresh install of CM13 on my Nexus 5 phone, which my watch was paired to at the time. I wiped everything and started over, so I then went into my watches settings and did the Factory Reset so I could start fresh and resync up with my new rom install on my phone.
But when I try to connect via ADB or even try to list the devices it always states "Unauthorized"...
For whatever reason, no matter what I try it wont bring up the prompt on my phone to authorize this computer.
I revoked Debug permissions on both my watch and my phone, tried different usb ports, turned off and on debugging in all its forms on both my watch and phone, plus restarted all my devices and my PC. I have tried google's adb drivers as well.
Not sure what else there is to possibly try, seems I have covered all my bases here. Just doesn't make sense that it worked and now all the sudden it doesn't...
Glad I'm not the only one having this problem! I've tried same exact methods you mentioned with no luck. Hopefully someone knows what's going on here and provide a solution
Maybe deleting the keys in the computer will fix it. If it works with another computer, then it's the solution. On Mac, they are stored in a folder called .android in the home folder, if I recall correctly. Anyway it should be easy to find online how to delete the keys in the OS you're using.
What I did was first authorise my phone to my pc's adb then I copied adb_keys from /data/misc/adb/ on my phone to my pc. I then copied that while in TWRP on my LG G watch to the same directory /data/misc/adb/ and rebooted to system and voila adb access restored!
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
xymic said:
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
Click to expand...
Click to collapse
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Xmaster24 said:
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Click to expand...
Click to collapse
Aaaaaand we're back, Houston! Thanks a lot man. Works great now.
Hello
I have the same problem as author of this thread. How can I get authorize adb? I need it to push some files to internal memory.
I suffer the same problem.
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
koszanty said:
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
Click to expand...
Click to collapse
Sorry, but, with ADB in "unauthorized" state it can't be done.
Guys, read Xmaster24's posts in first page. That's how I fixed it.
turbomann said:
Sorry, but, with ADB in "unauthorized" state it can't be done.
Click to expand...
Click to collapse
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
xymic said:
Guys, read Xmaster24's posts in first page. That's how I fixed it.
Click to expand...
Click to collapse
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
koszanty said:
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
koszanty said:
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
xymic said:
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
Click to expand...
Click to collapse
In my case adb doesn't worked at all
turbomann said:
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
Click to expand...
Click to collapse
It's compatibile but can occur bootloop. If you will have bootloop, you must do that what I write some posts earlier.
I'm realised that my phone with MM do the same bug, unauthorized, I look for adb_keys file but folder ADB is empty, then only remains flash and update on the watch.
i tried to do it my self. follow an instruction from a official website and other
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
https://www.getdroidtips.com/how-to...-plus-i3213-i4213-i4293-i3223/#Pre-Requisites
which i got stuck at, when i boot into bootloader mode . the phone seem to restart and appear only black screen with blue indicator.
then i tried to check if it still connect to adb or not, with {adb devices} its not listed there
PS.
-the drivers work fine
-my Xperia 10 plus model is I4293
The LED is all you get. The screen stays black for fastboot and flash modes. Not sure why adb devices isn't working.
Zaben said:
The LED is all you get. The screen stays black for fastboot and flash modes. Not sure why adb devices isn't working.
Click to expand...
Click to collapse
one thing weird
i using a Xperia Tool (Xperia Companion) and it display the text that my phone need to unlock the screen or allow to use data tranfer
which i already check a USB debugging to be on, and every time i connect it to my PC, it still ask me a permission to be allow or not
maybe this is a problem here ?
It cant be listed in ADB if the android isnt running.
Blue LED means fastboot mode. So to check if the device is in that mode you do "fastboot devices".
Once the LED is blue you can unlock the bootloader with the command "fastboot oem unlock 0x<insert your unlock code>".
Haxk20 said:
It cant be listed in ADB if the android isnt running.
Blue LED means fastboot mode. So to check if the device is in that mode you do "fastboot devices".
Once the LED is blue you can unlock the bootloader with the command "fastboot oem unlock 0x<insert your unlock code>".
Click to expand...
Click to collapse
When I pressed to volume up button and plug the cable in, led turned red>blue>off. I tried releasing the button at a different colour, but my phone still did not go into fastboot mode. Did I do something wrong?
ZimpleThing said:
When I pressed to volume up button and plug the cable in, led turned red>blue>off. I tried releasing the button at a different colour, but my phone still did not go into fastboot mode. Did I do something wrong?
Click to expand...
Click to collapse
I guess you are using windows. This is issue on windows when you don't install adb drivers. There should be tutorial on Sony site how to install them.
Haxk20 said:
I guess you are using windows. This is issue on windows when you don't install adb drivers. There should be tutorial on Sony site how to install them.
Click to expand...
Click to collapse
Yes, I am using Windows 10, but let me clarify my understanding first.
From what you said, I need to manually install the ADB driver by Device Manager > Portable Devices > Xperia 10 Plus > Browse my com... And that driver, I should get it from Sony site, but I only see Xperia 1, 5 and 8, not 10 nor 10 Plus.
However, I could see my phone by using command adb devices through minimal ADB and Fastboot. Does this imply that the driver is installed already?
ZimpleThing said:
Yes, I am using Windows 10, but let me clarify my understanding first.
From what you said, I need to manually install the ADB driver by Device Manager > Portable Devices > Xperia 10 Plus > Browse my com... And that driver, I should get it from Sony site, but I only see Xperia 1, 5 and 8, not 10 nor 10 Plus.
However, I could see my phone by using command adb devices through minimal ADB and Fastboot. Does this imply that the driver is installed already?
Click to expand...
Click to collapse
Adb and fastboot are not the same thing so you have to get fastboot driver.
I have no clue where this driver is as I use Linux only which includes the driver by default.
Haxk20 said:
Adb and fastboot are not the same thing so you have to get fastboot driver.
I have no clue where this driver is as I use Linux only which includes the driver by default.
Click to expand...
Click to collapse
I see. There is a fastboot driver on Sony site, but it was uploaded since 2014. I successfully installed it, but still nothing seems to work. I will try on Ubuntu later. Thanks for your help.
ZimpleThing said:
I see. There is a fastboot driver on Sony site, but it was uploaded since 2014. I successfully installed it, but still nothing seems to work. I will try on Ubuntu later. Thanks for your help.
Click to expand...
Click to collapse
There is a thanks button. Hit it instead of saying it.
Haxk20 said:
There is a thanks button. Hit it instead of saying it.
Click to expand...
Click to collapse
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
ZimpleThing said:
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
Click to expand...
Click to collapse
Glad I could help
I know its been a long time but maybe someone can help me.
I can get into the bootloader but when I trie to use the unlock code, mentioned above, and the sony unlock key it always says waiting for device but nothing happens. Any clue?
Edit fixed the Problem
Xperia 10 plus stuck on waiting for device
ZimpleThing said:
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
Click to expand...
Click to collapse
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
travy said:
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
Click to expand...
Click to collapse
I was using windows 10. From what I can remember, my problem is that I didn't install driver correctly (I'm not sure which one). I am not really sure if this fastboot driver the one I used. I saw my device in Device Manager, but I got waiting on device... just like you. So what I have done was locate my device in Device Manager and install the sony driver over that device. If sony's driver was not the correct one, then it was another driver that I can't remember, but the instruction still the same. Sorry for an unclear message, but I can barely remember anything now.
travy said:
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
Click to expand...
Click to collapse
Go in Windows Device Manager and check the device . If needed install drivers manually