Related
Guys, recently I converted my XT1032 to GPe version to get Lollipop update. I installed everthing and now I've got it.
The problem is, whenether I try to factory reset, it gets Error on Green Robot image.
Is there any solution for this? It freaks me out.
I have the same issue with my converted Moto G. I haven't had time to investigate yet, but there's a (relatively) easy way to do this:
Code:
fastboot erase userdata
Keep in mind that this will erase everything.
If you aren't already familiar with fastboot and the Moto G, there's a wealth of information on this forum. Just search Google and/or XDA for "fastboot Moto G".
Same error here. Got the same error if trying to reach stock recovery. Did you try to flash custom recovery to solve this?
Solved
Antique_Angel said:
Guys, recently I converted my XT1032 to GPe version to get Lollipop update. I installed everthing and now I've got it.
The problem is, whenether I try to factory reset, it gets Error on Green Robot image.
Is there any solution for this? It freaks me out.
Click to expand...
Click to collapse
Bro I did was flash the stock recovery for the GPE with mototool and then I did it manually entering fastboot , recovery and making wipe data . Solved for me
fastboot method is the only current method right now, once the 5.0.2 or 5.0.3 firmware comes out, flash the partition and the stock recovery and try again through recovery.
michael android said:
Bro I did was flash the stock recovery for the GPE with mototool and then I did it manually entering fastboot , recovery and making wipe data . Solved for me
Click to expand...
Click to collapse
Great! Is this a permanent solution, or you have to do this every time you want to reset the device?
Also, if I later want to go back to Motorola Stock will I have issues with this GPE stock recovery?
I hope my questions make sense, as you can see i'm one of those "first time commenting" newbies on XDA
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
HI all,
I have a Moto G 4G (XT1039 EU), after upgrading to Lollipop (5.1) i decided to root it.
I unlocked the bootloader and then i tried to follow this guide http://forum.xda-developers.com/moto-g/general/newb-friendly-guide-to-rooting-moto-g-t2793895 but TWRP didn't boot.
So i looked for another guide and i found this one http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-cwm-6-0-5-0-t2818161 , it worked (except that when you flash the the recovery to phone using
Code:
fastboot flash recovery clockworkmodrecovery.6051.peregrine.img
screen flickers) but i did a mistake: i backed up to internal memory instead of SD .
Next i backed up to SD and the rebooted phone but i discovered that my internal memory is messed up : i have less space on internal memory and after more than one month apps are starting to behave in strange ways.
I think i messed up the partition table, how can i fix it?
I have a backup but i think it's faulty (i did it after the mistake..), i think that i should revert to stock firmware, but i'm not sure and i didn't find a noob proof step-by-step guide (i'm not sure about which one i should follow).
Any help is appreciated, thanks in advance
Flash stock firmware.
motofirmware.center
Sent from my XT1031
ATTACK said:
Flash stock firmware.
motofirmware.center
Sent from my XT1031
Click to expand...
Click to collapse
Hi thanks for the reply.
I checked the site but there's no firmware for my Moto G 4G (23.21.17.peregrine_reteu.reteuall.en.EU reteu)), there is a US firmware but not for EU.
Browsing the forum i think i found the right firmware from this thread http://forum.xda-developers.com/showthread.php?t=2542219.
Do the instructions apply also to Moto G 4G (i think they do, there are links also to firmware for my phone)?
_Immanuel_ said:
Hi thanks for the reply.
I checked the site but there's no firmware for my Moto G 4G (23.21.17.peregrine_reteu.reteuall.en.EU reteu)), there is a US firmware but not for EU.
Browsing the forum i think i found the right firmware from this thread http://forum.xda-developers.com/showthread.php?t=2542219.
Do the instructions apply also to Moto G 4G (i think they do, there are links also to firmware for my phone)?
Click to expand...
Click to collapse
Yeah, just unpack the firmware zip and input those commands (listed in that topic) in mfastboot.
First confirm that the firmware files and commands are the same. If not, simply adjust the commands to match the firmware names.
Sent from my XT1031
ATTACK said:
Yeah, just unpack the firmware zip and input those commands (listed in that topic) in mfastboot.
First confirm that the firmware files and commands are the same. If not, simply adjust the commands to match the firmware names.
Sent from my XT1031
Click to expand...
Click to collapse
It worked!
I flashed all files in order, they had a different name (system.img_sparsechunk.* insted of system.img_sparsechunk*) and i had 4 chunks instead of 3.
Then i flashed cwm recovery (clockworkmodrecovery.6051.peregrine.img, screen flickers but it works) and then i rooted with SuperSu, right now i'm reinstalling all the apps.
Thank you! :victory:
Hi, I have CM13 2015-10-29 unofficial on my Moto G first gen (XT1032) . I've been gettings this notification about some updates so I thought I'd flash them. But because I'm new to this flashing stuff (only done it once and soft bricked my phone ) I have some questions:
1) There are three updates for my phone (2015-12-19, 20 and 21), do I need to flash them in the order they came out or do I need to just flash the latest one? Is there a risk of bricking? What are the exact steps I need to take to flash? (i.e. wiping data, etc)
2) I'm going to download from here: http://www.cmxlog.com/13/falcon/, I just want to know if there is an official (stable) version available for my phone.
3) I had a few more questions but I can't remember them right now. I'll post them when I remember.
harut2K said:
Hi, I have CM13 2015-10-29 unofficial on my Moto G first gen (XT1032) . I've been gettings this notification about some updates so I thought I'd flash them. But because I'm new to this flashing stuff (only done it once and soft bricked my phone ) I have some questions:
1) There are three updates for my phone (2015-12-19, 20 and 21), do I need to flash them in the order they came out or do I need to just flash the latest one? Is there a risk of bricking? What are the exact steps I need to take to flash? (i.e. wiping data, etc)
2) I'm going to download from here: http://www.cmxlog.com/13/falcon/, I just want to know if there is an official (stable) version available for my phone.
3) I had a few more questions but I can't remember them right now. I'll post them when I remember.
Click to expand...
Click to collapse
1) You can just pick up the latest 21 december build - no need for flashing each in order.
2) No stable version yet for falcon - https://download.cyanogenmod.org/?device=falcon
3) Sure
ssinghebay said:
1) You can just pick up the latest 21 december build - no need for flashing each in order.
2) No stable version yet for falcon - https://download.cyanogenmod.org/?device=falcon
3) Sure
Click to expand...
Click to collapse
So all I need to do is download the ZIP and flash? No wiping nessessary?
harut2K said:
So all I need to do is download the ZIP and flash? No wiping nessessary?
Click to expand...
Click to collapse
You can follow the "Clean Update" process in the 2nd post of this thread:
http://forum.xda-developers.com/moto-g/orig-development/rom-official-cyanogenmod-13-nightly-t3260344
Alternatively - why dont you try the CyanDelta app - it just downloads the changed files from the latest build and flashes it. This app works wel on CM12.1 and CM13.
ssinghebay said:
You can follow the "Clean Update" process in the 2nd post of this thread:
http://forum.xda-developers.com/moto-g/orig-development/rom-official-cyanogenmod-13-nightly-t3260344
Alternatively - why dont you try the CyanDelta app - it just downloads the changed files from the latest build and flashes it. This app works wel on CM12.1 and CM13.
Click to expand...
Click to collapse
Cool, thanks. One last question; it says that I should not wipe data, is this my internal memory? (photos, files, etc.)
harut2K said:
Cool, thanks. One last question; it says that I should not wipe data, is this my internal memory? (photos, files, etc.)
Click to expand...
Click to collapse
Yes : ) Apps, personal files and stuff.
And you can hit the thanks button instead of thanking in text
If I dirty update will it slow down my phone?????
Currently working with my onePlus one, 64gb version.
I was using This guide in order to install lineageOs. i'm a little rusty with my oneplus one, and some stuff happened and I ended up soft bricking it lmao. Currently it has no OS because I formatted the data in twrp wipe. Currently all I can do is [VOL UP + POWER] to go into fastboot, and [VOL DOWN + POWER] to go into twrp 3.1.1-0. I honestly need help just starting from the beginning. Anybody can help a fellow oneplus lover(69) out?
P.S. I also have access to this guide in order to unbrick the phone, but that gives me some old cyanogen mod 11.0 kit kat stuff. I really don't want that. I want the new lineageOS 14.1!
onepluslover69 said:
Currently working with my onePlus one, 64gb version.
I was using This guide in order to install lineageOs. i'm a little rusty with my oneplus one, and some stuff happened and I ended up soft bricking it lmao. Currently it has no OS because I formatted the data in twrp wipe. Currently all I can do is [VOL UP + POWER] to go into fastboot, and [VOL DOWN + POWER] to go into twrp 3.1.1-0. I honestly need help just starting from the beginning. Anybody can help a fellow oneplus lover(69) out?
P.S. I also have access to this guide in order to unbrick the phone, but that gives me some old cyanogen mod 11.0 kit kat stuff. I really don't want that. I want the new lineageOS 14.1!
Click to expand...
Click to collapse
Boot into twrp,wipe data/factory reset,format cache then go to advanced and wipe system and dalvik cache then flash lineage os+gapps and reboot.:fingers-crossed:
Mr.Ak said:
Boot into twrp,wipe data/factory reset,format cache then go to advanced and wipe system and dalvik cache then flash lineage os+gapps and reboot.:fingers-crossed:
Click to expand...
Click to collapse
for some reason when i connect my phone via usb, it doesn't show up on my computer. i have no idea why, because it shows up when there is an OS and connected, but not in twrp
onepluslover69 said:
for some reason when i connect my phone via usb, it doesn't show up on my computer. i have no idea why, because it shows up when there is an OS and connected, but not in twrp
Click to expand...
Click to collapse
No worries,you can use adb sideload to flash files.
Here's how:http://www.droidviews.com/sideload-roms-mods-using-adb-sideload/
Mr.Ak said:
No worries,you can use adb sideload to flash files.
Here's how:http://www.droidviews.com/sideload-roms-mods-using-adb-sideload/
Click to expand...
Click to collapse
So I tried abd sideloading, but I got an error saying that the: updater process ended with error 7. i have no idea what to do at this point. i feel like every guide I follow step by step only to get an error
onepluslover69 said:
So I tried abd sideloading, but I got an error saying that the: updater process ended with error 7. i have no idea what to do at this point. i feel like every guide I follow step by step only to get an error
Click to expand...
Click to collapse
Did you followed the guide correctly? If the drivers are correct,you should not get any errors.Make sure to not forget extension while writing file name which in our case is ".zip".
Can you post a screenshot of cmd screen?
forgot to reply
Mr.Ak said:
Did you followed the guide correctly? If the drivers are correct,you should not get any errors.Make sure to not forget extension while writing file name which in our case is ".zip".
Can you post a screenshot of cmd screen?
Click to expand...
Click to collapse
http://imgur.com/feR5GkZ
http://imgur.com/j5qGhmB
currently legitimately lost. am i just a ****ing idiot? i didnt even have this much issues when i was rooting my oneplus 5...
onepluslover69 said:
http://imgur.com/feR5GkZ
http://imgur.com/j5qGhmB
currently legitimately lost. am i just a ****ing idiot? i didnt even have this much issues when i was rooting my oneplus 5...
Click to expand...
Click to collapse
Hey,nobody is an idiot on xda.
On which rom were you before flashing lineage os?
Mr.Ak said:
Hey,nobody is an idiot on xda.
On which rom were you before flashing lineage os?
Click to expand...
Click to collapse
cyanogenmod 11s which was like 4.4.x kitkat. but i formatted the phone , so that shouldn't even matter should it. currently i have no os.. :\
onepluslover69 said:
cyanogenmod 11s which was like 4.4.x kitkat. but i formatted the phone , so that shouldn't even matter should it. currently i have no os.. :\
Click to expand...
Click to collapse
No,that is the thing causing issues,i thought were on cos13.1.x but since you're on cm11s,you'll have to flash new firmware first which supports nougat.
There are many but this one works fine for me,https://www.androidfilehost.com/?fid=24385658843824392
Wipe data factory reset and cache then go to advanced and wipe system and dalvik cache then Flash the firmware,then lineage os and gapps and reboot,Profit.
Mr.Ak said:
No,that is the thing causing issues,i thought were on cos13.1.x but since you're on cm11s,you'll have to flash new firmware first which supports nougat.
There are many but this one works fine for me,https://www.androidfilehost.com/?fid=24385658843824392
Wipe data factory reset and cache then go to advanced and wipe system and dalvik cache then Flash the firmware,then lineage os and gapps and reboot,Profit.
Click to expand...
Click to collapse
omfg it finally worked. i got lineage os 14.1 with 7.1.2 nougat, and mini gapps thanks bro you saved me
onepluslover69 said:
omfg it finally worked. i got lineage os 14.1 with 7.1.2 nougat, and mini gapps thanks bro you saved me
Click to expand...
Click to collapse
Told you,you're not an idiot.
Wow. The latest lineage os update killed my phone too and I tried doing this but I don't understand how to flash