Archos 97 Root and custom recovery step by step n00b guide.
Download files
rkflashtool http://sourceforge.net/projects/rkflashtool
ARCHOS 97 Titanium HD custom recovery from http://androtab.info/clockworkmod/rockchip/rk3066/
Edit rkflashtool.c, add 0x300a line
if (!(h = libusb_open_device_with_vid_pid(c, 0x2207, 0x290a)))
if (!(h = libusb_open_device_with_vid_pid(c, 0x2207, 0x281a)))
if (!(h = libusb_open_device_with_vid_pid(c, 0x2207, 0x300a)))
fatal("cannot open device\n");
Click to expand...
Click to collapse
comile rkflashtool with libusb
sudo apt-get install libusb-1.0-0-dev
gcc -o rkflashtool rkflashtool.c -lusb-1.0 -O2 -W -Wall -s
connect tablet USB to PC
power off tablet
hold volume- and insert charging cable
release volume- after screen turns on
dump system
sudo ./rkflashtool r 0x00154000 0x00100000 > system.loop
edit system, disable install-recovery.sh
sudo mount -o loop system.loop /loop
cd /loop/etc
sudo chmod 644 install-recovery.sh
flash system back to device
sudo ./rkflashtool w 0x00154000 0x00100000 < system.loop
backup original recovery and flash CWM recovery.img
sudo ./rkflashtool r 0x00010000 0x00008000 > recovery.backup
sudo ./rkflashtool w 0x00010000 0x00008000 < recovery.img
reboot to recovery (hold volume-, connect power cable)
donwload and install SuperSU.zip
Maybe you can add to the tutorial, howto restore the original content, so that it looks like "untouched".
starbright_ said:
Maybe you can add to the tutorial, howto restore the original content, so that it looks like "untouched".
Click to expand...
Click to collapse
Flash "recovery.backup" back you made in step 8. and delete super user app, that's it.
Though nobody checks those things anyway.
Additional info on partition offsets
MACHINE_MODEL:ARCHOS 97 TITANIUMHD
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
CMDLINE: console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000
mtdparts=rk29xxnand:
[email protected](misc),
[email protected](kernel),
[email protected](boot),
[email protected](recovery),
[email protected](backup),
[email protected](cache),
[email protected](kpanic),
[email protected](system),
[email protected](userdata)
Click to expand...
Click to collapse
Does this work on the Familypad 2? If not, are there any known methods to achieve root on the Familypad 2?
Thanks.
Moved Files
The Repository has been removed; what do you from this point?
GIgantorFNS said:
The Repository has been removed; what do you from this point?
Click to expand...
Click to collapse
it wasn't http://sourceforge.net/p/rkflashtool/code/HEAD/tree/trunk/
GIgantorFNS said:
The Repository has been removed; what do you from this point?
Click to expand...
Click to collapse
Thank you! It's there; beit that this is my first time rooting a tablet-I have NO idea what I do after this point!
Hmm.... I can't mount system.loop !
Everything works fine. but if i try to mount system.loop i'll get no access.
If i type in:
sudo mount -o loop system.loop /loop
Ubuntu tells me /loop does not exist.
Where is the error?
Can someone help?
THX LaGra
all working file. thank you for your tuto
:laugh:
LaGra said:
sudo mount -o loop system.loop /loop
Ubuntu tells me /loop does not exist.
Click to expand...
Click to collapse
you need to create /loop folder first.
Originalas said:
you need to create /loop folder first.
Click to expand...
Click to collapse
Sorry, but still not working.
Where i have to create that folder?
Linux is not my best.
my english too......
I have put an update on the tablet from archos. Maybe is that my fail.
LaGra said:
Sorry, but still not working.
Where i have to create that folder?
Click to expand...
Click to collapse
Try
sudo mkdir -p /mnt/loop
sudo mount -o loop system.loop /mnt/loop
Originalas said:
Try
sudo mkdir -p /mnt/loop
sudo mount -o loop system.loop /mnt/loop
Click to expand...
Click to collapse
Thanks a lot for your help.
Now its working. :good:
Hi, I can't get through number 5, ie dump system with "sudo ./rkflashtool r 0x00154000 0x00100000 > system.loop".
Every time I get "rkflashtool: fatal: cannot open device". Tablet is in recover mode and connected through USB.
The only difference - I'm using Linux Mint 14. Is that the problem?
type in terminal
lsusb
does your device show up in the list? Is it under name "0x2207, 0x300a"? or something like "Google Android"?
Check drivers, try differrent USB port, if tablet doesn't show up in the list at all.
If it's under other name, not "0x2207, 0x300a", then you haven't entered flashing mode properly.
Turn off tablet, connect usb, hold volume down button and connect power supply without releasing volume down for 10s. Then try lsusb again.
Originalas said:
type in terminal
lsusb
does your device show up in the list? Is it under name "0x2207, 0x300a"? or something like "Google Android"?
Check drivers, try differrent USB port, if tablet doesn't show up in the list at all.
If it's under other name, not "0x2207, 0x300a", then you haven't entered flashing mode properly.
Turn off tablet, connect usb, hold volume down button and connect power supply without releasing volume down for 10s. Then try lsusb again.
Click to expand...
Click to collapse
Thanks a lot for your reply.
In normal mode it shows as "Bus 003 Device 008: ID 0e79:14ad Archos, Inc.", but it doesn't show at all in recovery mode.
What might be the problem?
Ok, now i can go into CWM.
Superuser is installed. But if I start the tablet it does not boot
anymore!
Everytime it goes back to recovery menu.
nyboy1 said:
Thanks a lot for your reply.
In normal mode it shows as "Bus 003 Device 008: ID 0e79:14ad Archos, Inc.", but it doesn't show at all in recovery mode.
What might be the problem?
Click to expand...
Click to collapse
you haven't set tablet to flash mode.
Originalas said:
Turn off tablet, connect usb, hold volume down button and connect power supply without releasing volume down for 10s. Then try lsusb again.
Click to expand...
Click to collapse
Originalas said:
you haven't set tablet to flash mode.
Click to expand...
Click to collapse
Hi, thanks for your reply. I managed to get to number 6 now)
[email protected]:~$ sudo mkdir -p /mnt/loop
[email protected]:~$ sudo mount -o loop system.loop /mnt/loop
mount: according to mtab /home/ubuntu/system.loop is already mounted on /mnt/loop as loop
[email protected]:~$ cd /loop/etc
bash: cd: /loop/etc: No such file or directory
Can't understand where mistake was made. I'd appreciate your help. Thank you.
Well, if you created mount in /mnt/loop, path should be like
cd /mnt/loop/etc
You can use graphical file explorer, to check directories too..
Related
I'm trying to remove some of the stock apps on my Hero, including Rosie (Sense UI) and such. What mode do I boot in before doing this?
I know all of the steps to remove apps using adb (at least I think I do), I'm fully rooted, etc. But I can't seem to get it to work.
This is the command I'm using in adb
Code:
# rm /system/app/something.apk
(replacing something.apk with the actual apk name of course)
When I boot in Recovery, it says "File not found". When I boot in Fastboot, I can't connect to adb it seems. And when I boot into Android, it says "rm failed for something.apk, Read-only file system"
So am I missing a step? What should I be doing differently?
Boot into recovery, then do a "mount -a" to mount the filesystems.
marinierb said:
Boot into recovery, then do a "mount -a" to mount the filesystems.
Click to expand...
Click to collapse
It doesn't seem to work, here's the output:
Code:
C:\asdk\tools>adb devices
List of devices attached
HT9ALNT00557 recovery
C:\asdk\tools>adb shell
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or direc
tory
/ #
Thanks for the reply though.
Edit: Got it working, typing in "mount" alone without the -a switch worked Thanks marinierb
in normal mode you cold have just done
adb remount
adb rm /system/app/something.apk
garok89 said:
in normal mode you cold have just done
adb remount
adb rm /system/app/something.apk
Click to expand...
Click to collapse
That doesn't seem to work for me. This is what it outputs:
Code:
remount failed: Operation not permitted
If you can't remount it doesn't sound like you've rooted.
callummr said:
If you can't remount it doesn't sound like you've rooted.
Click to expand...
Click to collapse
I've performed other operations that would normally require it, so I should be rooted.
Is there a way I can confirm if it's properly rooted or not?
shell prompt:
$ .. no root
# .. root
..try typing "su" once in the shell (abd shell or adb-windows.exe shell) and see what it brings up
~David said:
It doesn't seem to work, here's the output:
Code:
C:\asdk\tools>adb devices
List of devices attached
HT9ALNT00557 recovery
C:\asdk\tools>adb shell
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or direc
tory
/ #
Thanks for the reply though.
Edit: Got it working, typing in "mount" alone without the -a switch worked Thanks marinierb
Click to expand...
Click to collapse
typing only "mount" just list the mounted partitions, it will not mount anything. if your partition is ext4 you need to downgrade it to ext2 or ext3 or set the testflag, see "if you're having issues with ext4" in the first post of the recovery image thread.
Make sure you have run a Nandroid backup first so that if you accidentally remove something important.
Boot into normal mode. (full GUI)
Then:
Code:
C:\ADB MOUNT
C:\ADB SHELL
# rm /system/app/something.apk
reboot
You have to reboot at the end so that the apps are taken out of RAM, you may get FC (errors) if you try to do stuff after removing the apps before rebooting.
I removed (actually moved) *Twit*, Stock*, Launcher*, and a few other things.
HTH,
Unconn
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or getting flammed because you re-rooted your phone instead of your tablet because you forgot to unplug your phone from the computer while the tablet was plugged in...
Please do some research if you have any concerns about rooting your device! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Ok, this was a pain in the arse!
I hope I can remember the steps I took in order to get this done.
By the way, I'm using windows
adb push mempodroid /data/local
adb push su /data/local
adb shell
$ chmod 777 /data/local/mempodroid
Click to expand...
Click to collapse
Then I went to here as directed,
http://rkeene.org/projects/info/wiki/210
but didn't follow the steps as they were shown because I got stuck many times and had to start over.
So here are my steps.
1.
$ /data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
which then should turn the $ into a #
2.
# mkdir /data/x-root /data/x-root/bin
Click to expand...
Click to collapse
3. Download this,
http://www.rkeene.org/projects/info/resources/diatribes/root-toshiba-thrive/busybox
and then move the file to where you have mempodroid and su so you can adb push them easier
4.
adb push busybox /data/x-root/bin/busybox
adb push su /data/x-root/bin/su
adb shell
Click to expand...
Click to collapse
5. This is where it got tricky. If you don't pay close attention, you will most likely do what I did and put files where they aren't supposed to go. So please, PAY ATTENTION!
If you still have the # in the shell, move forward. Otherwise,
/data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
and then move forward once # is confirmed.
# cd /data/x-root/bin
# chmod 755 busybox
# ./busybox bash
Click to expand...
Click to collapse
Now, there is no doubting it, you will get the "bash: precmd: not found" error.
# unset PS1 PROMPT_COMMAND
# ./busybox bash
# for tool in $(./busybox --list); do ln -s busybox $tool; done
# PATH="${PATH}:/data/x-root/bin"; export PATH
Click to expand...
Click to collapse
6. AGAIN, PAY CLOSE ATTENTION HERE!!
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
Click to expand...
Click to collapse
7. This is where I ran into another problem, so pay attention.
# cd /
# mkdir /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
You will see nothing as the steps describe. This is because we skipped a step. Why? Because mount -o ro -t ext4 /dev/loop0 /dev/tmpdir for some strange reason wouldn't unmount so I could mount the next step. So instead, we move on and then check again.
Here is the removed step
# mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
# umount /dev/tmpdir
Click to expand...
Click to collapse
You can try this but I advise not to or you could very well run into the same issue I had where you can't unmount in order to move on with the root process
# mount -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
And now you will see /system mounted.
8.
# cp /data/x-root/bin/su /dev/tmpdir/bin/
# chmod 4555 /dev/tmpdir/bin/su
# umount /dev/tmpdir
# losetup -d /dev/loop0
# sync
# reboot
Click to expand...
Click to collapse
9. Now once your A200 reboot and displays the home screen, we will confirm.
adb shell
[email protected]:/ $ su
Click to expand...
Click to collapse
If the $ doesn't turn into a #, you did something wrong...
Thank you hexmare, for opening this thread and giving the guidance.
Thank you d10369319, for "/data/local/mempodroid 0xd9f0 0xaf47 sh", I would have never figured this out.
Thank you RKeene, for writing out the guide to Root the Toshiba Thrive
And Thank you Saurik along with zx2c4, for mempodroid
Ok, for some reason, /system still refuses to mount with "mount -o remount,rw /system"
So my solution is this,
$ su
# cd /data/x-root/bin
# chmod 755 busybox
# unset PS1 PROMPT_COMMAND
./busybox bash
# PATH="${PATH}:/data/x-root/bin"; export PATH
# cd /
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
# mount -t ext4 /dev/loop0 /dev/tmpdir
Click to expand...
Click to collapse
You will have to go to /dev/tmpdir in order to do anything with /system but it is the secret passage way for now...
Why is there still no A200 forum?
agentfazexx said:
Why is there still no A200 forum?
Click to expand...
Click to collapse
Maybe there will be now that we have made some progress...
agentfazexx said:
Why is there still no A200 forum?
Click to expand...
Click to collapse
+1 A200 Forum
Enjoy your ICS A200 owners. I just saw a tweet from AcerAmerica that ICS is being rolling out to A200
Hello to all,
My A200 has been upgraded today 'OTA' , to ICS (V: 4.0.3) , so Europe/France seems to be available, now.
Applying this procedure, all goes fine, and my A200 is rooted.
I'm very happy
A lot of thanks to people having discovered this procedure, particularly mempodroid which set all of this possible.
Greetings
the last time when you do losetup -d /dev/loop0
returns No such device or address?????
ive been through it twice now
*EDIT* Nevermind I figured out my problem...I was typing in reboot instead of using the hardware power button. Got root now, sweet!
I am sooo glad we can now root the a200, but I cannot get mine to work. I have went through the steps 3+ times and had issues each time. I thought I had it twice and then tried Titanium backup root and it said it didn't work.
I can't see at all where I've gone wrong..
That's very strange because Titanium Backup works just fine for me...
rom toolbox pro doesnt work when changing numbers in kernel tweaks...numbers dont stick
titanium works though
ran into a mounting issue
i was attempting to root my A200 with the OTA ICS
first attempt i ran into an issue were i am unable to mount
# mount -t ext4 /dev/loop0 /dev/tmpdir
mount: invalid argument
so i then replaced ext4 to EXT4 and i then received error
# mount -t EXT4 /dev/loop0 /dev/tmpdir
mount: No such device
could some one please tell me where i went wrong thank you in advance
what i do wrong when i try adb push mempodroid /data/local i get evertime this here :/
D:\android-sdk-windows\platform-tools>adb push mempodroid /data/local
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Ghorn
ghorn222 said:
what i do wrong when i try adb push mempodroid /data/local i get evertime this here :/
Ghorn
Click to expand...
Click to collapse
Go download the drivers from Acer's website for this device
johnsonj067 said:
i was attempting to root my A200 with the OTA ICS
first attempt i ran into an issue were i am unable to mount
# mount -t ext4 /dev/loop0 /dev/tmpdir
mount: invalid argument
so i then replaced ext4 to EXT4 and i then received error
# mount -t EXT4 /dev/loop0 /dev/tmpdir
mount: No such device
could some one please tell me where i went wrong thank you in advance
Click to expand...
Click to collapse
You have to follow the guide to the T or you will run into numerous problems and stop signs. Try again
daimerion said:
rom toolbox pro doesnt work when changing numbers in kernel tweaks...numbers dont stick
titanium works though
Click to expand...
Click to collapse
That's because we don't have a custom kernel yet. Just wait a little while.
Unfortunate the root isn't 100% cool my boot loader Is unlocked though.
Droid 3 bldr is locked down however changing numbers in rom toolbox works w/o custom kernals or modules.
http://www.acertabletforum.com/foru...iscussions/3649-how-unlock-boot-loader-4.html
^this Does work
su file?
This may be a stupid question, but where does one get the su file they're supposed to push to the tablet in the first step? I searched and searched, and finally found one that I downloaded, but when I tried this method with that su file, everything seems to work perfectly, but when I reboot and type su I get a segmentation fault. This is feels like something everyone knows but me, because every guide I can find that has anything to do with rooting from adb it seems the possession of an the su file is just assumed.
shwilson24 said:
This may be a stupid question, but where does one get the su file they're supposed to push to the tablet in the first step? I searched and searched, and finally found one that I downloaded, but when I tried this method with that su file, everything seems to work perfectly, but when I reboot and type su I get a segmentation fault. This is feels like something everyone knows but me, because every guide I can find that has anything to do with rooting from adb it seems the possession of an the su file is just assumed.
Click to expand...
Click to collapse
Did u use reboot command or the power button on the tab? It only worked for me when I used the power button to turn off then on
daimerion said:
Did u use reboot command or the power button on the tab? It only worked for me when I used the power button to turn off then on
Click to expand...
Click to collapse
I tried using the power button. Same result. Where did you get the su file from?
I followed the instructions here: http://www.modaco.com/topic/361797-...-30android-235-guide-to-root-s-offsim-unlock/ but i always recieve errors. Is there any other way to get s- off?
crazynitro said:
I followed the instructions here: http://www.modaco.com/topic/361797-...-30android-235-guide-to-root-s-offsim-unlock/ but i always recieve errors. Is there any other way to get s- off?
Click to expand...
Click to collapse
adb shell /data/local/tmp/goldcard -c <string of numbers and letters should go here> -o /data/local /tmp/goldcard.img
this command is an error, it should be without a space after local,and remove the whole <sh*there> part and paste your goldcard numbers and letters.This is a step where most get stuck, I merely assumed you were here too.Describe on where you get stuck
Steam. said:
adb shell /data/local/tmp/goldcard -c <string of numbers and letters should go here> -o /data/local /tmp/goldcard.img
this command is an error, it should be without a space after local,and remove the whole <sh*there> part and paste your goldcard numbers and letters.This is a step where most get stuck, I merely assumed you were here too.Describe on where you get stuck
Click to expand...
Click to collapse
Thanks for replying i tried it but it said: The system cannot find the file specified. :/
way before that, when i entered this command: adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img , i got the response: /dev/block/mmcblk0p22: cannot open for read: Permission denied. Is this normal?
crazynitro said:
Thanks for replying i tried it but it said: The system cannot find the file specified. :/
way before that, when i entered this command: adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img , i got the response: /dev/block/mmcblk0p22: cannot open for read: Permission denied. Is this normal?
Click to expand...
Click to collapse
are you running the command from your phone or from your PC?I see you have skype, why don't we have a little chat there..
Steam. said:
are you running the command from your phone or from your PC?I see you have skype, why don't we have a little chat there..
Click to expand...
Click to collapse
i'm using my pc. whats your skype name?
crazynitro said:
i'm using my pc. whats your skype name?
Click to expand...
Click to collapse
I just added you.
After flashing lot of stock firmwares i still get bootloop. There's log from CWM:
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.dexopt-data-only=1
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.heaptargetutilization=0.75
persist.sys.dun.override=0
persist.sys.usb.config=mtp,adb,adb
persist.sys.vold.swithablepair=sdcard0,sdcard1
persist.sys.dalvik.lib=libdvm.so
persist.sys.root-access=1
persist.sys.recovery_update=false
persist.service.adb.enable=1
service.adb.root=1
keyboard.no_require_sim=true
mobiledata.interfaces=pdp0,wlan0,gprs,ppp0
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Cannot load volume /misc
I:[Touch] Loading virtual keays file: /sys/board_properties/virtualkeys.sec_touchscreen
I:[Touch] Could not open virtual keys file
I: Can't partion non mmcblk device: /devices/sdi2/mmc_host/mmc0/mmc0
I: Can't partion non mmcblk device: /devices/sdi2/mmc_host/mmc1/mmc1
When I wipe dalvik cache:
I:200 0 volume operation succeded
rm: can't remove '/sd-ext/dalvik-cache': No sucg file or directory
Please help! I'll ry everything, I really need my phone... :crying:
Whats ur phone model. From which country. Whats the name of the md5 package. List more details about ur phone
teddytsen said:
Whats ur phone model. From which country. Whats the name of the md5 package. List more details about ur phone
Click to expand...
Click to collapse
ehh..I8160P bought in czech republic..installed cyanogen mod 11 by Rox [android 4.4.4]
Md5 file--stock not what rom.
i don't know :/ it was android 4.1.2 (O2C)
sutr96 said:
I:[Touch] Loading virtual keays file: /sys/board_properties/virtualkeys.sec_touchscreen
I:[Touch] Could not open virtual keys file
Click to expand...
Click to collapse
Connect the phone to pc and type via adb:
Code:
dmesg
and attach log here.
ChronoMonochrome said:
Connect the phone to pc and type via adb:
Code:
dmesg
and attach log here.
Click to expand...
Click to collapse
Ehh, can you suggest me some guide? I'm noob at android. :/
sutr96 said:
Ehh, can you suggest me some guide? I'm noob at android. :/
Click to expand...
Click to collapse
There are no any special guides, afaik. Just connect the phone to the PC, then type via cmd.exe(windows) or the terminal (ubuntu) on PC:
Code:
adb shell
dmesg > /storage/sdcard1/dmesg.log
Then attach it here.
ChronoMonochrome said:
There are no any special guides, afaik. Just connect the phone to the PC, then type via cmd.exe(windows) or the terminal (ubuntu) on PC:
Code:
adb shell
dmesg > /storage/sdcard1/dmesg.log
Then attach it here.
Click to expand...
Click to collapse
Adb not worked for me, sayd error device not found. After lot of unsuccessful flashed firmwares I think internal storage is broken. When i want delete something, it take 15 minutes for one file I try go to shop and ask for repair. I hope repair will not be expensive.
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.