Hi at all, some days ago i buy a used moto Maxx xt1250 with lollipop and the first 2 days it work very well. From yesterday appear a problem. After some time thet i don't use the moto Maxx it seem like frozen (slowly to turn on) and the touch doesen't work. I have to power off it (power + vol-) and wait to re-poweron the smartphone. Someone have already my problem?
Stefano2991 said:
Hi at all, some days ago i buy a used moto Maxx xt1250 with lollipop and the first 2 days it work very well. From yesterday appear a problem. After some time thet i don't use the moto Maxx it seem like frozen (slowly to turn on) and the touch doesen't work. I have to power off it (power + vol-) and wait to re-poweron the smartphone. Someone have already my problem?
Click to expand...
Click to collapse
Are you on stock Lollipop (5.0.2) or custom ROM? custom kernel? Are you undervolted? (problems like you are describing can happen from undervolting)
Are you rooted? do you have TWRP custom recovery?
There's variables which can cause what you are experiencing. One of the first things you can do is boot into recovery, clear all caches and let the apps optimize on bootup.
If you are on stock Lollipop and wish to remain there, you can re-flash factory image. There's threads here which have the XT1250 5.0.2 factory image. If in settings it says you are on 5.1.1, then you are not on stock Lollipop, you are on a custom Lollipop ROM.
If you are on custom ROM, you can re-flash that ROM, but for now do not flash a custom kernel. I like BHB27 kernel, but that introduces more variables while we are trying to trouble shoot a problem.
ChazzMatt said:
Are you on stock Lollipop (5.0.2) or custom ROM? custom kernel? Are you undervolted? (problems like you are describing can happen from undervolting)
Are you rooted? do you have TWRP custom recovery?
There's variables which can cause what you are experiencing. One of the first things you can do is boot into recovery, clear all caches and let the apps optimize on bootup.
If you are on stock Lollipop and wish to remain there, you can re-flash factory image. There's threads here which have the XT1250 5.0.2 factory image. If in settings it says you are on 5.1.1, then you are not on stock Lollipop, you are on a custom Lollipop ROM.
If you are on custom ROM, you can re-flash that ROM, but for now do not flash a custom kernel. I like BHB27 kernel, but that introduces more variables while we are trying to trouble shoot a problem.
Click to expand...
Click to collapse
I already tried to reset it to factory reset on recovery mode but the problem remain. I'm in stock Lollipop without root. I do not have anything special installed (whatsapp, telegram, nova launcher, and some minor app). This morning i see that the problem seems appear only when the smartphone is in my pocket but can be only a coincidence.
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.
I tried a cm12.1 rom which used to get flashed perfectly without any issues earlier. Then i encountered some problems with the ROM and i decided to flash the stock international kitkat rom(yes, i followed the correct procedure from the guide by @codelover). I didn't unlock the bootloader nor root it nor flashed a custom recovery.
For the past few day's i've been trying to install the same cm 12.1 rom and some new cm12.1 roms(updated versions, here is the link:https://userscloud.com/go/kgu385awbw9z/) but without any luck. After flashing either of the roms, the phone boots up fine till the stage where it shows the static honor logo(non-animated one) but after that it just shows a black screen and just stays there.
If i reflash stock B115, B108-signed 4.2.2 roms and B320 kitkat rom, it happens perfectly. But if i flash any other roms (after unlocking the bootloader and flashing custom recovery by following the guide), the black screen problem pops up(which didn't used to happen earlier). AGAIN i have tried the older cm12.1 ROM whose zip file has been stored on the sd card since that day without any modifications, so there's no chance of the ROM being tampered with.
I have tried hard resetting it by deleting emmc partitions and then reflashing the stock roms, but still the problem pertains after flashing the custom roms.
Does anyone know where i might be going wrong or what the problem is?
Hi guys,
Not sure if anyone else has had this issue, but I've only got a Moto G 4G fairly recently (my Nexus 5 died) and have been attempting ROM flashing (never had an issue with multiple Nexus phones & tablets) I was flashing the rom OK but the sim card wasn't recognised - so went back to rooted stock Kitkat & Xposed.
Today I thought I'd give it another go, got into TWRP, advanced wipe as usual...but it didn't complete and the phone suddenly booted back into the system (with the Android upgrading/optimizing message you usually get when starting a new phone)
System is untouched, still rooted/xposed etc. Does anyone have an idea why this has suddenly happened? Never encountered anything like this before. TWRP is the latest version 3.1.1.0
Any suggestions welcome, cheers.
Just thinking....would flashing with adb be a solution?
Just flash lollipop stock ROM using mfastboot
later you can flash twrp recovery and then proceed with the nougat or oreo based ROM.. Bootloader should be updated so my suggestion is flash lollipop stock ROM
I was using the RR ROM (don´t remember wich version) and someday the screen starts to froze often, I manage to go to TWRP and did the wipes and re-flash the ROM, but it got stucked in RR logo, until reboot to recovery. I tried to flash different ROM's, but no different results. So I flash the Stock ROM, the TWRP version that I found here in the forum, and it worked!! But then again I tried to install a custom ROM and it not load, I don't know what problem it could be. So if someone here have any ideas I really appreciate the help!
Hoy. Did you tried to flash a stock rom with RSD lite? I always fully re-flash after a custom ROM. But imo custom roms don't sit well with Moto Maxx, they drain battery super fast. Back when mine was new i could get like 4 days of battery in the OEM rom, just debloated. With 6.0.1 i get at least one day, but with a custom rom i'm lucky if i get near that now.