Develop Bugs

Oppo find 7 X9076 rom problem, radi and wifi +

Hello, i hope there is someone that can help me with this problem i have.
I rooted and used cm12 sometime in the begining og 2015, then i unified the phone and used another rom(dont remember what), but it crashed sometime last summer and went black.
And after i have had it i started reading and found some posts and figured out i could try to get life in it befor cristhmas, and i found this: community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=&page=1[/url]
And i found a computer with win 7 on, and i got the phone back to life, but the rom stopped at language or region settings at installing.
and the i tried using nameless-recovery-twrp-2.8.7.0-find7-20151220 and the rom will start up, but i dont have wifi, radio or IMEI.
And i found someone that gave me oneplus.qcn this file, but i cant get my phone in to diagnostic mode, becouse the code *#801# is not working on my phone(Only *#06# is working).
I have tried different roms and recovery, but onlu namless rom is working in that way that i can start a rom (color os 1.4i up to 1,8i) over 1.8 will not start.
So i would be wery happy if there is someone that can help me fix it..
And i apologies for my English, but hopfully it is possible to understand.
Kindly regard
Johan

JPSimon said:
Hello, i hope there is someone that can help me with this problem i have.
I rooted and used cm12 sometime in the begining og 2015, then i unified the phone and used another rom(dont remember what), but it crashed sometime last summer and went black.
And after i have had it i started reading and found some posts and figured out i could try to get life in it befor cristhmas, and i found this: community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=&page=1[/url]
And i found a computer with win 7 on, and i got the phone back to life, but the rom stopped at language or region settings at installing.
and the i tried using nameless-recovery-twrp-2.8.7.0-find7-20151220 and the rom will start up, but i dont have wifi, radio or IMEI.
And i found someone that gave me oneplus.qcn this file, but i cant get my phone in to diagnostic mode, becouse the code *#801# is not working on my phone(Only *#06# is working).
I have tried different roms and recovery, but onlu namless rom is working in that way that i can start a rom (color os 1.4i up to 1,8i) over 1.8 will not start.
So i would be wery happy if there is someone that can help me fix it..
And i apologies for my English, but hopfully it is possible to understand.
Kindly regard
Johan
Click to expand...
Click to collapse
Hey there! Sad to hear that you have bricked your phone and lost your imei.
Im no expert, but have you retry the method provided in oppoforums? I suggest that you retry it once more.

Have tried
DingleBell said:
Hey there! Sad to hear that you have bricked your phone and lost your imei.
Im no expert, but have you retry the method provided in oppoforums? I suggest that you retry it once more.
Click to expand...
Click to collapse
Yes, i have tried it several times, and i only get to the same point every time.

JPSimon said:
Yes, i have tried it several times, and i only get to the same point every time.
Click to expand...
Click to collapse
Have you tried reverting back to stock ColorOS rom? Try to flash stock ColorOS 2.0.8i or ColorOS 2.1.5i to your phone. Usually when things go bad, people usually revert back to stock coloros rom and that fixed their problems as it fixed mine before this.

DingleBell said:
Have you tried reverting back to stock ColorOS rom? Try to flash stock ColorOS 2.0.8i or ColorOS 2.1.5i to your phone. Usually when things go bad, people usually revert back to stock coloros rom and that fixed their problems as it fixed mine before this.
Click to expand...
Click to collapse
The phone will only start up when i use colosos 1.4 up to 1.8, when i use higher or lower it will not start up..
And i can not use color recovery, only with nameless-recovery-twrp-2.8.7.0-find7-20151220..

HELP!!!! no wifi after going from slim remix to omni rom then back to stock

so today i was testing the roms availble outside of oxygen os (forgot to make a back-up of oxygen was on the oreo beta wich seems to have been pulled now )when i flashed liquid remix and saw everything worked well, so i went back to twrp to adb sideload the open beta build i ha saved from when it was released, adb sideload fails cant read the zip figured oh ill redownload it, see that oneplus has deleted the download link son i decided to test crdroid and that worked as well as the other so i flashed omni and loved it except that it couldnt get wifi working so i downloaded the stock zip for 4.74 adb sideload from the stock recovery and boot up, still not able to connect to wifi it allows me to enter the password and it starts connecting then fails for no reason after 3 tries to connect the ssid shows that it is disabled

Learn a bit before flashing

Do you still have a MAC address for the WIFI on your phone?

Flash stock including radios from the factory image via fastboot

i dont have the ip address on that phone but i can get it off my friends. where would i find the fastboot images for the oneplus 5T?

I had/have the same problem with my 5T. I flashed the Oreo beta and now I can't use any of the Nougat versions of Oxygen. I flashed the Oreo back on and the WiFi works fine.

RLD831 said:
I had/have the same problem with my 5T. I flashed the Oreo beta and now I can't use any of the Nougat versions of Oxygen. I flashed the Oreo back on and the WiFi works fine.
Click to expand...
Click to collapse
i cant find a version of the oreo beta that boots through could you link me to it

No problem. Let me upload it to my Google Drive and I'll post a link.

thanks ill report back

ummm its right in front of u... if it was a snake it would have bit u
https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074

Bradl79 said:
ummm its right in front of u... if it was a snake it would have bit u
https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074
Click to expand...
Click to collapse
already tried that build adb sideload cant read it and the stock oneplus recovery cant seem to see my internal storage whereas twrp can twrp flash fails

kanaan360 said:
already tried that build adb sideload cant read it and the stock oneplus recovery cant seem to see my internal storage whereas twrp can twrp flash fails
Click to expand...
Click to collapse
that is a full zip whether its stock or twrp... what error does it give u in twrp
or r u having an error flashing TWRP recovery via fastboot?

it doesnt give an error in twrp it just fails to boot after the flash also i know that it doesnt matter sice its a full zip im getting more at adb fails on both

kanaan360 said:
it doesnt give an error in twrp it just fails to boot after the flash also i know that it doesnt matter sice its a full zip im getting more at adb fails on both
Click to expand...
Click to collapse
sorry to hear the issues u are having, but this device is a Pain the Ass to try different things and flashing different things, unlike older devices which u could flash anything and everything back and fourth. I am not even going to try Open Betas on this device, I may even stay away from Oero and custom roms for awhile until we can find an unbricking tool
have u tried to the rollback and/or nougat full zip

Bradl79 said:
sorry to hear the issues u are having, but this device is a Pain the Ass to try different things and flashing different things, unlike older devices which u could flash anything and everything back and fourth. I am not even going to try Open Betas on this device, I may even stay away from Oero and custom roms for awhile until we can find an unbricking tool
have u tried to the rollback and/or nougat full zip
Click to expand...
Click to collapse
yea i think ill just fix my onplus 3 screen because damn only had one issue with that and it was an easy fix. ive gone back to 4.7.4 and im about to try the rollback

kanaan360 said:
yea i think ill just fix my onplus 3 screen because damn only had one issue with that and it was an easy fix. ive gone back to 4.7.4 and im about to try the rollback
Click to expand...
Click to collapse
good luck man... let me know how it goes

no luck, btw the roll back build puts you on 4.7.5

kanaan360 said:
so today i was testing the roms availble outside of oxygen os (forgot to make a back-up of oxygen was on the oreo beta wich seems to have been pulled now )when i flashed liquid remix and saw everything worked well, so i went back to twrp to adb sideload the open beta build i ha saved from when it was released, adb sideload fails cant read the zip figured oh ill redownload it, see that oneplus has deleted the download link son i decided to test crdroid and that worked as well as the other so i flashed omni and loved it except that it couldnt get wifi working so i downloaded the stock zip for 4.74 adb sideload from the stock recovery and boot up, still not able to connect to wifi it allows me to enter the password and it starts connecting then fails for no reason after 3 tries to connect the ssid shows that it is disabled
Click to expand...
Click to collapse
have you tried to remove the wifi Networks from the Network list and reconnect it? i had a similar issue where it showed my wifi Networks as saved by Default as it was synched trough Google. and i had to remove and reconnect in order to get it working.

nadejo said:
have you tried to remove the wifi Networks from the Network list and reconnect it? i had a similar issue where it showed my wifi Networks as saved by Default as it was synched trough Google. and i had to remove and reconnect in order to get it working.
Click to expand...
Click to collapse
yes i even have this issue without gapps

I had similar issue yesterday after flashing the liquid ROM - when i try to connect to Wifi it says "Disabled" after many struggle i flashed the OOS Open Beta 1 now it works fine.

I think my phone is totally dead

Hi everyone
Well im a type of guy who thinks that knows everything thats why im in problems right now. So i was using MIUI 10 beta since the first day it came out and i love it with weekly updates and noticable changes. Yesterday i saw that i can install Android P on my whyred i was pretty happy so i decided to try it today. I flashed everything and Android P worked like charm on my whyred.
But i wanted to go back to MIUI 10 and i was trying to flash using twrp but at the end i lost everything on my phone including OS. Then i downloaded MIUI 10 8.7.12 to flash it with MIFlash and i got the "Anti-Rollback" error. I found some toolkit on MIUI forum to remove anti-rollback so i tried again to flash rom but MIUI V.9.5.4.0 and it started to flash. Flash went good and it was completed but my phone turned off and its completly dead. No chance to turn it on or even to go in fastboot mode.
I dont really think that anyone can save it but if anyone heard or had that problem i will be so thankful if you could help! :fingers-crossed:

Have you try this?
https://forum.xda-developers.com/re...tutorial-unbrick-redmi-note-5-whyred-t3816260

I found some toolkit on MIUI forum to remove anti-rollback
Click to expand...
Click to collapse
There is no reported tool that can do that!
If it is the tool, I'm thinking of, it only allows unloking fastboot on ARP, so you can flash TWRP!

AlishaSama said:
Have you try this?
https://forum.xda-developers.com/re...tutorial-unbrick-redmi-note-5-whyred-t3816260
Click to expand...
Click to collapse
Thanks i will try. My pc can see my phone as "qusb_bulk" and i searched a little bit and i found out that is hard bricked so actually there is a way to fix this.

Dear seems that you flashed ARB 3 rom on ARB 4 enabled device
So hard bricked now you need mi authentication authorization to flash the latest rom.
All hard bricked users waiting for their permission from xiaome.

Question chinese tencent 120w red magic 6 pro 12gb/256gb eclipse black version with global rom?

anyone here that has successfully flashed this model of the rm 6 pro with a global rom? does that work or will i brick it?

Bet your the first tester to find out

Pachacouti said:
Bet your the first tester to find out
Click to expand...
Click to collapse
no, im too scared im a newb in this and i dont want to brick it. if i brick it i will be lost cause im a newb

And noobs had to start somewhere. So say someone says it works, then what will you do?

Pachacouti said:
And noobs had to start somewhere. So say someone says it works, then what will you do?
Click to expand...
Click to collapse
i would give it a try ^^

But your replying to me. I'd be shredding cables by now lol, but hey, is it possible your fone is a rebranded redmi 6 pro? Plenty of tuts here for that, but I'll try to help/guide you should you need it, tell me, what stock flashing application will you use to flash your stock BACK in case of a mistake?

Pachacouti said:
Pachacouti said:
But your replying to me. I'd be shredding cables by now lol, but hey, is it possible your fone is a rebranded redmi 6 pro? Plenty of tuts here for that, but I'll trry to help/guide you should you need it, tell me, what stock flashing application will you use to flash your stock BACK in case of a mistake?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
the problem is that the vendor from china put some crippled stock rom on my phone where they removed the system update service and so i cant do a local update with the phone. my rm 6 telegram group suggested that i install the qcom 9008 usb driver on my pc and boot my phone via adb into qcom 9008 edl mode and use miflash to flash it with a 4.15 unbrick package and if this would work i would have intact system update again and could flash it with a local update with the firmware id like. thanks for the help btw. gotta go out in 5 minutes but be back in a bit. please give me your opinion, i will read it once im back

What you wrote sounds good. Your flashing app is miflash. Download the 4.14 unbrick, and load it into miflash without fone plugged in, power fone OFF, start the miflash, hit download/flash (dont know the actual button to do the damage), then plug turned off fone into usb, miflash should auto find and flash, anything after that, feel free to ask.
Ps you could just jump in the deep end and flash the one you WANT, so that if it fails you'll know if it works or not, and will have tested a rom before flashing your stock back, kinda better than flashing stock first in a way.

Pachacouti said:
What you wrote sounds good. Your flashing app is miflash. Download the 4.14 unbrick, and load it into miflash without fone plugged in, power fone OFF, start the miflash, hit download/flash (dont know the actual button to do the damage), then plug turned off fone into usb, miflash should auto find and flash, anything after that, feel free to ask.
Ps you could just jump in the deep end and flash the one you WANT, so that if it fails you'll know if it works or not, and will have tested a rom before flashing your stock back, kinda better than flashing stock first in a way.
Click to expand...
Click to collapse
thanks for the suggestions! i want to give this a try as soon as i have some time. buthow do i backup my current stock rom in case the new rom wont work? i only know about rom manager app but that needs a rooted phone and mines isnt rooted. is there a way to backup the stock rom without having a rooted device?

Forget backing that up, your already at the stage where you learn if you back this up now, you MAY also back up the problem and have to do it all again, take my advice, keep it simple.
For your 'backup' - download latest official stock from your fone maker.
You may want to revert back AFTER you test the one you want to test.
So test first while it's 'broken' knowing once you go back to stock, it aint broke, dont fix it.

Pachacouti said:
Forget backing that up, your already at the stage where you learn if you back this up now, you MAY also back up the problem and have to do it all again, take my advice, keep it simple.
For your 'backup' - download latest official stock from your fone maker.
You may want to revert back AFTER you test the one you want to test.
So test first while it's 'broken' knowing once you go back to stock, it aint broke, dont fix it.
Click to expand...
Click to collapse
hey there! thanks for your tips, i appreciate it! ok just to clear things up, with "stock" firmware, you mean the official latest chinese firmware from the chinese nubia page, right?

Yup, if thats what you know is your STOCK, ie, not the one you wanna test, but in your scenario, I'd flash the test before stock, this way you gain experience flashing, and if you mess up, then you flash the stock, and learn not to. (again lol)
To clarify, stock is the firmware the fone maker has on their site.
Follow thir instructions, it's easier than you think, as my auld man told me, when testing, write down every step, so you REMEMBER instead of being unsure because I forgot....

Pachacouti said:
Yup, if thats what you know is your STOCK, ie, not the one you wanna test, but in your scenario, I'd flash the test before stock, this way you gain experience flashing, and if you mess up, then you flash the stock, and learn not to. (again lol)
To clarify, stock is the firmware the fone maker has on their site.
Follow thir instructions, it's easier than you think, as my auld man told me, when testing, write down every step, so you REMEMBER instead of being unsure because I forgot....
Click to expand...
Click to collapse
ok i got it. thanks for the help! i have the stock ready on my computer. unfortunately i cant flash my phone by following the manufacturers steps because my phone vendor flashed my phone with some custom chinese multi language firmware with google already pre installed. and whoever edited this firmware before flashing it on my new phone, removed the system service that is necessary to launch the "system update" options. therefore i have no way of making a local firmware update in my phone. unfortunately the red magic 6 pro also does not have a local update option in the recovery menu. thats why my only option is flashing the phone with my computer. but in the worst case i will have the latest stock rom on my phone in the end and this will have the system update options intact. thanks again for all the help!

Question Touchscreen not working

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.