Hi everyone,
Does anyone know how to open diagnostic mode on Moto G Stylus?
Unlike elder Moto devices there is not BP tool in recovery.
I also tried adb code
adb shell
su
until here worked fine and I granted permission from my phone.
setprop sys.usb.config diag,adb
this code did nothing.
My device is rooted btw.
barisny said:
Hi everyone,
Does anyone know how to open diagnostic mode on Moto G Stylus?
Unlike elder Moto devices there is not BP tool in recovery.
I also tried adb code
adb shell
su
until here worked fine and I granted permission from my phone.
setprop sys.usb.config diag,adb
this code did nothing.
My device is rooted btw.
Click to expand...
Click to collapse
Up!
noone?
Up!
Still couldn't find any solution.
This worked for me! Non rooted metro
Go into fastboot mode, then do ' oem config bootmode factory'
Related
I am trying to unlock the xoom (best-buy, wifi only - in Canada).
I have adb and fastboot installed.
I have been developing apps on it all week (direct from eclipse, by pushing, by adb shell, by adb install etc).
I am using ubuntu 10.10
Rebooting to bootloader runs properly using
Code:
adb reboot bootloader
when I try
Code:
fastboot oem unlock
it says
Code:
'< waiting for device >'
and does nothing (I have been waiting for 10 minutes now).
Code:
adb devices
does not show the xoom listed (it did before rebooting to bootloader)
Code:
fastboot devices
also does not list any devices
I have tried rebooting with the hardware method as well (plugged into the computer and not plugged into the computer.
Killing and starting the adb server doesn't help either.
I would appreciate any guidance on the issue. I will post if I find a fix somewhere else.
CoatedMoose said:
I am trying to unlock the xoom (best-buy, wifi only - in Canada).
I have adb and fastboot installed.
I have been developing apps on it all week (direct from eclipse, by pushing, by adb shell, by adb install etc).
I am using ubuntu 10.10
Rebooting to bootloader runs properly using
Code:
adb reboot bootloader
when I try
Code:
fastboot oem unlock
it says
Code:
'< waiting for device >'
and does nothing (I have been waiting for 10 minutes now).
Code:
adb devices
does not show the xoom listed (it did before rebooting to bootloader)
Code:
fastboot devices
also does not list any devices
I have tried rebooting with the hardware method as well (plugged into the computer and not plugged into the computer.
Killing and starting the adb server doesn't help either.
I would appreciate any guidance on the issue. I will post if I find a fix somewhere else.
Click to expand...
Click to collapse
Did u try to do a adb remount then try adb devices
Thanks for the help, I had not tried to remount.
If I remount before booting to bootloader it tells me that the operation is not permitted (Expected - I haven't been able to unlock it yet)
if I try it while I am waiting for fastboot to connect, it it says
Code:
error: device not found
.
CoatedMoose said:
Thanks for the help, I had not tried to remount.
If I remount before booting to bootloader it tells me that the operation is not permitted (Expected - I haven't been able to unlock it yet)
if I try it while I am waiting for fastboot to connect, it it says
Code:
error: device not found
.
Click to expand...
Click to collapse
Did u download motohelper drivers so your adb will recognize the device
if the xoom is in fastboot adb wont recognize it hold power and volume up to reboot and try again
The xoom is recognized already. I am able to send the adb reboot bootloader command. When the xoom is trying to load into fastboot, it is not visible, which makes it impossible to enter the oem unlock command.
I gave up on the device, I was having issues with geolocation as well which didn't exist on another device. I returned the device and am waiting to receive the 3g version from the US.
I have the same problem. Does anyone know how to get around this?
Sent from my Xoom using XDA Premium App
If when you can run the adb reboot bootloader command and don't get fastboot to work, then as yet I have not found a solution. Instead I just returned it and ordered the 3g version from verizon and had it shipped. The commands worked fine. If you cannot use the adb command to reboot, then check the instructions for installing adb and fastboot and/or post the error messages you are getting.
On a side note, where did you get your xoom (country/store etc). I wonder if it is a problem with a certain batch, or all the Canadian ones etc. I my wifi only version from bestbuy in Canada.
I'm having the same problem right now on my xoom.
I was preordered on Amazon and delivered to New York 3 weeks ago...
no solution as for now..
returning isn't an option for me, since I live in Poland :/
ok,
I've made two thing, not sure which one worked
1) added /etc/udev/rules.d/11-android.rules file with :
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
2) performed fastboot as root (I hate such obvious solutions)...
I'm not sure if you're using Windows or not but I didn't had any issues when I used fastboot. Just need to make sure you have the drivers installed, and when you do adb reboot bootloader check the device list to make sure it still shows your device listed in there and not as a question mark. If you don't see your device listed in the Device List or does show but with a question mark, double check to make sure you have the drivers installed or else fastboot will not work.
And don't bother trying to use adb when you're in the bootloader since adb will not work.
*** edited: just noticed now that you are using ubuntu 10.10 (I need to stop over reading stuff). Can't remember how the drivers aspect works in Linux since it's been forever since I've used a Linux flavor but you will still want to make sure you have the correct drivers installed or make the changes that niematunikogo did and see if that worked.
niematunikogo said:
ok,
I've made two thing, not sure which one worked
1) added /etc/udev/rules.d/11-android.rules file with :
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
2) performed fastboot as root (I hate such obvious solutions)...
Click to expand...
Click to collapse
niematunikogo,
I am having the same problem you had but I don't understand exactly what you did here. Is there any way you can explain this for me? Thanks
rrainz said:
niematunikogo,
I am having the same problem you had but I don't understand exactly what you did here. Is there any way you can explain this for me? Thanks
Click to expand...
Click to collapse
before typing all the commands, first type "sudo su". adb and fastboot both need to be executed as root (adb actually works without root in case you already edited the USB rules before)
I had same problem but just returning device was not what I intended to do
niematunikogo said:
2) performed fastboot as root (I hate such obvious solutions)...
Click to expand...
Click to collapse
This worked for my Ubuntu, thanks!
I'm comming from the Samsung vibrant so im fairly new to nexus community. However I did find a couple tut. that were very good, I followed everything exactly as the person in the video. By the way the tutorial i used was from the Unlockr. But anyways i followed everything i set up adb my device appeared in the command prompt. However the next step once your phone is recognized when setting up adb is to power off and get into "fastboot". I did that, plugged the usb in and opened another command prompt. When i type in "fastboot oem unlock" it just hangs on the "waiting for device" part forever. Can someone please help me out thankx
You should really use a more descriptive title. I had no idea what this was about until the last sentence.
If you closed your terminal, than adb probably closed as well. Open up the cmd window while the phone is in fastboot and type
adb devices
Click to expand...
Click to collapse
That should start adb back up and let you know if the phone is detected in one command. It should then be ready for
fastboot OEM unlock
Click to expand...
Click to collapse
Sent from my Nexus S 4G "Lore"
Hello all, just picked up a boost mobile moto G, loving it so far. Having some trouble unlocking the bootloader in Xubuntu. Right now its all i got.
well, I have adb set up, and i know it all works fine on my nexus 7.
I plug the moto g with debugging and mtp enabled, I use adb devices to check the connection, it shows my device, so i use adb reboot bootloader, it reboots to the bootloader.
then when i try fastboot devices, it just says "no permissions fastboot"
and nothing works. Anybody got any ideas?
Thanks for any help, would really love to get Slimkat running on this sweet little device
Edit: nevermind. Got it working
Andromendous said:
Hello all, just picked up a boost mobile moto G, loving it so far. Having some trouble unlocking the bootloader in Xubuntu. Right now its all i got.
well, I have adb set up, and i know it all works fine on my nexus 7.
I plug the moto g with debugging and mtp enabled, I use adb devices to check the connection, it shows my device, so i use adb reboot bootloader, it reboots to the bootloader.
then when i try fastboot devices, it just says "no permissions fastboot"
and nothing works. Anybody got any ideas?
Thanks for any help, would really love to get Slimkat running on this sweet little device
Edit: nevermind. Got it working
Click to expand...
Click to collapse
For the record: you need root permission to use Fastboot in Linux so use it with sudo.
Sent from my XT1032 using Tapatalk
Ya. Had to use sudo su. Then give the full path to platform-tools. Never had to do this with my n7
i have stock rooted moto g 4.4.2 i want to restore it to stock so i can update but it doesnt appear in adb devices. it does show up in device manager as motorola adb interface. adb is enabled on the phone. ive spent 2 nights googling and trying different stuff. i cannot get it to work. i have the same problem for a kindle fire 1st gen. but thats an unrelated note.
lolkidz said:
i have stock rooted moto g 4.4.2 i want to restore it to stock so i can update but it doesnt appear in adb devices. it does show up in device manager as motorola adb interface. adb is enabled on the phone. ive spent 2 nights googling and trying different stuff. i cannot get it to work. i have the same problem for a kindle fire 1st gen. but thats an unrelated note.
Click to expand...
Click to collapse
What is the phone booted into when you're entering the adb command? The phone is booted into Android or in recovery? If you're in bootloader you'll need to use fastboot commands. Such as fastboot devices
lolkidz said:
i have stock rooted moto g 4.4.2 i want to restore it to stock so i can update but it doesnt appear in adb devices. it does show up in device manager as motorola adb interface. adb is enabled on the phone. ive spent 2 nights googling and trying different stuff. i cannot get it to work. i have the same problem for a kindle fire 1st gen. but thats an unrelated note.
Click to expand...
Click to collapse
What os are you using on your PC? I had similar problems on Linux mint until I firgured out I had to add a line of code with the adb install
Sent from my Moto G using XDA Free mobile app
It doesnt show up when its booted into android, recovery or bootloader. I am running windows 7 home premium. Ive tried many different driver installers and nothing has worked.
ive just noticed also that when i have it connected and booted into recovery the driver "Android" couldnt be installed, but if its booted into android or bootloader the drivers are fine. i dont know what driver i should be installing for that, i went back and reinstalled my moto g drivers completely, i have philz touch recovery 6.55
lolkidz said:
ive just noticed also that when i have it connected and booted into recovery the driver "Android" couldnt be installed, but if its booted into android or bootloader the drivers are fine. i dont know what driver i should be installing for that, i went back and reinstalled my moto g drivers completely, i have philz touch recovery 6.55
Click to expand...
Click to collapse
I would suggest uninstalling whatever drivers you have installed. Disconnect your phone, uninstall drivers, restart, install drivers and connect your device then try again. When the phone is connected as mtp, adb, fastboot, it will install drivers for each type.
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050
i have done so and still to no avail. everything driver wise is working, but still the driver "Android" when in recovery could not be installed. still no trace of phone in adb devices when booted or fastboot devices when in bootloader.
lolkidz said:
i have done so and still to no avail. everything driver wise is working, but still the driver "Android" when in recovery could not be installed. still no trace of phone in adb devices when booted or fastboot devices when in bootloader.
Click to expand...
Click to collapse
Where did you DL the adb thing at? You could have a faulty adb download or just didn't install your correct api in the adb suite
Sent from my Moto G using XDA Free mobile app
I try to enable the diagnostic port with these codes:
Code:
setprop sys.usb.config diag,adb or setprop persist.usb.eng 1
but not work, no new device appears. I have all drivers installed on my pc and my phone it's rooted, s-off and the bootloader unlocked, and android 7.0.
My question is:
is there an other way to do this?
rgrivero said:
I try to enable the diagnostic port with these codes:
Code:
setprop sys.usb.config diag,adb or setprop persist.usb.eng 1
but not work, no new device appears. I have all drivers installed on my pc and my phone it's rooted, s-off and the bootloader unlocked, and android 7.0.
My question is:
is there an other way to do this?
Click to expand...
Click to collapse
##3424#