Have seen some posts where people got stuck in boot loop after changing system fonts. I got in that too.
To avoid that set permission & ownership to as original (Read - All , Write - Owner & Ownership - Root) before reboot & you shall be good.
Related
1. whats rooting ?
2. whats recovery for?
developers please tell me ... i read somany things and i am totally no where... windows was good for this
sathara said:
1. whats rooting ?
2. whats recovery for?
developers please tell me ... i read somany things and i am totally no where... windows was good for this
Click to expand...
Click to collapse
you need root for flashing custom roms that are not HTC/Google branded
you use recovery for backup your old Rom before you flash the new one ( so if brick it you can flash your old backup again )
Thats what i know
1. Rooting means get the root access right, since Linux system has very strict access control, without root access it is not possible to do any system level changes (including flashing the customized rom, change the system settings...)
2. Recovery is a special partition located in the rom, actually a recovery is a pre-built system image (a small fixed Linux system) that can be boot. With booting the recovery you can do a lot of changes to the normal booting system (ie. the /system and change the kernel with located in the boot partition in the rom). And with a lot of person's effort, the recovery image now getting easier by many preconfiged script on the menu, so that can get the system update, backup/restore and other system level changes)
rdcsueq said:
1. Rooting means get the root access right, since Linux system has very strict access control, without root access it is not possible to do any system level changes (including flashing the customized rom, change the system settings...)
2. Recovery is a special partition located in the rom, actually a recovery is a pre-built system image (a small fixed Linux system) that can be boot. With booting the recovery you can do a lot of changes to the normal booting system (ie. the /system and change the kernel with located in the boot partition in the rom). And with a lot of person's effort, the recovery image now getting easier by many preconfiged script on the menu, so that can get the system update, backup/restore and other system level changes)
Click to expand...
Click to collapse
1. That is correct.
2. That is correct.
Well done. You have passed the test. You may collect your cookie and be dismissed.
thanks bro ... i got every thing cleared and i flashed custom rom
This is insane... Creating new thread for the questions that are already answered....
Hello Fellow XDA Readers ,
I would like to bring back to the front some ways to change your boot animation on a Rooted Android phone without having
to use Rom Tool Box. I only started this topic again due to the fact that Rom Tool Box will only change your Boot Animation if your Bootloader is unlocked.
So, Some people have ran into that issue ..
Check XDA for boot animations or Google., for your device. and down load the required files *.QMG files
Once you have them downloaded, move them to your device. and copy them to your System/Media folder. (Pertaining you are Rooted)
Rename your existing boot and bootlogo files, rename them to the extension of (.BAK) minus the caps lock,,,lol
After you do that , make sure you set the permissions to ( -rw-r--r-- )
After you complete those steps. Fee free to Reboot and enjoy your new boot animation.
If you have any questions please post them. I will reply to them and answer them the best I can.
XDA:DevDB Information
Changing Boot Logos on Rooted Phones, Theme for all devices (see above for details)
Contributors
Sketch2017, Sketch2017
Version Information
Status: Stable
Created 2017-02-10
Last Updated 2017-02-09
As you may know, it's the time of the year when new phones get released and everyone is eager to grab the new boot animation!
Following this post is the Boot Animation grabbed directly from the system dump of the Google Pixel 2.
I will post the boot animation of the Pixel 2 XL at a later date.
Warning: I am not liable for any damage caused by the content in this forum. You agree to use my content at your own risk!
Instructions:
1. Download the file :
HTML:
https://goo.gl/KQ9ei7
2. Open your preferred Root Browser (ES, FX etc.) and give it root access. Then, navigate to system/media/.
3. Copy and paste the new boot animation exactly the way you download it into this folder (Change the permissions to rw-r-r).
4. Last but not least, rename the old boot animation to "bootanimation.zip.b" to retain the old boot animation if you want to go back.
5. Finally, reboot your phone and Voila! You have successfully changed the boot animation.
Note: This has been tested on a Nexus 5X.
Comment below for any questions!
The resolution of the animation is 1080x1920
Context: my motorola g4 is 5 years old and saw many different kinds of root attempts and amateurish handling (like modifying the system image) in its early days. I settled on magisk when it became a thing. Now I'm trying to go back to being rootless, including removing left-behind stuff like addon.d scripts.
TWRP shows a /supersu folder in the root fs, containing the usual apk, sh scripts, etc. I can delete this folder, but next time I boot my device (even just recovery!) it gets restored _somehow_. This is the only remaining trace of rooting I'm aware of, aside from the image just "not being untouched stock" anymore.
I'd like to get this folder permanently removed, without erasing my data.
Things I've tried:
- flash the stock rom: somehow it's defective (Package Installer crashes and I can't fix it by any means), despite it being the same zip I flashed two years ago and still use today, so this is not an option
- flashed stock boot
- unSU https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
- installed supersu just to run its own unroot procedure, then ran unsu again, then flashed stock boot again
It just keeps coming back after every time I delete it and I'm out of ideas to stop it. All the threads I've found online offered only the above solutions that don't work.
Thanks for any good tips
@Marnes That sounds like it's TWRP's superuser. It won't exist if you are not booted to TWRP and it'll be repopulated everytime you boot to TWRP...
@Didgeridoohan I hadn't considered that possibility... I guess there's no way to verify it since checking after a regular boot if the folder is there would require rooting again. Thanks for the input!
Namaste friends! Today we will learn how to remove Xiaomi's apps from Android's native battery optimization function also known as 'Doze' and how to optimize the whole MIUI further more for acute battery and performance optimization too.
Note: Please continue on your own risk. I will never be held responsible for anything you cause to your device. As I've never experienced any minor / major issues after the process explained here in this post. So, proceed on your own risk.
This process is extensively tried and tested multiple times with multiple MIUI release versions on a same single device running a global version of MIUI 12.5 and so. The device underwent in this process is Redmi 9 Power (India). Let's not waste time for modding our device to our own need.
Requirements: A Xiaomi device having root and unlocked bootloader with a custom recovery (TWRP/else) installed on it. A good root file manager, in my case it is MixPlorer.
Let's begin
Clean flash your ROM (Recovery or Fastboot, make sure the bootloader is unlocked after the flash) .
Reboot to recovery and flash Magisk Pathed Boot.img of the ROM you just flashed.
Format and reboot to system.
After boot, proceed with installing Magisk apk followed by MixPlorer.
Launch MixPlorer > goto /root folder > grant root (Magisk PopUp) .
Go to /system/xbin and delete all files in there. (these files do something at device boot-up and patch something before the lock screen appears) .
Again in /system/etc/sysconfig delete the xmls that include 'Xiaomi app names' with "allow-in-power-save" tag. You can also rename the xml file extention to anything other than xml that will also work like they are deleted or not there. ( XMLs like - miui core, miui-whitelist, power save config etc. Please open the xmls and verify before modifying the same )
Now head to /system/etc/permission, delete XMLs with "Facebook" names. You can also review some more XMLs in there as I found and patched some more XMLs including "allow-in-power-save" followed by mi apps.
If supported, go to /product/etc/sysconfig and rename google.xml to google.bak for gms to be optimised on next reboot.
Now debloat: Delete apps and their corresponding files in the same folder where apps are. Do not delete the folder only delete the apk and its dll or odex / vdex files. ( Never delete Find device, Mi account, Security etc.)
Now when done, reboot to recovery > format data > reboot to system.
to be continued...