Database Info

CWM not boot on European Moto G

I tryed to boot CWM recovery for moto G (from this thread) but it didn't boot.
I have an european XT1032 (italian version), there are any fix for this device?
I tested the recovery with the following command:
For the 4.3 version
Code:
fastboot boot CWM43.img
For the 4.4 version
Code:
fastboot boot CWM44.img
but the device prompt the motorola screen and then reboot without boot the custom recovery.

1) is your bootloader unlocked?
2) are you on a stock JB or KK rom?
3) Do you have the same issue with TWRP?

Yes I unlocked the bootloader. I'm on Stock KitKat (4.4.2) and I have the same issue if I try to boot TWRP. I also tried to flash it on device but the issue remains.

Read the OP from the site where you downloaded CWM carefully again and compare it to that what you have quoted here.
With fastboot boot you are trying to flash cwm (recovery) as a kernel:crying:
And even then something is missing in your syntax (flash).
For flashing Kernel use:
fastboot flash boot filename.img
Click to expand...
Click to collapse
For flashing CWM use:
fastboot flash recovery filename.img
Click to expand...
Click to collapse
By the way, here is a good fastboot HowTo.

I already try to flash the recovery on device but it doesn't boot.
so i want to test it before flash on the phone

I already try to flash the recovery on device but it doesn't boot.
so i want to test it before flash on the phone

ecila said:
I already try to flash the recovery on device but it doesn't boot.
so i want to test it before flash on the phone
Click to expand...
Click to collapse
Sorry i don't understand you. You flashed the recovery already? But you want to test it before you flash? Now what?
What did you do exactly?
I think you messed up something while doing this thats why i am suggesting you to go back to Stock first.

Just flash it by typing "fastboot flash recovery recovery.img" and then restart bootloader and press volume down, and then volume up. You should boot into recovery.

mokkami said:
Sorry i don't understand you. You flashed the recovery already? But you want to test it before you flash? Now what?
What did you do exactly?
I think you messed up something while doing this thats why i am suggesting you to go back to Stock first.
Click to expand...
Click to collapse
Before write this post i already tried flash and then boot the custom recovery, but it doesnt boot.
So i restored the stock recovery,and now i want to test recovery (on the fly) without flash it.

You have to flash it. You can not use it "on the fly" to test it.

ecila said:
So i restored the stock recovery,and now i want to test recovery (on the fly) without flash it.
Click to expand...
Click to collapse
I'm really sorry, i just opend the specific Thread again and then i read this.
Then i rememberd this thread. So i'll update my mistake
Rusty! said:
If you want to try it out, use:
Code:
fastboot boot recovery.img
So that the system remains unchanged.
Click to expand...
Click to collapse
So you can use the CWM on the fly.

stuck at motorola boot animation

hey all
i did backup of system and i wanted reboot the phone now will show Motorola boot-animation and will reboot again and again with same place , i didn't touch anything .
Best Regards

Can you get into the fastboot menu (hold volume down and then power) or into the recovery (from the fastboot menu)? Also, have you unlocked the bootloader and/or flashed a rom?

dvdkon said:
Can you get into the fastboot menu (hold volume down and then power) or into the recovery (from the fastboot menu)? Also, have you unlocked the bootloader and/or flashed a rom?
Click to expand...
Click to collapse
yes i can get to bootloader i cant get recovery its same thing it will stock on motorolla logo , yes its unlocked bootloader 41.19 .

Jwtiyar said:
yes i can get to bootloader i cant get recovery its same thing it will stock on motorolla logo , yes its unlocked bootloader 41.19 .
Click to expand...
Click to collapse
Did you try flashing recovery from fastboot mode? If not, try following the instructions on the TWRP website (minus the "adb reboot bootloader" part, of course).

dvdkon said:
Did you try flashing recovery from fastboot mode? If not, try following the instructions on the TWRP website (minus the "adb reboot bootloader" part, of course).
Click to expand...
Click to collapse
yes i did flash recovery again with no fix .

Jwtiyar said:
yes i did flash recovery again with no fix .
Click to expand...
Click to collapse
Did you try flashing the kernel? I can verify that the Optimus kernel and the TWRP from the Multirom thread work, so I'd recommend trying that combination.

dvdkon said:
Did you try flashing the kernel? I can verify that the Optimus kernel and the TWRP from the Multirom thread work, so I'd recommend trying that combination.
Click to expand...
Click to collapse
but i don't want multirom , and the kernel is in zip i cant flash it because i cant get into recovery .

Jwtiyar said:
but i don't want multirom , and the kernel is in zip i cant flash it because i cant get into recovery .
Click to expand...
Click to collapse
The MultiROM TWRP itself doesn't install multirom, I just know it works, while some other recovery images don't. You will be able to flash a different recovery once you fix your problem.
I forgot that a kernel can't be readily flashed via fastboot... You should try downloading a stock firmware package and flashing at least boot and system.

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.

Stuck in recovery mode....help pleaseeeeee

Hi folks...after messing im now stuck in the recovery mode....ive somehow also RELOCKED it....
is the phone keepable

ok latest i can do....usb plugged in...fastboot devices shows my phone.... but fastboot oem unlock say error...
is there anyway to flash image via fastbootusb?
update! phone is now unlocked but hangs at 4ext or boots cm12 upto "encryption unsuccessful"
what can i fix in fastbootusb mode? can i flash a rom??

thevilla1 said:
ok latest i can do....usb plugged in...fastboot devices shows my phone.... but fastboot oem unlock say error...
is there anyway to flash image via fastbootusb?
update! phone is now unlocked but hangs at 4ext or boots cm12 upto "encryption unsuccessful"
what can i fix in fastbootusb mode? can i flash a rom??
Click to expand...
Click to collapse
format all partitions except sdcard from 4ext
enable smartflash from 4ext(because you are on S-ON)
flash a rom
done

rzr86 said:
format all partitions except sdcard from 4ext
enable smartflash from 4ext(because you are on S-ON)
flash a rom
done
Click to expand...
Click to collapse
I cant get onto 4ext...i get into recovery mode....(volume - powerbutton) then if i click on recovery it tries to load 4ext...but just says preparing boot on 4ext page...
any other ideas..... thanks for responding

thevilla1 said:
I cant get onto 4ext...i get into recovery mode....(volume - powerbutton) then if i click on recovery it tries to load 4ext...but just says preparing boot on 4ext page...
any other ideas..... thanks for responding
Click to expand...
Click to collapse
post your bootloader details
fastboot getvar all

fixed
rzr86 said:
post your bootloader details
fastboot getvar all
Click to expand...
Click to collapse
dont really know how flashed twrp with fastboot...nothing was mounted......mounted everything....factory reset....reocvery boot.img... installed rom.zip gapps.zip
now im gonna mess again as i feel able to fix it
thanks

thevilla1 said:
dont really know how flashed twrp with fastboot...nothing was mounted......mounted everything....factory reset....reocvery boot.img... installed rom.zip gapps.zip
now im gonna mess again as i feel able to fix it
thanks
Click to expand...
Click to collapse
ooops i did it again..... will somebody punch me..... got cm11 working....so thought id try cm12... got a encryption unsuccessful error...reset phone.... flashed TWRP.img now when i go to recovery teamwin image just keeps flashing at me
update -
fastboot erase cache seems to have cured the flashing twrp screen

encryption unsuccessful
now for some reason i get the encryption unsuccessful after installing cm11... i was getting that with cm12... cm11 worked fine.....

thevilla1 said:
now for some reason i get the encryption unsuccessful after installing cm11... i was getting that with cm12... cm11 worked fine.....
Click to expand...
Click to collapse
did you ever used any format option from twrp?
if not don't ever do it

yup
rzr86 said:
did you ever used any format option from twrp?
in not don't ever do it
Click to expand...
Click to collapse
been formatting and wiping all day long with twrp

thevilla1 said:
been formatting and wiping all day long with twrp
Click to expand...
Click to collapse
i guess you are lucky

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!