I am preparing to use this phone as a dedicated display on a custom embedded system. Changing the boot logo is a must. I have been playing around with it and reading threads for hours and no luck.
Rooted with the latest Magisk, TWRP, unlocked bootloader, the whole 9 yards. A10 Stock ROM. I don't care I break SafetyNet, just need this to work.
I can't put the new bootloader on the system partition because it's mounted as read only. Since it's A10, I haven't found a working way to modify it with TWRP or within the ROM. Has anyone been successful yet?
There are existing Magisk modules for boot animations, but I need a custom one, and I don't know how to make it into a flashable ZIP. How do they do this?
I also tried a Magisk module that is supposed to let you put the boot animation on /sdcard, and it gets overridden on boot by the module, but that did nothing. But it was on a OnePlus forum, so maybe incompatible.
Thanks!
Hi
I think since A10 you can't mount the system unless in certain ROMs. You can try flashing Lineage OS 17.1 ROM since it allows you to mount the system partition.
I'm not sure about how to compile a magisk module. But you can Google it or search it here in xda, I think you might find a post about that.
Related
Hi all,
so today I found a treble-enabled ROM of Android Pie and wanted to flash it. Thing is, I need to enable treble for me first. The treble check says that Treble is indeed supported, and so does the OnePlus website, but I don't have access to the vendor partition in TWRP. Using TWRP 3.2.3-1, by the way.
So, I read that MoKee enables Treble. Tried that, flashed the rom, flashed the radio and then the rom, factory wiped, flashed rom, factory wiped, flashed radio and rom, nothing. Still can't get Treble support. Then I tried kylothow's Trebliser, but nothing there either. I am realy at a loss here - I even reinstalled OOS (newest beta of course) and I couldn't get the vendor partition to show up, which is weird considering installing said trebliser actually states "Vendor partition found, good!" when installing, and then proceeds to in fact patch the vendor partition. It just doesn"t do anything, I can't install GSIs, can't even get the treble check to register that I do in fact have treble.
So this is where I turn to you guys. Do you have any idea what I could do in this situation? Please answer genuinely and don't post "just wait for an official android p".
Thanks!
Okay there's a few things remember here after flashing the mokee trebleize pack you should have had the addition of the vendor partition included in your TWRP file system if you have the blue spark TWRP version YOU SHOULD BE ABLE TO SEE THE ADDITION OF THE VENDOR PARTITION WHEN YOU GO TO MOUNT FOLLOWING THAT.
*** Make sure that after the trebleize is installed or whatever don't touch vendor partition ever just leave it alone you don't need to do anything to it it's fine if some ROM needs to update it you don't have to worry about wiping it first because it'll take care of that with the configuration script in the zip file. Even if you want to go back to a regular Android 8. 1 ROM you don't have to worry about the vendor partition the way it's set up the vendor partition that exist inside the one plus 5T that was created for Treble is not seen by any AOSP ROMs so it's going to create its own vendor folder inside of the system partition like it normally does and that you will not conflict because the fs tab does not Mount the new vendor. By leaving vendor alone and never touching it you're just ensuring that when you flashed yes eyes you're not missing something that's essential to the boot up process and it's one thing that you can from any potential uncertainty as to why a treble mage may or may not be booting.
Follow this....
Normal Android ROMs you would usually wipe system data cache D-cache if you were going to install a new ROM that wasn't just an upgraded version of the one that you were already running you'd have to start from scratch always. This is still what you should do it whenever you want to start and flash a fresh regular ROM or treble run always do that but it's how you proceed from here that is a little difference between the two.
With a regular ROM you would just go on to flash the ROM that you want to install followed by Gapps and so on.
When you want to flash a treble image you need to be on a clean fresh ROM that has treble support already good to go in that it can see that vendor partition that was made before and that it contains the binderized HALs needed as well. Because official treble support is still in beta with the OnePlus 5T the only officially supported treble Android 8. 1 ROM is mokee so you always want to start with a clean flash of the Mokee ROM because it also contains the supported kernel and ramdisk and other things as well.
Upon flashing a fresh version of mokee you want to go ahead and Flash no-dm-variety to ensure data is not encrypted because it will lead to a bootloop and the only way to get it to work will be to either format your SD card or to install the no variety which is the way to go just install it every time you flash mokee so that way you know everything is good.
**** I've only had experience using Android 8. 1 GSi so I'm not sure exactly how it would work concerning open G apps because I've only had to do it with two 8. 1 apps I'm not touching the Android P treble ROM until it's official so anything that I'm saying here has nothing to do with that if that's the image you're trying to install that I can't help you with it because I don't honestly know I remember reading something about that changing something different with it and I got to read up more on it.****
So next part depends on whether the GSI you're trying to flash comes with GFS included inside of it some do some don't I think most do but just make sure you read the instructions on the forms from where you download them from where they will tell you about the gf's the ones that I've installed that didn't have gf's on I would install mokee then I would flashed gf's to mokee but I've seen ones where people have flashed the gf's after flashing the treble images well and they didn't have any problem so just make sure you read into that one. obviously if the GS I can change the gf's then don't flash any before flashing or after as it will be flashed when we install it to the image and everything will be.
Which brings us to the last part if you did everything right up to this point then you should have no trouble installing the GSI through either TWRP or fastboot but before you do just make sure you go back to White and you just swipe to factory reset again so that we know that we cleaned out the data and we're on something clean after on encrypting the data if you did Flash no variety but remember don't wipe any partitions you want to make sure that you leave mokee on there. if you do it correctly you won't even need to wipe anything afterwards you should literally just need to be able to install the image into the system partition now and then reboot and it should work fine
It's your choice on how to go about doing it I've had success with TWRP but I've had more success using the fastboot method if for some reason you do try TWRP and it flashes and says success in 10 seconds then just reboot to fastboot mode in just flash it from there because you probably going to run into an issue just factory reset it again before you do it by swiping you don't have to wipe any of the partitions leave those alone.
So either go to the fastboot route which is put the phone in fastboot Point your terminal to the area where your GSI is located on your computer and then type fastboot flash system xxxGSI NAMEXXX.IMG.... OBVIOUSLY REPLACE THE FIRST PART WITH THE ACTUAL NAME OF YOURS. Next press enter and give it a few seconds and then you should see it's a success at which time you can reboot the phone and it should boot after a few short minutes.
If you wanted to use the twrp I believe I saw something about how you have to be on version 3.2.2 or above most likely for blue spark version as I use that one because it has treble support and I can see the vendor image even though I don't touch it. So if you flash it here you want to make sure instead of rebooting to fastboot like before you would just go to install and select image then find the image on your phone select it and then select the system images where you are installing it and then wipe the bar at the bottom for Flash and then upon it finishing you should hit reboot and let the phone boot up the first time set it up and then you can go back and you can go back to TWRP if you want to flash magisk or any other modules or TWRP Zips I've stated first then make sure you move the phone and go back and do all the modifying after otherwise you're getting stuck. I hope this helps feel free to contact me if you have any trouble.
theandroidas said:
Hi all,
so today I found a treble-enabled ROM of Android Pie and wanted to flash it. Thing is, I need to enable treble for me first. The treble check says that Treble is indeed supported, and so does the OnePlus website, but I don't have access to the vendor partition in TWRP. Using TWRP 3.2.3-1, by the way.
So, I read that MoKee enables Treble. Tried that, flashed the rom, flashed the radio and then the rom, factory wiped, flashed rom, factory wiped, flashed radio and rom, nothing. Still can't get Treble support. Then I tried kylothow's Trebliser, but nothing there either. I am realy at a loss here - I even reinstalled OOS (newest beta of course) and I couldn't get the vendor partition to show up, which is weird considering installing said trebliser actually states "Vendor partition found, good!" when installing, and then proceeds to in fact patch the vendor partition. It just doesn"t do anything, I can't install GSIs, can't even get the treble check to register that I do in fact have treble.
So this is where I turn to you guys. Do you have any idea what I could do in this situation? Please answer genuinely and don't post "just wait for an official android p".
Thanks!
Click to expand...
Click to collapse
Bro can u plz tell me how to get back to 8.1 oreo i am on 9.0 and didn't get treble support
Just curious if anybody has some insight here...
I have a XT1710-09 which I have unlocked the bootloader and went to Lineage, only to find that the moto mods I use aren't working. So I've reverted back to the stock ROM. Everything works, but if I try and flash any version of Magisk (17.3 through 19), my phone will boot loop. I have tried the below items, but they all result in a boot loop:
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I can recover from the bootloop by reflashing the boot.img, but I obviously don't have any modification support. I've also noticed the boot.img seems to overwrite my TWRP install on the first boot when applying the encryption.
My phone is currently being flashed with ALBUS_OPS27.76-12-25. Does anybody have any guidance on getting this working? Sadly, I want to get the AAC codecs installed, otherwise my bluetooth system keeps falling back to sbc. Worked great in Lineage, but I have too many moto mods that wouldn't work (including the JBL and Hasselblad).
Thanks!
Are you sure you executed the two commands for keeping force encrypt and keep dm-verity before flashing on TWRP terminal? Because the only reason Magisk ever gives me bootloop on stock is because it automatically sets keep force encrypt, but not the other one.
And of course use v19
Will someone please help me before i go crazy. I done rooted several phones but i ran into this problem with the G7play. The bootloader is unlocked but Magisk wont install an everytime I modify the system partition (A or B) in TWRP recovery but I boot into Android and nothing changed… I go back to TW RP and it's still showing the files I put are all there but then when I boot back into Android nothing I do affects the actual system partition… why the hell can i modify it in TWRP an it has no effect when booted? is there a 3rd system partition or something's i don't know about??? where is it storing this original copy? someone please help me its drivin me crazy.
I'm having the same problem. I just created a new thread myself on this very issue. It seems some security has been implemented with the most recent stock OTA updates cause on older versions of the stock room, Magisk would flash fine and remain there once the phone started again.
DenhamsOwnSmoky said:
Will someone please help me before i go crazy. I done rooted several phones but i ran into this problem with the G7play. The bootloader is unlocked but Magisk wont install an everytime I modify the system partition (A or B) in TWRP recovery but I boot into Android and nothing changed… I go back to TW RP and it's still showing the files I put are all there but then when I boot back into Android nothing I do affects the actual system partition… why the hell can i modify it in TWRP an it has no effect when booted? is there a 3rd system partition or something's i don't know about??? where is it storing this original copy? someone please help me its drivin me crazy.
Click to expand...
Click to collapse
theburrus1 said:
I'm having the same problem. I just created a new thread myself on this very issue. It seems some security has been implemented with the most recent stock OTA updates cause on older versions of the stock room, Magisk would flash fine and remain there once the phone started again.
Click to expand...
Click to collapse
That is a pain the ass known as FEC hard at work. The only way around it is system root (which magisk doesn't use) or a custom kernel. Twrp is actually using a magisk binary to do root work. Magisk uses mirrors which don't actually change any files. They only simulate changes. So everything you do in twrp will never actually change anything until you root with magisk. If you make changes then root later, they'll show up when you boot the system.
I investigated it a couple months ago. If you want to see the technical side of it, read my posts that start on this page.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/page90
FEC is like ECC RAM, but for system files instead.
Spaceminer said:
That is a pain the ass known as FEC hard at work. The only way around it is system root (which magisk doesn't use) or a custom kernel. Twrp is actually using a magisk binary to do root work. Magisk uses mirrors which don't actually change any files. They only simulate changes. So everything you do in twrp will never actually change anything until you root with magisk. If you make changes then root later, they'll show up when you boot the system.
I investigated it a couple months ago. If you want to see the technical side of it, read my posts that start on this page.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/page90
FEC is like ECC RAM, but for system files instead.
Click to expand...
Click to collapse
Thanks that makes sense now...I managed to get it where I could modify it by installing AOSP. That's why I don't like Magisk confuses the hell outta me. Only reason I was installing it is cuz SuperSU dont usually work on newer systems no more but I have a trick with Magisk I did on my G6...This might be helpful to anyone who wants a system root with Magisk. Backup your boot an dtbo an system partition. Then install magisk. Then you go in an find all the lil files that magisk added that aren't really there (system-less) an create tarfiles of them. /sbin /data/adb /init /init.rc an there mite be more I don't remember fer sure. After you make the tarfiles you reflash the original magisk-free images you backed up earlier an go into TWRP (assuming youre usin the TWRP version that lets you make permanent changes to the system partition) an extract all the tarfiles into the same locations an then you install the magisk apk an if you did it right it'll act like magisk is installed an it manages root fer you an everything but it dont have all that system-less problems you get with regular magisk.
So it's been awhile since I've had a phone I cared to get into installing root and custom stuff but I just bought a 7t and am trying to get it all working. I have the bootloader unlocked and the latest version of TWRP flashed but every time I'm in TWRP it shows up as 0mb and can't mount the storage. I tried "fastboot format userdata" in adb and it worked for one boot cycle but once I rebooted TWRP after that I was back to the 0mb and can't mount storage (I also still cannot format storage from TWRP before anyone tells me to try that) so what gives? What am missing?
You're missing the search functionality of the forum.
TWRP does not currently support reading data partition when encrypted by OOS. It does work, however, for custom ROMs, as long as you don't use a PIN, but a pattern. It also does not support formatting data partition, regardless of the ROM you're using.
morphvale said:
You're missing the search functionality of the forum.
TWRP does not currently support reading data partition when encrypted by OOS. It does work, however, for custom ROMs, as long as you don't use a PIN, but a pattern. It also does not support formatting data partition, regardless of the ROM you're using.
Click to expand...
Click to collapse
Well that's disappointing. So it sounds like there's really not too much point to it then. So I'm assuming there's a guide on how to install root and magisk via fastboot commands?
Again, you're missing the search functionality.
You can see it on the home page of the 7T, under ONEPLUS 7T GUIDES, NEWS, & DISCUSSION, third topic right now..
morphvale said:
Again, you're missing the search functionality.
You can see it on the home page of the 7T, under ONEPLUS 7T GUIDES, NEWS, & DISCUSSION, third topic right now..
Click to expand...
Click to collapse
Still leaving trouble using the search function to find what I want but I'll figure it out. So is it worth installing a custom rom on this phone or should I just try and root the phone on the stock OS? I'm very new to this phone and everything that goes along with it.
Justin541 said:
Still leaving trouble using the search function to find what I want but I'll figure it out. So is it worth installing a custom rom on this phone or should I just try and root the phone on the stock OS? I'm very new to this phone and everything that goes along with it.
Click to expand...
Click to collapse
@Justin541 - If you need any help just PM me. Ill get you going.. As long as your bootloader is unlocked, the rooting process is easy. All you have to do is:
- Install magisk manager (here)
- Download a patched boot.img from here(try to find the boot.img that matches the build your on, all though it probably doesnt matter)
- Boot into bootloader (adb reboot bootloader) and BOOT(dont flash) the patched boot.img (fastboot boot patched_boot.img)
- When phone is booted, open up magisk manager and do a direct install. Booting the patched boot.img is what you gives you a temporary root to be able to install magisk.
Is there anyone who can provide information on how to 9 pro boot/shutdown-animation and or the bootloader unlocked warning splash screen?
Bout animation is in system or product media. Don't know about shutdown. No solutions here for unlocked bootloader as I have been told it is part of the bootloader
jwidel said:
Is there anyone who can provide information on how to 9 pro boot/shutdown-animation and or the bootloader unlocked warning splash screen?
Click to expand...
Click to collapse
You can refer to the link below, there are easy steps to change the boot animation.
How to Change Boot Animation on OnePlus [Android 12/13]
In this comprehensive tutorial, we will show you the detailed steps to change the boot animation on your OnePlus device.
www.droidwin.com
insert in product / media does not work, read-only. Authorization cannot be changed either. What now?
MikeBl1 said:
insert in product / media does not work, read-only. Authorization cannot be changed either. What now?
Click to expand...
Click to collapse
My understanding is that it can only be done with a magisk module since you cannot mount system partitions RW in A11/OOS11.
does this module exist? Can't find anything about it
MikeBl1 said:
does this module exist? Can't find anything about it
Click to expand...
Click to collapse
Sorry for the delay, I didn't get a notification for this since it wasn't a reply or quote.
A module would have to be manually built using a specific boot animation. It would have to overwrite the system file during boot, then most likely trigger a restart of the system UI (because by the time magisk overwrites the file, it has already read the original bootanimation.zip). It's not a very clean solution, but it may be the only way now that system partitions are read-only. There are a few more details in this thread, but I'm not aware of any sort of universal module that does this.
Another thought: I wonder if it's still possible to mount system partitions read/write from within TWRP when the system isn't booted? I'm guessing not, but it may be worth trying if you're still on OOS11. I can't test since I'm on OB1 now.
terlynn4 said:
My understanding is that it can only be done with a magisk module since you cannot mount system partitions RW in A11/OOS11.
Click to expand...
Click to collapse
+1
terlynn4 said:
Sorry for the delay, I didn't get a notification for this since it wasn't a reply or quote.
A module would have to be manually built using a specific boot animation. It would have to overwrite the system file during boot, then most likely trigger a restart of the system UI (because by the time magisk overwrites the file, it has already read the original bootanimation.zip). It's not a very clean solution, but it may be the only way now that system partitions are read-only. There are a few more details in this thread, but I'm not aware of any sort of universal module that does this.
Another thought: I wonder if it's still possible to mount system partitions read/write from within TWRP when the system isn't booted? I'm guessing not, but it may be worth trying if you're still on OOS11. I can't test since I'm on OB1 now.
Click to expand...
Click to collapse
Why are you still on OB1? Update to OB2! Night and day compared to OB1. Lol
I made one long time ago with Cyberpunk boot animation along with plenty of others stuffs/modspack.
If anyone interested I can prepare the cyberpunk boot animation module ?
terlynn4 said:
Sorry for the delay, I didn't get a notification for this since it wasn't a reply or quote.
A module would have to be manually built using a specific boot animation. It would have to overwrite the system file during boot, then most likely trigger a restart of the system UI (because by the time magisk overwrites the file, it has already read the original bootanimation.zip). It's not a very clean solution, but it may be the only way now that system partitions are read-only. There are a few more details in this thread, but I'm not aware of any sort of universal module that does this.
Another thought: I wonder if it's still possible to mount system partitions read/write from within TWRP when the system isn't booted? I'm guessing not, but it may be worth trying if you're still on OOS11. I can't test since I'm on OB1 now.
Click to expand...
Click to collapse
no longer works on op9pro (oos11), has to wait for module
Is there a way to unpack and repack splash.img ? Anyone found a way? I need to change the splash screen images and bootloader unlocked image.
TheKnux said:
Why are you still on OB1? Update to OB2! Night and day compared to OB1. Lol
Click to expand...
Click to collapse
That post is over 2 weeks old, so there was no OB2 then. The point remains I can't test anything on OOS11 since I'm on OOS12 and there's no TWRP for it yet.