Develop Bugs

commandprompt does not work

Hi all,
maybe a very silly question, but when I followed the instructions on https://wiki.cyanogenmod.org/w/Install_CM_for_amami, one of the steps is to open a cmd and type: fastboot getvar version. And well, when I do that and press enter, it says that: fastboot is not recognized as an internal or external command, program or batch file.
The phone is in fastboot mode (a blue light is on), and i have installed sdk and jdk 8u60 on my computer, which runs on windows 7.
Also my computer says that the device driver program is installed.
By the way, when installing jdk, it said I should enter "javac -version" in cmd, but that gave the same notification, howver jdk is installed on my computer.
Who can help me out?
Thanks in advance,
John

Joheee said:
Hi all,
maybe a very silly question, but when I followed the instructions on https://wiki.cyanogenmod.org/w/Install_CM_for_amami, one of the steps is to open a cmd and type: fastbood getvar version. And well, when I do that and press enter, it says that: fastboot is not recognized as an internal or external command, program or batch file.
The phone is in fastboot mode (a blue light is on), and i have installed sdk and jdk 8u60 on my computer, which runs on windows 7.
Also my computer says that the device driver program is installed.
By the way, when installing jdk, it said I should enter "javac -version" in cmd, but that gave the same notification, howver jdk is installed on my computer.
Who can help me out?
Thanks in advance,
John
Click to expand...
Click to collapse
Probably just a typo, but you wrote 'fastbood' in your post. Computer definitely won't recognize that. If you are spelling it right, either 1) you're in the wrong directly in terminal, (cd /(wherever adb is installed), or 2) adb package didn't install correctly, (reinstall). While you're testing it, you can just type 'fastboot', and you should get a list of command options, showing that it is installed.

Sorry yes fastbood was a typo. But what do you mean with: you're in the wrong directly in terminal, (cd /(wherever adb is installed).
A terminal is the same as a command prompt right?
And to reinstall adb package, i would have to delete the platform-tools right? And when i click on delete package, it asks if Im sure about it, bacause it can not be undone.

When you open command prompt, you're 'in a directory', usually in Windows, it's C:/(user)/desktop, or something. You need to get to the directory where adb is. If you installed it with defaults, it's probably C:/adb. If so, once you open command prompt, type 'cd /adb', and hit 'enter'. Then you'll be 'in the right directory'. If adb installed somewhere else, you'll have to find out where, then type 'cd /(whatever)/(whatever)/adb.

I still did not get it working. I deleted the whole android studio package and intalled the sdk tools only now, and installed platform tools in it and tried it all again.
My initial goal was to enter 'fastboot getvar version' in commandprompt. What I tried thus far:
This page (https://wiki.cyanogenmod.org/w/Doc:_adb_intro#Popular_adb_commands) said I should paste ;<path-to-sdk>/platform-tools behind the word Path in Environment variables so I did.
When I open commandprompt it already gives automatically: C:\Users\BTO>
When I just type adb there and hit enter, it says it is not recognized. When I hit cd /adb it says it can't find the given path. (why should I type adb at all by the way, and not fastboot getvar version?)
When I do first 'cd /' it gives C:\> and then adb it also says it can't find the given path.
When I hit C:\>Program Files (x86)\Android\android-sdk\adb it says it can't find the given path.
Deletion of the ;<path-to-sdk>/platform-tools behind Path in the Environment variables does not help.
Thanks for helping me!

Joheee said:
I still did not get it working. I deleted the whole android studio package and intalled the sdk tools only now, and installed platform tools in it and tried it all again.
My initial goal was to enter 'fastboot getvar version' in commandprompt. What I tried thus far:
This page (https://wiki.cyanogenmod.org/w/Doc:_adb_intro#Popular_adb_commands) said I should paste ;<path-to-sdk>/platform-tools behind the word Path in Environment variables so I did.
When I open commandprompt it already gives automatically: C:\Users\BTO>
When I just type adb there and hit enter, it says it is not recognized. When I hit cd /adb it says it can't find the given path. (why should I type adb at all by the way, and not fastboot getvar version?)
When I do first 'cd /' it gives C:\> and then adb it also says it can't find the given path.
When I hit C:\>Program Files (x86)\Android\android-sdk\adb it says it can't find the given path.
Deletion of the ;<path-to-sdk>/platform-tools behind Path in the Environment variables does not help.
Thanks for helping me!
Click to expand...
Click to collapse
First thing you have to do is find out where on your PC the adb files are. The computer won't recognize anything you type with fastboot, adb, etc., unless you're in that directory. I believe adding the environmental variable path is supposed to make that easier, but obviously it's not working out for you, so I would just skip that and find out where the files are, then you can just use 'cd', and go there. It should be easy to do a search in Explorer if you can't find it.

Thank you that you keep helping me.
I worked already 6 hours on it now in total and did not really get any step further. I found the adress of the adb files (the maps were hidden).
I found this page on internet: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
So I followed those steps very precize, I installed the google usb driver in sdk.
Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same case when it's just turned on.
Still when I run fastboot getvar version it says <waiting for device>...
The https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro page gives some poor troubleshooting info about this error. When I hit fastboot devices in the right directory it does not even give the waiting for device error. Changing usb ports does not help either.
Maybe it's something with the 'elevated privileges', I dont't know what they mean with that. But I have Administrator rights.

Joheee said:
Thank you that you keep helping me.
I worked already 6 hours on it now in total and did not really get any step further. I found the adress of the adb files (the maps were hidden).
I found this page on internet: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
So I followed those steps very precize, I installed the google usb driver in sdk.
Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same case when it's just turned on.
Still when I run fastboot getvar version it says <waiting for device>...
The https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro page gives some poor troubleshooting info about this error. When I hit fastboot devices in the right directory it does not even give the waiting for device error. Changing usb ports does not help either.
Maybe it's something with the 'elevated privileges', I dont't know what they mean with that. But I have Administrator rights.
Click to expand...
Click to collapse
Can you tell me what directory on your PC the adb files are located? As far as drivers, best bet is usually PC companion, or Flashtool.

Hi,
I found some time again. I have installed PC companion, but it doesn't show me how to install drivers. It says the software is up to date.
The location of the driver is C:\Users\BTO\AppData\Local\Android\sdk\extras\google\usb_driver
The location of the ADB files is C:\Users\BTO\AppData\Local\Android\sdk\platform-tools
Thanks

Joheee said:
Hi,
I found some time again. I have installed PC companion, but it doesn't show me how to install drivers. It says the software is up to date.
The location of the driver is C:\Users\BTO\AppData\Local\Android\sdk\extras\google\usb_driver
The location of the ADB files is C:\Users\BTO\AppData\Local\Android\sdk\platform-tools
Thanks
Click to expand...
Click to collapse
If PC Companion is giving you that msg, you might be OK w/ drivers. With that being the location of your adb files, you would open command prompt, and type - cd \Users\BTO\AppData\Local\Android\sdk\platform-tools\adb - then you'll be 'in' the right directory, (just to make sure, look in the 'adb' folder and see if fastboot exe is in there). Your command prompt should show - C:\Users\BTO\AppData\Local\Android\sdk\platform-tools\adb. Then type 'fastboot', and you should get output of command options.
If all goes well and you want to make it easier in the future, just move the whole 'adb' folder to C drive root. Then you'll only have to type 'cd \adb'.

Or you could just open a window in the correct directory, hold right shift button on keyboard and click right mouse button and select "open command prompt here "
Easy peezy

I already found how to fill in the commandprompt from the link from my post of 27 september (you can also go to the map, and shift+rightclick > open command here, then you can misspell anything). But the problem is it doesn't recognize my device. When I go to the right directory and fill in:
fastboot devices > nothing at all
fastboot device > <waiting for device>
fastboot getvar version > <waiting for device>
fastboot > a lot of stuff
adb devices > list of devices (but no items show up)
adb device > a lot of stuff
But to repeat a previous post: "Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot in device manager) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same is the case when it's just turned on."

Joheee said:
I already found how to fill in the commandprompt from the link from my post of 27 september (you can also go to the map, and shift+rightclick > open command here, then you can misspell anything). But the problem is it doesn't recognize my device. When I go to the right directory and fill in:
fastboot devices > nothing at all
fastboot device > <waiting for device>
fastboot getvar version > <waiting for device>
fastboot > a lot of stuff
adb devices > list of devices (but no items show up)
adb device > a lot of stuff
But to repeat a previous post: "Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot in device manager) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same is the case when it's just turned on."
Click to expand...
Click to collapse
Sorry i missed that... How about Flashtool driver installer? If you DL Flashtool, there's an exe in the 'drivers' folder that will install for you.

Hey you might be using windows 10,8,8.1 if so follow this guide http://forum.xda-developers.com/xperia-u/issues/guide-how-to-install-fastboot-xperia-t2170114
All The Best

Finally getting somewhere, flashtool worked, so fastboot getvar version and all stuff gave some answers.
I extracted the CM11 files, but when I enter fastboot flash boot boot.img in the platform tools directory, it says error: cannot load boot.img.
The CM11 map is in downloads, is is going wrong there? Or something else. The phone is in fastboot mode.

Joheee said:
Finally getting somewhere, flashtool worked, so fastboot getvar version and all stuff gave some answers.
I extracted the CM11 files, but when I enter fastboot flash boot boot.img in the platform tools directory, it says error: cannot load boot.img.
The CM11 map is in downloads, is is going wrong there? Or something else. The phone is in fastboot mode.
Click to expand...
Click to collapse
Try different files. Here's a boot IMG that I've used successfully - https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM - and try this for recovery - https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
Use 'fastoot devices' before flashing to confirm connection.

That didn't work either. I downloaded the files of your links (btw I wouldn't also know what to do with the recovery file), so they are in my Downloads map of my laptop (can I just leave it there?). Then I wrote in the platform tools directory 'fastboot devices' and it gave an answer. When I filled in 'fastboot flash boot boot.img' it said it cannot load boot.img
And maybe I'm getting it wrong, but the size of the CM11 download is 262.87 MB (I took the first snapshot in this list: https://download.cyanogenmod.org/?device=amami), and the size of that boot.img is just 12.1 MB, so I think that that single .img can never be enough for the whole installation of CM11 though?

Joheee said:
That didn't work either. I downloaded the files of your links (btw I wouldn't also know what to do with the recovery file), so they are in my Downloads map of my laptop (can I just leave it there?). Then I wrote in the platform tools directory 'fastboot devices' and it gave an answer. When I filled in 'fastboot flash boot boot.img' it said it cannot load boot.img
And maybe I'm getting it wrong, but the size of the CM11 download is 262.87 MB (I took the first snapshot in this list: https://download.cyanogenmod.org/?device=amami), and the size of that boot.img is just 12.1 MB, so I think that that single .img can never be enough for the whole installation of CM11 though?
Click to expand...
Click to collapse
The boot and recovery files will just enable you to get into recovery. You'll need a ROM file to put a ROM on your phone. There are many to choose from in the 'android development', and 'original android development' threads. To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img'). Then you can reboot into recovery. Once you download your ROM file, you want it to be on your SD card in the phone. When you get into recovery, you go to your ROM file and install.

Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 1,5 hours on the blue 'waving' startscreen, and getting quite hot even. So it is stuck.

Joheee said:
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 40 minutes on the blue 'waving' startscreen, and getting quite hot even.
Click to expand...
Click to collapse
If your phone is stock, it won't boot with the new IMG you flashed. That's also why the computer doesn't recognize it. You can copy your ROM onto the SD card with your computer, using a card reader or adapter. Just flash both IMGs, then unplug, then turn it on, and hit vol up when you see purple. Make sure you type flash 'boot' for the boot, and flash 'recovery' for the recovery, not 'boot' for both. Also, if you want, there are custom IMG files with recovery on xda for stock ROM that you could flash the same way, if you just want to use your stock.
---------- Post added at 04:54 PM ---------- Previous post was at 04:47 PM ----------
Joheee said:
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 1,5 hours on the blue 'waving' startscreen, and getting quite hot even. So it is stuck.
Click to expand...
Click to collapse
Try this for stock - https://mega.nz/#!k0cTUQbS!5XUZhTEK4xBKVBSeO83TEHE3xs9JEpvxt3g1Sc8tVH8

Stuck in Boot Animation Screen

Stock watch, never turned on debugging. Have tried to do the steps in Skin1980 post (return to stock... load boot, recovery and system (got the error on System). Tried the ADB steps (but noob on ADB with no luck). Am I toast? Attached are screen shot showing fastboot recognizes devices. Also here is device screenshot. Any help would be appreciated... Love this watch but for now it's a paperweight.

Also when I try and write .img files (boot, recovery, system) I get the FAILED (remote: device locked).. I am in fast boot screen on watch.

Can u see the device if it is connected n u enter 'adb devices' in the command prompt?
If not then have to confirm does your driver install correctly.
The device must be connected to PC before you can do anything to it. My understanding.
In fastboot screen on your watch doesnt mean it is connected to PC.

You have to unlock bootloader to be able to use fastboot flash.
While in bootloader, use "fastboot oem unlock" command.
Note, that this automatically wipes all user data on the watch.

What is the error you are getting on System?
A lot of people are reporting errors but in reality they are not.
Can you screenshot the error like you did the fastboot command?

Any progress so far???
It has been a while; have you succeeded to recover the Huawei watch pass the Google animation?
I have read no thread who has solved the problem. Any feedback is appriciated.
Update: After so many days I managed to flash... My watch is working again; still no news from Huawei!!!
For newbies like I am, you have to know is you don't need to enable anything before you are stuck to google logos.
I just downloaded "adb-setup-1.4.3" and "Minimal ADB and Fastboot". Whenever the windows didn't recognize the watch I ran adb-setup which at the end asks for installing drivers and when I disconnect and connect the device, it worked.
After getting connected check if the watch is getting fastboot command by c:\fastboot devices. If you can see any letters and fastboot at the right you're ok to go.
You need to c:\Fastboot Oem Unlock which unlocks the watch and you're out of warranty. Just accept it.
Then follow the steps of skin1980 (thanks it was really great)) http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596
If you need "twrp" not written; just "swipe right" and follow the instructions of skin1980.
Boot Stuck Problem is over.
The watch is getting the updates right now but I guess I'll learn more and get to stock by the experts' help...
Thanks to you all...

hi
i managed to get mine working as well ! (Thanks to abhanli, pkt_lnt and skin180)
make sure you are in fastboot menu on your watch (holding the power button till switches off and the pressing again after vibrates)
most important thing next is to press shift and right click anywhere in the adb folder on your computer, and then run command prompt from there, otherwise adb will not load up and you will think that you have just run a dodgy script !
unlock your bootloader (typing "Fastboot Oem Unlock" in the command prompt in adb folder)
then you can use steps of skin180 (link above)
OR
https://developer.android.com/wear/preview/downloads.html
scroll down to huawei watch and choose second download option (non preview image for after testing) (thanks pkt_lnt)
extract into your adb folder (located in c:\)
then using the command prompt in adb folder, navigate to that extracted folder (using dos commands)
then if you are on windows, type "flash-all.bat"
hey presto - will work !
when it reboots, you may think "darn it still has spinning dots !" but if you wait about 5-10 mins it progresses past that stage and comes up with welcome screen !
My watch is working again !
HUAWEI customer services are a pile of POO. Their repair centre in UK is waste of time. They never answer the phone and never reply to messages.
If the Huawei watch wasnt so beautiful, i'd never bother with them !
Good luck and thanks all.

This worked great for me thanks. BUUTTTT, I now have this issue:
error: cannot load 'bootloader-sturgeon-mec23l.img'
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
W/ (58966): Unable to open 'image-sturgeon-mec23l.zip': No such file or directory
error: failed to open zip file 'image-sturgeon-mec23l.zip': I/O Error
STEPHENs-Mac-Pro:~ HomePC$ fastboot devices
FFS7N15B06002296 fastboot
All 3 files are in the PATH sdk/platform-tools folder: bootloader img, flash shell, and image zip.

Can anyone please help me..
I got my Huawei watch today.. And u was doing the flash system and it didn't work so I did a reboot recovery from the watch.. Then it's not working.. After boot loading the Android logo appears for 2 sec then it's blank then the logo.. Etc.
It isn't recognized by my PS so I can't use any command prompt.. What can I do?
Please help

XT1676 - Stuck in Unlocked Bootloader, after Wipe Cache(?!)

Some informations at first:
XT1676 Moto G5, Fine Gold, 16GB
(TYPE M2675/ FCC ID: <known>/ SEQ#: <known>)
2017-10-30
Problem: Stuck in unlocked Bootloader
Hi all,
i am stuck on bootloader and cant get out.
On my PC I have "Minimal ADB and Fastboot"(v. 1.4.2.) installed and after i open a command prompt(admin) and type
- "fastboot devices" my phone is listed as <NR> fastboot
so that works as the only positive thing i can say
- "adb reboot", *daemon not running. starting it now on port 5037*
*daemon started successfully*
error: no devices/ emulators found
- "adb reconnect", error: no devices/ emulators found
i am not into the adb commands at all, i am a dummy and i would be so glad if someone could lead me out of my problem.
Maybe a word how i got into there:
1) i installed the minimal adb and fastboot(v1.4.2.)
2) i unlocked the bootloader by doing that over the Motorola UNLOCK Bootloader site
3) then i rooted & Flash Twrp Recovery (twrp-3.1.1-0-cedric)
with "fastboot flash recovery twrp-3.1.1-0-cedric.img"
4) first time entered into twrp recovery and i did the following:
A) a factory wipe-> reboot back to recovery mode->
B) install no-verity-opt-encrypt-5.1-> reboot and let system start before i turn off phone and enter bootloader(vol down+start) again
C) after entering recovery mode again, i install Magisk-v11.6 -> reboot->
D) now everything seemed to work, the system started properly rooted.
E) but then i decided to flash once again the Magisk-v11.6 followed by wipe data/ factory reset cause i wanted to completly do the flashing all over.
(dont ask me why i did it.. i could explain and tell you my intention but well it happened anyway and brought me to where i am stuck now)
but that was on this move not all yet: i also wipe dalvik cache
so after wipedalvik/ cache , since that moment i couldnt access to my SD Card anymore as it simply didnt show up anymore.
after a restart i was my first time in an endless bootloop of that Screen with "Erasing"(, the letters sourrounded by a spectral colored circle)
i had to disconnect the phone from power . also i tried to remove the battery for a day. but it would only get me back into that bootloop and only get me out by removing the battery...
i dont know anymore what happened then when the phone now got stuck in the bootloader instead of the bootloop. But yea, now i am stuck here, appreciating any help :highfive:
more infromation from my bootloader screen:
AP Fastboot Flash Mode(secure)
BLB8.12 (<known>, 2017-04-19 11:00:47)
Baseband <known>
Product/ Variant: cedric XT1676 16GB P5
Serial Number: <known>
CPU: MSM8937
eMMC: <known>
DRAM: <known>
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
flashing_unlocked
Software status: Official
Connect USB Data Cable
- When pressing <Start>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone drops back to Bootloader
when pressing <RESTART BOOTLOADER>
it restarts to BOOTLOADER
- When pressing <Start Recovery>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
after 10 seconds another screen poops up:
"Erasing", the letters sourrounded by a spectral colored circle for 3 seconds,
bevor the Phone just drops back to Bootloader
(talking about Erasing ..)
- When pressing <POWER OFF>
Power Off works
- When pressing <FACTORY RESET>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BARCODES>
Barcodes are shown
- When pressing <BP TOOLS>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <QCOM>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BOOTLOADER LOGS>
Display shows:
AP Fastboot Flash Mode(secure)
Fastboot Reason: UTAG "bootmode" configured as fastboot
When connecting an USC- cable
Transfer Mode: USB Connected
...shows up but i cant get any adb commands to work tho ofc i am a dummy at it...

oh my, i just helped myself by reading my first poste here on the forum from 2016.
i made it now to start twrp by downloading the twrp_cedric_3.1.1-0 once again putting the recovery in my adb folder and type
<fastboot flash recovery twrp.img>
followed by <fastboot reboot-bootloader>
i am curious if i can get going now and if my SD card will be read and if i can get a new flash going...

now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?

Techcri said:
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Click to expand...
Click to collapse
For failed mount data goto wipe & select format data (option on the right)
Reboot to recovery
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there

First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
TheFixItMan said:
For failed mount data goto wipe & select format data (option on the right)
Reboot to recoverye
Click to expand...
Click to collapse
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
TheFixItMan said:
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
Click to expand...
Click to collapse
i will parallel read your thread now, thx for being behind it solving the questions! :good:

Techcri said:
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Click to expand...
Click to collapse
You have to select recovery from the bootloader menu to enter recovery
You can also type in a terminal window whilst phone connected to pc in fastboot
fastboot erase userdata
This will erase all internal data (the same as format data in twrp)

Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing SuperSu zip which will disable it for you
Click to expand...
Click to collapse
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
but three things i noticed:
1) the boot progress is suspicous / wrong/ stuck at a moment:
"hello" and "moto" i still see and before the letters of moto start spinning around, the screen freezes for like 2-3 seconds and the next ting i see is the red mouth and cameleon and so on
2) i tried to test camera real quick and it says camera is busy
camera unable to start. if this repeats please power off your phone and restart.
(i did already 5 restarts now and still same problem)
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Edit:
ok, i have here 3 issues still but it goes offtopic already. i throw a thanks first of all at TheFixItMan and then i think thread cna be closed.
I will soon try to install a ROM, like LineageOS 15.1 , and hope that my previous 3 issues will be solved in the process. . .

Techcri said:
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
Click to expand...
Click to collapse
Cyanogenmod is now lineageos
Use the latest version of magisk to root (see official magisk thread on xda)
You can run modules to mod phone without tripping integrity or dm-verity which if false will stop apps that check if you are rooted from working
Magisk hide can hide apps from detecting you are rooted on a per app selected basis
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Click to expand...
Click to collapse
Phone should power off normally
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen

TheFixItMan said:
Phone should power off normally
Click to expand...
Click to collapse
it can be powered off normally as long as its not connected per usb (power or pc)
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Click to expand...
Click to collapse
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
Click to expand...
Click to collapse
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.

Techcri said:
it can be powered off normally as long as its not connected per usb (power or pc)
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Click to expand...
Click to collapse
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work

TheFixItMan said:
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
Click to expand...
Click to collapse
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?

Techcri said:
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Click to expand...
Click to collapse
Does it display a device when the phone is fully booted
If yes than the recovery you are using doesn't support adb (my official recovery does)
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)

Hello, thx for your support.
I linked the wrong picture. This Screeny shows the related cmd (when dev enabled, booted to recovery, connected via usb to pc and typed adb devices).
Does it display a device when the phone is fully booted. If yes than the recovery you are using doesn't support adb (my official recovery does)
Click to expand...
Click to collapse
it shows the same like linked above and when in recovery mode
so no , the 64bit version of twrp cedric 3.2.1-0 prolly isnt the problem.
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
ok i will try that. and the command prompt i have to open from the directoryy<platform tools folder> then right?
would you deinstall minimal ADB and fastboot before installing full android sdk?

TheFixItMan said:
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..

Techcri said:
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Click to expand...
Click to collapse
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)

On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Click to expand...
Click to collapse
yes i did that before as non admin
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
Click to expand...
Click to collapse
i use win7 and cd'ing to the path was almost getting annoying
as screenshot shows, it still doesnt work

in my desperation i deinstalled now all adb drivers(minimal+ sdk)
ran a ccleaner and cleaned registry and reinstalled minimal adb again (btw, there was a new version by now out, 1.4.3)
so the episodes still goes on and i could figure out some new details
because i bought the same phone again for a relative who needed a phone..
in the process of setting it up correctly( thankfully xda is around ) i enabled dev options and the adb debugging
here is the result for the new phone
that shows now that executing as admin or standard user wasnt the problem. i just did it as standard user..
then i thought "hey cool, wait, i connect now my own G5 and see if i can get the phones' Nr displayed there and make sure my phone can communicate with my pc over adb( dunno if the sentence just made sense- greetz from a dummy)"
what happened is shown in this screenshot .. same picture as before! :crying:
(dont get irritated by the screeny because i used the same command prompt for
first, the new phone and
second, my "old" phone which doesnt boot properly, if you look at the command and the result
i am lost!
is it possible to reinstall a bootloader? or how come my phone doesnt communicate with the pc anymore?
and how come that effects the booting process so that i always get this "stop" at the bootloader although i pressed for a restart?
can i do any more tests that indicates what problem i have here?

In fastboot mode, message "OTG NOT MOUNTED, File NOT FOUND"

I have used the SDK tools trying to root my M9.
Activated developper mode, OEM unlocking end usb debugging.
In bootloader mode I can use the command line "adb devices" and it list in terminal a number for the device.
If I do the same in fastboot mode ("adb devices" at command line) then it doesn't show any device number and keeps searching.
When in fastboot mode I got the following message:
SD MOUNTED
OTG NOT MOUNTED
File NOT FOUND
Can somebody help me to solve this issue pls!!

mgbeek68 said:
I have used the SDK tools trying to root my M9.
Activated developper mode, OEM unlocking end usb debugging.
In bootloader mode I can use the command line "adb devices" and it list in terminal a number for the device.
If I do the same in fastboot mode ("adb devices" at command line) then it doesn't show any device number and keeps searching.
When in fastboot mode I got the following message:
SD MOUNTED
OTG NOT MOUNTED
File NOT FOUND
Can somebody help me to solve this issue pls!!
Click to expand...
Click to collapse
Why don't you just install twrp using fastboot then flash magisk?

AT&T Moto Z2 force (XT1789-04) can't access recovery mode

I got a brand new AT&T's Moto Z2 force XT1789-04 (updated to Oreo using an AT&T SIM) and got it SIM unlocked through unlockstone.com's service. After the unlock, I found the following problems:
(1) After every reboot, the device first goes to the fastboot interface (Android man down with box open, just like the figure below but shows "Start" on top right instead ), and I have to press power button to continue a normal boot.
https://www.hardreset.info/media/re...fd1b9659973ee877f48/motorola-moto-z2-play.jpg
(2) In fastboot, If I choose "recovery mode" using volume down/up and press power button, it will go back to the fastboot interface with "start". In another word, I can't see menu of recovery mode, such as "wipe data/factory reset", "Apply update from ADB" and so on.
(3) In addition, the model number has been changed from XT1789-04 to XT1601, but it shouldn't matter according to discussions of other unlockstone's users.
My first questions is, can anyone help me to explain the reason and possible fix to those issues? Would a flash of official AT&T's firmware (such as, NASH_ATT_OCX27.109-47_subsidy-ATT_regulatory-DEFAULT_CFC.xml) be able to fix it?
I understand AT&T locked the bootloader, but it is still possible to flash the firmware, according to:
"With a locked bootloader you can flash an official firmware that is the same revision or newer. So in short, yes." (see, https://forum.xda-developers.com/z2-force/help/updating-att-ota-issues-help-sideloading-t3864514)
So, I gave it an try on my Mac (I also tried on Windows 10, see below):
(1) install moto device manager (MDM Intaller_2.2.9.dmg) downloaded from moto
(2) install 15 second adb and fastboot installer (adb-setup-1.4.3.zip) from XDA
(3) copy files unzipped from (2) to a working folder, copy the firmware as an update.zip file to the same working folder
(4) turn on the device, open developer's options, turn on USB debugging
(5) connect the device to the MAC, choose "USB for file transfer" mode
(6) open a terminal and type the following commands
$ adb devices
List of devices attached
ZG224AGZPZ device
$ adb reboot recovery
Both work fine.
(7) Now the device is in fastboot's "START" mode, not "recovery mode". Since I cannot Select "Apply Update from ADB" from the device, the following command certainly failed:
$ adb sideload update.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
My second question is, can any help me how I can flash the device if the above methods doesn't work?
By the way, I also tried several methods on Windows 10:
(1) Similar to the above method, install moto device manager/or install moto USB driver, install 15 second adb and fastboot, open a CMD window, but "adb devices" couldn't find the device.
(2) Use Lenovo Moto Smart Assistant to "rescue" the device. However, since the device's model number has been changed from XT1789-04 to XT1601, it couldn't go through.
Any suggestions? Many thanks!

Sounds like you have fastboot mode set on, most likely didn't clear from update.
In fastboot enter 'fastboot oem fb_mode_clear' w/o quotes then 'fastboot reboot' and you should boot normally.
When you flash an update, you do it from fastboot, not recovery. When you sideload, you do it from recovery.

Great! The first problem (automatically paused at fastboot interface) is fixed! Thanks a lot!
This is what I did:
(1)
$ adb reboot recovery
$ fastboot devices
$ fastboot oem fb_mode_clear
...
OKAY [ 0.008s]
finished. total time: 0.008s
(2) fastboot reboot or reboot the device manually, it will be brought a fresh start asking for account setting and so on.
In this step, the device got stuck at AT&T's Logo and "Checking for update", but can be solved by manual reboot.
(3) Soft reset works (Setting-->System-->Reset) and will show an "Erasing" screen during reboot.
Then a new but famous problem comes up: When use power+volume down to enter fastboot mode and then use volume key to enter "recovery mode", it shows a down Android robot with red exclamation mark + "no command" other then a menu of options.
There are multiple methods available online. What works for me is:
"it worked when pressing power button for 3 seconds then preesing volume up and released both together"
Then select reboot the system.
It can't remove the Android+Red exclamation+no command screen under the recovery mode but at least provides a method to access it.
However, I have to try it a couple of times before it can show me the recovery menu. I don't know why.
According to this (https://forum.xda-developers.com/z2-force/help/z2-force-booting-to-blank-screen-t3808222), this problem might be able to be fixed by "You should flash it back to stock.".
41rw4lk said:
Sounds like you have fastboot mode set on, most likely didn't clear from update.
In fastboot enter 'fastboot oem fb_mode_clear' w/o quotes then 'fastboot reboot' and you should boot normally.
When you flash an update, you do it from fastboot, not recovery. When you sideload, you do it from recovery.
Click to expand...
Click to collapse

I'm not sure what issue you're having. What you're describing is normal. In Nougat whenever you rebooted to recovery it went to recovery, in Oreo whenever you reboot to recovery you hit a post screen. When you see the android with 'no command' just hold power and tap vol_up, that will bring up the recovery menu like normal. That's the way it is.

XT1789-04 won't boot
Ok, here's my story. I have the very same problem here with the very same phone. Moto Z2 Force XT1789-04 from AT&T. Sim unlocked with same method as they unlocked yours. Converted to XT1601. Can't use Moto Assistant as it will find the mismatch.
Tried the fastboot commands shown here but looks like my problem goes deeper. I'm stuck on a black page that says "Your device is corrupt. It can't be trusted and will not boot. Visit this link on another device...."
Looks like they flashed a custom file or something and of course the boolotader is not unlocked and can't be. What are my chances of fixing it here?