I would like to find Moto G's (XT1028) 4.4.2 or 4.4.3 stock firmware. I can't find them anywhere... I can only find 4.4.4. But I want to downgrade from that. Does anyone have/knows where I can get the firmware/recovery?
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
You would be wise to go no earlier than Android 4.4.4, and to use a ROM zip rather than Firmware Image. Read this thread:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Edit2: Now I am having problems with 'fastboot flash system system.img_sparsechunk1' (all 4) and I got 'invalid PIV signed system image' so now I need help with that fixing that so I can downgrade.
Edit: fix it. The guild told me to use mfasboot but I tried just mfastboot and it worked better and it was fix. I might try to downgrade again using fastboot not mfastboot! I just wanted to let everyone to know I fixed it.
Well it did not work... So I revert back to 4.4.4 well reinstalled the recovery files for it because did not work as much. Now my phone restarts every so often and does not connect to WiFi; well the WiFi does not turn on it just says turning on WiFi the whole time. So now I need help to fix the phone. Can anyone help now?
Related
in this thread here (http://forum.xda-developers.com/showthread.php?t=2504712&highlight=baseband) is a thread about flashing a new baseband. I need to know if someone can pull the baseband from 12.15.15.
heres the situation. I received a replacement device from Verizon today as the camera on my current maxx keeps failing to initialize (low and behold as soon as the new phone arrives, the old one starts working LOL)
Any who..i wanted to root the phone and then update to 4.4 and since this phone shipped with 4.2.2 i figured why not try Jcase's methods.
Soooooo i made the mistake of using House of Moto and flashing the 12.15.15 firmware over top of the current OS instead of flashing the update file. Big MISTAKE. the phone booted and was fine..except no radio. no signal. baseband was missing. completely. sooo i decided to do a factory reset. now the phone wouldn't go past the activation screen. So i searched out the forums and found the thread above. but I believe the baseband is for the MotoX and the revert that is posted is for 12.7.7.. either way..the flash was successful and the phone boots and runs fine.. However..upon trying to upgrade to 4.4 it gives me an error message about the modem having unknown contents. Which leads me to believe that the baseband i reverted to is the 12.7.7 not the one for 12.15.15. Now the phone goes right to AP Fastboot and says 'Partition (boot) Security Version Downgraded. If i can flash the correct modem files, i can then try and reapply the update. Im going to see if i can FXZ back to 12.15.15 again. but who knows if it'll work
Can anyone help me?
dano1282 said:
in this thread here (http://forum.xda-developers.com/showthread.php?t=2504712&highlight=baseband) is a thread about flashing a new baseband. I need to know if someone can pull the baseband from 12.15.15.
heres the situation. I received a replacement device from Verizon today as the camera on my current maxx keeps failing to initialize (low and behold as soon as the new phone arrives, the old one starts working LOL)
Any who..i wanted to root the phone and then update to 4.4 and since this phone shipped with 4.2.2 i figured why not try Jcase's methods.
Soooooo i made the mistake of using House of Moto and flashing the 12.15.15 firmware over top of the current OS instead of flashing the update file. Big MISTAKE. the phone booted and was fine..except no radio. no signal. baseband was missing. completely. sooo i decided to do a factory reset. now the phone wouldn't go past the activation screen. So i searched out the forums and found the thread above. but I believe the baseband is for the MotoX and the revert that is posted is for 12.7.7.. either way..the flash was successful and the phone boots and runs fine.. However..upon trying to upgrade to 4.4 it gives me an error message about the modem having unknown contents. Which leads me to believe that the baseband i reverted to is the 12.7.7 not the one for 12.15.15. Now the phone goes right to AP Fastboot and says 'Partition (boot) Security Version Downgraded. If i can flash the correct modem files, i can then try and reapply the update. Im going to see if i can FXZ back to 12.15.15 again. but who knows if it'll work
Can anyone help me?
Click to expand...
Click to collapse
Try the fxz it should work it will reset everything.
bigv5150 said:
Try the fxz it should work it will reset everything.
Click to expand...
Click to collapse
tried to FXZ to 12.15.15 but because the recovery has been updated to 4.4 recovery...it won't fxz. still gives me the security version downgrade error. Looks like i might have to wait until the FXZ for 4.4 comes out for the Maxx
And..(for now) the camera in my other maxx is working LOL sooo i just throw my sim back in that one for the time being. Hopefully the camera doesn't fail again.
dano1282 said:
tried to FXZ to 12.15.15 but because the recovery has been updated to 4.4 recovery...it won't fxz. still gives me the security version downgrade error. Looks like i might have to wait until the FXZ for 4.4 comes out for the Maxx
And..(for now) the camera in my other maxx is working LOL sooo i just throw my sim back in that one for the time being. Hopefully the camera doesn't fail again.
Click to expand...
Click to collapse
there's and FXZ for 4.4 floating around here somewhere
Edit: and here it is https://www.dropbox.com/sh/om9j3iys8em3ccf/2r5u7m-h4d
I have to go to work.. But I will download when I come home. I hope this works lol
Sent from my XT1080 using xda app-developers app
BladeRunner said:
there's and FXZ for 4.4 floating around here somewhere
Edit: and here it is https://www.dropbox.com/sh/om9j3iys8em3ccf/2r5u7m-h4d
Click to expand...
Click to collapse
Thanks for that link man. I downloaded the file while i was at work..and used Fastboot to manually flash the entire OS completely. Phone is 100% up and running again.. AND!! The camera works!!
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Try putting twrp back on and flashing stock Lollipop Rom. http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 You can also try aosp, cm12.1 or any other lollipop ROM.
The Lollipop OTA is very picky, I believe any modifications to the stock firmware will cause the update to fail. You will need to have a completely stock system for the OTA to install successfully. Find the correct KitKat firmware for your phone and flash it then try upgrading.
Hi.
I'm having a similar problem with te OTA being picky (topic here).
Is there a stock firmware "file map" so that we can check manually what is wrong and erase/add needed files ?
Maybe this could be done by checking a flashable stock rom ?
Thanks a lot guys.
EDIT : Found a solution here http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072.
Worked perfectly !
OP, I am in the same situation. I did the same as you, and got the same results. Have you managed to solve it? It would be nice if you tell what you decide to do and what's the outcome. Thanks!
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Update to 5.1 success..... erm, well it's all relative
Eventually managed to update my XT1039 to 5.1 via ota.
Started with a fully charged phone and flashed 4.4.4 stock firmware (http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619).
Once completed, powered up phone and signed into google play then updated the motorola update services app.
DO NOT install a custom recovery or root yet or the update will fail!
Start the update by going into settings/about phone/system updates.
After first boot into 5.1, do a factory reset.
To root once the upgrade is completed, download cf autoroot (http://forum.xda-developers.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406) and unzip to a folder on your pc. Open a command prompt and change directory to this folder. Powerup handset in bootloader mode (hold vol down while switching on), connect USB and run 'root-windows.bat' from the command prompt.
So far I'm hugely disappointed in the update as I use WiFi tethering alot and it appears to be a massive fail. I know it wasn't 100% in 4.4.4 or CM12 5.1 with both reqiuring an occasional reboot, but in 5.1, something's just not right and it's basically unusable (could it be updated radio or something?). Fortunately, USB tethering appears flawless.
Another obsrvation seems to be abscence of a + appearing in the HSPA signal indicator, I seem to be getting just the H appearing regardless.
Also no more bluetooth visibilty timeout setting.
After installing CWM 6.0.5.0, I got gliches with the display in recovery mode but it works.
Now after I have it rooted, ad free and de-bloated, fixed the power on logo and installed CWM 6.0.5.0, I'll stick with it for a while to just to see how the battery lasts.
In hindsight I should've stuck with CM12 5.1.
URGENT HELP
On installing the update of 16.1 mb. The droid shows a error while installing after the reboot.
Nothing happens after that and the phone reboots
Right now it it running on 5.1.1
Same problem, LMY48B
I have the same problem, OTA update comes in a few times a day and never works, i simply get the message "Error". My update is 10.1 Mb. I am on build nr LMY48B and have Android version 5.1.1. When restarting using the power and volume button, the error message says "Empty". I tried Nexus Root Toolkit to update, no result.
Has anyone an idee to eather update or kill the updates all together?
Solution found !!Huraay!!
I just found a solution to this problem. You ll have to flash your nexus to stock (it is formatting not rooting)
Here are simple steps to it:
1. Enable Bootlegger
2. Turn on developer mode, enable USB debugging
3. Use a flash factory image (download it from any source)
Now you ll get 3 back to back OTA updates in settings, just install them and finally you ll get Marshmallow update of 403mb.
DONE.....
Cheers.
Contact if you still have a problem.
Thanks for sharing this. I tried to follow your instructions, using NEXUS Root Toolkit. At first i tried factory image 5.1.1, but this did not work , it just stopped. After that i tried to flash Hammerhead 6.0.0. Wich actually looked very promissing during the proces. After finishing reboot started, and it won't get out of reboot. I tried several times, up to 15 minutes. I also tried a factory reset, but it still keeps running the marsmellow startup grafic. Since i can't get into unlock mode, i do not have the opportunity to reflash the phone. Any ideas how to get out of reboot?
Hi,
We need to know more, what's actually failing. We could try and flash the update with TWRP, we'll get some output from there. Might be your radio or bootloader versions, for example.
And you using a toolkit, it doesn't help.
So, go learn some fastboot and some adb while you're at it, because you're going to need it. Guides to both are stickied everywhere around here.
Also, don't see the point on flashing a 5.1.1 factory image at this point, if the goal is to update to 6.0 (looking at the other user posting on this thread): just flash 6.0 factory image.
Sent from my Nexus 5 using Tapatalk
Please could someone help ! I'm trying to unlock my XT1032. I have the correct Sim-Unlock (network unlock) code from my old telco, but... it won't work because the phone is rooted, bootloader unlocked (S-ON) running CM13.
I figured that returning it to a stock build would allow me to unlock the phone, then I could re-root and return to CM13 on my new network.
However..... there are about a dozen guides on returning a Moto G to stock and the first one I tried left the phone stuck on the 'Warning: Bootloader is unlocked' message. Since then, I've tried several other guides and have got nowhere fast. I've been on this for four hours now and the only thing I seem to be able achieve is to get TWRP or CWM recovery on there by flashing from fastboot. Every other image I try either gives 'preflash validation failed' messages, sticks on the Bootloader Unlocked screen or gets it stuck in a bootloop!
I just want to switch networks... Why is this so bloody difficult ?
What Firmware did your XT1032 originally come with? or which Carrier?
Kitkat I think, and it's Tesco (UK).
I subsequently did the OTA update to Lollipop and then.... WHOAAAAA.... hold on... it's booting !!!
I don't know how, or what I've done to get this far, but the only thing I can think of that's changed is that the battery is now at 100% charge. It appears as though it's successfully flashed the 5.1 untouched ROM from http://forum.xda-developers.com/devdb/project/?id=7981#downloads
But, I've tried flashing that loads of times this evening and it's failed everytime.
Having said that it's booting, it's sitting here on the Motorola logo - and it hasn't got that far in the last five hours.... I'll be back shortly !
Update: It worked ! It completed the boot, I put the new SIM in, it asked for the unlock code and this time it worked OK. Now I'm tackling putting CM13 back on it. I think I'll stick with TWRP rather than CWM recovery, as long as TWRP can handle the automatic updating for the CM nightlies.
I have no idea what went wrong there - maybe it was just that the battery had to be at 100% ?? Who knows... Thankfully I doubt I'll be tackling that again !
I don't know if things have changed, but I would be careful with OTA Updates in CM. People have hard-bricked (phone is effectively destroyed) applying updates in this way. I also suggest you avoid official Motorola updates, rather use the factory firmware images available here: (which already include the content of OTA Updates)
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images
Thanks for replying anyway mate. In the end, it's all good now. Unlocked and back on CM13 and on my new network !
Ahhh... not so good after all. The phone reboots every time you try to uninstall an app. I've tried flashing back to CM12.1, the latest stable release, and it does the same, so I've obviously screwed something up along the way.
Could someone help me flatten this thing completely and get it working normally please?
I've tried reflashing loads of times, even tried Cyanogen Recovery instead of TWRP but nothing I do gets rid of this reboot problem.
Can anyone assist please?
OK, so I've followed the procedure detailed here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 and flashed the Untouched 5.0.2. EU Stock ROM successfully, but it still reboots when you try to uninstall any app.
Whatever it is that's causing this is not getting overwritten by the flashing procedures I'm using is it ?
HELP !!!!!
@aneng64 - You have not done what I told you to do. Read my post again.
Yes I did... and I still had the same problem. It was only once I stopped trying to flash zips from TWRP and used mfastboot to flash the whole set individually (non-hlos, motoboot etc) that I got it to behave. The issue, incidentally, seemed to be the same one mentioned elsewhere here that also causes settings to crash when you try to go into settings, security.
Once it was stable with a stock ROM, I was able to flash CM13 again and it's now sorted. Thanks for your help anyway.
I have an HTC One M9 (Sprint) software version 2.11.651.19 (OPJA2) with Android v5.1
Within the last couple months I unlocked the devices bootloader, and rooted it. Last night I left the phone under my laptop and I'm thinking it got way way way too hot, somehow the thing is still alive, however when I went to turn it on in the morning, I had no wifi or cellular capabilities. At first I assumed this was a hardware issue, however I then unrooted the device on a whim, and this fixed it (Until I turned it off again, to my dismay).
I'm thinking somehow my phone overheated (Which explains why my battery life won't go over 47%) and somehow my flash memory must have been corrupted because I can no longer boot into recovery mode, which is my serious catch 22. Since I figure this is some issue related to my firmware, which I would LIKE to reflash (This is my goal here). To my dismay, in order to flash a stock RUU or firmware to the device, you must have your bootloader relocked. However in order to relock your bootloader you must have root, and like an idiot I unrooted it. I can't reinstall SuperSU through my TWRP recovery because my phone refuses to boot into recovery mode. I attempted to re-flash TWRP to the device through download mode, the flashing is completed successfully, however I still cannot boot into my recovery. To break it down simply:
-Want to reflash stock firmware
-Must have root to reflash stock firmware/RUU
-Don't have root because I uninstalled it
-Can't re-root because my recovery is corrupted
-Can't re-flash TWRP (Already tried and it's not working)
-Can't re-root because I can't flash TWRP
-Can't reflash stock firmware because I can't disable it with root
Regardless of this I attempted to use adb and echo to relock the bootloader however instead of getting # I get $, so I'm not really able to do this either. Is there ANY way I can repair my recovery, has anyone ever run into an issue like this before? Or am I just completely screwed, hahaha.
Do you think I might be able to reflash Android V5.1 to try and fix the corruption and then maybe that would allow me to get into recovery mode so I can flash Super SU so I can at least factory reset my device with TWRP, or possible reload stock firmware and factory reset from there?
Thanks guys for any help you can provide.
*EDIT
If anyone wants to provide any advice great, but for now I'm going to try using HTC Sync Manager to load Marshmallow (v6.0) onto the HTC and see if this may allow me to actually get into recovery mode. Downloading the file from here: *nevermind can't post links yet, under 10 posts, you can find it on HTC's website* (This is for the HTC One M9, Sprint) in case anyone else EVER has to run into this awful issue, lol.
Moderators please feel free to update the thread to SOLVED status, I was able to update my phone to marshmallow to resolve the issue. This time around I WILL be backing up my phone, probably not going to root it this time around either, I have like 3 other phones so I'll just root them instead, lol. If you would like the download link I am happy to provide it VIA PM so you can update my OP with the link for the full fix. My phone is able to get wifi and texts now without an issue, unfortunately all my data is wiped but honestly I don't really care!!
Thanks everyone!
Good job on solving your issue.
If you have further questions or want to help out others, you can do so here
http://forum.xda-developers.com/sprint-one-m9/help
http://forum.xda-developers.com/sprint-one-m9
Thread closed