Hi,
I made an app to manage the Boot Logo and Boot Animation.
Forum post: http://forum.xda-developers.com/show....php?t=1076551
The app works on Defy and Milestone 2.
I want to add support for more devices but I need some info.
I need the output of the following command:
Code:
ls -R -l /dev
After that, I'll need more info.
Thanks.
Related
Ok, so I am trying to flash a new splash image onto my G2. The image is on the root of my SD card like this /sdcard/new_splash.img
I open the mobile terminal and get this:
$ su
# cd /sdcard
# flash_image splash1 new_splash.img
failed with error: -1
Any ideas??
Are you sure you have the flash_image script on your phone?
Sent from my HTC Vision
Yes, because I flashed CWM Recovery with flash_image.
Sent from my HTC Vision using XDA App
troby86 said:
Ok, so I am trying to flash a new splash image onto my G2. The image is on the root of my SD card like this /sdcard/new_splash.img
I open the mobile terminal and get this:
$ su
# cd /sdcard
# flash_image splash1 new_splash.img
failed with error: -1
Any ideas??
Click to expand...
Click to collapse
Try
$ su
# flash_image splash1 /sdcard/new_splash.img
This method still fails with error -1
Sent from my G2 using XDA App
Ops Dobbel post ..
Be very careful with this method and check that you typed everything correctly so you do not accidentally brick your phone
Code:
$ Su
# dd if=/mnt/sdcard/splash.img of=/dev/block/mmcblk0p19
(Copy and past it)
(Splash.img = the name of your splash.img )
Worked perfect! Thanks
Sent from my HTC Vision using XDA App
troby86 said:
Worked perfect! Thanks
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
No problem . Happy to help.
Will this work on the backflip?
stian230 said:
Be very careful with this method and check that you typed everything correctly so you do not accidentally brick your phone
Code:
$ Su
# dd if=/mnt/sdcard/splash.img of=/dev/block/mmcblk0p19
(Copy and past it)
(Splash.img = the name of your splash.img )
Click to expand...
Click to collapse
I want to be extra sure your method isn't device independent before I try it; especially since I'm not sure where it's pointing too...
To be a sharin, heres what I've tried and got so far...
I was able to pull the M splash screen and convert it to BMP on my backflip (s-on) with:
adb
su
cat /dev/mtd/mtd6 > /sdcard/splash.img
nbimg -h 480 -w 360 -F splash.nb
but now I can't get the new one back... any suggestions? Tried:
cat /sdcard/splash.img > /dev/mtd/mtd6
...and...
flash_image splash /sdcard/splash.img
to no effect.
can I...:
dd if=/sdcard/splash.img of=/dev/mtd/mtd6
? I'm fairly new to linux, I don't fully understand the mount process...
-----------------------------------------------------------------------------
I've been playing around, I don't have mmcblk0p19, I only have mmcblk0 and mmcblk0p1. My next task is to pull these off and see if I can't figure out what they are.
I have create a script file that will flash a recovery from the terminal in the Galaxy Nexus.
I got the command from xda but I could not remember it when I wanted to flash a recovery,
so I wrote a script to do it.
AS WITH ANY FLASHING OR MODDING OF "YOUR" PHONE, I AM NOT RESPONSIBLE FOR ANY DAMAGES YOU MAY CAUSE!
I have tested this on my:
Unlocked Galaxy Nexus 4.1.1 takju (flashed from yakju)
Sprint Galaxy Nexus 4.0.4
Thanks to -viperboy- for help.
Code:
Created by Smurph82 2012_0512 (c) v1.0
flashr [-h] [-r] [-m] [-s s] -- Flash a recovery
to the Galaxy Nexus.
where:
-h show this help text
-r will reboot after flashing is complete.
-m image is in the root of the sdcard
-s source of the recovery image (/sdcard/recovery.img).
To use the script:
Download and Flash the script file from your current recovery
Or download the zip file and move the flashr file in the /system/bin folder to /system/bin with RootExplorer
or other root level file manager.
If you manually add the file you must
Code:
chmod 0755 /system/bin/flashr
or change the permissions from RootExplorer
Then open Terminal and type
Code:
su
first, yes you have to be rooted to do this!
Next type
Code:
flashr
or
Code:
flashr -h
to get the help
If you want to flash a recovery you must have the recovery.img
somewhere on your device that you can remember. Like the root of the sdcard.
To flash a recovery type
Code:
flashr -s /sdcard/recovery.img
or if the recovery is in the root of the sdcard type
Code:
flashr -ms recovery.img
If you want to reboot after the flashing is complete next use
Code:
flashr -mrs recovery.img
In the code examples above I used recovery.img as an example.
This should be "what ever you named the recovery".img it does not have to be recovery.
Reserved
Change Log:
v1 - Initial Release
i know you might think that im trolling, but im really not. what id like to know is what makes that better than just flashing the recovery, via the terminal, the old-fashioned way..
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter, if you want to go to the recovery)
providing ithe file is on the main fs in the sd storage.
flash_image does not work with ics, that I have found. So I wrote my own. If there is a new flash_image that works with the galaxy nexus then I could not find it. Maybe it is because I'm still using the stock rom and kernel. I took the flash_image out of cm9 but it didn't work for me.
Sent from my Galaxy Nexus using XDA Premium HD app
Would you be willing to share the sources for this? It would be interesting to know how this works, since it may be useful also for other purposes than flashing recovery images. Or not?
I will post the source later today. It really is not much.
Sent from my Transformer Prime TF201 using XDA Premium HD app
E:V:A said:
Would you be willing to share the sources for this? It would be interesting to know how this works, since it may be useful also for other purposes than flashing recovery images. Or not?
Click to expand...
Click to collapse
Hope that this is helpful to someone.
Code:
#!/system/bin/sh
usage="Created by Smurph82 2012_0512 (c) v1.0
flashr [-h] [-r] [-m] [-s s] -- Flash a recovery
to the Galaxy Nexus.
where:
-h show this help text
-r will reboot after flashing is complete.
-m image is in the root of the sdcard
-s source of the recovery image (/sdcard/recovery.img)."
# Read in the options turn off verbose and require -s to have input
while getopts :hrms: opt; do
case $opt in
h) echo "$usage"
echo
exit;;
m) sdroot="/sdcard/";;
s) sourcedir=$OPTARG;;
r) reboot="t";;
*) echo
echo
echo "Invalid option: -$OPTARG" >&2
echo "$usage"
echo
exit;;
esac
done
shift $(($OPTIND - 1))
# This was for testing
#echo
#echo "Vars: m $sdroot: s $sourcedir: r $reboot: dir $sdroot$sourcedir"
#echo
# Check to make sure somthing was typed if not show help
if [ "$sourcedir" == "" ]; then
echo "$usage"
echo
exit
else
# Check that something is in that location if not dont flash
if [ -s $sdroot$sourcedir ]; then
echo "Flashing image from: $sdroot$sourcedir"
cat $sdroot$sourcedir > /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
else
echo "File not found at $sdroot$sourcedir"
exit
fi
fi
# Early in the morning I was getting cute
if [ "$reboot" == "t" ]; then
echo "Rebooting in 5.."
sleep 1
echo "Rebooting in 4.."
sleep 1
echo "Rebooting in 3.."
sleep 1
echo "Rebooting in 2.."
sleep 1
echo "Rebooting in 1.."
sleep 1
reboot recovery
fi
thank u very much for this! so easy now!!
It is just as easily done in a terminal by the following (assuming you downloaded the recovery you want to /sdcard and named it recovery.img):
su
dd if=/sdcard/recovery.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
efrant said:
It is just as easily done in a terminal by the following (assuming you downloaded the recovery you want to /sdcard and named it recovery.img):
su
dd if=/sdcard/recovery.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
Click to expand...
Click to collapse
Yes I know that but who wants to type all of that out. I just made it shorter more
or else. If you want to type the whole command then by all means have at it. I just
think that "flashr -mrs twrp.img" is a whole lot easier. Just my thoughts.
Hi
Nice enough script.
Although I feel I should warn people that it looks like this script will write anything you tell it. making no effort to verify that the file is a valid or correct for your phone. so be careful not to specify the wrong file.
fastboot flash recovery $file is much safer.
That is true if you are connected to a computer but this script is run on the phone from the terminal. If someone knows a way to check a file from the terminal running on the phone please tell me and I will update the script. I understand that there is currently no verification of the file that is being written so please make sure that you are writing the right file.
Sent from my Galaxy Nexus using XDA Premium HD app
Hello,
I would like to start an app installed on a non rooted fire tv (generic solution, and as an example for xbmc) by adb. I found some examples, which all don't work... (I am able to start the adb shell and launch other commands...)
eg:
Code:
am start -a android.intent.action.MAIN -n org.xbmc.xbmc/android.app.NativeActivity
returns
Code:
Error type 3
Error: Activity class {org.xbmc.xbmc/android.app.NativeActivity} does not exist
.
Is this not possible on non rooted fire tv's?
Or do I just use a wrong syntax?
I am working on some remote conrtrol options, so launchers are not a solution for me.
Thanks for support.
adb shell am start -n org.xbmc.xbmc/.Splash
Kramar111 said:
adb shell am start -n org.xbmc.xbmc/.Splash
Click to expand...
Click to collapse
Works, thanks a lot!
Is there any way to get this for other apps out of the system?
eg: if I want to start netflix the same way, can I get the parameters from anywhre in the system or is "google my friend""?
with aapt (part of Android SDK):
run
Code:
aapt dump badging name.apk
and search line "launchable-activity"
or in GNU/Linux run
Code:
./aapt dump badging name.apk | grep "launchable-activity"
Kramar111 said:
with aapt (part of Android SDK):
run
Code:
aapt dump badging name.apk
and search line "launchable-activity"
or in GNU/Linux run
Code:
./aapt dump badging name.apk | grep "launchable-activity"
Click to expand...
Click to collapse
adb shell am start -n ir.hamgam.mobile/.Splash
for doesn't work plz help me
Hi all,
I'm trying to create my own system.img for the Nexus 7 2013 Wifi from the stock system.img from https://developers.google.com/android/nexus/images 5.0.2 LRX22G. Basically I did it the common way using the android repack tools http://forum.xda-developers.com/showthread.php?t=2600364 and I'm also using branch android-5.0.2_r1 from the git repo.
I'm flashing with the simple:
Code:
fastboot flash system mysystem.img
The problem I'm having is, even with an unmodified tree from system.img, the image I created always get the device stuck at the boot Google logo screen. If I flash the original system.img, then it is fine, so I think my flashing part is working.
The command line I used to create the image is:
Code:
./mkuser.img.sh -s /path/to/loop_mounted_system/ mysystem.img ext4 system 880803840
which will run:
Code:
make_ext4fs -s -T -1 -l 880803840 -a system mysystem.img /path/to/loop_mounted_system/
Has anyone here actually managed to create a working system.img?
Any suggestions would be much appreciated, thanks!
UPDATE: Using ext2simg instead of mkuserimg.sh/make_ext4fs fixes the problem!
Hi there,
here comes my collection of bootanimations for Suzuran. Maybe they are useful for other devices?
Klick
bootanimation_Berni.zip: My used one
bootanimation_google.zip: From Google inspired, minimal and playful one
bootanimation_lineage.zip: The one from LineageOS team
bootanimation_stock.zip: The original one from Stock ROM 7.x
How to change the current bootanimation?
Enter these commands line by line:
Code:
adb root
adb shell
mount -o remount,rw /
exit
adb push <name_of_bootanimation_file> /system/media/bootanimation.zip
exit
Reboot.
If you want to save your current bootanimation file, you should perform this command FIRST:
Code:
adb pull /system/media/bootanimation.zip
Berni-0815 said:
Hi there,
here comes my collection of bootanimations for Suzuran. Maybe they are useful for other devices?
Klick
bootanimation_Berni.zip: My used one
bootanimation_google.zip: From Google inspired, minimal and playful one
bootanimation_lineage.zip: The one from LineageOS team
bootanimation_stock.zip: The original one from Stock ROM 7.x
How to change the current bootanimation?
Enter these commands line by line:
Code:
adb root
adb shell
mount -o remount,rw /
exit
adb push <name_of_bootanimation_file> /system/media/bootanimation.zip
exit
Reboot.
If you want to save your current bootanimation file, you should perform this command FIRST:
Code:
adb pull /system/media/bootanimation.zip
Click to expand...
Click to collapse
bootanimation.zip: 1 file pushed, 0 skipped. 436.3 MB/s (1496312 bytes in 0.003s)
but it still the same animation as before. renamed it to bootanimation
tarukanav said:
1496312 bytes
Click to expand...
Click to collapse
That's the file size of the bootanimation file from LineageOS team (see attached picture). I've tested every one of those four files and everytime after reboot I've gotten the wanted result.
You're doing something wrong!
Berni-0815 said:
That's the file size of the bootanimation file from LineageOS team (see attached picture). I've tested every one of those four files and everytime after reboot I've gotten the wanted result.
You're doing something wrong!
Click to expand...
Click to collapse
yea that am doing something wrong is the thing i cant figure out
Is every command executed successfully?
Code:
adb root
adb shell
mount -o remount,rw /
exit
adb push bootanimation_google.zip /system/media/bootanimation.zip
exit
There should be not one single error message:
Code:
[email protected]:~/Tmp$ adb root
restarting adbd as root
[email protected]:~/Tmp$ adb shell
suzuran:/ # mount -o remount,rw /
suzuran:/ # exit
[email protected]:~/Tmp$ adb push bootanimation_google.zip /system/media/bootanimation.zip
bootanimation_google.zip: 1 file pushed. 18.4 MB/s (1858574 bytes in 0.097s)
[email protected]:~/Tmp$
And after a reboot I can see this Google inspired animation.
Edit: Have you executed the "exit" command after the "mount" command?
Berni-0815 said:
Is every command executed successfully?
Code:
adb root
adb shell
mount -o remount,rw /
exit
adb push bootanimation_google.zip /system/media/bootanimation.zip
exit
There should be not one single error message:
Code:
[email protected]:~/Tmp$ adb root
restarting adbd as root
[email protected]:~/Tmp$ adb shell
suzuran:/ # mount -o remount,rw /
suzuran:/ # exit
[email protected]:~/Tmp$ adb push bootanimation_google.zip /system/media/bootanimation.zip
bootanimation_google.zip: 1 file pushed. 18.4 MB/s (1858574 bytes in 0.097s)
[email protected]:~/Tmp$
And after a reboot I can see this Google inspired animation.
Edit: Have you executed the "exit" command after the "mount" command?
Click to expand...
Click to collapse
yes , had no error messages, had same thing once before cant rememeber how i fixxed it .Also tried to just copy it with rootexplorer and same thing copies fine , but animation stays same
Which OS are you using at your device?
Berni-0815 said:
Which OS are you using at your device?
Click to expand...
Click to collapse
win10 ,but i know there was something else am doing wrong, had same situation a while ago but cant remember how i fixed it , tried to use different apps to change bootanimation and nothing worked , at the end it was something simple just cant remember what it was
No. Not the OS of your computer, the OS of your z5c.
I'm using los18. Maybe with other OS's this is not working?
hhe android is also 10, so los 17
I've flashed los17.1 yesterday and the changing of the bootanimation works flawlessly; as expected.
ook soo am just stupid as hell ,copied bootanimation.zip to just bootanimation.