Related
As most of us know only certain variants of the G6 is allowed by LG I to be unlocked and then that allows us to have some fun, I've posted most links to important threads that I feel you want to view.
Any questions then just find the help thread in the stickies section.
Here's some links to what most of you will want to know.......
Guide to unlock bootloader:-
https://forum.xda-developers.com/lg-g6/how-to/official-lg-g6-bootloader-unlock-t3614719
Twrp H870 official guide and install:-
https://forum.xda-developers.com/showthread.php?t=3627595
[ROM][US997][Stock] LG-US997 13A ROM
http://forum.xda-developers.com/showthread.php?t=3635756
[ROM][US997][Stock] LG-US997 13A ROM
[ROM][H870][Stock] OPEN EU LG-H870 10L ROM twrp flashable rom
http://forum.xda-developers.com/showthread.php?t=3633452
[ROM][7.1.2_r24][H870][UNOFFICIAL][Stable] Resurrection Remix 5.8.3 [19.07.2017]
https://forum.xda-developers.com/lg-g6/development/rom-resurrection-remix-5-8-3-t3639293
Fulmics Rom for both H870+US997
https://forum.xda-developers.com/lg-g6/development/rom-25-07-fulmics-rom-1-0-v10n-tweaks-t3642043
Official lineage OS
https://forum.xda-developers.com/lg-g6/development/7-1-2r24-rom-lineageos-t3657486
Unofficial AOKP Rom
https://forum.xda-developers.com/lg-g6/development/rom-aokp-t3679189
AquariOS Rom
https://forum.xda-developers.com/lg-g6/development/rom-aquarios-7-1-2-oms-t3639363
AOSPA Paranoid Android (unofficial)
https://forum.xda-developers.com/lg-g6/development/unofficial-aospa-paranoid-android-7-2-3-t3667399
Unofficial Dirty Unicorns
https://forum.xda-developers.com/lg-g6/development/rom-dirty-unicorns-11-6-t3659943
CrDroid unofficial
https://forum.xda-developers.com/lg-g6/development/rom-dirty-unicorns-11-6-t3659943
[RECOVERY] TWRP for LG G6 US997 (unofficial)
http://forum.xda-developers.com/sho...
[RECOVERY] TWRP for LG G6 US997 (unofficial)
[MOD] KALI NETHUNTER [7.0-7.1.2][Unoffcial][H870]
http://forum.xda-developers.com/sho...] KALI NETHUNTER [7.0-7.1.2][Unoffcial][H870]
[MOD] Dual speaker mod (LG G6) (all variants)
http://forum.xda-developers.com/sho...[MOD] Dual speaker mod (LG G6) (all variants)
Root, use either magisk or SuperSU V 2.82
[BETA][2017.06.09] SuperSU v2.82 SR1
http://forum.xda-developers.com/showthread.php?t=2868133
[2017.7.11] Magisk v13.1 - Root & Universal Systemless Interface [Android 5.0+]
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hi, as you are all aware some of us are lucky enough to unlock our bootloaders and flash custom firmwares/twrp, however many guides tell us how to do that but none tell you how to go back total stock+locked.
I've personally seen a few bricked phones as not doing it correctly or flashing on a locked bootloader which can cause BIG problems, here I'll help with a small but useful guide and simple steps I made to return stock.
**PLEASE NOTE THIS GUIDE IS FOR H870/US997**
I'm not 100% certain on how to revert changes on H872 but once I do I will add.
Now for this your going to need
1) stock unrooted zip for twrp
2) twrp installed
3) a pc
4) LG up/uppercut or bridge
5)stock recovery image
6) about 25-30 mins spare time
Step 1)Firstly your going to want to download stock zip from which can be found here
https://forum-xda--developers-com.c...ment/rom-op-il-lg-h870-11d-rom-t3711191/page1
, I recommendcyou copy to an external SD card for this.
Step 2) Next download stock recovery IMG from here
http://downloads.codefi.re/autoprime/LG/LG_G6/H870/H87010f
( same I used) and again copy to external SD card.
Step 3) Once you've done that reboot into twrp, then perform a factory reset and install the stock zip. Once that's installed **DO NOT INSTALL ANY ROOT ** reboot your device, skip though the setup and go right to settings, and click on build number to open developer settings and check to make sure ENABLE OEM UNLOCK is selected. If it is then reboot back to twrp via button combo.
Step 4) Once in twrp select install and select image instead of zip, then find and install stock recovery image and reboot recovery, now you should have stock recovery so it should perform a factory reset, if it does then reboot again ( it's a good way to make sure everything is ok) and if it boots fine then connect to PC,( you can if you wish skip step 3 and go right to step 4)
Step 5) Open up your lgup/uppercut/bridge (preferred choice), if LG up/uppercut then you need the latest kdz file downloaded to your pc, if bridge it detects your phone and should inform if it needs an update, if it does then allow the update to latest.
If not and your device is on and fully working then ONLY NOW can you use adb to reboot fastboot and enter "fastboot OEM lock", doing so will once again erase your device but now it's full stock and locked like you never touched it.
1 note I must add is NEVER EVER flash anything via fastboot is your device is locked as it will brick your phone. Your greeted with either of the screens below
Reserved
Sent from my LG-h870 using XDA-Developers Legacy app
Reserved 2
Sent from my LG-h870 using XDA-Developers Legacy app
new add
[ROM][H870][Stock] OPEN EU LG-H870 11G ROM
Update 1, most used and updated ROMs here
https://g6-community.org/
Good, guides for newbie are always a good thing here, just wanted to report that flashing stock recovery it's a useless passage if you flash the kdz trough lgup because it will overwrite TWRP anyway, another useless passage (only if already coming from stock firmware or rom based on it) is to flash a stock rom from twrp, LGUp does all the necessary after
Thanks for your efforts, as I said before this is really a good idea and imho it'll prevent useless threads and bricks =)
jimbomodder said:
Step 2) Next download stock recovery IMG from here
http://downloads.codefi.re/autoprime/LG/LG_G6/H870/H87010f
( same I used) and again copy to external SD card.
Click to expand...
Click to collapse
That'd be the "recovery.img 23.6 MB May-30-17", right?
Great guides, thank you!
DrNO[PL said:
;80381567]That'd be the "recovery.img 23.6 MB May-30-17", right?
Great guides, thank you!
Click to expand...
Click to collapse
Yeah, should not matter about date
[TREBLE] Project Treble for LEECO MAX 2 (x2)
PHP:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
### What is Treble? ###
https://android-developers.googleblog.com/2017/05/here-comes-treble-modular-base-for.html?m=1
I'll keep the technical details about treble away from this thread as it has been covered by xda already.
If you want to know more about that visit here : https://source.android.com/devices/architecture/
Treble is everywhere, so why shouldn't x2 join it?
I'm proud to announce that Le Max2 will now fully support project treble and you can flash Generic System Images (GSI) and even Android P. Exciting right ?
You just need to follow the instructions mentioned and you're good to go.
## How we did it? ##
You might be wondering how I managed to get treble support...
NO, I didn't repartition the phone so you shouldn't worry about bricking the phone unless the directions were not followed properly.
There is an empty and unformatted partition in the phone called "last_parti" with a size of <589mb> and I converted that to our vendor partition, similar to how OnePlus devices were able to achieve teble support without the need to repartition.
You may doubt that that you will still be able to flash stock eui rom, but yes u can and we have tested it. If you encounter any error no 7 during eui flashing? Please switch to a non-treble build of TWRP or just delete block checking in update-script.
If you have any difficulties? You may join our telegram group for help :
https://t.me/joinchat/HFzBDlHXN-52-GZBg7725w
## Things you'll need to download (instructions are below):
New method :
1) Treble supported TWRP : New one by @GalaticStryder https://drive.google.com/open?id=1mx-uGryLXiIR7fDSDL4iBPdXhd7qLHjQ
2) Treble supported builds can be found here : https://www.androidfilehost.com/?fid=5862345805528055916
Previous method :
1) Partition creator zip : https://www.androidfilehost.com/?fid=5862345805528055960
2) Treble supported TWRP : https://www.androidfilehost.com/?fid=5862345805528055961
3) Treble supported builds can be found here : https://www.androidfilehost.com/?fid=5862345805528055916
Let's trebelize your x2 shall we?
**Important: Instructions are absolutly clear, so please carefully follow the steps as written below. I shall not be held responsible for any bricked devices. You do this on your own risk.
New method :
1) Flash the Treble supported TWRP. Again there are multiple ways to flash TWRP like
Use TWRP and flash the new recovery as an image in the recovery partition.
Use fastboot on the computer to flash the recovery image.
If you have root access then you can use an app like Flashify to flash the recovery.
2) Reboot to recovery to ensure the treble version is launched.
3) In the "Advanced" menu please click and swipe on "Treblelize"
4) Try to wipe vendor partition. If Treblelize worked? It should wipe without errors.
Optionally, you can also try to mount Vendor partition to see if it mounts without errors too.
4) After completing 1-4 your device will have vendor partition but it won't be ready to flash GSIs. For being able to do it goto step
5) Wipe system, cache, dalvik cache and data.
6) Flash the AEX Treble ROM which you downloaded earlier.
Previous Method :
1)Flash the Treble supported TWRP. Again there are multiple ways to flash TWRP like
Use TWRP and flash the new recovery as an image in the recovery partition.
Use fastboot on the computer to flash the recovery image.
If you have root access then you can use an app like Flashify to flash the recovery.
2) Reboot to recovery once flashed. (Even if u flashed through twrp ,you should reboot to recovery again)
3) Flash the partition creator zip now. After flashing it it might show an error about cannot mount /vendor, ignore it and go on to
the next step.
4) Click wipe on TWRP homepage, select vendor and uncheck all other partitions and swipe to wipe. Nice you have successfully
created vendor partition.
optional. You can check if you are able to mount /vendor partition from the recovery.
5) After completing 1-4 your device will have vendor partition but it won't be ready to flash GSIs. For being able to do it goto step
6) Wipe system, cache, dalvik cache and data.
7) Flash the AEX Treble ROM which you downloaded earlier.
Bingo! You have successfully trebelized your x2!
Time for some DO NOTs
1) NEVER wipe /vendor. If you do that your device won't work with any GSI. (u should wipe vendor only if u flash non treble rom )In case you accidentally wiped it you can flash AEX Treble rom to get it back. I might provide a vendor.img but don't think like doing it right now.
2) NEVER install A/B GSIs. Our device is treble enabled but doesn't have an A/B partition structure. Le Max2 support A only GSIs.
Instructions for flashing GSI of any Rom
1) Download a GSI from here : https://forum.xda-developers.com/project-treble/trebleenabled-device-development
2) If it is in a zip archive, then please unpack it.
3) You can find instructions here : https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
and reboot
Want to try more awesome things like installing Android P?
Instructions for flashing Android P GSI :
Complete credit for P image goes to : @erfanoabdi
Xda link for P GSI : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/rom-android-p-developer-preview-t3816659
Steps:
1) Download link for P gsi (DP4): https://androidfilehost.com/?w=files&flid=279295
2) Wipe all Paritions except : vendor, internal storage
3) Install P system image to system
4) Mount vendor in TWRP
5) Flash POST-sGSI zips from 1 to 3 in priority
6) Then flash my sensor fix zip here : https://drive.google.com/open?id=11l4p6NxwixMSQlTLhLM_8wuXpvmrNpJq
and reboot
Volte Fix for P : https://drive.google.com/file/d/1h-2qTwhUidU9gDBFzj86RMfZn-vwLOnG/view#
BUGS IN ANDROID P GSI
VOLTE-its fixed
U tell me
Ok, all the best to you!
It is not easy to make complete treble with Zero Bugs
and we tried our best in making that.
I want to include all the contributers so the list is quite large.
Credits and contributors :
@shivatejapeddi (yeah I myself worked very hard to achieve Treble for x2)
@davidevinavil (literally helped me in creating partition and helped in solving crucial bugs )
@ThE_MarD (our official lineage contributer and helped me in solving some bugs)
@Chityanj (helped me with server and testing)
@prajjwal.laad (tester)
@Abhishek4587Kumar (tester)
@yaser59527 (tester)
@Rk585(dunno)
@GalaticStryder (for his newer and easier method to "Treblelize" x2)
Please let us know if we missed anyone.
Donations :
We worked very hard for fixing things and making things work, and I finised all my free google credits and am now using a paid legacy server for building roms.
Want to donate me ?
You can Here : https://www.paypal.me/shivatejapeddi
XDA:DevDB Information
[TREBLE] Project Treble for LEECO MAX 2 (x2) (Complete), Tool/Utility for the LeEco Le Max 2
Contributors
shivatejapeddi, ThE_MarD, Chityanj
Source Code: https://github.com/Chityanj/treble_devicetree
Version Information
Status: Stable
Current Stable Version: 8.1.0
Stable Release Date: 2018-07-23
Created 2018-07-22
Last Updated 2018-09-01
reserved
.Guys If you have any problem or confusion ask us in telegram group or XDA before proceeding
.
Congratulations! Thanks everyone to work in this project!..
Great work guys.
good!
Wow! Impressive stuff guys! How is the P GSI? Working well?
****! All of you are incredible, thanks a mil for this hard work.
I have no words
Congrats to all devs involved
I am unable to understand anything. So dumb.
Pro3 users come to congratulate. How do I admire it! With the same CPU, zl1 can't use Android P.
It's a new way of life Thank you all.
This really works nice, and very easy process,. I am running the AEX treble ROM at the moment, but tried the P gsi for a while - it booted up OK and runs, looks nice, but has a message on boot saying there is an error with the device, and has a notification that the P system is updating that never seems to complete and so you can't log in to google account or complete phone set up.
kanagawaben said:
This really works nice, and very easy process,. I am running the AEX treble ROM at the moment, but tried the P gsi for a while - it booted up OK and runs, looks nice, but has a message on boot saying there is an error with the device, and has a notification that the P system is updating that never seems to complete and so you can't log in to google account or complete phone set up.
Click to expand...
Click to collapse
Did you flash post GSI zips for P?
prajjwal.laad said:
Did you flash post GSI zips for P?
Click to expand...
Click to collapse
Yes, the three of them
kanagawaben said:
Yes, the three of them
Click to expand...
Click to collapse
Ahh. Then it's typical GSI behaviour. Maybe a final version will be more stable.
Thanks to all of the developers for bringing the much awaited treble support in our device.
kanagawaben said:
This really works nice, and very easy process,. I am running the AEX treble ROM at the moment, but tried the P gsi for a while - it booted up OK and runs, looks nice, but has a message on boot saying there is an error with the device, and has a notification that the P system is updating that never seems to complete and so you can't log in to google account or complete phone set up.
Click to expand...
Click to collapse
U should install google play services app link is there in that android p gsi XDA ,download and install problem solved
Crystal-L said:
Pro3 users come to congratulate. How do I admire it! With the same CPU, zl1 can't use Android P.
Click to expand...
Click to collapse
Hi don't worry, pro 3 will get very soon, devs working on it,
shivatejapeddi said:
U should install google play services app link is there in that android p gsi XDA ,download and install problem solved
Click to expand...
Click to collapse
Should have noticed that link earlier when i first tried. many thanks!
just wanted to add i got FC while restoring from the cloud on my google account, i think it was called data transfer tool, i had click on the 'i' to bring up the service/app and then give it storage permissions to continue. after that everything back and even my apps are now updating from the play store.:good:
edit 2: also for those needing usb connectivity after for whatever reason you can enable by going to developer options and changing default usb configuration to file transfer. learning do and donts as i go here as well lol
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.
Hi. When I first installed LOS 18.1 I had problems with fingerprint not working, so I have written a detailed guide how to fix it. 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 we use OrangeFox recovery instead of TWRP, because LOS 18.1 seems to work better with it.
NOTE:
When I used this method myself, I went back to latest MIUI ROM. I don't know if it is necessary, but I think everything should work fine without reverting to MIUI. If you would like to try fixing it without installing MIUI ROM, then go to the first reply below for a simplified guide. Nevertheless, I recommend reading the full guide anyway, just to get a better understanding of what steps you will have to do.
Also, some steps can be skipped because probably many of you have already done them when you were installing LOS or other custom ROMs. I have only tested this fix on LOS 18.1 but it might work on other custom ROMs too, I think.
I've written this guide while following OrangeFox recovery guides, and getting help from Redmi Note 4 users on Telegram groups.
FULL GUIDE (INCLUDES GOING BACK TO MIUI):
1. 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:
At this point I recommend backing up important data (photos, videos, documents, SD Card, etc.) from your phone to PC, Cloud or other safe storage.
2. You will need to go back to latest MIUI ROM. Use this page for instructions: https://c.mi.com/oc/miuidownload/detail?guide=2
If your Mido is global, then download "Redmi Note 4X Latest Global Stable Version Fastboot File Download" from (STEP 2).
VERY IMPORTANT! When flashing MIUI, make sure you select "Clean all" option. DO NOT select "Clean all and lock" (STEP 5).
3. After successful flashing, boot into MIUI. You may encounter this error when booting up MIUI 11: "Find device storage corrupted. Your device is unsafe now." This error also means that Wi-Fi and Bluetooth will not work. Don't worry, this will be fixed.
4. Next, download these files and put them in your SD Card (for example, Download folder).
(note: some zip file names written in this step will be outdated because Mido is still maintained - always make sure to check, download and use latest updated files).
OrangeFox recovery (R11.0) for mido:
https://dl.orangefox.download/5f14b74f26d98d90b476a532
Latest mido firmware:
https://xiaomifirmwareupdater.com/d...4XGlobal_V11.0.2.0.NCFMIXM_83170d3e3a_7.0.zip
LineageOS 17.1 with 3.18 kernel (you will need to install it first):
https://github.com/zeelog/OTA/releases/download/27.0/lineage-17.1-20201214-UNOFFICIAL-3.18-mido.zip
LineageOS 18.1:
https://github.com/zeelog/OTA/releases/download/41.0/lineage-18.1-20210417-UNOFFICIAL-mido.zip
GApps - "MindTheGapps arm64" was recommended by LOS Team for LOS 18.1 when I wrote this guide (before installing ask the ROM maintainer or users if this is still the recommended version of GApps):
MindTheGapps-11.0.0-arm64-20210412_124247.zip | by Alessandro Astone for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Also don't forget to download "persist.img" file attached below.
5. 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
6. Now, follow the instructions written in the attached "Fingerprint fix and MIUI errors" text file. (note: some zip file names in step 3 of this text file will be outdated because Mido is still maintained - always make sure to check, download and use latest updated files)
7. Finally, follow the instructions written in the attached "Readme - LOS 17.1 and 18.1 installation" text file, you should start from step 4. (note: some zip file names in step 1 of this text file will be outdated because Mido is still maintained - always make sure to check, download and use latest updated files)
Good luck!
One user reported that he successfully fixed the fingerprint issue on LOS 18.1 using this guide without going back to MIUI.
When I was fixing this fingerprint problem myself, I went back to the latest MIUI ROM. I did not test this method to see if it works without installing MIUI, but it looks like it should work just fine. In case you want to try fixing it without going back to MIUI, do this:
SIMPLIFIED GUIDE (WITHOUT GOING BACK TO MIUI):
* Back up important data (photos, videos, documents, SD Card, etc.) from your phone to PC, Cloud or other safe storage.
* Make sure that you have OrangeFox recovery installed, if not - install it.
* Download all the files mentioned in the step 4 of my initial post of this thread and put them on your SD Card. (check if there are any updated files before downloading, like newer ROM update, etc.)
* Download attached "Fingerprint fix and MIUI errors" text file, "persist.img" file and "Readme - LOS 17.1 and 18.1 installation" text file.
* Follow the "Fingerprint fix and MIUI errors" text file guide starting from step 8.
* Follow the "Readme - LOS 17.1 and 18.1 installation" text file guide, starting from step 4. I advise not to skip steps 17-18, although I'm not sure if installing latest Mido firmware is necessary at this point. But I think you should install it, just in case.
Good luck!
Cheers for all your efforts, @Rigadelt !
I'm trying your guide, as I can't get my fingerprint working in LOS18.1, although it works just fine in LOS17.1 ...
Can I ask you:
1) what for are your steps 10+11 & 23+24 in your "Readme - LOS 17.1 and 18.1 installation.txt" ?
2) at what point/step have you encrypted your phone?
Cheers! raimerik
Hi, @raimerik
1) I was advised by the Mido Telegram group users that Rebooting to recovery after ROM or GApps installation ensures that there is a lesser chance of errors during the finalizing of the ROM installation. I'm not sure if that is true, but it shouldn't hurt doing it this way either.
2) I did not encrypt my Mido, so I can't answer this question. You can find info in this post: https://forum.xda-developers.com/t/...-mido-vanilla-by-zeelog.4186179/post-83861307
What I would try to do:
* I would follow the "Readme - LOS 17.1 and 18.1 installation.txt" guide and install LOS 18.1 ROM without GApps (step 19 is the last step).
* After 18.1 ROM flashing, I would tap on "Wipe Caches" and then reboot to recovery.
* After the phone successfully reboots to OrangeFox recovery, I would then follow the Encryption guide written in the post I linked.
* After Encryption -> Dirty flash of LOS 18.1 ROM -> GApps installation process, I would reboot to recovery once again, and then try to boot the phone and see if everything works.
If I'm not mistaken, @manizuwo has fixed the fingerprint problem and encrypted his Mido using this guide, so you could ask him for advice.
Good luck! I also encourage you to share the results and info with other users here or in the main LineageOS 18.1 thread.
Rigadelt said:
* After 18.1 ROM flashing, I would tap on "Wipe Caches" and then reboot to recovery.
* After the phone successfully reboots to OrangeFox recovery, I would then follow the Encryption guide written in the post I linked.
* After Encryption -> Dirty flash of LOS 18.1 ROM -> GApps installation process, I would reboot to recovery once again, and then try to boot the phone and see if everything works.
Click to expand...
Click to collapse
Hi @Rigadelt - two minds thinking/tinkering alike!
I had updated and booted the 18.1, encrypted, went to recovery, dirty flashed the 18.1 and the gApps, wiped caches and rebooted.
Then I set up security pattern and fingerprint, which still does ONLY work if you activate SECURESTART which is an annoying bug, which the 18.1-thread-manager does not seem to understand...
(In Zeelog's 17.1 with 4.9-Kernel the fingerprint worked WITHOUT SecureStart...)
So, this is the first time I'm installing a custom rom and I was following along with this guy:
(I found the xda steps to be too confusing to follow) and everything was going just fine until around the 5.20 min mark where after flashing TWERP on the device through Odin I was supposed to press the volume - & the power key to restart the device and as soon as the device went black I was supposed to then press volume + & the power key which I did but then I got this: (attachment)
(btw, even when I don't press the volume + & power key afterwards I get the same result)
Can this still be fixed or have I bricked my device?
Hi @Winter413
I found a wonderful description on the installation of TWRP here .... maybe it's easier to follow though it's for the 8.
Just read the whole story .... your troubles while installing TWRP are not at all new.
It's a kind of trick which you learn as soon as you want to root your phone, or want a good user friendly recovery backup app.
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Hope it might be of help ....
Nice Sunday for you !
Here on the forum you will be able to meet all the specialists you need.
[RECOVERY] [OFFICIAL] TWRP 3.6.x for Galaxy A10 Exynos series [SM-A105] [4 January 2022]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Hi @xabu
First I'd like to greatly apologise you for answering so late. I did not mean to be rude I just didn't want to reply with "ok, I'll be working on it than" & I actually wanted to get something done first. I decided to do things that way becouse I thought that I'll find some time to do this rather soon however unexpected things happened that kept me from doing it but now I have some time & have done something in this regard so enough of my excuses let's get to what I did & what I want to ask you about:
So first I went onto the s8 thread you suggested & I flashed vbmeta_disabled & to my suprise when I restarted again & pressed volume up + power it actually booted into TWRP "and relief washed over me in an awesome wave" but then I went on to get lineage os on it and it doesn't show up in TWRP. I have also gotten some other stuff (magisk & a few files from NanoDroid) & those show up just fine. I got the file from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/
& the link I got from this thread: https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/
& as far as I'm concerned that is the only thread about lineage os on this phone on xda so that doesn't work I guess.
I have also tried this: http://www.mediafire.com/file/4w6vaq4lu2tbjfj/lineage-17.0-20200110-UNOFFICIAL.zip/file
& this: https://mega.nz/file/gw4QTYSS#IqqswGusWIW5l10LyvSfmtVUoE4gqn6_g6jywH96Z5Q
& got this:
(I've done these sequentially but I hope that doesn't make any functional difference however one important thing is the first one goes 'till the first "done" and the second one is the rest. You surely could figure that out by yourself but I wrote this just for clarity's sake.)
P.S. I know that both of the error messages I got seem to refer in one way or another to the fact that I'm not using an sd card for this operation, however as far as I'm concerned it should also be possible to install lineage os to the internal storage of the phone & that is what I want to achieve with this.
P.S. 2
I forgot to mention that I obviously wiped everything properly before trying to install lineage os so that's not the problem.
Hi Winter ,
it's important to check if you found the right version of TWRP:
Samsung Galaxy A10
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
every other version might get you in trouble.
And then: there is still no official LineageOS for the A10 (this gives problems too)
[ROM] [GSI] [GUIDE] Lineage os A10 A105F
A guide for how to install Lineage OS [ GSI ] on Samsung A10 A105F Notes / Warning! Use at your own risk, I’m not responsible for bricking your device. Make sure to backup your important data before everything. here is a summary of the steps I...
forum.xda-developers.com
should be the place to be, though there is not too much activity there ...
but look at this thread too:
Samsung Galaxy A10 ROMs, Kernels, Recoveries, & Ot
Improve your Samsung Galaxy A10's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
with many good ideas.
Whatever:
I learned that LineageOS should be installed before other additions like Magisk and G-apps. Do this from internal storage and not from an external sd-card.
In TWRP we always make a Zip queue before installing but always starting with the OS or ROM.
You should be successful now you experienced how to install TWRP.
Always check for the right version or ask in the threads.
Thanks for coming back to me though I just wanted to help you
with installing TWRP and I don't have a A10 at my disposal.
Sincerely @xabu
Ps: I saw that you had courage enough to experiment. Be careful but go for it.
Hi @xabu
So as I mention I made it work by flashing this file through odin while in dowload mode & then restarting & pressing the volume up + power buttons which was supposed to take me to twrp & it did & twrp for me seems to be working just fine so I'm a little hesitant to try & install some different version of it but if you think that's the issue than I will try installing those other versions.
As soon as you are in TWRP and it functions fine, then just look to it's version and go to the link which I gave you for the newest version of TWRP for the A10.
"
If you intend to root your (a10) device, be advised that Magisk will be installed to the recovery partition, not the usual boot partition. Both TWRP and Magisk-rooted Android boot using the recovery kernel, with the device's hardware keys used to choose between TWRP and Android at boot time.
You are therefore strongly advised to first root your device with Magisk and then pre-root a TWRP image before flashing it to recovery. The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP. Furthermore, prior rooting of the device with Magisk carries the significant advantage of disabling various device protection mechanisms that you will otherwise need to take care of manually."
In this website the instructions about flashing TWRP to your device goes further .... so try to understand it step by step.
If you want to install Magisk, then you should know that from some weeks ago, Magisk started a complete new life with new important instructions: look here:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
As you can see .... there is a lot to do and to learn.
Hope you'll enjoy it like your
"and relief washed over me in an awesome wave"
no one could have said it better .
PS:
Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot.
is especially for your kind of device and certainly not in general.
Alright, so I checked my twrp version with your link & I have the latest one so everything is fine. I also got lineage os 18.1 & it seems to have installed just fine. So now it's time for Magisk. So first I'm also kinda following this guide:
& Wolfgang recommends to not only install the .zip file but also Magisk manager & I couldn't find any link to download it.
"The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP" so does that mean that I have to go back to the download mode & from there flash the root file in odin & then install magisk.apk like here?:
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Also, If you're curious, the "and relief washed over me in an awesome wave" is an almost direct quote (I only changed "washes" to "washed") from my favourite movie - American Psycho.
@xabu
If you liked my previous post, does that mean that I should do the steps I mentioned?
Dearest @Winter413 ....
No, this does not mean that you should do the steps mentioned.
Again read the instructions on the official TWRP where they help you with Magisk. You can always upgrade the moment all works.
I'm not familiar enough with your device. All is working here on the S7.
A complete different device as I noticed while studying your situation.
My like also shows my admiration for your courage to root your phone and try out how to go further and further.
Ps: https://github.com/topjohnwu/Magisk/releases/tag/v24.1
What about Magisk Manager? Do I need that?
And also this :
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Is from this:
https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/#post-82196787
So that's why I asked where or not I should back off to the download screen and flash the root.
Winter413 said:
And also this :
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Is from this:
https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/#post-82196787
So that's why I asked where or not I should back off to the download screen and flash the root.
Click to expand...
Click to collapse
Yes you need the new Magisk manager. If you want a rooted phone.
But as I told you....Magisk is changed maybe a month ago .... this means totally new instructions ... so keep this in mind while working with older instructions.
And also regarding the root - If I've gone this far than I might as well go further & attain some more control over my device & also learn a bit about how computers work along the way. This is definitely not the last project of this kind that I'll be doing. I'm already running Pop os on my main computer instead of windows (however I did use windows for this whole process as Odin is unfortunately unavailable for linux). For now I'm also very very slowly learning javascript (I'll try to pick up the pace cuz it's really bad) & once I buy myself a new computer I'll try installing arch on it & using that as my daily driver & yeah, further carrer routes in IT & such are definitely also something that I'll be looking into so while pretty inconmpetent I'm not afraid to play around with computers.
Alright than. If everything is different about Magisk now than I will definitely look into how to properly install both Magisk.zip & Magisk Manager.
So I must admit I haven't looked to much into rooting yet & it seems that It is not required to install a custom rom, however this sounds pretty cool:
Advantages of rooting include the possibility for complete control over the look and feel of the device. As a superuser has access to the device's system files, all aspects of the operating system can be customized with the only real limitation being the level of coding expertise. mmediately expectable advantages of rooted devices include the following:
1. Support for theming, allowing everything to be visually changed from the color of the battery icon to the boot animation that appears while the device is booting, and more.
2. Full control of the kernel, which, for example, allows overclocking and underclocking the CPU and GPU.
3. Full application control, including the ability to fully backup, restore, or batch-edit applications, or to remove bloatware that comes pre-installed on some phones.
4. Custom automated system-level processes through the use of third-party applications.
5. Ability to install software (such as Xposed, Magisk, SuperSU, BusyBox, etc.) that allows additional levels of control on a rooted device or management of root access.
Winter413 said:
Alright than. If everything is different about Magisk now than I will definitely look into how to properly install both Magisk.zip & Magisk Manager.
Click to expand...
Click to collapse
Yes learn about the denylist and Zygisk !
So from my understanding currently the steps left are:
1. installing Magisk.zip & Magisk Manager
2. Installing NanoDroid
3. & perhaps locking my bootloader afterwards to make my device more secure? (I think that's something that should be done but correct me If I'm wrong)
& then I can finally start using my phone on Lineage os, right?