On the retail US XT1045 (Peregrine), I saw that the OTA to upgrade from 4.4.4 to 5.1 was available. I used a stock firmware to flash the stock recovery and system, then updated the Motorola Update Services app to download the OTA. After applying the OTA, I made a nandroid in TWRP. While I was playing around, I noted that heads up notifications were working for all notifications; new emails, downloads finishing in Google Play, and SMS.
I did a factory reset soon after, and since then the heads up notifications have not worked. I have tried factory resets in stock 5.1, I have tried factory resets in stock recovery, I have tried restoring the nandroid I made of 5.1, I have tried restoring my 4.4.4 KitKat nandroids and reapplying the OTA from there, I have tried a complete wipe of /system and /data and flashing stock 4.4.4 firmware with mfastboot, then applying the OTA update in stock recovery, but none of this has worked. Heads up will appear for phone calls and text messages, but nothing else.
Incidentally, I have had this issue in several CyanogenMod 12.1-based ROMs such as official CM 12.1, beeto's SaberMod ROM, the AOSP ROM by Kayant, and Paranoid Android ROMs. I've found that BlissPop, AICP, and crDroid ROMs have heads up working. What could be causing this, and is there a way to get heads up back?
Related
Okay, I'll start with the problem. After a few days I flashed the Moto G GPE Firmware using MotoTool, from the xda forums. Everything was great, but I downloaded a ROM (Paranoid Android), made a Backup, and flashed it as usual. When the phone booted, an encryption unsuccessful message popped up. I rebooted into recovery and restored my last backup. I saw in xda that the problem was probably generated by using the GPE version, so today I downloaded my stock firmware, flashed it, but the phone got stuck on the logo. Tried the same with another firmwares, and still got the same problem. I rebooted into the Bootloader, flashed TWRP, flashed the PhilZ GPE recovery, sideloaded PA again, got the same problem. Flashed CarbonROM (after doing every wipe and stuff), and got the same message. Tried CM11, didn't worked. But the problem is...
How can I correctly flash my original firmware if it's not working? I need to go back to the "normal" Moto G, so I can flash ROMs and stuff.
Bump
Please, close thread
Finally fixed it flashing the 4.4 US Retail. I was trying to flash the 4.3 US Retail, from the GPE Firmware, and it wouldn't work because the gpt.bin command always failed.
Please, close thread.
Help guys.. I recieved the 4.4.4 update lately (currently on 4.4.3)
I was waiting for L update but recived this.. But the problem here
Is that this 21mb update wont install. I get this error and sometimes
I am stuck on bootloop.
I have stock rom, twrp recovery,
Ive tried to install with stock recovery no luck..
Right now its good im afraid what will happen with L update.. Help plz
There is other phone in your place has same problem?
Hi..!
AArga said:
There is other phone in your place has same problem?
Hi..!
Click to expand...
Click to collapse
People i know haven't even unlocked their bootloader
But can't update?
me too, have the same problem.
I'll just flash the 4.4.4 EU image for my XT1032...
and I'll do the same thing for when lollipop comes around
Its look like you must reset factory then direct updating your firmware..
have you unroot and relocked your bootloader?
Try restoring to stock: Flash 4.4.3, go to stock recovery and try to make the update search, if this is not working do a clean flash (wipe cache+userdata) and try to update, some time ago i noticed that cannot update the firmware of my 4.4.2 because the cmw recovery, then wiped cache and intalled stock recovery and everything went fine
To receive OTA updates device should be only on stock recovery no cmw, no twrp. Try to install stock recovery with fresh stock rom, and remember to enable any disabled system apps (if any) like Motorola services, Motorola OTA, then only you will able to receive and install updates....
You need the stock recovery
Hello forum, basically, when I got my moto G, it was on 4.3, so I did all the bits, and the step i did after all the rooting unlocking etc was upgraded my bootloader to the lollipop one (ending in 8 i believe) - which i wish i didnt do, and cant downgrade to 4.4.4 (or can I without bricking)......right back to the story.......the problem now is, whenever i try uninstalling apps, or wiping data in any app etc, my phone does a reboot, I installed the brazillian 5.0.2 flashable rom (the optimised one) which worked perfectly, did all the correct wipes etc, but it reboots when uninstalling apps......, and thought i would try dirty unicorns....works well except the rebooting problem...... help....what can I do????????
I read somewhere that maybe to solve it, you gotta change runtime from dalvik to ART, but there is no option to change this....
There are no 5.0.2 uk images available that i have read (so i cant completely get back to complete factory settings)
I really wished i kept the KK bootloader!!!! so who can help me????? I want to try some of the great CM11 builds!!!
Since your bootloader is unlocked and you have the lollipop bootloader, I suggest flashing the stock 4.4.4 (not 4.4.2) ROM for your xt1032 (you will not be able to flash the motoboot file so don't bother trying), upgrade the Motorola apps via Play store, and take the 5.02 OTA update.
FInd your stock ROM here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
audit13 said:
Since your bootloader is unlocked and you have the lollipop bootloader, I suggest flashing the stock 4.4.4 (not 4.4.2) ROM for your xt1032 (you will not be able to flash the motoboot file so don't bother trying), upgrade the Motorola apps via Play store, and take the 5.02 OTA update.
FInd your stock ROM here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
Click to expand...
Click to collapse
do i have to update to 5.0.2 again? as i want to try cm11 again
@audit13 is this a flashable zip, or do you need to do it via fastboot? as its got a bootloader included in the zip (4.4.4 kitkat bootloader)
The files from filefactory need to be unzipped and flashed via fastboot or mfastboot.
You do not need to do anything with the stock ROM if you want to install a custom ROM. All you need to do is install a compatible custom recovery and a custom ROM. I suggest flashing right to the latest CM12 rather than using CM11.
I suggested flashing back to the stock for your phone and upgrading to 5.02 via OTA to see if the uninstall problem goes away.
yep understood @audit13 read your other posts on this matter too, the reason I want to use a cm11 rom, is I had a moto g about 8-9 months ago, and there was a rom i loved, and it was cm11 based......will i brick if i do flash this cm11 rom? i know about flickering bug, and possible hard brick if i went back to versions below 4.4.4 ...... and i love cyanogenmod roms, as i dont get irritating moto updates etc
Flashing CM11 should not be a problem as CM11 ROMs do not touch the bootloader or modem.
so basically, downgrade to the 4.4.4 firmware file, and cm11 and im done? yeah?
You can try to flash cm11 directly over stock 5.02. If it doesn't work, you may have to flash back to stock 4.4.4, install recovery, and then flash cm11.
I have a Nexus 5 with Dirty Unicorns 4.4.4 and TWRP installed. I want to update to Dirty Unicorns 5.0.2.
I've heard that radio flashes or something need to be done and i've never done that so i'm assuming I can't just backup/wipe/installDU5.0.2.
What would be the best way to go about this? Do I need to flash some extra stuff along the way or do I need to return to stock, OTA update to 5.0.1 and then TWRP/wipe/flashDU5.0.2?
Ok, looks like DU moved to 5.1, same scenario though.
- returning to factory images to take an OTA is pointless (you could just flash the new factory images)
- returning to factory images to take an OTA to then flash a custom ROM is pointless (you could just flash the custom ROM)
Just your desired custom ROM and flash it in recovery. Best to wipe data.
Radio versions are optional. You can use any radio version with any version of Android (at least on the Nexus 5). They are in .img form and flashed using fastboot while booted into the bootloader.
I had a lot of issues with lollipop 5.1.1 in my nexus. All Google apps connected to internet only via WiFi and it wouldn't connect through the mobile data connection.
And then there was the battery life problem. So I switched to PA 4.6 beta based on kitkat. I would now like to try Marshmallow.
My question is, will downloading the factory image and flashing it through clockwork mod work? Or should I revert back to 5.1.1 nandroid backup I made earlier and wait for OTA? I can see some post about a feature called verity and the complications it brings to rooted users in 6.0. Does this affect the process of flashing a stock factory image on a rooted phone?
Karthick_M said:
I had a lot of issues with lollipop 5.1.1 in my nexus. All Google apps connected to internet only via WiFi and it wouldn't connect through the mobile data connection.
And then there was the battery life problem. So I switched to PA 4.6 beta based on kitkat. I would now like to try Marshmallow.
My question is, will downloading the factory image and flashing it through clockwork mod work? Or should I revert back to 5.1.1 nandroid backup I made earlier and wait for OTA? I can see some post about a feature called verity and the complications it brings to rooted users in 6.0. Does this affect the process of flashing a stock factory image on a rooted phone?
Click to expand...
Click to collapse
You can safely flash the Marshmallow factory images. Verity is a security feature which makes root more complex and you can still have root:
1. modded stock kernel provided by Chainfire then flash SuperSU v2.50+
2. flash a custom kernel like HellsCore, Blu_spark, ElementalX then flash SuperSU v2.50+