I attempted to root the moto G, but the instructions were unclear and I think I flashed the stock firmware incorrectly. So now the WI-FI won't turn on and my device still isn't rooted. Can somebody walk me through the process of fixing this please? Thanks in advance.
Related
Greetings y'all.
I'm rocking a Moto X from the Canadian carrier Rogers and I'm currently running on Android 4.2, with the well... what was latest version for the Moto X, the update that included the camera fixes. I originally rooted my Moto X with the first root method that became available and then recently I used the new RockMyMoto method and I've experienced a peculiar issue and I was hoping someone would be able to offer me some advice.
After rooting my device with RockMyMoto my device had root working perfectly! The applications that rely on root were working perfectly and then one day... something happened. AdAway failed to install the updated host file, so I went into AdAway and it gave me a warning that said root was required.
I found this to be odd... so I exited the application and tried again. The same dialog came up with the same message. I decided to clear the application data and remove AdAway from SuperSU and then reinstalled the application. The problem persisted. I then rebooted my device and tried again and all of a sudden it worked. Now it appears my device is getting intermittent root?
When I turn my phone on I get a notification from Koush's Superuser (I switched from SuperSU, this might be the issue, at least I thought it might be until I switched back to SuperSU) saying that the binary was outdated and I needed an update, so I updated it and it was working so then I decided to try AdAway and... it worked! Success! or so I thought... a few minutes later I tried again and that same dialog came up.
Herumph! I proclaimed. What is this sorcery? Well... it seems my Moto X is getting an intermittent root or something that's only available once the system starts up again.
I tried running RockMyMoto again but that didn't seem to work, mind you I didn't unroot and then reroot.
My question for you is, well... how can I fix this? I don't want to restore my device to stock Android and I also don't want to do some sort of complex trickery because I'm expecting a 4.4 update sometime soon. Anyways, give me a hand guys!
You may not have root after 4.4 anyway... Some say.
Sent from my Moto X cell phone telephone...
Turbocom said:
Greetings y'all.
I'm rocking a Moto X from the Canadian carrier Rogers and I'm currently running on Android 4.2, with the well... what was latest version for the Moto X, the update that included the camera fixes. I originally rooted my Moto X with the first root method that became available and then recently I used the new RockMyMoto method and I've experienced a peculiar issue and I was hoping someone would be able to offer me some advice.
After rooting my device with RockMyMoto my device had root working perfectly! The applications that rely on root were working perfectly and then one day... something happened. AdAway failed to install the updated host file, so I went into AdAway and it gave me a warning that said root was required.
I found this to be odd... so I exited the application and tried again. The same dialog came up with the same message. I decided to clear the application data and remove AdAway from SuperSU and then reinstalled the application. The problem persisted. I then rebooted my device and tried again and all of a sudden it worked. Now it appears my device is getting intermittent root?
When I turn my phone on I get a notification from Koush's Superuser (I switched from SuperSU, this might be the issue, at least I thought it might be until I switched back to SuperSU) saying that the binary was outdated and I needed an update, so I updated it and it was working so then I decided to try AdAway and... it worked! Success! or so I thought... a few minutes later I tried again and that same dialog came up.
Herumph! I proclaimed. What is this sorcery? Well... it seems my Moto X is getting an intermittent root or something that's only available once the system starts up again.
I tried running RockMyMoto again but that didn't seem to work, mind you I didn't unroot and then reroot.
My question for you is, well... how can I fix this? I don't want to restore my device to stock Android and I also don't want to do some sort of complex trickery because I'm expecting a 4.4 update sometime soon. Anyways, give me a hand guys!
Click to expand...
Click to collapse
I presume you're making changes/updates to SuperSU booting into recovery? I'm not sure, but I know I had some problems, lost root briefly when I updated but wasn't in recovery.
Issue resolved! I wasn't applying the update in recovery. Silly me!
The annoyance I saw was I had to reboot into "recovery" to make it have R/W status. That only lasts until the next reboot.
I ran the new pwnnomo or however its spelt, and don't have to worry about that anymore. And also now have safestrap
Sent from my XT1049 using Tapatalk
It is a Rogers Moto X so you can always make life simple and simply unlock the bootloader, no stopping you from enjoying root then even with the 4.4.x update.
Steve-x said:
It is a Rogers Moto X so you can always make life simple and simply unlock the bootloader, no stopping you from enjoying root then even with the 4.4.x update.
Click to expand...
Click to collapse
Are you using 4.4?
Just picked up this phone yesterday. It was a Galaxy S4 Active from AT&T model i537 build number UCUCNH3 running 4.42. I wanted to root it so I scoured the internet and came upon this thread:
http://forum.xda-developers.com/showthread.php?t=2629093
which explained how I needed to flash the NE3 kernel in order to exploit the root and then I could flash NH3 back (although I did not realize this last part until later )
I rooted my phone which was successful. Then I loaded safestrap which was also successful and I attempted to load some roms that I had heard some had limited success with. I did not have success with the ROMs but I also didn't brick my phone so no harm no foul. However, I after doing a factory reset I realized my Wi-Fi is not working. It will work right after a factory reset briefly but then it just kind of disappears and the Wi-Fi screen will perpetually say it is turning on.
I tried turning back the clock by getting rid of safestrap and re-flashing the NH3 kernel and doing many more factory resets (both through recovery mode and from system) but no luck
TLR; Please Help me get my Wi-Fi back!
Let me know if you found a solution.
I have a similar problem. My i537 Wifi configuration is not remembered by NH3 and after a few reboots, it will fail to turn on completely.
So I didn't read any guides and was following an old YouTube video on how to go back to stock and OTA. Unfortunately the link was for an older version of the Moto X Toolkit and it took me back to 4.2.2 and I accepted the OTA. gg.
I have tried flashing 4.4.4, 4.4.2, 4.2.2 again from fastboot and in the end the result is the same: a flashing dead android popping up every few seconds that says error. After reading the Q/A I think this is a hard brick but has there been any updates on ways to fix this?
I can't USB mount to put in a custom rom either and it won't let me sideload since the USB mounting isn't working. I can flash custom recoveries but that's about it.
Thanks.
Not researching first on any device is a mistake for sure... Especially the X. You've done the procedure that guarantees bricking a Moto X unfortunately.
This thread may be your only hope now...
http://forum.xda-developers.com/showthread.php?t=2629057
Good luck!
I looked into this method but couldn't get it to work since it wasn't recognizing the phone when I plugged it in. I did manage to unbrick it somehow by flashing a 4.2.2 version again using the toolkit (post camera I believe). I managed to boot up again in 4.2.2 but not really sure how to upgrade to 4.4.4 at this point without bricking again.
Is it safe to RSDlite to 4.4.4 using the right carrier?
edit:
nevermind... I turned the phone off to check the status of the bootloader and saw it was unlocked, did a normal power up. For some reason it said android is updating even though I didn't do any updates and it randomly turned off and now it's completely dead .
So just to summarize what I've done so far, I have a Moto G (2014) which has been updated to Lollipop through normal means. I started off following this guide: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818/page12
The guide then lead me to this one, as my model is XT1064, a Moto G from Windmobile. I had no issues unlocking my bootloader. http://forum.xda-developers.com/moto-g-2014/development/xt1064-lollipop-root-t2938051
With the guide above, after I flashed that file, my wifi would not turn on. Every time I pressed the toggle, it would immediately switch back to off. I then flashed the TWRP Recovery, and used that to finally root my device with SuperSU.
I checked my root, and my device is confirmed to be rooted, but the wifi is still not working. I looked around a little, and found this: http://forum.xda-developers.com/moto-g-2014/general/guide-lollipop-xt1064-north-edition-t2955076
The problem with the guide above is that its for a phone that was kitkat, while my phone is already lollipop. The guide does mention the wireless issue though, so I was thinking of trying out the steps outlined in that guide, also using that file (though that file is for 4.4).
Would this work? Or is the safer bet finding an 5.0.1 stock rom, and flashing back to that?
Edit: I found a link to a 5.0.2 stock rom (which is the version my phone currently is) I think downloading that and using that to fix the modem files is the better thing to do. (link: http://www.filefactory.com/file/53c1pepzp9cp/RETCA_XT1064_5.0.2_LXB22.99-24.2_cid14_CFC.xml.zip)
Thanks for all and any help.
I recommend flashing the stock images, that will almost certainly fix your issue with Wifi.
The lollipop upgrade caused my 2013 Moto X frequent crashes and the BT stack is broken. So I decided to downgrade. I found this walkthrough: https://www.youtube.com/watch?v=SRV2qoQX-P4
and followed it. It wasn't until I was done that I found it was for Moto G not X. The phone starts, but is obviously in a corrupted state - wifi doesn't work, etc...
What is my best/easiest course of action to downgrading to Moto X's image of Kit Kat?
Thanks!
Use this guide:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Thank you. I was able to unlock bootloader, root and install CM11. However, something major is screwed up in my phone as a result of the incorrect as the Wifi and BT don't work (don't turn on).
Also, as soon as I try to open security in setting, it crashes. Is there a way to do a deeper recovery/reinstall?
Thanks!
Andy T11 said:
Thank you. I was able to unlock bootloader, root and install CM11. However, something major is screwed up in my phone as a result of the incorrect as the Wifi and BT don't work (don't turn on).
Also, as soon as I try to open security in setting, it crashes. Is there a way to do a deeper recovery/reinstall?
Thanks!
Click to expand...
Click to collapse
Try installing CM12.1 and wipe the '/system' partition in the process before flashing CM12.1.
If that doesn't fix WiFi and Bluetooth then try this:
http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
Andy T11 said:
Thank you. I was able to unlock bootloader, root and install CM11. However, something major is screwed up in my phone as a result of the incorrect as the Wifi and BT don't work (don't turn on).
Also, as soon as I try to open security in setting, it crashes. Is there a way to do a deeper recovery/reinstall?
Thanks!
Click to expand...
Click to collapse
If you followed the guide you were linked to, it used fastboot to reflash all the partition on your phone... This means your rewriting basically all the phones software. If it is not working after that
a.) The software is bad
b.) The user is bad
OR
c.) The hardware is bad.
Read all the output of the commands you enter, make sure there are no errors, and verify you have the correct software.
scryan said:
If you followed the guide you were linked to, it used fastboot to reflash all the partition on your phone... This means your rewriting basically all the phones software. If it is not working after that
a.) The software is bad
b.) The user is bad
OR
c.) The hardware is bad.
Read all the output of the commands you enter, make sure there are no errors, and verify you have the correct software.
Click to expand...
Click to collapse
The '/persist' partition never gets written upon.
And it stopped working after he flashed the Moto G firmware.
So it's obvious that the software that is bad.
What XT is this phone and is it locked into a carrier?
Did you re flash back the stock radios for the X? Flashing CM on your device does not include the radios. Having the wrong radios will cause you to have problems. If you flashed the radios for the moto g you will need to flash the ones back for the moto x.
Travisdroidx2 said:
Did you re flash back the stock radios for the X? Flashing CM on your device does not include the radios. Having the wrong radios will cause you to have problems. If you flashed the radios for the moto g you will need to flash the ones back for the moto x.
Click to expand...
Click to collapse
THIS