1. It had stock KitKat firmware (About said 4.4) - I unlocked bootloader and installed TWRP 3.3m1.
2. I had it backed up with TWRP but I tried various quark roms and none of them would get past the initial boot loading. I couldn't figure out why, I had erased data/system/dalvik/cache/etc, tried different kernels, tried erasing everything then installing rom, nothing worked.
Please help. Any help will be greatly appreciated! Thank you
Did you try with the official TWRP?
I'm not sure about the Moto Maxx, but with some other phones you would need specific bootloader versions that work with newer Android ROMs (e.g. install stock Android 6 for the XT1254 first).
Related
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.
Hello,
I have an XT1032 ('falcon') MotoG, purchased from Tesco in the UK. The bootloader was unlocked very soon after I bought it and I purchased an unlock code to allow it to be used on all UK networks. It works well. I think it was supplied with Android 4.3 Jellybean, and it was updated OTA to 4.4.4 KitKat.
I'm trying to install CM11 M6 (dated 4/5/2014) on the 'phone using CWM6.0.4.7. It appears to install fine, but goes to the bootloop, with the CM face in the middle and the rotating arrow running around it - and never progresses from there. This seems to be a common problem as there are a number of threads about it on this forum. It appears that the solution is to downgrade it to 4.3 by flashing it.
Following the instructions here:
http://www.nerdoholic.com/mobiles/restore-stock-firmware-motorola-moto-g/
... the opening instruction is "Download and install Motorola drivers" - which is where the problems start as it appears that the Motorola drivers are only available for Windows and Mac users, but not for Linux users, and I only have Ubuntu machines to play with.
So, where do I go from here? How can I downgrade to 4.3 with a Linux machine? I have tried the instructions, and they don't complete (although they seem to get most of the way there.)
Alternatively, is there any other way of installing CM11 on my 'phone without downgrading? There seem to be some people around who have made it work by installing CM11 twice (which didn't work for me), by wiping the 'phone and the Dalvik Cache (which also hasn't worked) or by using a different Recovery tool ('Philz Advanced CWM Tool' is mentioned occasionally, but I haven't tried it.)
All help welcomed, thanks. (For clarity, the 'phone is an original Moto G, 16GB. It's not the Moto G2, nor is it the 4G/LTE version that was released a little later.)
Oli.
A little more information - I have backed-up the working configuration of the 'phone with CWM and can restore from it fine. This is hence allowing me to tinker with all sort of other configurations and still get back to an operational 'phone - which is great! However I would be nervous about trying anything that would jeopardise this restore capability, which is one of the reasons why I haven't progressed with Philz Advanced CWM Tool.
Oli.
Linux requires no drivers. Fastboot tutorial here:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378http://forum.xda-developers.com/showthread.php?t=2542219
You cannot boot into 4.3 with your 4.4.4 bootloader. I suggest you flash the Retail UK 4.4.4 firmware image available here:
http://forum.xda-developers.com/showpost.php?p=54872143&postcount=362
Lost101,
Thanks - I suspected that it was the case that Ubuntu needed no drivers. Will the fact that I am trying to downgrade from 4.4.4 to 4.3 explain the fact that the flash didn't complete?
If so, and I try using the Retail UK 4.4.4 image then will it subsequently allow me to install CM11 (which is my final goal)?
Thanks again for your help.
Oli.
Personally I am more inclined to suspect the ROM itself and/or your custom recovery version is the problem.
Lost101,
Thanks again. Following the instructions in your first post (above) has successfully installed 4.4.4 from the Retail UK image. It boots and (appears) to work OK. However manually rebooting into fastboot and choosing 'Recovery' has highlighted the fact that CWM seems to have been lost and SuperSU is not in the Apps List - so it really does look like a very stock build (albeit the unlocked bootloader remains unlocked, as you'd expect).
I guess I therefore gain Root Access and re-install CWM and see where we go from there. Thanks again for your help.
Oli.
You have been using an early build of CWM. I recommend Philz Touch or TWRP.
To flash custom recovery in Fastboot:
fastboot flash recovery recovery-name.img
Hey, so i formatted the boot partition by accident today and could not boot anymore.
I was on a 5.1.1 Custom ROM before that. So i googled a bit and found a fix by flashing the Stock Firmware. Downloaded a 4.4.4 Stock Firmware here (RETAIL-DE) and flashed it using the commands here (as described in 3b). The second command failed with "Preflash validation failed". I believe thats because i had bootloader version 4.1.19 already and its not possible to flash an older one over that.
After that i could boot the phone again into the Stock Android 4.4.4. So i wanted to go back to an Lollipop or Marshmallow ROM. Using fastboot i flashed the latest TWRP Recovery and used it to flash a Custom ROM. I've tried several ROMs but every ROM results in an bootloop. Also tried using TWRP 2.6.0.0 and 2.7.0.0, but it didnt change sth.
I hope someone can help me solving this issue. Thanks.
You should probably full-flash the latest original Motorola firmware (GPE 5.1 or stock 5.0.2) before putting TWRP and custom roms based on Android L or M.
Hello all, my problem is that I've unlocked the bootloader and tried CF Auto Root but it just hangs - I've since read it isn't compatible with 5.1.
So how do I root the phone now? Do I actually need a custom recovery, or can I just root it? In the past I've flashed a file from the sdcard and the phone was instantly rooted, so have no experience with recoveries.
Some of the guides I've found are a couple of years old so may be outdated, and there's so many different ways I've been going round in circles.
I have Motorola Device Manager and Minimal ADB + Fastboot installed on a Windows 10 PC, 5.1 version is 23.26.3 peregrine.
Any help greatly appreciated!
Find a compatible recovery for your phone , flash the recovery via adb and then flash SuperSU zip through it .
Thankyou, is there a recommended custom recovery for the xt1039 (Is cwm or twrp better?)?
Is the correct version for xt1039 twrp-3.0.2-0-peregrine.img? Found here: twrp(dot)me/devices/motorolamotog2013lte(dot)html And follow the 'Fastboot Install Method (No Root Required)' instructions?
Will this still work if I'm on 5.1, or does it not matter what version I'm on?
Thankyou for any help, as I said I haven't installed custom recovery before so am a bit unsure.
I am having a problem installing customs ROM on stock LG G2. My phone was bricked so I reverted to stock AT&G firmware using LG flash tool (Android version - 4.4.2, Kernel version - 3.4.0).
I then perform the following steps:
(1) Enable developer mode with USB debugging
(2) Use Kingo Root to root phone
(3) Install TWRP using AutoRec
(4) Update TWRP to latest version (3.2.1)
This is where the problems start. I get the same result when I try installing crDroid 7.1.2 or Resurrection Remix 5.7.4 custom ROMs.
The installation of the custom ROM (and gapps) succeeds in TWRP and then I reboot the system. However, the reboot always results in the "LG" logo showing for 1/2 seconds and then a constant black screen.
I am able to recover the phone from this by putting it into firmware update and then using LG Flash tool however I would still like to successfully install and use the custom ROMs. Not sure why this is happening (I am sure it might have been treated with in the forums however I cant find anything). Any help would be appreciated here as I really do not want to be stuck on stock AT&T firmware.
Update
randyesh said:
I am having a problem installing customs ROM on stock LG G2. My phone was bricked so I reverted to stock AT&G firmware using LG flash tool (Android version - 4.4.2, Kernel version - 3.4.0).
I then perform the following steps:
(1) Enable developer mode with USB debugging
(2) Use Kingo Root to root phone
(3) Install TWRP using AutoRec
(4) Update TWRP to latest version (3.2.1)
This is where the problems start. I get the same result when I try installing crDroid 7.1.2 or Resurrection Remix 5.7.4 custom ROMs.
The installation of the custom ROM (and gapps) succeeds in TWRP and then I reboot the system. However, the reboot always results in the "LG" logo showing for 1/2 seconds and then a constant black screen.
I am able to recover the phone from this by putting it into firmware update and then using LG Flash tool however I would still like to successfully install and use the custom ROMs. Not sure why this is happening (I am sure it might have been treated with in the forums however I cant find anything). Any help would be appreciated here as I really do not want to be stuck on stock AT&T firmware.
Click to expand...
Click to collapse
Update: It seems as if older ROMs can be installed with no issues. I got a copy of Cyanogen 12 and it installed perfectly and works fine. However, trying to install new ROMs still give issues. Don't know if I am missing something here and/or someone had a similar previous experience.