[Q] What are essential things I do before I root? - Moto G Q&A, Help & Troubleshooting

I (assumed) bricked my Moto G LTE today and just ordered another one. How it happened was that I factory reset my phone, but the setup stopped working after I finished it so I had no launcher. I naturally panicked and booted into recovery using ClockworkMod, but it didn't work. Eventually it got to the point where it was stuck at the Motorola "M" logo, so I continued to factory reset with ClockworkMod and installed a zip hoping a stock would fix it. It did not, since I misunderstood and now my phone is currently stuck at the warning bootloader screen (replaced by "Motorola powered by Android").
So I gave up and ordered the "Motorola Moto G - Universal 4G LTE - GSM Unlocked - 8GB (Black)" from Amazon.
To prevent something like that happening again what are some things I need to do to ensure I'll always have a safe recovery? I'm also overwhelmed by how many ways there are to root a Moto G LTE and could use some direction. I'm also confused on how I can find the appropriate stock ROM of 4.4.4 for my new XT1045.

Blkdrgn415 said:
I (assumed) bricked my Moto G LTE today and just ordered another one. How it happened was that I factory reset my phone, but the setup stopped working after I finished it so I had no launcher. I naturally panicked and booted into recovery using ClockworkMod, but it didn't work. Eventually it got to the point where it was stuck at the Motorola "M" logo, so I continued to factory reset with ClockworkMod and installed a zip hoping a stock would fix it. It did not, since I misunderstood and now my phone is currently stuck at the warning bootloader screen (replaced by "Motorola powered by Android").
So I gave up and ordered the "Motorola Moto G - Universal 4G LTE - GSM Unlocked - 8GB (Black)" from Amazon.
To prevent something like that happening again what are some things I need to do to ensure I'll always have a safe recovery? I'm also overwhelmed by how many ways there are to root a Moto G LTE and could use some direction. I'm also confused on how I can find the appropriate stock ROM of 4.4.4 for my new XT1045.
Click to expand...
Click to collapse
I am in no way an expert but here is my few cents :
0) make sure your bootloader is unlocked, see motorola website
1) Install TeamWin recovery latest version. For that just use adb to connect to your phone in debug mode and flash it, read up on that. Its easy process once you know it.
2) Hold vol down and power for a bit then release power, that goes into fastboot/bootloader, in which you press down then up to get into recovery.
3) erase everything from recovery, this should destroy your OS, to start at a clean slate.
4) make sure all your drivers are install on pc, for all modes that the phone can be in, so in the recovery now you should even see ur phone using adb devices
5) do a side load using adb of the rom your want to load, should take seconds
6) restart phone, rom should work, check it all out
7, if there is no root, then go back into recovery and install Super SU zip file, you can find.
Look at this guide: http://www.swedroid.se/forum/thread...nlock-recovery-root-guide-for-windows.106595/ it has all the tools you should need.
Oh, and don't panic, its very hard to really brick your phone.

Thanks for the help. Is it OK to use the guide even though it's intended for 4.4.2? What's the difference between CWM and TWRP, which one is better? In the scenario where I need to load the stock ROM because of corrupted recovery like before, how would I do that?

Blkdrgn415 said:
Thanks for the help. Is it OK to use the guide even though it's intended for 4.4.2? What's the difference between CWM and TWRP, which one is better? In the scenario where I need to load the stock ROM because of corrupted recovery like before, how would I do that?
Click to expand...
Click to collapse
For the Moto G hands down twrp
You can even flash IMG files after 2.8( if you even need to heh)

I just got my new phone today from Amazon. Apparently it's a XT1039 rather than my old XT1045. Is there a difference? I'm in the U.S. if that matters.
Edit: While following the guide @MuhammadA linked, I can't flash any recovery for some reason. When I try to flash them, my phone says "Mismatched partition size (recovery)" and when I try to launch "Recovery" it says "Boot up failed"
Edit: Found the problem. I don't know what it was, but I used a different version of CWM called "Unofficial CWM - 6.0.5.0 - peregrine" by Shabbypenguin and the OUDHS.
Edit again: The first thing I decided to do when I installed CWM was to backup my system, the first backup to my phone which went well and finished in a minute or so. When I started another one to my external SD card, it's stuck on "Generating MD5 checksums..." for about 20 minutes. Is it safe to force restart it via the power button?

Related

I've made a few extremely rash decisions, and I'm not sure if I can fix this.

Okay, this all happened because I tried to install CyanogenMod without taking into consideration the fact that I'm using the SV version, of which there does not seem to be any easy way to install CyanogenMod on.
My provider is Boost Mobile if that's important.
The first step I took was to unlock the bootloader, which was successful (I did use the HTCDev website, submit my identifier token, and it definitely worked).
The real trouble was when I tried flashing my recovery and boot .img's using the files in this link (for the HTC One S): ((I can't post links as a new user, but I tried acquiring my .img's from the CyanogenMod wiki, in the guide for the HTC One S, which was probably the root of this problem)
Terrible mistake, I know. I think my phone is bricked, but I'm not 100% sure because this is the first time I've tampered with any phone on this level. The only comparable mistake was when I accidentally formatted my hard drive when I tried installing Arch on my desktop, two years ago.
Right now, my phone won't start properly. When I do a normal bootup, by simply holding down the power button, I get treated to the HTC logo followed by a blank blackish-grey screen. I have to remove the battery to exit it. I can access fastboot, but when I attempt to access recovery I get taken to a perpetual load screen with an HTC logo and "Entering recovery mode..." on top of it. I have to remove my battery at this point because it never goes beyond that screen.
The other trouble is that while I seem to be able to access my phone through a USB cable, and apparently detect it using the "fastboot devices" command, the device itself doesn't seem to show up on Windows (as C525c, like it did before). I'm not sure if this has to do with me screwing up my boot and recovery .img's or my USB drivers.
Ok, this was not a good idea, to flash a boot.img from different device!
If there is any chance for your device, then try to flash the recovery from here (boost version).
old.splatterhand said:
Ok, this was not a good idea, to flash a boot.img from different device!
If there is any chance for your device, then try to flash the recovery from here (boost version).
Click to expand...
Click to collapse
Okay, I just did. I am finally able to boot into recovery! Thanks!
I'm not sure what I should do next though, because I don't want to screw it up again. Which options should I choose?
They are: Install, Wipe, Backup, Restore, Mount, Settings, Advanced, Reboot.
I'll guess you don't have a backup to restore?
Then you can try to restore some from here.
Or somebody gives you an backup from 4.2.2 boost version.
old.splatterhand said:
I'll guess you don't have a backup to restore?
Then you can try to restore some from here.
Or somebody gives you an backup from 4.2.2 boost version.
Click to expand...
Click to collapse
I'm unable to use any of the mega.co.nz links. I get taken to a loading screen, but it never actually starts downloading.
Try another browser.

[Q] Stuck on boot logo! literally tried everything

Okay guys, now I baught a moto g x1032 from ebay, gave it a try and It seemed laggy and buggy, went to settings and found that it was running a custom rom, so I wanted to go back to stock and I found a tutorial and I pretty much followed the tutorial, the tutorial said to download mfastboot, the firmware file, and adb fastboot as well as the drivers.
I did all of that, I installed the stock firmware and went to turn the phone on and it just shows the motorola logo then restarts.
I'm not sure what to do to get it working, I even downloaded another stock rom but it was in .zip format so I needed to transfer it to the phone and install it via cwm, I tried to install it via sideload but I kept getting the error on adb: error device not found.
I can still get into the fastboot menu by holding down the volume down + power.
I have also read that you apparantly need to have debug mode enabled, but how am I supposed to enable that when I can't get past the boot screen?
All i can think of is that maybe i was trying to downgrade the device when i shouldn't be?
If anyone can help me with this or point me in the right direction to fixing this phone back to stock that would be great.
Thank you.
What version of android did the phone come with? And what version did you try to flash?
I believe it came with 4.4 and I tried flashing 4.4 normal edition.
The phone now boots up but there is no sound or vibration or anything, tried making a call and the phone freezes, any ideas?
Which retail 4.4.4 are you needing? I can upload the UK version I use.
ramo55 said:
Okay guys, now I baught a moto g x1032 from ebay, gave it a try and It seemed laggy and buggy, went to settings and found that it was running a custom rom, so I wanted to go back to stock and I found a tutorial and I pretty much followed the tutorial, the tutorial said to download mfastboot, the firmware file, and adb fastboot as well as the drivers.
I did all of that, I installed the stock firmware and went to turn the phone on and it just shows the motorola logo then restarts.
I'm not sure what to do to get it working, I even downloaded another stock rom but it was in .zip format so I needed to transfer it to the phone and install it via cwm, I tried to install it via sideload but I kept getting the error on adb: error device not found.
I can still get into the fastboot menu by holding down the volume down + power.
I have also read that you apparantly need to have debug mode enabled, but how am I supposed to enable that when I can't get past the boot screen?
All i can think of is that maybe i was trying to downgrade the device when i shouldn't be?
If anyone can help me with this or point me in the right direction to fixing this phone back to stock that would be great.
Thank you.
Click to expand...
Click to collapse
You can flash one from here via recovery: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 then reboot.

[Q] My moto g doesn't work after flashing a mod

Dear reader,
Yesterday I rooted and unlocked my phone, but something went terribly wrong. When I tried to flash a rom, I thought it worked and i wanted to reboot my phone. Now it doesn't boot up anymore. I have a moto G first gen (xt1032). This is what my phone does when i try to boot it up:
It keeps saying the motorola warning message that my phone has been unlocked, it vibrates 1 short time (as normal when the moto g should boot up) but then doesn't do anything anymore. I can get into bootloader, but not in recovery. I tried to select Factory reset in the bootloader, but then I get the same as when I boot up my phone. When I connect my phone to my laptop my laptop plays the sound when you connect it to your computer, but I can't enter the files of my phone.
I think there might be no OS on my phone anymore, but I really don't know. I'm a noob in this, my first root was yesterday. Can someone please help me out?
Edit: I think I don't have a backup... I don't know for sure but did Titanium Backup made one on my phone itself? And I also tried to do this, but it didn't succeed: i tried to wipe everything via fastboot
May be you have flashed a wrong ROM.
Download the usb/adb driver fir your model and download adb(just do Google)
After connecting phone to computer, in the adb shell type the following
Adb devices
Reboot recovery
May be this helps you
Thank me if it helped you
If not reply me

[Q] Android noob Moto G bricked?

Hello, I've bricked my device (( moto g xt1032, I bought the device from Tesco back in 2013 and I just wanted to get the lollipop update on my phone, I looked online and found this video: watch?v=-L44JqysUy8 it didnt do as intended it rebooted and my device was ok, so I looked again and came accross a thread here on XDA: http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
first mistake I made was doing step 2.1 instead of going straight to 2.2, my phone rebooted and got stuck in a boot loop (i think, it was a black powered by android screen) I looked on google yet again and found an article that told to clear the cache in recovery I did that and it didnt work, boot loop again, then I found a forum post saying that having bluestacks on your machine will cause a conflict I uninstalled that and started from scratch with the same problem, I re did the steps seen in the above youtube video thinking that would put my device back to normal and still stuck in bootloop with the blue motorola m logo, I cant enter recovery of the fast boot menu anymore and my battery doesnt seem to be charging, its essentially a paperweight.
paulh2k8 said:
Hello, I've bricked my device (( moto g xt1032, I bought the device from Tesco back in 2013 and I just wanted to get the lollipop update on my phone, I looked online and found this video: watch?v=-L44JqysUy8 it didnt do as intended it rebooted and my device was ok, so I looked again and came accross a thread here on XDA: http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
first mistake I made was doing step 2.1 instead of going straight to 2.2, my phone rebooted and got stuck in a boot loop (i think, it was a black powered by android screen) I looked on google yet again and found an article that told to clear the cache in recovery I did that and it didnt work, boot loop again, then I found a forum post saying that having bluestacks on your machine will cause a conflict I uninstalled that and started from scratch with the same problem, I re did the steps seen in the above youtube video thinking that would put my device back to normal and still stuck in bootloop with the blue motorola m logo, I cant enter recovery of the fast boot menu anymore and my battery doesnt seem to be charging, its essentially a paperweight.
Click to expand...
Click to collapse
im now back to the boot loop thing not much better lol, is it fixable or should i just not bother
If it is booting up, then probably it is soft bricked. Not hard bricked.
If it can detect in ADB, re-flash the recovery?
Thankyou both for your replies, I dont know why I bothered back in the day symbian was so much easier lol, im an absolute noob when it comes to this so how would i go about getting to the recovery you mention, i can get to the fastboot menu but after selecting recovery the phone just loops at the boot logo
SInce it is bootlooping, I'm not sure which ROM is currently on your phone.
Try and flash the recovery from the ROM you tried to install by finding the recovery.img file, boot the phone into fastboot, and type "fastboot flash recovery recovery.img" or, if using mfastboot commands, type "mfastboot flash recovery recovery.img".
If you can't get into recovery, flash the recovery from your original ROM.
If you still can't get into recovery, flash your stock ROM, one partition at a time.
In fastboot, which bootloader version is on your phone?
the last thing I flashed was the link provided in the youtube vdeo if that helps, ive done the recovery thing and it still loops, my bootloader hmm im not sure heres the details from the fast boot screen..
AP Fastboot Flash Mode (S)
41.13 (sha-7dc8e78, 2014-06-16 16:33:29)
Device is locked Status Code (0)
is it because my bootloader is locked, I fail
You need to unlock your bootloader via the motorola website.
Thanks for your reply it turns out its not eligible for unlock for some reason so I'm deciding its a decent paper weight and giving up, I really appreciate the replies and the time the posters have taken out to help, I'll know to take my time to read every detail if I decide to do this again, thankyou!!
Are you sure it's not eligible? I thought my Telus xt1032 was not eligible but it turns out I mistyped a couple of numbers.
I tried a few hours later and I got the code from Motorola.
audit13 said:
Are you sure it's not eligible? I thought my Telus xt1032 was not eligible but it turns out I mistyped a couple of numbers.
I tried a few hours later and I got the code from Motorola.
Click to expand...
Click to collapse
I copied and pasted direct from the cmd, I read on another forum that you needed to be logged into the phone with the Motorola account which I didn't
I don't recall logging into the phone, I just recall logging into the Moto site with a google ID.
Don't worry bro just try and you will be successful. I'm also bricked my Micromax Canvas A1 on first try.
audit13 said:
I don't recall logging into the phone, I just recall logging into the Moto site with a google ID.
Click to expand...
Click to collapse
Thanks ill try it again
lol i need to wake up, I had spaces when iIcopied from the cmd its working now... and I have the code!!!
and im unlocked ! so what do i do know, i dont want to ruin it all now
Excellent. Boot into fastboot and post your bootloader version. It should be 41.xx.
41.13 ? thats on the second line in the boot menu
You have a KK bootloader. I suggest downloading the stock 4.4.4 ROM for your carrier and flash everything except the gpt and motoboot file. Once you finish flashing all partitions via fastboot, use the phone's volume button to boot into recovery, wipe perform a full wipe, and reboot.

Moto G (falcon) - Recovery img problem

Ok, I've been reading around the forum for about a week, trying to solve a problem with an original moto g (falcon). Basically my cousin got the moto g a few years back, and I, in my ignorance, tried to root the device for him. What I can remember was oem unlocking the bootloader with Motorola's unlock code through their website and adb. then my cousin freaked about the warranty warning on the boot animation, and decided against it. So cut to now, I'm a little more experienced, the phone's years old now, and he'd like to refresh it with a new rom, which I suggested, trying to help him. So forgetting what I'd originally done those years ago, I started the process of rooting the phone, installing a custom recovery, to hopefully put a lighter rom on it for him.
OK so it's a UK Retail on tesco mobile, moto g xt1032 running Android 5.1.
in bootloader menu it says "Device Locked status 2", dunno what this is in relation to.
first I checked the bootloader was still unlocked, and adb said it was. so I tried to use CF-autoroot to finish the job, but there was issues. it restarted the phone into fastboot mode, but when the script started, pc end did nothing, on the phone it said, "flashing unlock" and just sat there for 10-15mins doing nothing (i left it the time, just incase it was doing it).
So i read a little more, and found because i'd already unlocked the bootloader, I could just flash a custom recovery and root from adb? so I downloaded the latest twrp and tried. I was unable to do so. it said the partition wasn't the right size? should have documented it, but really didn't expect to run into any problems.
So I restarted and tried to do my usual fallback, and flash the factory image and start again, But couldn't find a source for the specific img, and tried to keep fighting on.
So I noticed that the phone wouldn't respond to adb or fastboot once in fastboot mode, when in android with usb debugging, no problems, in fastboot, didn't show up as adb devices?
I tried booting into the recovery from the bootloader menu, and got a no command. So there isn't a recovery, and I can't flash a new one? if i could find the stock recovery, I would try that.
so apart from deleting all his apps and settings, I hadn't solved the problem at all, and had to leave the job there as I couldn't find a solution.
I know this isn't the most detailed, but I've done this with quiet a few phones now, and felt I was pretty competent. I see everyday as an excuse to learn more, and like to think I have humility. So, I'm assuming I did something those years ago to damage the recovery? I'm running out of ideas, and was hoping someone could point me in the right direction?
I've lurked on xda for years, and learned so much about this kind of thing through my past experiences, but I'm stumped this time, and feel obliged to resolve the problem, as it was me who caused it.
TL DR
Can't flash recovery, no command when I try to open recovery, trying to either factory image back, or root/custom recovery it.
any insight would be much appreciated.
Hi. I just rooted and installed CM13 on an old XT1034 about two days ago. I am also sort of a ROM noob, I have ROMed a few devices, but usually but following strict step by step guides I have found here on XDA. Over the years I have some minor understanding of the process now.
I also got the "No command screen" when trying to get into TWRP recovery. The issue seems to be that if you reboot via ADB and the ROM launches it will automatically rewrite the recovery to the stock one, and when you try to go to recovery from fastboot, it gives you the "no command" error. Apparently you can get to the stock recovery from there by a hardware key combo, something like holding up vol for 10 sec then a quick press of power (I can't remeber the exact key sequence or what forum I read it in). If it does this you have to reflash TWRP again. This issue is mentioned here (http://wiki.cyanogenmod.org/w/Install_CM_for_falcon) in step 8 about installing recovery. What I ended up doing was after the flash of TWRP via ADB, I manually powered down, then manually bood into fastboot by holding volume down and power, and selecting recovery. This was a bit fiddly and I had to attempt it a few times but eventually it worked and TWRP installed.
The issue with the phone not being recognized may be due to incorrect drivers. I had no issue with this because I installed the official driver package from Motorola. It is available in their website in the developer section. I don't have the URL right now.
Hopefully this helps, for me CM13 Official has been an a stable fresh start for this old device.

Categories

Resources