So I recently got a boost moto g, specifically for the purpose of unlocking it and installing custom roms, First I had CM11, ran great but I needed more, then I flashed SlimKat, that was even better after I flashed pink kernel in but, I derped it some how and went back to stock 4.4.2, now when ever I flash a new ROM, it has this dumb activation that dials *22899 and then tells me "we're sorry, we could not complete your activation at this time, please try again later" then kicks me to the beginning and I all get is the option to try and activate again, it even does it on CM11 now. what did do? I followed all instructions to the tee on the rom websites. I just downgraded to stock 4.3, then manually updated to 4.4.2 and now its giving me a "cellular activation bug" update, hopefully this fixes my problem. I'll post again if it does not, Thanks for any insight.
-Naylo
EDIT: The "Cellular activation bug fix" you can receive via manual updates on the stock 4.4.2 rom fixed my issue, If you find your self with this issue, fear not! just flash lowest stock android for you phone and let it update by checking for them via the system update in the system settings. ^.^ (i feel this will be useful to anyone who instantly unlocks the BL and flashes a custom rom before even starting stock like I did)
edit edit: I only worked for one installation, when I tried switching again, it broke it again and got caught in activation again.
Related
Hi, today I got the notification on my G (India-Dual Sim version) that the 4.4.4 was available to download.
I tried to go back to stock recovery to do the upgrade but for some reason it didn´t work, I was able to flash but the stock recovery never came up. In the end I decided to give a shot and see what happened.
I have the CWM recovery, and it notified me that the file used for the update had not a correct signature, decided to continue, no problems so far. In the end it notified me that maybe root may have some issues (the same warning when you root the phone the first time), told it to fix it and it rebooted.
All smooth and so far no problems, but it did show a warning on the main screen (after being all loaded) that something went wrong, but the phone booted OK and the system version is 4.4.4, maybe something to do with the stock recovery or something, don´t know, but so far, is you have CWM, I believe you can do the OTA update withouth problem.
Will let you know if something comes up.
Phone: Motorola Moto G XT1032
OS: Android 4.4.4
Let me start by saying that I am new here, and I am not sure if this is the correct place to ask for help, but here I go anyway...
I am in desperate need of assistance. Against all better judgment, I rooted my phone a few months ago and now I am in a "pickle" so to speak. I recently recieved the Android 5.0.2 OTA Update notification. I have attempted multiple times to install this update but each and every time I do so, it returns me (after rebooting) a message along the lines of "software update was unsuccessful". I have sifted through some posts online with no avail. I am not the best person when it comes to my phone, however I do know how to get around on a computer.
I guess I should also add that I read somewhere that the phone must be un-rooted before attempting to upgrade, however, I have alrady attempted to do so with the "Full Unroot" option in SuperSu, but the only thing that seemed to have happened is the app is now deleted.
Another thing, I only rooted my phone and did not install any of the recovery programs like CWM or TWRP. This is stock android and no Custom ROM.
Any help would be greatly appreciated, as I have been waiting for Andoid L for a very long time and am very upset that I am having all these issues trying to use it.
Thank you for listening and look forward to seeing if anyone can help me.
DubstepCanada.
What you may try to want to do is to find the factory stock image online for which ever version you have and run it then upgrade to each new version till you get to lollipop update. Yes you will lose all of your data but if lollipop is what you want that is probably what your gonna have to do. Every time a factory update is available on Motorola before it does the update it will check for every app and checks file system and recovery. Anything out of the ordinary and it will usually not upgrade it. So if I was you look for the stock factory image of 4.4.4 and update to lollipop 5.0.2.
Alternatively flash a custom recovery, TWRP or Philz Touch, and then do a factory reset and flash one of the zips in this collection:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Less risk and you keep your photos etc.
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.
Ok guys,
I'm gonna post this knowing that there is probably NO SOLUTION to my issue. Let me attempt to explain EXACTLY my issue and what I did. I found a potential solution here > http://forum.xda-developers.com/showthread.php?t=2582142 however my issues don't exactly match the description in that thread.
So, long story short - I've ended up back on the G2 for now (until I upgrade) - I got the G2 on Amazon brand new. When I got it the other day - I discovered when I attempted to boot into download/fastboot or recovery using ADB - the phone would just reboot. The G2 came with KK 4.4.2. I had it rooted but still couldn't get into recovery or download modes. So, for the hell of it - I decided to take the OTA (after reading the G2 can still be rooted on LP). Halfway thru the OTA update (after it reboots into stock recovery) the device reboots. Did it multiple times. So, I went to LG's website and downloaded the LG Mobile Support tool. Plugged the G2 in - it said there was no update available. So, I tried one of the options I found to update the recovery. So, it starts updating.... and then I realized it flashed Lollipop instead of updating the recovery. So, no I'm on stock Lollipop 5.0.2 and I still can't boot into recovery/download/fastboot to flash a stock KitKat image so I can root, ROM, etc.
Anyone heard of this issue or even possibly know how to fix it WITHOUT using a bootable Linux drive or a virtual machine (I have a Windows 8,1 laptop - 8.1 doesn't support Hyper-V out of the box)? If you know anything related to this - please post. I have no clue what else to do except accept the fact that I have a stock G2 that I will NEVER be able to root. I was going to send it back to Amazon and get another one but I don't feel like going thru all that for a phone I'm probably not gonna end up using too much longer.
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.