Database Info

[Q] Stuck in "FASTBOOT MODE - NO BOOT OR RECOVERY IMG"

My NExus S is stuck on the screen that says:
Fastboot Mode No Boot or Recovery IMg.
Product Name - Herring
HW Version - Rev34
Bootloader Version - D720SPRKC5
Baseband Version - D720SPRLCI
Carrier Inro - SPR
Serial Number 32300E25C33500EC
Lock State - Locked
options to select
Reboot Bootloader (gives me exact same screen) except it only says "Fastboot"
Reboot Back to the "FASTBOOT MODE - NO BOOT OR RECOVERY IMG"
Recovery (Can boot to CWM but I can't mount anything)
Power OFF (That works fine)
Then the little green man and the android logo
Followed by USB Control INIT
USB Control INIT End
STANDARD_SET_CONFIGURATION
Conventional wisdom says download some files and fix via fastboot. However in fastbootI can't run ANY of the steps without running FASTBOOT OEM UNLOCK. When I run it my phone asks if I really want to unlock the bootloader. when I choose YEs and hit power it just freezes there.
My next thought Boot to recovery and restore. A restore through recovery followed by a reboot leads me back to the original no boot or recovery img.
Okay I'll just sideload a working rom by mounting usb storage. Then I can flash it with CWM and be up and running.
but when I try to do mount the USB Storage I get "E:Unable to write to ums 1unfile (No such file or directory)"
Finally, Last ditch Effort, I'll load up ODIN and use that to put on a working recovery. there's forums all over the place explaining how to do that right? Well yes, but the links to the Tar file are all broken.
What next my friends? I'd really like to get this phone working.

Wug's Nexus Root Toolkit.

ej8989 said:
Wug's Nexus Root Toolkit.
Click to expand...
Click to collapse
I tried doing the Flash stock + unroot in wug's kit but no luc. any other ideas?

swing4thefence said:
I tried doing the Flash stock + unroot in wug's kit but no luc. any other ideas?
Click to expand...
Click to collapse
Your bootloader is LOCKED. You must first UNLOCK the bootloader by clicking "Unlock" on Nexus Root Toolkit.

ej8989 said:
Your bootloader is LOCKED. You must first UNLOCK the bootloader by clicking "Unlock" on Nexus Root Toolkit.
Click to expand...
Click to collapse
No matter how I try to do it, it always freezes at the unlock bootloader step.

Did you install proper drivers?

ej8989 said:
Did you install proper drivers?
Click to expand...
Click to collapse
I thought so. My wife is on the computer so if she ever gives it back I'll re-install the drivers and try again.

swing4thefence said:
I thought so. My wife is on the computer so if she ever gives it back I'll re-install the drivers and try again.
Click to expand...
Click to collapse
Reinstalled Drivers. Still no luck.

I have the same problem.

Same situation for me, because i pressed "Reboot" in CWM without having flashed a Rom (stupid ). Broken power button, hanging on Google logo or in Fastboot mode.
I hope RTK will help me :good: :laugh:
Edit: I have no idea how to revive my Nexus S. Status: Broken Power button, Bootloop, can access Fastbood Mode but dont select someting, Bootloader unlocked, RTK doesn´t find any devices in Fastboot Mode, Device is rooted and has CWM

!Lür said:
Same situation for me, because i pressed "Reboot" in CWM without having flashed a Rom (stupid ). Broken power button, hanging on Google logo or in Fastboot mode.
I hope RTK will help me :good: :laugh:
Edit: I have no idea how to revive my Nexus S. Status: Broken Power button, Bootloop, can access Fastbood Mode but dont select someting, Bootloader unlocked, RTK doesn´t find any devices in Fastboot Mode, Device is rooted and has CWM
Click to expand...
Click to collapse
what about just using adb? Can you find it when you type fastboot devices? If so there's a command in fastboot to reboot to recovery I think.
I on the other hand am screwed. I read in another forum that it hangs on unlock because the internal memory is fubar.

swing4thefence said:
what about just using adb? Can you find it when you type fastboot devices? If so there's a command in fastboot to reboot to recovery I think.
I on the other hand am screwed. I read in another forum that it hangs on unlock because the internal memory is fubar.
Click to expand...
Click to collapse
Solution for me:
1. Turn device on into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
5. reflash everything i wanted :good:
Requirement is a working Android-SDK!

I wish it was that easy for me. I can access recovery just fine. It's the memory I can't touch. Unless someone knows a way to fix corrupted memory...
Sent from my SCH-I510 using xda app-developers app

Im having this same issue too i can still get to CWM recovery but nothing really helps from there. I can still mount my storage and put zip files on there etc but nothing seems to fix the problem...any progress?

swing4thefence said:
I wish it was that easy for me. I can access recovery just fine. It's the memory I can't touch. Unless someone knows a way to fix corrupted memory...
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I think I'm going to try using my computer to mount and format the internal memory. any ideas as to the correct settings to use when I try this? at this point what have I got to lose?

swing4thefence said:
I think I'm going to try using my computer to mount and format the internal memory. any ideas as to the correct settings to use when I try this? at this point what have I got to lose?
Click to expand...
Click to collapse
Was this solved by any means ??, i am myself stuck at that position

Flash the stock image again using the Nexus Toolkit
Sent from my Nexus S using xda app-developers app

Akbar89 said:
Flash the stock image again using the Nexus Toolkit
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Wug's Nexus toolkit ?? It is stuck on bootloader unlock menu, as unlocking bootloader makes it freeze. Without unlock it doesn't flashI anything.
If there is another tool please guide me with link.
Avoid Spells!!! "Auto correct : ON"

stuck on fastboot mode(lenovo S860)
recently i've bought lenovo s860 (2GB version).....its latest updates had bugs....so i was trying to downgrade to lower version(jelly bean).....in the way i got stuck in fastboot mode......is there any way to get out of it??

same problem in galaxy nexus i9250m
ej8989 said:
Did you install proper drivers?
Click to expand...
Click to collapse
i have same problem in galaxy nexus i9250m
my bootloader showingh no boot or recovery img
i have working fastboot, workin adb and driver
my oem is unlocked with fastboot
bt i am unable to flash recovery and rom

[Q] Bricked one

os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?

brooklynchildxbc said:
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
Click to expand...
Click to collapse
Push a custom rom via adb and flash in recovery or flash stock images via fastboot

acuicultor said:
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
Click to expand...
Click to collapse
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.

brooklynchildxbc said:
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
Click to expand...
Click to collapse
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?

boober78 said:
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
Click to expand...
Click to collapse
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back

brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
No problem. I'm glad I could help
Sent from my One using Tapatalk

brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
Don't give up.... I was in the same position like you for a couple days....and now is fix by my self..... If you unlock your bootloader try to lock back (fastboot oem lock) now try to flash via fastboot Philz Recovery ( try until is rebooting himself into recovery) .... After that put on a memory stick the new system .... You may need to mount the USB flash drive ..... That's exactly what I have done....Good Luck ...

It is damn near IMPOSSIBLE to actualy, truly "brick" these devices. There are way too many safeguards in place.
Be careful before announcing that you are "bricked". Bootlooping (which is what your device was doing) is not "bricked". As long as you have fastboot, you can always reflash recovery, and then use recovery to reflash your custom ROM (or you can bypass all of that and reflash the factory images from fastboot).
Don't panic, you know more than you think you know. Just don't get freaked out, and read. You'll be fine.

[Q] bootloader ? fastboot mode issue

previously i unlocked rooted my device running stock 5.0
I tried to flash cynogenmod 11s and didn't get installed showing error for" MD5 check"
I tried many times and now i m not able to get into twrp recovery which i installed . Instead its showing stock recovery.
I tried OEM lock to start the process from beginning after fastboot mode showing many times for the process, its stuck in the 'waiting for device' in nexus toolkit and in device , the screen isnt moving from fastboot mode unless i manually start it. after starting manually the bootloader haven't re-locked.
I tried reinstalling my ABDdrivers in pc and did all the process again but nothing worked.
wonder whether the nand memory is fried ???

Do this.... Boot the phone in fastboot mode.... Connect to your PC and confirm with fastboot devices if the same is recognized ....
If it is.... Check the current status of the bootloader of it being unlocked or not.... If it is unlocked .... Just flash the stock image

rohit25 said:
Do this.... Boot the phone in fastboot mode.... Connect to your PC and confirm with fastboot devices if the same is recognized ....
If it is.... Check the current status of the bootloader of it being unlocked or not.... If it is unlocked .... Just flash the stock image
Click to expand...
Click to collapse
i jus tried it .
and also flashed the stock image , its in unlocked state only.
but i m not able to relock it or get into the twrp recovery which i installed
the phone always stops in the process before getting into recovery mode. after getting in the bootloader mode, the pc shows ' waiting for device ' and the phone stops the process waiting in the bootloader.

karthi2 said:
i jus tried it .
and also flashed the stock image , its in unlocked state only.
but i m not able to relock it or get into the twrp recovery which i installed
the phone always stops in the process before getting into recovery mode. after getting in the bootloader mode, the pc shows ' waiting for device ' and the phone stops the process waiting in the bootloader.
Click to expand...
Click to collapse
So you can normally boot ? If you can, the nand memory is fine. Can you reflash stock bootloader using TWRP ? Can you try "adb reboot recovery" to see whether it boots to recovery or not ?

F4uzan said:
So you can normally boot ? If you can, the nand memory is fine. Can you reflash stock bootloader using TWRP ? Can you try "adb reboot recovery" to see whether it boots to recovery or not ?
Click to expand...
Click to collapse
i m not able to get into TWRP . every time i get into recovery , only stock recovery is facing me even after flashing TWRP many times. The phone isn't entering the recovery mode and its staying in bootloader whenever the command for entering TWRP is given.

Are you doing all this through a toolkit?
Sent from my Nexus 5 using Tapatalk

Ben36 said:
Are you doing all this through a toolkit?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yup , i m using nexus root tool kit

karthi2 said:
i m not able to get into TWRP . every time i get into recovery , only stock recovery is facing me even after flashing TWRP many times. The phone isn't entering the recovery mode and its staying in bootloader whenever the command for entering TWRP is given.
Click to expand...
Click to collapse
Wait. Let me get this straight, so when you flash TWRP, the stock recovery persist ? But you said the phone isn't entering recovery mode ? What command do you use to enter TWRP ?
Sorry if I asked too much, I wanted to help but your words kinda contradict each other.

karthi2 said:
yup , i m using nexus root tool kit
Click to expand...
Click to collapse
If you are using a tool kit.... Sorry can't help.. Search a bit and find the command.....
P.S tool kits are dangerous

karthi2 said:
yup , i m using nexus root tool kit
Click to expand...
Click to collapse
Fastboot flash recovery "name of recovery. Img"
while in bootloader screen
Sent from my Nexus 5 using XDA Free mobile app

Toolkits.. *sighs*
Sent from my Nexus 5 using Tapatalk

karthi2 said:
yup , i m using nexus root tool kit
Click to expand...
Click to collapse
Stop now and go read a fastboot guide
Sent from my Nexus 5 using Tapatalk

First of all. Don't. Never. Ever use toolkits. 99% of questions here could be avoided if you had read fastboot guide instead of using toolkit...

F4uzan said:
Wait. Let me get this straight, so when you flash TWRP, the stock recovery persist ? But you said the phone isn't entering recovery mode ? What command do you use to enter TWRP ?
Sorry if I asked too much, I wanted to help but your words kinda contradict each other.
Click to expand...
Click to collapse
the phone is entering jus to stock recovery when i manually enter ...
its not entering by flashing twrp.. even after flashing twrp , the phone stops on bootloader which it have to enter the twrp recovery .
i jus use nexus root toolkit

How to Downgrade bootloader 41.1A to 41.18 or 41.19

please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you

Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help

Why do you need to downgrade? Messing with Bootloaders can destroy your phone.

even i want to downgrade... I cant flash custom recovery on 41.1A

poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.

Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...

@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.

kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).

I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk

I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.

Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too

SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.

How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!

Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?

_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.

Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.

_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.

Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.

_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)

Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.

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!