Hi everyone,
So it would appear that the current builds of CWM and TWRP for the retail XT1032 Moto G won't boot on the Google Play Edition, at least not while booting from memory.
I've tried using fastboot boot recovery.img and it simply reboots and boots into the stock ROM normally.
Since factory images aren't available, I won't attempt to do a perm flash (fastboot flash recovery recovery.img) because I don't want to overwrite stock recovery without dumping it first (for archival purposes).
So, I guess my question here is twofold.
1. Has anyone else with a Moto G GPE had luck booting CWM or TWRP?
2. If not, is someone willing to try to get a version of one or both that WILL boot?
Any insight and help would be appreciated!
Sent from my Moto G Google Play Edition using Tapatalk
Have you tried the Supervboot method? That may allow you to root without modifying the recovery.
Maybe it sounds dumb, but did you unlocked the bootloader first? maybe you just can flash the recovery safely since the GPE its Android 4.4.2, you can flash the same stock recovery from the US Retail 4.4.2... I don't see why the recovery must be updated on the GPE since it has the same Android version as the other 4.4.2 firmwares...
Beegee7730 said:
Have you tried the Supervboot method? That may allow you to root without modifying the recovery.
Click to expand...
Click to collapse
I'll check into that.
EDIT: Not going to work. It would involve changes to the boot image, which I also don't want to do. I want raw, untouched dumps of system, boot, and recovery. I get the feeling that the only way to get that right now is going to be booting CWM or TWRP from memory using "fastboot boot," but that method doesn't currently work with the currently available Moto G builds of TWRP or CWM.
joel_sinbad said:
Maybe it sounds dumb, but did you unlocked the bootloader first? maybe you just can flash the recovery safely since the GPE its Android 4.4.2, you can flash the same stock recovery from the US Retail 4.4.2... I don't see why the recovery must be updated on the GPE since it has the same Android version as the other 4.4.2 firmwares...
Click to expand...
Click to collapse
The recovery is different between each and every Android ROM. The stock recovery from the retail ROM would probably boot but you wouldn't be able to flash GPE OTAs with it. And yeah, I unlocked the bootloader before I booted it for the first time.
Sent from my Galaxy Note 3 using Tapatalk
I saw this from a post from XDA but maybe you can try it:
conect via adb shell or in terminal emulator type: cat/proc/mtd and press enter
you will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
after that you will have recovery.img on your sd card
OK so I downloaded the stock XT1032 US falcon_umts images for Android 4.4.2. I did fastboot boot recovery.img on the stock recovery from those images. It worked, so the bootloader is definitely capable of booting a recovery from memory. I think this is more an issue with the actual custom recoveries available. With that said, anyone up for trying to get this working? I'll happily be the guinea pig for any test builds.
joel_sinbad said:
I saw this from a post from XDA but maybe you can try it:
conect via adb shell or in terminal emulator type: cat/proc/mtd and press enter
you will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
after that you will have recovery.img on your sd card
Click to expand...
Click to collapse
Unfortunately, that only works if you're rooted. That's why I'm looking to boot a custom recovery from memory. I'll have root access via adb shell and be able to dump to my heart's content without overwriting the stock recovery or the stock boot image. Thanks for the suggestion, though.
Beegee7730 said:
Have you tried the Supervboot method? That may allow you to root without modifying the recovery.
Click to expand...
Click to collapse
@oldblue910 I don't think this method changes boot.img. it just boots a custom boot.img from your PC and roots phone. On next boot it boots boot.img from the phone as normal.
BTW I'm on non-GPE 4.3 stock recovery and can issue
fastboot boot recovery.img
to boot into a custom recovery.
However I believe on nexus devices the option to boot a recovery from PC was removed but you can still do it using some weird parameters on the command - maybe the same type of thing on moto g GPE when booting just a custom recovery??
See following link for the parameters on nexus 7 (which is most likely just for nexus 7 but you get the idea)
http://forum.xda-developers.com/showthread.php?t=2380675
scott_doyland said:
@oldblue910 I don't think this method changes boot.img. it just boots a custom boot.img from your PC and roots phone. On next boot it boots boot.img from the phone as normal.
BTW I'm on non-GPE 4.3 stock recovery and can issue
fastboot boot recovery.img
to boot into a custom recovery.
However I believe on nexus devices the option to boot a recovery from PC was removed but you can still do it using some weird parameters on the command - maybe the same type of thing on moto g GPE when booting just a custom recovery??
See following link for the parameters on nexus 7 (which is most likely just for nexus 7 but you get the idea)
http://forum.xda-developers.com/showthread.php?t=2380675
Click to expand...
Click to collapse
Thanks for clarifying about the boot.img. I'll look into it some more.
As for "fastboot boot", every Nexus and GPE can do it as long as the bootloader is unlocked. I've never had any issue booting recoveries from memory except on the GS4 GPE. Not to get off topic, but touch recoveries are useless if booted from memory on the GS4 GPE. That's not so much of a problem for CWM since you can navigate with the volume and power keys, but TWRP, forget it. If you perm flash, everything is fine.
EDIT: That's interesting about the Nexus 4. Apparently that was a bootloader change beginning with Android 4.3. I can confirm that more modern Nexus devices do not have this issue. Weird.
Anyway, I'm going to look into that root method some more. I'll report with success or failure.
OK, just an update. Superboot doesn't work with the Play Edition ROM. If you fastboot boot it (I tried using normal Android fastboot and the Moto fastboot that comes in the zip file), it just boots to a blank screen and hangs. No boot animation, no nothing.
Obviously there's something different somewhere between the GPE and the retail US XT1032. Not sure what it is...but yeah, right now none of the custom recovery kangs work and superboot doesn't work. The only thing I've managed to boot successfully using fastboot boot was the 4.4.2 stock recovery for the retail US XT1032.
At this point I'm going to loop @a1Pha into this thread and ask if he has any thoughts, since he created the working kangs of CWM and TWRP that people seem to be using.
oldblue910 said:
OK, just an update. Superboot doesn't work with the Play Edition ROM. If you fastboot boot it (I tried using normal Android fastboot and the Moto fastboot that comes in the zip file), it just boots to a blank screen and hangs. No boot animation, no nothing.
Obviously there's something different somewhere between the GPE and the retail US XT1032. Not sure what it is...but yeah, right now none of the custom recovery kangs work and superboot doesn't work. The only thing I've managed to boot successfully using fastboot boot was the 4.4.2 stock recovery for the retail US XT1032.
Click to expand...
Click to collapse
I just rooted my XT1032 US Retail 4.4.2 with Superboot, it booted a weird purple screen and then went black screen, but after Hard Rebooting, the phone was rooted, did you checked that?
joel_sinbad said:
I just rooted my XT1032 US Retail 4.4.2 with Superboot, it booted a weird purple screen and then went black screen, but after Hard Rebooting, the phone was rooted, did you checked that?
Click to expand...
Click to collapse
Just checked. There is no su binary in /system/xbin or /system/bin/.ext and there is no Superuser.apk file either.
Sent from my Moto G Google Play Edition using Tapatalk
oldblue910 said:
At this point I'm going to loop @a1Pha into this thread and ask if he has any thoughts, since he created the working kangs of CWM and TWRP that people seem to be using.
Click to expand...
Click to collapse
Interesting. So did I understand this correctly, that flashing a stock recovery from non-GPE Moto G does work?
Which version does your bootloader show? Which kernel version shows up in phone settings?
a1Pha said:
Interesting. So did I understand this correctly, that flashing a stock recovery from non-GPE Moto G does work?
Which version does your bootloader show? Which kernel version shows up in phone settings?
Click to expand...
Click to collapse
You understand correctly, yes. The bootloader version is 41.05 and the kernel version in settings is 3.4.0.
Sent from my Galaxy S4 Google Play Edition using Tapatalk
oldblue910 said:
You understand correctly, yes. The bootloader version is 41.05 and the kernel version in settings is 3.4.0.
Sent from my Galaxy S4 Google Play Edition using Tapatalk
Click to expand...
Click to collapse
Looks like we have to wait for GPE sources to be released to adapt the kernel to the new bootloader. They should release the sources quite soon, so said a source of @dhacker29
a1Pha said:
Looks like we have to wait for GPE sources to be released to adapt the kernel to the new bootloader. They should release the sources quite soon, so said a source of @dhacker29
Click to expand...
Click to collapse
Sounds good. Thank you very much for your help! Let's keep this thread open for continuing discussion once the sources are released. Once we have kernel source, I'll be happy to test any recovery builds on my GPE device if you need testers.
Sent from my Galaxy S4 Google Play Edition using Tapatalk
oldblue910 said:
Sounds good. Thank you very much for your help! Let's keep this thread open for continuing discussion once the sources are released. Once we have kernel source, I'll be happy to test any recovery builds on my GPE device if you need testers.
Sent from my Galaxy S4 Google Play Edition using Tapatalk
Click to expand...
Click to collapse
The GPE Moto G uses ext4 data partition vs f2fs data partition for the Retail version so it's just a matter of having the right fstab in the recovery.
Try with this build
https://mega.co.nz/#!P8BQGYKK!StnnD0z91KLFxAgxQvSMUVWGC-A-4tcqiv9sgh1yXcw
alternate link
https://drive.google.com/file/d/0BxD_8WtIEc3SZnY2al9ZM0VTOFE/edit?usp=sharing
install with flashify app from phone booted in normal mode and then go to recovery
oldblue910 said:
Hi everyone,
So it would appear that the current builds of CWM and TWRP for the retail XT1032 Moto G won't boot on the Google Play Edition, at least not while booting from memory.
I've tried using fastboot boot recovery.img and it simply reboots and boots into the stock ROM normally.
Since factory images aren't available, I won't attempt to do a perm flash (fastboot flash recovery recovery.img) because I don't want to overwrite stock recovery without dumping it first (for archival purposes).
So, I guess my question here is twofold.
1. Has anyone else with a Moto G GPE had luck booting CWM or TWRP?
2. If not, is someone willing to try to get a version of one or both that WILL boot?
Any insight and help would be appreciated!
Sent from my Moto G Google Play Edition using Tapatalk
Click to expand...
Click to collapse
If you go through a1pha's thread, you'll find a TWRP repack from me that was based on a stock 4.4 kernel. Can you try that with "fastboot boot"? (In fact, that particular release from me is ONLY compatible with fastboot boot as it's too big to fit into the recovery partition...) That particular build has a lot of flaws, but should at least let you flash SuperSU on your device so you can back up the stock recovery and kernel partitions.
My observations on Monday are that a lot of recoveries that work properly when flashed to the device fail when attempting to boot them using "fastboot boot" - even on the non-GPe variants! None of the recoveries in dhacker's CM11 thread work with "fastboot boot" and neither does any one I build from Omni sources.
Many non-Nexus devices often have weird issues where "fastboot boot" doesn't work properly. I know Omni lost at least two weeks on the Oppo N1 due to the fact that "fastboot boot" is broken on that device.
Related
Alright, so here's the issue. I tried to flash a version of CW onto my HDMaxx (XT926) and it failed, saying the file size was incorrect. Now, whenever I boot, it goes to the same recovery screen and says that the flash failed, even when I don't boot into recovery. After many failed attempts, I still cannot reflash the recovery. It still boots if I manually go into the bootloader and just select normal bootup, but as you can imagine, it gets pretty old having to do that. I just installed OTA JB yesterday, and it worked fine (after manually installing the zip myself) but the same problem still occurs on boot. Any help? Thanks in advance.
Action123 said:
Alright, so here's the issue. I tried to flash a version of CW onto my HDMaxx (XT926) and it failed, saying the file size was incorrect. Now, whenever I boot, it goes to the same recovery screen and says that the flash failed, even when I don't boot into recovery. After many failed attempts, I still cannot reflash the recovery. It still boots if I manually go into the bootloader and just select normal bootup, but as you can imagine, it gets pretty old having to do that. I just installed OTA JB yesterday, and it worked fine (after manually installing the zip myself) but the same problem still occurs on boot. Any help? Thanks in advance.
Click to expand...
Click to collapse
Reflash stock firmware. Check the stock firmware thread for your device in development subforum.
Its usually a good idea to flash to stock before upgrading os anyway.
Action123 said:
Alright, so here's the issue. I tried to flash a version of CW onto my HDMaxx (XT926) and it failed, saying the file size was incorrect. Now, whenever I boot, it goes to the same recovery screen and says that the flash failed, even when I don't boot into recovery. After many failed attempts, I still cannot reflash the recovery. It still boots if I manually go into the bootloader and just select normal bootup, but as you can imagine, it gets pretty old having to do that. I just installed OTA JB yesterday, and it worked fine (after manually installing the zip myself) but the same problem still occurs on boot. Any help? Thanks in advance.
Click to expand...
Click to collapse
you said HDMaxx? do you have a retail verizon razr hd? because clockwork is only for developer devices unlocked. and im pretty sure they dont have a developer Maxx HD
You need to successfully flash any of your partitions with a signed image in fast boot. Pick a small and relatively minor one like device tree.
The bootup error you are seeing means that an unsigned image was attempted to be flashed on a locked boot loader device and should go away once any properly signed image is flashed again afterwards. You could just flash the stock recovery image from the full XML fast boot file too.
The device should boot normally again thereafter.
zooyork0721 said:
you said HDMaxx? do you have a retail verizon razr hd? because clockwork is only for developer devices unlocked. and im pretty sure they dont have a developer Maxx HD
Click to expand...
Click to collapse
cellzealot said:
You need to successfully flash any of your partitions with a signed image in fast boot. Pick a small and relatively minor one like device tree.
The bootup error you are seeing means that an unsigned image was attempted to be flashed on a locked boot loader device and should go away once any properly signed image is flashed again afterwards. You could just flash the stock recovery image from the full XML fast boot file too.
The device should boot normally again thereafter.
Click to expand...
Click to collapse
No, It is an HDMaxx. It has the version XT926, but it is stock Verizon. Does anyone have any knowledge of a thread with an instructional for unlocking my bootloader and a clockwork/Amon Ra/etc. flash? I'm just struggling to find anything. Almost seems like very few people are working with my device as of this moment.
Action123 said:
No, It is an HDMaxx. It has the version XT926, but it is stock Verizon. Does anyone have any knowledge of a thread with an instructional for unlocking my bootloader and a clockwork/Amon Ra/etc. flash? I'm just struggling to find anything. Almost seems like very few people are working with my device as of this moment.
Click to expand...
Click to collapse
Verizon branded XT926 are bootloader locked, period. Verizon insisted it be that way. Since the HD Maxx doesn't have a developer's edition (which you can unlock the bootloader on), you are limited to hacks/workarounds that use a signed kernel to load a custom one. Check the Developers forum for hack posts.
EdwardN said:
Verizon branded XT926 are bootloader locked, period. Verizon insisted it be that way. Since the HD Maxx doesn't have a developer's edition (which you can unlock the bootloader on), you are limited to hacks/workarounds that use a signed kernel to load a custom one. Check the Developers forum for hack posts.
Click to expand...
Click to collapse
Thank you sir.
Action123 said:
No, It is an HDMaxx. It has the version XT926, but it is stock Verizon. Does anyone have any knowledge of a thread with an instructional for unlocking my bootloader and a clockwork/Amon Ra/etc. flash? I'm just struggling to find anything. Almost seems like very few people are working with my device as of this moment.
Click to expand...
Click to collapse
Google safe strap for this device. We don't have clockwork on the consumer version but we do have safestrap which uses TWRP recovery. I use that to flash stuff. It's actually better because you leave your stock rom on the safe side and flash on the other partition and don't have to worry about bricking anything.
Sent from my DROID RAZR HD using xda premium
clouse2013 said:
Google safe strap for this device. We don't have clockwork on the consumer version but we do have safestrap which uses TWRP recovery. I use that to flash stuff. It's actually better because you leave your stock rom on the safe side and flash on the other partition and don't have to worry about bricking anything.
Sent from my DROID RAZR HD using xda premium
Click to expand...
Click to collapse
I did read up on TWRP a while ago. It kinda looked like a pain to me. I don't know, but I just want to be able to boot straight into my ROM of choice immediately without having to go through a bootloader (for someone other than myself, not in the knowing of what they're doing ICE). I used to have an N1 running CM7 and it was just what I wanted. Are there any downfalls of using this method that you have seen?
http://youtu.be/faSg3puGssQ
download
http://www.mediafire.com/download/3..._recovery_6.13.19,_root,_drivers,_logo_fix.7z
basically this is a one click solution to flash a moto g into GPE, with a custom recovery, and boot logo fixed with every file included
hi, i just made this pack, in order to get an easy GPE rom with fixed logo and philz recovery with everything included for the flash ib 1 click, i just compiled some things so it can be easier for noobs and even no noobs to save time
the original idea came from this:
http://forum.xda-developers.com/showthread.php?t=2646404, but i wanted to add a custom recovery, logo fixed for unlocked devices, and have it all ready in a single package
features:
-4.4.2 rom GPE xt1032 stock
-adb files
-philz recovery falcon gpe philz_touch_6.13.9-falcon_gpe, you can replace the recovery for any other you want (using the same name for recovery) (i 100% recommend to use this included) warning read the last part of post
-supersu compatible with the philz recovery included for root (newer philz recovery does not work in gpe, also newer supersu cannot be flashed in the included recovery, you have to use this 2 versions included, trust me, later you still can update supersu)
-motorola drivers included, MotorolaDeviceManager_2.4.5
-logo fixed for unlocked devices (normal logo without the dumb unlocked blablabla info)
usage:
1)you need a moto g 1032xt with UNLOCKED BOOTLOADER, yes i mean you can use a stock moto g with motorola rom 4.4.2 or even a moto g GPE 4.4.2 if you want to restore the firmware as long as they are 1032xt, i don´t know about other models, my moto G are from amazon USA unlocked global gsm xt1032 16gb, if you are on 4.3 please update to oficial motorola rom 4.4.2, then you can use this
2)you need to install motorola drivers, included MotorolaDeviceManager_2.4.5, connect the phone on and let windows setup drivers, then off, then in bootloader in order to install drivers, if you don´t know what bootloader is, then please get out (ok noobs, bootloader is when the phone is off, press power + vol down for 3 secs and release, that is the bootloader)
3)after drivers, connect the phone in bootloader screen
4)execute in the PC GPE_XT1032_KOT49H.M004_CFC
5)wait............there are some purple lines of text like warnings, ignore them, don´t worry it is normal, wait until the end, unplug and press normal powerup or reboot the phone
6)phone should start into android welcome screen
optional (root)
7)in welcome screen or any other time, plug the phone and copy supersu into phone memory, power off the phone
8)boot into bootloader again, go to recovery, flash supersu (install zip, choose zip from sd card, select supersu.zip, yes install supersu.zip, wait some......................., press any key, reboot system now), restart, download supersu from playstore, done, you are root
WARNING about OTAs updates
no matter what firmware you use, if you have custom recovery, do not update the phone via OTA, i repeat DO NOT UPDATE
flash a stock recovery, then update via OTA, else the phone will be in a boot loop
thanks
dashiell.cano, for discovering that way of flash
Phil3759, for custom recovery
alonsoch, for moto g tool
This isn't a rom, it is just a guide.
thelegendofzeth said:
This isn't a rom, it is just a guide.
Click to expand...
Click to collapse
i was uploading the files
will it work on xt1033?
dark ryder said:
will it work on xt1033?
Click to expand...
Click to collapse
Yes
Could you give a link to the fixed boot logo?
mrbloog said:
Could you give a link to the fixed boot logo?
Click to expand...
Click to collapse
download the entire file and get the logo from the zip
dark ryder said:
will it work on xt1033?
Click to expand...
Click to collapse
i have no idea but some dude said it will
added a little info on OP, corrected text mistakes
Hi I am running SlimRom but want too go to GPE will it delete my music + photos etc?
abell431 said:
Hi I am running SlimRom but want too go to GPE will it delete my music + photos etc?
Click to expand...
Click to collapse
yes, everything is deleted
ive tryed dozons of roms in the last couple of week & mobile date or gps has not works on all of them
but this rom works fine on my uk o2 xt1032 devise just fm radio was missing but added Spirit2 which works fine
thanks
scdsone said:
ive tryed dozons of roms in the last couple of week & mobile date or gps has not works on all of them
but this rom works fine on my uk o2 xt1032 devise just fm radio was missing but added Spirit2 which works fine
thanks
Click to expand...
Click to collapse
there is no radio on any GPE rom
maurocds said:
there is no radio on any GPE rom
Click to expand...
Click to collapse
is there a reason why they dont add it in any GPE rom?
Can you add a link for the stock recovery? Thanks!
please, is it based on 176.44.1 or older???
thanks
myabc said:
please, is it based on 176.44.1 or older???
thanks
Click to expand...
Click to collapse
GPE has only 1 version until now, this is not motorola rom, is GPE like nexus
Ballesss said:
Can you add a link for the stock recovery? Thanks!
Click to expand...
Click to collapse
look the forums, there are 3 custom recovery, i like philz
scdsone said:
is there a reason why they dont add it in any GPE rom?
Click to expand...
Click to collapse
because there are 1000 apps for it on the store, why bother, no ones uses that, listen to ads lol, no way
maurocds said:
look the forums, there are 3 custom recovery, i like philz
Click to expand...
Click to collapse
Yes, but you have said that we can't use the OTA's if we dont have a stock recovery. Where can i found it?
Ballesss said:
Yes, but you have said that we can't use the OTA's if we dont have a stock recovery. Where can i found it?
Click to expand...
Click to collapse
no one can be sure 100% about otas since the GPE has not had none
and sorry, i did not read well, i though you mean custom recoveries
if you want stock GPe or motorola recovery, then download a stock firmware and unzip the files, extract the recovery and you can replace the one i included
sorry, but it is something easy, i dont want to upload that, maybe later
just wanted to say that i updated my phone to 4.4.4 using this but with the stock gpe recovery (i am not sure if philz recovery works), will post on the main post
http://www.mediafire.com/download/hbyk97y9250cuus/recoveries.7z
included
stock 4.4.2 moto g GPe recovery, and latest philz recovery 6477
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
this is a great device but its pretty new. Will we be getting TWRP for it? Is there at least an unofficial version yet?
My understanding is it won't work on Android 10.
androiddiego said:
My understanding is it won't work on Android 10.
Click to expand...
Click to collapse
You are correct! Here is the official blog post I just found:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
This is super bogus and especially since this phone (at least mine) does not seem to have a stock recovery (I get a no command dead android). I think I am going to return this phone. Shame. It's pretty slick, but no way I am going to have one that has no viable recovery!
It sounds like they'll get there, just not quickly. If you read that link closely, this seems to apply to all phones shipped with android 10. So jumping to another phone is not necessarily a solution.
does anyone with a Moto G Stylus have a working stock recovery?
fronto said:
this is a great device but its pretty new. Will we be getting TWRP for it? Is there at least an unofficial version yet?
Click to expand...
Click to collapse
Did u unlock the bootloader
Sent from my moto g stylus using Tapatalk
When you go into recovery hit the + and - volume buttons together and it will pop up.
Yes their is recovery software. It's rescue mode.
fronto said:
You are correct! Here is the official blog post I just found:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
This is super bogus and especially since this phone (at least mine) does not seem to have a stock recovery (I get a no command dead android). I think I am going to return this phone. Shame. It's pretty slick, but no way I am going to have one that has no viable recovery!
Click to expand...
Click to collapse
https://motorola-global-portal.custhelp.com/app/mcp/service
twrp
why do you need a recovery when you can unlock the bootloader and use the factory recovery to flash what ever you want and they have a nice recovery option using the rescue and smart assistant software for pc mac or lin. i fail to see why you would want a custom recovery.
Has anyone tried flashing a system image yet, just rooted my Metro Stylus and wondering what's good to flash
DMedina559 said:
Has anyone tried flashing a system image yet, just rooted my Metro Stylus and wondering what's good to flash
Click to expand...
Click to collapse
How did you root? Are there instructions somewhere for Android 10 root?
cyrusalmighty said:
How did you root? Are there instructions somewhere for Android 10 root?
Click to expand...
Click to collapse
I unlocked my bootloader through Motorola then flashed a magisk patched boot.img through fastboot
DMedina559 said:
I unlocked my bootloader through Motorola then flashed a magisk patched boot.img through fastboot
Click to expand...
Click to collapse
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
cyrusalmighty said:
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
Click to expand...
Click to collapse
I haven't kept up with the android modding scene for years so I'm kinda out of the loop, but the general rule of thumb is to not do ota updates unless you're flashing full images with fastboot or using an OEM recovery software (Lenovo\Moto have one here)
As for the patch, I got the boot.img from the recovery software I linked above and installed magisk manager on my phone to patch the img which I then moved to my laptop to flash in fastboot
cyrusalmighty said:
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
Click to expand...
Click to collapse
Hi,
First download Rescue and Smart Assistant from Motorola website, make sure activate the developer options and usb debugging and download your phone's software with Rescue and Smart Assistant (it will find it automatically), find boot.img from inside the downloaded zip file and copy it to your phone, download Magisk Manager to your phone, and patch the boot.img with Magisk Manager, copy patched boot.img to your computer and flash it with adb.
If you have a desire to get TWRP, you should write to Telegram @mauronofrio and raise some donate to develop TWRP for this device.
Root Moto g stylus
fronto said:
does anyone with a Moto G Stylus have a working stock recovery?
Click to expand...
Click to collapse
My moto G stylus if it has an active recovery, when I buy it at 2 hours I unlock the bootloader and root with magisk, I put Xposed and BusyBox, the Xposed does not seem to work very well android 10, Aceves if and sometimes it turns off, buxybox is necessary reinstall again and again every time you turn the phone off and on, and Xposed works 60%, my Motorola G Stylus is from Metro
Luiszipatla said:
My moto G stylus if it has an active recovery, when I buy it at 2 hours I unlock the bootloader and root with magisk, I put Xposed and BusyBox, the Xposed does not seem to work very well android 10, Aceves if and sometimes it turns off, buxybox is necessary reinstall again and again every time you turn the phone off and on, and Xposed works 60%, my Motorola G Stylus is from Metro
Click to expand...
Click to collapse
Same issue, I've had the same provoking anger problem with this phone and previously a Moto e5 plus. It's rooted yet no Magisk module seems to work. This phone I can't even get lucky patcher to work. Android 10 sucks, I miss the good old days of Android 6 and 7.
Anyone else notice the modules not working at all but it's rooted?
Also to do a backup, adb backup and adb restore are your friends.
Rooted you can clone the device at least with adb commands. Slower but it's an exact copy at least.
Anyone with a rooted phone who could grab kernel logs after a fresh boot and post them here ?
vache said:
Anyone with a rooted phone who could grab kernel logs after a fresh boot and post them here ?
Click to expand...
Click to collapse
Going to flash the patched boot IMG once the firmware is done. Is there an app to catch the log or an adb command?