yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
Did you upload the version i've tested? So i don't have to update again?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
Again, its not working for me. Played a bit around, it seems the recoveries has different file size. I have a twrp, im totally sure its was yours is named as twrp-3.3.1-0-android-10.0-beyond2lte-2.img (30.03.2020) - works flawlessly. Its 64MB big, the other newer one are only 22MB. Ive tested with the last 3.3.1-0 and got the same error. Flashed with different methods and with odin too. Still the same. The same like on 3.4.0-0.

So 2 guys are saying its impossible to update, only one guy tell its working. And beleive me, im not a noop or so.;)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
If i take a look at the AndroidFilehost page of the twrp for the S10+ i dont see an image with the size of 64 MB. Every image has about 22 MB. Are you sure you have flashed the one of modpunk?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
I know, this is what is a bit strange. But there is no twrp which is named like his one. Fact is, i cant flash the smaller size recoveries. Maybe bootloader related, i have atm no clue (im still on cte6). But [MENTION=5031484][Legenda][/MENTION] is sitting in the same boat?

So ive unpacked the working recovery. Here are some textfiles of the properties:

ro.bootimage.build.date=Mon 30 Mar 2020 05:31:57 PM CEST
ro.bootimage.build.date.utc=1585582317
ro.bootimage.build.fingerprint=samsung/beyond2ltexx/beyond2:10/QP1A.190711.020/G970FXXU4BTA8:user/release-keys
persist.sys.usb.config=adb

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PQ3B.190801.002
ro.build.display.id=omni_beyond2lte-eng 10.0 PQ3B.190801.002 eng.asn.20200330.173207 dev-keys
ro.build.version.incremental=eng.asn.20200330.173207
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=10.0
ro.build.version.security_patch=2025-12-31
ro.omni.version.security_patch=
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=17
ro.build.date=Mon 30 Mar 2020 05:31:57 PM CEST
ro.build.date.utc=1585582317
ro.build.type=eng
ro.build.user=asn
[COLOR=Red]ro.build.host=magrathea[/COLOR]
ro.build.tags=dev-keys
ro.build.flavor=omni_beyond2lte-eng
ro.build.system_root_image=true
ro.build.ab_update=false
ro.product.model=SM-G975F
ro.product.brand=Samsung
ro.product.name=beyond2lte

I cant check the newer recoveries cause it show me an an incompatible format (Unrecognized format.

Error!).

Ive checked other recoveries and they all have other files inside(name etc,), so it must be one of the first releases which where removed or so. Maybe with samsung sources compiled. Reason why its so big compared with the newer asop versions.

Im still playing sherlock holmes.;) Searched for ro.build.host=magrathea and found a twrp thread for xperia device from Modpunk. So im totally sure its his twrp.;)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] majorkid:
Hi modpunk , I'm on Stock Rom CTE6 bootloader unlocked , I tried installing your twrp , but I can't flash vbmeta-disabled.tar at all , This is what I tried

1.Flashed twrp(Flashed fine ) and then flashed vbmeta(stuck at file analysis)

2.Tried flashing vbmeta first guess what it didn't flash .

3.Tried three different version of odin

still , it can't load , any help ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] FrankFoss:
The twrp-3.4.0-0-android-10.0-beyond0lte-2.img.xz is about 20mb small thats right.

After you download it you have to unpack it so you get the img which you can flash with the twrp recovery. After you unpack the img.xz file you will get twrp-3.4.0-0-android-10.0-beyond0lte-2.img and its about 67mb big.

Hope this helps.

(its working here fine!)

---------- Post added at 08:56 PM ---------- Previous post was at 08:40 PM ----------

You can flash the vbmeta-disabled.img from the TWRP recovery (select the boot partition) and it will work.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
I cant remember that ive extracted the recoveries:eek:, but this method works. It seems like you never stop learning.:silly:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] [Legenda]:
I'm using a custom Twrp from Corsicanu (The dev who made Hades rom). May be that's why i can't update with this TWRP? What do you think?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
No. Did you read the post above me? You must extract the .img.xz file dont rename at as is did.:p Otherwise it wont work. Btw. are you getting the same kernel length error like me when you flash it?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] [Legenda]:
Yeah i read it. I'll give it a try later. And i rename it like you did :D ! I don't have the same error like you had.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] __Michael__:
I have already modpunk's TWRP , I want to update to last version , can i just flash the img on TWRP?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
Yes. But extract it first and flash the .img through twrp by selecting the recovery slot. Or use the twrp- or flashify app.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] [Legenda]:
I succed to install the latest update. Thanks :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JohnDandel:
Building TWRP

I can build [MENTION=4297219]modpunk[/MENTION] TWRP, but flashing it with TWRP gives me an error. I get sent back to Download Mode with an error message on the phone's screen. Here is the error

Just FYI: I am flashing a TWRP.tar file using ODIN that contains the recovery.img file and vbmeta.img file.

BIN MODE (DT Load Fail)

[OTH] dt table header check Fail: <unknown error>

load_kernel: Could not do Normal boot (DT LOAD Fail)

vbmeta: Error verifying vbmeta image OK_NOT_SIGNED (3)

CUSTOM VBMETA

VBMETA : No Sign info

VBMETA .

I unpacked the recovery.img file that I created and the one that Modpunk created using the following command.

python unpack_bootimg --boot_img recovery.img --out recovery

The results of Modpunks official release gives me this

RELEASE unpack output:

boot_magic: ANDROID!

kernel_size: 46350348

kernel load address: 268468224

ramdisk size: 12152716

ramdisk load address: 285212672

second bootloader size: 0

second bootloader load address: 284164096

kernel tags load address: 268435712

page size: 2048

boot image header version: 1

os version and patch level: 335544732

product name: SRPRI28A004RU

command line args: androidboot.selinux=permissive buildvariant=eng

additional command line args:

recovery dtbo size: 8388608

recovery dtbo offset: 58507264

boot header size: 1648

My recovery unpack output gives me this

boot_magic: ANDROID!

kernel_size: 46350348

kernel load address: 268468224

ramdisk size: 11799690

ramdisk load address: 285212672

second bootloader size: 0

second bootloader load address: 284164096

kernel tags load address: 268435712

page size: 2048

boot image header version: 1

os version and patch level: 335544732

product name: SRPRI28A004RU

command line args: androidboot.selinux=permissive buildvariant=eng

additional command line args:

recovery dtbo size: 8388608

recovery dtbo offset: 58155008

boot header size: 1648

The differences are the recovery_dtbo offset and ramdisk size.

The instructions for building and installing this TWRP are very simple.

What am I doing wrong?

Thanks for any help.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Something seems to be wrong with the ramdisk, did you run extract-util.sh and it found all the libs?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Download the stock rom, convert the system and vendor image from sparse images to raw images, mount them and copy the files into a directory then run:

./extract-files.sh /path/to/ROM
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hamzih:
rom works perfectly, but i cant get safetynet to work

i have tried props config but both cts and basicintegrity stay in red.

Followed all instructions correctly and flashed the magisk boot img also
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JohnDandel:
Thanks for the advice on how to extract the files. It worked. I then built TWRP and installed it with heimdall using this command

heimdall flash --RECOVERY recovery.img --VBMETA vbmeta.img --no-reboot

After restarting the phone to get into recovery, the phone still goes back into Download mode with this error

BIN MODE (DT Load Fail)

[OTH] dt table header check Fail: <unknown error>

load_kernel: Could not do Normal boot (DT LOAD Fail)

vbmeta: Error verifying vbmeta image OK_NOT_SIGNED (3)

CUSTOM VBMETA

VBMETA : No Sign info

VBMETA .

Are you building this TWRP and signing it? Do I need to build a vbmeta.img myself to get TWRP to install?

Thanks for you help
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Normally you just have to flash a disabled vbmeta image once, then it will be disabled until you flash a new vbmeta image.

The error above sounds like it can't find the dtbo image which is part of the recovery. I the error from the screen? If it fails to boot into TWRP but then boots into system you can check /proc/last_kmsg which has the log of the bootloader (sboot) tryint to boot the recovery.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Gymcode:
I patched my AP file with the replaced 'recover.img' of TWRP. However, after flashing and installing via Odin, I am still on stock recovery.

I checked the .tar file generated by Magisk after patching, and there is no 'Recovery.img' inside it after it was patched.

May I know if the above behavior is normal, should 'Recovery.img' exist in the magisk-patched .tar output file?

Below is my flash log:

- Device platform: arm64-v8a

- Processing tar file

-- Extracting: boot.img

-- Writing: dqmdbg.img.lz4

-- Writing: dt.img.lz4

-- Writing: dtbo.img.lz4

-- Writing: meta-data/

-- Writing: meta-data/fota.zip

-- Extracting: recovery.img

-- Writing: system.img.lz4

-- Writing: userdata.img.lz4

-- Writing: vbmeta.img

-- Writing: vendor.img.lz4

-- Writing: boot.img

- Unpacking boot image

- Stock boot image detected

- Patching ramdisk

- Repacking boot image

-- Writing: recovery.img

****************************

Output file is placed in

/storage/emulated/0/Download/magisk_patched.tar

****************************

- All done!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] FrankFoss:
Is your phone rooted?

If yes just download the Recovery img and flash it with odin or heimdall,

1.Download the recovery.img.xz file and extract it so you get the recovery.img then name it recovery.tar if you wanna use Odin. (you will need also the vbmeta-disabled.img so download it too)

2.Uncheck Auto Reboot then Click the AP button on Odin and choose your recovery.tar file.

3.Click Start.

4.You have now flashed the TWRP Recovery, don't reboot the System!

5.Boot your phone directly into TWRP recovery mode!

(Press Power and Volume Down buttons together to exit Download Mode.

As soon as the screen turns off, quickly press and hold the Power, Volume Up, and Bixby buttons together until the Bootloader Warning message appears.

Once the Bootloader Warning screen appears, release the Bixby and Power buttons and keep holding the Volume Up button to enter TWRP recovery mode.)

6.Now navigate to the Place you have placed the vbmeta-disabled.img (sd card) click on flash img then choose the file and flash it on the boot partition.

7.After it has been flashed go to Wipe/Format Data and format it.

8.(now you can install Lineageos for example)

9.If you dont wanna install a Custom OS reboot your OS and install the Magisk Mananger, then open it with wifi or data connection so Magisk can perform the needed setup for your phone.

10. Enjoy!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ^^rac:
*Deleted
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JohnDandel:
I was able to build and install TWRP but I am seeing something weird between your build and mine when I look at the unpacked image file types. The ramdisk file sizes are the same but the file types are not.

//What A Wurst recovery image

File Name Type Size

kernel data 46.6MB

ramdisk LZMA compressed data, streamed 12.2MB

recovery_dtbo data 8.4MB

second emtpy 0MB

//My recovery image

File Name Type Size

kernel data 46.6MB

ramdisk data 12.2MB

recovery_dtbo data 8.4MB

second emtpy 0MB

But I was able to get my TWRP build installed using a little trick I found. Here is how I was able to get it done.

First I did a normal build of TWRP. Got a success.

Then I took the WhatAWurst offical recovery image and unpacked it using this command

$ python unpack_bootimg --boot_img twrp-3.4.0-0-android-10.0-beyond1lte-2.img --out recovery

$ cd recovery

Then I deleted the ramdisk file. I then copied my ramdisk-recovery.img from the

/out/target/product/beyond1lte/ramdisk-recovery.img file to the /recovery directory.

The ramdisk-recovery.img does have a file type of LZMA compressed data, streamed

I renamed it ramdisk. Then I packaged it up using this command.

$ python mkbootimg --kernel kernel --recovery_dtbo recovery_dtbo --ramdisk ramdisk --second second --output recovery.img --pagesize 2048 --header_version 1

I went into download mode and flashed the recovery.img onto the phone using heimdall with this command

$ heimdall flash --RECOVERY recovery.img --VBMETA vbmeta.img --no-reboot

I then went into TWRP and success.

Done :)

I also tried replacing my recovery images ramdisk with the ramdisk-recovery.img, but that did not flash. Don't know why.

So why does flashing work when I replace the ramdisk in the official build with my ramdisk-recovery.img work?

Why are the file types between your build and my build different?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Sounds like a bug in the omni environment, did you just try to create the recovery image with `mkbootimg` after it built. Just recreate the image manually and try.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] NowLearn:
Bro, you the boss. im about to flash lineage+Flash Twrp on my stock s10 plus. Im follow your instruction. i dont understand that two twrp version. THat one here ind this thread and the other TWRP by anmacd. Hopefully if i do what u said i wont brick my phone, thank you

---------- Post added at 01:06 AM ---------- Previous post was at 12:37 AM ----------

quick question, did you have any issues with banking application? thank you
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] NowLearn:
I tried this for s10 Plus. I got a message on ODIN

recovery.img

<ID:0/006> vbmeta.img

<ID:0/006> RQT_CLOSE !!

<ID:0/006>

<ID:0/006> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

It failed, I use the VBMETA(step 13) . its there a new VBmeta version for android 10. Thank you
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] NowLearn:
Im on Android 10, june security. I finaly got my phone root with magisk after 14 hours. But now I cant flash twrp. I tried using the File with extension .xy to rename to .TAR and added on ODIN AP

D:0/006> File analysis..

<ID:0/006> Total Binary size: 0 M

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> NAND Write Start!!

<ID:0/006> SingleDownload.

<ID:0/006> ANDROID!*É

<ID:0/006> RQT_CLOSE !!

<ID:0/006> RES OK !!

<ID:0/006> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

<ID:0/006> Removed!!

after I reboot I still get the same samsumg recovery. I also did the version where you take the recovery.IMG to magisk and get a patches one, and still i cant get to install twrp. Help a brother out. What am i doing wrong.

Thank you
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] FrankFoss:
Check out my post https://xdaforums.com/showpost.php?p=82897165&postcount=147

it may help you.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] davidnghk:
Hi [MENTION=4297219]modpunk[/MENTION] or someone knows

after install this twrp and magisk, on each reboot and power on the device, will it auto boot into the magisk root mode without pressing the "key combo (VOL up key + Power + Bixby)"

thank you.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] DevilFu:
Any chance with S10 5G (Exynos) such as SM-G977N?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Gymcode:
I have a Magisk installed and running S10e. I would like to install TWRP. Are the following steps correct? I am not sure of the steps, and would like to know if there is a way not to lose data....

1. Have a Magisk-patched TWRP (AP) file

2. Run the above file in Odin

3. Full Format required (?)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] WalterCool:
Hard to answer that question. One of my bank accounts has problems, not with others.

It depends of the bank mostly
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
Same here with one banking app..but for me it fixes the problem to use the Canary Build of the Manager
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] 7hr08ik:
Guys, I need help.

Back in December i shattered my screen, just got it sorted out this week. So i've reset to latest stock CTF1.

Now im trying to install TWRP and 'Only release binaries are allowed to be flashed'
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] 7hr08ik:
Fixed: https://xdaforums.com/showpost.php?p=79944730&postcount=2

Relock > date fix > Unlock > Fine :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I've released new TWRP builds. Changelog on the first page.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ^^rac:
Hi AndrOdin

Thank you so much for this tutorial, i was looking everywhere could not get the gist of how to continue to complete TWRP with root etc. This helped a stack!:D:D:D
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] grymmy:
hey there..I'm about to receive my S10+ (G975F) soon and definitely would like to root. Read the instructions above for the S10e, is it the same for the S10+ but download relevant files for S10+ instead?

Will it be too much to have a write up for the S10+ as well?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Srbija2012:
I have the same question... Following...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Gymcode:
I am on a Magisk installed s10e, is it possible to install TWRP, and without wiping data?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
It depends on what you want to do with it in future...

Other TWRP installed and if you don't want to install lineageos of [MENTION=4297219]modpunk[/MENTION] -> Yes!

Other TWRP installed and you want to install [MENTION=4297219]modpunk[/MENTION]'s LOS with FBE -> No!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Gymcode:
I'm on stock OneUI 2.1. So I can follow the steps to install TWRP, or there are some differences in steps that I need to take note of?

Thank you! :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] szata.68:
Hi all!

I have an S10 with stock G973FXXU8CTG4 firware. I already unlocked the bootloader, and I'd like to ask if I can install twrp,root,and flash a custom ROM from this stock version?

Thanks in advance

Best regards
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
3d post, the change log.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] szata.68:
I must be the stupid, but I read it,and don't understand if it's good for me or not. :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
Don't say that my friend, only CTF1-3 for now.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
This recovery works with any fw. Im on older 3.3.1-x on my ctg4 ROM and all is working well. Its not like in ians builds, which is mostly incomaptible to newer FWs.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ^^rac:
Hi guys, looking for the VBMETA file for Galaxy S10e? No mirrors found on the current download link? Thanks alot
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
Click me
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Braunbär_1:
Thank you :) - Wie sagen die Amis: you saved my day.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
You're welcome....or like we say in bavaria "Basst scho!" :D
[Samsung Galaxy Note 10+ Themes, Apps, and Mods] deio:
Hello all,

Can I remove annoying shutter sound somehow? I have deleted shutter.ogg but camera still has shutter sound. I wonder from where it pulls the ogg sound?

It's most anoying.
[Samsung Galaxy Note 10+ Themes, Apps, and Mods] ianmb:
Mine has option in camera settings Note10+Sprint
[Samsung Galaxy Note 10+ Themes, Apps, and Mods] ianmb:
PicView attachment 4972633
[Samsung Galaxy Note 10+ Themes, Apps, and Mods] deio:
Mine is European version Exynos and is forbidden in some countries to have shutter sound. Can someone tell me what to enter in OMC CSC? I have tried to edit customer.xml and add the line <CSC Shuttersound option etc, but no succes. I have even tried to create an others.xml, but no luck.
[Samsung Galaxy Note 10+ Themes, Apps, and Mods] butchieboy:
Usually it's a law that says you have to have shutter sound in some countries and states.
[Samsung Galaxy Note 10+ Themes, Apps, and Mods] deio:
I found out the problem. There is a file in OMC folder, in each CSC region, that is encoded, Samsung are scumbags. The file needs to be decoded with an OMC decoder. The file is CSCFeature.xml

Problem is, I don't have the decoder. Also, the Samsung Camera app, has inside the shutter.ogg now, so deleting the file from UI folder is useless. Real scumbags Samsung. They hid the file inside in priv-app folder and if you try to delete it, camera app won't start.

Also, I do not want workarounds like putting volumes to silent or Tasker or Bixby Routines, I wanted a real solution. Working in apk would destroy the camera app, so the only solution is decoding the omc file and encoding it back, after inserting <CscFeature_Camera_ShutterSoundMenu>TRUE</CscFeature_Camera_ShutterSoundMenu> inside CSCFeature.xml when it's decoded.

It's a tough one, I reckon and only someone with good programing skills can do it ...
[Samsung Galaxy Note 10+ Themes, Apps, and Mods] TheFerhatKing:
There you go my man. You need Java installed and put the commands in cmd on Windows.

https://github.com/fei-ke/OmcTextDecoder/blob/master/README.md

Gesendet von meinem SM-N975F mit Tapatalk
[Samsung Galaxy Note 10+ Themes, Apps, and Mods] Vita.T:
I'm using the app Mute Camera pro and it got the job done well.
[Samsung Galaxy Note 10+ Themes, Apps, and Mods] deio:
OMG, it worked! I couldn't find a proper decoder without Python.

Du bist ein Engel! Danke!
[Realme 6 Pro Questions & Answers] debdeep98:
Wanted to disable all the bloat using ADB but for some wierd reason the device doesn't show in the ADB devices list. Installed the Qualcomm drivers too. Couldn't find any realme usb drivers. Used original cable. Old moto and asus are showing up but the 6 pro isn't. Tried midi, ptp, mtp, usb tether too.

Anyone know a solution to this?

Edit: installed pdanet on pc. Auth prompt showed up. Works fine now.
[Touch Diamond, MDA Compact IV General] nokmond:
Hi all, i've downloaded Opera Mini because i find its quicker than full opera for checking ebay/quick google search etc. Its a java app but i can't seem to install it and keep it installed?

ie. i click on opera mini in file explorer and it installs it and runs but next time i want opera mini i have to do the same thing allover again.

I'm guessing i'm stupid and doing something wrong. :p
[LG V40 Questions & Answers] Droidman61:
I am having major issues with GFIL working. My bootloader showed locked, though I know it was unlocked. Now it is grey out and says it is unlocked, it there a way to get that back to showing locked so I can manually unlock it again.

I am thinking that is the only reason QFIL is not working:confused:

Thank you:good:
[LG V40 Questions & Answers] KouaV1:
Qfil only works if you entered the bulk or 9008 mode only. If you have unlocked your bootloader and reflashed or flashed a stock kdz for your device you will now have to relock and unlock it again, a reason why its greyed out.