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 : (

[XT1033][MOTO G][DUAL SIM]What Not to do during DOWNGRADING from Brazil OTA 5.0

There is only 1 main point that I wanted to share with others....
DO NOT EVER EVER TRY TO FLASH THE BOOTLOADER OF ANY ROM OTHER THAN 5.0/5.0.1 OR LATER VERSIONS AFTER YOU HAVE UPGRADED TO LOLLIPOP!!.
Let me tell you first what happen if you do so........
1.) 95% Probability of Permanent Hardbrick Device
2.)Intense Graphical Glitches[These can be get rid off by flashing cm12 or any Android OS 5.0/5.0+ since it has upgraded bootloader]
3.)You May NEVER ever recover your device again.
How will you recognize you are about to flash Bootloader??
It usually has a name "motoboot.img"
What if the name is different?!
Let this time the name is abcdefg.img
The guide you may be following will ask you to perform a command line query on fastboot by the syntax-
"fastboot flash motoboot "abcdefg.img"
Pay attention it still has motoboot in command line.
Now why this happens??
I believe that with the release of Android 5.0 aka Lollipop, the Bootloader of ROM has been upgraded and modified to work with ART system efficiently.
So if you flash the older Bootloader over an upgraded one, you are gonna regret your move completely.
What is Permanent Hardbrick?!
This is a state of your phone which cannot be recovered either easily or permanently. Your device becomes completely useless. You will only see a black screen. Neither you will access Fastboot Mode nor Recovery. Your Phone will become a showcase or in other words a real BRICK.
An Advice- If you are going to flash a zip via a custom recovery like TWRP/CWM/PHILZ. First do check it by opening that it should not have the bootloader image file. If it has, make sure you delete it and then try flashing it.
Now I will share my experience-
How I Downgraded successfully
1.) I Installed a custom recovery via fastboot. [TWRP 2.7.1][2.8.1 WILL DO IT TOO]
2.)Wipe Data/cache/Dalvik Cache/etc,..The normal procedure.
3.)Copied the ZIP file of Moto G Revolution G XT1033 4.4.2 Brazil Firmware to my pendrive.
4.)Make sure your pendrive is in FAT32 Format. if not do a format in FAT32.
5.)Connected via OTG Cable to my phone in recovery mode to TWRP Recovery.
6.)Mount OTG Storage in Mount Option.
7.)Chosen my zip file under flash option and flashed it successfully.
Cons: A water like wave keeps coming from the top of the screen to bottom while booting up but goes off as soon as you turn your screen off for the 1st time. then its all normal again.
Link to Revolution G Firmware- https://forum.xda-developers.com/showthread.php?t=2690047
Guys this is my 1st post here that is well laid. Hope you thank me if this helped you.

There's a tool called Motoflasher. It can do a blank-flash your corrupted bootloader with the latest one. But until today it only support 4.3, 4.4.2, 4.4.4. And for 5.0 will be coming soon. Motoflasher is a tool to revive your-corrupted-bootloader-device after do an accidental downgrade. :fingers-crossed:

Yes, but I want to know, what would happen, when you delete the bootloader. Will it still be under device manager. So will it get detected by windows?

Why would someone do that?!
Freakfussel said:
Yes, but I want to know, what would happen, when you delete the bootloader. Will it still be under device manager. So will it get detected by windows?
Click to expand...
Click to collapse
Delete the actual bootloader from the phone?! I would not recommend you to do that. Coz bootloader is the final option for a device's recovery.

[Q] Moto G no communication with Sdcard

Well, first thanks for listening, and please have patience, haha.
I have a Moto G XT1033, my cousin, he tried to unlock the bootloader and the process has not been finalized (I think) because the phone does not turn over, just stood in the LOGO screen.
I tried to reinstall the ROM Stock, but unfortunately I did not succeed
I tried several things and nothing.
I've tried:
1- reinstall the original ROM XT1033 4.4.4
2- install the original ROM XT1033 4.4.2
3- Install the ROM XT1032 4.4.4
4- Install the ROM XT1033 5.0.2
and nothing happened :'( .
so I tried to unlock the Bootloader to see if I could get into recovery mode, to be able to WIPE Cache and Factory. But that was when I discovered that even reinstalling the ROM's and clearing the caches, was not affecting anything on the phone, I was in the Install from SDcard and all folders were there (Whatsapp, PicsArt ...)
I can not install Custom Recovery and not install any ROM since it is not installing anything !!!
and when I Wipe cache it restarts on its own and does not delete anything!
I am Brazilian and I used Google translator to write this text, I hope to help me! Thank you for listening! <3
I have a Moto G XT1032 with unlocked bootloader, custom recovery TWRP and android 5.0.2 via adb, no problem

Can you boot into fastboot? Does it say the bootloader is unlocked?
So you are able to flash a stock ROM without errors?
Can you get into stock recovery to wipe?

audit13 said:
Can you boot into fastboot? Does it say the bootloader is unlocked?
So you are able to flash a stock ROM without errors?
Can you get into stock recovery to wipe?
Click to expand...
Click to collapse
Yes, but nothing works, the adb process of all "Okay" but when rebooting, it is only on screen logo and does not start, and after about 2 minutes it restarts again.

audit13 said:
Can you boot into fastboot? Does it say the bootloader is unlocked?
So you are able to flash a stock ROM without errors?
Can you get into stock recovery to wipe?
Click to expand...
Click to collapse
You can boot into fastboot? - Yes said the bootloader is unlocked? - yes
So you are able to flash a ROM stock without errors? - Yes and no XD (in adb shows that installs but does not actually install anything)
You can get in stock recovery to clean? yes and no (the screen shows that wiped but not actually cleaned anything, the fiction folders all there in the same place, whatsapp etc ...)

You are using ADB or fastboot to flash stock ROM? Fastboot commands only work when the phone is in fastboot mode.

audit13 said:
You are using ADB or fastboot to flash stock ROM? Fastboot commands only work when the phone is in fastboot mode.
Click to expand...
Click to collapse
good, I do not know a lot of things, but change ROM's and those kinds of things I can do, you see, is that what's going on I've never seen, practically the cell turned into a zombie, he's dead just not hahaha.
I'm using the ADB and Fastboot the in the same folder, and installed the ROM's in fastboot mode (vol - + Power)
it's OKAY in the installation process, only it does not actually install anything.
already tried deleting the cache but he n erases anything already gave factory reset and nothing happens: '(
researched two days and a half on the subject to try to solve it, but I was out of options, so I posted here in the forum, takes a lot to help me with this!
in the process with my phone got everything worked unlock the good bootloader, install custom recovery and rom lollipop
since my cousin was not so lucky
he screwed the phone in bootloader unlocking process (if I'm not mistaken)

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.

Flashed wrong rom into phone, now I can't flash full roms [HELP]

Well, long story short, I've managed to f*ck up my Moto G. I was having problems with the SD Card ejecting itself on the modified stock 6.0.1 Rom found here so I decided to go full stock again to have a good base to go to, and flash again TWRP, and Turbo or another rom. I had one stock rom downloaded, so I tried that one, I applied that with RSD Lite without noticing that wasn't for XT1542, but for XT1040, aka Moto 1st gen LTE. Needless to say that I received a black screen with red letters tell me that the kernel failed to load. I tried flashing again with stock 5.1.1 in RSD Lite and manually since the XT1040 rom was a 5.1.1, and I can't, gpt.bin fails to flash (preflash validation failed), so I skipped it, and skipped the bootloader like it was a downgrade from 6.0 to 5.1.1, and it worked, the OS boots, and I was able to flash 5.1.1 and 6.0 again, but can't flash anything else stock, like I was on a locked bootloader, even when it says "Device is UNLOCKED" and the "oem unlock {key}" says that the command doesn't work in the device in that state (unlocked) and I can't relock (it asks me to fully flash stock, which I can't do), and I can't manual flash anything else since gives the "preflash validation failure" error.
TL;DR: Flashed wrong stock full rom into G 2015, semi fixed it, phone works but now can't flash own device full stock roms. Send halp.

Did you Flash the bootloader from xt1040?

Have you tried fastboot erase? Erase all partitions and then fastboot flash. I had the same issue when I had Moto G1 and had to erase the partitions before fastboot flashing stock rom.

Śūnyatā said:
Have you tried fastboot erase? Erase all partitions and then fastboot flash. I had the same issue when I had Moto G1 and had to erase the partitions before fastboot flashing stock rom.
Click to expand...
Click to collapse
NO!!! Never do a 'fastboot erase all' - this is really bad, it will wipe the hidden partition that hold the IMEI and other special information, which may not be recoverable at all.
Fastboot flash the bootloader, then reboot to bootloader again, then proceed to flash each piece manually, should be OK. If you can't flash the bootloader, you are pretty much screwed.

HelpMeruth said:
Did you Flash the bootloader from xt1040?
Click to expand...
Click to collapse
I suppose so. Because the rom I flashed, I did it via RSDLite, and the flashing process wasn't interrupted in at any time.

acejavelin said:
NO!!! Never do a 'fastboot erase all' - this is really bad, it will wipe the hidden partition that hold the IMEI and other special information, which may not be recoverable at all.
Fastboot flash the bootloader, then reboot to bootloader again, then proceed to flash each piece manually, should be OK. If you can't flash the bootloader, you are pretty much screwed.
Click to expand...
Click to collapse
Thanks! I'll try that.

Update: Finally fixed it. I had to use another official stock rom (I deeply thank the guys that put together the stock rom images in the General section, true saviors there), this time the operator 'branded' rom (Personal Argentina) that came with the phone, because the Latin American Retail found here didn't work at all, and gave all that flashing errors. With that and RSD Lite flashed successfully, no errors whatsoever, and the OTA worked great so now my bootloader screen reads "Software status: Official" again. Thanks to everyone that replied.