First, I apologize if this is the wrong place to post this. I am new to these forums.
Essentially, the other day, my Google services stopped working, due to something in my hosts file. I booted into recovery, and commented out android.clients.google.com mtalk.google.com, which had pointed to 74.125.93.113
After booting up normally, and logging in to my Google account again, I was able to access the play store among other apps normally.
However, when I went on the Play store to download an app, the store immidiatlely closed and prompted me with "Unfortunately, Google Play Store has stopped."
I have tried the following to solve my issue, none of which have worked.
Factory Reset
Clear Cache\Data
Reinstall from APK
Uninstall updates
Log out of google, restart, log back in
Wipe data from Titanium Backup and install anew
I have yet to find a solution to my problems.
My System Specs:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Rooted 4.4)
Help would be much appreciated.
Thanks!
Any help please?
Did I post this in the wrong section?
Is there something wrong with my post?
Am I being ignored by the "great XDA minds" because apparently I'm stupid?
I still cannot fix my play store, and I would appreciate any form of help, please.
Delete please , this great mind did not read the op!
Tough problem.
Edit try clearing data for the play & play service app?
See edit
aviwdoowks said:
Delete please , this great mind did not read the op!
Tough problem.
Edit try clearing data for the play & play service app?
Click to expand...
Click to collapse
Already done that, no success.
themsftcpu said:
Already done that, no success.
Click to expand...
Click to collapse
Switch the dev runtime to the other try it & switch back. ART or dalvik.
Not to be bumping old threads, but I still have not resolved this issue. For now I am using an alternative app store, but I would like to know what the issue is.
I manually reinstalled gapps through adb, directly into /system, and it changed nothing. Any help would be appreciated.
themsftcpu said:
Not to be bumping old threads, but I still have not resolved this issue. For now I am using an alternative app store, but I would like to know what the issue is.
I manually reinstalled gapps through adb, directly into /system, and it changed nothing. Any help would be appreciated.
Click to expand...
Click to collapse
IF you have an unlocked bootloader (I'm assuming that you do, since you mention booting into recovery):
Follow the "Return to Stock" thread to flash the entire 4.4.2 SBF for your carrier (AT&T, I'm assuming - based on your screenshots).
I suggest using the manual method. If a factory reset did not help, this is likely your only hope.
SBFing back to stock can actually FIX a corrupt filesystem - a factory reset can not.
Everything you need is listed in that thread, including links to the SBF files themselves, and all drivers you may need (which are probably already installed since you mention booting into recovery and modifying your 'hosts' file).
If you do NOT have an unlocked BL, let me know. I will help you with alternative instructions, if you tell me which exploit you are using, and whether or not you are using safestrap, and which android version you are on (4.4?)
DON'T flash the 4.4.2 SBF if you are not unlocked or you will never be able to root and achieve write-protect-disable.
Good Luck
samwathegreat said:
IF you have an unlocked bootloader (I'm assuming that you do, since you mention booting into recovery):
Follow the "Return to Stock" thread to flash the entire 4.4.2 SBF for your carrier (AT&T, I'm assuming - based on your screenshots).
I suggest using the manual method. If a factory reset did not help, this is likely your only hope.
SBFing back to stock can actually FIX a corrupt filesystem - a factory reset can not.
Everything you need is listed in that thread, including links to the SBF files themselves, and all drivers you may need (which are probably already installed since you mention booting into recovery and modifying your 'hosts' file).
If you do NOT have an unlocked BL, let me know. I will help you with alternative instructions, if you tell me which exploit you are using, and whether or not you are using safestrap, and which android version you are on (4.4?)
DON'T flash the 4.4.2 SBF if you are not unlocked or you will never be able to root and achieve write-protect-disable.
Good Luck
Click to expand...
Click to collapse
Unfortunately I do not have an unlocked bootloader, as there is no way that I am aware to unlock the Moto X. When I said booting into recovery, I meant /system read\write mode. I am running Android 4.4 still, never updated to 4.4.2. I have adb, mfastboot (as well as fastboot on the device), and RSD Lite for flashing images to the device.
themsftcpu said:
Unfortunately I do not have an unlocked bootloader, as there is no way that I am aware to unlock the Moto X. When I said booting into recovery, I meant /system read\write mode. I am running Android 4.4 still, never updated to 4.4.2. I have adb, mfastboot (as well as fastboot on the device), and RSD Lite for flashing images to the device.
Click to expand...
Click to collapse
OK. Yes, there is a possibility to unlock your device. See the "China Middleman Back?" thread for details.
Anyways, since you are on 4.4, I assume you are using the "Slap My Moto" exploit + MotoWpNoMo (write protect disable exploit). (I asked which exploit you used, but you didn't advise)
What YOU will need to do (with locked BL) is follow the instructions in the "Return to Stock" thread, but instead of what I mentioned earlier, flash the entire 4.4 SBF for YOUR CARRIER (you never confirmed AT&T...)
After you have flashed the entire 4.4 SBF, you will need to re-apply the exploits to re-gain root and Write Protect Disable.
Once this is finished, your device should work 100% properly.
BE VERY CAREFUL. It seems you aren't aware of many of the nuances regarding the Moto X, so here is some info for you:
1. If you EVER attempt to downgrade your software version, you will brick your phone - possibly permanently. This applies to ALL Moto X phones - locked, unlocked, rooted, or not.
2. Additionally, if you ever update to 4.4.2, you will completely/permanently LOSE the ability to root and achieve write protect disable (unless you unlock the BL). There is a new temporary root method that works on 4.4.2, but it does not disable write protect, so you cannot write to /system, cannot flash custom recovery, and every time you reboot your device, you will have to re-run the exploit to gain root back again.
3. There is a gentleman from China who is selling bootloader unlock codes for the Moto X. He somehow has access to some of Motorola's database. Currently, he can unlock most devices that have a manufacture date of 2014 (he doesn't have access to 2013 codes). The cost is $45 (very reasonable, IMO), and you can find all the details in the "China Middleman Back?" thread. If you DO decide to try this unlock method and are successful, you will need to re-flash the entire stock SBF to remove the 'exploits' you are using. Also, with unlocked BL, you can successfully root and flash recovery (and write to /system) no matter which android version you are on.
Hope this clears everything up for you. Let me know if you have questions.
samwathegreat said:
OK. Yes, there is a possibility to unlock your device. See the "China Middleman Back?" thread for details.
Anyways, since you are on 4.4, I assume you are using the "Slap My Moto" exploit + MotoWpNoMo (write protect disable exploit). (I asked which exploit you used, but you didn't advise)
What YOU will need to do (with locked BL) is follow the instructions in the "Return to Stock" thread, but instead of what I mentioned earlier, flash the entire 4.4 SBF for YOUR CARRIER (you never confirmed AT&T...)
After you have flashed the entire 4.4 SBF, you will need to re-apply the exploits to re-gain root and Write Protect Disable.
Once this is finished, your device should work 100% properly.
BE VERY CAREFUL. It seems you aren't aware of many of the nuances regarding the Moto X, so here is some info for you:
1. If you EVER attempt to downgrade your software version, you will brick your phone - possibly permanently. This applies to ALL Moto X phones - locked, unlocked, rooted, or not.
2. Additionally, if you ever update to 4.4.2, you will completely/permanently LOSE the ability to root and achieve write protect disable (unless you unlock the BL). There is a new temporary root method that works on 4.4.2, but it does not disable write protect, so you cannot write to /system, cannot flash custom recovery, and every time you reboot your device, you will have to re-run the exploit to gain root back again.
3. There is a gentleman from China who is selling bootloader unlock codes for the Moto X. He somehow has access to some of Motorola's database. Currently, he can unlock most devices that have a manufacture date of 2014 (he doesn't have access to 2013 codes). The cost is $45 (very reasonable, IMO), and you can find all the details in the "China Middleman Back?" thread. If you DO decide to try this unlock method and are successful, you will need to re-flash the entire stock SBF to remove the 'exploits' you are using. Also, with unlocked BL, you can successfully root and flash recovery (and write to /system) no matter which android version you are on.
Hope this clears everything up for you. Let me know if you have questions.
Click to expand...
Click to collapse
Sorry, I didn't see the exploit, but yes I am using the SlapMyMoto exploit .here Yes I am using ATT
In reponse to
1. Got it, don't downgrade whatever I do.
2. I actually disabled the OTA updater app because the 4.4.2 update notification was stupid, and I accidentally hit "Yes, update."
3. I have the XT1058, which is the 2013 model. Besides that, not sure I want to be giving my money to a (hacker?).
As for the instructions above that: I will try in the morning, I have an important phone call to take tomorrow and I can't afford to have my phone acting up.
themsftcpu said:
Sorry, I didn't see the exploit, but yes I am using the SlapMyMoto exploit .here Yes I am using ATT
In reponse to
1. Got it, don't downgrade whatever I do.
2. I actually disabled the OTA updater app because the 4.4.2 update notification was stupid, and I accidentally hit "Yes, update."
3. I have the XT1058, which is the 2013 model. Besides that, not sure I want to be giving my money to a (hacker?).
As for the instructions above that: I will try in the morning, I have an important phone call to take tomorrow and I can't afford to have my phone acting up.
Click to expand...
Click to collapse
1. Great!
2. Good idea. Disabling the OTA updater is wise to prevent the possibility of losing root/write protect.
3. What is important is the date YOUR phone was manufactured. If you purchased it in 2013, obviously it has a 2013 manufacture date, but the Moto factory is still churning out brand new XT1058s. If you are curious, the manufacture date is listed on the box, OR you can find it by issuing "fastboot getvar all". I understand your reluctance to send money to this gentleman - fortunately you never updated to 4.4.2 so you can still use the 4.4 exploits. This is the ONLY option to achieve full root for those on 4.4.2+
Again, I highly recommend using the manual method (using fastboot/mfastboot) listed in the Return to Stock thread. Faster and easier than using RSD Lite, IMO.
Please let us know if the procedure I outlined fixes your problem once you have completed all the steps.
themsftcpu said:
Sorry, I didn't see the exploit, but yes I am using the SlapMyMoto exploit .here Yes I am using ATT
In reponse to
1. Got it, don't downgrade whatever I do.
2. I actually disabled the OTA updater app because the 4.4.2 update notification was stupid, and I accidentally hit "Yes, update."
3. I have the XT1058, which is the 2013 model. Besides that, not sure I want to be giving my money to a (hacker?).
As for the instructions above that: I will try in the morning, I have an important phone call to take tomorrow and I can't afford to have my phone acting up.
Click to expand...
Click to collapse
samwathegreat said:
1. Great!
2. Good idea. Disabling the OTA updater is wise to prevent the possibility of losing root/write protect.
3. What is important is the date YOUR phone was manufactured. If you purchased it in 2013, obviously it has a 2013 manufacture date, but the Moto factory is still churning out brand new XT1058s. If you are curious, the manufacture date is listed on the box, OR you can find it by issuing "fastboot getvar all". I understand your reluctance to send money to this gentleman - fortunately you never updated to 4.4.2 so you can still use the 4.4 exploits. This is the ONLY option to achieve full root for those on 4.4.2+
Again, I highly recommend using the manual method (using fastboot/mfastboot) listed in the Return to Stock thread. Faster and easier than using RSD Lite, IMO.
Please let us know if the procedure I outlined fixes your problem once you have completed all the steps.
Click to expand...
Click to collapse
I must make a slight revision to my previous statements:
We always advise users to never downgrade, because IF the bootloader OR gpt.bin (partition table) changed between the updates, the phone will be a brick. There is one exception: You CAN successfully downgrade 4.4 to the 4.2.2 Post-Camera Update firmware (NOT the original 4.2.2), because this is the only version where neither the bootloader, nor partition table was updated.
Upon reading up on SlapMyMoto, it is necessary to 'downgrade' to the 4.2.2 Post-Camera Update.
Please do not use the guide you linked from Reddit -- jcase has since released a NEW version of SlapMyMoto, and you should follow the new guide here: http://forum.xda-developers.com/moto-x/orig-development/4-4-root-slapmymoto-1-0-motowpnomo-t2538896
Also, you won't be flashing the 4.4 SBF as I had previously stated, but rather the Post-Camera Update firmware that is linked in jcase's thread.
Flash the AT&T file linked in jcase's thread, per the "Return to Stock" manual method, then follow the instructions in his thread.
This should fix your issues.
Sorry for the confusion....I haven't used SlapMyMoto personally, as I have an unlocked bootloader. In hindsight, I should have read up on SlapMyMoto before I advised you....
themsftcpu said:
Essentially, the other day, my Google services stopped working, due to something in my hosts file. I booted into recovery, and commented out android.clients.google.com mtalk.google.com, which had pointed to 74.125.93.113
Click to expand...
Click to collapse
From the OP, it looks like you edited the HOSTS file and have had problems since, but you do not say if you un-did your host file edit.
Did you?
If no, you should try that first. try and put the original, unmodified hosts file on there.
Related
This might be crystal clear for most of you, but I will ask this to avoid any unwanted scenarios. Coming from a SGS2, I flashed almost anything without worrying, but I see lots of people bricking their phones here, so I'd like to be on the safe side with this.
How do I root my Moto X with 4.4.2 and unlocked bootloader?
I've read a couple of articles, where they casually mention to flash TWRP, and then SuperSu, and that's it. I can't find a TWRP 4.4.2, only 4.4. Will that work?
I'm also reading the "The Complete Moto X Guides/Information Thread", where under "Unlocked bootloader" there are some instructions, which seem a bit... complicated. Should I follow those?
Thanks guys! :silly:
TheSaw said:
This might be crystal clear for most of you, but I will ask this to avoid any unwanted scenarios. Coming from a SGS2, I flashed almost anything without worrying, but I see lots of people bricking their phones here, so I'd like to be on the safe side with this.
How do I root my Moto X with 4.4.2 and unlocked bootloader?
I've read a couple of articles, where they casually mention to flash TWRP, and then SuperSu, and that's it. I can't find a TWRP 4.4.2, only 4.4. Will that work?
I'm also reading the "The Complete Moto X Guides/Information Thread", where under "Unlocked bootloader" there are some instructions, which seem a bit... complicated. Should I follow those?
Thanks guys! :silly:
Click to expand...
Click to collapse
That's good you did the reading first!
According to the TWRP thread, version 2.6.3.1 (by posted Hashcode) works fine for 4.4.2. Look for the thread in the "Android Development" section with the green square before the thread title. I know it's long but you really should read through the whole thread to get a feel for what people have been doing wrong, etc. For example, you NEED to flash it with Moto's fastboot.exe (often called mfastboot but it's not actually called that when you download it from Moto).
The guide you are referring to seems fine, except the mfastboot command assumes you changed the name of the Moto fastboot executable to mfastboot...
I don't mean to be one of those trolls around here but if the guide seems too complicated, I would encourage you to wait for Moto to release the SBF files for 4.4.2 before rooting. I say this because, without those files, things could get tricky of you're not an expert (I'm not) and you do something wrong. When those files come out, you can follow the simple guide on the Moto site for returning your phone completely to factory specs, should you mess up /system or something.
I'm actually doing what I'm recommending to you. I'm confident I wouldn't mess things up but on the other hand this is my only phone, I'm too poor to replace it, and I'm living abroad so sending it back would be tricky.
[EDIT]: By SBF I mean either the real SBF or the package you can download from the Motorola "return to factory" page. I'm not actually sure if they are the same thing or not as I haven't downloaded. But you don't need RSDLite for them...
droib said:
That's good you did the reading first!
According to the TWRP thread, version 2.6.3.1 (by posted Hashcode) works fine for 4.4.2. Look for the thread in the "Android Development" section with the [...]
Click to expand...
Click to collapse
Hey, thanks for the detailed answer! I'm in a very similar situation to yours. I live in Europe, so returning the phone is not an option, and I don't want to brake it either .
I've flashed a lot of things on my old phone, so I can't say I'm a beginner, but some of these things are new to me, so I'm a bit cautious. For example: what are the SBF file? Those are not needed to root, they are only as backup, right?
If following those instructions correctly are 100% fail-proof, then I would try it.
TheSaw said:
Hey, thanks for the detailed answer! I'm in a very similar situation to yours. I live in Europe, so returning the phone is not an option, and I don't want to brake it either .
I've flashed a lot of things on my old phone, so I can't say I'm a beginner, but some of these things are new to me, so I'm a bit cautious. For example: what are the SBF file? Those are not needed to root, they are only as backup, right?
If following those instructions correctly are 100% fail-proof, then I would try it.
Click to expand...
Click to collapse
Given your experience I don't think there is any real chance of phone death by following those instructions. The issue is, as you say, backup, or what happens AFTER you successfully root. Motorola's SBF files are everything your phone needs to go back to stock, and 4.4.2 is not available yet. So for example if you were on 4.4 and you corrupted something important like your partition table, you could just go to Motorola's website, request the files for 4.4 and flash them all using fastboot (mfastboot as they say here) to get back to a pristine phone. Right now, you can make a recovery backup of /system, etc. right after rooting which SHOULD be fine for correcting OS tinkering errors, but you never know... People have posted on the possibility of flashing, for example, the 4.4 recovery.img on top of 4.4.2 in order get future OTAs, etc, but this sort of thing is very risky. Maybe it works or maybe you hard-brick.
This guide will work on 4.4.2 and has all the files you need to download. If you're already unlocked you can skip those steps of course
http://www.elementalxdesigns.com/ec...our-Moto-X-Developer-Edition-and-install-TWRP
It doesn't tell you how to root, but when you exit TWRP it will ask "would you like to install supersu?" so select yes. Once you're in Android go to Google play and download supersu from the market. Open it and it will ask if you want to install binaries. Select yes and the twrp/cwm option. Your phone will reboot then you're done
This still works to root if your bootloader is already unlocked -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
Now there is a newer version of SuperSU. See this thread -> http://forum.xda-developers.com/showthread.php?t=1538053 and use the link for the CWM / TWRP / MobileODIN installable ZIP.
TheSaw said:
This might be crystal clear for most of you, but I will ask this to avoid any unwanted scenarios. Coming from a SGS2, I flashed almost anything without worrying, but I see lots of people bricking their phones here, so I'd like to be on the safe side with this.
How do I root my Moto X with 4.4.2 and unlocked bootloader?
I've read a couple of articles, where they casually mention to flash TWRP, and then SuperSu, and that's it. I can't find a TWRP 4.4.2, only 4.4. Will that work?
I'm also reading the "The Complete Moto X Guides/Information Thread", where under "Unlocked bootloader" there are some instructions, which seem a bit... complicated. Should I follow those?
Thanks guys! :silly:
Click to expand...
Click to collapse
Follow these instructions with clickable links to TWRP and SuperSU
Step-By-Step Instructions for Unlocking and Rooting a Moto X Dev Ed
works for both 4.4 and 4.4.2.
Okay, I have rooted my phone. I've read several articles on the subject, and this is the easiest method I've found to do it:
Cozume said:
1) Put device in bootloader mode while not connected to PC using the buttons (Volume Down + Power);
2) Connect device to PC using USB cord;
3) mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
4) fastboot reboot-bootloader
5) Disconnect device from PC;
6) Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and then pressing the Volume Up button to select the recovery mode; and
7) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
Click to expand...
Click to collapse
After you downloaded the files needed for this from here (make sure they're not outdated, if you're reading this somewhere in the future), you can just follow these steps for a quick root access. UNLOCKED BOOTLOADER ONLY.
Hello all,
Hopefully this is not considered a useless post and is deleted! I have previously owned the OG Droid and GNex, both rooted and have run custom ROMs so, I am not a COMPLETE noob, but I'm also not an expert.
In any event, I purchased a Verizon DE phone so I could easily unlock and root. I have yet to even activate it, so it is FRESH! It has come with 4.2.2, 139.10.53-ghost, which seems like the original image. I want to upgrade this ONLY to the point of still being able to run my standard tethering app (which I am not sure which 4.4 upgrade breaks this functionality), and root. I also want to be able to run custom ROMs if desired.
I am also confused by whether or not there is a potential downgrade "bricking" of the device. There are threads out there which seem like it can be done, (see http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358), and many other threads that say that regardless of being a DE, it cannot be downgraded. If someone can clarify this for me, that would be great.
Three other questions at this point. One, the thread referenced above discussed using TWRP or CWM for recovery. I have only used CWM in the past. Are there pros and cons to either one? Seems like most everyone uses TWRP for the Moto X.
Two, are there ROMs for the Moto X that have all of the rooted functionality of 4.4.2, with none of the drawbacks of stock, rooted 4.4.2? Would I be better off using one of those?
Finally, will I be able to prevent OTA notifications if I stay with stock, rooted, and upgrade only to certain point?
Sorry for all the questions, and yes, I have been searching and reading, but I have not found enough clear information to feel comfortable not asking directly.
Thank you all in ADVANCE!
There are currently 4 Moto or Stock ROMs for the Verizon Moto X XT1060
139.10.53 = Initial Shipping 4.2.2
139.15.1 = 4.2.2 w/camera update or 1st OTA
140.45.5 = 4.4 or 2nd OTA
164.55.2 = 4.4.2 or 3rd OTA.
The Developer Edition, once the bootloader is unlocked, can be rooted no matter what Moto ROM is on your phone.
Due to changes in parts that are included with 4.4.2, under certain circumstances when trying to downgrade from 4.4.2 to 4.4 or lower, you could either brick your phone, or set it up to brick in the future when you take an upgrade. So it is suggested you just stick with what is on your phone once you get on 4.4.2. Besides, you wont need to downgrade to gain root once you unlock your bootloader.
If you haven't had 4.4.2 on your phone yet, you are perfectly welcome to upgrade from 4.2.2 to 4.4, then downgrade to 4.2 w/camera update (4.2.2 with camera update is Blur_Version.139.15.1.ghost_verizon.Verizon.en.US aka VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml). which is pretty much what the "Downgrading the bootloader" section of -> http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358 says.
Why worry about downgrading? Well, Locked bootloader users needed to downgrade to take advantage of an exploit in the older rom to gain root and disable write protection. This is not needed on the Dev Edition once the bootloader is unlocked.
As for custom roms, or 3rd party roms. Once your bootloader is unlocked you can flash them.
As for tethering. If you stick on a Stock Moto ROM, On 4.2.2 I used the Wifi Tether for Root from the Play Store.
For 4.4 and 4.4.2 I Use the wifi_tether_v3_4-experimental1.apk from https://code.google.com/p/android-wifi-tether/
change device profile to galaxy nexus (cdma/lte)
check box: wifi-driver reload
check box: enabled routing fix
If you have troubles, its also suggested to...
check box: wifi-driver reload 2
Doing this, I can set the SSID and WPA key. And it doesn't touch any system files or anything, so it is one less thing to get in the way of taking future OTA updates.
Oh, and the Dev Edition XT1060 and the retail/motomaker XT1060 use the same roms, radios, etc.
To root the dev edition see -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738
KidJoe said:
If you haven't had 4.4.2 on your phone yet, you are perfectly welcome to upgrade from 4.2.2 to 4.4, then downgrade to 4.2 w/camera update (4.2.2 with camera update is Blur_Version.139.15.1.ghost_verizon.Verizon.en.US aka VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml). which is pretty much what the "Downgrading the bootloader" section of -> http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358 says.
Click to expand...
Click to collapse
Thanks KidJoe! So I gather there would really not be a reason to downgrade a DE device anyway, since you can root it regardless of what stock ROM you are running. And since there are ways to wifi tether on 4.4.2, that is a non-issue.
I am still a bit confused regarding your quote above about the "upgrade from 4.2.2 to 4.4, then downgrade to 4.2 w/camera update..." Do you have to follow that path to get to 4.2 w/camera update, or can you just flash that ROM (139.15.1) once unlocked?
I currently use FoxFi on my GNex (paid for it!) and was hoping to use on Moto X. That's really why I didn't want to upgrade too far. Not sure that it works on it though.
Thanks again!
amajamar said:
I am still a bit confused regarding your quote above about the "upgrade from 4.2.2 to 4.4, then downgrade to 4.2 w/camera update..." Do you have to follow that path to get to 4.2 w/camera update, or can you just flash that ROM (139.15.1) once unlocked?
Click to expand...
Click to collapse
No. Was just saying that if you never had 4.4.2 on your phone, wanted to upgrade to 4.4, and later wanted to go back to 4.2.2 w/camera, you could.
amajamar said:
I currently use FoxFi on my GNex (paid for it!) and was hoping to use on Moto X. That's really why I didn't want to upgrade too far. Not sure that it works on it though.
Thanks again!
Click to expand...
Click to collapse
As far as I know, FoxFi still doesn't work on 4.4.2 on the X even when rooted. I don't recall if it works on 4.4. But I never used it.
If you have a DE there is absolutely no reason to downgrade. Ever. If you want to be able to tether here's the easiest way to do it.
Activate your phone.
Take all the updates.
Go to this site: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Follow those directions to a "T". Once that's done, download Xposed Framework, then download MotoTether.
The only time you'll need to worry about being rooted is if you delete bloatware and go to take the next OTA. You'll either need to reinstall all the apps you deleted manually or go to Motorola and request the factory image to reflash it.
The Tallest said:
If you have a DE there is absolutely no reason to downgrade. Ever. If you want to be able to tether here's the easiest way to do it.
Activate your phone.
Take all the updates.
Go to this site:
Follow those directions to a "T". Once that's done, download Xposed Framework, then download MotoTether.
The only time you'll need to worry about being rooted is if you delete bloatware and go to take the next OTA. You'll either need to reinstall all the apps you deleted manually or go to Motorola and request the factory image to reflash it.
Click to expand...
Click to collapse
So I should take the updates BEFORE unlocking? I was assuming it was the other way around. OK. Regarding "bloatware", if you just "freeze" it, does that prevent future OTAs? If you attempt to take an OTA with those apps either frozen or deleted, will you be risking bricking?
amajamar said:
So I should take the updates BEFORE unlocking? I was assuming it was the other way around. OK. Regarding "bloatware", if you just "freeze" it, does that prevent future OTAs? If you attempt to take an OTA with those apps either frozen or deleted, will you be risking bricking?
Click to expand...
Click to collapse
Rather than retyping.. please see -> http://mark.cdmaforums.com/MotoX-Unlock1.htm
while written due to the 3rd party supplier of bootloader unlock codes, the info applies equally to Dev Edition phones (other than the source of your unlock code)
The Tallest said:
If you have a DE there is absolutely no reason to downgrade. Ever. If you want to be able to tether here's the easiest way to do it.
Activate your phone.
Take all the updates.
Go to this site: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Follow those directions to a "T". Once that's done, download Xposed Framework, then download MotoTether.
The only time you'll need to worry about being rooted is if you delete bloatware and go to take the next OTA. You'll either need to reinstall all the apps you deleted manually or go to Motorola and request the factory image to reflash it.
Click to expand...
Click to collapse
I whole-heartedly agree with everything written in this post. You also have to make sure you are on stock recovery if you want to take an OTA. There are plenty of guides around here about taking an OTA, so just make sure you read some of those before you accept an OTA.
I have a suggestion for the OP:
1 - take all the updates on the phone. This will update the radios, boot loader; recovery, and the main ROM (system).
(The boot loader can not be downgraded, but as mentioned above, there really isn't any reason why you would want to try and downgrade your bootloader because you have a DE device)
2 - unlock the bootloader. you can google the steps in the process. Basically you get the unlock key from Motorola. The toughest part of the process is getting the fastboot and device drivers set up properly on your computer. This step will all of the userdata (pictures, apps etc.)
3 - use Fastboot to flash a custom recovery (I use TWRP ver 2.7). then boot into TWRP recovery w/o rebooting. Note that the volume down button is used in the bootloader to highlight your desired option, then volume up is used to select the option. When you are in TWRP and then exit, I believe it will prompt you to install the superuser binaries, which you will want to do.
At this point you can choose do flash a custom 4.4.2 ROM from the Dev section here (the Krypton rom is very good), or you can run stock w/ root. If you choose stock, I recommend the following steps for wifi and customization:
4 - boot up device normally and set it up. you will have be on the stock 4.4.2 rom with root.
5 - install Xposed from here on XDA.
6 then install the xposed module from the moto x apps section (it may also be available to download from within xposed) that enables wifi tethering. This will allow you to use the built in tethering without subscription issues.
7 - install the GravityBox xposed module (you can download this from within Xposed). This allows many of the customizations that you would normally find only in a custom rom (custom quicksettings, reboot options etc).
8 - install rootcloak module for xposed (download within xposed). This will let you run Isis or other apps that don't like root (it comes preconfigured for many apps).
jasoraso said:
I have a suggestion for the OP:
1 - take all the updates on the phone. This will update the radios, boot loader; recovery, and the main ROM (system).
(The boot loader can not be downgraded, but as mentioned above, there really isn't any reason why you would want to try and downgrade your bootloader because you have a DE device)
2 - unlock the bootloader. you can google the steps in the process. Basically you get the unlock key from Motorola. The toughest part of the process is getting the fastboot and device drivers set up properly on your computer. This step will all of the userdata (pictures, apps etc.)
3 - use Fastboot to flash a custom recovery (I use TWRP ver 2.7). then boot into TWRP recovery w/o rebooting. Note that the volume down button is used in the bootloader to highlight your desired option, then volume up is used to select the option. When you are in TWRP and then exit, I believe it will prompt you to install the superuser binaries, which you will want to do.
At this point you can choose do flash a custom 4.4.2 ROM from the Dev section here (the Krypton rom is very good), or you can run stock w/ root. If you choose stock, I recommend the following steps for wifi and customization:
4 - boot up device normally and set it up. you will have be on the stock 4.4.2 rom with root.
5 - install Xposed from here on XDA.
6 then install the xposed module from the moto x apps section (it may also be available to download from within xposed) that enables wifi tethering. This will allow you to use the built in tethering without subscription issues.
7 - install the GravityBox xposed module (you can download this from within Xposed). This allows many of the customizations that you would normally find only in a custom rom (custom quicksettings, reboot options etc).
8 - install rootcloak module for xposed (download within xposed). This will let you run Isis or other apps that don't like root (it comes preconfigured for many apps).
Click to expand...
Click to collapse
After reading the link Kidjoe supplied earlier (That was a FANTASTIC, MUST READ reference for noobs who want to understand the complexities of the Moto X), I may stay off KitKat, as I am not a fan of the white icons in the notification bar, however I do think this is the route (root??) I will take.
I am on Verizon 4.4.2, bootloader unlocked, rooted, with TWRP. Obviously, OTA won't work, but what is the best way for me to update to 4.4.4 stock ROM w/o wiping my user data?
If the Moto X is anything like the Nexus 5, there may be an OTA update.zip that is lurking around and you can just flash that and then reflash root to update you to the latest software version. Or you could download and flash the SYSTEM.IMG and BOOT.IMG from the 4.4.4 Verizon ROM. I'd recommend the first one and make sure that someone else can safely say that the second method would even work!
Toys Samurai said:
I am on Verizon 4.4.2, bootloader unlocked, rooted, with TWRP. Obviously, OTA won't work, but what is the best way for me to update to 4.4.4 stock ROM w/o wiping my user data?
Click to expand...
Click to collapse
The proper way to update is to use the 4.4.4 FXZ from here: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
In order to retain your data and apps, you need to use the tools provided by @SamuriHL and use the "keep data" option.
Everything you need is listed in the first post, including links and instructions for the tools to use. All of your apps and settings will be intact --AS LONG as you use the tools provided in the OP. If you fail to do this, you WILL lose your data. Afterwards, you can flash TWRP again (from here: http://techerrata.com/browse/twrp2/ghost ) using fastboot, and re-root your device.
Next time, please remember to post your questions in Q&A, not general.
Good Luck :good:
P.S. I also want to add that using the FXZ is superior to taking the OTA for several reasons, many that I don't care to list. First and foremost, you don't need to worry about flashing stock recovery back (required to take an OTA), and you don't need to worry about any changes you may have made to /system. Follow the simple instructions, and it is done.
You will find numerous instances of people who have struggled to take the OTA, or who have spent enormous amounts of time trying only to have the OTA fail to install. I doubt you'll find ONE person who has struggled with the FXZ. It is so much simpler that I don't understand why anyone recommends using the OTA unless you are completely stock and unrooted. IMO, that is the only time you should use the OTA when an FXZ is available.
samwathegreat said:
The proper way to update is to use the 4.4.4 FXZ from here: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
In order to retain your data and apps, you need to use the tools provided by @SamuriHL and use the "keep data" option.
Everything you need is listed in the first post, including links and instructions for the tools to use. All of your apps and settings will be intact --AS LONG as you use the tools provided in the OP. If you fail to do this, you WILL lose your data. Afterwards, you can flash TWRP again (from here: http://techerrata.com/browse/twrp2/ghost ) using fastboot, and re-root your device.
Next time, please remember to post your questions in Q&A, not general.
Good Luck :good:
P.S. I also want to add that using the FXZ is superior to taking the OTA for several reasons, many that I don't care to list. First and foremost, you don't need to worry about flashing stock recovery back (required to take an OTA), and you don't need to worry about any changes you may have made to /system. Follow the simple instructions, and it is done.
You will find numerous instances of people who have struggled to take the OTA, or who have spent enormous amounts of time trying only to have the OTA fail to install. I doubt you'll find ONE person who has struggled with the FXZ. It is so much simpler that I don't understand why anyone recommends using the OTA unless you are completely stock and unrooted. IMO, that is the only time you should use the OTA when an FXZ is available.
Click to expand...
Click to collapse
Curious,
What would the difference be in using FXZ vs flashing a 4.4.4 ROM such as krypton? Is it because the FXZ will update boot loader?
SR3TLAW said:
Curious,
What would the difference be in using FXZ vs flashing a 4.4.4 ROM such as krypton? Is it because the FXZ will update boot loader?
Click to expand...
Click to collapse
Flashing Krypton is possible from Custom recovery, unlike an OTA / FXZ. In addition, I believe that Krypton only includes the /system and /boot partitions. This is why he states that you need to be on 4.4.2+ first.
The FXZ overwrites all relevant partitions with new data.
Vekhez said:
If the Moto X is anything like the Nexus 5, there may be an OTA update.zip that is lurking around and you can just flash that and then reflash root to update you to the latest software version. Or you could download and flash the SYSTEM.IMG and BOOT.IMG from the 4.4.4 Verizon ROM. I'd recommend the first one and make sure that someone else can safely say that the second method would even work!
Click to expand...
Click to collapse
Unfortunately the X is nothing like the N5.
KJ said:
Unfortunately the X is nothing like the N5.
Click to expand...
Click to collapse
Yeah, I've found that out as of recently, they are very different devices, very very different indeed
There are a lot of people joining xda on daily basis, and there are a lot of repetitive questions being asked which fill up Development threads. Point them here. Feel free to ask or answer questions. Idea of this thread is to get users to help other users with their problems/questions. Please do not spoon feed, but rather point in the direction where that user can find an answer and educate himself
First thing first. I strongly advise you to read THIS thread before posting ANYTHING on XDA.
Then, have a quick look at the names of threads in post no2, you might find what you need right away.
For ROM issues please do mention in your post about:
ROM name
ROM version and base
kernel version and its settings
any mods applied on top of it
flashing "style" aka dirty or clean
something like this
...and be sure you have asked before on the ROM thread unless you have less than 10 posts on XDA
Third. Even if you do get your question answered, please, do come back and read threads in post no2 (coming later as soon as we start getting the guides) to educate yourself. You'll be surprised how much time and frustration it will save you in the future.
ASK ANY QUESTION HERE,adb, drivers, superCID etc...... You will either get an answer or will get pointed in the right direction.
No abuse towards noobs tolerated here! No question is stupid in this thread.
***I feel that a little OT is healthy to the success of this type of thread. The people here who help the most will develop a comradery therefore OT is allowed within reason. Common sense will be applied ***
Credits to @xanthrax who made the original nexus 4 thread where i got inspired! :highfive:
Great idea!!! And well needed! :good::good:
Darth said:
Great idea!!! And well needed! :good::good:
Click to expand...
Click to collapse
Thanks i hope we can fill this up quickly! Just share it!
Enviado desde mi XT1060 mediante Tapatalk
Sorry I am a noob.
Currently i am using kitkat 4.4.4.
I wanted to know if i Root my phone will i get the lollipop update that will be officially launched for the phone ??
4yush said:
Currently i am using kitkat 4.4.4.
I wanted to know if i Root my phone will i get the lollipop update that will be officially launched for the phone ??
Click to expand...
Click to collapse
yes, you will get the update. but the installation fails
I have got tired of waiting for official update and have decided to root my moto x on 4.4.4.
This is what I understood.
1 . unlock bootloader
2. Install twrp
3. Install rom.
I would want to know if I can flash BlissPop directly after the above steps.
Also can kernels be flashed directly from recovery or they have to be flashed using pc like my xperia did
4yush said:
Currently i am using kitkat 4.4.4.
I wanted to know if i Root my phone will i get the lollipop update that will be officially launched for the phone ??
Click to expand...
Click to collapse
To root on 4.4.4 you need an unlocked (or unlockable) bootloader. An unlocked bootloader phone roots by flashing custom recovery.
If you try to take an OTA without stock recovery on your phone, you'll get stuck in a bootloop (fastboot earase cache will get you out of it), and can not apply an OTA. Further, if while rooted you modify /system, certain files, or other parts of the phone too much while rooted, the OTA could fail its pre-flash validation checks, thus preventing it from installing.
Then again, those who use SlapMyMoto/RockMyMoto/PwnMyMoto or other HACKS to root their phone with locked bootloader, could also run into issues with the OTA's pre-flash validation checks causing the OTA Update to fail too. However, those old processes don't work on 4.4.4 as the vulnerabilities they used are patched.
If you have an unlocked bootloader, root your phone by flashing TWRP (or CWM, etc) and installing SuperSU, then flash stock recovery back on, and run rooted with apps installed that use root, like RootExplorer, Wifi Tether for Root, Greenify, etc. You can take the OTA just fine.
Note: If you install something like Xposed, it will cause the Pre-flash vaildations to fail because it does modify things the pre-flash checks look for. You'd have to disable it, which involves having 3rd party recovery, and flashing the disable.zip (on your phone as /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip), then put stock recovery back on.
adity said:
I have got tired of waiting for official update and have decided to root my moto x on 4.4.4.
This is what I understood.
1 . unlock bootloader
2. Install twrp
3. Install rom.
I would want to know if I can flash BlissPop directly after the above steps.
Also can kernels be flashed directly from recovery or they have to be flashed using pc like my xperia did
Click to expand...
Click to collapse
If BlissPop is a custom ROM then yes after all of those steps you can flash it directly, I'll suggest to make a nandroid backup before. And then to get some gapps for that ROM. And kernels can be flashed directly on recovery too! Good luck!
Enviado desde mi XT1060 mediante Tapatalk
Should this have to be sticky?
Enviado desde mi XT1060 mediante Tapatalk
Using blisspop which is based on cm12 and mobile standby is using abnormal amounts of battery(75%)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adity said:
Using blisspop which is based on cm12 and mobile standby is using abnormal amounts of battery(75%)
Click to expand...
Click to collapse
I think battery life on custom ROM is very bad compared to stock, I'm back at it because of that and for moto features.
Enviado desde mi XT1060 mediante Tapatalk
Making a bump to everyone can see this post!
Enviado desde mi XT1060 mediante Tapatalk
Moto X - No Signal?
So I got the Verizon XT1060 a couple of days back, put my SIM in and everything was working fine for a couple of days. Made a few calls, texted a bunch. Everything was good.
Never really got a chance to check how data worked since I was always on WiFi but yesterday when I tried making the mobile internet work it just wouldn't . I have a 3G connection, so I thought might as well give it a shot and started putting in the APNs in according to what my provider said. I came across a post that said you can't select just 3G for the XT1060 and you'd have to install this app called PhoneInfo(Ad) to make 3G only work.
So I installed the app. Set it to WCDMA only. And restarted the phone. Ever since then my phone has been on no-signal. Can't make calls/texts. No bars. I can read stuff on the SIM card just fine though. Today I went and got a new SIM Card hoping it'll work. But nothing. Zilch. Factory reset multiple times. Just no signal at all. In About Phone, in status information, the network shows up as unknown.
I don't exactly know what the problem is here. I talked to my provider and they said everything was fine on their end and I should check if my model is compatible. Which it is. At least for EDGE, if not for 3G. If phone was receiving signals and all before, then that definitely means it was compatible, right?
Any way. I'm based in Islamabad, Pakistan. And the phone is a Verizon XT1060 16GB. This is the only phone I have right now and I REALLY need to get this phone working asap.
I'm going to try and flash the stock image onto it. The phone was running stock VZW 4.4.4 and is not the dev edition. So I can't root.
Any suggestions or ideas are welcome.
Thank You.
NadirChaudhry said:
So I got the Verizon XT1060 a couple of days back, put my SIM in and everything was working fine for a couple of days. Made a few calls, texted a bunch. Everything was good.
Never really got a chance to check how data worked since I was always on WiFi but yesterday when I tried making the mobile internet work it just wouldn't . I have a 3G connection, so I thought might as well give it a shot and started putting in the APNs in according to what my provider said. I came across a post that said you can't select just 3G for the XT1060 and you'd have to install this app called PhoneInfo(Ad) to make 3G only work.
So I installed the app. Set it to WCDMA only. And restarted the phone. Ever since then my phone has been on no-signal. Can't make calls/texts. No bars. I can read stuff on the SIM card just fine though. Today I went and got a new SIM Card hoping it'll work. But nothing. Zilch. Factory reset multiple times. Just no signal at all. In About Phone, in status information, the network shows up as unknown.
I don't exactly know what the problem is here. I talked to my provider and they said everything was fine on their end and I should check if my model is compatible. Which it is. At least for EDGE, if not for 3G. If phone was receiving signals and all before, then that definitely means it was compatible, right?
Any way. I'm based in Islamabad, Pakistan. And the phone is a Verizon XT1060 16GB. This is the only phone I have right now and I REALLY need to get this phone working asap.
I'm going to try and flash the stock image onto it. The phone was running stock VZW 4.4.4 and is not the dev edition. So I can't root.
Any suggestions or ideas are welcome.
Thank You.
Click to expand...
Click to collapse
Do you know which exactly are the bands your network uses? And I have stock ROM too and I get the 3G only option without the use of an external app. See here.
Enviado desde mi XT1060 mediante Tapatalk
Used Moto X What to look at.
Hello! (second post after saying hello on the corresponding post).
Please my native language is spanish so forgive my mistakes if any.
Going to the point and abusing the "ask ANY question" theme,
¿What to look in a Used Moto x?
In other words, here in Argentina phone are really expensive, and i have the chance to buy a Moto x really cheap.
Besides the obvious scraches, marks, screen details, and checking battery status and life. What else should i look? Any specific serial, date of production? any data?
Also i ad one more question.
As far as i understood with this post http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 if i have a 4.4.4 Phone all will be useless since there is no Rooting or bootunlock.
In any other cases there is some way to get root acess and also could get bootunlock (did i understood correctly?)
Also Unlocked boot would give me the chance to install a new operating system (Cyanogen mod or whatever)
Root would only give me the chance to uninstall app and so.
Thanks for all your answers!
Kind Regards!
cabe72000 said:
Besides the obvious scraches, marks, screen details, and checking battery status and life. What else should i look? Any specific serial, date of production? any data?
Click to expand...
Click to collapse
I've seen no evidence that any date range or serial number range is better than another.
One thing i would look for is... If you have the option to find out what ROM and bootloader is on the phone, that is helpful.
ROM: On the phone, go App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number.
Bootloader: check by Booting the X into Bootloader/Fastboot mode, and make note of the second line on the screen.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
The android version and bootloader version should match, otherwise it means someone was experimenting when they were flashing, and if you buy that phone you definitely make sure you fully flash the correct SBF onto the phone to bring everything in line. (I would ask the owner to do it BEFORE you buy, so if something goes wrong while flashing, you aren't the one bricking the phone).
cabe72000 said:
As far as i understood with this post http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 if i have a 4.4.4 Phone all will be useless since there is no Rooting or bootunlock.
In any other cases there is some way to get root acess and also could get bootunlock (did i understood correctly?)
Also Unlocked boot would give me the chance to install a new operating system (Cyanogen mod or whatever)
Root would only give me the chance to uninstall app and so.
Click to expand...
Click to collapse
Read further in that thread... like what I posted -> http://forum.xda-developers.com/mot...w-root-moto-x-confusion-t2826159/post54671918
So when you get your X, try to get the unlock code from Moto's web site. Then.... If you can get the code, and unlock the bootloader, you can root and disable write protection no matter what ROM is on your phone.
Moto gives the bootloader unlock code for most 2013 X's, its only a few carriers they don't give them for.
For Example: While Moto doesn't give out the Unlock Code for the ATT XT1058, they do give out the unlock code for the XT1058 from Rogers in Canada. So if you are buying a used Rogers XT1058 you can unlock the bootloader for free. The same holds true with nearly every XT1052, XT1053, and XT1056 I've seen (moto gives the bootloader unlock code on their web site).
Another thing to keep in mind, IF you get a model from a carrier that Moto doesn't give out the bootloader unlock code for, If the phone and its bootloader are still on 4.4.2/30.B4 or below, you can use Sunshine to unlock the bootloader.
Unlocking the bootloader will allow you to flash 3rd party or custom Recoveries, Roms, parts, etc. (so CM12, etc) With a locked bootloader, you can only flash ROMS/Parts which have been digitally signed by Moto and are for your particular Phone Model and Carrier combo. (The CID comes into play).
Rooting will allow you some access and control over /system and other files that are usually inaccessible to normal users. It doesn't allow you to flash 3rd party roms and pieces,etc. If you have a LOCKED bootloader, you basically need to find and exploit a flaw or vulnerability in the phone, or its software. i.e. Hack It , if you want root. Right now, with 4.4.4 and a locked bootloader, there are no vulnerabilities which can gain root, that is why having an unlocked or unlockable bootloader is so important. For more see -> http://mark.cdmaforums.com/MotoX-Locked.html
KidJoe said:
I've seen no evidence that any date range or serial number range is better than another.
One thing i would look for is... If you have the option to find out what ROM and bootloader is on the phone, that is helpful.
ROM: On the phone, go App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number.
Bootloader: check by Booting the X into Bootloader/Fastboot mode, and make note of the second line on the screen.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
The android version and bootloader version should match, otherwise it means someone was experimenting when they were flashing, and if you buy that phone you definitely make sure you fully flash the correct SBF onto the phone to bring everything in line. (I would ask the owner to do it BEFORE you buy, so if something goes wrong while flashing, you aren't the one bricking the phone).
Read further in that thread... like what I posted -> http://forum.xda-developers.com/mot...w-root-moto-x-confusion-t2826159/post54671918
So when you get your X, try to get the unlock code from Moto's web site. Then.... If you can get the code, and unlock the bootloader, you can root and disable write protection no matter what ROM is on your phone.
Moto gives the bootloader unlock code for most 2013 X's, its only a few carriers they don't give them for.
For Example: While Moto doesn't give out the Unlock Code for the ATT XT1058, they do give out the unlock code for the XT1058 from Rogers in Canada. So if you are buying a used Rogers XT1058 you can unlock the bootloader for free. The same holds true with nearly every XT1052, XT1053, and XT1056 I've seen (moto gives the bootloader unlock code on their web site).
Another thing to keep in mind, IF you get a model from a carrier that Moto doesn't give out the bootloader unlock code for, If the phone and its bootloader are still on 4.4.2/30.B4 or below, you can use Sunshine to unlock the bootloader.
Unlocking the bootloader will allow you to flash 3rd party or custom Recoveries, Roms, parts, etc. (so CM12, etc) With a locked bootloader, you can only flash ROMS/Parts which have been digitally signed by Moto and are for your particular Phone Model and Carrier combo. (The CID comes into play).
Rooting will allow you some access and control over /system and other files that are usually inaccessible to normal users. It doesn't allow you to flash 3rd party roms and pieces,etc. If you have a LOCKED bootloader, you basically need to find and exploit a flaw or vulnerability in the phone, or its software. i.e. Hack It , if you want root. Right now, with 4.4.4 and a locked bootloader, there are no vulnerabilities which can gain root, that is why having an unlocked or unlockable bootloader is so important. For more see -> http://mark.cdmaforums.com/MotoX-Locked.html
Click to expand...
Click to collapse
Thanks for your answer!!
Im sure that the actual owner knows nothing about Android, what im trying to say is that he didn't even know how to root or check software updates.
Besides that, what you answered to me is what i was looking for. On monday i have access to the phone so i will check everything you told me.
Tell you the news on Monday.
Muchas gracias!! (Thank you very much)
EDIT: Kidjoe Where do you work to have such a list of phones??? I work on Automotive industry and i drive maybe 5 o 6 cars but your's is incredibly long! hehe (sorry offtopic but i was amazed with the list )
cabe72000 said:
EDIT: Kidjoe Where do you work to have such a list of phones??? I work on Automotive industry and i drive maybe 5 o 6 cars but your's is incredibly long! hehe (sorry offtopic but i was amazed with the list )
Click to expand...
Click to collapse
I've been using cell phones since 1992... There was a period in there, for personal, that I was part of a Verizon Wireless customer "focus group" known as the VerizonWireless Customer Council, so many of my PERSONAL phones were acquired that way (for free).
Long story short... I worked for one global company for just a week shy of 20 yrs. While always a field employee needing mobility to do my job, for about the last 7 or 8 years, my focus was shifted to doing a lot of work in the mobility support space. The current company I'm working for (also global), I've been a part of the Tier 3/4 Mobility Support team, supporting our network, MDM solution, etc for our employees. We also take part in the design... so I have to have all, or as many as I can, of the devices we allow our employees to have. I often times joke that my job is being paid to play with my toys
KidJoe said:
I've been using cell phones since 1992... There was a period in there, for personal, that I was part of a Verizon Wireless customer "focus group" known as the VerizonWireless Customer Council, so many of my PERSONAL phones were acquired that way (for free).
Long story short... I worked for one global company for just a week shy of 20 yrs. While always a field employee needing mobility to do my job, for about the last 7 or 8 years, my focus was shifted to doing a lot of work in the mobility support space. The current company I'm working for (also global), I've been a part of the Tier 3/4 Mobility Support team, supporting our network, MDM solution, etc for our employees. We also take part in the design... so I have to have all, or as many as I can, of the devices we allow our employees to have. I often times joke that my job is being paid to play with my toys
Click to expand...
Click to collapse
My wife has forbid me to get another phone for a couple years.... Lol
Moto X, N5 and M8 in a year. Though, she's in love with the hand me down moto X... It finally got her off her iPhone 4s. So she benefited from my whims.
So I'm stuck for awhile. ?
I did find a solution to the battery problem.
Thing is google keeps data on even when wifi is connected for the handofff feature. So I make sure that I turn off data while at home.
Since then I have been having great battery life.. Even better than stock, more than 4 hours screen time
Hi guys. I somehow messed things up really bad.
I was running a modded ROM, but decided I wanted to go back to unrooted stock. I followed this instructions in this video: https://www.youtube.com/watch?v=6avEPGWB8E0
Unfortunately, things didn't work out. When I tried flashing the files it kept saying "system not found". Now I'm stuck in recovery forever. If I try to press start, nothing happens. If I scroll up to factory, nothing happens either. If I look at the Bootloader logs, all it says is "failed to validate system image. Boot up failed".
The one good thing is that the phone recognizes being plugged into my computer (Windows 10), so maybe there's a small chance I can get my phone back. If you guys have a solution, please let me know, as I'm pretty distraught right now. Also hoping there's a chance I can get my photos back that are on the device, though that seems unlikely now.
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
ChazzMatt said:
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
Click to expand...
Click to collapse
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Xpwnage123 said:
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Click to expand...
Click to collapse
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Also with custom ROMs you can still run the ROM and UNroot your phone. (I know you can with CM.) No need to go back to stock, unless parent company of Pokemon is clueless and demands stock.
Well, seems they are clueless and doing what Android Pay does:
http://www.xda-developers.com/lates...blocks-rooted-devices-from-entering-the-game/
What Niantic has managed to do with the update is kill off the enthusiasm in users who had root but were not cheating. Root is used for many more things outside of cheating in a game, and to assume that all rooted users are cheaters is just silly.
_____
After some more reading around, it seems Niantic is actually using the SafetyNet checks to check for root. XDA Senior Member MaaarZ found the SafetyNetService being called in the game code. Niantic is really making users jump through the whole nine yards, as this is the same method employed by Android Pay. This means that if you do need to run Pokémon GO on a rooted device, you need to go through the whole Magisk and systemless root way. Or stop playing completely, because that is what Niantic wants you to do.
Click to expand...
Click to collapse
ChazzMatt said:
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Click to expand...
Click to collapse
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Xpwnage123 said:
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Xpwnage123 said:
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
ChazzMatt said:
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Click to expand...
Click to collapse
TheSt33v said:
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
Click to expand...
Click to collapse
Thank you guys. I was able to revive my phone from the dead using your advice. Unfortunately, I lost all of the photos from my trip to Europe, but overall I'm happy my phone is back and running. That will be a lesson to me to be less lazy about backing up my data.
Once again, thank you very much.
Someone over in Resurrection Remix thread got Pokemon Go to work with Root Cloak:
Nitefire77 said:
Pokemon go works on my phone with rootcloak. Wasn't too difficult to get it working
Click to expand...
Click to collapse
You can ask him for details. So, you can still run a custom ROM if you wish...