Related
I am trying to install the KK update for Tesco retail bought handsets and for some reason when I try to flash through CWM it says "this package is for falcon_umts devices : this is a xt1034
Yet it is a device I bought directly from tesco....I am at a loss on this one?
Can anyone help me reset the device back to default so it recognises as the correct XT1032?
I am stuck all I want is the KK update and me trying to root the device seems to have caused more problems.
Aye Up said:
I am trying to install the KK update for Tesco retail bought handsets and for some reason when I try to flash through CWM it says "this package is for falcon_umts devices : this is a xt1034
Yet it is a device I bought directly from tesco....I am at a loss on this one?
Can anyone help me reset the device back to default so it recognises as the correct XT1032?
I am stuck all I want is the KK update and me trying to root the device seems to have caused more problems.
Click to expand...
Click to collapse
You could try a data factory reset or flash a stock rom to solve your problem.
This one is easy: your CWM's build.prop identifies itself as an XT1034. Change your CWM, or remove the relevant assert line in the updater-script.
Darkshado said:
This one is easy: your CWM's build.prop identifies itself as an XT1034. Change your CWM, or remove the relevant assert line in the updater-script.
Click to expand...
Click to collapse
Thanks a lot. I never thought about this. I changed the CWM I had with Philz for x1032 and could finally install my OTA updates.
request for help to update CWM
Hi m3adow,
I have moto g UK version which i got from Amazon. I have rooted and installed CWM and xpose Framework. The OTA update fails. I get the same error that you have mentioned in the post - "this package is for falcon_umts devices : this is a xt1034". Can you please let me know how to update the CWM
thanks
You can download PhilZ touch here.
You can flash his cwm using your existing cwm or extract it and flash the img file using fastboot.
Darkshado said:
This one is easy: your CWM's build.prop identifies itself as an XT1034. Change your CWM, or remove the relevant assert line in the updater-script.
Click to expand...
Click to collapse
Mind helping me with that?
I'me having the same issue. Already tried with Phill xt1032 recovery and no go...
Any help will be welcome
Help
m3adow said:
Thanks a lot. I never thought about this. I changed the CWM I had with Philz for x1032 and could finally install my OTA updates.
Click to expand...
Click to collapse
Could you tell me how did you do that please I'm having the same problem as you!!!
Aprecciate it !!!!:fingers-crossed:
Read post 6
Rhazi3l said:
Mind helping me with that?
I'me having the same issue. Already tried with Phill xt1032 recovery and no go...
Any help will be welcome
Click to expand...
Click to collapse
Maybe you need Phil's for Faclon? I have a retail GB Moto G and Phil's for falcon was the only one that worked. The XT1032 failed also.
mdentener said:
Maybe you need Phil's for Faclon? I have a retail GB Moto G and Phil's for falcon was the only one that worked. The XT1032 failed also.
Click to expand...
Click to collapse
Tried with falcon as well and it still doesn't work. This one was bought on amazon UK and when connecting onto the PC it shows as XT1032. I was already looking into the build.prop on the system and it shows XT1032 and falcon_umts. And the update_script on Phil's recovery lists them all in order to be able to install easily on every Moto G model. Not rly sure what else we can try to add / change on build.prop or on recovery to get it to be recognised correctly.
I will try the other recoveries to see if any works.
i solved this problem, by flashing this rom "RETAIL-DE_FALCON_KLB20.9-1.10-1.9.1_cid7_CFC_1FF_v8.xml". It works perfectly, and original recovery is also working fine. You should try out this one here:
https://app.box.com/s/kdey7xefe9kez1phorpi
I need help.
I just unlocked my BL (yay!) but for some stupid reason, I excuted a .bat file I downloaded from a post here in XDA, that I thought would give me option to root, install recovery or whatever I choose to do. Well, that .bat file turned my Moto G into Moto G GPE. Is that a problem if I want to root or install a custom recovery or even to install this ROM?
I don't know what should I do. Bacause everything in this world is saparated for stock and GPE so I don't know if I treat my phone like a GPE or like a stock
A quick answer would help a lot.
Greetings.
Um, prob not
XXtremiXX said:
I need help.
I just unlocked my BL (yay!) but for some stupid reason, I excuted a .bat file I downloaded from a post here in XDA, that I thought would give me option to root, install recovery or whatever I choose to do. Well, that .bat file turned my Moto G into Moto G GPE. Is that a problem if I want to root or install a custom recovery or even to install this ROM?
I don't know what should I do. Bacause everything in this world is saparated for stock and GPE so I don't know if I treat my phone like a GPE or like a stock
A quick answer would help a lot.
Greetings.
Click to expand...
Click to collapse
Only downloading the .bat file wouldn't turn your phone to GPe. It would turn to GPe only if you would have downloaded the whole ROM which is about 450 mb. Do you remember downloading something this big. And even if you did convert to GPe then don't worry... everything is same as the non GPe... except the custom recovery which is also available for GPe devices here https://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon_gpe/ It is the CWM advanced edition by PhilZ.
And if you want to gio back to the original by flashing the stock XT1032 firmware(don', don't, even by mistake flash the xt1033 one). The link for the firmware and how to flash it is here www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
Meuuks13 said:
Only downloading the .bat file wouldn't turn your phone to GPe. It would turn to GPe only if you would have downloaded the whole ROM which is about 450 mb. Do you remember downloading something this big. And even if you did convert to GPe then don't worry... everything is same as the non GPe... except the custom recovery which is also available for GPe devices here https://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon_gpe/ It is the CWM advanced edition by PhilZ.
And if you want to gio back to the original by flashing the stock XT1032 firmware(don', don't, even by mistake flash the xt1033 one). The link for the firmware and how to flash it is here www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
Click to expand...
Click to collapse
Yes, it was like 700mb of files, so I think I downloaded the ROM too
I just want to install CyanogenMod or PA (I just installed PA and it works perfectly).
Now the question is, it is still like a GPE? Even if I have PA installed?
Thanks for answering.
XXtremiXX said:
Yes, it was like 700mb of files, so I think I downloaded the ROM too
I just want to install CyanogenMod or PA (I just installed PA and it works perfectly).
Now the question is, it is still like a GPE? Even if I have PA installed?
Thanks for answering.
Click to expand...
Click to collapse
GPe edition means that you will get Android update faster and the android version is untouched. Now since you have PA, you won't recieve any official updates and android version has already been touched and customized for PA.
So you can safely say it isn't GPe.
In short you flashed a wholw different ROM so its not GPe anymore.
And bro, recovery imgs are around 10 mb and SuperSu is around 2mb... Save bandwidth and don't just download anything..
Meuuks13 said:
GPe edition means that you will get Android update faster and the android version is untouched. Now since you have PA, you won't recieve any official updates and android version has already been touched and customized for PA.
So you can safely say it isn't GPe.
In short you flashed a wholw different ROM so its not GPe anymore.
And bro, recovery imgs are around 10 mb and SuperSu is around 2mb... Save bandwidth and don't just download anything..
Click to expand...
Click to collapse
Hahaha made me laugh. You are right. I didn't realise that. I thought it was dirvers and stuff. Like I said, I thought it was kind of a tool for doing all thw work instead of using console. Like Flashtool or something like that.
Now I will be careful with the things I download and run.
Thanks for helping me.
XXtremiXX said:
Hahaha made me laugh. You are right. I didn't realise that. I thought it was dirvers and stuff. Like I said, I thought it was kind of a tool for doing all thw work instead of using console. Like Flashtool or something like that.
Now I will be careful with the things I download and run.
Thanks for helping me.
Click to expand...
Click to collapse
Always welcome..
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 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