Guys,
Don't know if this has been posted yet, but I figured I would throw it in here just in case (I searched around and didn't see anything - I know there's a thread out there on flashing a zip over the boot animation, but I saw nothing specific to the BootUp sound. Forgive me if I missed it). You can also manually replace the The MyTouch Boot Screen (the second one that loads with all the gaudy animations) in the same directory as listed below.
(Obligatory 'I'm not responsible for your phone exploding' notice)
Make sure you do your removing/pushing of files from your command prompt while in clockwork recovery - AFTER mounting the system.
In order to remove the uber-irritating T-mobile BootUp sound (must have root and have flashed SlideMEROOT2):
adb shell
cd /system/customize/resource
rm TMO_Bootup_sound.mp3
You can change this sound to something else as well - just rename your own file as named above. Same with the Boot Screen: just replace MyTouch_v8_Final.gif with a gif that is named the same.
To replace the file:
adb push [file location & name] /system/customize/resource
I pulled my gif from here: http://forum.xda-developers.com/showthread.php?t=567291
Nice find with the mp3, will give it a try in a bit.
Thankssss!
Awesome! Doing this tonight after I get done with the Fathers Day activities...
Awesome
It worked perfectly for me. I pulled a GIF of my "Stark Industries" boot animation that someone made for me on the G1 themes forum, and my 'Good evening Mr Stark, how may I assist you" boot sound I made from an Iron Man commercial. I feel like Tony Stark
And to go with it, a quick transformers boot theme. Just because I felt like making one for myself...
Sorry, forgot the desktop wallpaper to go with the transformers boot theme...
The tall one if for the lock screen.
Re: HowTo: Remove/Replace T-Mobile BootUp Sound/Animation
Can you post the stark industries mp3 . Thanks
Sent from my android device using tapatalk
Stark Industries
This is the link to the Stark Industries boot sound from the G1 forum.
http://forum.xda-developers.com/showpost.php?p=6538090&postcount=5
Re: HowTo: Remove/Replace T-Mobile BootUp Sound/Animation
Nice thanks
Sent from my android device using tapatalk
so if I wanted to use the Transformers one I would rename the sound file to "TMO_Bootup_sound" and the .gif to MyTouch_v8_Final to get it to work? and then push it out?
what about the wallpaper zip?do we just install them on the sd card?
Yep
@Ravenwulf yep thats exactly how you do it.
and the wall paper zip just gets put on the sd card right?
everytime I try the following commands it tells me it failed because it is a read only file
adb shell
cd /system/customize/resource
rm TMO_Bootup_sound.mp3
I'm working on a new kit for the transformers theme that also has the animation morph into the locked desktop, and re-timing the sound file.
And, it's done...
This kit needs you Android Mytouch Slide to be rooted.
Copy the files into your tools directory of your android-sdk and CD into it.
Then run the following commands:
adb push autobot.gif /system/customize/resource/MyTouch_v8_Final.gif
adb push transformers-hum.mp3 /system/customize/resource/TMO_Bootup_sound.mp3
Copy the following files to your SD card:
autobot-black.png
autobot-blue.png
autobot-lock.png
autobot-lockFF.png
The black and blue autobot images allow you two choices for backgrounds, while autobot-lock acts as a good lock screen. autobot-lockFF shows an example of how to edit the image to add a name to the bottom bar.
Click to expand...
Click to collapse
Hope this makes it simple enough to use.
(The changes are making the animation shift into the locked screen without text, and making the sound match the animation)
RavenWulf said:
and the wall paper zip just gets put on the sd card right?
everytime I try the following commands it tells me it failed because it is a read only file
adb shell
cd /system/customize/resource
rm TMO_Bootup_sound.mp3
Click to expand...
Click to collapse
That would mean your phone is not rooted. None of the startup animation kits can be used without a rooted phone. Root is what gives you write access.
I know what root is and my phone IS rooted. I was running Legend to Slide until the lack of KB lights was making me nuts (no offense eugene) and am now running SlideMEROOT2 with the Matrix bootloader animation. with the way you are showing the adb commands shouldn't the supplied files overwrite the stock images?
RavenWulf said:
I know what root is and my phone IS rooted. I was running Legend to Slide until the lack of KB lights was making me nuts (no offense eugene) and am now running SlideMEROOT2 with the Matrix bootloader animation. with the way you are showing the adb commands shouldn't the supplied files overwrite the stock images?
Click to expand...
Click to collapse
<frowns> Yes. I never had a problem overwriting even once. Works fine on mine.
You should never be denied write access if you are root. It's just not the way it works. I would advise you can -shell into the phone and delete them first, then add them, but now I'm worried about the way your phone's acting.
Foolish Frost said:
<frowns> Yes. I never had a problem overwriting even once. Works fine on mine.
You should never be denied write access if you are root. It's just not the way it works. I would advise you can -shell into the phone and delete them first, then add them, but now I'm worried about the way your phone's acting.
Click to expand...
Click to collapse
just a possible theory but is it possible that it isn't acting as it should because I am running one of the bootloader animations from here http://forum.xda-developers.com/showthread.php?t=705279
and maybe I need to re-flash SlideMEROOT2 and start fresh to get it to work... am a huge Transfan
RavenWulf said:
and the wall paper zip just gets put on the sd card right?
everytime I try the following commands it tells me it failed because it is a read only file
adb shell
cd /system/customize/resource
rm TMO_Bootup_sound.mp3
Click to expand...
Click to collapse
Raven, Where are you trying those commands from? Are you booting into stock recovery, then applying the update to get to get to clockwork and mounting the system?
jadambpharm said:
Raven, Where are you trying those commands from? Are you booting into stock recovery, then applying the update to get to get to clockwork and mounting the system?
Click to expand...
Click to collapse
straight from the command prompt : adb shell in command prompt
do we need to go into clockwork first? then use the commands Foolish Frost put in post #13
RavenWulf said:
straight from the command prompt : adb shell in command prompt
do we need to go into clockwork first? then use the commands Foolish Frost put in post #13
Click to expand...
Click to collapse
Yes, you do. The system has to be mounted and the only place you can do that from (at the moment) is clockwork. Get into there, mount, open up your command prompt and go from there
I'll update the original post w/ that info.
Related
All,
With the help of @cemian, I was able to successfully port the US Dell Streak (Baseband ending in 31 originally) boot animation to the O2 Android 2.1 Image.
To install, you will need to mount the system folder R/W and replace the bootanimation.zip file in the /system/media folder.
This will get rid of the O2 boot image and replace it with the US Stock Dell Streak animated logo. Enjoy!
**** MODIFIED BOOT ANIMATION *** No more blank screen after the animation completes!!!
how do you mount the system folder R/W ?
Thanks.
Thanks, I didn't even know the 31 Streak had this. The animation is a bit short so it cuts off early and you're left with a black screen for a few seconds, i'm sure it could be extended or looped??
@mrmrmrmr, you have to have root enable on you ROM, but the command is:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock6 /system
@gingernator007, yes you are correct, the animation can be possibly extended and/or looped, the latter is trivial change.
My goal was to keep it as stock as possible, but because the animation system is different, something my have gotten lost int he translation.
ok; so I have root enabled on the ROM. then I have to login with "adb shell" , correct ?
is there any other way ? can I get to the shell directly on the device ? not using the PC.
ok; so I have root enabled on the ROM. then I have to login with "adb shell" , correct ?
Click to expand...
Click to collapse
Yes: "adb shell" is correct.
is there any other way ? can I get to the shell directly on the device ? not using the PC.
Click to expand...
Click to collapse
Yes there is another way, but unfortunately, I am not proficient with any other way except using adb. I believe if you install a terminal app from the market--ConnectBot comes to mind--you should be able to copy the bootanimation.zip file from your SD Card to the /system/media/ folder.
Hope this helps some... May someone else can chime in.
thank you
Works well, cheers pal!
mrmrmrmr said:
ok; so I have root enabled on the ROM. then I have to login with "adb shell" , correct ?
is there any other way ? can I get to the shell directly on the device ? not using the PC.
Click to expand...
Click to collapse
Yes you can use Root Explorer, its £2 but it does the job.
the only other way is really long teminal commands
mistadman said:
To install, you will need to mount the system folder R/W and replace the bootanimation.zip file in the /system/media folder.
This will get rid of the O2 boot image and replace it with the US Stock Dell Streak animated logo. Enjoy!
Click to expand...
Click to collapse
Will it work with 1.6 4399?
If not, could you share the original files of 1.6?
smokku said:
Will it work with 1.6 4399?
If not, could you share the original files of 1.6?
Click to expand...
Click to collapse
@smokku, I am pretty sure the 2.1 boot animation attached to this thread will not work in 1.6. Also, I do not have the original files; someone gave me bits and pieces from the 6601 build (Android OS 1.6) that allowed me to hack together a boot animation for the 2.1 ROM.
If you are savvy enough, and if you are on a 1.6 ROM, you should be able to hack together what you need using the file in this thread along with the original boot animation on your 1.6 ROM.
Good luck and I hope this helps!!
I held off rooting since in got my streak at launch since I had no need for it, but I got quite fed up of the O2 boot screen it looks totally out of place and ugly, so when I saw this post I took the plunge and it was worth it. I am running 2.1 (6941) on contract O2 streak and I used Androot 1.6.1 to root, one click like it said on the tin, then replaced the animation with Root Explorer (as recommended for noobs) and job done 5 mins.
Anyway thanks a lot for the animation looks awesome only shame its quite short though, any more custom versions to come?
Thank you SO much... It was a small thing, but bugging the hell out of me.
mistadman said:
If you are savvy enough, and if you are on a 1.6 ROM, you should be able to hack together what you need using the file in this thread along with the original boot animation on your 1.6 ROM.
Click to expand...
Click to collapse
Code:
# ls /system/media
audio
It's gonna be hard.
Where did you get the 6601 build?
Im looking to take a go at some theme making / startup shows. Ive done some looking but I can't find a definitive guide on pulling the framework-res.apk. I have found some how-too on modifying the files contained inside but most assume you already have a pretty solid understanding of abd. Mine is basic so if someone was willing to right out the abd commands for pulling it, backing it up (im guessing just a right click and copy), and then putting the original / modified (if different) back in, it would be much appreciated.
Not much in the line of themes for the Streak so far, so although it take me a while, im willing to do some work.
Any help is appreciated.
Ok I have been looking around and since no one has provided any info/insight ill post what ive found here and perhaps "someone" could be kind enough to just verify.
Pulling "framework-res.apk":
adb pull /system/framework/framework-res.apk
Pushing "framework-res.apk":
adb shell remount rw
adb push framework-res.apk /system/framework/
I also found this code for remount (not sure which is more appropriate?):
adb shell mount -o rw /dev/block/mtdblock1 /system
Also has anyone tried using this:
http://forum.xda-developers.com/showthread.php?t=737526
i was looking to change the bootscreen and in the process i found 'rootexplorer' together with z4root working great. you can copy the files to sdcard (i use usb, but bluetooth or wifi works also) and from there to the system dir.
dell splash logo
you have themed the dell splash logo @ power on? Sweet! can you tell us where it is located?
maybe a short vid to see it in action.
Yes I cant wait do debrand my streak,
chrisrotolo said:
you have themed the dell splash logo @ power on? Sweet! can you tell us where it is located?
maybe a short vid to see it in action.
Yes I cant wait do debrand my streak,
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=859009
please dont hijack the poor man's thread lol
Ha, ha @da_jojo. I suppose that should be happy that sooomeone posted any reply in this thread. Im going to have a look at the boot animation you posted as that was something else id like to try tackling in the future as well. Although I have to admit I was a little bummed that no one could confirm my questions. Just keeping trying on my own I guess.
Sent from my Dell Streak using XDA App
brunswick000 said:
Ha, ha @da_jojo. I suppose that should be happy that sooomeone posted any reply in this thread. Im going to have a look at the boot animation you posted as that was something else id like to try tackling in the future as well. Although I have to admit I was a little bummed that no one could confirm my questions. Just keeping trying on my own I guess.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
yeah same here.. information sharing is limited to helpdeskfunctionality nowadays lol
the method i used works great and doesnt require a pc to use. the adb commands should be fine i guess.remount the dir should do. im not to sure about the block remount. you can remount system in adb with :
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
after some fiddling i found out that bootanimations installer for droid x works good.
You don't neccessarily need a knowledge of ADB to theme. You could just open up Steve's ROM, edit what you want and sign it again (each .zip inside the update.zip must be signed also).
Then you just flash it through recovery.
Meltus said:
You don't neccessarily need a knowledge of ADB to theme. You could just open up Steve's ROM, edit what you want and sign it again (each .zip inside the update.zip must be signed also).
Then you just flash it through recovery.
Click to expand...
Click to collapse
yu, but i think its more handy to just copy the file over with rootexplorer, for testing. the end-product can then be implented in the update if required , the way you describe it.
Ok sounds good. Ill give it a try tomorrow if I have some down time at work. Cant wait to get to work on something for this beast.
Any one out there that can help me understand the last part of Adb.
lol.
I learned how to use Odin and superoneclick.
Now I am on Adb.
I read all I can on Team Whiskeys and XDA website and other googled websites. I installed everything and did the My computer/system properties/advance/Enviroment Variables/Path entries.
I start ADB and then I do in command prompt "adb devices" and whoopie I see my phone.
NOW WHAT?
No body on the instructions or website that I have read goes past that.
How do I push down a Rom to overwrite the system with the new Rom I want to try?
Hope someone out in the Forum has really done this before and will post how they do it.
Need to find someone smart enough to finish the instructions.
Thanks,
CatfishKnight
with adb you can copy files to your sd card or system without ever having to mount your sd card to your phone. that's the main thing I use it for
for instance, I have a rom named Trigger_281.zip on my desktop, to push it I would do
Code:
adb push Trigger_281.zip /sdcard/Trigger_281.zip
you can also pull files by using "adb pull <location of file on phone>"
and so on.
Furthermore if you ever need shell access you can do "adb shell" and run unix commands from console instead of on the phone
birgertime said:
with adb you can copy files to your sd card or system without ever having to mount your sd card to your phone. that's the main thing I use it for
for instance, I have a rom named Trigger_281.zip on my desktop, to push it I would do
Code:
adb push Trigger_281.zip /sdcard/Trigger_281.zip
you can also pull files by using "adb pull <location of file on phone>"
and so on.
Furthermore if you ever need shell access you can do "adb shell" and run unix commands from console instead of on the phone
Click to expand...
Click to collapse
Thanks for showing me how to push to my phone. Now do I install it. In recovery mode as a zip? I thought adv installed it and I just rebooted and it was installed.
birgertime said:
with adb you can copy files to your sd card or system without ever having to mount your sd card to your phone. that's the main thing I use it for
for instance, I have a rom named Trigger_281.zip on my desktop, to push it I would do
Code:
adb push Trigger_281.zip /sdcard/Trigger_281.zip
you can also pull files by using "adb pull <location of file on phone>"
and so on.
Furthermore if you ever need shell access you can do "adb shell" and run unix commands from console instead of on the phone
Click to expand...
Click to collapse
Thanks for showing me how to push to my phone. Now do I install it. In recovery mode as a zip? I thought adb installed it and I just rebooted and it was installed.
It just moves the file to the phone. You have to flash the file yourself if it is a flashable.
You can push a .jpg file if you want, it doesn't matter, it only moves it.
And I think you're getting confused with the 'adb install' command. You can install NON-system APKs by doing that.
Code:
adb install someprogram.apk
birgertime said:
It just moves the file to the phone. You have to flash the file yourself if it is a flashable.
You can push a .jpg file if you want, it doesn't matter, it only moves it.
And I think you're getting confused with the 'adb install' command. You can install NON-system APKs by doing that.
Code:
adb install someprogram.apk
Click to expand...
Click to collapse
I guess I was confused on what ADB could do.
I thought it could push down a Rom and install it onto the phone.
Then I would disconnect it and reboot the phone and I would have the newer rom installed.
I didn't know that it only pushed the ROM onto the sdcard and then I would install the zip from the phone itself.
Finally I got an answer to my question.
LOL.
I have tried on the team whiskey site to and no one answered it. Also all the stuff I read on it really didn't tell me that either.
I really appreciate your answer in helping me understand it.
I am also using Trigger 2.8 like you. But you said you had Trigger2.8.1 saved??
I have only seen Trigger 2.8 today.
^ birgertime is the developer of Trigger. He is already cooking something new in the kitchen.
s15274n said:
^ birgertime is the developer of Trigger. He is already cooking something new in the kitchen.
Click to expand...
Click to collapse
Duhhh... I missed that... LOL. I am brain fried!!! I have installed Odin, SuperOneClick, and ADM. I have be learning all three but was having trouble with understanding what ADB could do. Been reading lots and lots about it all day. Whew. I am tired. Ever instruction got down to connecting and seeing your phone and then it would end there. Finally I got an answer from Birgertime. Thanks.
I have 4 different roms saved to my phone to switch between if I want too. But I love Trigger 2.8 with Overclock v2. Also I am seeing 9 sats out of 11 on my gps. With Overclock v2 and using CPUBoostPro I am right at 2000 with Quadrant.
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem
Yes, it's possible, and yes, it's pretty much exactly the same process as on your phone. If you've done it there, you can do it on Wear.
Oh, apologies if this is old news to you, but I couldn't find threads on this particular topic, and I'm quite satisfied that it worked, so why not share.
Now, the stock Wear boot animation is great. I personally love it, at least -- so why change it? Well, why do we do most things on XDA? Because we can. Do at your own risk, I take no responsibility if you screw up. Take these notes as suggestions. I mean, they work, but you know. Backups are always a good idea.
tl;dr for people who don't need help with adb:
push the bootanimation.zip to /system/media (back up the original!), then
chmod 644 bootanimation.zip
reboot
done.
Stuff you'll need:
1. An Android Wear device (any should do, I have a Sony Smartwatch 3) that has root access and ADB debugging enabled
2. A custom kernel that has adbd insecure (I used this)
3. ADB drivers on your computer
4. A boot animation. Duh. I used this for testing purposes because the resolution is meh x close enough.
Optional: a file explorer that works on Wear. I use ES.
How to do it (the way I did, I know there are other ways):
1. On your computer: move the .zip file your animation comes in to the folder where you have ADB installed. It's probably something like "C:\Users\yourname\AppData\Local\Android\android-sdk\platform-tools".
2. Open a command window in that location by shift+right clicking on the folder and selecting "Open command window here".
3. Connect your watch to your computer no later than now. If prompted, allow debugging (note that if it's your first time, the prompt should show. If not, check developer settings again).
4. In the command prompt, type
Code:
adb devices
This lists the devices that are connected to your computer. You should see the text "List of devices attached", your watch's serial number, and the text "device" next to it. If you don't, check your drivers.
5. Copy the .zip onto your watch:
Code:
adb push bootanimation.zip /sdcard/
The directory doesn't actually matter, just make sure it's not /system and somewhere you can remember.
6. Why not /system? Because it's, by default, a read-only partition we can't access via normal adb commands. Yet that's where that zip is headed. This is where the adbd insecure kernel comes in: with it, you can remount /system as read-write. For that, enter the adb shell:
Code:
adb shell
It'll show (don't write this!)
Code:
[email protected]:/ $
To get the root privileges you'll need, type
Code:
su
What you should get is
Code:
[email protected]:/ $ su
[email protected]:/ #
The # means you're rooted. If it shows without typing "su," great.
7. Remount /system as read-write by typing the following:
Code:
mount -o rw,remount /system
8. We can now alter the partition, and we'll start by backing up your stock boot animation. To do that, we need to "move" the file to an identical file with a different name. If that sounds like it doesn't make sense, that's because it doesn't -- it's stupid, but adb shell doesn't have a rename command. This is to avoid the stock animation from getting overwritten by the new one if anything goes wrong. Anyway, to accomplish that, type
Code:
mv /system/media/bootanimation.zip bootanimation.zip1
This changes the animation's extension to .zip1, which doesn't exist. The point of this is that Android looks for /system/media/bootanimation.zip when booting up, so "bootanimation.zip1" gets ignored and is out of our way. If you'd reboot the watch now, there would be no boot animation, just a plain "Android" text (or as is the case with my 320x320 SW3, "NDROI")
9. Now we'll need to move our new animation to replace the old one. To accomplish that, use the aforementioned "move" command:
Code:
mv /sdcard/bootanimation.zip /system/media/
10. Finally, to make the animation actually display, we'll need to give it proper permissions, which are rw-r-r. "chmod" is the command that alters permissions, rw is represented by a six, and r by a four.
Code:
chmod 644 /system/media/bootanimation.zip
11. Close down /system
Code:
mount -o ro,remount /system
12. Done! Reboot your watch and enjoy your new boot animation!
Worked thanks
Gave this a try on the train on my way home from work and it worked a treat thanks now off to find some more suitable boot anims to play around with
Smackedgnome said:
Gave this a try on the train on my way home from work and it worked a treat thanks now off to find some more suitable boot anims to play around with
Click to expand...
Click to collapse
Good to hear! Now all we need is that the artistically inclined among us make some awesome-looking animations for our itty-bitty screens.
If you find any, please post them here so I can add them to the OP.
[NUMINIT] said:
Now all we need ... some awesome-looking animations for our itty-bitty screens.
If you find any, please post them here so I can add them to the OP.
Click to expand...
Click to collapse
Went looking for them and found a few, thought that I would share.
There appears to be a size limit to what boot animation can be used (at least with my Sony Smartwatch 3), the biggest file used being ~3000KB.
Watchdogs
view here
https://www.youtube.com/watch?v=ZhH-4zsMB5w
This is the one I currently use
Cyanogenmod12
(sorry dont have a link/ gif - it looks good trust me )
Nexus 7 boot animation
(no link either sorry and tbh havent tried it yet - theoretically works)
I made none of these myself, they belong to the original owners. (I just cant remember where from lol)
Files are aptly named, dont forget to rename to bootanimation.zip
Enjoy
On my aw2 huawei 2 sport 4g sawshark, the time shows during the boot process. Any way to remove for aw2 or add for aw1?
Sent from my amami using XDA Labs