Related
Back to stock recovery, help!
Hi, need help with my beloved Moto G (XT 1063). I rooted it, installed custom recovery and image and used it for months like that, two days ago went back to stock (restored from nandroid backup) and got a message about the new OTA update, download it but TWRP cannot install it, the phone just turns off again and again. Restored it once more, but this time did not give it a go to update. My question is, is it possible to flash just the original recovery (for Lollipop) and how in order to update the phone, or is it possible to stop the phone warning me about the new software being available all the time (so annoying). Thanks for any input.
Same here. My wife just got a new Zenfone 2, so I'm giving her Moto G 2014, XT1063 to my daughter.
I want to get it back to stock so it can get all the updates.
It currently has TWRP installed and is rooted.
Every single link I've found here in the XDA forum for the stock firmware for this phone is dead. The links all say they were pulled because of TOS violations.
Anyone have a mirror? Or are there any flashable zips that work with TWRP to get this phone current?
Here is the current About Phone information:
Android version
4.4.4
Baseband version
MSM8626BP_1032.394.88.00R,
RETUSA_GLB_CUST
Kernel version
3.4.42-g6c9aef2-00110-gd543d01
[email protected] #1
Thu Jul 24 16:10:12 CDT 2014
System version
21.11.17.titan_retuglb.retuglb.en.US retus
Build number
KXB21.85-17
http://i.imgur.com/jdxfXFB.png
Have you checked these links?
http://forum.xda-developers.com/showthread.php?t=3153533
For me the links are working but I know that Mega isn't allowed in all countries.
If you want to download with your mobile you need the Mega app, on your PC it can be done with the browser.
Choose the right firmware for your phone, extract the recovery.img and flash it.
Use the full unroot function of the superSU.
Sent from my XT1068
I want to flash the marshmallow update to my phone and I can't seem to find the stock system image for the TMO xt1095. Anyone have a good download link for this file? I went to file factory but I have to wait 6 hours for the download.
There's one here, it seems a little newer:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Motorola Z2 Force users! Your issues will be resolved!
Reasons for using this method:
If you haphazardly flashed a ROM, and now can't boot.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock.
You then can update.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:
Motorola Firmware Team for the zips
Great, So you've read why you might have borked your phone!
Now, let's get it fixed! Below is the link to the only flashall bat file I currently have. This is a simple process to do. There are some requirements though.
Requirements:
Correct drivers (ADB and fastboot is included in the utilities zip if you don't have minimal adb and fastboot installed, or don't have the SDK.)
Over 4GB of RAM.
How to fix your phone:
Download the Utilities zip
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
This process can take up to 10-15 minutes depending on USB connection and your PC
Disclaimer: I did not personally test the zips below besides the Sprint and T-Mobile ones. These are the official Firmware links from the Motorola Firmware Team. My only contribution is this thread and the utilities zip.
Disclaimer 2: it is never suggested to flash a zip not intended for your device/major patch version. If you're on Oreo, DO NOT FLASH NOUGAT. (I flashed T-Mobile to my Sprint phone for testing purposes and so I can tell you what it does. I lost all sim functionality and had to do some wonky stuff to get my phone back to working shape... Word of advise: don't do it.)
Disclaimer 3: if you have minimal adb and fastboot or the Android SDK, please be sure you update to the latest fastboot. The exe files included in the zip are for those who don't have a development environment set up.
Downloads:
Flash All Utilities
AT&T Oreo Flash All
Sprint Oreo Flash All
T-Mobile Flash All (Not official download link, but official files, See here)
USC (check version) Flash All
Verizon Flash All
NOTE: yes, it's in the Z2 play folder. Motorola Firmware Team did not make another folder for our device. Check the file name. It has "Nash" specifying the Z2 force. If you ask why it's in the Play folder, I will not respond.
If you have any other official links, I will add to second post and give proper credits to who found the zip. Only perm links like the AFH ones I posted.
Uzephi said:
First: The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA. This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
This zip will fix that and put you back to stock on the "August" security patch (September update). You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits: Motorola Firmware Team for the zips
Me for modifying the zip to fix oem.img issue on B partitions and turning the xml into a simple flash all.bat
Note: I am mobile and I will clean up the OP and second post when I get time @ home
Click to expand...
Click to collapse
I was going to add yours in but kinda got busy
Thanks for this! I flashed a modified boot.img for root to get my phone unlocked, and flashed the stock kernel back, but I couldn't update to the September patch. After flashing this, updates are working fine. A bit of a lifesaver!
full circle...
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
esuormai said:
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
Click to expand...
Click to collapse
I don't take donations, just pay it forward! Thanks for the offer though.
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
WeUseLord- said:
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
Click to expand...
Click to collapse
Added in requirements, thank you for verifying that.
Uzephi said:
Added in requirements, thank you for verifying that.
Click to expand...
Click to collapse
Okay thanks OP
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
cooleoboom5 said:
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
Click to expand...
Click to collapse
That is a "permanent" flag that triggers when you flash something unsigned and not from Motorola. I.E. custom boot image for root. Reason it's in quotes is because we don't know how to return it back or if we even can.
moto z2 force
WeUseLord- said:
Okay thanks OP
Click to expand...
Click to collapse
where do you download the bat file from
irule1977 said:
where do you download the bat file from
Click to expand...
Click to collapse
It's in the zip
So Sprint Z2 can't get GSM unlocked by flashing ROMs from other carriers? Any idea how it can be unlocked?
How to get back to software status official in bootloader menu? I did managed to do it with T-Mobile version but cant get that from this one.
Uzephi said:
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Sprint Motorola Z2 force users! Your issues will be resolved!
First: Our phone differences
The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA.
This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
Reasons for using this method:
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock on the "August" security patch (September update).
You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:Motorola Firmware Team for the zips
Versions currently available:
NCXS26.122-59-8-6
NCX26.122-59-8
NCX26.122-51
Versions on OTA but no firmware files available:
NCXS26.122-59-8-9
Click to expand...
Click to collapse
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
robdevil said:
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
Click to expand...
Click to collapse
I would only release something I can test. I don't have TMobile service, so I won't be releasing TMobile only firmware. There is a thread by joemossjr for TMobile flashall.
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
hackenggr said:
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
Click to expand...
Click to collapse
My Sprint model has the -03 identifier. You should be safe if the bootloader is unlocked. Needs that to flash this
Hi!. I recently received my new Moto E5 XT1944-1 and i wanted to root, unlock bootloader and everything. For that reason i enter this forum and get the TWRP recovery from de Moto E5 (James), but i dont know that the James (5,2 inch screen) is not the same that my Moto E5 (5,7 inch screen), and now the recovery seems to be corrupt and cant enter, only enter on fastboot mode. I need to say that the smartphone boots normally, but i fear the day that i need to make a full wipe and cant enter recovery. What can i do to reflash the original recovery?. Thanks to all help given.
Edit: I need to say that the bootloader is successfully unlocked, but still the problem with the recovery.
intherior said:
Hi!. I recently received my new Moto E5 XT1944-1 and i wanted to root, unlock bootloader and everything. For that reason i enter this forum and get the TWRP recovery from de Moto E5 (James), but i dont know that the James (5,2 inch screen) is not the same that my Moto E5 (5,7 inch screen), and now the recovery seems to be corrupt and cant enter, only enter on fastboot mode. I need to say that the smartphone boots normally, but i fear the day that i need to make a full wipe and cant enter recovery. What can i do to reflash the original recovery?. Thanks to all help given.
Edit: I need to say that the bootloader is successfully unlocked, but still the problem with the recovery.
Click to expand...
Click to collapse
Because the Moto E5 series is so young in terms of both its recent release and its limited support within the Android community, finding factory firmware packages is not easy right now. Typically, in your situation, simply extracting a stock recovery image from a firmware package and flashing it in fastboot would be your best remedy by far. But, if you have corrupted your recovery partition and are unable to locate a stock image, I would recommend first that you ask some members and devs on the furum to dump a stock recovery image that you could flash to fix your issue. Second, if you are rooted, make an immediate dump of your /system, /boot, /oem and /vendor partitions. That way, if your OS does decide not to boot, you can restore your partition dumps via fastboot (as long as your bootloader is unlocked). If you are not rooted and are thus unable to dump your key partitions, I'd advise to just be really careful in terms of modding or tweaking your stock OS. Firmware packages will likely be available by September, maybe sooner. Until then, reach out and ask some members & devs if they can provide you with a stock recovery image. Good luck...
First, thanks for your fast reply. My phone isn't rooted yet, i stop doing the guide of the James version because i think i do it worst. I can test the Kingroot app o whetever it names, but i prefer to wait and stop installing apps (only the basic: Telegram, Youtube, etc for daily use). I dont know who Devs or Members have this system. But i will stay reading this section of forum everyday to stay update of the news. Thanks for all pal!.
Edit: Sorry for my bad english, i'm spanish and dont know so much
intherior said:
First, thanks for your fast reply. My phone isn't rooted yet, i stop doing the guide of the James version because i think i do it worst. I can test the Kingroot app o whetever it names, but i prefer to wait and stop installing apps (only the basic: Telegram, Youtube, etc for daily use). I dont know who Devs or Members have this system. But i will stay reading this section of forum everyday to stay update of the news. Thanks for all pal!.
Edit: Sorry for my bad english, i'm spanish and dont know so much
Click to expand...
Click to collapse
It's ok friend. I understand you good. I am currently developing for the James xt1921-5 (Boost/Virgin/Sprint) variant and, as such, I am keeping a close watch for factory firmware to be released for the James. I will contact you as soon as I can confirm a firmware source for your particular model (xt1944-1). Currently, there are only paid subscription-type repositories which offer firmware downloads online. I don't recommend or support sources that charge a fee for firmware. But, it won't be long. September at the latest, possibly sooner.
MotoJunkie01 said:
It's ok friend. I understand you good. I am currently developing for the James xt1921-5 (Boost/Virgin/Sprint) variant and, as such, I am keeping a close watch for factory firmware to be released for the James. I will contact you as soon as I can confirm a firmware source for your particular model (xt1944-1). Currently, there are only paid subscription-type repositories which offer firmware downloads online. I don't recommend or support sources that charge a fee for firmware. But, it won't be long. September at the latest, possibly sooner.
Click to expand...
Click to collapse
Thank you so much!. I will stay update to any news here. I know that this model is so soon, my network provider offers me this, and cause i allways use Motorola (Moto E1, Moto G, Moto G2014), then i accept thinking that the scene was more advanced. My surprise when i see that this version was recently released...
Well, then it's time to wait to see how the scene grow up.
Regards pal!.
intherior said:
Thank you so much!. I will stay update to any news here. I know that this model is so soon, my network provider offers me this, and cause i allways use Motorola (Moto E1, Moto G, Moto G2014), then i accept thinking that the scene was more advanced. My surprise when i see that this version was recently released...
Well, then it's time to wait to see how the scene grow up.
Regards pal!.
Click to expand...
Click to collapse
Great news @intherior -- Motorola Mobility has leaked some factory firmware packages for yours and a few other variants. I'll be posting a thread with download links by tomorrow evening. In fact, here is you a link to the specific file you need -- the stock recovery image for the xt1944-1. You can flash this via fastboot mode by:
fastboot flash recovery recovery.img
Link: https://drive.google.com/file/d/17sgV8t6jYgahml6Huv3Hq2IgygqJZnsH/view?usp=drivesdk
Yeah!!! That's really very good news!. I'm not at home now, but this night i Will download and comment if it fix my problem. Thank u so much bro!
Edit: One picture is better that thousand words xD
Thank u bro!. Finally was fixed with the recovery u posted!. Now i take care from do something stupid. I will wait to a stable and probed version of TWRP to finally get my Moto E5 Xt1944-1 rooted. But for now i will take it easy.
Regards my friend! :fingers-crossed:
intherior said:
Yeah!!! That's really very good news!. I'm not at home now, but this night i Will download and comment if it fix my problem. Thank u so much bro!
Edit: One picture is better that thousand words xD
Thank u bro!. Finally was fixed with the recovery u posted!. Now i take care from do something stupid. I will wait to a stable and probed version of TWRP to finally get my Moto E5 Xt1944-1 rooted. But for now i will take it easy.
Regards my friend! :fingers-crossed:
Click to expand...
Click to collapse
Very glad the stock recovery worked for you. I have an entire stock firmware package for your device if you ever need it to restore your device to factory state. Just let me know and I'll upload and post a link. Cheers...
Sure bro!. Will be good to keep that firmware safe if I have any problem. Give me the download link when you have time. Thanks again!
Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched
Hey all, I just updated my wife's P4 to Magisk 20.4 as of yesterday and have had no issues so far on the new version (nor on my P4XL). Here are the stock and recently newly updated Magisk patched (v20.4) boot images. I couldn't direct install the update on either of the phones via Magisk Manager, so I figured I would share these images.
Stock March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757144
Magisk Patched (v20.4) March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757143
Remember, these are ONLY for those on QQ2A.200305.003 firmware already. Don't flash if you don't know what you're doing.
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
falawefulwaffle said:
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Click to expand...
Click to collapse
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
Spookymyo said:
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
Click to expand...
Click to collapse
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
i5lee8bit said:
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
Click to expand...
Click to collapse
Thanks for the reply. I ended up getting it to work using the "payload_dumper-win64" method i found in another thread to extract the boot.img from the payload.bin file. Turns out the OTA file was online from google.
To updatePixel 4 xl with "coral-ota-qq2a.200305.003-3b25765d" MAach update OTA software:
- uninstalled Magisk
-updated software
-reinstalled magisk
-patched the boot img from payload.bin
-pushed modified boot to device
-Done
Everything seems to be working well. I got to use python for the first time, so that was kind of fun. I was a flashing machine back around the galaxy s4.
I got root working. Spent so much time trying different things and all I had to do was factory reset my phone. There must have been some file or module interfering with the process. Once I reset my phone the root process went without error. ?*