Database Develop

[OTA] Moto G XT1045 4.4.4 OTA Update official_untouched.

Fresh off the servers, here is the 4.4.4 OTA for the Moto G XT1045_US
Link: 4.4.4 OTA_XT1045.
Enjoy.

rawtek said:
Fresh off the servers, here is the 4.4.4 OTA for the Moto G XT1045_US
Link: 4.4.4 OTA_XT1045.
Enjoy.
Click to expand...
Click to collapse
Is this just a flashable zip?

nklenchik said:
Is this just a flashable zip?
Click to expand...
Click to collapse
Yes, however it needs the stock recovery.

Out of curiosity how does one actually flash the OTA ?
IF I let the System Download the OTA, it will reboot, have an error and not complete the install. (using the stock recovery)
If I Push the update via ADB and use CWMR it tells me there is a footer error.
If I open the update with WinRAR or 7zip I get an unexpected End of archive.
Is the OTA itself Broken in some way (which is what it appears to be to me on the surface), or have other people gotten it to work on the XT1045 ?
I am Running the Stock rom, with the stock recovery. I even did a factory firmware Flash (though I cannot seem to relock the boot loader, everything else completes)

MissyVixen said:
Out of curiosity how does one actually flash the OTA ?
IF I let the System Download the OTA, it will reboot, have an error and not complete the install. (using the stock recovery)
If I Push the update via ADB and use CWMR it tells me there is a footer error.
If I open the update with WinRAR or 7zip I get an unexpected End of archive.
Is the OTA itself Broken in some way (which is what it appears to be to me on the surface), or have other people gotten it to work on the XT1045 ?
I am Running the Stock rom, with the stock recovery. I even did a factory firmware Flash (though I cannot seem to relock the boot loader, everything else completes)
Click to expand...
Click to collapse
just noticed that on mind as on my wife moto G she was able to download and install via system updates without a hitch and she is running stock even with a locked bootloader and the install complete with no errors however when trying to flash on mines with stock recovery and a unlocked bootloader it produces the same error, only thing different is the boot loader being unlocked on mines. I'll look a little more into this after work..will keep ya posted.

I installed 4.4.4 on my XT1045 without any problems last night, via the OTA update notification I received. My bootloader was unlocked. Full details here.

I got the update thru the regular update from the y XT1045 rooted with TWRP 2.7 1 0 the system ask me If I want to update, I say yes, on reboot got stuck on the Twrp push reboot system the phone reboot and shut down to get back to T W R P
after turning phone off the phone says Update unsuccessful
how to install from the recovery?
any solution?

guliver365 said:
I got the update thru the regular update from the y XT1045 rooted with TWRP 2.7 1 0 the system ask me If I want to update, I say yes, on reboot got stuck on the Twrp push reboot system the phone reboot and shut down to get back to T W R P
after turning phone off the phone says Update unsuccessful
how to install from the recovery?
any solution?
Click to expand...
Click to collapse
You need to use the stock recovery for this, not TWRP. Try castuis' instructions and see if they work for you too. Let us know if they do or don't.

Reverted back to stock before updating via OTA, no issues here. 64GB SanDisk finally works in 4.4.4. I am having an issue where the 64GB isn't really working in recoveries, like philz CWM or TWRP. Anyone got an idea what that's about? I figured if the card worked with 4.4.4 using the new kernel, the recoveries should also be fine.

Slinkwyde said:
You need to use the stock recovery for this, not TWRP. Try castuis' instructions and see if they work for you too. Let us know if they do or don't.
Click to expand...
Click to collapse
Revert it to stock Recovery, started the upgrade process again, after the reboot the update started but stopped to one third and gave me an error.

guliver365 said:
Revert it to stock Recovery, started the upgrade process again, after the reboot the update started but stopped to one third and gave me an error.
Click to expand...
Click to collapse
Finnaly working.:laugh: I got to reinstall a fresh copy of the stock firmware and the update went well just had to root it again and change the nasty warning about unlocked device

My XT1045 has an unlocked bootloader, TWRP in lieu of the stock recovery, and it's rooted. I also run Xposed.
I downloaded the 4.4.4 update via the official OTA process after being notified.
I further uninstalled my Xposed framework files. After rebooting, I realized I'd also need my stock recovery back.
After (visiting this forum and) reconsidering, I don't want to bother installing my update at this time.
Anybody know how I can revert those pesky dialogs asking me to install the update?
I think it's gonna do it every time I reboot.

danny8 said:
My XT1045 has an unlocked bootloader, TWRP in lieu of the stock recovery, and it's rooted. I also run Xposed.
I downloaded the 4.4.4 update via the official OTA process after being notified.
I further uninstalled my Xposed framework files. After rebooting, I realized I'd also need my stock recovery back.
After (visiting this forum and) reconsidering, I don't want to bother installing my update at this time.
Anybody know how I can revert those pesky dialogs asking me to install the update?
I think it's gonna do it every time I reboot.
Click to expand...
Click to collapse
Delete the OTA zip located in /cache using a root explorer. Or you can 'fastboot erase cache'.
People have reported success with OTA using Philz recovery. But i suppose that requires flashing a recovery which is the same effort as flashing stock recovery. Note: A modified system partition may still cause OTA error on stock recovery, and you may have to restore stock system partition by flashing system.img from your stock firmware.

I tweaked the updater script on mine to eliminate the stock recovery stuff before flashing with TWRP, and it seemed to work :
Code:
http://rhysw.com/peregrine/xt1045-4.4.4.norecovery.zip
Usual disclaimers apply; back up your device first ! Diff the changed updater script vs. the stock one. Do not use if you don't know what an updater script is.

Gentlemen..Not sure why all the reverting to stock recovery is needed, if your device is on TWRP..please help me to understand.?
Here's what I done with one of my XT1045's in a matter of few minutes..keeping my other XT1045 on 4.4.3 for awhile longer..
Running TWRP v2.7.1.0_peregrine (shabby penguin) version..
With this zip copied to the storage in the device, installed from TWRP, rebooted and never lost Root..simple, quick, painless..
Absolutely did NOTHING (except update framework) to XPosed, Gravity Box [KK 3.1.7], Advanced Power Menu [6.0a_r1], AcDisplay [2.4.7], Android L Navigation Bar [6.1], GPSNotifications [2.9]..
ONLY thing I had to do was update Framework..kept Root with no problems either..
This is 4.4.4_21.11.56 in flashable, installable zip format..
Here >> https://docs.google.com/file/d/0B67RS0BDBp_iOWhZdGlmWXpOQW8/edit?usp=docslist_api
sent by my Jelly Bean_ 4.1.2_98.72.16
(Root Exploit) XT912 Droid RAZR Maxx

Update fails
I have both the stock rom and stock recovery installed but I cannot get the OTA update to complete without an error and if I try to manually run the update from the stock recovery I also get the same error. The error is...
Verifying current system...
"/system/app/Drive.apk" has unexpected contents.
Installation aborted
I have gone as far as removing the drive.apk from my device altogether but it still gives me the same error. I have tried installing a fresh copy of the drive.apk but the same error occurs. I am at the end of my ideas. Anyone else run into this or have any suggestions?

USCanthony said:
I have both the stock rom and stock recovery installed but I cannot get the OTA update to complete without an error and if I try to manually run the update from the stock recovery I also get the same error. The error is...
Verifying current system...
"/system/app/Drive.apk" has unexpected contents.
Installation aborted
I have gone as far as removing the drive.apk from my device altogether but it still gives me the same error. I have tried installing a fresh copy of the drive.apk but the same error occurs. I am at the end of my ideas. Anyone else run into this or have any suggestions?
Click to expand...
Click to collapse
If you remove any system apps, the OTA will fail everytime. When you installed the apk, did you set it as a system app? Did you change the permissions back to how they should be?

charesa39 said:
If you remove any system apps, the OTA will fail everytime. When you installed the apk, did you set it as a system app? Did you change the permissions back to how they should be?
Click to expand...
Click to collapse
Ahhh...thank you....this is beginning to make a little more sense but also brings up another question. According to Titanium backup, the original Drive.apk was a system file but updates to that apk now reside in [root]/data/app/. I never installed drive.apk form the Play Store and then made it a system file so I have to assume that the original drive.apk that is sitting with all the other system files is part of the stock rom. There is a possibility that it could be a different version than what cam with the stock rom though since I did perform a merge of updated apk's from that location into the [root]/system/app/ folder several months ago but I have no idea if the drive.apk was one of those that I merged because I do not remember what apk's were merged. Does the OTA look for what it has been told is the version that existed in the "system/app" folder of the ROM it is updating and if it finds any other version it will fail (which means that merging any apk's is an OTA killer)? I had also deleted several Motorola apk's from the stock rom that are bloated system files such as "Alert" and "Assist" but I have Titanium backup's of those files so restoring them is not a problem. Is it possible that the drive.apk error is an erroneous error because drive.apk was simply the last file it checked before the script bailed because of those missing files?

USCanthony said:
Ahhh...thank you....this is beginning to make a little more sense but also brings up another question. According to Titanium backup, the original Drive.apk was a system file but updates to that apk now reside in [root]/data/app/. I never installed drive.apk form the Play Store and then made it a system file so I have to assume that the original drive.apk that is sitting with all the other system files is part of the stock rom. There is a possibility that it could be a different version than what cam with the stock rom though since I did perform a merge of updated apk's from that location into the [root]/system/app/ folder several months ago but I have no idea if the drive.apk was one of those that I merged because I do not remember what apk's were merged. Does the OTA look for what it has been told is the version that existed in the "system/app" folder of the ROM it is updating and if it finds any other version it will fail (which means that merging any apk's is an OTA killer)? I had also deleted several Motorola apk's from the stock rom that are bloated system files such as "Alert" and "Assist" but I have Titanium backup's of those files so restoring them is not a problem. Is it possible that the drive.apk error is an erroneous error because drive.apk was simply the last file it checked before the script bailed because of those missing files?
Click to expand...
Click to collapse
I don't think it checks the version of the app. I think it just checks whether the apk is there, and if the permissions are correct. This is why I never actually delete system apps. I'll just disable them in the stock settings app, or freeze them with TiBu. I assume that all the apps that came loaded on the phone (including the Motorola ones you mentioned) need to be present in order for it to update, or at least the apps that don't give you the option to uninstall them in the stock settings app, meaning they can only be disabled.

can someone pull out the boot.img from a 4.4.4 updated xt1045, and share with me? thanks.

Wifi won't toggle on after bootloader unlock, root, and new recovery

Hey guys, I just recieved my Moto G 2014 and the first thing after my initial boot (to make sure everything was working) I did was unlock the bootloader, flash twrp, and root.
I just booted it up for the first time after doing all that and my wifi won't turn on. Toggling it on causes the switch to immediately go back off.
Is it a radio problem? I didn't touch any files other than logo.bin, recovery, or boot.img.
Can anyone help? Thanks.
Edit: It seems that whatever guide I followed had me flash a boot.img that probably messed my phone up. How can I get the original boot.img for my phone? This is the guide I used, which I got from the xda portal. It seems a few other people had problems with wifi in that thread, but a solution was never posted.
Edit2: I downloaded a stock based rom for the moto g 2014 and flashed the boot.img from it, but now I can't get root, even after flashing the supersu zip in recovery. Can anyone help?

Maybe you have to go through unlocking procedure once again? Not because the bootloader is relocked but there could be some kind of setting that has changed after flashing boot.img.
Just thinking.

Wolfcity said:
Maybe you have to go through unlocking procedure once again? Not because the bootloader is relocked but there could be some kind of setting that has changed after flashing boot.img.
Just thinking.
Click to expand...
Click to collapse
Eh, I don't think so. The root process, in all reality, should just be unlock bootloader, flash recovery, flash supersu if I'm not mistaken. I've done all that and i still can't get root. At least my wifi works again though.

Flash complete stock rom and try again.
I unlocked bootloader, rooted by booting (instead of flashing) into TWRP 2.8.5.0 and flashed SuperSU 2.46 without any problems. There must have been something wrong with the first boot.img.
Sent from my XT1068 using XDA Free mobile app

Ciao.
I have the same problem with my Moto G 2014 LTE XT1039. I installed the twrp 3. No network, no wifi signal.
Inform me if you find a solution.
Thanks a lot
Nicola

My solution
quanic said:
Ciao.
I have the same problem with my Moto G 2014 LTE XT1039. I installed the twrp 3. No network, no wifi signal.
Inform me if you find a solution.
Thanks a lot
Nicola
Click to expand...
Click to collapse
I had the same problem but could solve it as follows:
Download the file WCNSS_qcom_wlan_factory_nv.rar
Extract the file "WCNSS_qcom_wlan_factory_nv.bin" to folder "/persist" (root required)
Restart system
Information taken from the post http://forum.xda-developers.com/moto-g-2014/general/fix-wifi-missing-file-t3007540

Hi, I had the same problem . If WIFI DONT TURN ON .then u might have not used the command fastboot flashing unlock_critical . Try using this command will work for sure. If it didn't work flash using miflashtool but don't select clear all instead select 2nd option only storage

Phone not booting after FlashFire flash.

Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.

Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.

irontaco1 said:
... so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Click to expand...
Click to collapse
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.

irontaco1 said:
Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.
Click to expand...
Click to collapse
Read this for information on how to bypass the password that your backup is asking for https://www.google.com/amp/s/www.ho...fter-restoring-from-twrp-android-backups/amp/

Strephon Alkhalikoi said:
Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.
Click to expand...
Click to collapse
Hey thanks for the help phone is running just fine now. I grabbed the factory image from the Google dev page and flashed it the hard way. For some reason ADB wouldn't mount /system after it was finished so I used fastboot to flash system, boot, radio, etc. Guess I won't use Flashfire for baseband anymore :laugh:

ktmom said:
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.
Click to expand...
Click to collapse
Phone is working fine now. The files were encrypted because the stock kernel I was using was obviously non-permissive so it automatically encrypted my files upon reboot before it bootlooped. Really appreciate the help though.

Can't access developer options

Hi,
I recently flashed the TWRP recovery on my Honor 5C which is running Android Nougat and EMUI 5.0. Since that, I was not able to enter recovery mode, some system applications disappeared on my phone and Bluetooth stopped working.
Today I flashed the original boot.img and recovery.img, extracted for the stock ROM. Now I can access recovery mode and I wiped the whole data from the recovery menu.
That didn't solve anything, my apps didn't reappeared. But now I have a new problem : currently my bootloader is unlocked so I want to relock it. For that I need to use ADB, which also needs USB debugging to be enabled. So I opened the settings app and clicked on the About section, then clicked several times on the build number.
But now, when I try the "Developer Options" menu, the settings application close and I can't access it! So I can't use ADB on the phone, which is a really big problem for me...
Can anyone help me ?
NOTE: My phone is a NEM-L51 french model ; Android Nougat + EMUI 5.0 (latest official update) ; no root.

Finally I solved that problem by succeeding in TWRP installation

ClementNerma said:
Finally I solved that problem by succeeding in TWRP installation
Click to expand...
Click to collapse
What have you done to solve your problem?

I downloaded the TWRP "Venus" recovery to my device. The first time I did it several weeks ago that didn't work but this time it worked perfectly fine
Then I attempted to flash the original stock ROM but I got an error with status code 7. I edited "update-script" file in the ZIP archive to remove the assert() command but then it gave me an unknown error with message "[]]", I didn't find anything about this error. So I downloaded instead the Elite ROM v2.0 for Honor 5C and installed it using TWRP Venus.
And now my phone works fine, without any bug. I have access to the system applications that disappeared on the previous ROM (the stock one), the Bluetooth works again, and I have root. So that's how I solved the problem ; if some other users have the same problem you can still try to flash this recovery it may solve your problem too !

ClementNerma said:
I downloaded the TWRP "Venus" recovery to my device. The first time I did it several weeks ago that didn't work but this time it worked perfectly fine
Then I attempted to flash the original stock ROM but I got an error with status code 7. I edited "update-script" file in the ZIP archive to remove the assert() command but then it gave me an unknown error with message "[]]", I didn't find anything about this error. So I downloaded instead the Elite ROM v2.0 for Honor 5C and installed it using TWRP Venus.
And now my phone works fine, without any bug. I have access to the system applications that disappeared on the previous ROM (the stock one), the Bluetooth works again, and I have root. So that's how I solved the problem ; if some other users have the same problem you can still try to flash this recovery it may solve your problem too !
Click to expand...
Click to collapse

Bluetooth Issues and cannot flash stock ROM

i recently unlocked bootloader and flashed lineagos 16 on the phone, after booting insantly and non stop a message saying 'Bluetooth Stopped Working' and then `Bluetooth keeps stopping`, I then tried the resurrection remix ROM and the blutooth stopped working sign didn't appeardes but Bluetooth didn't work anyways. After a bit I remembered seeing a Bluetooth partition on TWRP, and I tough that maybe something missing in there for the phone to recognize the bluetooth module, as the phone didn't showed the bluetooth adress either.
Then when I tryed to flash the stock rom back I realized I forgot to Backup, and going around on the internet I couldn't find anyone that work, or at least I couldn't flash it with the adb loader.
The Phone Model is the XT1929-6 and I don't know if it's useful but in the fastboot mde the baseband version is M636_29.59.01.96R BECKHAM_LATAM_CUST.
Everything else works without problem.

Try reflashing the Bluetooth firmware..
If all else failes then the Leveno LMSA will allow you to download & flash factory images
https://support.lenovo.com/us/en/downloads/ds101291
NOTE: it wipes userdata

Do i download the bluetooth firmware from the LMSA or where can I get it?
MadMan29729 said:
Try reflashing the Bluetooth firmware..
If all else failes then the Leveno LMSA will allow you to download & flash factory images
NOTE: it wipes userdata
Click to expand...
Click to collapse
..

Nevermind I used the LMSA and got everything working, Thanks!!
D15F16UR3 said:
..
Click to expand...
Click to collapse
........................................................