I'm purchased my Moto X (XT1060) on Verizon when it just came out), it came with 4.2.2 and I rooted shortly after that) then Android 4.4 KitKat came out, so I jumped on that) and now 4.4.2 (and possibly soon 4.4.4), unfortunately since root wasn't available for 4.4.2 I never went to it but I really looking forward to 4.4.4 or Android L.
at the end of the day my Moto X now is running Android 4.4 KitKat and it's rooted using one of @jcase methods.
... and as few others, going to Android 4.4 KitKat unfortunately meant shorten your battery life((
now I'd like to try out following : MOTO X - Clear Cache Partition and even though I'm pretty sure it won't do me any good, I still want to give it a go.
I'm issuing
Code:
adb reboot bootloader
and I end up inside of my bootloader, over there I selecting "recovery" yet my phone just ends up rebooting itself(
What am I doing wrong? How else I can do that? I also tried following:
Code:
fastboot erase cache
... which I'm not sure as it does anything to my phone since after reboot, my phone goes to Android without rebuilding cache normally like it'd do it in any other time I reboot my phone.
If you're battery is the same now as when you first installed 4.4....clearing cache won't change anything.
But if you want to...sorry, unfamiliar with locked root methods....do you have a custom recovery you can clear cache with?
Or....try an app, since you're rooted. There's tonnes on the play store.
Related
Just got the Verizon Moto X and now I am attempting to update it to the latest version (Android 4.4.2). I am currently on Android 4.2.2, which came with the phone out of the box. Whenever I go to About Phone > System Updates, it says "Checking for an available update" for a second and then the error message "An unexpected error has occured. Please try again later." pops up. I tried talking to Verizon (they redirected me to Motorola) and Motorola, where I was sent through the standard troubleshooting steps by someone who clearly didn't know anything about the phone. I tried restarting the phone, wiping the phone's cache, and looking for updates through the Motorola Device Manager on my computer (which said that my phone was up to date, even though it clearly isn't). Is there anything else I can do before I try a factory reset? I would prefer to download the OTA, but I have experience with rooting and installing custom ROMs, so if I have to install the update manually, I will (if it gets to that step, I will probably end up installing the 4.4.4 update which got sent out to soak testers).
mikestrong19 said:
Just got the Verizon Moto X and now I am attempting to update it to the latest version (Android 4.4.2). I am currently on Android 4.2.2, which came with the phone out of the box. Whenever I go to About Phone > System Updates, it says "Checking for an available update" for a second and then the error message "An unexpected error has occured. Please try again later." pops up. I tried talking to Verizon (they redirected me to Motorola) and Motorola, where I was sent through the standard troubleshooting steps by someone who clearly didn't know anything about the phone. I tried restarting the phone, wiping the phone's cache, and looking for updates through the Motorola Device Manager on my computer (which said that my phone was up to date, even though it clearly isn't). Is there anything else I can do before I try a factory reset? I would prefer to download the OTA, but I have experience with rooting and installing custom ROMs, so if I have to install the update manually, I will (if it gets to that step, I will probably end up installing the 4.4.4 update which got sent out to soak testers).
Click to expand...
Click to collapse
Do NOT upgrade until you've read another 24 hours on this board!!!!! I think you should take a second look at your status and see if you misread 4.4.2 as 4.2.2
If I may ask, why not update?
mikestrong19 said:
If I may ask, why not update?
Click to expand...
Click to collapse
If you dont mind having an unrootable phone than update.
4.2.2 and 4.4 is fully rootable and able to disable write protection, 4.4.2 and newer is not. once you upgrade past 4.4 you lose ability to gain write and root.
doitinthedirt said:
If you dont mind having an unrootable phone than update.
4.2.2 and 4.4 is fully rootable and able to disable write protection, 4.4.2 and newer is not. once you upgrade past 4.4 you lose ability to gain write and root.
Click to expand...
Click to collapse
Oh OK, that makes sense. Thanks for the info. I have another phone that I use for rooting, ROMs, etc. The Moto X is currently my daily phone, and I need it to be stable, so I am not worried about rooting or anything like that. Just want the latest stock Android version on there.
I just talked to Motorola on the phone again, and they went through the same standard checklist (restart, wipe cache, factory reset -- none of which worked). At this point, they are going to exchange my current phone for a new one, which works out for me. The Moto X I bought was used, so I am getting a new phone for a used price in a convoluted way.
mikestrong19 said:
Oh OK, that makes sense. Thanks for the info. I have another phone that I use for rooting, ROMs, etc. The Moto X is currently my daily phone, and I need it to be stable, so I am not worried about rooting or anything like that. Just want the latest stock Android version on there.
I just talked to Motorola on the phone again, and they went through the same standard checklist (restart, wipe cache, factory reset -- none of which worked). At this point, they are going to exchange my current phone for a new one, which works out for me. The Moto X I bought was used, so I am getting a new phone for a used price in a convoluted way.
Click to expand...
Click to collapse
Wow, what a waste. You could have just flashed the entire STOCK SBF as per the Return to Stock thread, and avoided costing Moto money, and hence raising the prices for everybody... :/
This would have repaired any filesystem corruption/damage, which is the only conceivable thing that might have caused your issue.
Your new one will probably have 4.4.2....which means no write protection disabling.
D'oh!
---------- Post added at 07:17 PM ---------- Previous post was at 07:17 PM ----------
You could have had FULL root on 4.2.2.
Hi people.
One week ago I bought my phone. Unlocked bootloader and rooted my device. I was running stock 4.4.4, from Personal - Argentina.
Today I was messing with Titanium BackUp and used the feature "integrate updates" wich made apps like google play, hangouts and Motorola Modality Services to crash repeatedly. I read that I needed to restore to the stock rom...
I couldnt find any file from the 4.4.4 so I decided to get back to 4.4.2, found on sbf.droid-developers
I followed this tutorial mark.cdmaforumscom/MotoX-ReturnToStock html step by step and now my phone is almost dead.
When I turn my phone, it shows the boot screen (the unlocked bootloader message), then the motorola animation and then goes black.
I can reboot into fastboot but cant enter into the recovery mode (when I enter into recovery appears the stock recovery image but no text or option)
Can you guys help me with this problem? Is there a way to save my phone?
Thanks in advance. If you need more info just ask
luizdf said:
Hi people.
One week ago I bought my phone. Unlocked bootloader and rooted my device. I was running stock 4.4.4, from Personal - Argentina.
Today I was messing with Titanium BackUp and used the feature "integrate updates" wich made apps like google play, hangouts and Motorola Modality Services to crash repeatedly. I read that I needed to restore to the stock rom...
I couldnt find any file from the 4.4.4 so I decided to get back to 4.4.2, found on sbf.droid-developers
I followed this tutorial mark.cdmaforumscom/MotoX-ReturnToStock html step by step and now my phone is almost dead.
When I turn my phone, it shows the boot screen (the unlocked bootloader message), then the motorola animation and then goes black.
I can reboot into fastboot but cant enter into the recovery mode (when I enter into recovery appears the stock recovery image but no text or option)
Can you guys help me with this problem? Is there a way to save my phone?
Thanks in advance. If you need more info just ask
Click to expand...
Click to collapse
Dude...this is sad.
You say that you followed @KidJoe 's excellent tutorial, but you missed the BIG ORANGE warning???
"NOTE: If you have Android 4.4.2 or later on your Moto X, do NOT attempt to downgrade the ROM version on your phone! Updated parts included with the 4.4.2 and above prevent successful downgrading to a lower version, causing you to either brick your phone, or set you up to brick later!"
You have very few options at this point. Any attempt to recover is going to leave you with mismatched partitions because you can NOT downgrade motoboot (bootloader) or gpt.bin (partition table).
Why oh why didn't you heed the warning?
Now your only option is to try using the manual method (OPTION 5) to flash everything from the 4.4.2 SBF except gpt.bin (which will leave you in a mismatched, but MAYBE working state) and hope that the 4.4.4 full SBF is released soon. Until then you will have mismatched partitions. And if you successfully flash the 4.4.2 ROM with the mismatched gpt.bin, you have a very good chance of bricking AGAIN if you take the OTA to 4.4.4. Don't do it! Assuming you are even able to get back to 4.4.2 and it works, don't take the OTA. Stay on 4.4.2 until the full 4.4.4 SBF is released....
It was a silly mistake. I didnt paid attention to that line... :/
Fortunately I had the problem solved by following the Moto X > Moto X General > [GUIDE][VIDEO] Moto X - Return to 100% stock (which have different lines for manual flashing)
I guess this is the line responsible for solving the problem:
fastboot oem fb_mode_clear
The system seem to run normally and I already updated again to 4.4.4 (I didnt seen your warning before...). Is there a way to check if everything is ok?
Thank you so much for your answer.
luizdf said:
It was a silly mistake. I didnt paid attention to that line... :/
Fortunately I had the problem solved by following the Moto X > Moto X General > [GUIDE][VIDEO] Moto X - Return to 100% stock (which have different lines for manual flashing)
I guess this is the line responsible for solving the problem:
fastboot oem fb_mode_clear
The system seem to run normally and I already updated again to 4.4.4 (I didnt seen your warning before...). Is there a way to check if everything is ok?
Thank you so much for your answer.
Click to expand...
Click to collapse
You are welcome. It looks like you got lucky. Just beware that the next OTA you accept could leave your device in a semi-bricked state. Keep your fingers crossed that all is well. There is no way to tell until you attempt to take the next OTA that is released (whenever that happens).
So Motorola just rolled out the Android L 5.1 OTA update. I never rooted my Moto X before, just unlocked the bootloader on Android L 5.1, but i'm having problems booting/flashing custom recovery on fastboot as it shows permission denied. Anyone help?
If fastboot says the permission is denied, then it sounds like you didn't unlock the bootloader properly. Do you have a developer edition or otherwise unlockable device?
Sent from my Nexus 6
imnuts said:
If fastboot says the permission is denied, then it sounds like you didn't unlock the bootloader properly. Do you have a developer edition or otherwise unlockable device?
Sent from my Nexus 6
Click to expand...
Click to collapse
Thanks for the reply but i managed to root it. Seemed like i was using the wrong adb and fastboot files. Anyway i rooted my Moto X 2013 on Android L V5.1 successfully but i'm facing this problem of slow boot time now. Any idea what might causing it? I rooted the stock Android L and installed SuperUser, Xposed Framework etc. i started installing a couple of apps like motox led & Font changer etc. With every reboot the devices keeps on taking longer time to boot to the home screen.
Teejay94 said:
Thanks for the reply but i managed to root it. Seemed like i was using the wrong adb and fastboot files. Anyway i rooted my Moto X 2013 on Android L V5.1 successfully but i'm facing this problem of slow boot time now. Any idea what might causing it? I rooted the stock Android L and installed SuperUser, Xposed Framework etc. i started installing a couple of apps like motox led & Font changer etc. With every reboot the devices keeps on taking longer time to boot to the home screen.
Click to expand...
Click to collapse
This is quite normal and has to do with the RunTime being ART vs Davlik. In KitKat we had a choice between the two but with Lollipop it's only ART now. The thinking is that the device runs more smoothly with ART at the expense of longer boot time.
Greetings,
Just bought a VZW Moto X 2014 loaded with 5.0. Unfortunately, right after I powered it on, it pulled down the 5.1 OTA, though it appears to have deferred the installation, which is good, as I intend to give it the MOFO treatment shortly.
Questions:
1. How can I continue to defer the installation?
2. If I do a factory reset (I still have another phone to use), assuming the 5.1. didn't install yet, will it wipe the download?
3. If I can factory reset and eliminate the 5.1 download, how can I avoid this repeating? With my original Moto X, I was able to freeze the MotoOTA after I rooted it.
TIA,
GG
Garageguy05 said:
Greetings,
Just bought a VZW Moto X 2014 loaded with 5.0. Unfortunately, right after I powered it on, it pulled down the 5.1 OTA, though it appears to have deferred the installation, which is good, as I intend to give it the MOFO treatment shortly.
Questions:
1. How can I continue to defer the installation?
2. If I do a factory reset (I still have another phone to use), assuming the 5.1. didn't install yet, will it wipe the download?
3. If I can factory reset and eliminate the 5.1 download, how can I avoid this repeating? With my original Moto X, I was able to freeze the MotoOTA after I rooted it.
TIA,
GG
Click to expand...
Click to collapse
Same thing. Freeze MotoOTA after rooting and clear your cache to get rid of the OTA file.
Thanks.
Do I need to worry about the update self-executing at some point, similar to what I saw on my HTC One? Or will it stay dormant until it is activated by the user?
GG
Garageguy05 said:
Thanks.
Do I need to worry about the update self-executing at some point, similar to what I saw on my HTC One? Or will it stay dormant until it is activated by the user?
GG
Click to expand...
Click to collapse
Not sure if it will. Best bet is to clear the cache once you freeze MotoOTA that way it will delete the OTA sitting on your device.
After restoring my Pure Edition Moto X to stock recovery and unrooting it, every time I try to update to 6.0 my Moto X it show the android guy with the software installing for a few seconds until it flashes on the screen "Error!". After that, the phone starts back at the homescreen still on 5.1.
datwhiteguy said:
After restoring my Pure Edition Moto X to stock recovery and unrooting it, every time I try to update to 6.0 my Moto X it show the android guy with the software installing for a few seconds until it flashes on the screen "Error!". After that, the phone starts back at the homescreen still on 5.1.
Click to expand...
Click to collapse
Something else in your phone is not stock. You have to be 100% unmodified to take the OTA. This means no xposed, no root, no modifications to files in system with root, no busybox, etc.
You have 2 choices. Undo whatever it is that is modified(if you remember what is modified). Or you can flash the full 5.1 system image to revert completely back to stock.