Database Info

[Q] help - unlocked, recovery wont flash

So I have my bootloader unlocked, but for some reason I can't flash a recovery (CWM or TWRP). I've tried to flash recovery through fastboot using adb fastboot commands, mfastboot commands, and mototool aio. I've also tried to flash recovery through rom manager and rashr. ( I am rooted )
cmd: getvar:max-download--size
cmd: download:007b1800
cmd: flash:recovery
mismatched partition size (recovery)
Click to expand...
Click to collapse
I get
Boot up failed
Click to expand...
Click to collapse
Whenever trying to enter recovery afterwards. I get the warning bootloader unlocked motorolla screen for .1s before going back to fastboot.
Can anyone point me towards what I should be doing please? Thank you

Is the phone being detected when you type "adb devices" in cmd window ?
If not you need to install correct and drivers, then in while in the boot loader type "fastboot flash recovery RECOVERYNAME.img" obviously you change it to your Recovery's image file and it has to be in the directory with adb and fastboot of course.
Sent from my Nexus 5

Yes it is, it is detected as the phone boots ( it still boots to the stock rom ) and detected in fastboot as w ell.
edit:
to clarify, this is on 4.4.3 if it matters

kdbrown5 said:
Yes it is, it is detected as the phone boots ( it still boots to the stock rom ) and detected in fastboot as w ell.
edit:
to clarify, this is on 4.4.3 if it matters
Click to expand...
Click to collapse
I guess I didn't look up as well as I should have. So even with an unlocked bootloader, there are no recoveries out for 4.4.3 ?

kdbrown5 said:
I guess I didn't look up as well as I should have. So even with an unlocked bootloader, there are no recoveries out for 4.4.3 ?
Click to expand...
Click to collapse
Yeah, of course there are recoveries for 4.4.3/4.4.4. Try to flash another recovery bro
Sent from my Moto G using XDA Premium 4 mobile app

I've tried like 5 recoveries so far. i just tried cwm 6.0.4.5 and now i can't even get into the bootloader, (adb reboot recovery, as well as holding recovery keys at phone turn on) just goes into the rom now. Does it sound like i have to recover everything to stock now?
Not sure that it matters, but I am rooted if that helps or gives you ideas for any other options
edit: through rom manager i was able to reflash the latest CWM and now i have bootloader access back. I still can't get into any recovery though.

kdbrown5 said:
I've tried like 5 recoveries so far. i just tried cwm 6.0.4.5 and now i can't even get into the bootloader, (adb reboot recovery, as well as holding recovery keys at phone turn on) just goes into the rom now. Does it sound like i have to recover everything to stock now?
Not sure that it matters, but I am rooted if that helps or gives you ideas for any other options
edit: through rom manager i was able to reflash the latest CWM and now i have bootloader access back. I still can't get into any recovery though.
Click to expand...
Click to collapse
You can try to go back to stock, and after, flash a custom recovery and see what happens
Sent from my Moto G using XDA Premium 4 mobile app

Ok, I guess I'll try that tomorrow. The thing I'm wondering is, If it doesn't work flashing through fastboot, outside of the ROM, how would reverting back to stock help at all? A stock flash shouldn't change the bootloader at all?

bump : (

Custom Recovery Issue

I initially rooted by OPO without wiping data but today I decided to unlock the bootloader and root it the regular way.
I used fastboot oem unlock and then flashed TWRP using fastboot flash recovery recovery.img onto my OPO.
After this, when I go into recovery mode it still shows as Cyangenmod Simple Recovery instead of TWRP..
What gives and how do I get it to use TWRP?

qwerty123321 said:
I initially rooted by OPO without wiping data but today I decided to unlock the bootloader and root it the regular way.
I used fastboot oem unlock and then flashed TWRP using fastboot flash recovery recovery.img onto my OPO.
After this, when I go into recovery mode it still shows as Cyangenmod Simple Recovery instead of TWRP..
What gives and how do I get it to use TWRP?
Click to expand...
Click to collapse
Did you remember to uncheck the 'update cm recovery' option in Developer Options?
Transmitted via Bacon

--- Mistake, Please delete.

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!

Boot Freezing after twrp installation

Hi !
I had follow this thread https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
and I had install TWRP but now when i try to start my phone,I can access to TWRP and fastboot but I can't access to the system.
My Nokia 3 freeze on "Powered by Android - Orange state -Your device has been unlocked and can't be trusted - Your device will boot in 5 seconds"
------
Nokia 3 - 1032 / Dowgraded to 7.0
Somebody help me plz ! :fingers-crossed:

>Taps< said:
Hi !
I had follow this thread https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
and I had install TWRP but now when i try to start my phone,I can access to TWRP and fastboot but I can't access to the system.
My Nokia 3 freeze on "Powered by Android - Orange state -Your device has been unlocked and can't be trusted - Your device will boot in 5 seconds"
------
Nokia 3 - 1032 / Dowgraded to 7.0
Somebody help me plz ! :fingers-crossed:
Click to expand...
Click to collapse
Did you unlocked your bootloader and after that did you flash TWRP without reboot?
Maybe I'm wrong but when you unlock your bootloader, the phone automatically reboots into stock recovery and and immediately wipe everything (included your internal storage) and then reboots normally. If you flashed TWRP after unlocking your bootloader, your phone will boot into TWRP but it won't wipe anything.
I think that happened.

Isrks said:
Did you unlocked your bootloader and after that did you flash TWRP without reboot?
Maybe I'm wrong but when you unlock your bootloader, the phone automatically reboots into stock recovery and and immediately wipe everything (included your internal storage) and then reboots normally. If you flashed TWRP after unlocking your bootloader, your phone will boot into TWRP but it won't wipe anything.
I think that happened.
Click to expand...
Click to collapse
Mmh after I unlocked the bootloader, my phone was freeze on this
Select Boot Mode :
[VOLUME_UP to select. VOLUME DOWN is OK]
[Recovery Mode]
[Fastboot Mode] <<==
[Normal Mode]
=> FASTBOOT mode.....
So, I forced it to reboot, after everything seems ok.
What part must I reflash ?

>Taps< said:
Mmh after I unlocked the bootloader, my phone was freeze on this
Select Boot Mode :
[VOLUME_UP to select. VOLUME DOWN is OK]
[Recovery Mode]
[Fastboot Mode] <<==
[Normal Mode]
=> FASTBOOT mode.....
So, I forced it to reboot, after everything seems ok.
What part must I reflash ?
Click to expand...
Click to collapse
When I unlocked the bootloader my phone freezed too, so I typed in Windows cmd "fastboot reboot". After that, my phone was formatted by stock recovery.
You should reflash stock recovery if you have TWRP, so the stock recovery can format your internal storage, if not, your phone won't boot.
:fingers-crossed:

Isrks said:
When I unlocked the bootloader my phone freezed too, so I typed in Windows cmd "fastboot reboot". After that, my phone was formatted by stock recovery.
You should reflash stock recovery if you have TWRP, so the stock recovery can format your internal storage, if not, your phone won't boot.
:fingers-crossed:
Click to expand...
Click to collapse
Ok, so fastboot didn't work at all (just waiting devices)
I tried to reflash TWRP nothing happens, I tried to do a factory wipe with twrp but nothing happens too.
I searched a stock recovery for nokia 3 1032- Android 7.0 but found nothing - must i use stock recovery for Android 7.1.1 or do you have a link to a stock recovery for 7.0 ?
------------
I found this on XDA : Is it a good way if nothing work ?
Hi, I was able to unbricked my phone using this:
"https://mega.nz/#F!0lMBiIIYgB!c9TeOWFrKpf0XfOwXzunrg"
Here is the SP Flash tool, the download agent for Nokia's phones and the ROM unpacked
As SkaboXD said (i don't know if it were in this post or in other one) you must:
1- Download the files I provided you
2- Install SP Flash Tool
3- Choose the download agent
4- Choose the scatter
5- Press download and plug your phone (it must be OFF)
6- Wait and enjoy.
I must thank to everyone who give us this files. I couldn't unbricked my phone without your help
Click to expand...
Click to collapse

>Taps< said:
Ok, so fastboot didn't work at all (just waiting devices)
I tried to reflash TWRP nothing happens, I tried to do a factory wipe with twrp but nothing happens too.
I searched a stock recovery for nokia 3 1032- Android 7.0 but found nothing - must i use stock recovery for Android 7.1.1 or do you have a link to a stock recovery for 7.0 ?
------------
I found this on XDA : Is it a good way if nothing work ?
Click to expand...
Click to collapse
I think that this is the link:
https://forum.xda-developers.com/nokia-3/help/nokia-3-preloader-bricked-t3719357/post76069467#post76069467
I used SP flash tools to downgrade and install TWRP in my phone.
Which tool did you use to downgrade your phone?

Isrks said:
I think that this is the link:
https://forum.xda-developers.com/nokia-3/help/nokia-3-preloader-bricked-t3719357/post76069467#post76069467
I used SP flash tools to downgrade and install TWRP in my phone.
Which tool did you use to downgrade your phone?
Click to expand...
Click to collapse
Ok thanks :fingers-crossed:, I will try it
To downgrade I used OST LA and to flash TWRP I used SP flash tools

>Taps< said:
Ok thanks :fingers-crossed:, I will try it
To downgrade I used OST LA and to flash TWRP I used SP flash tools
Click to expand...
Click to collapse
Good luck. :fingers-crossed:
You can flash again with OST LA. Or try to flash with SP flash tool the whole rom or just the recovery. To flash with SP flash tools you need a nb0 unpacker tool (my previous post have a link to another post with the tool link).
BTW feel free to ask something that you don't understand. :highfive:

Isrks said:
Good luck. :fingers-crossed:
You can flash again with OST LA. Or try to flash with SP flash tool the whole rom or just the recovery. To flash with SP flash tools you need a nb0 unpacker tool (my previous post have a link to another post with the tool link).
BTW feel free to ask something that you don't understand. :highfive:
Click to expand...
Click to collapse
Heyyyyy !!! Thank you !!!
It works again :victory: !!!
I used OST LA to reflash it !!! Thanks again <3

I think I will use the second alternative step to not get a brick bootloader ^^' https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
----------
Do you know the safest way to relock the bootloader ?

>Taps< said:
I think I will use the second alternative step to not get a brick bootloader ^^' https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
----------
Do you know the safest way to relock the bootloader ?
Click to expand...
Click to collapse
Is like unlock bootloader, just change "fastboot oem unlock" to "fastboot oem lock".
But your internal storage will be formatted again by stock recovery, so you must have stock recovery installed.
After relock, your device will get ota updates, so you need stock recovery to install them.
I recommend root your device after all the updates, even you can install TWRP without problems.
I installed TWRP, root and installed stock recovery to get updates. Choose the method that you like.
Good luck. :highfive:

stuck at bootloader , No OS No Recovery :(

hi my oneplus 7 pro 1910 stuck at bootloader and when i press start or recovery it gets back to the bootloader screen i cant even turn off the phone
i accidentally wiped all partitions in twrp and made a format .
anyhelp ? ive tried to do the fastboot rom flash but my pc doesnt detect my phone
i tried almost every solution i found but nothing works

Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?

@soka said:
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
Click to expand...
Click to collapse
Yes it’s unlocked , any help

Search on the fast boot rom thread for the fast boot rom version you were last on, i have used this many times and it worked.
One thing to note, after it flashed everything , I ended up in crash dump error. I went into stock recovery and wiped/formatted my device and it boot up great.

https://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ - just follow this guide

One thing that worked for me is when your phone is plugged into your pc open a command prompt and type fastboot boot twrp-*.img (make sure it is the .img not .zip), and from there download the twrp installer .zip and flash that, reboot to recovery, and install the OTA for your device (OTAs can be found at this thread).
If it fails to boot and gives you an error, try fastboot getvar all to see which slot is currently active then do fastboot --set-active=*inactive slot letter* then fastboot --set-active=*original active slot letter* then try to boot to the twrp .img from fastboot again. If fastboot doesn't detect your device at all, try seeing if adb devices outputs anything, and if it does type adb reboot bootloader