Related
Feel free to discuss non-development-related topics here or ask any questions.
Creating an almost functional build of CM11 for the Buzz would be really tough isn't it?? I say this mainly because it does not have a GPU
Probably... I doubt it will ever be as "usable" as Kitkat on the HTC Wildfire S or Salsa....
What you need to fix gprs?
maloy4800 said:
What you need to fix gprs?
Click to expand...
Click to collapse
Well I am guessing that he most likely would need a logcat to start with. You can get this by connecting your wfs to you PC and runing:
adb logcat > logcat.txt
Or you can install CatLog and app from the play store to get the logcat.
WiFi Tethering
Any WiFi tethering apps recommendation? I've tried OpenGarden and FoxFi (rooted). Pls give me some advice. Thx.
ivanto0115 said:
Any WiFi tethering apps recommendation? I've tried OpenGarden and FoxFi (rooted). Pls give me some advice. Thx.
Click to expand...
Click to collapse
https://code.google.com/p/android-w...etail?name=wireless_tether_2_0_7.apk&can=2&q=
Don't know if this is the right place but here it goes, so I installed CM 11 flashed rom reboted and then reboted in recovery flashed gapps working so far, but I have no lockscreen no play store and its very laggy works very slow.. have to press the back button like 5 times so it goes back, is there anyway to fix this?
That being said, great work Olivier and thanks for all your great roms !
Abyt said:
Don't know if this is the right place but here it goes, so I installed CM 11 flashed rom reboted and then reboted in recovery flashed gapps working so far, but I have no lockscreen no play store and its very laggy works very slow.. have to press the back button like 5 times so it goes back, is there anyway to fix this?
That being said, great work Olivier and thanks for all your great roms !
Click to expand...
Click to collapse
Have you tried turning it off and on again?
Just did that and now, I have the welcome menu problem. Maybe its because of int2ext4+ ?
I will just try to wipe everything and reflash it maybe it will fix the problem.
Olivier said:
Have you tried turning it off and on again?
Click to expand...
Click to collapse
Isn't that the solution to everything?
Abyt said:
Just did that and now, I have the welcome menu problem. Maybe its because of int2ext4+ ?
I will just try to wipe everything and reflash it maybe it will fix the problem.
Click to expand...
Click to collapse
Are you flashing the right GApps?
I am flashing the recommended gapps from the CM11 topic.
You said ROM had a bug about screen recording and now it's fixed
Any recommended screen recorder
AmirNajjar said:
You said ROM had a bug about screen recording and now it's fixed
Any recommended screen recorder
Click to expand...
Click to collapse
]https://play.google.com/store/apps/details?id=com.nll.screenrecorder
Don't know if it works. But this has a nice UI and good performance.
Would just like to point out that the "Initial SetupWizard Bug" only appears to be on Kitkat roms based on CM11(currently only 2)............. I'm able to go through the setup process on both Omni and Aospa
csoulr666 said:
Would just like to point out that the "Initial SetupWizard Bug" only appears to be on Kitkat roms based on CM11(currently only 2)............. I'm able to go through the setup process on both Omni and Aospa
Click to expand...
Click to collapse
I believe the problem is with CMSetup. I am looking into it now.
That's unfortunately another issue with the proprietary GAPPs on our old devices we can't do much about.
EDIT: Strange it works in other ROMs lol.
Gesendet von meinem Xperia S mit Tapatalk
Hi,
I've just installed the latest CM11 Version on my WFS. Everything works properly, but now i'm facing old problems: the internal storage is too little.
It's the first time i rooted a phone and I haven't yet installed Data2SD on it before, but I'd like to install Data2SD. So far I've tried to install Data2InstallerNXE2 and OnDemandSingleCoreZip. But none of these two worked. I got a "Failure" notification.
I tried it the following way:
-1st: partitionated the SD-Card with Minitool Partition Wizard: 8GB; now: EXT2: 1,5GB.
-then wiped everything
-installed CM 11
-booted
-tried to install Data2SD -> "Failure"
-because it didn't work I already installed the GAPPS.
As I said, the system works fine..but I've only some MB's left of storage... Did I do something wrong or were the versions I tried not the correct ones? Is there a possibility to increase the internal storage of the WFS? Which is it and how does it work?
Thanks for any help!
Quetzalcoatl2086 said:
Hi,
I've just installed the latest CM11 Version on my WFS. Everything works properly, but now i'm facing old problems: the internal storage is too little.
It's the first time i rooted a phone and I haven't yet installed Data2SD on it before, but I'd like to install Data2SD. So far I've tried to install Data2InstallerNXE2 and OnDemandSingleCoreZip. But none of these two worked. I got a "Failure" notification.
I tried it the following way:
-1st: partitionated the SD-Card with Minitool Partition Wizard: 8GB; now: EXT2: 1,5GB.
-then wiped everything
-installed CM 11
-booted
-tried to install Data2SD -> "Failure"
-because it didn't work I already installed the GAPPS.
As I said, the system works fine..but I've only some MB's left of storage... Did I do something wrong or were the versions I tried not the correct ones? Is there a possibility to increase the internal storage of the WFS? Which is it and how does it work?
Thanks for any help!
Click to expand...
Click to collapse
Well if you just want to link apps to 2nd partition of sdcard, you can try link2sd . Unlike the other scripts, it always work for me.
GeeteshK said:
]https://play.google.com/store/apps/details?id=com.nll.screenrecorder
Don't know if it works. But this has a nice UI and good performance.
Click to expand...
Click to collapse
Didn't work
Hi, sorry for my English
A month earlier, I used cm13 without problems . After the update (I did not know, about fresh install) by the OTA to CM14.1 I have a problem with the mac address. Return to stock version helps, but re-installing CyanogenMod no matter what 12,13,14.1, any custom rom changed my mac address to 02:00:00:00:00. How I turn off the wifi and I reboot phone, my mac is 02:00:00:00:00, but after turn on WiFi changed to 00:00:00:00:00. I tried reflash TWRP, change aboot.bin, nothing works.I installed the update, I had bootloop, tried reinstalling the CM and I make wipe internal partition. Maybe that's the problem? I'm trying to solve this problem 3 weeks help please!
If you can please give me links to bootloader 100%working, and twrp.
I use from http://forum.xda-developers.com/lg-g3/general/lg-g3s-beat-d722-thread-t3110048 for KitKat (now I use KK version), and something's wrong :-/
I have this roms on my computer: 20a,20b,20d,10b,10d form all I try install cyanogenmod without success :crying:
Now use 10d, rooted, aboot from this post from xda, twrp 3.0.2, I tested all TWRP not helped :silly:
Thank you for your time !
killerro_lab said:
Hi, sorry for my English
A month earlier, I used cm13 without problems . After the update (I did not know, about fresh install) by the OTA to CM14.1 I have a problem with the mac address. Return to stock version helps, but re-installing CyanogenMod no matter what 12,13,14.1, any custom rom changed my mac address to 02:00:00:00:00. How I turn off the wifi and I reboot phone, my mac is 02:00:00:00:00, but after turn on WiFi changed to 00:00:00:00:00. I tried reflash TWRP, change aboot.bin, nothing works.I installed the update, I had bootloop, tried reinstalling the CM and I make wipe internal partition. Maybe that's the problem? I'm trying to solve this problem 3 weeks help please!
If you can please give me links to bootloader 100%working, and twrp.
I use from http://forum.xda-developers.com/lg-g3/general/lg-g3s-beat-d722-thread-t3110048 for KitKat (now I use KK version), and something's wrong :-/
I have this roms on my computer: 20a,20b,20d,10b,10d form all I try install cyanogenmod without success :crying:
Now use 10d, rooted, aboot from this post from xda, twrp 3.0.2, I tested all TWRP not helped :silly:
Thank you for your time !
Click to expand...
Click to collapse
Today i try install 20a, one more time unlock bootloader install kernel and install cm13 from above post. I not try this
not working :/
info: i install stock rom from LG flash tool CSE option
up, still nothing :/ no fix ? ;(
i have the same problem. doesnt matter the version, cm get null mac after ota update to cm14 now i'm using stock rom to d724 kitkat
up, no fix ?
sorry man, i'm so sad about this, i've tryied everything, but nothing work, not even ressurection remix and others. I'm using the stock rom, it is too slow, but work well, i'm giving up from cm, no one know how to solve this problem, i regret have updated cm13 to cm14
killerro_lab said:
up, no fix ?
Click to expand...
Click to collapse
dude i get it to work. Install macchanger by osama abukmail, worked for me on cm13 and 14, set to change mac every boot , now i'm using cm again, i'm so happy about it
https://apkpure.com/br/wifi-mac-changer/com.wireless.macchanger
now working lol I try this app before but not working... now working and I have mac adress to connect wifi ! thx bro!
killerro_lab said:
up, no fix ?
Click to expand...
Click to collapse
killerro_lab said:
now working lol I try this app before but not working... now working and I have mac adress to connect wifi ! thx bro!
Click to expand...
Click to collapse
unfortunately hotspot won't work with this tool, i hope a fix for the next update
icarooo said:
unfortunately hotspot won't work with this tool, i hope a fix for the next update
Click to expand...
Click to collapse
cyanogenmod is end ... so I install lineageosrom, this is the same as cyanogenmod ... mac changer working on this rom... one more time thx for the info :good:
Hi,
Until yesterday i had LineageOS and everything worked fine.
I installed ViperOS and everything ok too, but without root. But then i made a new installation with superSU this time, and I dont know why NFC turns on and off constantly, even the menu settings that normally shows NFC is gone, I can see NFC state just in quick settings.
I dont think that is ViperOS rom problem, because nobody reported that issue.
I made the wipes cache, davilk, data and system few times, and problem continues. Plus, there are more things that continue from previous installations, and I dont know why because i made clean installations. For ex. it asks for patron before start android always after making clean installations...
Because of that, i think that for everything back to normal state, maybe there is a way to make wipes deeply that i dont know... also for NFC come to normal work, is that so?
Please, give me any help... Thanks
I solved it doing this:
I have installed rom stock by twrp, next one:
https://forum.xda-developers.com/mot...l-sim-t3620551
Then i installed ViperOS. NFC is working ok again.
Regards
xuncall said:
I solved it doing this:
I have installed rom stock by twrp, next one:
https://forum.xda-developers.com/mot...l-sim-t3620551
Then i installed ViperOS. NFC is working ok again.
Regards
Click to expand...
Click to collapse
Glad to hear you solved your issue, but your question should have been in the Viper OS thread.
Jimi Mack said:
Glad to hear you solved your issue, but your question should have been in the Viper OS thread.
Click to expand...
Click to collapse
Thanks, but i dont agree. As i said, ViperOS was not the main aspect of my problem, it was a problem with the phone.
What are your thoughts? does it boot for you too? I work on a lot of stuff for various devices in the background and behind the scenes..
Just curious if other people are having success with some of my projects as well.
Unofficial pie RR
Edit: link removed
AnierinB said:
What are your thoughts? does it boot for you too? I work on a lot of stuff for various devices in the background and behind the scenes..
Just curious if other people are having success with some of my projects as well.
Unofficial pie RR
https://androidfilehost.com/?fid=11410963190603910079
No gapps included
Click to expand...
Click to collapse
Hey brother,
just seen your RR-Rom on AFH and found this thread. I will try in a bit to see if it is booting. Thanks for for this...
EDIT: forgot to ask, i assume this is built on faygi's LoS build? I am downloading now to test. RR is my favorite and glad to see this...
_Sherrif said:
Hey brother,
just seen your RR-Rom on AFH and found this thread. I will try in a bit to see if it is booting. Thanks for for this...
EDIT: forgot to ask, i assume this is built on faygi's LoS build? I am downloading now to test. RR is my favorite and glad to see this...
Click to expand...
Click to collapse
Yes, it's built with the same trees and dependencies so expect the same device side bugs.
I also built XenonHD pie but I accidentally set it to only include common.mk which resulted in missing latinIME (aosp keyboard).
I totally spaced out and forgot that common_full_phone.mk inherits common_full and common_full.mk inherits common.mk ?
I'll recompile XenonHD tonight with the fix tonight and make a thread for it on this forum as long as someone else doesn't already have plans to maintain it.
@AnierinB,
OK, i just installed the ROM and it would not boot. I wipe and factory reset, not boot. Then i wiped, factory reset and FORMATED data, still no boot. I only tried to install and boot without any gapps, ROM only. Not sure. I get to the RR logo and it tries to boot for about 2-3 minutes then re-boots back to TWRP.
Also, i found your HAVOC-OS build, i think it was yours anyway, if i remember correctly. I tried as above with HAVOC-OS and had the same result. The only thing i have not tried is to RUU back to the latest OREO build, then install the ROM(S). If there is anything i can do to assist in trouble shooting let me know, and i can re-install later today and get the log, or whatever is needed for ya! I use my phone for work so i can't go long during the day with service.
_Sherrif said:
@AnierinB,
OK, i just installed the ROM and it would not boot. I wipe and factory reset, not boot. Then i wiped, factory reset and FORMATED data, still no boot. I only tried to install and boot without any gapps, ROM only. Not sure. I get to the RR logo and it tries to boot for about 2-3 minutes then re-boots back to TWRP.
Also, i found your HAVOC-OS build, i think it was yours anyway, if i remember correctly. I tried as above with HAVOC-OS and had the same result. The only thing i have not tried is to RUU back to the latest OREO build, then install the ROM(S). If there is anything i can do to assist in trouble shooting let me know, and i can re-install later today and get the log, or whatever is needed for ya! I use my phone for work so i can't go long during the day with service.
Click to expand...
Click to collapse
Interesting, I'll have to take a look when I get off work tonight. I apologise for that. XenonHD is still planned as it works flawlessly with no boot issues
AnierinB said:
Interesting, I'll have to take a look when I get off work tonight. XenonHD is still planned as it works flawlessly with no boot issues
Click to expand...
Click to collapse
Noted and Tahanks.
Also, I would like to give XENON-HD a try but i do not see it on AFH any longer. I saw it the other day when i seen the HAVOC upload, but was uncertain as to what android flavor it was and could not find any posts anywhere about it so i passed on it. If you could provide a link to XENON-HD i would be happy to give it a test run.
_Sherrif said:
Noted and Tahanks.
Also, I would like to give XENON-HD a try but i do not see it on AFH any longer. I saw it the other day when i seen the HAVOC upload, but was uncertain as to what android flavor it was and could not find any posts anywhere about it so i passed on it. If you could provide a link to XENON-HD i would be happy to give it a test run.
Click to expand...
Click to collapse
I have to recompile it tonight with the keyboard fix. I already have all the source on @holofractals server so when I get off work I'll get right on that. The previous build was deleted from Android file host because of the missing aosp keyboard.
i cant get xenon to boot. tried pico gapps from today and pervous days what gapps you recommend?
voodooline said:
i cant get xenon to boot. tried pico gapps from today and pervous days what gapps you recommend?
Click to expand...
Click to collapse
Mind the gapps
AnierinB said:
Mind the gapps
Click to expand...
Click to collapse
I tried without gapps and couldnt get it to boot not sure whats up
voodooline said:
I tried without gapps and couldnt get it to boot not sure whats up
Click to expand...
Click to collapse
Try the latest build. I compiled two last night and they retained the same package name since the date was the same. I deleted the previous one in favor of the new one so download everything from the links in xenonhd thread (mindthegapps, and ROM). advance wipe everything in TWRP before flashing so make a backup prior and store it on sdcard or PC
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
Did you contacted the assistance? Seems a bad driver or kernel problem.
zSyntex said:
Did you contacted the assistance? Seems a bad driver or kernel problem.
Click to expand...
Click to collapse
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
persifele said:
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
Click to expand...
Click to collapse
We couldn't provide support for the hardware, mostly because you said that you've tried to reset the device and flash the stock ROM again.
If this doesn't fix the hardware issue, the assistance is the only way.
Probably a failure batch etc.
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
persifele said:
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
Click to expand...
Click to collapse
Simply download the latest firmware from SamLoader (Bifrost) and use Odin in order to flash it.
Tell me if you couldn't flash
I tried installing the latest firmware with odin, everything went fine but nothing, touch still doesn't work, i think tomorrow i'll take it to someone to fix it.
persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Captain_cookie_200 said:
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Click to expand...
Click to collapse
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
persifele said:
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
Click to expand...
Click to collapse
its fine. those are normal. if the flash suceeds at last that is all that matters
Captain_cookie_200 said:
its fine. those are normal. if the flash suceeds at last that is all that matters
Click to expand...
Click to collapse
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
persifele said:
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
Click to expand...
Click to collapse
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Captain_cookie_200 said:
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Click to expand...
Click to collapse
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
persifele said:
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
Click to expand...
Click to collapse
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Captain_cookie_200 said:
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Click to expand...
Click to collapse
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Captain_cookie_200 said:
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Click to expand...
Click to collapse
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
persifele said:
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
Click to expand...
Click to collapse
So uh looks like you have no options left. I just want to make sure. could you list the exact methods you used to flash the fw. Along with where u got the fw from? Lets see if the fw itself is broken or something.
Also this is very unrelated and time wasting. but you could try download one ui 5 firmware. Then extract super.img from ap. unsparse it and extract vendor.img and flash it to vendor partition using twrp. Then decrypt by typing
multidisabler twice in terminal as said in my previous post. Check if maybe an older version one ui 5 firmware has this issue fixed. one ui 5's kernel boots so one ui 5 vendor should work on 5.1 as well. It may not work but worth a try. you could also try doing this with android 12 firmware if that fixes it. if you do not have a linux machine availible i'll do it for you and upload the files for both firmwares here. Otherwise if its a hardware issue get your phone replaced or try getting the screen replaced. if still nothing happens ig switching to a new phone would be the only optiion.
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
persifele said:
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
Click to expand...
Click to collapse
i use samfw mostly for my firmwares. anyways. You need a linux machine nearby. ubuntu or arch. any distro based on them would work.
first you need to unsparse the super.img
for that we use
simg2img super.img super-raw.img
then we can use lpunpack or mount it to get our vendor.
we flash it using twrp and then we run multidisabler twice like we did when we first flashed gsi.
As you said above if you could do it for me it'd be awesome because i don't have a pc with linux rn.