I changed my clogo from the one I made with MotoMaker when I got my phone. It recently reverted back to the Motomaker one. At the same time, it changed the boot animation from the animated globe, to a winter themed animation. Anyone know how and why this happened?
I don't think the phone has updated via any OTA's, right now it's rooted 4.4 with SlapMyMoto.
Probably has to do with the app that automatically changes the boot animation depending on the date.
Thanks, any ideas which app that is/where those extra (backup) clogo files are kept?
Related
Don't know if this has been mentioned yet, but I thought I'd try to contribute... I flashed liquid today and ended up hating the boot image but loving the ROM. So as I was contemplating my options I remembered I had jrummy's Root Tools from my Droid x. Since jrummy usually builds for Motorola's[?] It hadn't crossed my mind before but Root Tools does have some alternate boot images available and an option to back up you current image. Long story short root tools will work to change boot image on tb. Still wondering if notification bar editor will work since it has only been tested on Motorola's and apparantly that messes with some framework stuff which could have some serious consequences.
*edit* font packs also work.
Sent from my ADR6400L using XDA App
I am rooted and my bootloader is unlocked. I got rid of the bootloader unlocked warning by flashing the original kit kat logo.
Before I did that though, I erased clogo and then I think I over wrote it with the kit kat logo file. Anyhow, I don't get the Kit Kat easter egg when I tap Android Build repeatedly. I suppose erasing clogo and overwriting it messed that up because the only other thing I did was overwrite the entitlement services apk so I could wifi tether for free but I can't imagine that would have anything to do with the kit kat easter egg.
What is the best way for me to try to fix this?
I am mostly concerned about getting back to stock for the OTA and I clearly did something that is not stock.
Cozume said:
I am rooted and my bootloader is unlocked. I got rid of the bootloader unlocked warning by flashing the original kit kat logo.
Before I did that though, I erased clogo and then I think I over wrote it with the kit kat logo file. Anyhow, I don't get the Kit Kat easter egg when I tap Android Build repeatedly. I suppose erasing clogo and overwriting it messed that up because the only other thing I did was overwrite the entitlement services apk so I could wifi tether for free but I can't imagine that would have anything to do with the kit kat easter egg.
What is the best way for me to try to fix this?
I am mostly concerned about getting back to stock for the OTA and I clearly did something that is not stock.
Click to expand...
Click to collapse
Use rsdlite to convert back to stock.
MOTO X Slapped
---------- Post added at 02:10 AM ---------- Previous post was at 02:08 AM ----------
Cozume said:
I am rooted and my bootloader is unlocked. I got rid of the bootloader unlocked warning by flashing the original kit kat logo.
Before I did that though, I erased clogo and then I think I over wrote it with the kit kat logo file. Anyhow, I don't get the Kit Kat easter egg when I tap Android Build repeatedly. I suppose erasing clogo and overwriting it messed that up because the only other thing I did was overwrite the entitlement services apk so I could wifi tether for free but I can't imagine that would have anything to do with the kit kat easter egg.
What is the best way for me to try to fix this?
I am mostly concerned about getting back to stock for the OTA and I clearly did something that is not stock.
Click to expand...
Click to collapse
Here you go. http://forum.xda-developers.com/showthread.php?p=45634726
MOTO X Slapped
[email protected] said:
Use rsdlite to convert back to stock.
MOTO X Slapped
Click to expand...
Click to collapse
ok, will that completely put me back to stock in other words, reverse any changes I made?
Also, would I have to reverse the changes I made to the entitlement services apk manually?
Cozume said:
ok, will that completely put me back to stock in other words, reverse any changes I made?
Also, would I have to reverse the changes I made to the entitlement services apk manually?
Click to expand...
Click to collapse
I came from a gs4 and we had Odin. Looks like rsdlite is almost the same thing. You will download your needed firmware which will have everything you need to go back to stock. No need to mess with anything because flashing the XML file should flash everything back to original stock.
MOTO X Slapped
---------- Post added at 02:17 AM ---------- Previous post was at 02:13 AM ----------
Cozume said:
ok, will that completely put me back to stock in other words, reverse any changes I made?
Also, would I have to reverse the changes I made to the entitlement services apk manually?
Click to expand...
Click to collapse
Follow instructions to the T. I used rsdlite to downgrade. I had to modify the XML file but I was on 4.4 and reverted back to 4.2 and ota back to 4.4
MOTO X Slapped
Don't you click the version number(4.4.2) to get the easter egg, not the build version?
Steve-x said:
Don't you click the version number(4.4.2) to get the easter egg, not the build version?
Click to expand...
Click to collapse
That doesn't work for me either. The screen dims on me but then no animation starts. It is the same with the tapping the version number as it is with tapping the build number.
Clearly whatever I did with clogo cracked my easter egg. I don't care about that so much as I want to make sure I can revert back to stock if necessary. Looks like I can flash the firmware once it becomes available, but I am worried about accidentally accepting the OTA when I am not stock.
I am on Verizon and they haven't even started the soak test yet, but I want to get back to stock soon.
If I've learned anything the past couple of days, it's that I'm an idiot.
I rooted my Moto X. I mounted system as R/W. Changed density to 213.
Now my phone refuses to boot at all. It turns on, flashes the Bootloader Unlocked thing, and then it cuts off. Can't get into recovery, but I'll keep trying.
Am I screwed?
Thanks in advance,
Giggybyte
Can u get to Fastboot?
Sent from Moto X
Fastboot your models firmware.... Same version you're on now. Or try rsdlite.
Assuming you can get either working.
Good luck!
I think rsdlite will wipe everything tho.... Be warned.
Here's a guide, see the return to stock section. You can leave data in tact if you want the fastboot way. See notes at bottom of the return to stock section for how to do that.
http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358
(Apologies if you already know all this).
After a million tries, I managed to boot into recovery. Thakfully, I had TWRP, so all I had to do was restore a backup.
Why don't newer versions of Android like custom densities? (and is there any way to get a custom density working?) I almost bricked my Nexus 10 the same way, just by changing the density. On Gingerbread, I could change my density to just about anything and I could reboot and see the effects. It seems Jelly Bean/Kit Kat has no support for it at all.
use app settings and xposed, changing android system will change the base density for all apps.
xposed has a safe mode if something doesnt like something else
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).
I'm having an issue changing the boot animation for my e5 plus
I flashed a new animation and it plays in this order The one i flashed, moto, metro.. Is there anyway to get rid of the moto and metro boot logos so i just see the one i flashed?
Ofcourse 5 minutes after i decide to ask for help I Figure it out.
For anybody who wants to do this as well get a root brower and go to oem/metropcs/media and delete bootanimation.zip in there.