hello! bootanimation of windows xp, it works perfectly on 1080x2400 screens, (RN10PRO) I don't know how to make a flashable zipper, if you are able do it please
Racconex84 said:
hello! bootanimation of windows xp, it works perfectly on 1080x2400 screens, (RN10PRO) I don't know how to make a flashable zipper, if you are able do it please
Click to expand...
Click to collapse
So, what are we supposed to do with it now, if it cannot be flashed? Wait? Also, is this file staged on the phone where we can replace it manually later? (location, name, ownership, permissions, etc) I know another person is asking about changing boot animations on these Redmi's.
Sheist! said:
So, what are we supposed to do with it now, if it cannot be flashed? Wait? Also, is this file staged on the phone where we can replace it manually later? (location, name, ownership, permissions, etc) I know another person is asking about changing boot animations on these Redmi's.
Click to expand...
Click to collapse
you can replace it manually in recovery
once in recovery mode, (twrp/orangefox)
you will have to mount /product
once mounted, from the terminal you will need to make /product into rw, then type
"mount -o remount,rw /product"
copy "bootanimation.zip" to "/product/media"
afterwards assign "bootanimation.zip" chmod 644
return to console and remount /product in ro
"mount -o remount,ro /product"
reboot.
(if you are on stock miui, you may have problems mounting /product in rw)
Racconex84 said:
you can replace it manually in recovery
once in recovery mode, (twrp/orangefox)
you will have to mount /product
once mounted, from the terminal you will need to make /product into rw, then type
"mount -o remount,rw /product"
copy "bootanimation.zip" to "/product/media"
afterwards assign "bootanimation.zip" chmod 644
return to console and remount /product in ro
"mount -o remount,ro /product"
reboot.
(if you are on stock miui, you may have problems mounting /product in rw)
Click to expand...
Click to collapse
Oh wow, wasn't expecting the perfect steps; thanks! Not using stock MIUI for a long time, but I am having custom recovery issues which is not your problem. Are you able to easily create these bootanimation.zip files using different image source files?
it depends on the gif, all I did was download the gif, split the frames via ezgif, edit frame by frame with paint. net, and then create the zipper, if the gif is very simple (like black background) I can do it, but I'm not very good with image editing, I just downloaded the gif and adjusted it to the right resolution, this is a bugdroid startup animation I made a year ago, I'm not skilled in making animations, I just download gifs and repurpose them, just that
A funny android, thanks
Related
I've been trying to figure out how to fix my phone and through using the adb logcat the only thing left is just getting the core.jar file in the /system/framework to change from read only to rw. Each time I try to change it it says its read only or bad mode. Any ideas?
Metatronx said:
I've been trying to figure out how to fix my phone and through using the adb logcat the only thing left is just getting the core.jar file in the /system/framework to change from read only to rw. Each time I try to change it it says its read only or bad mode. Any ideas?
Click to expand...
Click to collapse
try
Code:
adb remount
What would the syntax be for remounting the core.jar and is it possible to do in terminal? Thank you especially for the quick response\!
From your other thread..
The entire /system partition is always read-only, unless you tell your phone to remount it read-write.
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
But for your problem.. You shouldn't really need to manually tweak files in /system if you flash another ROM. The new ROM will replace that entire partition. Have you wiped? What ROM are you trying to flash?
Kudos for using logcat and trying to jump in yourself though.
I have a rooted (rage) N1 that I loaded the G2 Launcher2.apk on to. Doing this caused the N1 to fail the update when it tried to apply FRG83D.
Stupidly, I decided that deleting the /system/app/launcher2.apk file was the right idea. And then rebooted.
Now the phone hangs on the boot animation. Attempting to apply with NO launcher2.apk results in the same error.
I have ADB installed, and I can adb shell into the phone and su. I have the old, original N1 launcher backed up on my SD card, but I can't figure out how to:
1) Mount the sdcard while ADB shell'd in from just the boot animation screen so that I can browse the card
2) Move the launcher2.apk backup file into the /system/app directory without getting a "Cross-device link" error when I use mv.
Can someone provide me with the exact commands to get the /sdcard/launcher2 backup/launcher2.apk file on to /system/app while ADB'd in only from the boot animation?
Thanks so much, I'm digging through the forums in the mean time, but it's tricky to track down exactly what to do.
I appear to have fixed everything. I wasn't able to access the SD card through ADB, but I *was* able to mount it using the:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
method.
From there, I copied my backup to my desktop, and I found I was able to ADB push to just the /data/local/tmp directory. Don't know if I could've gone anywhere else, but that worked.
From there, I was about to:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount/make writable the /system/app directory,
and then:
Code:
cat /data/local/tmp/launcher2.apk > /system/app/launcher2.apk
So there's that. All to restore the Launcher to a version that would allow for a somewhat pointless update. Woo!
need to go back to the stock bootanimation.zip from the DHD and cant find it...
here you go
normal bootscreen
http://www.megaupload.com/?d=YUUNF8DR
why would you want it lol
or the is this bootanimation i got from UOT kitchen
same as the normal htc bootscreen but black and has this little android thats pops from behind the htc letters lol
http://www.megaupload.com/?d=21QVGAR0
thank you very much, that was very useful !
How do you flash to the phone ? Thanks!
saquib said:
How do you flash to the phone ? Thanks!
Click to expand...
Click to collapse
cant flash these in recovery
you use can use adb
place the bootanimation.zip on to root of sdcard
open command prompt
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p25 /system
cp /sdcard/bootanimation.zip /system/customize/resource/
reboot phone
or use root explore (android market) as this can write to the system
top of screen, tap the mount button to r/w
then copy/paste bootanimation to /system/customize/resource
it will ask to overwrite the bootanimation select yes
then hightlight new bootanimation select permissions
user needs to be ticked as read and write
group needs to be ticked as read
others also ticked as read
press ok
reboot
these folder locations are for the sense based roms or stock
for cyanogen/aosp just need to place the bootanimation in /data/local/
any chance to get the bootanimation sound file ?
Alright.. I wanted the Note 8 version of gallery and i went into system/app folder and deleted the SecGallery2_Galaxy.apk but before deleting i saw that its size was 0.00 kb lol ..
But when i tried tried to copy and pasted in the extsd it pasted and showed 13mb..
Now i deleted the file and copied the Note 8 Galley and pasted in the system/app folder only to get an error " Operation failed " and i realized only 7 mb free space is there in the partition by going into the android emulator!
Now i also found out that, full size SecGallery2_Galaxy.apk was in the preload partition and i instead of replacing that i deleted the file in system/app..
Now how do i get back that file in system/app?.. is that what they call deodexed file?.. Please help..
Thanks a lot in advance
Just copy it from other rom, that You can explore with winrar.
Sent from galaxy n7105
The actual apk was in preload and was symlinked to system partition. Thats why it showed 0 KB in system.
You can get it back by typing in shell
Code:
$ su
# ln -s "Path of apk in preload" /system/app/
And this is not called deodexing.
nokiamodeln91 said:
The actual apk was in preload and was symlinked to system partition. Thats why it showed 0 KB in system.
You can get it back by typing in shell
Code:
$ su
# ln -s "Path of apk in preload" /system/app/
And this is not called deodexing.
Click to expand...
Click to collapse
Thanks but i dont know the path.. the name of the file is SecGallery2_Galaxy.apk, so whats the path of the file?..
can u please type and show?..
Thanks in advance
CustomRomAddicts said:
Thanks but i dont know the path.. the name of the file is SecGallery2_Galaxy.apk, so whats the path of the file?..
can u please type and show?..
Thanks in advance
Click to expand...
Click to collapse
I dont remember... but something like
/preload/symlink/system/app/SecGallery2_Galaxy.apk
but double check.
nokiamodeln91 said:
I dont remember... but something like
/preload/symlink/system/app/SecGallery2_Galaxy.apk
but double check.
Click to expand...
Click to collapse
It says read only file system
I even changed the permission of the file in preload to 644 ( rw-r--r-- )
still the same message?.. any idea what it might be?.
Thanks in advance
use adb shell
then mount the preload partition as rw
# mount -o remount rw /preload
# mount -o remount rw /system
the use the codes written above.
nokiamodeln91 said:
use adb shell
then mount the preload partition as rw
# mount -o remount rw /preload
# mount -o remount rw /system
the use the codes written above.
Click to expand...
Click to collapse
Honestly i just now searched in google for adb shell and it says to run windows but when i download and double click the adb.exe it runs and exits!.. Please help..
Will mounting the preload and system in recovery and rebooting the device and running the script again in android emulator work?..
Keep in recovery and mount both.. Then run....
nokiamodeln91 said:
Keep in recovery and mount both.. Then run....
Click to expand...
Click to collapse
I tried in adb shell too.. but its not working
Do u guys have the symlink file?.. can u share with me?.. will it work?..
Thanks in advance
Oh Yeah! SOLVED IT!!
I installed Root explorer and created symlink via that and Voila it worked!
Although i dont know why when i open a photo in gallery i experience FC!
There have been quite a bit of people with issues with Systemless root, there are some apps that are not recognizing root, i had this issue with my Oneplus One on COS 13.1 and now the same thing works with our OnePlus 3 on OxygenOS
I had come across this on another forum, i don't recall where so i don't want to take the credit for this, i just want to provide the fix for people who have this phone and having issues
Download Terminal from app store and type
Code:
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot
Thank you ! Before I try this , can you tell me what this method is doing ? All I can tell is that it is mounting something as read only instead of read write
I belive it creates a dummy file bc some apps require it to show as a system file
SDMU said:
Thank you ! Before I try this , can you tell me what this method is doing ? All I can tell is that it is mounting something as read only instead of read write
Click to expand...
Click to collapse
Code:
1. su
2. mount -o remount,rw /system
3. touch /system/bin/su
4. mount -o remount,ro /system
5. reboot
1. To get root privileges
2. Remounts /system partition in writable mode
3. Creates an empty file called su to /system/bin/ folder
4. Remounts /system partition to read only mode.
5. reboot
Edit. As stated above, some apps still check root access by looking su file in /system/bin folder
Squabl said:
1. To get root privileges
2. Remounts /system partition in writable mode
3. Creates an empty file called su to /system/bin/ folder
4. Remounts /system partition to read only mode.
5. reboot
Edit. As stated above, some apps still check root access by looking su file in /system/bin folder
Click to expand...
Click to collapse
This defeats the purpose of a system less su, I.e., not modifying the system partition. Step 3 modifies the system partition.
The reason apps are not seeing the su in system less state is because they have been written incorrectly. Chainfire already said these apps should be re written
candiesdoodle said:
This defeats the purpose of a system less su, I.e., not modifying the system partition. Step 3 modifies the system partition.
The reason apps are not seeing the su in system less state is because they have been written incorrectly. Chainfire already said these apps should be re written
Click to expand...
Click to collapse
Yes, it "disables" systemless root and afterwards it is just a root and banking apps and ota updates etc will fail. I don't need systemless root so I have modified my system partition to get some poorly coded apps to function. This method is not recommended if you need systemless root and it's a good thing that you pointed that out!