Related
Hello,
Many people have problem with bricked device because they complied many diffrent tutorials and broke their G2.
I will explain you how to root stock rom/update bootloader and back to stock via lg flashtool.
Perform operations step by step
Okay, so first thing - ROOT STOCK LG ROM.
1. Stump ROOT (Without usb cable, working with 20h ROM)
Stump Root v1.2 (Newest version)
-->> Download Stump ROOT v1.2 <<--
Go to settings>general>security and check "Unknown Sources" to install external APKs.
Now install Stump ROOT app from download link. (In installation progress Android will ask you for install permisions because this integrate in system code. OFC ACCEPT)
Open Stump ROOT and press GRIND, then wait sec and press BruteForce, after 1-2 min your device will restart and now u got ROOT, u need install -->> SuperSU <<-- from market.
2. Install TWRP for your device. (Autorec)
-->> Download AUTOREC <<--
Okay, it's easiest step, just install Autorec application (Be sure it's for your model in file name!)
Open, accept and flash.
This way will downgrade your bootloader and kernel. After device reboot u have already ROOT and TWRP.
Now u can update first your TWRP to newest 2.8.5.1
-->> HERE THEARD WITH NEW TWRP <<--
If you download new TWRP, then u can easy flash it via -->> Flashify <<-- app from market. There select recovery>zip and select your new TWRP, it will reboot device to recovery and flash. (BE SURE IT'S FOR YOUR D802 MODEL!!)
3. Update bootloader. (IMPORTANT!!! U ALWAYS NEED UPDATE BOOTLOADER WITH VERSION ROM WHAT YOU ALREADY HAVE, IF YOUR ROM V20H, USE 20H BOOTLOADER, IF YOU HAVE 20D, THEN USE 20D BOOTLOADER OR UPDATE YOUR DEVICE TO 20H!!)
Now u need becareful, because it is easy way to brick device if you will not perform tutorial.
-->> Download v20h bootloader <<--
Download bootloader to your memory storage in device, and open flashify, press Menu button and Reboot Recovery, when it will reboot to TWRP, press INSTALL and select bootloader v20h zip file in path you downloaded it.
Now reboot device and Enjoy ROOTED device with newest bumped TWRP and newest bootloader.. AND NO BRICK )
Enjoy your powerfull device.
I will update theard with new steps like install kernels, back to stock step by step, easiest way to secure your device.
I know there are many tutorials, but we have still many people on XDA with problems like QS_BULK device, 9008, secure verify problem etc etc. So this is way to bypass every danger things.
Im not creator of any used in this tutorial mods, i just complied few theards to few easy steps
Credits:
Dorimanx
Cloudyfa
blastagator
jcase
Codefire Team
Hi good Job!
I have Two questions.
Can i upgrade my twrp Version with flashing the zip file in twrp?
Which Bootloader version use cyanogenmod 12?
Thank you!
A few additional info for the D802 variant:
-You don't NEED to change boot loader if you're fully on stock unless:
--You plan to use AOSP Lollipop
--You use any JB based ROMs (they should say in their respective threads for the D802)
-If you stick with the KK boot loader, only flash BUMPed flashables (they should state if they use this method)
-I recommend to use Blastagator's TWRP as it has thermal protection that stock TWRP doesn't have
-Only flash ROMs/any other flashables while the phone is cool
-Most ROMs can use the KK modem unless stated otherwise
Correct me on any misunderstood/incorrect information
---------- Post added at 10:56 AM ---------- Previous post was at 10:48 AM ----------
exxilee said:
Hi good Job!
I have Two questions.
Can i upgrade my twrp Version with flashing the zip file in twrp?
Which Bootloader version use cyanogenmod 12?
Thank you!
Click to expand...
Click to collapse
1. You should be able to
2. You should be on the JB boot loader, we don't have the 12B one, that's for another variant
exxilee said:
Hi good Job!
I have Two questions.
Can i upgrade my twrp Version with flashing the zip file in twrp?
Which Bootloader version use cyanogenmod 12?
Thank you!
Click to expand...
Click to collapse
Yes. If you installed AutoRec and u are able to open recovery, you can flash via older twrp. It is no problem
goodguy25 said:
A few additional info for the D802 variant:
-You don't NEED to change boot loader if you're fully on stock unless:
--You plan to use AOSP Lollipop
--You use any JB based ROMs (they should say in their respective threads for the D802)
-If you stick with the KK boot loader, only flash BUMPed flashables (they should state if they use this method)
-I recommend to use Blastagator's TWRP as it has thermal protection that stock TWRP doesn't have
-Only flash ROMs/any other flashables while the phone is cool
-Most ROMs can use the KK modem unless stated otherwise
Correct me on any misunderstood/incorrect information
---------- Post added at 10:56 AM ---------- Previous post was at 10:48 AM ----------
1. You should be able to
2. You should be on the JB boot loader, we don't have the 12B one, that's for another variant
Click to expand...
Click to collapse
I just wrote this tutorial for Stock, and it's always good to have new stuff. It's safe with bumped twrp and it shouldn't make any problem with device.
Thank you guys!
So i dont need to change my Bootloader to Flash cm12?
Installed twrp via autorec and im on Stock kk.
exxilee said:
Thank you guys!
So i dont need to change my Bootloader to Flash cm12?
Installed twrp via autorec and im on Stock kk.
Click to expand...
Click to collapse
U no need, no matter u have JB or KK bootloader if you use CM12 or other AOSP ROMs
Ganjax said:
I just wrote this tutorial for Stock, and it's always good to have new stuff. It's safe with bumped twrp and it shouldn't make any problem with device.
Click to expand...
Click to collapse
Ok, good. I liked your tutorial, pretty informative.
Hello, i'm stuck at this step :
"3. Update bootloader. (IMPORTANT!!! U ALWAYS NEED UPDATE BOOTLOADER WITH VERSION ROM WHAT YOU ALREADY HAVE, IF YOUR ROM V20H, USE 20H BOOTLOADER, IF YOU HAVE 20D, THEN USE 20D BOOTLOADER OR UPDATE YOUR DEVICE TO 20H!!)
Now u need becareful, because it is easy way to brick device if you will not perform tutorial.
-->> Download v20h bootloader <<--
Download bootloader to your memory storage in device, and open flashify, press Menu button and Reboot Recovery, when it will reboot to TWRP, press INSTALL and select bootloader v20h zip file in path you downloaded it. "
Edit : i flashed the rom without KK bootloader and it worked
-> I Was on 20H. I rooted, installed twrp, updated twrp. I've flashed 20d KK bootloader and now, secure booting error
I have access to download mode. What can i do do boot normally ? (i know i could probably flash a kdz but i don't really want to)
i cannot enter into the twrp by pressing the vol down + power, it just ask me whether i want to format, this means i still do not have twrp ?
coc014 said:
Hello, i'm stuck at this step :
"3. Update bootloader. (IMPORTANT!!! U ALWAYS NEED UPDATE BOOTLOADER WITH VERSION ROM WHAT YOU ALREADY HAVE, IF YOUR ROM V20H, USE 20H BOOTLOADER, IF YOU HAVE 20D, THEN USE 20D BOOTLOADER OR UPDATE YOUR DEVICE TO 20H!!)
Now u need becareful, because it is easy way to brick device if you will not perform tutorial.
-->> Download v20h bootloader <<--
Download bootloader to your memory storage in device, and open flashify, press Menu button and Reboot Recovery, when it will reboot to TWRP, press INSTALL and select bootloader v20h zip file in path you downloaded it. "
Edit : i flashed the rom without KK bootloader and it worked
-> I Was on 20H. I rooted, installed twrp, updated twrp. I've flashed 20d KK bootloader and now, secure booting error
I have access to download mode. What can i do do boot normally ? (i know i could probably flash a kdz but i don't really want to)
Click to expand...
Click to collapse
Well if you cant enter your recovery or system then you have to flash kdz.
chris7617 said:
i cannot enter into the twrp by pressing the vol down + power, it just ask me whether i want to format, this means i still do not have twrp ?
Click to expand...
Click to collapse
You already flashed TWRP right? If so then you need to confirm it twice with the power button. It says like format data/factory reset but it will boot into the custom recovery.
please help me...i have a lg g2 d802 32gb model ..its a traded phone...when i got the phone it was running 4.4.2 kitkat the phone was rooted bt there was no suprrueser app i installed the app and then i flashed recovery with autorec now whenever i open my data or wifi and use my phone for some minutes my screen becomes unresponsive is it due to the jellybean bootloader that the autorec installed or something else please help me...
Recovery combo gone
The thread seems like dead now, but maybe I get help .
I flashed 20H and now there is the recovery combo, when I try pwr + volume down it simply reboots . The recovery is instaled, but I only can access it from software (that now is corrupted, so, soft brick).
Wrong combo
chris7617 said:
i cannot enter into the twrp by pressing the vol down + power, it just ask me whether i want to format, this means i still do not have twrp ?
Click to expand...
Click to collapse
You're not soft bricked, it's just that key combo changes in 20H, new combo to enter recovery is vol down + power key, As lg logo appears, release keys and press vol up + vol down and you can easily access twrp
and i ran intro bootloop.. help!
I'll update theard soon to aosp/lollipop support, bootstacks explains etc.
Wysłane z mojego LG-D802
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device (and all of your apps and settings are the same)
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again ( to be sure ) - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
10. make TWRP backup when needed
11 IF YOU WANT TO UPDATE TO B02 : use this methode https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
EDIT : when you want to get rid of the bootscreen which states that you have an unlocked bootloader, follow this procedure (very easy )
https://forum.xda-developers.com/showpost.php?p=71444728&postcount=496
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
raystef66 said:
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
Click to expand...
Click to collapse
I'm on stock B29, rooted, unlocked bootloader.
Been avoiding updates, but this looks promising to keep root.
Think it will work for me? Forgot to mention I have 3.0.4 twrp
HTC55555 said:
I'm on stock B29, rooted, unlocked bootloader.
Been avoiding updates, but this looks promising to keep root.
Think it will work for me?
Click to expand...
Click to collapse
Don't know exactly.
For G users the latest update before 7.0 was the B10. Therefore B10 is the necessary flash before G users can flash N
As long as you keep TWRP running ( as far as i know do not wipe system etc...therefore i mentioned earlier to not wipe anything) and your latest backup, you can always restore it.
Hmm... I did this a week ago and forgot to flash SuperSU. Messed up big time... Axon7tool gives the what() error, but people say that even if it successfully flashes the recovery, the stock recovery remains there.
So I need the inverse process... any idea how?
Choose an username... said:
Hmm... I did this a week ago and forgot to flash SuperSU. Messed up big time... Axon7tool gives the what() error, but people say that even if it successfully flashes the recovery, the stock recovery remains there.
So I need the inverse process... any idea how?
Click to expand...
Click to collapse
Perhaps this will help : https://forum.xda-developers.com/showpost.php?p=71444519&postcount=494
unplug usb when you give command to flash twrp recovery, otherwise it always reflashes stock recovery....
Hope that helps
Thanks for the reply! I'll have to figure out how to make axon7tool work now. Much appreciated
Dear raystef66!
I'm on Resurrection Remix now-2017G (it is 7.1.1 based).I would like to have a stock 7.1.1.Can i just do the steps in your post 1,without flash b10, just flash
7.1.1 stock bootstack, system and Super SU?Would it working solution, to go from Resurrection Remix to stock 7.1.1 on 2017g?And will be twrp still prsent after those steps?
Thanks in advance!
ValVK said:
Dear raystef66!
I'm on Resurrection Remix now-2017G (it is 7.1.1 based).I would like to have a stock 7.1.1.Can i just do the steps in your post 1,without flash b10, just flash
7.1.1 stock bootstack, system and Super SU?Would it working solution, to go from Resurrection Remix to stock 7.1.1 on 2017g?And will be twrp still prsent after those steps?
Thanks in advance!
Click to expand...
Click to collapse
IMO you have to flash b10 too. Would do no harm though as long as you don't fully wipe system to keep twrp. As long as you keep a backup of twrp you can always go back. In worst case you have to flash twrp again in edl axon7tool.
@ValVK I flashed B03, then B08, then B10, and THEN B01, like any normal update. That because I don't know if B10 is only an incremental update
But after you flash the stock system, remember to root! You'll lose TWRP otherwise
Thanks all for responces! If i will go that way-flash in Twrp b08, then b10 and then Nuga, what should i wipe first in Twrp-all inclusive System, or just Factory reset? And if i will go that way, should my Twrp still intakt? (I would like avoid to Flash Twrp again, seems bit risky for me).
I had the official bootloader unlock but it broke the com.android.phone process on 7.1.1.
They are working on getting it fixed and once fixed will make the root publicly avialble.
The official root works on b10 marshmallow and is very easy to install.
@ValVK o sorry, I only flashed B03 :silly:
You should flash B03 THEN update via the native sdcard update on mifavor
raystef66 said:
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device (and all of your apps and settings are the same)
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again ( to be sure ) - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
10. make TWRP backup when needed
EDIT : when you want to get rid of the bootscreen which states that you have an unlocked bootloader, follow this procedure (very easy )
https://forum.xda-developers.com/showpost.php?p=71444728&postcount=496
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
Click to expand...
Click to collapse
Hi, I am on the stock rom 7.0 nougat for the A2017G.
Can I just flash the leaked rom 7.1.1 for a2017g model??, I have no root, total stock.
Oliver Aa said:
Hi, I am on the stock rom 7.0 nougat for the A2017G.
Can I just flash the leaked rom 7.1.1 for a2017g model??, I have no root, total stock.
Click to expand...
Click to collapse
I suggest you wait for the 7.1.1 OTA update when you're not rooted etc.
I flashed through twrp the package made by tron1 for android 7.1.1 , the bootstack and supersu to make sure i have root install at the first boot but for some reason supersu framework gets deleted. I tried flashing supersu package multiple times and it gets deleted after boot up . How could i fix this ?
S0wL said:
I flashed through twrp the package made by tron1 for android 7.1.1 , the bootstack and supersu to make sure i have root install at the first boot but for some reason supersu framework gets deleted. I tried flashing supersu package multiple times and it gets deleted after boot up . How could i fix this ?
Click to expand...
Click to collapse
Did you follow my steps ? From which version did you come ? Were you already rooted....
Perhaps flash SU 2.79 (!) in edl mode and when it is resetting for a reboot, unplug your phone before it can reboot. You get a black screen. Just press Vol+/Power and when you see ZTE logo you release. Normaly you should/can enter TWRP.
But normaly my guide should work if you were rooted, BL unlocked and on stock ROM (B08 or earlier). I do not know which steps you already performed so it's just gessing.
What you guys think??
I want to know if I update my phone to this version, can I continue using xposed
Hello, can someone create TWRP files from the new B02 image?
Gesendet von meinem ZTE A2017G mit Tapatalk
@raystef66
I have a question:
Can step 8) be skipped? (flash 7.0=A2017GV1.1.0B01 bootstack and system, flash SU2.79).
Since in step 9) we will flash immediately 7.1.1B01=A2017GV1.2.0B01 bootstack and system, and flash SU2.79.
I guess step 8) is harmless, but not necessary. Is it true? Or are there other reasons for this?
Also maybe you could at end of this guide add a link to your another guide
https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
which continues the upgrade to 7.1.1B02=A2017GV1.2.0B02 keeping TWRP, unlock, fastboot and root?
Thank you.
dnlilas said:
@raystef66
I have a question:
Can step 8) be skipped? (flash 7.0=A2017GV1.1.0B01 bootstack and system, flash SU2.79).
Since in step 9) we will flash immediately 7.1.1B01=A2017GV1.2.0B01 bootstack and system, and flash SU2.79.
I guess step 8) is harmless, but not necessary. Is it true? Or are there other reasons for this?
Also maybe you could at end of this guide add a link to your another guide
https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
which continues the upgrade to 7.1.1B02=A2017GV1.2.0B02 keeping TWRP, unlock, fastboot and root?
Thank you.
Click to expand...
Click to collapse
IMO step 8 can not be skipped due to the fact you have to have 7.0 first. Could be wrong, but then again, it only last for a minute or so
I will ad the link to upgrade B01 to B02.
Thnx !
ps : did you get B02 with my method ? Pls post on thread if succeeded - thnx !
Hello! i have used the search tool to see if there is a custom recovery for my device but i am unable to find any. I found TB-X103F custom twrp but im unsure about trying it!.
I may be rather early as this tablet only recently came out.
Lenovo X 104F- 1 GB RAM
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
Care to share any links?
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
kpfx said:
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
Click to expand...
Click to collapse
I've been looking for one also and was gonna see about working on one
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
I can attest to this, I flashed the last Resurrection Remix Oreo GSI (12/21/18) and a (Magisk) rooted kernal I got from firmware (Lenovo MOTO Smart Assistant). And so far everything seems to be working fine.
So I also flashed resurrection remix pie gsi... it works as well... only thing is it doesn't come with gapps... and without twrp i can't flash a gapps package. The resurrection remix I used was the final oreo build... zt has gapps pre-installed... you have to register the device with google because it is not certified... but after that everything seem good. One thing to mention is both the oreo and pie builds are "go edition" so some features are missing because of that... one in particular I noticed is notification access for 3rd party apps... go edition devices don't have that feature
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
44Guest said:
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
Click to expand...
Click to collapse
Use Lenovo MOTO Smart Assistant to repair your tablet (you wont actually repair tablet, just using to get firmware)
Follow steps to get to download the firmware (it will save to ProgramData folder, its hidden folder... in widows anyway)
Take the boot image (boot.img) from firmware folder and transfer to storage on tablet
Instal magisk manager and use to patch the boot image you transfered from computer
Transfer patched boot image back to computer
Download the latest oreo gsi for resurrection remix or lineage
Use fastboot to unlock bootloader
Use fast boot to flash gsi
Use fastboot to flash patched boot image
Google anything you need help with...
I used the resurrection remix oreo also because there is a build that has gapps pre-installed... the pie version works but doesn't have gapps pre-installed and without twrp I couldn't find a way to install them
After tablet boots up install magisk manager and you will be rooted
You will need to register your device with google because it will not be certified... that was a pain to get done even though the process is pretty straight forward
So far only "issues" I have encountered are not actually issues they are due to the fact that the resurrection remix gsi is android "go edition" I haventr tried lineage because I like the customization options that resurrection remix offers
Here is the magisk patched boot image I made so you can skip that part...
https://www.mediafire.com/download/x4d3xp8w3e8bw3g
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
4niner4 said:
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
Click to expand...
Click to collapse
So you want all files on the computer at first...
When you unlock bootloader it will wipe the tablet.
Flash the the gsi image then the magisk patched boot image using fastboot (there are instructions on xda regarding flashining gsi... you have to wipe system before flashing)
After tablet reboots to resurrection remix move the magisk manager apk to the tablet and install it... open magisk manager and you should have magisk installed giving you root and so much more.
Before you attempt this make sure you familiarize yourself with all the steps... search google/xda.
Also... I will say this... I tried to just root the tablet first but it wouldn't boot after so I tried to fix it using the Lenove tool and it failed... flashing the resurrection remix gsi with the patched boot image saved me from a lot of headache and wasted time... I would prefer if it was not a "go edition" rom but its still better than stock.
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
4niner5 said:
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
Click to expand...
Click to collapse
Make sure you fastboot flash unlock and fastboot flash unlock_critical. Just look an here for the links for lineage gsi. It flashes just fine and is super easy. I have resurrection remix on my 104f. I'm trying to compile twrp for it right now but hard to do with kids lol also if you use the lenovo tool you can download the recovery files which has boot recovery and all that in it and you can use magisk to patch the boot.ing and then copy that to the Lenovo tool and replace the stock boot img then recover it and you now have a working patched boot.img. I went through the same thing
Any Luck?
Any luck with that twrp? I'm willing to test it out...
Would like to be able to use the resurrection remix pie rom with gapps. So I can hopefully give some helpful feedback... one warning I am an amateur at anything beyond using fastboot and some adb commands, but I can learn pretty quick if i have the time to spend...
Another warning I have a sub-par windows pc to work with (and its the wife's) it prob can't run Linux in VM.
Disable "go edition" in Resurrection Remix Oreo
Using root explorer...
Navigate to /system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Navigate to /sbin/.magisk/mirror/system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /sbin/.magisk/mirror/system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Reboot
This allowed me to set notification access again (its disabled in "go edition")
Hey guys, I'm trying to follow the steps in this thread to install Resurrection Remix Pie on the tablet using fastboot but whenever I try to flash a ROM to the system partition I get a (remote: size too large) error.. Does anyone know why this could be? I've tried using flags like -S, I've wiped the partitions and I don't know what else I can try. I have tried with Lineage, AOSiP and RR GSIs.
Thanks.
I cant get this to work.. What version of RR or Lineage OS works with tb-x104f?
up..................
I got the final version of rr oreo running fine... no luck with the latest rr pie unfortunately...
Anyone know if this is an A or AB device?
Note 8 V5 Bootloaders If Not Already On Safestrap Follow My EDL Pie Safestrap Method
Please Note This Is Not A Root Method For Oreo Or Pie. As Of Now There Is Still No Root Method For Oreo Or PieThis Takes Some Patience To Install
N8 SM-N955U/U1/W Install Instructions And Files
Download
SM_N950_DSF6_SYSTEM.rar Latest Build
Install Instructions Safestrap Method
Make Sure The Latest Samsung Drivers Are Installed. They Can Be Found Here
1. Copy ****_SYSTEM.img to your internal sdcard. Reboot to download mode and in BL slot in Odin flash Use The BL_ENG_BOOTLOADERS_SAFESTRAP_N950U_V5.tar.md5 and reboot to safestrap
2. In Safestrap choose install then choose select storage and select internal storage click ok then at bottom choose install image and choose ****_SYSTEM.img then select flash to system image then swype to flash
3. Now chose zip and flash Safestrap-4.10-B03-GREATQLTE-PIE.zip
4. To leave safestrap reboot to download mode
5. In odin load BL_N950USQU5****tar.md5 in BL slot and flash
To Enter And Exit Safestrap After Intitial Install
1. To enter safetrap flash the BL_ENG_BOOTLOADERS_SAFESTRAP_N950U_V5.tar.md5 in BL Slot in odin phone will boot too safestrap sometimes it may take a minute to do so
2. To leave safestrap reboot to bootloader or download still does not work so you still need to manually reboot to bootloader
3. Use modded Odin and load BL_N950USQU5****tar.md5 In BL Slot
Helpful Key Combos
Recovery Mode
Bixby + Volume Up + Power @ Same time
Download Mode
Bixby + Volume Down + Power @ Same time
Safe Mode
Phone Powered Off
Press and hold the Power key past the model name screen.
When “SAMSUNG” appears on the screen, release the Power key.
Immediately after releasing the Power key, press and hold the Volume down key.
Maintenance Mode
Press and hold the Power + Volume Down buttons for approximately 10
Bugs:
DO NOT USE ENCRYPTION
Safestrap rom slots do not work
Safestrap might not read larger than 64gig sd cards on some cards
Formating data in safestrap may cause reboot so make sure to format data very last thing
What Is Safestrap
Safestrap is a Bootstrap / Recovery for locked bootloader phones. Safestrap is now based on TWRP Recovery (a touch based recovery) and you can perform .zip installs, backups and restores here.
View attachment 4531040View attachment 4531041View attachment 4531042View attachment 4531043View attachment 4531044View attachment 4531045
Credits:
- @Raymonf for modified odin
- @afaneh92 for safestrap Main Thread Here Consider a donation to him he worked along time on this Donation Link
- @me2151 for finding this method
- @tytydraco for some instructions
- @mweinbach for some instructions
- @Craz Basics for xposed on non rooted
- @partcyborg for finding the root method!
- @elliwigy for being great help and original S8 root
- @rayan-refoua for boot animation
- @SamGuy2020 for testing S8 install method
Click to expand...
Click to collapse
View attachment Safestrap-4.10-B03-GREATQLTE-NOUGAT.zip Needed If running nougat rom
View attachment Safestrap-4.10-B03-GREATQLTE-PIE.zip Needed If running Pie rom
Main question I have is about the battery do we get %100 on the unrooted pie?
DroidisLINUX said:
Main question I have is about the battery do we get %100 on the unrooted pie?
Click to expand...
Click to collapse
Still 80% battery.
Sent from my Pixel 3 XL
DroidisLINUX said:
Main question I have is about the battery do we get %100 on the unrooted pie?
Click to expand...
Click to collapse
Yes
Sent using some kind of device I modified
Eudeferrer said:
Still 80% battery.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
80 percent is only on rooted nougat. Pie is unrooted and battery will charge to 100 percent
Sent using some kind of device I modified
jrkruse said:
80 percent is only on rooted nougat. Pie is unrooted and battery will charge to 100 percent
Sent using some kind of device I modified
Click to expand...
Click to collapse
Magisk just tweeted that the "world's first true system-as-root" was just created. Do you think that with this we could achieve root for Pie? Or would this not change anything?
Sent from my Pixel 3 XL
Eudeferrer said:
Magisk just tweeted that the "world's first true system-as-root" was just created. Do you think that with this we could achieve root for Pie? Or would this not change anything?
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
All that a and b partition stuff reefers to phones that were released with pie. Our phone is still old school no treble support.
Sent using some kind of device I modified
Would I have to flash every time i want to enter safestrap?
also if I were to want to revert to the rooted nougat ROM, do I have to follow all the steps on the rooting guide or could I just flash an image through safestrap?
purpleuser said:
also if I were to want to revert to the rooted nougat ROM, do I have to follow all the steps on the rooting guide or could I just flash an image through safestrap?
Click to expand...
Click to collapse
you can just flash image in safestrap and then flash the safestrap for nougat zip in post 2 (or its included in the new DSF6 build) after you flash the nougat system image in safestrap to get back to nougat safestrap. If you fail to flash the safestrap zip for nougat your phone will automatically boot to safestrap on every reboot on a nougat rom.
jrkruse said:
you can just flash image in safestrap and then flash the safestrap for nougat zip in post 2 (or its included in the new DSF6 build) after you flash the nougat system image in safestrap to get back to nougat safestrap. If you fail to flash the safestrap zip for nougat your phone will automatically boot to safestrap on every reboot on a nougat rom.
Click to expand...
Click to collapse
Thanks for answering my question. I'm new to all of this, so I appreciate the guidance.
Another question. Would I brick my phone if I tried to flash a ROM image with a v3 bootloader through safestrap?
purpleuser said:
Thanks for answering my question. I'm new to all of this, so I appreciate the guidance.
Another question. Would I brick my phone if I tried to flash a ROM image with a v3 bootloader through safestrap?
Click to expand...
Click to collapse
You can flash a system image from v3 firmware but must remain on v5 boot and recovery images and bootloaders and modems
Sent using some kind of device I modified
Nice this ROM just goes over the Nougat image with all my settings and apps intact. Even the pay apps are working (probably because no root). Now I just need to find a way to flash Viperaudio drivers then I'm all set.
jrkruse said:
You can flash a system image from v3 firmware but must remain on v5 boot and recovery images and bootloaders and modems
Sent using some kind of device I modified
Click to expand...
Click to collapse
Awesome. This is great. Thanks
Hey, is it alright to do an update for June Security Patch? It's changing my build number to N950USQS / N950UOYN - DSF3.
vman00 said:
Nice this ROM just goes over the Nougat image with all my settings and apps intact. Even the pay apps are working (probably because no root). Now I just need to find a way to flash Viperaudio drivers then I'm all set.
Click to expand...
Click to collapse
I've tried to flash a few different viper zips in safestrap to no avail. The driver would not load. I was told that root is needed to actually "load" the drivers, even if you install them via safestrap. I'm not sure this is true though because if it was, the viper app would ask for root privs, wouldn't it? Anyways, if you make any progress let me know I need that viper in my life.
BotsOne said:
I've tried to flash a few different viper zips in safestrap to no avail. The driver would not load. I was told that root is needed to actually "load" the drivers, even if you install them via safestrap. I'm not sure this is true though because if it was, the viper app would ask for root privs, wouldn't it? Anyways, if you make any progress let me know I need that viper in my life.
Click to expand...
Click to collapse
might as well wait for rootless
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
vman00 said:
might as well wait for rootless
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
Click to expand...
Click to collapse
You should be able to change the permissions for the files themselves with safestrap you can change file permissions if it allows us read write to system then you could try making an init script to load in on boot with rooted permissions to load the viperaudio like an init.d
Vipermod start service this is just off of the top of my head but I will look into more this weekend when I got some time to test out the new rom and safestrap
Viper will not work without root because it needs to execute a script at startup and no scripts will execute on a stock system. There were or maybe are rootless version but they still needed a permissive kernel to work
Sent using some kind of device I modified
Hi all from Noob member.
I am wanting to update my Redmi Note 4 Snapdragon from stock MIUI Global 11.0.2 as no OTA updates for a long time.
Having searched the forums I see a lot of guides are from 2017 so need up to date help.
I understand first step is to install unlock bootloader and install TWRP.
Q1 I need a recommended guide for 2021. I have found this but the advice is slightly different from that on the TWRP Redmi page e.g. regarding how to deal with DM Verity. These terms are all new to me and somewhat confusing.
Q2 Will I be able to backup the factory ROM in case it all goes wrong and I need to get it back to the current state?
Any other advice gratefully received.
Hi. I have recently installed LineageOS 18.1 on my Redmi Note 4 Global (Snapdragon) and have written a detailed guide for myself, in case I would need to do it again. At first, I had problems with fingerprint not working even though I have installed everything correctly. I have fixed that issue with the help of LOS 18.1 main tester, and I have also written myself a guide for that fix.
If you would like to install LineageOS on your mido, I could share the guide with you.
Regarding your question 2, you can always make a backup of your current ROM before installing customs ROMs, and usually backups work fine, although I do not have any experience with that yet, so your mileage may vary.
Also, if your device is not bricked after tinkering with custom ROMS, you can always use latest fastboot MIUI ROM for your device, and flash it with official Mi Flash tool to get back to MIUI.
First step, as always, is to unlock your bootloader with Mi Unlock tool, which you can find here:
Apply for permissions to unlock Mi devices
en.miui.com
Read this FAQ as well:
https://c.mi.com/thread-2262302-1-0.html
By the way, bootloader on my mido was unlocked instantly with that tool, I did not have to wait at all.
Hi Rigadelt
Many thanks for the reply. I would indeed be interested in seeing your guide if it is not too much trouble.
Everything working correctly including the fingerprint reader would be a must for me. Glad to hear you fixed it.
Good to know you can make backups - I'm assuming this is via TWRP?
Appreciate the tip about fastboot MIUI ROMs - I think I have found them before on the official site when I searched a year or so ago about flashing a new ROM. It seems things are a bit more developed now.
Thanks for getting me pointed in the right direction!
Grump
No worries, just a disclaimer - I am not responsible if you somehow break your phone while following this guide.
I am also a noob on custom ROMs, but I have done the exact same steps, and my phone appears to be working fine, so you should be all right too. After all, these steps are almost identical to all custom ROMs installation instructions, the difference is that this time you will need to use OrangeFox recovery instead, because LOS 18.1 works better with it.
I have written this guide while following OrangeFox recovery guides, and getting help from Redmi Note 4 users on Telegram groups.
First install ADB + Fastboot in your PC (I assume you use Windows 10).
Download these files:
SDK platform tools: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Google USB Driver: https://dl.google.com/android/repository/usb_driver_r13-windows.zip
I am not sure if Google USB Driver is necessary, but install it anyway because I had it installed too.
For installation instructions, use the attached "ADB Fastboot installation.txt" file.
You can check this video for visual guide as well:
After that, unlock your bootloader with Mi Unlock tool.
Confirm that bootloader is unlocked on your Redmi Note 4 via ADB + Fastboot, following this article (go to PC section, ignore Android phone):
How to check if bootloader is unlocked or locked on Android
How to check if bootloader is unlocked or locked on Android
www.addictivetips.com
At this point, if everything is working fine and your phone is indeed unlocked, I recommend backing up important data (photos, videos, documents, SD Card, etc.) from your phone to PC, Cloud or other safe storage.
Next, download these files and put them in your SD Card or internal phone storage (for example, Download folder). I recommend formatting SD Card and putting the files on it, but you can use internal storage as well.
OrangeFox recovery (R11.0) for mido:
https://dl.orangefox.download/5f14b74f26d98d90b476a532
Latest mido firmware (you will probably not need it, but have it just in case): https://xiaomifirmwareupdater.com/d...4XGlobal_V11.0.2.0.NCFMIXM_83170d3e3a_7.0.zip
LineageOS 17.1 with 4.9 kernel (you will need to install it first):
https://github.com/zeelog/OTA/releases/download/28.0/lineage-17.1-20201215-UNOFFICIAL-4.9-mido.zip
LineageOS 18.1:
https://github.com/zeelog/OTA/releases/download/31.0/lineage-18.1-20210107-UNOFFICIAL-mido.zip
GApps (FlameGApps "basic" is recommended for LOS 18.1):
https://sourceforge.net/projects/flamegapps/files/arm64/android-11/BETA/2020-12-29
I will continue the guide in the next message.
Now, make sure that your phone is charged and has more than 80% battery (just to be safe).
Also note that after the following step, you won't be able to boot to MIUI anymore, so make sure you have made a backup of your files.
Install OrangeFox recovery using this guide:
Installing OrangeFox Recovery
wiki.orangefox.tech
Then, follow the instructions written in the attached "Readme - LOS 17.1 and 18.1 installation" text file.
If you installed LOS 18.1 successfully but your fingerprint does not work anymore (although it worked fine on MIUI and LOS 17.1), then you will need to go back to latest mido MIUI ROM with Mi Flash tool and then follow the instructions in "Fingerprint fix and MIUI errors" text file.
Good luck. If you have any questions, I recommend creating a Telegram account and joining discussions on Redmi Note 4/4x groups.
Thanks for this !!!
I was going to ask about the orangefox option, as some guides I have found suggest this.
I had looked on the LineageOS page and see their listed version for Redmi note 4 is 16.0, so looks like you are leading the way with your method.
I'm going to take my time and digest all this excellent info you have provided.
Great tip on the telegram group !
the_real_grumpazoid said:
Thanks for this !!!
I was going to ask about the orangefox option, as some guides I have found suggest this.
I had looked on the LineageOS page and see their listed version for Redmi note 4 is 16.0, so looks like you are leading the way with your method.
I'm going to take my time and digest all this excellent info you have provided.
Great tip on the telegram group !
Click to expand...
Click to collapse
You're welcome.
Just wanted to let you know that the main tester of LineageOS 18.1 as of recently recommends using FlameGApps "basic" instead of NikGapps. Apparently some users experienced failed OTA updates (bootloops) due to problems associated with NikGapps.
Download it here:
FlameGApps - Browse /arm64/android-11/BETA/2020-12-29 at SourceForge.net
A Google Apps installer package for devices running on arm64 platform
sourceforge.net
Also, I have updated the installation instructions a bit, so I recommend re-downloading both attached text files above.
Some new info regarding LOS 18.1 updating:
Dirty flash method
1) Download the latest ROM udpate zip file and save it in phone's internal storage or SD Card.
2) Turn off your phone and reboot to recovery.
3) Go to Wipe and wipe:
Dalvik / ART Cache, Cache, System, Vendor
-- DO NOT WIPE "DATA" or "INTERNAL STORAGE" --
4) Ignore "Reboot System" option.
5) Go back to OrangeFox recovery, select latest ROM Update zip and flash it.
6) Ignore "Wipe Caches" and "Reboot System" options.
7) Go back to OrangeFox recovery, select GApps zip and flash it.
8) After flashing, tap "Wipe Caches". Wait for it to wipe and then ignore "Reboot System" option.
9) Go back to OrangeFox recovery, go to Menu, tap on Reboot, then Reboot to Recovery.
10) When the phone successfully reboots to OrangeFox recovery, go to recovery Menu, then Reboot, and Reboot to System.
OTA Update
1) Do not change anything in OrangeFox recovery OTA update options, leave all settings default (OTA disabled). To check if OTA is disabled in the recovery, do this:
1a) Turn off your phone and boot to OrangeFox recovery.
1b) Go to OrangeFox recovery Menu, tap on the Gear symbol in the upper right corner and select OTA & ROM.
1c) Make sure that OTA is disabled (enable OTA is greyed out)
1d) Go back to OrangeFox recovery Menu, then Reboot, and select Reboot to System.
2) Go to Settings, System, Advanced, Updater.
3) Tap on three dots in the upper right corner and select Preferences.
Preferences must be set like this:
* Auto updates check: Once a week
* Delete updates when installed: OFF
* Mobile data warning: ON
* Update recovery: OFF
If you can't disable "Update recovery" option in Updater preferences, then do not worry and leave it enabled. The stock recovery won't be updated (replaced) with LineageOS recovery even if this setting is enabled.
***--- OTA PROBLEMS ---***
In some (rare) cases OTA update might fail (usually due to GApps issues) causing your phone to bootloop, i.e. the phone gets stuck at LineageOS logo loading screen for a couple of minutes, and then reboots to recovery.
To solve this problem you need to install the update manually using Dirty flash method.
The downloaded OTA update file is in this location (in recovery):
root/data/LineageOS Update folder
You will have updated ROM without loosing any data.
Also, you can change GApps from NikGApps to FlameGApps or other GApps every time when you are using Dirty flash method to update your ROM.