Related
Hey all, ive been trying to change my boot screen to the haters gonna hate one for a few days now but cant seem to get it to work at all, i have full root and tried to the fastboot method and recovery/adb method. no matter what it stays the same as the one i had originally, i never get errors when trying to push the files if someone can give me instructions for dummies haha or another method id really appreciate it sorry for being a noob at all this.
I had the same problem
First of all, what rom are you using? Different rooms pull from different places. I might be able to help you out. If you are running cyan6, try this:
Adb reboot recovery
Adb remount (make sure it remounts. Maybe also do adb root to make sure.)
Adb push blahblah.zip /system/customize/resource/bootanimation.zip
Adb push blahblah.zip /system/media/bootanimation.zip
Adb push blahblah.zip /data/local/bootanimation.zip
If you want sound, push that to the same locations. Make sure there is only one of each file in each folder. Then, to check,
Adb reboot
Hope this helps
oh yeah sorry i should have included that i am on evios 1.2 beta 2 rom
I'm not familiar on where to place boot on this rom. Try all three locations I suggested. System customize resource. System media. Data local. Tell me if it works out.
I had this animation on EViO. I just pushed it from my desktop to system/media. Worked fine for me.
how do you push it from the desktop? i tried all 3 methods posted above and none worked. i had the file in the android sdk tools folder though...also whenever i try to do adb remount i get "remount failed:invalid argument" and adb root gives me "error:closed" i tried killing adb and restarting but no luck
This might be an obvious question, but do you have USB debugging enabled on your phone? Under Setting>Applications>Development
You arent going to be able to push anything if you can't get ADB running first.
yeah debugging has been enabled the whole time
ok have you been in recovery mode?
try typing
adb shell
su (make sure #comes up.)
exit (retype until you get back to the tools directory)
then do the push commands to system media, system customize resource, and data local.
Just use this program. Its as easy as it gets.
http://forum.xda-developers.com/showthread.php?t=701295
dkdude36 said:
First of all, what rom are you using? Different rooms pull from different places. I might be able to help you out. If you are running cyan6, try this:
Adb reboot recovery
Adb remount (make sure it remounts. Maybe also do adb root to make sure.)
Adb push blahblah.zip /system/customize/resource/bootanimation.zip
Adb push blahblah.zip /system/media/bootanimation.zip
Adb push blahblah.zip /data/local/bootanimation.zip
If you want sound, push that to the same locations. Make sure there is only one of each file in each folder. Then, to check,
Adb reboot
Hope this helps
Click to expand...
Click to collapse
Putting sound in boot animation doesn't work with cm6. Just to clarify. No one has been able to get it to work unless you found something out to make it work please share as I have hates going to hate also and want to use haters everywhere mp3 and is perfect for it.
Sent from my PC36100 using XDA App
yeah i have also been in recovery mode every time i tried to run a command prompt for adb...i tried that when i hit adb shell i get # but when i type su after the # it says "/sbin/sh: su: not found"
mount: mounting /dev/block/mtdblock4 on /system failed: Device or resource busy
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
thats what i get when in command prompt when i try to use the program you just posted above
Want a easier way? Use root explorer and copy and paste. Works for my every time. It's in the market. And root explore you can manually turn writeable on and off to move it into system. It's on the top right of screen in root explorer when you go into system folder.
Edit: the command you are tying to put in enables you to push and pull in the system folder. Root explore you can just click a button.
Sent from my PC36100 using XDA App
Good idea
Root explorer works most of the time. If you have the cash, go ahead. You should make site out posted though.
/sbin/sh: reboot: not found
been trying to use adb and i keep on getting that....any of you know a fix?
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
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!
Was just wondering if there is a way to replace the framework with just using root without a custom recovery for the stock Rom?
On my s3 I couldn't do it with just root don't know if that would work on this or if I might have missed something.
Sent using xda premium.
re: install apks
TheArtiszan said:
Was just wondering if there is a way to replace the framework with just using root without a custom recovery for the stock Rom?
On my s3 I couldn't do it with just root don't know if that would work on this or if I might have missed something.
Sent using xda premium.
Click to expand...
Click to collapse
All you need is to be rooted, it does not matter if you have custom recovery or not.
You can install any apk's since you do not need to go into recovery to install apks.
When I tried with root only before on a different phone I used root explorer to replace.
But when I went to paste it in the folder the phone locked up and rebooted.
Was that not the right way to do it?
Maybe using adb terminal would be better and not cause it to lock and reboot when I paste over the existing framework-res.apk.
Being in the system directory causes some issue with being that is also a constant used file.
Sent using xda premium.
re: install apk
TheArtiszan said:
When I tried with root only before on a different phone I used root explorer to replace.
But when I went to paste it in the folder the phone locked up and rebooted.
Was that not the right way to do it?
Maybe using adb terminal would be better and not cause it to lock and reboot when I paste over the existing framework-res.apk.
Being in the system directory causes some issue with being that is also a constant used file.
Sent using xda premium.
Click to expand...
Click to collapse
The framework-res.apk should be installed like any other app
unless the OP of wherever you got it from gives instructions
to "copy" it to the /system/app folder.
Why not do it the default normal way? just double click on it
when you are in root explorer and it should install like any
other app. If it gives an error, then you can copy it.
If you "copy" it you have to fix permissions and you have to
change the attributes of the /system/app folder so it's "read and write".
NOTE: if there is an existing framework-res-apk in /system/app
delete it with root explorer before doing any of the above.
Framework-Res.apk must reside in system directory. /system/framework to be exact.
Easiest way to do it without locking up is with adb.
You were right OP that it locks up because it's consistently being used. When I make my mods and such to the framework, this is how I quickly get it to the device.
adb remount (if the kernel supports it in other words, anything but stock)
Turn phone screen on
Adb shell stop (your phone should now have a black screen. This command stops all running threads except the one for adb)
Adb push framework-Res.apk /system/framework
Adb shell chmod 644 /system/framework/framework-Res.apk
Adb shell start
You should now see the boot animation then the prompt "android is upgrading"
If you do not have adb remount option (it returns with permission denied)
Copy new framework Res apk to root of internal sd card.
Adb shell stop
Adb shell mount -o remount,rw /system
Adb shell cp /sdcard/framework-Res.apk /system/framework/framework-Res.apk
Adb shell chmod 644 /system/framework/framework-Res.apk
Adb shell start
Just a pointer, disregard my capitalization. Only capitalize when needed.
This method should get everything copied successfully. Any issues just post back!
Sent from my SGH-M919 using Tapatalk 2
Oh thank you very much.
I will give that a try and sounds exactly like what I was looking for.
Sent using xda premium.
Not sure if this is really relevant but...
When I had the samsung vibrant, I used root explorer to make a copy of my framework-res.apk. I extracted the entire thing, found my battery icon files, replaced them with different images given the same name, then repacked the file. Then I copied it back to the original folder to replace the original apk and my phone immediately shut off and rebooted. When it came back I had my new battery icon working just as I had hoped. I was rooted running stock.
Wait... Are you saying that I can simply copy the framework-res.apk from SlimKat and use it on a Google Play Edition ROM?
I'm going to try it!
Like a dummy I tried to rename framework-res while using my nexus so I could replace it with an edited one (deb rooted, stock 4.4.4 rom, franco -17 kernel)
Now Im trying to ADB in to rename the original file so it will boot again.
I'm connected to the nexus in ADB but when I try to pull or rename the file I always get some sort of error.
I was able to adb push a framwork file I downloaded on my computer but it still wouldnt boot. Im assuming it was bad.
Any help is much appreciated!
thanks!
Rhatfield25 said:
Like a dummy I tried to rename framework-res while using my nexus so I could replace it with an edited one (deb rooted, stock 4.4.4 rom, franco -17 kernel)
Now Im trying to ADB in to rename the original file so it will boot again.
I'm connected to the nexus in ADB but when I try to pull or rename the file I always get some sort of error.
I was able to adb push a framwork file I downloaded on my computer but it still wouldnt boot. Im assuming it was bad.
Any help is much appreciated!
thanks!
Click to expand...
Click to collapse
The reason it would not boot with the one you pushed to the device is probably because you have to set permissions correctly after the push. Framework res should probably be set to rw-r--r--
Run this after the push, or if the file is still on the phone, run it now.
Code:
adb shell
su
chmod 644 /system/framework/framework-res.apk
SwoRNLeaDejZ said:
The reason it would not boot with the one you pushed to the device is probably because you have to set permissions correctly after the push. Framework res should probably be set to rw-r--r--
Run this after the push, or if the file is still on the phone, run it now.
Code:
adb shell
su
chmod 644 /system/framework/framework-res.apk
Click to expand...
Click to collapse
I will give it a shot the second I get home! Thank you so much for the help. So by default files pushed to the system do not have full read and write permissions?
Thanks again!
Rhatfield25 said:
I will give it a shot the second I get home! Thank you so much for the help. So by default files pushed to the system do not have full read and write permissions?
Thanks again!
Click to expand...
Click to collapse
Yes, most of the time, pushed files will copy with bad permissions. Every time I've ever edited a system APK, I've had to subsequently set permissions before it would act correctly. Might not be 100% your issue, but it's definitely worth a shot.
SwoRNLeaDejZ said:
Yes, most of the time, pushed files will copy with bad permissions. Every time I've ever edited a system APK, I've had to subsequently set permissions before it would act correctly. Might not be 100% your issue, but it's definitely worth a shot.
Click to expand...
Click to collapse
Well now Ive run into a new problem. When I SU to get root access it tells me that /sbin/sh isnt found.
I rooted the n7 with cf autoroot.
this would be a whole lot easier if twrp would mount the tablet so I could just upload and flash a zip to update it.
Well I was able to sideload the boot animation herehttp://forum.xda-developers.com/showthread.php?t=2591471 just to confirm that sideload was working. I rebooted and it worked but still will not get past the boot animation.
The framework file simply needs to be put in /system right? so the command would look like
abd sideload framework-res.apk /system
Is that right?
Rhatfield25 said:
Well now Ive run into a new problem. When I SU to get root access it tells me that /sbin/sh isnt found.
I rooted the n7 with cf autoroot.
this would be a whole lot easier if twrp would mount the tablet so I could just upload and flash a zip to update it.
Click to expand...
Click to collapse
What about trying to use the terminal emulator in twrp?
Rhatfield25 said:
Well I was able to sideload the boot animation herehttp://forum.xda-developers.com/showthread.php?t=2591471 just to confirm that sideload was working. I rebooted and it worked but still will not get past the boot animation.
The framework file simply needs to be put in /system right? so the command would look like
abd sideload framework-res.apk /system
Is that right?
Click to expand...
Click to collapse
You need to fix the framework file before you can boot. Try running the permission command without su first.