Related
How would it be able to do this? I've seen terminal codes floating around, but none of them look like they'd be replacing the proper files for a cupcake build (old RC33 builds I believe, long lost now!)
I'm running TheDude's 1.3 RC2. I've seen plenty of ADB commands, however I've never been able to get ADB to work on my computer, and I don't feel like putting more pointless hours into it
So how would the terminal commands work, and what would the pre-requisites for the files have to be? Thanks!
http://forum.xda-developers.com/showthread.php?t=467693 Im pretty sure all you need is fastboot not adb for splash1 the animated splash just requires you to resign an update.zip http://forum.xda-developers.com/showthread.php?t=467693
crotalusfreak said:
http://forum.xda-developers.com/showthread.php?t=467693 Im pretty sure all you need is fastboot not adb for splash1 the animated splash just requires you to resign an update.zip http://forum.xda-developers.com/showthread.php?t=467693
Click to expand...
Click to collapse
I'm pretty sure it uses ADB, hence why I'm asking...Fastboot IS ADB
yea fastboot is the only other way that I know of!!
this is where i downloaded the tools for creating your own boot image!
http://www.modmygphone.com/forums/downloads.php?do=file&id=1471&act=down
this is the link that teaches on how to make one and im pretty sure there is one here in the forums!
http://modmygphone.com/forums/showthread.php?t=10461
if you need help PM me ill take you step by step!
or email [email protected]
lukekirstein said:
I'm pretty sure it uses ADB, hence why I'm asking...Fastboot IS ADB
Click to expand...
Click to collapse
it wont use ADB, fastboot is like an alternate route...
Drizzy Drake Rogers said:
yea fastboot is the only other way that I know of!!
this is where i downloaded the tools for creating your own boot image!
http://www.modmygphone.com/forums/downloads.php?do=file&id=1471&act=down
this is the link that teaches on how to make one and im pretty sure there is one here in the forums!
http://modmygphone.com/forums/showthread.php?t=10461
if you need help PM me ill take you step by step!
or email [email protected]
Click to expand...
Click to collapse
Step number two of those directions: "2. Get ADB setup and working. Read here. "
Let's clarify. I cannot get ADB to work, at all, on my computer. Fastboot doesn't work because I can't get ADB to work. Moreso, I just realized that I can't even find my data cord.
Either way, the point of my post is to find a way to change the boot animation at start up, without having to use anything but the phone and maybe some photo editing software.
So how can we do this?
You do not have to have the whole sdk(adb etc..) for fastboot to work you do have to have a driver running for android found in the sdk or here http://dl.google.com/android/android_usb_windows.zip .
The boot animation is found in /system/framework/framework-res.apk/assets/images,android-logo-mask.png and android-logo-shine.png are the images you wanna edit.Dont believe you can get it back on your phone without the sdk set up with adb working though as you will either have to resign an update or push the edited files back somehow.
Edit:without a data cord I think this is an impossibility I dont think you can go through the process needed on your phone,dont hold me to that though good luck man.
crotalusfreak said:
You do not have to have the whole sdk(adb etc..) for fastboot to work you do have to have a driver running for android found in the sdk or here http://dl.google.com/android/android_usb_windows.zip .
The boot animation is found in /system/framework/framework-res.apk/assets/images,android-logo-mask.png and android-logo-shine.png are the images you wanna edit.Dont believe you can get it back on your phone without the sdk set up with adb working though as you will either have to resign an update or push the edited files back somehow.
Edit:without a data cord I think this is an impossibility I dont think you can go through the process needed on your phone,dont hold me to that though good luck man.
Click to expand...
Click to collapse
Alright, I just confirmed the location on the phone. So if I upload a file onto my SD card, and overwrite it through Terminal, what do you think that'll do? I'm not big into the Themes section, I'm into the Development section, so I'm not sure what overwriting will do to my phone.
Actually you might be able to get away with that.Try backing up framework res in terminal type:
$su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#cp -r /system/framework/framework-res.apk /sdcard
Now the .apk you want is on your sdcard root pull that onto a computer unzip it with 7zip.In the framework-res folder there are some more folders go to assets then images edit those two images to your liking.Then go back to your framework-res.apk that you backed up add .zip to the end,right click it and choose open or explore navigate back to the images folder and paste your edited boot images in there.Now remove .zip so it is framework-res.apk again put that back on your sd cards root.Go to terminal and type
$su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#cp -f /sdcard/framework-res.apk /system/framework
#reboot
If all goes well that should work.
crotalusfreak said:
Then go back to your framework-res.apk that you backed up add .zip to the end,right click it and choose open or explore navigate back to the images folder and paste your edited boot images in there.Now remove .zip so it is framework-res.apk again put that back on your sd cards root.
Click to expand...
Click to collapse
Lost you at naming it as a .zip. I can't explore or open the file, as Windows Vista doesn't know how to handle it. Any ideas?
lukekirstein said:
Lost you at naming it as a .zip. I can't explore or open the file, as Windows Vista doesn't know how to handle it. Any ideas?
Click to expand...
Click to collapse
right click-> open with -> WinRAR
Or go to Folder Options and uncheck "Hide extensions for known filetypes" (you should do that for all folders.... its a bad idea not to because a virus may look like *.doc instead of *.doc.exe anyways its also more convenient)
does anyone know how to change the boot image for a rogers g1 none of these things work for me i bricked my last phone a week ago cause someone said it would work
jokefox said:
does anyone know how to change the boot image for a rogers g1 none of these things work for me i bricked my last phone a week ago cause someone said it would work
Click to expand...
Click to collapse
Well if you're bricking phones, I wouldn't recommend trying it again
Ok so i have looked at all the other posts on how to change the boot screen animation, but none of them seem to work. My phone is running on Android 2.2. Does anybody have any ideas on what i should do?
I JUST did this and it worked for me. I am on the 8/1 2.2 leak as well.
Plug in phone
reboot to recovery
Code:
adb reboot recovery
Once booted in to recovery do
Code:
adb shell
mount -a
It will give you this error. Thats fine (It's just saying it couldnt mount the sdcard which we dont need right now.)
Code:
~ # mount -a
mount -a
mount: mounting /dev/block/mmcblk1 on /sdcard failed: Invalid argument
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: No such file or directory
now type exit to get back to your computer prompt.
Now push your bootanimation.zip you want to /system/customize/resource
Code:
adb push bootanimation.zip /system/customize/resource
now now get back in to adb shell and type
Code:
cd /system/customize/resource
then ls *.zip and it should look like this. l = lowercase L
Code:
/system/customize/resource # ls *.zip
ls *.zip
bootanimation.zip VZW_bootanimation.zip
Now we want to rename the vzw boot animation to .back to save it
Code:
mv VZW_bootanimation.zip VZW_bootanimation.back
Then we want to rename the new bootanimation to the vzw bootanimation
Code:
mv bootanimation.zip VZW_bootanimation.zip
OPTIONAL STEP: IF YOU DONT WANT THE DROID SOUND ON BOOT
Code:
mv Droid.mp3 Droid.back
type exit and adb reboot . It should now boot with your new boot animation.
Ok so i just did that twice and every time i try to all it does reboot my phone and its all the same nothing changed
Check where I've been posting. Somewhere along the way I was in a thread that worked for me. I just can't remember where.
Utopia73 said:
Ok so i just did that twice and every time i try to all it does reboot my phone and its all the same nothing changed
Click to expand...
Click to collapse
so you have a bootanimation.zip downloaded to the folder you have adb at? and you followed my steps EXACTLY?
So is it still just showing the stock boot animation?
zerf said:
so you have a bootanimation.zip downloaded to the folder you have adb at? and you followed my steps EXACTLY?
So is it still just showing the stock boot animation?
Click to expand...
Click to collapse
Yes i have everything in the right spot, and followed the steps exactly. I did once more and the animation was gone, now all there is, is a black screen.
Utopia73 said:
Yes i have everything in the right spot, and followed the steps exactly. I did once more and the animation was gone, now all there is, is a black screen.
Click to expand...
Click to collapse
boot your phone to recovery and then adb shell then run this for me and paste in your output.
Code:
ls -l /system/customize/resource/*.zip
zerf said:
boot your phone to recovery and then adb shell then run this for me and paste in your output.
Code:
ls -l /system/customize/resource/*.zip
Click to expand...
Click to collapse
Ok did that. Nothing happened
sorry forgot to tell you to either run mount -a or go in the partitions menu of your phone and mount /system
zerf said:
sorry forgot to tell you to either run mount -a or go in the partitions menu of your phone and mount /system
Click to expand...
Click to collapse
Ok sweet that worked! Although its not the animation i downloaded hmm... oh well this one is cool too.
Utopia73 said:
Ok sweet that worked! Although its not the animation i downloaded hmm... oh well this one is cool too.
Click to expand...
Click to collapse
haha ok.. not sure how you got an animiation you didnt download.... but glad its working. Im guessing you missed the step at the top of my instructions that says mount -a after you adb shell in the first time but anyway let me know if you have any more issues.
zerf said:
haha ok.. not sure how you got an animiation you didnt download.... but glad its working. Im guessing you missed the step at the top of my instructions that says mount -a after you adb shell in the first time but anyway let me know if you have any more issues.
Click to expand...
Click to collapse
Well i saw that...maybe its another mount but instead of mounting in prompt i just went to the partitions menu and did it there. Thank you very much!
Ok i have one last question.
So now that the boot screen has been changed this is what i get when i try to change it again...
Code:
cannot stat 'bootanimation.zip' : No such file or directory
And i can see the file in the folder....so now what?
Utopia73 said:
Ok i have one last question.
So now that the boot screen has been changed this is what i get when i try to change it again...
Code:
cannot stat 'bootanimation.zip' : No such file or directory
And i can see the file in the folder....so now what?
Click to expand...
Click to collapse
where are you seeing this (what directory) and what command are you trying to run?
Not sure what version of 2.2 you're running. I know on SkyRaider you can't put your boots in resource anymore. They now reside in /system/media. You'd need to:
Code:
adb push bootanimation.zip /system/media/
You can also push a custom sound to the same folder, outside of the zip. I'll also take this as an opportunity to shamelessly plug the boot animation I created for SkyRaider. It can be found in the Goodies section of ROM Manager.
zerf said:
where are you seeing this (what directory) and what command are you trying to run?
Click to expand...
Click to collapse
I was trying to run
Code:
adb push bootanimation.zip /system/customize/resource
Ok, now its saying
Code:
adb push bootanimation.zip /system/customize/resource
failed to copy 'bootanimation.zip' to '/system/customize/resource/bootanimation.zip': No space left on device
So maybe i tried to many times or something.
vbhines said:
Not sure what version of 2.2 you're running. I know on SkyRaider you can't put your boots in resource anymore. They now reside in /system/media. You'd need to:
Code:
adb push bootanimation.zip /system/media/
You can also push a custom sound to the same folder, outside of the zip. I'll also take this as an opportunity to shamelessly plug the boot animation I created for SkyRaider. It can be found in the Goodies section of ROM Manager.
Click to expand...
Click to collapse
I tried that too, now its saying
Code:
adb push bootanimation.zip /system/customize/resource
failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip': No space left on device
Not sure what version of 2.2 you're running. I know on SkyRaider you can't put your boots in resource anymore. They now reside in /system/media. You'd
Click to expand...
Click to collapse
I tried that too, now its saying
adb push bootanimation.zip /system/customize/resource
failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip': No space left on device
Click to expand...
Click to collapse
You have to push it while in Recovery until we have s-off/full NAND. If you're already doing it in Recovery, make sure you've mounted /system first.
Sent from my ADR6300 using XDA App
I don't understand why this won't work. I'm running the stock 2.2 rom and I've tried all the correct directories like system/media or system/customize/resources and still the boot screen won't change. Somewhere along the way I lost my original boot screen too, so now all I have it the words "android" when it boots up.
Any ideas on how to make this work other than doing a restore?
Umm, you should have the PB zip file in the SD card, go to bootloader, have it update, and then it should work. o.o
AKHincredible said:
Umm, you should have the PB zip file in the SD card, go to bootloader, have it update, and then it should work. o.o
Click to expand...
Click to collapse
Negative. Bootanimations are not flashed as a PB31IMG. You're confusing it with Splash1.
OP- what are you naming the zip? VZW_bootanimation.zip or bootanimation.zip? If you're stock 2.2, it should be the former and placed in system/customize/resource, IIRC.
Problem solved, flashed incredibly re-engineered rom. Used adb to push bootanimation.zip. It worked. Pushed android_audio.mp3, didn't work. Its probably needing to be named VZW_Droid.mp3 or something, but I don't really care for sound.
All else fails, flash a custom rom.
PS: A ideas why xda's search function hasn't worked for days? EPST doesn't work at all in this rom and I'm being forced to use qpst, which lacks some of the features I'm looking to edit.
The audio needs to be named boot_audio.mp3 for it to work correctly.
got bored and tried pushing a new boot audio. So far boot_audio.mp3 doesn't work, nor VZW_Droid.mp3. I'm still trying more names
rotaryboots said:
got bored and tried pushing a new boot audio. So far boot_audio.mp3 doesn't work, nor VZW_Droid.mp3. I'm still trying more names
Click to expand...
Click to collapse
I use root explorer to do things like this, and it's very simple. Let me know if you make progress! I don't see how it's not working....
More than likely, its going to be named VZW_Droid on the inc.
regarding your first un-edited post, no I'm not adding .mp3 to the mp3's file name. I'm simply using adb push boot_audio.mp3 /system/customize/resource
Just tried putting it in /system/media, no dice
rotaryboots said:
regarding your first un-edited post, no I'm not adding .mp3 to the mp3's file name. I'm simply using adb push boot_audio.mp3 /system/customize/resource
Just tried putting it in /system/media, no dice
Click to expand...
Click to collapse
If you want it that bad, spend the 4 bucks and get root explorer, and try that method. Couldn't hurt, and root exp is a great tool to have if you're rooted. That is my suggestion, sir
your kidding right? Or I could just use terminal and use commands like mv, chmod, rm, cd, ls, ls -l, etc. Been using linux commands since redhat came out. I could also just use adb shell, then cd /system/customize/resource, ls, mv boot_animation.mp3 VZW_Droid.mp3, then ls, cd /, umount /system, (command C), adb reboot, and then check to see if it works.
root explorer doesn't offer me anything I can't just do with adb or terminal on the phone.
rotaryboots said:
your kidding right? Or I could just use terminal and use commands like mv, chmod, rm, cd, ls, ls -l, etc. Been using linux commands since redhat came out. I could also just use adb shell, then cd /system/customize/resource, ls, mv boot_animation.mp3 VZW_Droid.mp3, then ls, cd /, umount /system, (command C), adb reboot, and then check to see if it works.
root explorer doesn't offer me anything I can't just do with adb or terminal on the phone.
Click to expand...
Click to collapse
Just letting you know of the hands down simplest way to do it, bud
josepho1997 said:
I can't get sound on my dragon ball boot animation. I've put the android_sound.mp3 in system/media and bootsnd in my Sdcard, then in terminal emulator, I did:
su
Cd /sdcard
sh bootsnd.sh
And then I get the error:
Greg: not found
And then something about mounting and -r,-w,-o.
Please help.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
It has to be a .ogg file. Not mp3.
Sent from a thingymajig that sends things.
Just use Boot Animation Factory
Sent from a thingymajig that sends things.
the creator of boot animation factory specifically stated in the thread that he couldn't get the sound to work. quote, " I still haven't come up with a way to install boot sound"
josepho1997 said:
I used boot factory for sound before, but it didn't work. I guess because it wasn't .ogg so I will try it again. Thanks!
Click to expand...
Click to collapse
chris_m128 said:
the creator of boot animation factory specifically stated in the thread that he couldn't get the sound to work. quote, " I still haven't come up with a way to install boot sound"
Click to expand...
Click to collapse
Whoops, my bad.
Have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1096068
not sure about anybody else but i get stuck at step 3,
the "3. Open Terminal Emulator and type the following commands using the stock keyboard. Press enter after each line:
su
cd /sdcard
sh bootsnd.sh
reboot"
after typing in sh bootsnd.sh I get " No Such User 'root:shell' "
Hi, First I'm not a clever man, nor do I know what I did to brick it but, I used
"LCD Density Modder" on the market and bricked my phone.
https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&hl=en
My phone is bricked, it won't load anything past "Google", I've taken out the battery and put it back in MULTIPLE times, I've tried to reboot into Recovery Mode and get a red Triangle with an error.
I'm on 4.1.1 GSM model, Rooted and Stock ROM.
Is there anyway to fix this issue without completely wiping out my phone? The last backup I did was a week ago by hand, with click and drag.
Thanks for any help, I would appreciate it.
That's not bricking. And the red android is the stock recovery. Your going to need to flash a recovery and flash another ROM.
Sent From My Toro+ via White Tapatalk
First off, your device is not bricked. Bricked means it is irreparable.
Second, all you have to do is get a hold of the stock build.prop file for your ROM build and replace what you currently have with it.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
First off, your device is not bricked. Bricked means it is irreparable.
Second, all you have to do is get a hold of the stock build.prop file for your ROM build and replace what you currently have with it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Or this
Sent From My Toro+ via White Tapatalk
Oh, wow, thanks, and that will save my files?
Is there a step by step process? I...am not a clever man =| or if there's a keyword I can search. Thanks...
I'm asking because I can't transfer files via USB to my Galaxy Nexus, nor does my computer detect it.
Download CWM, rename it to cwm.img and place it in the same directory as your fastboot.exe file on your PC
Boot your device into the bootloader
Type: fastboot boot cwm.img
In the CWM menu on your device, navigate the mounts menu and click mount /system
Type: adb pull /system/build.prop
Open it up in a text editor, change the value in the ro.sf.lcd_density to 320 and save it.
Type: adb push build.prop /system/
Type: adb shell chmod 0644 /system/build.prop
Type: adb reboot
Ignore the post I just made,
I found it manually, and rebooted the phone but it's still black screen when I pushe d it to the phone.
"build.prop /system/" sounds wrong though...but I am still shocked I was able to pull it.
I hate double bumping but "efrant" instructions, I pushed it via your manner, which still boots into the black screen via build.prop /system" and it goes to black screen...and I tried pushing to "/system/build.prop" still doesn't work.
Any assistance?
smartedpanda said:
I hate double bumping but "efrant" instructions, I pushed it via your manner, which still boots into the black screen via build.prop /system" and it goes to black screen...and I tried pushing to "/system/build.prop" still doesn't work.
Any assistance?
Click to expand...
Click to collapse
So what did you do exactly? Did you pull the file from your ROM first, modify it, and then push it back?
So, I'm not using ADB kit, I'm using Galaxy Nexus Tookit v 7.4. I pull it through there, and modify it from 241 to 320 by hand. Save the file. Push it back up using the toolkit, and it's not sticking to the ROM.
I push it up, reboot, and check it by re-pulling it making sure it stucks but I keep seeing the 241 density not the corrected 320.
Should, I be pushing to /system/build.prop or "build.prop /system/" ?
Both methods aren't sticking to /system/build.prop
smartedpanda said:
So, I'm not using ADB kit, I'm using Galaxy Nexus Tookit v 7.4. I pull it through there, and modify it from 241 to 320 by hand. Save the file. Push it back up using the toolkit, and it's not sticking to the ROM.
I push it up, reboot, and check it by re-pulling it making sure it stucks but I keep seeing the 241 density not the corrected 320.
Should, I be pushing to /system/build.prop or "build.prop /system/" ?
Both methods aren't sticking to /system/build.prop
Click to expand...
Click to collapse
I don't provide support for toolkit use. Either do it the way I mentioned or ask in the toolkit thread for support if you want to use a toolkit.
It's to do with the permissions that get set on the file when you push it back to the device. it needs to be read only for the group and world
It baffled me for a good while. After pushing the file, do the following.
Code:
adb shell chmod 0644 /system/build.prop
Hope that helps
Sent from my HTC Sensation using xda premium
efrant said:
I don't provide support for toolkit use. Either do it the way I mentioned or ask in the toolkit thread for support if you want to use a toolkit.
Click to expand...
Click to collapse
- Didn't know it was a hassle, my apologizes. I'll try to do it the old school method.
trevd said:
Its to do with the permissions that get set on the file when you push it back to the device. it needs to be read only for the group and world
It baffled me for a good while. After pushing the file, do the following.
Code:
adb shell chmod 0644 /system/build.prop
Hope that helps
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I had a feeling it was a permissions issue, but wasn't sure how to fix it.
I'll start pulling up the command prompts...wish me luck, thanks for all the help so far guys. I'll do two backup a week from now on, instead of weekly.
Finally got adb in cmd setup, I get a "failed to copy 'build.prop' to '/system/build.prop': Read-Only file system
I'll try it again, I'm pretty sure I forgot a step.
smartedpanda said:
Finally got adb in cmd setup, I get a "failed to copy 'build.prop' to '/system/build.prop': Read-Only file system
I'll try it again, I'm pretty sure I forgot a step.
Click to expand...
Click to collapse
Probably missed this step:
efrant said:
In the CWM menu on your device, navigate the mounts menu and click mount /system
Click to expand...
Click to collapse
efrant said:
Probably missed this step:
Click to expand...
Click to collapse
LOL, yeah I did, got that, did everything from scratch per your instructions, got up to the lovely adb reboot...and nothing, at all, black screen.
I re-pulled it, to make sure the DPI was changed to 320...and it was, and still black screen...=[ I'm really sad now.
smartedpanda said:
LOL, yeah I did, got that, did everything from scratch per your instructions, got up to the lovely adb reboot...and nothing, at all, black screen.
I re-pulled it, to make sure the DPI was changed to 320...and it was, and still black screen...=[ I'm really sad now.
Click to expand...
Click to collapse
Did you change the permissions like trevd suggested?
While booted in CWM with /system mounted:
adb shell chmod 0644 /system/build.prop
If that still doesn't work after a reboot, I suggest you re-flash grab the system image for 4.1.1 from Google's site, extract the system.img, reboot your device into the bootloader, and type: fastboot flash system system.img. It won't wipe your device, but it should fix anything that was messed up. (It will also remove root and busybox and whatever else you have installed on the system partition.
)
FINALLY! SUCCESS! I forgot the permission like you mentioned, but it didn't work the first two times, guess I mistyped something, it worked the third time.
I honestly appreciate all the help, and all the inputs. My phone is at 100%, and I'm doing a backup as we speak now.
efrant said:
Download CWM, rename it to cwm.img and place it in the same directory as your fastboot.exe file on your PC
Boot your device into the bootloader
Type: fastboot boot cwm.img
In the CWM menu on your device, navigate the mounts menu and click mount /system
Type: adb pull /system/build.prop
Open it up in a text editor, change the value in the ro.sf.lcd_density to 320 and save it.
Type: adb push build.prop /system/
Type: adb shell chmod 0644 /system/build.prop
Type: adb reboot
Click to expand...
Click to collapse
I know this thread is dead but I would like to say that this is the single most useful post I've seen in ages! I was looking around for nearly an hour and every post resulted in saying "reflash rom"...
Then I saw this, and worked!! My phone is her old self again
thumbs up!