The new update today for the moto g is causing my phone to be in a boot loop. I really don't know why. It's rooted and I use twrp recovery to wipe the cache and it works again but if I try to install the update it will just cause the boot loop again. Please help I really need this update my internet is slow on my phone! Thanks.
The same thing happened here, with CWM recovery. The update probably expects stock recovery.
Same here
Sent from my XT1032 using xda app-developers app
Nevermind
Doesn't matter. I remember reading somewhere that you no longer get updates from motorola once you root your device. I'll wait for someone to release a flash for it. Thanks.
cillian334 said:
Doesn't matter. I remember reading somewhere that you no longer get updates from motorola once you root your device. I'll wait for someone to release a flash for it. Thanks.
Click to expand...
Click to collapse
Not true. I rooted, flashed custom recovery and all, and STILL received the update. The trick is how to get it into the phone without the bootloop.
Try the suggestions I put in this thread
http://forum.xda-developers.com/showthread.php?t=2663205
A little attention is all that is needed...
Just went to hell and back.
I just reflashed to stock and it turns out it was a bad rom and i couldn't fix it but i think it's ok now.
I have the Indian dual sim version, and my Moto G is having bootloop problem after a month of installing the OTA :\
Can anyone help me out? I have tried reflashing the stock firmware but of no use.
Just the motorola blue logo shows up and then black screen. The recovery also doesn't work
ahank said:
I have the Indian dual sim version, and my Moto G is having bootloop problem after a month of installing the OTA :\
Can anyone help me out? I have tried reflashing the stock firmware but of no use.
Just the motorola blue logo shows up and then black screen. The recovery also doesn't work
Click to expand...
Click to collapse
Did You found any solution?
I have same problem here...
jayrocky11 said:
Did You found any solution?
I have same problem here...
Click to expand...
Click to collapse
Wipe cache, it sabed MY bacon for sure. Use fastboot
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!!
Randomly today my brother's Moto G just turned off and refused to get past the bootscreen and upon turning it off it simply reboots to the bootscreen, at the time the firmware was 4.4.2 and i attempted to flash it back to stock 4.3 using this guide http://forum.xda-developers.com/showthread.php?t=2542219 , I got all the OKAYs, followed instructions completely and it still reboots to the bootloader after the 4.3 Stock load.
My question is, is there anything else I can do or is this phone done with?
I am currently in the process of reflashing with a 4.4.2 firmware, all for the xt1034 which is the phone model. Any help would be appreciated as none of the modes in the boot console [recovery,factory] etc do nothing but get stuck on the bootscreen.
And one last question, how long does the phone last on the bootscreen after a reflash? I waited 10mins but nothing changed.
EDIT: can someone change this thread to question, it seems i didnt click it properly >.>
2Ponies1Apple said:
Randomly today my brother's Moto G just turned off and refused to get past the bootscreen and upon turning it off it simply reboots to the bootscreen, at the time the firmware was 4.4.2 and i attempted to flash it back to stock 4.3 using this guide http://forum.xda-developers.com/showthread.php?t=2542219 , I got all the OKAYs, followed instructions completely and it still reboots to the bootloader after the 4.3 Stock load.
My question is, is there anything else I can do or is this phone done with?
I am currently in the process of reflashing with a 4.4.2 firmware, all for the xt1034 which is the phone model. Any help would be appreciated as none of the modes in the boot console [recovery,factory] etc do nothing but get stuck on the bootscreen.
And one last question, how long does the phone last on the bootscreen after a reflash? I waited 10mins but nothing changed.
EDIT: can someone change this thread to question, it seems i didnt click it properly >.>
Click to expand...
Click to collapse
Type: Fastboot -w
It will Delete user data but it will work normally
xxeldaddyjrxx said:
Type: Fastboot -w
It will Delete user data but it will work normally
Click to expand...
Click to collapse
Thanks, this worked but everything is ridiculously unstable at the moment, google services stopping all the time did i use a bad fw?
2Ponies1Apple said:
Thanks, this worked but everything is ridiculously unstable at the moment, google services stopping all the time did i use a bad fw?
Click to expand...
Click to collapse
do the Fastboot -w then re flash the android 4.3 and update to 4.4.2 and it should go back to normal
sorry for a late reply, been busy lately , im only 14 years old cx and got alot of school work and help my dad at work too.
Please pardon me for any faux pas as I am new here.
Mods please refer me to the appropriate thread and close this one, in case this one is a duplicate.
It seems my Moto G 1 Gen XT1033 is hardbricked. I had been running a CM 12 for falcon - nightly release since May 2015 and had had no problems so far. I had also upgraded my recovery to CWM Touch.
Two weeks ago, my phone got stuck in a boot loop (I now realise that that is called a softbrick), I managed to boot into recovery and updated my OS with the latest nightly release of CM 12 for my phone. I also tried to upgrade the recovery version with the same as that of the OS version but I don't think that it got upgraded. (I'm not sure what it said).
Anyway my phone was working fine for an hour or so until CM gave some errors on opening the themes configuration, so I thought rebooting my phone would solve the problem.
My phone never booted after that. It didn't even turn on or boot into the bootloader/recovery etc. I checked the battery etc. and it was fine. There was no issue with the hardware.
I then connected my phone to my laptop and it recognised it as qhsusb_bulk. I have spent a lot of time searching and trying various methods like:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076
Using the MotoTool All In One etc.
I cant seem to figure out the problem. I don't even know what my bootloader version was etc.
Is there a problem with my bootloader or recovery? I can't seem to understand.
Can someone please help me with this?
Thanks
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
motolollipop said:
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
Click to expand...
Click to collapse
Thanks man. But no help so far
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
CoolCrusader said:
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
Click to expand...
Click to collapse
That happened to me too, I think even the same image! It was a long time ago and I have now switched to a Oneplus One after using a Moto E which actually isn't that bad - I got it new super cheap. For me, Cyanogen restarted to update and after a LONG period of time stopped doing anything (I have upgraded before). I couldn't mount anything in CWM and I lost all data irrecoverably. The partition table got all messed up, and I had to flash a dual sim image as it was the only one that loaded - done through fastboot. I then flashed the original kitkat image and then massively messed up and updated, making my phone qhs_bulk.
Basically everyone who has had lollipop on their devices and have this are waiting for files to be leaked from Motorola so they can make their phones work. Not much is happening currently, you might as well get a new budget phone - some of the new ones are much better than the Moto G 1st gen! Or you could do what some people are doing which is ordering broken Moto Gs off eBay and replacing the board. Good luck!
---------- Post added at 01:49 AM ---------- Previous post was at 01:42 AM ----------
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
You may want to go the fastboot method to flash a stock lollipop image and CWM recovery - if you don't have a backup, you may want to try just flashing something like TWRP to see if you can get some files off your device, then completely flash over it.
Hi
I have my Moto G in 5.0.2.
Wednesday I receive a notification to update to 5.1, so I tried to do it.
The update downloads fine, but then when it comes to install it there's a problem.
The phone reboots and the android logo appears. Then it starts to install the update. However, after a while, a error occurs and the phone reboots again and starts up normally.
I don't know why I can't install 5.1.
I have bootloader unlocked and the phone is rooted.
May this be the problem?
Thanks
I have the same problem with my Boost Moto G XT 1031. Update downloads, reboots, update fails, reboots to 4.4.4. I have tried a factory reset, and changed to ART. Still update fails everytime. Does anyone know if there is a log on the phone?
Joaosacramento said:
I don't know why I can't install 5.1.
I have bootloader unlocked and the phone is rooted.
May this be the problem?
Click to expand...
Click to collapse
OTA updates contain only the differences to the official previous ROM, so yes, a modified /system partition may be the problem.
paulsaz said:
I have the same problem with my Boost Moto G XT 1031. Update downloads, reboots, update fails, reboots to 4.4.4. I have tried a factory reset, and changed to ART. Still update fails everytime. Does anyone know if there is a log on the phone?
Click to expand...
Click to collapse
I don't know much about the stock recovery, but look in /cache/recovery.
You have to be completely stock. Unrooting won't fix the problem. Flash stock firmware before upgrading. This is specific to lollipop updates because they refuse to install on modified system partition. That's why Unrooting wouldn't work.
Sent from my XT1032 using Tapatalk
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
BlackSkorpion said:
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
Click to expand...
Click to collapse
You don't give much detail as to what happened or what you were doing prior to your bootlooping. I suffered from a bootloop that took me several months to finally resolve on the very device I'm responding to you with. I was able to resolve it by installing the latest Oxygen OS from the OPO forums. I followed the directions exactly, then after booting into Oxygen it turned out that my WiFi and Bluetooth were refusing to turn on. After several attempts and force close reboots I was able to get them to function. Then I reinstalled TWRP, then flashed CMOS12, then finally CM which I'm using now. BTW for more detail look for my post about it in this forum. Hope this helps.
Odysseus1962 said:
You don't give much detail as to what happened or what you were doing prior to your bootlooping. I suffered from a bootloop that took me several months to finally resolve on the very device I'm responding to you with. I was able to resolve it by installing the latest Oxygen OS from the OPO forums. I followed the directions exactly, then after booting into Oxygen it turned out that my WiFi and Bluetooth were refusing to turn on. After several attempts and force close reboots I was able to get them to function. Then I reinstalled TWRP, then flashed CMOS12, then finally CM which I'm using now. BTW for more detail look for my post about it in this forum. Hope this helps.
Click to expand...
Click to collapse
Hi, i dont know what happened before because the Phone is not mine, is of the gf of a friend. I can reach fastboot and recovery and I also changed the recovery to twrp and installing a new rom, but bootloop still is running. What can i do else?
BlackSkorpion said:
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
Click to expand...
Click to collapse
Do you have a backup? try restoring just the system and the data of your backup.. i used to flash the boot too but as far as i know flashing boot doesn't solve the issue (still bootloop-ing). if you are still in bootloop and really have no idea, try consider a full reset of your phone (all except your custom recovery, ofc) and flash a new flashable.zip rom.. (data+media also wiped) you can always copy files to your phone while in recovery by mounting a usb drive, in case you don't have a zip on your phone. of course, this is not the solution, and is not recommended, but take this as your last choice if any other method didn't work
hope it helps!
Kevin1705 said:
Do you have a backup? try restoring just the system and the data of your backup.. i used to flash the boot too but as far as i know flashing boot doesn't solve the issue (still bootloop-ing). if you are still in bootloop and really have no idea, try consider a full reset of your phone (all except your custom recovery, ofc) and flash a new flashable.zip rom.. (data+media also wiped) you can always copy files to your phone while in recovery by mounting a usb drive, in case you don't have a zip on your phone. of course, this is not the solution, and is not recommended, but take this as your last choice if any other method didn't work
hope it helps!
Click to expand...
Click to collapse
I dont have a backup, so i also tried yet everything you said. I dont have to save datas, so i flashed everything new, but still dont work. I also tried to flash everything from oneplusrecoverytool that in any difficult situations helped me, but in this case it did not worked. Is there any radical solution to get this Phone working? (i can install twrp and reach fastboot, but after installing something, it's always in bootloop. ?
i have the same problem , don't know what to do , i even used the tool to return to stock
maybe an overheat problem? i don't know
Gentlemen, please try the method I suggested above in my response. Go to the OPO forums and follow the procedure to switch to Oxygen OS exactly as they lay out. As long as you're unlocked and can get to the bootloader and recovery you aren't hard-bricked and will be able to eventually fix your handsets. I know from personal experience, because as I mentioned this device was hopelessly stuck in a bootloop for months before I was able to get it running again. Do a search for my previous post for instruction and as I said follow the guide to installing Oxygen to the letter. More than likely you've got several corrupt partitions and this method will resolve it. Once you've got your handset successfully running again on Oxygen you can then begin to flash other ROMs with no issues. For some reason the Oxygen OS is more robust in that it will boot up when there are issues with these corrupted partitions when CM based ROMs won't. I believe the title of my previous post was "hopelessly stuck in bootloop (solved)". I hope this helps.
Odysseus1962 said:
Gentlemen, please try the method I suggested above in my response. Go to the OPO forums and follow the procedure to switch to Oxygen OS exactly as they lay out. As long as you're unlocked and can get to the bootloader and recovery you aren't hard-bricked and will be able to eventually fix your handsets. I know from personal experience, because as I mentioned this device was hopelessly stuck in a bootloop for months before I was able to get it running again. Do a search for my previous post for instruction and as I said follow the guide to installing Oxygen to the letter. More than likely you've got several corrupt partitions and this method will resolve it. Once you've got your handset successfully running again on Oxygen you can then begin to flash other ROMs with no issues. For some reason the Oxygen OS is more robust in that it will boot up when there are issues with these corrupted partitions when CM based ROMs won't. I believe the title of my previous post was "hopelessly stuck in bootloop (solved)". I hope this helps.
Click to expand...
Click to collapse
i tried your solution but nothing changed i also tried this procedure http://forum.xda-developers.com/one...lusrecovery-tool-v1-0-restore-t2991851/page23 , the process is success but at the reboot the phone is always in bootloop
still same problem here =/
Download the latest fastboot image from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 follow step #8