Hello,
I keep trying to update to the latest nightly to get cyanogenmod 12 on XT1302. However they don't work. I get weird scan lines, even during the boot logo and animation. Everything is slow and unstable. During installation it always says root access possibly lost, fix, yes or no. Thankfully I have a working backup, but it's stuck on an old 2014 cm 11 snapshot and I want to upgrade
I suspect there is a problem with gapps since I get incessant "X app has stopped working error" messages and it's always a google service. However I do not know what the procedure is. I downloaded the cm12 gapps and flashed them after flashing the nightly as said in faq but it doesn't seem to work. Sometimes even Trebuchet stops working, making the phone totally unusable.
Any help would be greatly appreciated. :good:
Are you running with a lollipop bootloader? I think the latest CM12 requires it.
audit13 said:
Are you running with a lollipop bootloader? I think the latest CM12 requires it.
Click to expand...
Click to collapse
I've been googling this and I think you have correctly identified the issue. If I install the lollipop bootloader, will I be able to go back to my cm11 backup in case of an emergency?
Just to confirm, to update the bootloader, you have to flash the brazil lollipop rom and it should work?
If you unzip the stock ROM, the bootloader is the motoboot.img file.
I don't think you need to flash everything, just the bootloader file. If that doesn't allow you to use CM12, you may have to restore your CM11 nandroid and then flash CM12.
Related
Hi
Just moved onto the Moto G from a couple of Huawei devices, G300 then Y300... (bye bye Modaco!) - So I'm pretty used to flashig, wiping etc using TWRP and CWM...
Anyhow, got the Moto G (XT1033), booloader unlocked, done a full restore to clean 4.2 and let it update to 4.4 fine, no problems.
Installed the latest CWM, got root, all fine... again, no problems...
But EVERY rom I try - slim, CM11, always install OK but on booting come up with phone process failures and I have to abandon.
I tried putting the 422 modem zip from the CM11 thread on, made no difference.
So I've rewiped back to stock and updated to 4.4.2, and flashed CWM, but still can't install a custom rom, getting the phone process error on startup.
Any suggestions?
Resolved myself! Revert to factory, install CWM and flash new roms without doing the ota to kitkat first.
TangerineTractor said:
Resolved myself! Revert to factory, install CWM and flash new roms without doing the ota to kitkat first.
Click to expand...
Click to collapse
So you installed CM11 from stock jelly bean??
Sent from my XT1032 using Tapatalk
xheon said:
So you installed CM11 from stock jelly bean??
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Yes. Originally I let it run through the ota update, then installed CWM and tried to install various roms. All gave me a FC on outdoor process as soon as I booted.
tried again with TWRP, same thing. third time lucky, I restored to factory, let it boot but didn't do the ota update, installed CWM for 4.3 bootloader, and all has been find since, flashed several roms with no problems.
So you have a dual SIM version and you flashed a custom ROM which means only one SIM works now. Am I right? How is everything else, no issues with performance just because yours is a dual SIM variant?
Ok, this is weird, a while ago i didnt had any problems installing any kind of custom rom, used CWM while wiping everything... eveything was OK, ROM worked OK, etc... But one time i installed a ROM (Slimkat) and i lost signal, tried to use my recovery of stock android but it didnt work, so i tried a lot of things untill i got bootlop without being able to install anything since some files were missing, bad luck
After that, i just reflash stock 4.3 and upgrade from there 4.4.2, everything fine again... except that i cant install any kind of ROM, every ROM says "installation succesful" but everyone is stuck into bootloop.
While i havent tried ALL ROMS i have tried the same ones i was using (Nexus G+, LiquidSmooth and CM11), so i guess this problem is coming from my device.
On a side note, i tried to factory reset, but no luck... it shows the Android working but it inmediately turns the screen off, and then it shows it again and then off again... in an infinite loop
Same problem!
Bump.
I just got my Moto G yesterday (European XT1032), updated to 4.4.2, unlocked bootloader, rooted with superboot and flashed Philz Touch CWM.
Seems I have done everything by the book, wipes included, but no luck. I tried Slimkat, Paranoid and Codename Lungo (latest builds as of 3/12).
Liberr said:
Bump.
I just got my Moto G yesterday (European XT1032), updated to 4.4.2, unlocked bootloader, rooted with superboot and flashed Philz Touch CWM.
Seems I have done everything by the book, wipes included, but no luck. I tried Slimkat, Paranoid and Codename Lungo (latest builds as of 3/12).
Click to expand...
Click to collapse
Hmmm... Pay attention to which version of Bootloader you are using.
You might want to try both 4.3 and 4.4 to see which one would work.
Extract the motoboot.img from the stock .zip image for your phone, then flash with mflashboot flash motoboot motoboot.img
Good luck!
neozen21 said:
Extract the motoboot.img from the stock .zip image for your phone, then flash with mflashboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Thanks. I'll give that a try. Is there a way to check bootloader version on the phone? If that doesn't work out I'll start from scratch and report back in this thread..
Liberr said:
Thanks. I'll give that a try. Is there a way to check bootloader version on the phone? If that doesn't work out I'll start from scratch and report back in this thread..
Click to expand...
Click to collapse
Hmmm.. I see there is a version number on mine, 41.05 dated 2013-12-06, but I'm not sure if that's the version or not.
And yeah... if changing the bootloader doesn't help, you probably would have to restore from the stock image and start over..
Got root and custom roms working after I 1.) downgraded to 4.3 and 2.) flash TWRP (instead of CWM).
So I'm not sure what the problem was. Besides the two main rooting methods (superboot and custom recovery), there are some other methods described on the forum specifically for people who already did a international variant OTA to 4.4.2. and one that is absolete (here) but apparently works for some when the two main methods fail.
However I'm still not sure if this solved everything. I am not sure if I can flash Cyanogenmod (which is 4.4.2) over a 4.3 firmware. Maybe I need to manually flash a 4.4.2 radio or something... Gonna check that out next...
EDIT: No need to downgrade. Not sure how it works but two main root methods (superboot and custom recovery) didn't work for me. Somehow I got stuck in boot animation. Just installed TWRP instead of CWM after Kitkat firmware (EU Retail) and rooted (/installed Super Su) from there. Everything works fine now.
So I have been reading but still confused. I am running validus 5.2 on my maxx HD. I am assuming I have a jb bootlaoder. I have philz touch 6.48.xx on my phone. I have tried to install validus 6 on my phone but I keep getting a status 7 error on my phone and it will not flash. I am thinking maybe I need to go back to stock and update to kk. Maybe I am wrong, I don't know. I am confused a bit on what I should do to flash to the new kk update on the custom ROMs. Any input is appreciated!
Update, I have searched and tried other methods to get rid of the status 7 error. I have unzipped and deleted the assert, get prop lines. I was able to flash validus 6 but unfortunately, it just sits on boot image. Any other ideas I can try?
dolfns99 said:
Update, I have searched and tried other methods to get rid of the status 7 error. I have unzipped and deleted the assert, get prop lines. I was able to flash validus 6 but unfortunately, it just sits on boot image. Any other ideas I can try?
Click to expand...
Click to collapse
if you have a xt926 you can follow this link to guide you to KK and you can install new roms afterwards.
I appreciate the help. I so want to make sure I understand, I am already rooted and unlocked, running validus 5.2 on my phone. So I still need to flash back, reroot, reunlock and upgrade to KK before trying to flash a KK custom ROM? is: CM11, validus 6?
Well after reading the other post numerous times, I think I will just start from scratch!!! Happy flashing to me. Its been a good year since using rsd but I'm sure I can follow directions!
so i flashed the lolli img from google and all was fine. wanted to install a custom rom so i flashed the latest twrp and then cataclysm. all seemed well but when i turned off wifi i just get the no service error, its on LTE and seems correct. then i tried to go back into recovery and it just reboots. i had slimlp rom on there and the same thing happened with the recovery problem.
any help? just want to keep the recovery working and get the cell radio all fixed with cataclysm
People with TWRP 2.8.2.0.might need to.downgrade to 2.8.1.0.
The latest version hangs at the curtain if it has MTP enabled.
Hi,
I wonder if anyone could offer me a little assistance please ? I have a UK Tesco Moto G 16GB (2013) that I have successfully unlocked the bootloader and rooted and CWM recovery installed. Currently, it's running 4.4.4 Kitkat. I gave up with the OTA update as I was getting the 'preflash validation failed' message. More recently, I have tried following the guide on here to flash the XT1032_GPE_5.1_Optimized_v1.1.zip file using CWM. However, this resulted in what I believe is termed a bootloop - i.e. the coloured dots animation just never stopped - I waited half an hour and it was still going.
I've managed to restore it back to my previous 4.4.4 for the moment, but I would like to move to Lollipop at some point - if I could !
Could someone suggest a method I could try please ?
Many thanks !
Kev.
Hi there.
Well, my device is a XT1032 Retail US but I may have been through the problems you're facing right now.
Here we go:
Go full stock (don't know if you revocer from a backup or already did this but in any case you'd know what to do: This guide helped me a lot. http://forum.xda-developers.com/showthread.php?t=2542219.
Do not install any official update using a custom recovery
Make sure you got the actual latest recovery version. If you went stock from the latest firmware you should have already got it.
If you have your OTA, Install it manually from the stock recovery
This method should work. It is the one I followed.
I got two errors: 1st was because was using custom recovery.
2nd was because my rom was stock but had deleted system apps, so the install failed always at some point.
Once I flashed the latest stock firmware including the stock recovery, I was able to install my OTA update.
Let me know if this works.