Found the directory storing bootanimation.zip in Product/Media However the files themselves cannot be modified even though I have rooted with magisk and tried to move them with Material Files. Device passes safetynet attestation. Tried booting into twrp, and mounting the partitions. It cannot even read the files in product partition, only folder shows up. When moving a bootanimation.zip file into the Product/Media directory it gives an error message. Obtained the boot animation from OnePlus 7 Pro forums. Need some help getting rid of this ugly magenta logo. Thanks
Edit: On OOS 11.0.3BE88CB
Ive also been trying to change boot animation.
OxygenOs 11.0.2.BE86AA
Rooted w/ magisk
It's in /system/product/media for stock roms and /system/media for gsi roms.
heres a couple that i use, one is the same as stock, only blue, the other i barrow from octavi gsi.
Be careful not to change the permissions on the file if you swap it out.
Related
Dear fellas,
I replaced my build.prop file to an another one and my phone is not booting up anymore.
I have a rooted Xiaomi Mi 5s Plus, with custom recovery.
Can anyone advise what to do without wiping the phone completely and flashing a new ROM?
What I've tried doing:
- I had the original build.prop that the phone had before it got stuck.
- I used the file explorer in custom recovery, copied that file to the system folder in root.
- Rebooted the device, still no luck!
- After rebooting, when I reopen the recovery, and navigate to the system folder again, I don't find the file I copied to the system folder!
Any thoughts on the matter please? Thanks in advance!
Have you tried writing original Rom to the phone. Don't have much experience with that kind best I can suggest
Sent from my SM-G930V using Tapatalk
black_hawk1990 said:
Dear fellas,
I replaced my build.prop file to an another one and my phone is not booting up anymore.
I have a rooted Xiaomi Mi 5s Plus, with custom recovery.
Can anyone advise what to do without wiping the phone completely and flashing a new ROM?
What I've tried doing:
- I had the original build.prop that the phone had before it got stuck.
- I used the file explorer in custom recovery, copied that file to the system folder in root.
- Rebooted the device, still no luck!
- After rebooting, when I reopen the recovery, and navigate to the system folder again, I don't find the file I copied to the system folder!
Any thoughts on the matter please? Thanks in advance!
Click to expand...
Click to collapse
Try mount system read/write first then copy og build prop file in system partition and reboot or use aroma file manager.
Hello.
I'm using Xiaomi Pocophone F1 (Global Edition). Upgraded from Android Oreo (8.1) MIUI Global 10.0.6.0 to Android Pie (9.0) MIUI Global 10.1.3.1 using system update (choose update package), then it will update through custom recovery, TWRP. The phone is root using Magisk v18.0.
Before I upgrade to Android Pie, I was able to move files from internal storage and SD Card to /system folder, such as bootanimation.zip. I'm using ES File Explorer Pro as a File Manager, and I already enable the Root Explorer in the tools tab. Next, I able to flash ARISE Sound Systems such as Viper4Arise, Dolby Digital Plus and Dolby Atmos. It works pretty good.
Right after I upgrade my phone to Android Pie, I can no longer create, move, modify files in /system folder. Moving files using the TWPR File Manager also failed. I also can't flash ARISE Sound Systems sound mod. There's no error flashing the sound mod, but after rebooting, the phone is still the same, no Viper4Arise, Dolby Digital Plus or Dolby Atmos was found.
Outside the system folder, (the root folder, "/"), I'm able to move the bootanimation from my internal storage and SD card to there.
I tried changing the ro.debuggable = 1, ro.secure = 0, ro.build.type = userdebug, using the MagiskHide Props Config modules. I don't know if that have something to do with my problem, but still no luck. I also have Busybox enabled in Magisk modules.
It seems like there's a problem with the system folder. Maybe it's because of Android Pie? Or the File Manager itself? Or Magisk? Who knows.
Below I provide you the screenshots of the result when I tried to move my bootanimation.zip file to /system folder.
I hope someone could help me with my problem. Thank you for taking your time to read my thread.
- Chaorrupted X - said:
Hello.
I'm using Xiaomi Pocophone F1 (Global Edition). Upgraded from Android Oreo (8.1) MIUI Global 10.0.6.0 to Android Pie (9.0) MIUI Global 10.1.3.1 using system update (choose update package), then it will update through custom recovery, TWRP. The phone is root using Magisk v18.0.
Before I upgrade to Android Pie, I was able to move files from internal storage and SD Card to /system folder, such as bootanimation.zip. I'm using ES File Explorer Pro as a File Manager, and I already enable the Root Explorer in the tools tab. Next, I able to flash ARISE Sound Systems such as Viper4Arise, Dolby Digital Plus and Dolby Atmos. It works pretty good.
Right after I upgrade my phone to Android Pie, I can no longer create, move, modify files in /system folder. Moving files using the TWPR File Manager also failed. I also can't flash ARISE Sound Systems sound mod. There's no error flashing the sound mod, but after rebooting, the phone is still the same, no Viper4Arise, Dolby Digital Plus or Dolby Atmos was found.
Outside the system folder, (the root folder, "/"), I'm able to move the bootanimation from my internal storage and SD card to there.
I tried changing the ro.debuggable = 1, ro.secure = 0, ro.build.type = userdebug, using the MagiskHide Props Config modules. I don't know if that have something to do with my problem, but still no luck. I also have Busybox enabled in Magisk modules.
It seems like there's a problem with the system folder. Maybe it's because of Android Pie? Or the File Manager itself? Or Magisk? Who knows.
Below I provide you the screenshots of the result when I tried to move my bootanimation.zip file to /system folder.
I hope someone could help me with my problem. Thank you for taking your time to read my thread.
Click to expand...
Click to collapse
I personally have almost the same setup as you (magisk 18 but updated using stock recovery) and have no issue using jrummy root browser (https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree). Try with it
Blendman974 said:
I personally have almost the same setup as you (magisk 18 but updated using stock recovery) and have no issue using jrummy root browser (https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree). Try with it
Click to expand...
Click to collapse
It's okay. My problem has been solved. I flash the rom (same version as I'm using) through the TWRP, without wiping anything (except dalvik cache). Root with Magisk. Now I can create, move and modify files in the /system folder.
Thanks for the suggestion anyway. I did try the jrummy Root Browser before I flash the rom through TWRP, but it's still the same.
I guess there's problem during my first upgrade to Android Pie.
- Chaorrupted X - said:
It's okay. My problem has been solved. I flash the rom (same version as I'm using) through the TWRP, without wiping anything (except dalvik cache). Root with Magisk. Now I can create, move and modify files in the /system folder.
Thanks for the suggestion anyway. I did try the jrummy Root Browser before I flash the rom through TWRP, but it's still the same.
I guess there's problem during my first upgrade to Android Pie.
Click to expand...
Click to collapse
Google enhanced the security on Android 9 including the Safetynet. I think that's the reason why we can't just deliberately create nor modify /system partition
I need help editing the default.prop of my rooted boot.img for an LG LM-X210ULM K8+. I want to mark ro.debuggable off as 1 instead of 0 but which i have no problem doing but when i use any kitchen program it puts it back together as 15mb instead of 32mb and when i flash it to my device it always bootloops.
If any one could help i would appreciate it. Im including a copy of the rooted boot.img freshly pulled ftom my device
The size probably isn't the issue. Using AIK the size was even bigger than the original.
It's all just 0x00 the rest of that partition...
By using my old uImage/_recovery unpack-repack batch file
http://cxzstuff.blogspot.com/2013/03/uimagerecovery-unpack-repack-batch-file.html
the result was smaller but still a bit bigger than the Magisk had made.
But that is irrelevant really... result attached.
Yea i dont get it. The size doesnt matter as long as it diesnt exceed the max amount of space the partition can hold. But why does changing one value cause the boot.img to boot loop after flashing.
Even the boot.img you made looped after flashing
Duhjoker said:
Even the boot.img you made looped after flashing
Click to expand...
Click to collapse
Just tells that it's not the tool used. Or mine oldie is as bad/good as the newer one in this case.
What that Magisk img had was like it had some signature but it should not be needed and probably just garbage left there from the stock...
Should not matter, but how about doing it other way around? Modify the stock boot first and then give it to Magisk for rooting.
I think it was stock. Ill have to make sure though. wonder why magisk doesnt make the image debuggable to begin with. But your right it might be that im using a magisk patched image. Ive got some firmware already broke down ill give it another try here in a bit and post my results.
Duhjoker said:
I think it was stock. Ill have to make sure though. wonder why magisk doesnt make the image debuggable to begin with. But your right it might be that im using a magisk patched image. Ive got some firmware already broke down ill give it another try here in a bit and post my results.
Click to expand...
Click to collapse
So here we are. There should be some shortcut or something left to the original sub forum at least for a week or two when you boys move these threads - dammit...
Any luck? You have a customized recovery? How about these?
https://forum.xda-developers.com/an...g/mod-bootimage-adb-unsecure-patcher-t3618558
Yes luck tonight i did a fresh reflashing on my QC Lg k8+ and decided to break open the boot.bin from the kdz i used and made my changes to default.prop then i put the renamed to boot.img on my phone and let magisk patch it then flashed it via fastboot and dared it to go into system. Then i double dared it. Then for safe measure i double dog dared it to boot into system to which it had no choice but to go along with the or be labled a @!%\**__(€.
It booted.
So the lesson learned is to patch a fresh boot.img with your default.prop changes then have magisk patch it for root.
Now oddly when i patched and tweaked my recovery using carlive kitchen, i also made sure that the same changes to default.prop or rather i made sure they had been made and they had. But any terminal like emulator or termux pulls up the props using getprop with the changes unmade and i still cannot change the values of the system build.prop and when i patch it manually it reverts on reboot.
I literally have to open a vi in twrp to make changes. And forget about copying my own patched build.prop to system in twrp. Because that leads to boot loop as well
Ok so is there a reason that you dont make those changes in the boot.img any more? Because the past two days i have woke up to no root. I have had to reflash my boot.img both times
Ok i just compiled my first kernel from lg source code and now i dont know which of the split images in my folder is the zimage
Back to the drawing board quite literally. Im stuck for sure.
I need to make edits to a few files like init.rc and init.lge.power.rc to allow for changes in my newly compiled kernels. Basically im adding a couple properties and some cpu frequency stuff. Plus i want to make it back to adoptable storage and add a second sd partition for ext4 projects im working that would work best right off the root file system.
Im using the stock extracted boot.img from a kdz using salt and carliv kitchen to unpack and repack i have also mkbootimg tools that i compiled myself and some static arm version.
I extracted the ramdisk place my new kernel image in and repack with the init files changed and flash using recovery or fastboot and bootloop every time. And magisk isnt signing with the verity key.
ok i dont know whst was going on the other day but i can split boot.img again and make changes with out looping.
i used gparted on my linux machine to partition my 128gb sd card with 3/4 vfat and 1/4 ext4 i know that by using adb it will automount but thats one timr and i may need to switch out every now and then plus it put a center part in it of about 15mb. with gparted i get the two parts with no bs. any way i created a script that mounts the second part and even symlinks some stuff. it works good but im having trouble getting init.rc to run it.
on early-init
chmod 0755 /system/etc/init/init.mntsd.sh
exec system system /system/bin/sh /system/etc/init.mntsd.sh
any tips
Hi!
I noticed that all change i made in system or vendor build.prop are ignored, or in some other xml files, even if i made a factory reset!
I try to add camera2 API and doesn´t work as example, APN changes to, etc...
The files i add, Change after boot still like stock but if i mount it on twrp it shows the changes i made!
Why?!
After some research i think there is no way to tweak system or vendor.
In some way i think vendor and system are writed in data when is flashed and stay in encriped data partition and when it boot only read data.
I read in some where that images only are use for fast update like dual images something problably the tweak image is not the one in use...
https://source.android.com/devices/tech/ota/ab/
Only customs ROMs will work maube because it have their own boot images and works in a diferent way.
I think it is the end of stock mods... :\
Thanks
Hello i had the same problem in android 10 miui 11.0.3 // you will need to reinstall your stock rom from https://xiaomifirmwareupdater.com/miui/platina/ fastboot rom using mi flash tool
After flash done flash twrp / magisc / install root explorer.
After that you should be able to edit again these files.
Or you can use twrp file manager to edit that .xml files // find a recovery that have the ability to edit those files.
Hi,
I have recently been pulling build.prop from my phone using a booted twrp and mounting the system folder using twrp.
I am on linux, and the file appears in my home folder.
---fine--
I am no expert when it comes to the android system so can anyone explain this?
If I flash stock to my sony experia z2, I can pull build . prop from /system/build.prop.
However, after flashing lineage over stock, I seem to have two systems, and I pull build.prop from /system/system/build.prop?
Even if prior to flashing the stock rom with TWRP, I erase the stock rom ''system'' folder, after flashing I still have to navigate past two systems in order to get to build.prop?
I am guessing that is normal? - or am I doing something wrong?.
pootler
Thread closed on request of OP @pootler