INFO:
Model: SGH-M919
Kernel: 3.4.0-cyanogenmod-g93df44d [email protected] #1 Fri Jan 31 22:47:46 2014
ROM: CM 10.2.1-jfltetmo
Build #: cm_jfltetmo-userdebug 4.3.1 JLS36I 5ce70171d1 test-keys
Recovery: ClockworkMod 6.0.4.7
Basically, ever since I flashed AOKP a while back, my phone has been acting weird. Every once in a while the phone will freeze and black lines will appear, immediately followed by the phone re-booting. It happens completely at random. Afterwards, I flashed various ROM's and Android versions thinking that maybe the ROM was the issue, to no prevail.
Also, apps such as GoSMS, Instagram, PowerAmp, and my Camera, to name a few, bug out and either crash or freeze the phone and again it re-boots. The phone doesn't produce sound (from internal speakers or headphones, when plugged in). The Camera app will not record videos, or lag when record button is pressed, overall most of applications bug out and dont work the way they're suppose to.
My main concern is the random re-booting and what might be causing it, and what can do to fix it?
Thank You for the Help!
SlinerX said:
INFO:
Model: SGH-M919
Kernel: 3.4.0-cyanogenmod-g93df44d [email protected] #1 Fri Jan 31 22:47:46 2014
ROM: CM 10.2.1-jfltetmo
Build #: cm_jfltetmo-userdebug 4.3.1 JLS36I 5ce70171d1 test-keys
Recovery: ClockworkMod 6.0.4.7
Basically, ever since I flashed AOKP a while back, my phone has been acting weird. Every once in a while the phone will freeze and black lines will appear, immediately followed by the phone re-booting. It happens completely at random. Afterwards, I flashed various ROM's and Android versions thinking that maybe the ROM was the issue, to no prevail.
Also, apps such as GoSMS, Instagram, PowerAmp, and my Camera, to name a few, bug out and either crash or freeze the phone and again it re-boots. The phone doesn't produce sound (from internal speakers or headphones, when plugged in). The Camera app will not record videos, or lag when record button is pressed, overall most of applications bug out and dont work the way they're suppose to.
My main concern is the random re-booting and what might be causing it, and what can do to fix it?
Thank You for the Help!
Click to expand...
Click to collapse
Flash stock firmware via Odin to fix rom affected issiues.
LS.xD said:
Flash stock firmware via Odin to fix rom affected issiues.
Click to expand...
Click to collapse
I flashed the latest stock firmware, 4.4.2, via odin 3.09. The problems still stand, everything seems fine at first and then things start crashing and phone reboots. Any other thoughts on what might be causing it?
Don't worry about the rebooting my main concern are those black lines appearing I would flash to stock and claim warranty
Sent from my Nexus 5 using Tapatalk
markdapimp said:
Don't worry about the rebooting my main concern are those black lines appearing I would flash to stock and claim warranty
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I've already triggered the Knox Warranty Void
Hi all!
I bought a new Nexus 5 but I have the following problem: a luminous point in the top left, out of the screen.
Here is a picture of the problem in attached files.
Is this normal? or should I ask an exchange?
Thanks!
Looks like a stuck pixel. Sometimes they go away, sometimes they don't.
If it's always present, I'd exchange.
KJ said:
Looks like a stuck pixel. Sometimes they go away, sometimes they don't.
If it's always present, I'd exchange.
Click to expand...
Click to collapse
Stuck pixel? It isn't part of the screen lol
Then a pin hole in the black letting light through? I dunno. Either way I'd return it. Lol
Yeah, looks like the backlight or something is going through an imperfection in the hardware. Doesn't look too bad to me, but you might want to exchange it.
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)[/SIZE][/SIZE]
I contacted Google and they confirmed that it was a defective product. So they will send me a new one.
Thank you for your answers!
Okay. So we all know the d2vzw isn't perfect.
Right?
Mine recently has slowed to a grinding halt. Really nothing worked, the battery lasted maybe 30 minutes of usage (and maybe 10 hours standby), and the boot time was unbearable. So, I decided to try flashing and installing CyanogenMod 12, mainly because I have read that it breathes new life into the phone. But, alas, I am not cut out for this sort of gig alone, as I have discovered.
I come to you all today to ask for some help, or links to help. My recovery mode has been completely messed up, and I don't know what to do.
My questions are: 1. Can I still install a fresh OS, be it CyanogenMod, AOKP, or anything else? 2. How or why?
For more information, here is a timeline of what exactly I did to the phone.
-Bought the GS3
-Owned for ~1.5 years
-Updated to 4.4 KitKat
-Noticed battery life started sucking, as did speed
-Decided to root/flash/install
-Rooted using Towelroot V3
-Tried flashing ClockWork Mod via Odin, but Odin couldn't connect or something. No yellow box.
-Tried flashing CWM via terminal and rebooted into recovery
-Got the message "System Software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." when entering recovery mode
-Managed to get around that by quickly pressing the volume-up button a few times while booting
-Installed BusyBox
-Got a new Splash Screen that says "Samsung" then at the bottom an unlocked lock that says "Custom"
-Tried using Flashify to flash CWM
-Same error message when booting into recovery
-Tried flashing CWM Touch with Flashify
-Same issue
-Tried using SafeStrap
-Says "Install Successful" but the state still says "Not Installed"
-Tried using EZ-Recovery from Google Play Store
-Didn't work
And that's it so far. The phone works, however recovery mode does not, and I still have all the slow and battery problems.
I have no idea where to go from here.
If you have any more questions, just ask! If you have any suggestions, please let me know!
Thanks!
lordkennedy99 said:
Okay. So we all know the d2vzw isn't perfect.
Right?
Mine recently has slowed to a grinding halt. Really nothing worked, the battery lasted maybe 30 minutes of usage (and maybe 10 hours standby), and the boot time was unbearable. So, I decided to try flashing and installing CyanogenMod 12, mainly because I have read that it breathes new life into the phone. But, alas, I am not cut out for this sort of gig alone, as I have discovered.
I come to you all today to ask for some help, or links to help. My recovery mode has been completely messed up, and I don't know what to do.
My questions are: 1. Can I still install a fresh OS, be it CyanogenMod, AOKP, or anything else? 2. How or why?
For more information, here is a timeline of what exactly I did to the phone.
-Bought the GS3
-Owned for ~1.5 years
-Updated to 4.4 KitKat
-Noticed battery life started sucking, as did speed
-Decided to root/flash/install
-Rooted using Towelroot V3
-Tried flashing ClockWork Mod via Odin, but Odin couldn't connect or something. No yellow box.
-Tried flashing CWM via terminal and rebooted into recovery
-Got the message "System Software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." when entering recovery mode
-Managed to get around that by quickly pressing the volume-up button a few times while booting
-Installed BusyBox
-Got a new Splash Screen that says "Samsung" then at the bottom an unlocked lock that says "Custom"
-Tried using Flashify to flash CWM
-Same error message when booting into recovery
-Tried flashing CWM Touch with Flashify
-Same issue
-Tried using SafeStrap
-Says "Install Successful" but the state still says "Not Installed"
-Tried using EZ-Recovery from Google Play Store
-Didn't work
And that's it so far. The phone works, however recovery mode does not, and I still have all the slow and battery problems.
I have no idea where to go from here.
If you have any more questions, just ask! If you have any suggestions, please let me know!
Thanks!
Click to expand...
Click to collapse
Well I have bad news, your bootloader is locked if you took the OTA to Kitkat version 4.4.2 NE1. You can't flash custom roms or even a custom recovery (twrp, cwm, philz) your limited to safestrap as a recovery and approx 3 roms that are TW) touchwiz based)
Safestrap should work and your going to be on the lookout for roms in the development section that say BL(bootloader locked) if you have anymore questions feel free to post them
Sent from my Nexus 5
ShapesBlue said:
Well I have bad news, your bootloader is locked if you took the OTA to Kitkat version 4.4.2 NE1. You can't flash custom roms or even a custom recovery (twrp, cwm, philz) your limited to safestrap as a recovery and approx 3 roms that are TW) touchwiz based)
Safestrap should work and your going to be on the lookout for roms in the development section that say BL(bootloader locked) if you have anymore questions feel free to post them
Sent from my Nexus 5
Click to expand...
Click to collapse
That's what I feared. Thank you for letting me know! So, even though it's locked up, can I revert what I did? I still would like to send the phone into Verizon for some trade-in money when I upgrade.
Thanks again!
lordkennedy99 said:
That's what I feared. Thank you for letting me know! So, even though it's locked up, can I revert what I did? I still would like to send the phone into Verizon for some trade-in money when I upgrade.
Thanks again!
Click to expand...
Click to collapse
Yes you can. You can Odin back to that same version which should bring it back to stock kk with the 4.4.2 update
Sent from my Nexus 5
ShapesBlue said:
Yes you can. You can Odin back to that same version which should bring it back to stock kk with the 4.4.2 update
Sent from my Nexus 5
Click to expand...
Click to collapse
Okay, great! Do you know of a place to get the ROM and some instructions for flashing? Also, I couldn't get Odin to connect to my phone. Is there something I need to do before flashing to make it connect correctly?
Thanks!
lordkennedy99 said:
Okay, great! Do you know of a place to get the ROM and some instructions for flashing? Also, I couldn't get Odin to connect to my phone. Is there something I need to do before flashing to make it connect correctly?
Thanks!
Click to expand...
Click to collapse
I do but if it's not connecting to Odin that may be a problem. I've yet to see a device that won't connect to Odin
Sent from my Nexus 5
Q&A for [ROM][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
no calls or data
I have an xt1031 flashed to page plus. I have bootloader 41.19 from a failed lollipop update attempt. I flashed the 4/8 build and I can't make calls and do not have 3g. The network shows as 31000. What should I do?
I have been trying each of his builds and anything newer than 4/8 data hasnt worked I'm on boost if that makes any difference
Verizon?
Good morning,
I'm on an XT1028 still with service through Verizon Prepaid; my bootloader is unlocked and I'm on an optimized KK stock ROM at the moment. I've been following the development of Meticulus' CM12.1 through the primary thread and there has been a lot of discussion as to problem solving and issues on the XT1031 and various carriers but little mention as to the status of the latest weekly builds on the XT1028 still on Verizon in terms of functionality or hiccups from users. Does anyone have the latest versions running on their 1028? Are any of the data or service issues present when running it on Verizon?
Thanks.
Followup: Installed the latest 4/25 weekly on my XT1028 on Verizon Prepaid. Installed fine, got phone and SMS, but the network is identified as Boost Mobile and I have no mobile data. Is there a fix? Is a build.prop edit necessary for Verizon? Thanks.
Reboot then bootloop
Hi, I've been trying to get my installation of this ROM working for two days now, but keep running into an issue that I cannot seem to solve
My device is a 2013 Moto G XT1031 (Boost Mobile) with Bootloader version 41.05 and the latest CWM recovery.
The issue has been occurring on build 4/8, 4/25, and 5/2.
The exact steps I have been taking to install this ROM (for all builds) and then what happens:
Bootloader is unlocked
Going into recovery and wiping dalvik cache then factory reset (wipe)
Installing CM11 (latest snapshot) [on my first attempts only, not afterwards since it made no difference anymore]
Factory reset again (just to be certain)
Installing the zip for a build specified above
Installation always succeeds with no errors
Installing gapps-L-3-28-15 with success
Reboot into android
First boot always succeeds (and takes appropriate length of time)
Set up the phone (connect to wifi, google account, restore my apps [18 of them, just common popular ones, mostly Google actually], and apply a theme
Use it for a couple minutes (enable root and usb debug in Developer Settings, set my apps up, etc)
Restart two or three times without any hiccups
Suddenly, after a random reboot, the boot animation happens twice (instead of only once how it supposed to be)
Phone boots and shows "Android is starting..." and optimizes the apps (104 of them) one by one
Goes to "Starting apps..." and succeeds
The phone shows the lockscreen, but only for approximately 1-2 seconds
Phone reboots
CM boot animation runs twice, once for a long time then again for a shorter period of time
Phone goes through process described above (Android is starting, optimizes, then flashes lockscreen)
This just happens again and again and again
Steps I've taken to try and remedy the issue:
Run: "adb reboot" from computer while phone is optimizing apps
Hard reset the phone by holding the power button for 15 seconds
Run: "adb reboot bootloader" from computer when possible, then go into recovery and wipe both dalvik and normal cache
Swipe on the lockscreen as soon as I see it to see if I can get in (lockscreen does not respond though)
Go into recovery and shut the phone off, then start again
Let it loop for about 2 hours
I had also tried leaving the phone overnight looping, and when I woke, it was still looping, but after a eight or so more hours, I came back and found that it had booted and stayed on (and was working completely normally).
The phone was running stock 4.4.2 completely fine before this (with no reboot issues). I attempted installing the latest version of BlissPop, which exhibits a similar but still different issue (it would always boot into android [and not loop], but after a couple restarts, it showed an error about the System UI crashing that would pop up every time I dismissed it, and continued doing so after each restart after that). CM11 seems to be running well on the phone (but only in my very limited test while transitioning between ROMs and such).
I unfortunately cannot provide a log due to not being able to run any logging app during bootup, but hopefully I have provided enough details above to allow understanding of the issue and maybe bring suggestions on how to fix it. I can provide any more information needed on request. I really would like to get this phone back up and running (and especially on this ROM as I do love the work the creator has put into it).
Sorry for the very large wall of text :| Thank you in advance for any suggestions on how to proceed from here
tartilc said:
My device is a 2013 Moto G XT1031 (Boost Mobile) with Bootloader version 41.05 and the latest CWM recovery.
Click to expand...
Click to collapse
Having not experienced your issue I can't say for certain, but it may be possible you need to update the bootloader to at least 41.13, which is the 4.4.4 KitKat BL? I'd run it past @Meticulus and see if he might have some direction, there. Also, does the theme you apply have a different bootanimation, by any chance? There is a known issue/potential memory leak related to large boot animations on Lollipop that can cause failures at boot or bootloops.
a_gert said:
Having not experienced your issue I can't say for certain, but it may be possible you need to update the bootloader to at least 41.13, which is the 4.4.4 KitKat BL? I'd run it past @Meticulus and see if he might have some direction, there. Also, does the theme you apply have a different bootanimation, by any chance? There is a known issue/potential memory leak related to large boot animations on Lollipop that can cause failures at boot or bootloops.
Click to expand...
Click to collapse
Thank you for the advice I have downloaded a file with the name of falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip, unzipped it, then flashed according to the directions posted on how to restore the stock firmware. Everything during installation seemed to go smoothly, but at this point, I am stuck again. When I try to boot up, it just shows the splash screen ("Warning Bootloader Unlocked") and stays there indefinitely :| I have hard reset the phone and got into boootloader, which states that I am now on 41.13, but it just stays at that splash screen Should I boot into TWRP and try flashing an update.zip of the stock 4.4.4 Boost ROM? What else can I try?
EDIT: Flashing the stock update did not work, but I was able to install CM11 (so I'm am on bootloader 41.13 with CM11 currently)
EDIT TWO: Yes! I'm on bootloader 41.19 now and official CM12.1 nightly is booting!!
EDIT THREE: NOOOO It just started bootlooping again! CM animation twice, "Android is starting...", lockscreen, then cycle again. It happened after I changed my DPI from 320 to 280 (never restarted, just looped from then on).
I now have a logcat! I'm having trouble understanding what it is talking about, but I started logging as soon as the "Android is starting..." box changed status from "Optimizing apps x of x" to "Starting apps" and then stopped logging after a couple seconds of the boot animation. It is attached below (split into three parts).
EDIT: Attached what might be a better logcat reading (recording started right before lockscreen showed, I tried unlocking it, then stopped as soon as I saw the blue animation)
tartilc said:
Thank you for the advice I have downloaded a file with the name of falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip, unzipped it, then flashed according to the directions posted on how to restore the stock firmware. Everything during installation seemed to go smoothly, but at this point, I am stuck again. When I try to boot up, it just shows the splash screen ("Warning Bootloader Unlocked") and stays there indefinitely :| I have hard reset the phone and got into boootloader, which states that I am now on 41.13, but it just stays at that splash screen Should I boot into TWRP and try flashing an update.zip of the stock 4.4.4 Boost ROM? What else can I try?
EDIT: Flashing the stock update did not work, but I was able to install CM11 (so I'm am on bootloader 41.13 with CM11 currently)
EDIT TWO: Yes! I'm on bootloader 41.19 now and official CM12.1 nightly is booting!!
EDIT THREE: NOOOO It just started bootlooping again! CM animation twice, "Android is starting...", lockscreen, then cycle again. It happened after I changed my DPI from 320 to 280 (never restarted, just looped from then on).
Click to expand...
Click to collapse
Whoa, that's a lot of jumps! Be careful with the bootloader, as once you're on the Lollipop BL (and it appears you've already made that jump), you're kind of locked into LP ROMs from this point out. The point you were failing on the 4.4.4 stock would probably have been a good time to go in and manually restore things via fastboot just to make sure all your partitions were straight. What did you use to update your bootloader to 41.19? And have you tried a ROM specifically designated for the CDMA-only XT1031/Boost? I've only used the Meticulus and the unofficial Linaro CM12.1 buld by Cody on my XT1028 specifically because I know they're CDMA compatible, so I'm not sure where the official CM12.1 sits on that right now.
I know there exists an actual legitimate stock 5.0.2 Boost ROM and it's possible that may be able to be restored manually as a last resort, so don't move too hastily.
XPOSED on Meticulous Rom?
Is there any way to get XPOSED working? I really want gravity box for LL.
Awesome. I was going to download this from your site today but it is showing an error with connecting to its database. None of the computers i have access to can get on your site.
no wifi no cellular network
and after i flashed cynogenmod 12.0 in my moto g 2014, there is no wifi nor network :'( what am i suppose to do now?
Ui crash
Is there anything special i need to do to flash this update? i'm running on the 408 build and every time i try ti go the next version there is an issue. Either data stops working or i get a system Ui crash like on the 530 build. I would love to get this issue fixed with the 606 build. Besides that, great job.
a_gert said:
Whoa, that's a lot of jumps! Be careful with the bootloader, as once you're on the Lollipop BL (and it appears you've already made that jump), you're kind of locked into LP ROMs from this point out. The point you were failing on the 4.4.4 stock would probably have been a good time to go in and manually restore things via fastboot just to make sure all your partitions were straight. What did you use to update your bootloader to 41.19? And have you tried a ROM specifically designated for the CDMA-only XT1031/Boost? I've only used the Meticulus and the unofficial Linaro CM12.1 buld by Cody on my XT1028 specifically because I know they're CDMA compatible, so I'm not sure where the official CM12.1 sits on that right now.
I know there exists an actual legitimate stock 5.0.2 Boost ROM and it's possible that may be able to be restored manually as a last resort, so don't move too hastily.
Click to expand...
Click to collapse
Yeah that is a lot of jumps I'd be hella nervous myself lol
K well guys today is your day , as a_gert stated there is a boost 5.02 , and it does work fine on any cdma xt1031 so first flash that
-depending on signal you may wish to update your modem also there is only 4.4 modem for boost public
Buuuutttt nvm all that for now
The problem the ONLY problem I have had when bootlooping was that it was not prepped correctly and my phone came with 41.19 and came unlocked-
1.) Make sure you are on c/O SuperR-Developer -- PhilZ-Touch-6.59.0_LPK .img OR twrp * twrp-2.8.6.0.1-falcon_STOCK.img
**Notice For Even PhilZ I only Named the -IMG- Version which means flash it with adb properly please
***if ever after you flash it via recovery it will show partition mismatch which apparently is no problem just that the custom recovery does not match the factory one is all.. ..
1.) Download PhilZ-Touch-6.59.0-LPK.img to PC
2.) Reboot to bootloader
3.) Plug phone into PC
4.) Open terminal in directory where the img is located
5.) Issue the following command:
Code:
fastboot flash recovery twrp-2.8.6.0.1-falcon_STOCK.img
2.) Do a format of System w/EXT4 AND REBOOT INTO RECOVERY
3.) Format dalvik/art + Cache + Data w/EXT4 & REBOOT INTO RECOVERY
4.) Format Data PLUS data/media with f2fs then Do the 'factory wipe' then manually format data/media with f2fs again please ..
- SIDELOAD THE ATTACHED STOCK LOLLIPOP NO GAPPS GIVE IT TEN MINUTES REBOOT FEW TIMES/ POWER DOWN ONCE & REBOOT AGAIN
5.) Reboot into recovery and flash the first zip I have attached (I_nomodem is just IF you find your 4.4 radio baseband worked better and want to format it for LP again in the future WITHOUT LP radio included)
****EDIT - SEE VERY BOTTOM OF POST CENTERED AREA LOL
6.) Power off & reboot into recovery manually
7.) Flash your Rom (OR STOCK LOLLIPOP DEBLOATED AGAIN) + Kernel(if any custom one) + Gapps -wait 5-15 minutes for initial boot
* I recommend AeroKernel for the included stock lollipop 5.0 debloated if not the stock kernel or after flashing and few reboots to settle ,just follow instructions from that thread if any are needed..
Please anyone with any moto g don't think updating your bootloader is needed or even really safe whatsoever it is THE main reason moto phones get bricked or messed up otherwise it is not necessary or any kind of improvement yes once you are on an LP one leave it be..
Other flashing yeah okay, bootloader no if so proceed with utmost caution.
After this your modem will be updated with the cdma LolliPop one, if you have any signal issues or what not go to the stock modems section for your specific phone and flash the one for your specific carrier and/or find the "update RIL" flash thingie on here in moto G section and follow instructions but the boost modems work on all cdma variants of Moto G..
For whatever reason I could not upload files to xda I tried five times it kept dying so here there are on googldrive :good:
**Do not Click individual Item Use the Download Arrow At the Very Top of Page to DL the zip properly plz
1.) Falcon LolliPop Part Updater + Modem
2.) Falcon LolliPops Part Updater (No Modem)
_____________________________________________________________________________________________________________________________
--EDIT #2-- LolliPop 5.0 Falcon XT1031 debloated
SIDENOTE: IF YOU FORMAT DATA/MEDIA & DO NOT KNOW HOW TO SIDELOAD THE ABOVE STOCK DEBLOATED ZIP I'M PRETTY SURE YOU'RE NOT GONNA LIVE TO TELL BOUT IT
BE PREPARED TO SIDELOAD - REBOOT IMMEDIATELY AFTER SIDELOAD THE ZIP ROM IS COMPLETE NOT INTO RECOVERY NOT ANYWHERE ELSE SYSTEM REBOOT
-And wait 5-10 Minutes For First Boot - You Only Need to Do this for the first LP rom loadin after that normal flashing do NOT format data/media anymore after this initial setup
--You can try to just use the script, but it did not work for me after many tries the above was the real solution and has been perfect since
2,3,4,5,6,7
·Install flashable (Boost Mobile/CDMA XT1031 only):
·Download falcon_PhilZ-Touch-6.59.0_LPK.zip to phone
·Reboot into current custom recovery
·Flash zip
·Enjoy!
Use the script again to prepare you partition properly anytime you are about to flash a new rom clean after factory wipe/ format is done..
As I said before data/media is never necessary again after this and MAY not be this time but it is the only thing that kept me out of bootloops ,and if you do it yeah it will force you to sideload your rom it erases all leftovers and your rom zips off the internal card and formats them for fresh start The script does not format /media guys k no worries
------TWRP 2.8.6..1 does not seem to restore properly- -system write only thing .. PhilZ-Touch is fine as is twrp-2.8.6..0 also
Nice, got 41.19 BL!
I tested this and works fine, now i have my shiny new moto g running AICP. Thanks @shoobiedoobiiwhompwop!
rammsteinaus said:
I tested this and works fine, now i have my shiny new moto g running AICP. Thanks @shoobiedoobiiwhompwop!
Click to expand...
Click to collapse
K welcome
Arrite guys for a little clearer step by step see here please apologies carrying on and on I have been gone quite some time here http://forum.xda-developers.com/mot...-moto-g-xt1031-lollipop-t3132974#post61346260
It actually Runs really nice, really REALLY nice once the system app package I am adding shortly was used and tweaked out ..
Is it safe to flash cyanogenmod onto the verizon moto G - 1028 4.3 plus
Hello community ,
I had serious problems flashing cyanogenmod onto a galaxy S3 that was running stock 4.3 , verizon bricked my S3 , and said that the software was not authorized by Verizon. Does this problem exist across the board for any verizon phone running 4.3 or higher ?? If so ... then anything to do with flashing cyanogenmod onto a verizon phone should have warnings in BIG RED LETTERS ... because you cannot even buy a new phone with 4.2 on it anymore.
Issues flashing cm12.1 on XT1031 Please Help
Tried flashing the second to last release on 2 of my moto g xt1031's and I keep getting diff issues. This is what I did:
I had complete stock 4.4.4
unlocked bootloaders,
flashed latest TWRP,
Did a factory wipe
Flashed CM12.1
Flashed Gapps
Rebooted
Stuck in boot loop--> waited over 30mins and rebooted a few times. No luck.
I heard to try flashing CM11 first, then flashing 12.1 so I did this:
Back to TWRP -->factory wipe
Flash cm11
reboot to cm11
reboot to TWRP -->factory wipe
Flash CM12.1
Now I can get past the boot logo and begin setup, however, it will randomly reboot to the boot logo and then back to setup after a minute or so- erasing anything I've already input. Sometimes I could make it through the setup to the desktop, but then it would do the same thing. Had this same exact issue on both of my xt1031s with the same process used for both.
After this I tried doing a factory wipe and then also wiping /data and /system in the advanced wipe options and then flashing cm12.1 and still had the same issue of the rebooting. At some point I must have done somthing, but I started trying to just flash cm12.1 several times over to see if it would stick and I noticed when I did the factory wipe I was getting a parsing error so I tried doing a full data format, and fix data filesystem. I'm not sure what format it was supposed to be so I did a ex4. THat stopped the parsing error, but still having the same issues.. any help would be appreciated.
Moto G CDMA issues
citizen3rased said:
Tried flashing the second to last release on 2 of my moto g xt1031's and I keep getting diff issues. This is what I did:
I had complete stock 4.4.4
unlocked bootloaders,
flashed latest TWRP,
Did a factory wipe
Flashed CM12.1
Flashed Gapps
Rebooted
Stuck in boot loop--> waited over 30mins and rebooted a few times. No luck.
I heard to try flashing CM11 first, then flashing 12.1 so I did this:
Back to TWRP -->factory wipe
Flash cm11
reboot to cm11
reboot to TWRP -->factory wipe
Flash CM12.1
Now I can get past the boot logo and begin setup, however, it will randomly reboot to the boot logo and then back to setup after a minute or so- erasing anything I've already input. Sometimes I could make it through the setup to the desktop, but then it would do the same thing. Had this same exact issue on both of my xt1031s with the same process used for both.
After this I tried doing a factory wipe and then also wiping /data and /system in the advanced wipe options and then flashing cm12.1 and still had the same issue of the rebooting. At some point I must have done somthing, but I started trying to just flash cm12.1 several times over to see if it would stick and I noticed when I did the factory wipe I was getting a parsing error so I tried doing a full data format, and fix data filesystem. I'm not sure what format it was supposed to be so I did a ex4. THat stopped the parsing error, but still having the same issues.. any help would be appreciated.
Click to expand...
Click to collapse
Hello Citizen 3 , You are farther along than me. I have only successfully flashed cyanogenmod once , and that was on an S3 so it was straightforward. I still have not unlocked my bootloader. I have not been able to copy and paste the long strings of characters from motorola , inside command prompt. It would be so nice if Meticulus or one of the other developers could get this to be an official release. The Moto G , and a few other inexpensive phones ( LG realm , Kyocera Hydro latest version ) would work like greased lightning , if they were running CM12. Any help that you could offer with pasting the strings of unlock code would be so appreciated.