Database Info

Operation not permitted

Subject line pretty much sums it up. I've been to loads of GUIs and walkthroughs - in the end my device remains locked down. I have TWRP as my recovery and a rooted version of the stock CM11S. I have my debugging on. My computer has permission with it set to remember my choice. I've dabbled in both OSX and Windows adb. The goal is to go back to stock EVERYTHING. I'm going to send it back.
Please help.

Lol you told us everything except for which operation is not permitted.
Transmitted via Bacon

Flashing pretty much anything via fastboot. When I 'fastboot oem unlock' the system isnt formatted or anything. Is it because my recovery isnt stock? I've tried restoring stock recovery, but after it loads once, a reboot just goes into TWRP again. I dont understand.

Xephrey said:
Flashing pretty much anything via fastboot. When I 'fastboot oem unlock' the system isnt formatted or anything. Is it because my recovery isnt stock? I've tried restoring stock recovery, but after it loads once, a reboot just goes into TWRP again. I dont understand.
Click to expand...
Click to collapse
If you don't have the stock recovery installed, isn't your bootloader unlocked already? What happens when you issue these commands?
Code:
fastboot devices
Code:
fastboot oem device-info
Transmitted via Bacon

timmaaa said:
If you don't have the stock recovery installed, isn't your bootloader unlocked already? What happens when you issue these commands?
Code:
fastboot devices
Code:
fastboot oem device-info
Transmitted via Bacon
Click to expand...
Click to collapse
C:\Users\Chris\Desktop\android-sdk-windows\platform-tools>fastboot devices
97e265f5 fastboot
and
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s

What about the question I asked?
Transmitted via Bacon

Oh sorry. Yeah, that's where things get weird. It's locked now, but I guess I was able to get it unlocked long enough to get TWRP injected. Not sure when / how it locked.

So you don't know at what point this started happening?
Transmitted via Bacon

I don't.

Usually there's a catalyst for things like this, without knowing the catalyst it's difficult to troubleshoot.
Transmitted via Bacon

Well shoot.

Come to think of it, I think I may have typed in oem lock at one point and then unlock promptly thereafter.

Solution
Great news! I've solved the issue. I used OnePlus One Toolkit by @manudroid19
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
I tried the Experimental Method or #2 to unlock the bootloader. Then you're given the option of downloading TWRP. At first I thought that was lame cause I already had that installed - that's what I was trying to get away from. But I finally understood that I had the option of running that recovery off of my PC by initiating fastboot mode on my One, then typing 'fastboot boot <local path of TWRP.zip I just downloaded>'. And from there I was able to sideload the unlock / tamper toggler as made available here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Sideload actually completed successfully! I had tried sideload before with every attampt ending in red-text failure. I then went into fastboot mode on my One and flashed stock recovery. Then I used OnePlus One Toolbox v2 by @inthiaano:
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
Because it had stock CM11S as an option. This was also the toolbox I used to flash stock recovery earlier cause I couldn't find it anywhere else. After I flashed that, I did the fastboot boot <local TWRP> sideload unlock toggler again to achieve:
DUN DUN DUN DUUUNNNNN...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
Factory reset and return-ready. FINALLY!
So happy. Now I can get my money back and buy an Nvidia Shield 2 instead.

Lg l80 d380 cwm recovery & unlock bootloader

I have rooted LG L80 D380 v10d-IND-XX with Purpledrake-lite.
cwm recovery for lg l80 is being tested at below links but it is in russian language. Procedure for unlocking lg l80 bootloader with 'auto unlock script' and installing cwm.img with terminal emulator is mentioned. it would be helpful if anyone can interpret the discussions and answer some queries.
( ____SOLVED____ )
Bootloader unlock link:
http://4pda.ru/forum/index.php?showtopic=576048&st=680#entry37784411.
Cwm recovery installation link:
http://4pda.ru/forum/index.php?showtopic=576048&st=900.
Thanks.
SOLVED:
Bootloader unlock and cwm at above links are working for lg l80 d380 v10d. Originally it is developed for v10c. No data will be erased during the process. Backup and restore is checked working.
Some tips-
1) bootloader unlock script LGL80D380.exe have option for english language but only russian is working. There are 6 executions in russian language, i opted first one to unlock bootloader.
2) cwm 6_0_5.img to be installed with terminal emulator.
3) reboot to system from cwm prompts root fix ---> click yes.
4) to enter cwm recovery ( to be used only after confirming installation of cwm recovery, otherwise all data will be erased)
*press vol.down+power.
*when lg logo is seen release power and press again until factory reset screen is seen.
*click yes.
*again yes.
*cwm recovery will appear.
Note-
To check bootloader lock status adb command 'adb reboot bootloader' is not working. Also service menu code 3845#*380# does not have any option for bootloader lock status. But i think bootloader must have been unlocked.

Any other method for system backup and restore for lg l80 D380 ?

sasays said:
I have rooted LG L80 D380 v10d-IND-XX with Purpledrake-lite.
cwm recovery for lg l80 is being tested at below links but it is in russian language. Procedure for unlocking lg l80 bootloader with 'auto unlock script' and installing cwm.img with terminal emulator is mentioned. it would be helpful if anyone can interpret the discussions and answer some queries.
Click to expand...
Click to collapse
Hey Friend, I am unable to download those tools from 4pda.ru. It says 404 Error - Not Found. Can you please mirror it. Thanks.
---------- Post added at 06:07 AM ---------- Previous post was at 05:26 AM ----------
And also, How may I boot into fastboot mode?

lifehacker69 said:
Hey Friend, I am unable to download those tools from 4pda.ru. It says 404 Error - Not Found. Can you please mirror it. Thanks.
---------- Post added at 06:07 AM ---------- Previous post was at 05:26 AM ----------
And also, How may I boot into fastboot mode?
Click to expand...
Click to collapse
File is attached..
For fastboot mode, i have seen some some lg post at xda that it is hidden behind download mode. For fastboot you will have to disable download mode by editing/deleting some system file.. search for it.. i have not tried that..

sasays said:
File is attached..
For fastboot mode, i have seen some some lg post at xda that it is hidden behind download mode. For fastboot you will have to disable download mode by editing/deleting some system file.. search for it.. i have not tried that..
Click to expand...
Click to collapse
Thanks Friend. Was waiting for this file. The link seems to no longer work. Now the page gives me error 404. Thanks mate. :good:

lifehacker69 said:
Thanks Friend. Was waiting for this file. The link seems to no longer work. Now the page gives me error 404. Thanks mate. :good:
Click to expand...
Click to collapse
Fastboot guide for l90.. not checked for l80..
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825

sasays said:
Fastboot guide for l90.. not checked for l80..
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
Click to expand...
Click to collapse
Thanks mate. Will try and report soon.

Fatsboot Worked!
The Method for l90 for obtaining fastboot worked.
Thanks!

lifehacker69 said:
The Method for l90 for obtaining fastboot worked.
Thanks!
Click to expand...
Click to collapse
What is bootloader lock status on fastboot screen?

Unlocked!
sasays said:
What is bootloader lock status on fastboot screen?
Click to expand...
Click to collapse
When I entered 'fastboot oem device-info' , it showed tampered and unlocked status as false.
Then I entered 'fastboot oem unlock'. And again checking device-info it showed unlocked status true.
It might mean Unlocking actually worked by this modified bootloader.
Code:
C:\Users\admin\Desktop>fastboot devices
4a141be fastboot
C:\Users\admin\Desktop>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.013s]
finished. total time: 0.015s
C:\Users\admin\Desktop>fastboot oem unlock
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\admin\Desktop>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
finished. total time: 0.007s

lifehacker69 said:
When I entered 'fastboot oem device-info' , it showed tampered and unlocked status as false.
Then I entered 'fastboot oem unlock'. And again checking device-info it showed unlocked status true.
It might mean Unlocking actually worked by this modified bootloader.
Click to expand...
Click to collapse
That means we installed cwm.img on a locked bootloader and is working well. So can cwm.img be flashed on original locked bootloader without running .exe script.. have you tried cwm installation before running script..
Thanks

sasays said:
That means we installed cwm.img on a locked bootloader and is working well. So can cwm.img be flashed on original locked bootloader without running .exe script.. have you tried cwm installation before running script..
Thanks
Click to expand...
Click to collapse
No, But I think installation of cwm was only possible when the script cracked the bootloader.
The bootloader got unlocked but the flag of unlocked status was not set.

lifehacker69 said:
No, But I think installation of cwm was only possible when the script cracked the bootloader.
The bootloader got unlocked but the flag of unlocked status was not set.
Click to expand...
Click to collapse
I changed the lock status flag of my device as stated by you. Would like to know something more from you.
I tried rom porting with rom-porter guide as below-
1) port-rom cm11( for L40 with similar chipset,cpu,sdk etc.) and base-rom Lfino(working on L80 with bugs) from 4pda.
2) init.d not supported in stock rom and base-rom, but i copied init.d folder from cm11 to base-rom.
3) updater script in base-rom has set_perm and in port-rom it shows set_metadata. Editing gives error so i kept it unchanged.
4) All other steps were completed as stated.
After flashing the ported zip cm11 booted with a blank screen and again went to boot animation after few seconds. So what must be stopping the rom at blank screen after boot animation..
1) does cm require script to run at startup to boot-in thus requiring init.d which is missing in base-rom..
2) or is it due to the conflict of set_perm and set_metadata in updater script.
3) or something else.
i know its all crap and i dont know anything about development. Your comments please..

set_perm is deprecated since cwm version 6.0.4.5. We have to use set_metadata.
The problem you state might be due to incorrect permissions or unsupported libraries from l40.
Better would be to use ArchiKitchen to port as it takes care of the permissions.
As I know, it is very hard to port cm roms to non cm based roms because cm roms uses various scripts and custom kernel with optimizations.
The nearest device I found with working cm11 was LG L70 (D325 global w3ds version. Our is D380 w6ds.)
I have ported all the device trees and vendor files for L80 and will try to build cm11.
My current status is I am at repo sync and will take some days to complete. (My internet is very slow. )
As of now, I have successfully built cwm recovery and kernel (boot.img) for stock based roms.
Link to the folder : https://drive.google.com/folderview?id=0Byu6dt70FNVkTFhCa0lia2p1cDg&usp=drive_web
Please test and report me whether they are working?
This thread might be useful. Give it a try. :- http://forum.xda-developers.com/showthread.php?t=2532300

Ok

lifehacker69 said:
Please test and report me whether they are working?
Click to expand...
Click to collapse
Ok.. can i flash with flashify? Cwm and boot img both at a time or individually?

sasays said:
Ok.. can i flash with flashify? Cwm and boot img both at a time or individually?
Click to expand...
Click to collapse
You may but better use fastboot to flash.

lifehacker69 said:
You may but better use fastboot to flash.
Click to expand...
Click to collapse
Used flashify.. chkd cwm 6.0.5.1 backup, restore, wipe data, dalvik and all worked. Not sure, but I felt backup of system partition was little slower. Back camera is not working, it shows front cam view on all modes including video recording. Torch (flashlight) not working.
Thanks

___

lifehacker69 said:
You may but better use fastboot to flash.
Click to expand...
Click to collapse
sshots

Shield tablet wont boot beyond fastboot menu :'(

I hope you guys can help me, i have been wandering around blogs forums to find a fix to this issue but to no avail. I got my replacement tablet about a few month ago. I decide to keep the old one and install custom rom on it. The old one is still usable now, but the replacement tablet is dead to me. One day i restart the repl tablet and it just stucked at the fastboot menu. When i choose to go into recovery mode. Nothing happened except a blink of message said that cold linux booting failed. So i try to unlock bootloader to flash it using adb command. Now it wont let me unlock boot loader giving me an error same as the guy here ( i cant paste an outside link here, google : Shield Tablet (LTE) won't boot beyond fastboot, fastboot OEM)
Ps : sorry for bad english im from Malaysia and also im tech newbie

flash the official firmware, you shouldn't need the the bootloader unlocked to flash a signed nvidia package.
this should replace your recovery and system and get you up and running again.
if not, perhaps your NAND is corrupted or damaged.

DreadApex said:
flash the official firmware, you shouldn't need the the bootloader unlocked to flash a signed nvidia package.
this should replace your recovery and system and get you up and running again.
if not, perhaps your NAND is corrupted or damaged.
Click to expand...
Click to collapse
I have downloaded the firmware 3.1.1 2.3gb, but it still required me to unlock bootloader to use this command
Fastboot flash recovery recovery. Img
Fastboot flash boot boot. img
Fastboot flash system. Img
........
Would appreciate if you guys can guide me in this matter

RaybenBB said:
I have downloaded the firmware 3.1.1 2.3gb, but it still required me to unlock bootloader to use this command
Fastboot flash recovery recovery. Img
Fastboot flash boot boot. img
Fastboot flash system. Img
........
Would appreciate if you guys can guide me in this matter
Click to expand...
Click to collapse
Hi,
The "fastboot oem unlock" command don't work?

Elpatii said:
Hi,
The "fastboot oem unlock" command don't work?
Click to expand...
Click to collapse
Nope, also cant detect device using adb devices command. Tried same command in the other shield tablet, work just fine. Its not driver problem.
Tried fastboot oem unlock, and somehow it ask me on the shield to unlock or not, choose unlock and this error occured
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 3.736s

Maybe that you can flash the stock image from NVIDIA (https://developer.nvidia.com/shield-open-source)

Elpatii said:
Maybe that you can flash the stock image from NVIDIA
Trying to flash that one, still it require me to unlock bootloader. I think my chipset was damaged or fried. Have escalate this issue to nvdia, and it seems they want to do a replacement
Click to expand...
Click to collapse

RaybenBB said:
Maybe that you can flash the stock image from NVIDIA
Trying to flash that one, still it require me to unlock bootloader. I think my chipset was damaged or fried. Have escalate this issue to nvdia, and it seems they want to do a replacement
Click to expand...
Click to collapse
I think that's the best solution for now!

Latest root/twrp process?

Hi, can someone point me into the right process to root this phone with latest SuperSU binaries and latest TWRP for this device? I own a 6045Y. Thanks in advance.
Edit: while waiting for an answer i tried the most basic task: unlocking the bootloader. Unfortunately, i get this error:
Code:
D:\Desktop\adb>fastboot -i 0x1bbb oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.003s
The device is brand new, i opened the box this morning.

Band 12 needed for T-Mobile
The same issue here.
I have got 6.0.1 over OTA update on my 6045. I am looking to install TWRP on it, root the phone, and then flash the old radios.
Please advise me how to install TWRP on 6.0.1.

The answer was in a thread on the same page as yours. Something along the lines of "now that I have marshmallow, how do I root?".
You need to learn to use the search.
http://forum.xda-developers.com/showpost.php?p=67644383&postcount=486

I forgot to mention in the OP, i'm not on Marshmallow. I'm still on 5.0.2-010 09. I supposed it being a 6045Y and coming fresh out of the box you guys figured out i couldn't have been on MM yet. But anyway it still seems strange that they locked those fastboot commands... Am i doing anything wrong? I should be able to unlock bootloader just entering the right command while in fastboot mode right?

plumbe0 said:
I forgot to mention in the OP, i'm not on Marshmallow. I'm still on 5.0.2-010 09. I supposed it being a 6045Y and coming fresh out of the box you guys figured out i couldn't have been on MM yet. But anyway it still seems strange that they locked the bootloader... Am i doing anything wrong? I should be able to unlock bootloader just entering the right command while in fastboot mode right?
Click to expand...
Click to collapse
The bootloader always comes locked. It's nothing new. Go to this thread by DallasCZ http://forum.xda-developers.com/idol-3/general/guide-unlock-bootloader-root-alcatel-t3161878 and follow the steps completely. Don't skip any.

Unfortunately I have got installed the OTA (factory) 6.0.1 ROM on my idol 3. Those steps would not on the device. There is a thread referring fastboot commands being disabled on 6.0.1.
I have downloaded Panasonic Firmware Eluga switch and also ADB drivers, but it could not find my device.

kingoftheafro said:
The bootloader always comes locked. It's nothing new. Go to this thread by DallasCZ http://forum.xda-developers.com/idol-3/general/guide-unlock-bootloader-root-alcatel-t3161878 and follow the steps completely. Don't skip any.
Click to expand...
Click to collapse
I don't mean to be rude or anything, but haven't you read my first post? I can't unlock the bootloader because entering the commands in the guide gives me an error, while unlocking the bootloader on 5.0.2 should be possible (already did it on an idol3 of my friend).

plumbe0 said:
I don't mean to be rude or anything, but haven't you read my first post? I can't unlock the bootloader because entering the commands in the guide gives me an error, while unlocking the bootloader on 5.0.2 should be possible (already did it on an idol3 of my friend).
Click to expand...
Click to collapse
I did read your first post. Since there can be a plethora of issues you can be having such as, not having usb debugging enabled, making sure your phone has set permissions for adb on your computer to access phone, making sure your drivers are correctly installed, etc I decided to send you the link that would pretty much tell you everything just to be safe. So I can pretty much expect you didn't read the whole thread so why not try the 3 things I stated and see if that solves your issue.

kingoftheafro said:
I did read your first post. Since there can be a plethora of issues you can be having such as, not having usb debugging enabled, making sure your phone has set permissions for adb on your computer to access phone, making sure your drivers are correctly installed, etc I decided to send you the link that would pretty much tell you everything just to be safe. So I can pretty much expect you didn't read the whole thread so why not try the 3 things I stated and see if that solves your issue.
Click to expand...
Click to collapse
USB Debugging is active, i have the drivers installed, PC has been secured access to USB debug. Still get the error.

plumbe0 said:
USB Debugging is active, i have the drivers installed, PC has been secured access to USB debug. Still get the error.
Click to expand...
Click to collapse
Interesting. I've never come across that issue so I'm a bit stumped and haven't a way currently to replicate said issue. I'm completely at a loss. Unless someone else had this issue or someone else has more experience with this I don't know what else to recommend.

It turns out that the bootloader is unlocked even if adb says that the OEM unlock is not available. Tried with 3 different devices on latest firmware (5.0.2-010 09) and i managed to get root and twrp even if fastboot -i 0x1bbb oem device-info says the bootloader is locked.

Only you Root with systemless....follow instructions
write in twrp terminal?
echo SYSTEMLESS=true >> /data/.supersu
flash the supersu zip and then wipe cache and davik cache...

Alek Dev said:
Only you Root with systemless....follow instructions
write in twrp terminal?
echo SYSTEMLESS=true >> /data/.supersu
flash the supersu zip and then wipe cache and davik cache...
Click to expand...
Click to collapse
What? I couldn't understand a thing of what you've said.

Trying to flash TRWP Moto Z recovery - not working

Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork

spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar

the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork

spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.

the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:

Do you have the Verizon model?

samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03

spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.

The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?

I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?

What if fastboot boot twrpname.img
It's really weird anyway...

enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.

spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...

enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.

spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...

if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img

hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????

Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.

I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.

cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!