Related
So i tried flashing the lollipop software to my moto g xt1032 (i am a noob at this) and i think i messed up my phone. It now wont go past the bootloader/fastboot screen. Before updating i was running android 4.4.2. When i initially boot up my phone it says version downgraded for boot, failed to validate boot image, fastboot reason: fall through from normal boot cycle i have tried to follow the many guides their are out there that work/i am too dumb to understand them. If anyone can please help me. If i did not give enough info please ask and i will try my best to give it to you.
austin66887 said:
So i tried flashing the lollipop software to my moto g xt1032 (i am a noob at this) and i think i messed up my phone. It now wont go past the bootloader/fastboot screen. Before updating i was running android 4.4.2. When i initially boot up my phone it says version downgraded for boot, failed to validate boot image, fastboot reason: fall through from normal boot cycle i have tried to follow the many guides their are out there that work/i am too dumb to understand them. If anyone can please help me. If i did not give enough info please ask and i will try my best to give it to you.
Click to expand...
Click to collapse
You need to flash android 5.0 factory image for boot, and system. Follow the regular fastboot procedures to flash the 5.0 firmware. Makr sure you don't downgrade back to kitkat once you flash lolipop or else YOU WILL END UP IN A HARDBRICK!!!!!
skyguy126 said:
You need to flash android 5.0 factory image for boot, and system. Follow the regular fastboot procedures to flash the 5.0 firmware. Makr sure you don't downgrade back to kitkat once you flash lolipop or else YOU WILL END UP IN A HARDBRICK!!!!!
Click to expand...
Click to collapse
as i said i am a noob i am not really sure how to do that
skyguy126 said:
You need to flash android 5.0 factory image for boot, and system. Follow the regular fastboot procedures to flash the 5.0 firmware. Makr sure you don't downgrade back to kitkat once you flash lolipop or else YOU WILL END UP IN A HARDBRICK!!!!!
Click to expand...
Click to collapse
i have been trying to flash 5 and when i go in to recovery and load the file through adb it goes for like 5 minutes then says installation aborted
austin66887 said:
i have been trying to flash 5 and when i go in to recovery and load the file through adb it goes for like 5 minutes then says installation aborted
Click to expand...
Click to collapse
You need to flash using fastboot not adb. Look around the forum there are some great tutorials for a beginner.
skyguy126 said:
You need to flash using fastboot not adb. Look around the forum there are some great tutorials for a beginner.
Click to expand...
Click to collapse
So I tried to flashing using fastboot and my device still wont load up
Were you trying to install GPE 5.0.1? Or the soak test for X1033?
austin66887 said:
So I tried to flashing using fastboot and my device still wont load up
Click to expand...
Click to collapse
You need to flash all the partitions.
motorola actually agreed send me a new one despite what i did so all is good
Hello everybody i have a moto g XT1032 16 gb, bought on amazon. after unlocking bootloader and rooting my device, i used a guide on youtube (Convert Moto G (XT1032) to a Google Play Edition) to try the gp edition .... i updated to kitkat 4.4.4 and after that i received the update to lollipop 5.0.1, i updated it but now my device is stuck on bootloop
please someone help me!!
Can you give us more details?
Like if this is really a bootloop (in wich you would see that white image with an exclamation mark for a loooong time) or if you just can't switch your phone on?
I've read about it and, in a situation like yours, the phone usually bricks...
______________________________________
Edit:
When it happened to me, I did the following:
Download and execute the .bat of this topic after installing the phone drivers.
http://forum.xda-developers.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729
After this, my phone went to the GPE but it could not flash an stock rom. Than, I did this:
forum.xda-developers.com/ moto-g/general/guide-moto-g-xt1033-android-5-0-lollipop-t2979623
Follow this steps exactly the way its written and it should work.
BobDiaz said:
Can you give us more details?
Like if this is really a bootloop (in wich you would see that white image with an exclamation mark for a loooong time) or if you just can't switch your phone on?
I've read about it and, in a situation like yours, the phone usually bricks...
______________________________________
Edit:
When it happened to me, I did the following:
Download and execute the .bat of this topic after installing the phone drivers.
forum. xda-developers. com/ moto-g/general/ guide-xt1033-downgrade-lollipop-5-0-to-t2969729
After this, my phone went to the GPE but it could not flash an stock rom. Than, I did this:
forum. xda-developers. com/ moto-g/general/guide-moto-g-xt1033-android-5-0-lollipop-t2979623
Follow this steps exactly the way its written and it should work.
Click to expand...
Click to collapse
Thanks for your reply, basically is stuck on the boot with the google logo and a lock unlocked that i think it's for the unlocked bootloader..And when I power off the device by pressing for a long time the power button, after 2/3 seconds it reboot automatically....
now i'll try with the guides you gave me! I hope it will works
------------------------------------------------------------------------------
Edit: I did execute the .bat file and it did work! Thank you so much! now,i can't understand the second link you gave me... do i have to do that process' or it's fine like this? and now if I download the lollipop update, am i supposed to have the same problem?
stechiocca said:
Edit: I did execute the .bat file and it did work! Thank you so much! now,i can't understand the second link you gave me... do i have to do that process' or it's fine like this? and now if I download the lollipop update, am i supposed to have the same problem?
Click to expand...
Click to collapse
When you say "it work", did you mean that you can boot normally or that you can flash any rom that you wish? Or you didn't try that? The second link helped me because I couldn't flash any rom except GPE's (the partition table of these are different). If you wish to revert to your stock rom, you'll need to do as the second tutorial said.
I am now with an 5.0.1 Lollipop running well.
Please, give-me a feedback of your situation.
:good:
BobDiaz said:
When you say "it work", did you mean that you can boot normally or that you can flash any rom that you wish? Or you didn't try that? The second link helped me because I couldn't flash any rom except GPE's (the partition table of these are different). If you wish to revert to your stock rom, you'll need to do as the second tutorial said.
I am now with an 5.0.1 Lollipop running well.
Please, give-me a feedback of your situation.
:good:
Click to expand...
Click to collapse
So, first of all, now I can only boot normally and use it as gpe 4.4.4... This morning I received the lollipo 5.0.1 update, I did it but when it was at half of the installation, it stopped and there was the little android with an "ERROR" message.. if you want I can attach a photo with the error, so you may know how to solve (I did it when I had the stock recovery)... Now I tried to flash a ROM, so I put the CWM and rebooted into recovery, but when I tried ti install zip from SD card it said me "error: can't mount /sdcard" (I had this problem already when I used the guide to convert into gpe) So now what I have to do? I would like to try Lollipop, and I would like also to be able to flash any rom whenever I want!
--------------------------------
Edit: I just attached a photo of the problem so may be you can understand what happens!
stechiocca said:
So, first of all, now I can only boot normally and use it as gpe 4.4.4... This morning I received the lollipo 5.0.1 update, I did it but when it was at half of the installation, it stopped and there was the little android with an "ERROR" message.. if you want I can attach a photo with the error, so you may know how to solve (I did it when I had the stock recovery)... Now I tried to flash a ROM, so I put the CWM and rebooted into recovery, but when I tried ti install zip from SD card it said me "error: can't mount /sdcard" (I had this problem already when I used the guide to convert into gpe) So now what I have to do? I would like to try Lollipop, and I would like also to be able to flash any rom whenever I want!
--------------------------------
Edit: I just attached a photo of the problem so may be you can understand what happens!
Click to expand...
Click to collapse
So, like I said above... Just follow the second link.
The first one give you a temporary solution. It main objective is restore the capacity of mounting the partitions and booting into /system.
The second one open your horizons again, letting you decide which rom you will install. Just follow this and you'll can feel the sweetness of the Lollipop!
DO NOT try to install ANY actualizations over the TEMPORARY GPE edition. If you want do go back to GPE, do the second tutorial before.
Gimme your feedback and click ThankYou if it was usefull!
Nice wood bench, by the way.
:good:
BobDiaz said:
So, like I said above... Just follow the second link.
The first one give you a temporary solution. It main objective is restore the capacity of mounting the partitions and booting into /system.
The second one open your horizons again, letting you decide which rom you will install. Just follow this and you'll can feel the sweetness of the Lollipop!
DO NOT try to install ANY actualizations over the TEMPORARY GPE edition. If you want do go back to GPE, do the second tutorial before.
Gimme your feedback and click ThankYou if it was usefull!
Nice wood bench, by the way.
:good:
Click to expand...
Click to collapse
Ok i'm downloading the necessary files ... just two last questions before I do this, cause i'll wait for your answer before starting doing everything... 1) Will I lose all userdata? obviously I'm going to backup my data but ... am I going to lose my file and data?
2) will it work even if my original software was Retail DE?
and finally, thank you for the help, I'm going to click thank you even if it doesn't work (hope not obviously ), cause you were very helpful
I've got the same problem after trying to convert my Moto G to Google Play Edition (worked fine up to 4.4.4), then I wanted to install Android 5.0.1 OTA and ended in the Reboot Loop.
I followed the first link and was able to get 4.4.4 working again. Then I tried to continue with the second link to get the chance to update later on 5.0.1, but everytime I wanted to run the command "mfastboot flash system system.img_sparsechunk.0" my Moto G in Fastboot alerts "File Size too large". Is there a way to get an 4.4.4 which enables me OTA Update to 5.0.1?
stechiocca said:
Ok i'm downloading the necessary files ... just two last questions before I do this, cause i'll wait for your answer before starting doing everything... 1) Will I lose all userdata? obviously I'm going to backup my data but ... am I going to lose my file and data?
2) will it work even if my original software was Retail DE?
and finally, thank you for the help, I'm going to click thank you even if it doesn't work (hope not obviously ), cause you were very helpful
Click to expand...
Click to collapse
Wel... The answers:
1) Yes. You'll loose all your user data. One of the steps during the installation of any room is erase all the cache partitions and the userdata. That way, you can prevent any compatibility issues.
2) You phone will "forget everything about it's past", and will "think" that it is Brazilian now. If you don't like it, try downloading an ADB compatible DE rom. But, in my opinion, the Lollipop is way better than the Kit Kat. Unless you need the Xposed Modules.
Cheers!
Merry Christmas! :laugh:
---------- Post added at 01:30 AM ---------- Previous post was at 01:19 AM ----------
redbull93 said:
I've got the same problem after trying to convert my Moto G to Google Play Edition (worked fine up to 4.4.4), then I wanted to install Android 5.0.1 OTA and ended in the Reboot Loop.
I followed the first link and was able to get 4.4.4 working again. Then I tried to continue with the second link to get the chance to update later on 5.0.1, but everytime I wanted to run the command "mfastboot flash system system.img_sparsechunk.0" my Moto G in Fastboot alerts "File Size too large". Is there a way to get an 4.4.4 which enables me OTA Update to 5.0.1?
Click to expand...
Click to collapse
Did you did everything like said in the tutorial? Well, if yes, I suggest trying to do as the first link before. That way, all the partition table will be in the correct place.
Give us a feedback!
Cheers!
@BobDiaz do you think i should also erase dalvik cache? because i do everything step by step but it does remain in bootloop with the google logo ....
Let me just understand:
Did you try the first tutorial again or you are in the second for the first time?
You ALWAYS need to erase your cache partitions. Doing a clean installation always prevent bugs and incompatibility issues.
I'll ask for photos again. Show me, if possible, the step-by-step; Or upload a video on youtube.
Cheers!
BobDiaz said:
Did you did everything like said in the tutorial? Well, if yes, I suggest trying to do as the first link before. That way, all the partition table will be in the correct place.
Give us a feedback!
Cheers!
Click to expand...
Click to collapse
Thanks for your answer! I tried to do everything as described, the first tutorial worked fine. Then I wanted to flash the Brazilian kitkat image image with fastboot like described in the second tutorial. While flashing the phone dropped the error notice "Image File Size too Large" while flashing system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2. I was able to finish the further steps but after rebooting the bootloader the Moto G was back in Boot Loop.
Can I do the second part of this tutorial (transfering moto g brazilian update to the phone and apply the update from sd card) also with the image of the first tutorial? How does this work?
redbull93 said:
Thanks for your answer! I tried to do everything as described, the first tutorial worked fine. Then I wanted to flash the Brazilian kitkat image image with fastboot like described in the second tutorial. While flashing the phone dropped the error notice "Image File Size too Large" while flashing system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2. I was able to finish the further steps but after rebooting the bootloader the Moto G was back in Boot Loop.
Can I do the second part of this tutorial (transfering moto g brazilian update to the phone and apply the update from sd card) also with the image of the first tutorial? How does this work?
Click to expand...
Click to collapse
Actually, you can't.
You can only apply UPDATES to the rom it was meant to be. You cannot apply an Lollipop Update made to an 4.4.4 Retail-BR to an GPE, even if it was an 4.4.4. It will bug the partition table, leading your device to bootloop.
If you've already tried to do as the second tutorial said more than one time, following all the steps, and it still is in bootloop, i recommend you to try searching for a alternative.
Give us the feedback anyway!
Cheers!
Here are some pictures of the error that occurs during flashing Kitkat 4.4.4 like it is described in the second tutorial.
Before, I launched the first tutorial and got a running 4.4.4 on my Moto G.
Image 1: State after entering "mfastboot flash system system.img_sparsechunk.0"
Image 2: Feedback on the Windows console after entering "mfastboot flash system system.img_sparsechunk.0"
Image 3: State after entering the last "flash system .. " command
redbull93 said:
Here are some pictures of the error that occurs during flashing Kitkat 4.4.4 like it is described in the second tutorial.
Before, I launched the first tutorial and got a running 4.4.4 on my Moto G.
Image 1: State after entering "mfastboot flash system system.img_sparsechunk.0"
Image 2: Feedback on the Windows console after entering "mfastboot flash system system.img_sparsechunk.0"
Image 3: State after entering the last "flash system .. " command
Click to expand...
Click to collapse
You may need to flash gpt.bin from 4.4.4 (it is in the 4.4.4 flashable). This will create a new correctly sized partition table.
Also, make sure you are using the mfastboot to flash (a.k.a motorola fastboot) and not the Google fastboot.
This is probably a partition table error.
Give us the feedback!
=]
________________________________________
I've seen this in other topic:
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884
BobDiaz said:
You may need to flash gpt.bin from 4.4.4 (it is in the 4.4.4 flashable). This will create a new correctly sized partition table.
Also, make sure you are using the mfastboot to flash (a.k.a motorola fastboot) and not the Google fastboot.
This is probably a partition table error.
Give us the feedback!
=]
________________________________________
I've seen this in other topic:
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884
Click to expand...
Click to collapse
I can't find the gpt.bin file, probably this is why i'm getting "image is too large" error... can you please explain to where i can find it??
stechiocca said:
I can't find the gpt.bin file, probably this is why i'm getting "image is too large" error... can you please explain to where i can find it??
Click to expand...
Click to collapse
I could not upload here in XDA the gpt.bin that I've used.
Try catching the one that comes with any ADB flashable rom (it is called "gpt.bin").
Try the stock from your country.
BobDiaz said:
I could not upload here in XDA the gpt.bin that I've used.
Try catching the one that comes with any ADB flashable rom (it is called "gpt.bin").
Try the stock from your country.
Click to expand...
Click to collapse
hey, how are you? i'm really happy because it finally worked! I just had to "mfastboot flash partition gpt.bin" to make it works and i didn't get the "image is too large" problem... now i'll do the second part of the second guide hope it will work!! thank you a lot @BobDiaz
Excellent.
Try the other tutorial and tell me how did it go.
@BobDiaz Now i'm currently running correctly lollipop 5.0 brazil en BR, am i able to install a custom recovery and flash any rom whenever i want?
Me being an impatient person, I updated my moto g XT1032, to 5.0.1 GPE firmware, before it came out for official Motorola rom. Since the UI was a bit too laggy, I switched to Cyanogenmod 12 (Yes, it was much smoother). But I started noticing a moving line with a flickering screen (I noticed this on TWRP recovery while I was on GPE firmware, but it didn't bother me). The flickering line is on the boot animation of CM, and it stays there when it turns on, unless I turn off the screen, then turn it on again. This goes for recovery mode as well. This starting to really bother me, so I hope there is a fix for this. One thing I noticed on Fastboot Flash Mode is the following: AP Fastboot Flash Mode (S)
41.18 (sha-99084d5, 2014-10-29 23:54:18)
Noticed the version? It was 2014-10-29, that's a very recent version. I think the bootloader got updated, I didn't think that was possible. Maybe this is causing the flickering's and the line? I saw other articles about this problem, but all of them only talked about recovery mode, and didn't give much detail. I hope someone finds a fix for this. Thanks for reading!
Same problem!
I am facing the same problem too. any solution?
MetalPhoenix45 said:
Me being an impatient person, I updated my moto g XT1032, to 5.0.1 GPE firmware, before it came out for official Motorola rom. Since the UI was a bit too laggy, I switched to Cyanogenmod 12 (Yes, it was much smoother). But I started noticing a moving line with a flickering screen (I noticed this on TWRP recovery while I was on GPE firmware, but it didn't bother me). The flickering line is on the boot animation of CM, and it stays there when it turns on, unless I turn off the screen, then turn it on again. This goes for recovery mode as well. This starting to really bother me, so I hope there is a fix for this. One thing I noticed on Fastboot Flash Mode is the following: AP Fastboot Flash Mode (S)
41.18 (sha-99084d5, 2014-10-29 23:54:18)
Noticed the version? It was 2014-10-29, that's a very recent version. I think the bootloader got updated, I didn't think that was possible. Maybe this is causing the flickering's and the line? I saw other articles about this problem, but all of them only talked about recovery mode, and didn't give much detail. I hope someone finds a fix for this. Thanks for reading!
Click to expand...
Click to collapse
dhyaneswaran.s said:
I am facing the same problem too. any solution?
Click to expand...
Click to collapse
No still didn't find a fix. ?
Sent from my Moto G using XDA Free mobile app
I have the same problem
MetalPhoenix45 said:
Me being an impatient person, I updated my moto g XT1032, to 5.0.1 GPE firmware, before it came out for official Motorola rom. Since the UI was a bit too laggy, I switched to Cyanogenmod 12 (Yes, it was much smoother). But I started noticing a moving line with a flickering screen (I noticed this on TWRP recovery while I was on GPE firmware, but it didn't bother me). The flickering line is on the boot animation of CM, and it stays there when it turns on, unless I turn off the screen, then turn it on again. This goes for recovery mode as well. This starting to really bother me, so I hope there is a fix for this. One thing I noticed on Fastboot Flash Mode is the following: AP Fastboot Flash Mode (S)
41.18 (sha-99084d5, 2014-10-29 23:54:18)
Noticed the version? It was 2014-10-29, that's a very recent version. I think the bootloader got updated, I didn't think that was possible. Maybe this is causing the flickering's and the line? I saw other articles about this problem, but all of them only talked about recovery mode, and didn't give much detail. I hope someone finds a fix for this. Thanks for reading!
Click to expand...
Click to collapse
I downgrade to cm11 snapshot 6 stable, it worked one time always with this line which disappears after unlocking and then I had a sim card issue and force close com.android.systemui. Phone unusable, solution please
moumss52 said:
I downgrade to cm11 snapshot 6 stable, it worked one time always with this line which disappears after unlocking and then I had a sim card issue and force close com.android.systemui. Phone unusable, solution please
Click to expand...
Click to collapse
Factory reset, or update to a later version. If you restored a backup from a stock ROM, its probably why. I suggest you backup from adb then restore it to cyanogen mod.
Sent from my Moto G using XDA Free mobile app
MetalPhoenix45 said:
Factory reset, or update to a later version. If you restored a backup from a stock ROM, its probably why. I suggest you backup from adb then restore it to cyanogen mod.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
I handed the rom stock kitkat, it works but I still have this line in the recovery, in the boot and in the rom which disappears after lock screen. For now no other bug, I stay in rom stock some time to see if bugs appear.
I'm french, sorry if my english sucks!
The line is caused by the Kernel you are using not being compatible with the current Bootloader on your phone.
The problem will hopefully be solved by custom Kernels in the [near] future. If you absolutely can not wait, flash Lollipop Bootloader and Stock Lollipop, Motorola or GPE.
lost101 said:
The line is caused by the Kernel you are using not being compatible with the current Bootloader on your phone.
The problem will hopefully be solved by custom Kernels in the [near] future. If you absolutely can not wait, flash Lollipop Bootloader and Stock Lollipop, Motorola or GPE.
Click to expand...
Click to collapse
I am using CyanogenMod's stock kernel, I hope cyanogen looks into this in the future. But your answer doesn't make sense for recovery mode, unless recovery mode uses a kernel. Why does the line disappear after turning off and on then?
Sent from my Moto G using XDA Free mobile app
MetalPhoenix45 said:
I am using CyanogenMod's stock kernel, I hope cyanogen looks into this in the future. But your answer doesn't make sense for recovery mode, unless recovery mode uses a kernel. Why does the line disappear after turning off and on then?
Click to expand...
Click to collapse
Recoveries are also affected, because they are not fully compatible with the new Bootloader.
No Custom Roms in GPE 5.0.1
How did you install Cyanogenmod and other Custom Roms ? Because when I try to install them I get an error. I tried it with Philz Touch and TWRP. Of course I have made a full wipe. I'm running 5.0.1 GPE on my XT1032 Moto G. I used this thread to install GPE : http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847 . And here is a photo of the error in Philz Touch.
Sorry for my bad english.
Philz Recovery is no longer in development.
TWRP support for Lollipop is being worked on. More here.
Cameo164 said:
How did you install Cyanogenmod and other Custom Roms ? Because when I try to install them I get an error. I tried it with Philz Touch and TWRP. Of course I have made a full wipe. I'm running 5.0.1 GPE on my XT1032 Moto G. I used this thread to install GPE : http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847 . And here is a photo of the error in Philz Touch.
Sorry for my bad english.
Click to expand...
Click to collapse
I never saw this error before, I will search Google for it. But can you give me a screenshot of what it says on TWRP, because I'm more used to that. Thanks.
Sent from my Moto G using XDA Free mobile app
Of course here it is. I did a full wipe.
Sent from my XT1032 using XDA Free mobile app
This has been a known issue since the first unofficial CM12 builds; current kernel is not compatible with new bootloader (41.18), the issue won't be fixed until Motorola releases the kernel source code, so people can see where the problem is and fix it in custom roms or custom kernels.
To fix it you can:
a) follow a guide here in the forum to downgrade from 5.0.1 GPE to 4.4.4 GPE, then to 4.4.4 Motorola and then updating to 5.0.2 OTA (some people had the flickering fixed this way)
b) Wait for the full Motorola 5.0.2 firmware, wipe everithing and flash it
c) wait for the kernel source release, so someone can debug and fix that and then go to a custom ROM like CM12
Ok thank you for your helping. And when I downgrade to 4.4.4 Stock Motorola can I install custom roms ? Or does lollipop changed everything and I really have to wait till Motorola releases the codes. And I read many threads from people who hard bricked there moto g when they tried to downgrade. Is there a " safe " instruction.
Cameo164 said:
Ok thank you for your helping. And when I downgrade to 4.4.4 Stock Motorola can I install custom roms ? Or does lollipop changed everything and I really have to wait till Motorola releases the codes. And I read many threads from people who hard bricked there moto g when they tried to downgrade. Is there a " safe " instruction.
Click to expand...
Click to collapse
I have bootloader 41.18, if you read my post you would know that. It actually has nothing to do with bootloader. TWRP couldn't mount system. You could fix by changing file system to EXT4.
Sent from my Moto G using XDA Free mobile app
moralesnery said:
This has been a known issue since the first unofficial CM12 builds; current kernel is not compatible with new bootloader (41.18), the issue won't be fixed until Motorola releases the kernel source code, so people can see where the problem is and fix it in custom roms or custom kernels.
To fix it you can:
a) follow a guide here in the forum to downgrade from 5.0.1 GPE to 4.4.4 GPE, then to 4.4.4 Motorola and then updating to 5.0.2 OTA (some people had the flickering fixed this way)
b) Wait for the full Motorola 5.0.2 firmware, wipe everithing and flash it
c) wait for the kernel source release, so someone can debug and fix that and then go to a custom ROM like CM12
Click to expand...
Click to collapse
This could possibly fix the screen issue?
Sent from my Moto G using XDA Free mobile app
MetalPhoenix45 said:
I have bootloader 41.18, if you read my post you would know that. It actually has nothing to do with bootloader. TWRP couldn't mount system. You could fix by changing file system to EXT4.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
My file system is already ext4 so I don't understand the problem why TWRP can't mount the system partition.
Cameo164 said:
My file system is already ext4 so I don't understand the problem why TWRP can't mount the system partition.
Click to expand...
Click to collapse
Install the TWRP app from playstore and then go to install recovery and install the latest version available.
Sent from my Moto G using XDA Free mobile app
Cameo164 said:
My file system is already ext4 so I don't understand the problem why TWRP can't mount the system partition.
Click to expand...
Click to collapse
Maybe try and do a factory reset through fastboot?
Sent from my Moto G using XDA Free mobile app
Hello everyone, I have a Moto G (2013) aka first generation Moto G & I live in India. I had unlocked my bootloader. I even flashed cwm touch via fastboot but it doesn't go to recovery mode at all. I get a black screen. I tried flashing the official TWRP 2.8.4.0 today, but I get a message that reads, "Partition size mismatch" & I'm stuck. The phone is usable & it boots up normally & I use it daily. But it is the recovery that is messed up. I tried updating to lollipop by ota but the device got stuck on a black screen once the ota was downloaded. I tried downloading the KitKat factory image, but the link is dead. Please, somebody help!! Thanks in advance!
Sent from my XT1033 using xda premium
The partition size mismatch error can be ignored, You get that error because the TWRP 2.8.4.0 is for the XT1032 and not the XT1033. To flash the OTA, you have to use the stock recovery only. Your system should not be modified (eg. It shouldn't be rooted, and if it had been rooted previously, you will have to unroot it.) To flash the stock recovery again, download the Asian XT1033 4.4.4 firmware and just flash the "recovery.img" from it. The flash the OTA. The numerous guides regarding this in the general section should help you.
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
pr.itdude said:
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Click to expand...
Click to collapse
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
SoberDogs said:
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
Click to expand...
Click to collapse
Try fastboot erase cache, it shouldn't delete any of your data and it might be enough to get the device working again. You might want to wipe the dalvik-cache as well. If all else fails, since you can access you filesystem, backup all important files and do a factory reset.
skyguy126 said:
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
Click to expand...
Click to collapse
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
pr.itdude said:
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
Click to expand...
Click to collapse
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
skyguy126 said:
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
Click to expand...
Click to collapse
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
pr.itdude said:
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
Click to expand...
Click to collapse
Yep you should be good good luck!!!
Hello there,
Recently I had tried to go back to back from cyanogenmod 4.4.4 to stock 4.4.4, I accidentally flashed a XT1033 4.4.4 version.
Which was successful, but as I have a XT1031 device my phone does not use a sim card.
I then found a correct XT1031 4.4.4 stock firmware, but when I flashed this I had gotten stuck on the Bootloader Unlocked screen.
I tried it again with the same firmware, as well as others I found around, with little success.
I back tracked to the XT1033 version, went into fastboot mode and installed a custom recovery, CWM to be specific.
I then tried to sideload a stock 4.4.4 XT1031 ROM, I managed to get past the bootloader unlocked screen, but my phone then got stuck on "Starting Services" and I also noticed it was still getting detected as XT1033 on my computer.
Once again I tried to flash stock 4.4.4 firmware, again getting stuck at the bootloader unlocked screen.
At this point I'm at a loss how I should proceed or if my phone is even recoverable, I'm not worried about my data (as I backed it up before this whole fiasco, if only I had backed up a ROM too...).
If it wasn't obvious already, I'm not too experienced with all this, but at this point I'm just wondering if I should order another moto g.
Any help is appreciated.
Thanks,
Dan
Dan2QT said:
Hello there,
Recently I had tried to go back to back from cyanogenmod 4.4.4 to stock 4.4.4, I accidentally flashed a XT1033 4.4.4 version.
Which was successful, but as I have a XT1031 device my phone does not use a sim card.
I then found a correct XT1031 4.4.4 stock firmware, but when I flashed this I had gotten stuck on the Bootloader Unlocked screen.
I tried it again with the same firmware, as well as others I found around, with little success.
I back tracked to the XT1033 version, went into fastboot mode and installed a custom recovery, CWM to be specific.
I then tried to sideload a stock 4.4.4 XT1031 ROM, I managed to get past the bootloader unlocked screen, but my phone then got stuck on "Starting Services" and I also noticed it was still getting detected as XT1033 on my computer.
Once again I tried to flash stock 4.4.4 firmware, again getting stuck at the bootloader unlocked screen.
At this point I'm at a loss how I should proceed or if my phone is even recoverable, I'm not worried about my data (as I backed it up before this whole fiasco, if only I had backed up a ROM too...).
If it wasn't obvious already, I'm not too experienced with all this, but at this point I'm just wondering if I should order another moto g.
Any help is appreciated.
Thanks,
Dan
Click to expand...
Click to collapse
Try restoring stock. http://forum.xda-developers.com/showthread.php?t=2542219
ROMs here http://www.filefactory.com/folder/c6cdedc45a775d27/
dominati said:
Try restoring stock. http://forum.xda-developers.com/showthread.php?t=2542219
ROMs here http://www.filefactory.com/folder/c6cdedc45a775d27/
Click to expand...
Click to collapse
Thanks for your input, but unfortunately that actually was the method I was using,
Any other suggestions?
Dan2QT said:
Thanks for your input, but unfortunately that actually was the method I was using,
Any other suggestions?
Click to expand...
Click to collapse
You did all the fastboot commands? Was each command successful?
dominati said:
You did all the fastboot commands? Was each command successful?
Click to expand...
Click to collapse
Yeah, each of them gave me an "[OKAY]". I tried multiple ROM's too.
As of right now, the only one I could actually boot up on my device, was an XT1033 Brazillian 4.4.4 version (which boots successfully, but I can't use because it's not compatible with my device).
I might try to flash to that firmware, then re-install the XT1031 cyanogenmod I was using and restart the whole process.
I've tried a lot of different things at this point, so I'm willing to do whatever now.
-Dan
Same thing happened to me. In fact I ended up flashing xt1032 on my xt1031. Good thing is if it goes to the screen when loading to starting services and just keeps trying and trying then just look for the NON-HLOS.bin and fgn.mbn files for xt1031 and flash through fastboot. Basically those files are your radio. Or what you can do as well if you want to is to look for the radio flash zip file and flash it through custom recovery. Find the radio and kernel flash zip file and it should work as well. Those two files are here on XDA somewhere so you'll have to look for those. If your gonna use custom recovery route I found that twrp works better. I've had problems with cwm and philz.
christopher68369 said:
Same thing happened to me. In fact I ended up flashing xt1032 on my xt1031. Good thing is if it goes to the screen when loading to starting services and just keeps trying and trying then just look for the NON-HLOS.bin and fgn.mbn files for xt1031 and flash through fastboot. Basically those files are your radio. Or what you can do as well if you want to is to look for the radio flash zip file and flash it through custom recovery. Find the radio and kernel flash zip file and it should work as well. Those two files are here on XDA somewhere so you'll have to look for those. If your gonna use custom recovery route I found that twrp works better. I've had problems with cwm and philz.
Click to expand...
Click to collapse
Good call! I flashed the XT1032 GPE onto my device and it worked great!
Question for you though, would my wifi speeds be affected by using this firmware and would using the NON-HLOS.bin and fsg.mbn from the XT1031 firmware make any difference?
Thanks!,
Dan Anderson
Dan2QT said:
Good call! I flashed the XT1032 GPE onto my device and it worked great!
Question for you though, would my wifi speeds be affected by using this firmware and would using the NON-HLOS.bin and fsg.mbn from the XT1031 firmware make any difference?
Thanks!,
Dan Anderson
Click to expand...
Click to collapse
It shouldn't affect your WiFi. If you flashed the right kernel for your device then you won't have a problem. So if you downloaded the kernel for xt1031 and flashed it to a xt1031 then your WiFi will be fine. If you need help to get the radios then go on to google and type in xt1031 radio zip. First link will give you all the radios and kernels and recovery for each moto g model. The zips on that link are to be flashed through custom recovery. Find your device and then send it over to your device and flash. A lot of custom recovery will let you send files in recovery mode.
Have you tried downloading the xt1031 firmware again? May be a bad download. I have never had an issue returning back to stock on the boost variant.
I have the same problem
I have the same problem on the xt1031 just stuck into the screen unlocked bootloader and dont turn on please help mee!!
I need help converting xt1032 back to xt1031
I accidentally flashed xt1032 rom on my boost xt1031 unable to use it as a phone anymore is there anyway I can fix it I currently running GPE 5.1 I want to know if i can flash a xt1031 rom on it to fix it but everything I tried messed up and I would be stuck on a bootloader unlocked screen please help
jwj2ssp said:
I accidentally flashed xt1032 rom on my boost xt1031 unable to use it as a phone anymore is there anyway I can fix it I currently running GPE 5.1 I want to know if i can flash a xt1031 rom on it to fix it but everything I tried messed up and I would be stuck on a bootloader unlocked screen please help
Click to expand...
Click to collapse
Have you tried flashing stock firmware?
http://forum.xda-developers.com/showthread.php?t=3110795
Sent from my XT1031
ATTACK said:
Have you tried flashing stock firmware?
http://forum.xda-developers.com/showthread.php?t=3110795
Sent from my XT1031
Click to expand...
Click to collapse
I have tried flashing stuck many times it either get stuck on bootloader unlocked screen or It boot loops into fastboot I dont know if im doing everything right or im missing something Im going to try the rom from the link you sent me and see if it works thanks in advance