Hi fellow developers. Can anybody please tell me does a universal build of TWRP or Orangefox exist and where can I find such a thing?
I'm looking for a universal build of any custom recovery that is able to run straight out of the box on as many devices as possible.
I need it for bundling with my recent project
Some folks have a TWRP with a very limited sh version that doesn't even understand basic arrays! That's why I'm looking to deploy a universal build of custom recovery together with my script to prevent any avoidable shell errors.
Thanks.
Of course that thing doesn't exist and never will. Recovery image needs device specific kernel.
Well I can try making one. But for sure, it wont work.
Royna said:
Of course that thing doesn't exist and never will. Recovery image needs device specific kernel.
Click to expand...
Click to collapse
"Recovery image needs device specific kernel."
are you sure about that
after all GKI exist
@Rush It does. FSTAB and stuff. If the recovery doesn't know the partition, how will it work? After flashing a GSI you are supposed to flash your own kernel. Though in most cases it is not required but it is advised and recommended. Likewise recoveries also need to know the FSTAB and stuff from the kernel level. So it is not possible.
Otus9051 said:
@Rush It does. FSTAB and stuff. If the recovery doesn't know the partition, how will it work? After flashing a GSI you are supposed to flash your own kernel. Though in most cases it is not required but it is advised and recommended. Likewise recoveries also need to know the FSTAB and stuff from the kernel level. So it is not possible.
Click to expand...
Click to collapse
hmmm, that makes sense yeah, I guess we need to have that be more generic before something like this can exist then
You can probably make it if you use have GKI, and it could be also possible if you have something like a custom build of lk2nd to boot the recovery using the kernel from the boot image.
As for fstab, we might be able to add a script to try mounting all the common partitions.
TipzTeam said:
You can probably make it if you use have GKI, and it could be also possible if you have something like a custom build of lk2nd to boot the recovery using the kernel from the boot image.
As for fstab, we might be able to add a script to try mounting all the common partitions.
Click to expand...
Click to collapse
Would be painful, but will work yes, and will have 40% it wont boot.
Otus9051 said:
Would be painful, but will work yes, and will have 40% it wont boot.
Click to expand...
Click to collapse
The fstabp part is pretty easy, but the kernel part isn't.
The lk2nd uses a generic kernel though.
TipzTeam said:
The fstabp part is pretty easy, but the kernel part isn't.
The lk2nd uses a generic kernel though.
Click to expand...
Click to collapse
Then we would need to port lk2nd to all devices, or make a GSI of it lol.
Otus9051 said:
Then we would need to port lk2nd to all devices, or make a GSI of it lol.
Click to expand...
Click to collapse
It's just gonna be an infinite loop. I will try to work on it later.
TipzTeam said:
I will try to work on it later.
Click to expand...
Click to collapse
oh.no.
You're right. I'm searching for GKI and not GSI. Thanks!
lebigmac said:
Does any random GSI firmware include a boot.img file that can be booted by any device out there running Marshmallow or newer?
Click to expand...
Click to collapse
...why would any GSI (S as in System) include boot?
If you ask me, the premise of this thread is wrong to begin with.
Thread closed on request of OP @lebigmac
2022-07-07 Update: Thread re-opened on request of OP.
Thanks Oswald for re-opening this thread. I renamed it to better describe my request. There was actually a very interesting conversation going on above. Hopefully those gentlemen can continue where they left off.
Cheers
@AndyYan @Otus9051 @tipzrickycheung @Rush @Royna
Related
I have experimented with different ROMs and two versions of TWRP, and have installed the fff bootloader. (I have two working cracked-glass KF's that I picked up cheap in addition to a like-new one, so I can try different ROMs, etc., at the same time.)
I had presumed until recently that the kernel was a part of the ROM that was locked in by the ROM developer. It appears, though, judging by the two lengthy threads about a kernel 3.0, that users can install different combinations of kernel and ROM.
Can somebody explain, or point to an explanation of, the relationship between a kernel and a ROM and how one installs a desired combination of the two? Can one install a new kernel over an existing ROM, install the kernel and then a ROM, or is it necessary to do something else, such as editing a .zip file before installing it?
I realize that if I were to read a few hundred messages in a few threads, I might come up with the answers myself, but I might also transition from being a still-coherent old guy to one with senile dementia before I got to that point. Aside from my personal needs, though, it seems that an explanation of this matter deserves to be someplace where it can be easily found.
The kernel is the main component of the operating system (ROM). The kernel is essentially the middle man between the applications and the processing being executed at a hardware level. Basically the kernel is the communicator between software and hardware.
With that said, ROM developers will use a specific kernel with their ROM. You are not locked in to use the kernel which came with "x" ROM. A new kernel can be installed. You want to make certain if you are using an ICS ROM you parallel it with an ICS kernel. If you flash an incompatible kernel that could be a problem. Some kernels work better with some ROMS. Different combinations produce different bugs. It's just a matter of tinkering until you find the combination which suits you best. Hash's latest 3.0 kernel (http://forum.xda-developers.com/showthread.php?t=1591850) is popular and seems to be mostly stable with the ICS ROMS for the KF.
Installing a kernel is just like flashing a ROM although you don't need to wipe anything. Just boot in to recovery and select the kernel you've downloaded.
Should the custom kernel be installed after the ROM? It would seem that that would be necessary if the ROM itself comes with a kernel, as it apparently does.
Also:
? Are both the kernel and the rest of the ROM installed into the system partition, /dev/block/mmcblk0p9? If not there, then where?
? Does the kernel include the compiled code for all the standard linux commands, or only the system-level ones? Does it include the Dalvik interpreter?
aarons510 said:
Should the custom kernel be installed after the ROM? It would seem that that would be necessary if the ROM itself comes with a kernel, as it apparently does.
Also:
? Are both the kernel and the rest of the ROM installed into the system partition, /dev/block/mmcblk0p9? If not there, then where?
? Does the kernel include the compiled code for all the standard linux commands, or only the system-level ones? Does it include the Dalvik interpreter?
Click to expand...
Click to collapse
1. boot.img
2. Kernel come with system calls, or API, the commands you mentioned is binutils (most popular is GNU's). In Android you can install busybox to get these commands.
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
linktohack said:
1. boot.img
Click to expand...
Click to collapse
What part of my question is this an answer to? I'm guessing that it's meant to answer the questions in the third paragraph of my original post, but it's a bit cryptic, to say the least. I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.
2. Kernel come with system calls, or API, the commands you mentioned is binutils (most popular is GNU's). In Android you can install busybox to get these commands.
Click to expand...
Click to collapse
I just checked the version of ICS I have installed on one KF and the CM7 installation I have on another. On both of them, the system calls seem to be in /system/bin while the file manipulation and document processing commands are in /system/xbin. Most of the latter are, indeed, symlinks to busybox while many of the former are symlinks to toolbox.
So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
aarons510 said:
What part of my question is this an answer to?
Click to expand...
Click to collapse
I think he meant to tell you that the kernel is usually distributed as boot.img in the ROM zips.
aarons510 said:
I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.
Click to expand...
Click to collapse
The kernel is installed along with whatever ROM you install. Let's say you pick MadeUpRom and it features kernel #8 with it. You'd have to flash kernel #11 after installing said ROM.
aarons510 said:
So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
Click to expand...
Click to collapse
Kernels are installed to the boot partition, which is separate from the ROM's /system partition. Installing a new kernel will overwrite the existing one. For the dalvik, read this to understand it better: http://stackoverflow.com/questions/7541281/what-is-dalvik-and-dalvik-cache
aarons510 said:
What part of my question is this an answer to? I'm guessing that it's meant to answer the questions in the third paragraph of my original post, but it's a bit cryptic, to say the least. I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.
I just checked the version of ICS I have installed on one KF and the CM7 installation I have on another. On both of them, the system calls seem to be in /system/bin while the file manipulation and document processing commands are in /system/xbin. Most of the latter are, indeed, symlinks to busybox while many of the former are symlinks to toolbox.
So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
Click to expand...
Click to collapse
In Android world, a kernel is an image contains a Linux kernel and a ramdisk which is named *boot.img* and will be *write* (byte copy) to the boot partition.
A complete ROM is a singed zip file contains at least /system files and a kernel. When you flash a ROM, it will unpack and *copy* file of /system to the system partition (that's why we wipe the system partiton aka. factory reset before we flash a new ROM) then *write* boot.img to boot partition.
Usually, a kernel needs external modules, offen reside at /system/lib/modules, so developer create an *uncomplete* ROM, which contains only kernel and these external files. This flashable kernel looks like a ROM, but it's really small size compare to complete ROM.
Like I said above, files in /system/bin/ and /system/xbin/ is not related to kernel (boot.img). They are just binaries, compiled to use system calls that kernel (and modules) offer.
--- Dev only ---
System calls is not binaries, they are CPU interupt instructions. Your programs need to be compiled to call them.
In linux, system calls are called through interupt *0x80*
Original Thread by Philz3759:
http://forum.xda-developers.com/note-4/snapdragon-dev/trltexx-philz-touch-t2927930
Recovery Package [Goo]
http://goo.im/devs/playground/trltesku/
This is the CWM-based Philz Touch Recovery with a shiny new kernel, SELinux tweaks, and some other modifications that enable it to run on the N910T and N910W8 out of the box.
May also run on the Sprint and AT&T variants, but make sure to have a copy of a working recovery handy in case you need to restore.
Kernel: http://forum.xda-developers.com/note-4/unified-development/kernel-dealers-choice-t2915824
Device: https://github.com/StarKissed/android_device_samsung_trltetmo
[Recovery]Philz Touch Recovery - Ported to North America
The initial version uses a kernel for the N910W8 and SELinux policy settings from the N910T. If that combination works for me, I can almost guarantee it will work on either of those devices because those values would not match up.
re: Philz Custom Recovery
twistedumbrella said:
Original Thread by Philz3759: http://forum.xda-developers.com/note-4/snapdragon-dev/trltexx-philz-touch-t2927930
Download from Mega
https://mega.co.nz/#F!l1RBBbDI!KHcF184rkhshJhdF_tO7gw
Download from Goo
http://goo.im/devs/playground/trltetmo/recovery
This is the CWM-based Philz Touch Recovery with a shiny new kernel and some other minor tweak that enable it to run on the N910T and N910W8 out of the box.
May also run on the Sprint and AT&T variants, but make sure to have a copy of a working recovery handy in case you need to restore.
Click to expand...
Click to collapse
Thanks for sharing Philz Touch Recovery for our N910T, it's always good to
have a backup custom recovery just in case twrp ever stops working properly.
Misterjunky said:
Thanks for sharing Philz Touch Recovery for our N910T, it's always good to
have a backup custom recovery just in case twrp ever stops working properly.
Click to expand...
Click to collapse
Yeah, I used to just make my own but it's far easier to outsource the core and then replace it with the kernel I'm already working on.
Kernel control apps
twistedumbrella said:
Yeah, I used to just make my own but it's far easier to outsource the core and then replace it with the kernel I'm already working on.
Click to expand...
Click to collapse
Just out of curiosity, in your opinion what is the best app at the play store which
is fully compatible and easy to use with your StarKissed kernels that even noobs
can use without fear of messing anything up when changing the kernel settings?
Thanks!
Thanks.....will wait for corrected upload
louforgiveno said:
Thanks.....will wait for corrected upload
Click to expand...
Click to collapse
It should be uploaded in the next minute or two to Mega and shortly after for Goo
These links not working?
Hanoverfiste said:
These links not working?
Click to expand...
Click to collapse
They should be. I just tried them and they did
twistedumbrella said:
They should be. I just tried them and they did
Click to expand...
Click to collapse
I read back and saw where Tapatalk won't work properly, so I tried through Chrome and that's not working either.
Hanoverfiste said:
I read back and saw where Tapatalk won't work properly, so I tried through Chrome and that's not working either.
Click to expand...
Click to collapse
Mega was the issue on the device, so there is a Goo mirror below it. That should be working.
Or it would have been if I remembered I changed folders on Goo. Now it does.
twistedumbrella said:
Original Thread by Philz3759:
http://forum.xda-developers.com/note-4/snapdragon-dev/trltexx-philz-touch-t2927930
Download from Mega:
https://mega.co.nz/#F!l1RBBbDI!KHcF184rkhshJhdF_tO7gw
Download from Goo:
http://goo.im/devs/playground/trltesku/recovery
This is the CWM-based Philz Touch Recovery with a shiny new kernel, SELinux tweaks, and some other modifications that enable it to run on the N910T and N910W8 out of the box.
May also run on the Sprint and AT&T variants, but make sure to have a copy of a working recovery handy in case you need to restore.
Kernel: http://forum.xda-developers.com/note-4-tmobile/orig-development/kernel-dealers-choice-t2915824
Device: https://github.com/StarKissed/android_device_samsung_trltephil
Click to expand...
Click to collapse
Guys, I don`t know if I am doing something wrong.
I have been using Twrp 2.8.1.1, I used it to flash CWM.
I tried to back up using CWM but says error while making a backup image of /data!
please press any key to continue.
I need help please!
sunnyo_ola said:
Guys, I don`t know if I am doing something wrong.
I have been using Twrp 2.8.1.1, I used it to flash CWM.
I tried to back up using CWM but says error while making a backup image of /data!
please press any key to continue.
I need help please!
Click to expand...
Click to collapse
The partition scheme may be off. I assumed there were identical from Europe to NA but I'll verify that tonight
twistedumbrella said:
The partition scheme may be off. I assumed there were identical from Europe to NA but I'll verify that tonight
Click to expand...
Click to collapse
Thank you, I am using US T-Mobile note 4!
Yeah... The partition scheme is off. I'm on T-Mobile and it won't work. Thanks for your efforts and I can't wait to try again.
[Recovery]Philz Touch Recovery[North American Variants]
Edit: nevermind. The issue is obviously deeper than the fstab or SELinux
Thanks for your hard work. I'm happy to test if you need anything.
After a lot of building, rebuilding, reconfiguring, etc some new builds are finally up.
The current version only supports identifying itself as a T-Mobile device until fully tested.
Rather than modifying the existing European version for the US, this now fully source-built.
twistedumbrella said:
After a lot of building, rebuilding, reconfiguring, etc some new builds are finally up.
The current version only supports identifying itself as a T-Mobile device until fully tested.
Rather than modifying the existing European version for the US, this now fully source-built.
Click to expand...
Click to collapse
Thank you I am going to try it right now,
I will you a feedback.
thank you again for the great work always!
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/
Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Azlun said:
I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/
Click to expand...
Click to collapse
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/
cam30era said:
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/
Click to expand...
Click to collapse
" Dees_Troy to allow TWRP to decrypt the data partition involves modifying the same init binary " is NOT what I want according developer's
https://plus.google.com/+DeesTroy Pixel update 4 picture.
What I want is need the full device decryption permanently, on Anroid running time, not only on TWRP.
so, I think that is maybe more than TWRP can do, I guess a special boot.img or a kernel patch zip is need to reach what I need.
Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387
blueyes said:
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387
Click to expand...
Click to collapse
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.
Mike02z said:
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.
Click to expand...
Click to collapse
Don't you need to format user data with fast boot to decrypt?
Sent from my Google Pixel XL using XDA Labs
Hi,
Trying to dualboot OOS and stock. Anyone got this working on oreo only?
matteosaeed said:
Hi,
Trying to dualboot OOS and stock. Anyone got this working on oreo only?
Click to expand...
Click to collapse
There is not a solution that is confirmed to work on the op5t, multirom was released for the op5 but needs to be ported over to 5t. feel free to work on the port!
Misanful said:
There is not a solution that is confirmed to work on the op5t, multirom was released for the op5 but needs to be ported over to 5t. feel free to work on the port!
Click to expand...
Click to collapse
I came across this and was asking. Seems like it has a few downloads wasn't sure if someone had used it.
https://androidfilehost.com/?fid=745849072291693835
matteosaeed said:
I came across this and was asking. Seems like it has a few downloads wasn't sure if someone had used it.
https://androidfilehost.com/?fid=745849072291693835
Click to expand...
Click to collapse
Hmmm. If you test it please report back here how it worked for you!
matteosaeed said:
I came across this and was asking. Seems like it has a few downloads wasn't sure if someone had used it.
https://androidfilehost.com/?fid=745849072291693835
Click to expand...
Click to collapse
I tried it last night. It works, I was able to dual boot. You must download the custom TWRP by the same guy for the 5t. The custom twrp is outdated so it won't read my ntfs formatted portable hard drive. You must also be decrypted.
cubandanger05 said:
I tried it last night. It works, I was able to dual boot. You must download the custom TWRP by the same guy for the 5t. The custom twrp is outdated so it won't read my ntfs formatted portable hard drive. You must also be decrypted.
Click to expand...
Click to collapse
Hey, thanks for trying this. Did you flash any roms?
matteosaeed said:
Hey, thanks for trying this. Did you flash any roms?
Click to expand...
Click to collapse
Yes. I flashed Omni as secondary, although I had to remove the assert lines in the updater script. Then it failed to install magisk on secondary, so to make it work I had to swap primary and with secondary, Flash what I needed to Omni as primary, then swap it again. Pain sticking but worked.
I wonder how hard would it be to update the custom twrp with the most recent changes in regular twrp.
Sounds interesting, what was your other room?
Any chance you tried to restore a nandroid backup as second rom?
pargas said:
Sounds interesting, what was your other room?
Any chance you tried to restore a nandroid backup as second rom?
Click to expand...
Click to collapse
I was using codename Phoenix as primary. I didn't try backing up or restoring using the customer twrp
Anybody that knows anybody that would be able to use the twrp and multirom source and update the recovery with most recent changes?
Hi guys,
I know custom ROMs are made of AOSP. However, it's not very clear to me why do they also have lower quality signal compared to stock ROMs. In the same area where I usually got 4G (not great signal, but still 4G), now I only get 3G.
Is there a reason for this? Aside from "it's not made by the manufacturer". Yeah, I know that, but why exactly isn't the same quality...? What makes it slightly worse?
Also, is there anything can do to improve reception?
arsradu said:
Hi guys,
I know custom ROMs are made of AOSP. However, it's not very clear to me why do they also have lower quality signal compared to stock ROMs. In the same area where I usually got 4G (not great signal, but still 4G), now I only get 3G.
Is there a reason for this? Aside from "it's not made by the manufacturer". Yeah, I know that, but why exactly isn't the same quality...? What makes it slightly worse?
Also, is there anything can do to improve reception?
Click to expand...
Click to collapse
Exactly what you said: "It's not made by the manufacturer". Proprietary blobs are extracted from the device, creating vendor image while building AOSP and modifying vendor partition it when installing a zip.
I don't think there's anything to improve, until someone makes a kernel or a vendor image.
(flashing original vendor lead to bootloop on my phone, probably because encryption?)
However, you can try downloading stock ROM and flash stock vendor, but make sure to not have your device encrypted (I did not try on a non-encrypted device).
georg3_ said:
Exactly what you said: "It's not made by the manufacturer". Proprietary blobs are extracted from the device, creating vendor image while building AOSP and modifying vendor partition it when installing a zip.
I don't think there's anything to improve, until someone makes a kernel or a vendor image.
(flashing original vendor lead to bootloop on my phone, probably because encryption?)
However, you can try downloading stock ROM and flash stock vendor, but make sure to not have your device encrypted (I did not try on a non-encrypted device).
Click to expand...
Click to collapse
I've noticed this with stock ROMs as well, when they weren't dedicated for that specific region... So...I'm guessing it's probably the same here. AOSP includes some files to make the ROM work...but not dedicated files for each region.
By the way, can you please, guide me how should I do this? It's been a really long time since I've done stuff like this. Android has changed a lot.
I already have the ROM at hand, downloaded via RSA. But it's Android 11, since that's the last ROM that Motorola released for this phone.
So that part is done. What next? )
Also, any idea if this method should also bring back VoLTE and VoWIFI? Or it's not that simple?
arsradu said:
I've noticed this with stock ROMs as well, when they weren't dedicated for that specific region... So...I'm guessing it's probably the same here. AOSP includes some files to make the ROM work...but not dedicated files for each region.
By the way, can you please, guide me how should I do this? It's been a really long time since I've done stuff like this. Android has changed a lot.
I already have the ROM at hand, downloaded via RSA. But it's Android 11, since that's the last ROM that Motorola released for this phone.
So that part is done. What next? )
Also, any idea if this method should also bring back VoLTE and VoWIFI? Or it's not that simple?
Click to expand...
Click to collapse
EDIT: Newer OS than vendor shouldn't make a problem.
Newer vendor than OS does.
Extract the ROM, there should be vendor.img in there, and there are 2 methods for this:
1. TWRP method
Install, Install Image, select your vendor image set it to flash as vendor image, and swipe to flash.
2.Fastboot method
Open a terminal/command prompt in the extracted ROM folder, and type
Code:
fastboot flash vendor vendor.img
That should do it.
georg3_ said:
Older OS than vendor shouldn't make a problem.
Older vendor than OS does.
Extract the ROM, there should be vendor.img in there, and there are 2 methods for this:
1. TWRP method
Install, Install Image, select your vendor image set it to flash as vendor image, and swipe to flash.
2.Fastboot method
Open a terminal/command prompt in the extracted ROM folder, and type
Code:
fastboot flash vendor vendor.img
That should do it.
Click to expand...
Click to collapse
Alright. So....I can't use Android 11 vendor, extracted from stock ROM, if I'm currently on PixelExperience based on Android 12, right?
arsradu said:
Alright. So....I can't use Android 11 vendor, extracted from stock ROM, if I'm currently on PixelExperience based on Android 12, right?
Click to expand...
Click to collapse
Stau bine pe engleza daca e )
I translated it wrong, i meant it would be fine to flash it
Buun. Thank you, kind sir. Will try it then and let you know.
georg3_ said:
Stau bine pe engleza daca e )
I translated it wrong, i meant it would be fine to flash it
Click to expand...
Click to collapse
I'm getting bootloop, too...
I tried to flash the rom, flash Disable_Dm-Verity_ForceEncrypt.zip (should disable encryption...unless I'm missing something). But after flashing vendor.img from stock Android 11, I can't boot anymore. I also tried wiping data after that, but no luck.
arsradu said:
I'm getting bootloop, too...
I tried to flash the rom, flash Disable_Dm-Verity_ForceEncrypt.zip (should disable encryption...unless I'm missing something). But after flashing vendor.img from stock Android 11, I can't boot anymore. I also tried wiping data after that, but no luck.
Click to expand...
Click to collapse
Probably not an encryption related issue, guess we can't fix anything.