Related
Requirements:
Patched aboot: https://forum.xda-developers.com/lg-k10/how-to/bootloader-unlocked-guys-bootloader-t3558810
TWRP: https://eu.dl.twrp.me/m216/
Python scripts: https://github.com/Lekensteyn/lglaf/archive/master.zip
PyUSB: https://walac.github.io/pyusb/
Instaled python
LINUX
LG UP
Device must be: LG K420ds or LG K420n
Video tutorial: https://www.youtube.com/watch?v=vL14_XPrMzs
Watch with subtitles.
1. Install rom
Download this rom https://lg-firmwares.com/download-file/?fileId=4124
Flash it using LG UP with the refurbish option
2. Unlock Bootloader
Enter into Download Mode
Copy aboot_patched.img into folder with python scripts
Type in terminal "python partitions.py --wipe aboot"
Type in terminal "python partitions.py --restore aboot_patched.img aboot"
Exit from Download Mode and from now your BT is unlocked
3. Install TWRP
Enter into Download Mode
Copy recovery.img into folder with python scripts
Type in terminal "python partitions.py --wipe recovery"
Type in terminal "python partitions.py --restore recovery.img recovery"
Exit from Download Mode and from now your recovery is TWRP
Don't enter to recovery from comand "reboot recovery" because it restore your settings to default
Install SuperSU
Download this file https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip and copy to sdcard
Enter into Recovery
Enter into "Install"
Choose your zip file
Swipe for install
Thanks to @pvineeth97 for twrp and patched aboot.
Thread with a tool then I use https://forum.xda-developers.com/android/software-hacking/tool-lg-download-mode-laf-t3285946
[6.*] ? It is wrong. The patched aboot is only for 5.1.
Yes, it is but it work on android 6.0
Yeah, you extracted all the things from the LAF link I provided. Great job!
I recomment you to add the original XDA link for more details and extra information for the rest of users.
https://forum.xda-developers.com/android/software-hacking/tool-lg-download-mode-laf-t3285946
A video tutorial would not be bad, so that people do not have problems when executing the tutorial
flamenkito34 said:
A video tutorial would not be bad, so that people do not have problems when executing the tutorial
Click to expand...
Click to collapse
Instructions are simple buddy! Just follow them.
pvineeth97 said:
Instructions are simple buddy! Just follow them.
Click to expand...
Click to collapse
Well clear, they are not where we put aboot_parched.img and Twrp.img.
Enviado desde mi LG-K420 mediante Tapatalk
flamenkito34 said:
Well clear, they are not where we put aboot_parched.img and Twrp.img.
Enviado desde mi LG-K420 mediante Tapatalk
Click to expand...
Click to collapse
I added information into guide where copy aboot.img and recovery.img file
Well I try and tell me that quw python is not an executable command, it makes the tutorials to facilitate the work to other users, now if you put this is what it takes and you can look for life, it's like having a cough and scratching The eggs, no good
Enviado desde mi LG-K420 mediante Tapatalk
TWRP Backup!
Somebody please share your TWRP backup of system and boot partitions.
Marshmallow offcourse!
Use TWRP Manager from GooglePlay.
Than i will be able to work with it.
Don't want to waist my time to make work python.
And many other users will appreciate it!
D_Vovan_238 said:
Somebody please share your TWRP backup of system and boot partitions.
Marshmallow offcourse!
Use TWRP Manager from GooglePlay.
Than i will be able to work with it.
Don't want to waist my time to make work python.
And many other users will appreciate it!
Click to expand...
Click to collapse
I have LP's backup if you want
Thanks
Ajshal said:
I have LP's backup if you want
Click to expand...
Click to collapse
Thanks but I also have it ?
I need MarshMallow System backup, not LolliPop.
D_Vovan_238 said:
Thanks but I also have it ?
I need MarshMallow System backup, not LolliPop.
Click to expand...
Click to collapse
Ok cheers mate!
hey..
some things you should add to this guide...
How to enter download Mode: Plug In usb cable while holding volume up
*5. python, libusb etc. all installed at stock ubuntu 15.04
*6. Ubuntu 15.04 this os has everything needed in this guide onboard
create live usb usb stick with this tool and this guide
choose install ubuntu and follopw the next steps
how to set up lg up for k10 420n
Important Info: Reboot Phone (into Download Mode) after Bootloader unlock ... the video tutorial doesnt work on my phone ... Im tryed it like in the video .. dont work
How to enter Twrp:
1. Press and hold Volume Down + Power untill you see the lg logo ..
2. at the first lg logo : release volume down and power, and press volume down and power again quickly
3.confirm factory reset ... If twrp correct installed it doesnt wipe your phone
greetings martin
When I typing console commands on linux PC dont see my phone
szymm3 said:
When I typing console commands on linux PC dont see my phone
Click to expand...
Click to collapse
1. Connect phone in download mode
2. *** under linux *** theres no feedback (download mode) that the phone is connected... (Make sure that python and some other packages are installed) see my post with ubuntu
3.open terminal in folder where you placed aboot_patched.img and recovery.img (twrp)
4. Type sudo -s in terminal... Confirm.
5. Type the commands from first page or the tutorial .. I recommend to make a screenshot ...
6. When entering commands you only will see a "feedback" that your phone is correct connected... You see... Only a cryptic message that a file or partition is changed witg trim etc...
I type:
python partitions.py --wipe aboot
and this is output:
Traceback (most recent call last):
File "partitions.py", line 276, in <module>
main()
File "partitions.py", line 248, in main
comm = lglaf.autodetect_device()
File "/home/szymm3/Pobrane/lglaf-master/lglaf.py", line 318, in autodetect_device
return USBCommunication()
File "/home/szymm3/Pobrane/lglaf-master/lglaf.py", line 206, in __init__
raise RuntimeError("USB device not found")
RuntimeError: USB device not found
Phone is lg k10 (k420ds/n?)
Do you have ubuntu / linux installed or do you using live system (try ubuntu)
Little guide to install ubuntu even on a extern hard disk, usb stick , etc.
1. Boot live usb stick or dvd/cd
2.choose try ubuntu
3. Open gparted (search or download it)
4. Choose your device where linux / ubuntu should be installed
5. I recommend to use a empty disk... Delete the main partition
6. Create follow partitions :
Extended ... Select the whole disk
/ ext4 minimum 10-15gb
Logical
Linux swap ...size: Ca. 20% more then installed ram
/home ext4 size you want ...
Logical
Click here for a guide
7.click apply at gparted
8. Reboot to live usb stick
9. Choose install ubuntu
10. When asked where ubuntu should be installed click something else ... Or what you at the last option
****bootloader installation device****
Choose your device not a partition ...
Example. Dev/sdxyz/your harddisk ... Not
Dev/sdx1
11. You now see your installed / pluged devices /hard disk
12.select your device... There now are your prepared partitions ... Choose your / partition.. Click change ... Now choose as mount ... /
13. Install
click here for more infos
dont know how to show this in english
In the live system there are some tools and packages not installed... Seems like there is an issue with pyusb ...
Check... Python status ... Type
ls /usr/bin | grep python .... There should be now pop up some lines1 with python version installed
Now type in terminal
apt-cache policy libusb-1.0
One of the now showed version has to be installed....
If both packages are installed correct... Make sure pyusb is installed ... (As i post above ... Ubuntu 15.04 has both installed
Install python :
Open terminal in pyusb folder...where setup.py is placed
Type
Sudo python setup.py install
Now pyusb should be installed correct....
These are the requirements to use this guide..
If you received more issues .. Just write... But after i do all steps above it worked...
- martin
ps now im off for some hours... repair 260 hp car and ride with my simson moped yeeeeeeha
When im have the time too .. Im write a detailed guide
I have lg k10 k420n
Im using Ubuntu and when i made every step from this instruction I still have the same error
dom133 said:
Requirements:
Patched aboot: https://forum.xda-developers.com/lg-k10/how-to/bootloader-unlocked-guys-bootloader-t3558810
TWRP: https://eu.dl.twrp.me/m216/
Python scripts: https://github.com/Lekensteyn/lglaf/archive/master.zip
PyUSB: https://walac.github.io/pyusb/
Instaled python
LINUX
LG UP
Device must be: LG K420ds or LG K420n
Video tutorial:
Watch with subtitles.
1. Install rom
Download this rom https://lg-firmwares.com/download-file/?fileId=4124
Flash it using LG UP with the refurbish option
2. Unlock Bootloader
Enter into Download Mode
Copy aboot_patched.img into folder with python scripts
Type in terminal "python partitions.py --wipe aboot"
Type in terminal "python partitions.py --restore aboot_patched.img aboot"
Exit from Download Mode and from now your BT is unlocked
3. Install TWRP
Enter into Download Mode
Copy recovery.img into folder with python scripts
Type in terminal "python partitions.py --wipe recovery"
Type in terminal "python partitions.py --restore recovery.img recovery"
Exit from Download Mode and from now your recovery is TWRP
Don't enter to recovery from comand "reboot recovery" because it restore your settings to default
Install SuperSU
Download this file https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip and copy to sdcard
Enter into Recovery
Enter into "Install"
Choose your zip file
Swipe for install
Thanks to @pvineeth97 for twrp and patched aboot.
Thread with a tool then I use https://forum.xda-developers.com/android/software-hacking/tool-lg-download-mode-laf-t3285946
Click to expand...
Click to collapse
______________________________________
Is Flashing the above Rom Necessary?
I already have 5.1.1 Qualcomm but the security patch is Jan 2017.
I want to do it, without flashing.. will it work?
Any Suggestions..?
--------------------------------------------------------------
Hi, I created this thread because I noticed that more and more people are experiencing the bootloop after flashing gapps on rom 8.1.0 Oreo.
If you experience bootloop after installation oreo, just do everything according to the instructions.
What you will need:
- adb and fastboot,
- notepad++;
1. -- clean flash rom you want to install,
2. -- flash newest gapps ARM64, you can download it here - https://opengapps.org
3. -- don't start the device, in TWRP go to mount, and select "system",
4. -- connect your phone to your computer and run fastboot and adb as administrator,
5. -- type:
Code:
adb pull /system/build.prop
now in the folder with fastboot you will have the build.prop file,
6. -- open build.prop with Notepad ++ and find "ro.setupwizard.mode = OPTIONAL", replace it with "ro.setupwizard.mode = DISABLED" and save it,
7. -- now in fastboot type:
Code:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
8. -- reboot device.
now there will be no bootloop, but you will not see wizard setup, you have to configure the phone manually.
Most roms already have this fixed anyway, I haven't come across any that haven't yet.
Exanneon said:
Most roms already have this fixed anyway, I haven't come across any that haven't yet.
Click to expand...
Click to collapse
Possible, but it does not happen to everyone, I, for example - I have this problem on AospExtended, FireHound and many other roms released after March, I have no idea why it is, most people do not have bootloops, but some people, including me, have problem, that's why it is better to have one guide here than on one of the pages of the topic of some rom.
I see, I suppose that's just to do with your model, mine is XT1675 and the only rom I've had this issue with was bootleggers rom, however, a recent update had fixed this.
With the recent AOSP Extended rom I still have this problem but changing the build prop doesn't work as it turns back to OPTIONAL on boot for some reason, any idea?
EDIT: changed from optional to disabled and it worked
So, what's the best method?
For what I read:
- see what slot I currently use
- put the right kernel on memory
- boot temp twrp
- flash like a normal zip?
It's like this? Anything different?
Yep, that's the normal method. But twrp doesn't have encryption for pie stock, so if you are on pie, you will need to use sideload to install files.
Steps:
-Download latest hex from hex telegram groups, you can get groups on hex xda thread.
-Move files to your fastboot/adb directly.
-Boot phone to twrp
-Go to reboot, and check what is the current slot
-Return to the menu
-Go to Advanced>ADB Sideload and swipe to confirm
-Now on pc, open an adb command prompt, and use the command :
"adb sideload zipname.zip"
zip name can be hex_a.zip, hex_a_rebase.zip, or hex_b.zip, hex_b_rebase.zip. Depends of the version of hex, and of your current slot. Need to use the a if your current slot is a, and same for b...
Good luck
Matteo
Hi,
I would like install at the Samsung SM-A515F the Lineage OS and the TWRP. I found only TWRP for the SM-A50. And the flashing dose not work for this phone.
I has try it with Heimdall and Odin.
The recovery I had downloaed from this Page:
https://www.droidthunder.com/install-twrp-recovery-on-galaxy-a51/
Need help or better information, if there exist an TWRP and lineage for this device.
Regards tiptel170
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
s 10 page? which one is that? can u please provide the link?
Go here for odin flash method without twrp
sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
so does this method work for lineage os on A515F too?
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
Don't pay.Its fake
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
of course it would be fake
How can I open the img-files in the Linux desktop?
Found here this link, for the Magisk in the A515F:
https://forum.xda-developers.com/ga...w-to-root-samsung-a51-sm-a515f-t4032389/page2
I'll found this:
1. https://www.androlite.com/2020/01/twrp-root-samsung-galaxy-a51.html
2. https://appslova.com/install-twrp-on-samsung-galaxy-a51/
This links look likes good, because, my phone will not start or the heimdall goes into the error (likes in de page one, the screenshots ).
I found this, and I used basic from this page: https://forum.xda-developers.com/showpost.php?p=82241115&postcount=70
My first steps to install the lineage os 17 on the SM-A515F
Lineage: https://sourceforge.net/projects/andyyan-gsi/
All commands in the linux terminal, the path please use your own paths you like it!
Unpack lineage****.xz:
unxz lineage*.xz
1) Extract the AP_file.tar.md5 from your firmware.zip file using 7zip
2) Extract the super.img.lz4 file from the AP_file.tar.md5 file using 7zip
3) Put super.img.lz4 file in LZ4 folder and run in CMD the command
lz4 -d super.img.lz4 superLZ4.img
4) Put superLZ4.img file in Simg2img folder and run in CMD the command
chmod 777 ~/bin/otatools/bin/simg2img
~/bin/otatools/bin/simg2img superLZ4.img superSIMG.img
In Linux OR Bash shell:
1) Put superSIMG.img in otatools/bin folder and extract it in Linux terminal using the command
chomd 777 ~/bin/otatools/bin/lpunpack
~/bin/otatools/bin/lpunpack --slot=0 superSIMG.img ~/1
2) Put, in the folder where you extracted superSIMG.img, the GSI file you downloaded and rename it to system.img. Now you should have odm.img, system.img, vendor.img and product.img files in the same folder.
You may also need to delete/remane the original system.img file before renaming the GSI file.
3) Now you’re going to make a brand new super.img file containing all 4 files of the previous step. This is a critical and tricky step. Run Linux terminal and type:
chomd 777 ~/bin/otatools/bin/lpmake
~/bin/otatools/bin/lpmake ~/bin/otatools/bin/lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:4294967296 --group main:4293513600 --partition system:readonly:1959841792:main --image system=./system.img --partition vendor:readonly:680239104:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
4) Make an tar file:
tar -H ustar -c super.img > lineageos17.1_SMA515F.tar
5) Goto Windows -> Odin -> AP, put the file lineageos17.1_SMA515F.tar in to the AP-slot -> Start
This is what I has done:
But, by the compiling, I got this error:
Code:
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition system will resize from 0 bytes to 1959841792 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition vendor will resize from 0 bytes to 680239104 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition odm will resize from 0 bytes to 4349952 bytes
Invalid sparse file format at header magic
Invalid sparse file format at header magic
And the phone is into the boot-loop, it will not starting the system.
Any help please...
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
tiptel170 said:
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
Click to expand...
Click to collapse
It is work ???
GreggBorowski said:
It is work ???
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
sankhauaa said:
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
Don't pay.Its fake
Click to expand...
Click to collapse
sar please send me a51 group
Mehran` said:
sar please send me a51 group
Click to expand...
Click to collapse
Go to s10 page
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
Not working. I has done step by step in this guide.
ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
No. Withe manipulation from the vbmeta.img, the system is unwilling to start. It gos in to the bootloader, with error-codes. Like in first thread I describe. Olny the SAMSUNG original system works with the kernel modification for the MagiskManager.
I saw black for the future, there will be exist an custom rom for this device.
I have no idea, what can I do for this device. But I use and spend a lot of time for modification, without an good result. Has anyone an idea what can I do? But it look likes, it has an great secure system intern for not using an customer rom. This is my intention.
Installing Lineage
Few quick things.
Since the 8T does not have a single unified guide like FunkWizard did for other OnePlus devices, I'm adding some things that are likely important, but don't necessarily have to do with installing LOS.
This will be similar to my 6T installing Lineage guide. However the 8T is a newer device, and new to me. Expect it to change and get updated as things change. I'll add in pictures like the 6T guide soon.
I also want to address a common question, you can use Windows for this process. I prefer Linux, and Fastboot just works in Linux without driver issues. If you have Fastboot and ADB working in Windows already feel free to use that if you want. If you use Windows, remove "sudo" from the commands (this is for Linux).
I am using a Global 8T, and have only tested these methods on such.
Make Sure OOS is Updated1. Start fresh, and make sure OOS is up to date.
This should be self explanatory. Go to settings, and system, check for updates. Download and install any system updates OOS has to make sure you have the latest firmware on your device.
Unlock the Bootloader2. Unlock the Bootloader
sudo fastboot flashing unlock
For this step you will need fastboot. I use Linux, and honestly I feel like it's easier and more reliable for fastboot and ADB so that's what I'm including here in these steps. It's easy to boot from a USB.
To create a bootable Linux flash drive you can use Unetbootin, which you can download for free here (Your other option would be to burn the ISO straight to a DVD and skip the unetbootin step):
https://unetbootin.github.io/
For Linux, I'm using Linux Mint Cinnamon, You can download for free here:
https://www.linuxmint.com/download.php
Then run unetbootin (yours will look a little different, I'm running it in Linux):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Point it to the Linux ISO, and tell it where an empty flash drive is. It will erase everything on the flash drive. Afterwards you can load whatever you want on the flash drive. However be aware when booting Linux from this drive you can't access what is on the drive (at least not by normal methods).
After this has successfully completed, reboot the PC, and boot from the USB drive. Your PC will boot into Linux (turning off the PC and removing the USB drive will make it boot up like normal again).
Next we need to install fastboot and adb. You need to open up the "start menu" and open the "synaptic package manager". You can find this stuff in the menus, however the easiest way to get to these items is to just start typing the name of the item. See below:
Search fastboot, click the boxes, choose install. Then search for ADB, click the boxes, choose install and then click apply. That will install most of the stuff we need, but really old versions of fastboot and adb. You must update fastboot to install LOS. Time to open up a terminal:
In the terminal run these commands to update fastboot and adb (this is downloading them directly from Google).
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
sudo cp platform-tools/adb /usr/bin/adb
sudo cp platform-tools/fastboot /usr/bin/fastboot
Next you need to make sure OEM unlocking is enabled. If you haven't tapped on the build number and enabled devloper options, do this now. enabling USB debugging for the moment, would also be helpful.
Now would be a good time to back everything up. The phone will get wiped.
Place the phone in fastboot mode. You can do this using the advanced reboot menu or ADB, or the key combinations (all key combos listed below for reference):
Volume Up + Power while turning on will boot to fastboot. (<-- Don't believe this works on the 8T)
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
If you enabled USB Debugging in the terminal window, type (the phone will pop up a warning asking you to allow USB debugging, make sure you allow this):
sudo adb reboot bootloader (<-- This command will make the phone restart to the bootloader / fastboot)
Once there type the command below. Your phone will be wiped. Make sure you backed up any important information. Use the volume buttons to select unlock, and press the power button.
sudo fastboot flashing unlock
Backing up Persist / EFS3. Backing up the persist partition and EFS backup.
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.bin
dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.bin
Hopefully you never need a backup of your persist paritition or EFS backup. However if anything ever happens you'll be glad you have it. The EFS contains the IMEI, so it is unique to every device. You can do this at any point as long as you have root. The easiest way, epsecially for those not want to root their device is to use the broken TWRP. I got this TWRP and a bunch of my initial rooting information from @Mpolo87 's Guide OnePlus 8T EasyRoot. It is an excellent guide. The TWRP is in step 4. This is not the way you need to root LOS though. Download this TWRP.
Once again from the terminal:
The image explained:
cd Desktop <-- Switched the directory to the Desktop the default directory when you open up the terminal is the /home directory.
sudo fastboot devices <-- Is just checking to see if my PC can see my phone, and making sure it's in fastboot. Sudo is necessary for this distro, as both fastboot and ADB must be run as root.
sudo fastboot boot recovery.img * <-- Sends that TWRP image to the phone to be booted temporarily. Only boot this, never run the command "flash".
With this TWRP loaded it is normal that the screen will be blank and just briefly flash the TWRP logo screen. All we need to do is use the terminal window on the PC. Run these commands:
sudo adb shell
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.bin
dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.bin
exit
sudo adb pull /sdcard/persist.img /home/mint/Desktop
sudo adb pull /sdcard/modemst1.bin /home/mint/Desktop
sudo adb pull /sdcard/modemst2.bin /home/mint/Desktop
It is important to use ADB to pull the files off of the device after creating them. They won't be accessible after you restart. Also if you are using a live Linux distro (USB) the files do not remain on the USB after you restart / power off. So you need to place these files on another hard drive or USB. The persist.img should be ~ 32MB the Modems should be ~ 2MB each. Once you have the files you can run
sudo adb reboot bootloader
Installing Lineage4. LOS 18.1 Thread
Quick Common questions:
Gapps are not included, you must sideload them if you want them. Personally I use NikGapps, LOS Recommends MindtheGapps.
Official LOS 8T Download Link
Download the latest build, and the recovery image from the link above.
You must have a current version of fastboot / adb to successfully install this. (Update method mentioned previously in this guide) To install Lineage it is as simple as the instructions listed on the LOS site.
From the terminal:
sudo adb reboot bootloader
sudo fastboot flash recovery lineage-18.1-20210506-recovery-kebab.img
Now reboot in recovery. Doesn't matter how you get there. You can use the volume keys to change the options in the bootloader, you can use volume down and power, etc. Once in Lineage Recovery we need to run the copy partitions zip. The link for this is on the LOS install page. However here is a direct link. In LOS recovery choose:
- Apply Update
- Apply from ADB
From the terminal on the PC
- sudo adb sideload copy-partitions-20210323_1922.zip
LOS recovery will warn you about the zip not being signed, flash this anyways. Hit the back button, choose advanced, and then reboot to recovery. It is now time to actually install LOS. In LOS Recovery:
- Factory Reset. (You did backup everything right?)
- Press Format data / factory reset.
- From the main LOS Recovery menu, Apply Update
- Apply from ADB
From the terminal on the PC
- sudo adb sideload lineage-18.1-20210506-nightly-kebab-signed.zip
If you want to install Gapps or Magisk, you must reboot to recovery. Go to advanced and choose reboot to recovery before install anything else. If you are only installing LOS you are ready to reboot to system now.
Optional, Gapps5. Sideloading Gapps.
For Android 11 I've been using NikGapps:
NikGapps <-- For Lineage 18.1 (Use the R Folders for Android 11. I recommend the "Core" version. I also tested Basic though if you want that level of Gapps. I strongly recommend you grab setup wizard out of the R Addons Folder, I used the regular setup wizard, not the pixel one.)
Remember you need to reboot to recovery once after installing LOS (as mentioned above). This does not mean you need to let LOS boot, just reboot to recovery, so that it switches slots.
In LOS recovery choose:
- Apply update
- Apply from ADB
Now in the terminal on the PC:
- sudo adb sideload NikGapps-core-arm64-11-20210501-signed.zip
- Remember between each zip file you must again hit apply from ADB.
- sudo adb sideload NikGapps-Addon-11-SetupWizard-signed.zip
LOS recovery will warn you about the zip not being signed, flash this anyways.
If you get a warning about them not being signed, choose flash anyways. If you are going to flash Magisk, move to the next section. If you don't need Magisk, reboot to system.
Very Optional, Magisk5. Sideloading Magisk.
All the devices I've tested with Android 11 have worked fine since Magisk 21.2. At this point I don't see a reason to still run the Canary builds unless you want to for some reason.
Download Magisk: [urlhttps://github.com/topjohnwu/Magisk/releases]Magisk GitHub Link[/url]
This will be flashed in LOS recovery. To get to recovery you can use the ADB (if you enable USB debugging), key combination, or the advanced restart menu, doesn't matter.
In LOS recovery choose:
- Apply update
- Apply from ADB
Now in the terminal on the PC:
- sudo adb sideload Magisk-v22.1.zip
If you get a warning about them not being signed, choose flash anyways. We should be ready to reboot to the system now.
Very Optional, Passing Safety Net6. Magisk Required.
These items are add-ons are flashed in Magisk after the first boot (Don't flash these in TWRP anymore):
MagiskHide Props Config
Busybox
To flash modules in Magisk press the puzzle piece icon. Then choose install from storage. Now just choose your addons. After flashing the icons it will have a reboot icon at the bottom. You can reboot or you can press back and flash another. After you are done reboot.
You will also need a Terminal Emulator. I personally use:
Terminal Emulator for Android
Once all these are installed the first step is setup Magisk. Under Magisk go to settings:
In version 20.4+ Magisk Hide is no longer on by default. So make sure the Magisk Hide, Hide Magisk from various forms of detection switch is flipped. Then press Hide Magisk Manager. This will bring up a box for you to choose a random name for the Magisk Manager, type whatever you want here. You can leave it Manager if you wish, but I typically change this.
Now open Magisk again. It will ask you to download it again, click ok, then manually open the app again as it says. Now we need to open Magisk hide. This is now under the shield icon, then click the arrow at the top:
These are the apps you don't want to know that you have root. Less is better. You can cause instability problems by just choosing everything. My general rule of thumb is, Google, steaming video, music, and payment apps get selected. In my experience if I come across an app that needs it and I didn't select it, I just clear cache and/or data and re-open the app and it works. There are some big multiplayer apps that ban hardware / people, so do your research (don't ask me, I don't play those games).
Next time to change the device fingerprint using MagiskHide Props Config Module. We do this using the terminal emulator. In the terminal emulator, type "su" to gain root privileges. Then type props to run the module:
Now it's just following the menus. Choose option 1 - Edit device finger print. (type 1, hit enter)
After this you will see a menu of devices. It doesn't matter what device you pick really. If you want apps / Google to think you have a OPPO or Samsung pick one of those Fingerprints. However there's a bit more to passing Safety-net than that. Since Google has changed how things work not all those fingerprints that used to work will work now. Also now you may get an error when you turn on the phone because of the security dates. My 8T passes saftey net, just choosing the 8T and Android 11 fingerprint. Also keep in mind some fingerprints will require Force basic key attestation to pass.
After choosing the fingerprint you want, it will ask you if you want to reboot. Choose yes. After rebooting, you may need to clear the cache from the play store for some apps to appear in it. You should now pass safety net. Check this in Magisk:
Very Optional, Ad Blocking7. Root required.
You can block many things with a hosts file, most popular would be ads. I've been use StevenBlack's host file which is a compilation of several hosts files. This is located on Github:
https://github.com/StevenBlack/hosts (Scroll down you'll see the options of what you can block)
Direct link to the hosts file I use. This will block Adware / Malware.
First we have to make the hosts file. The hosts file must use Unix / Linux line endings. If you are using Linux, don't worry about this, just create the file. If you are using Windows, the easiest thing to do is use Notepad++ (Free).
Notepad++ Downloads
Next one other caveat. The hosts file is quite large. I've never had much luck copy and pasting it from any other browser than Firefox (Windows or Linux), but however you get it into Notepad++ is not a big deal.
Once in you have the hosts file into Notepad++ go to Edit, EOL Conversion, and Choose Unix (LF).
Now save the file as "hosts" no ending. This does mean under file type you will need to change it to All File types *.*. Move this hosts file to your phone.
You will need to use a root file explorer to copy this hosts file to /system/etc/ and replace the file that is there. I used Solid Explorer for this.
Updating Lineage
Updating Lineage is pretty much the same as installing it, just without the reset or wipe. First reboot to Lineage recovery. Doesn't matter how you get there. You can use the advanced reboot menu, or the adb.
Couple things to remember:
You will need a PC for this.
Fastboot / ADB must be updated for this to work, otherwise you will have problems.
Apply Update --> Apply From ADB
- sudo adb sideload lineage-18.1-20210506-nightly-kebab-signed.zip
If you use Gapps or Magisk, you also need to sideload these. Once again you still need to reboot recovery. Hit the back button, choose advanced, and then reboot to recovery.
Apply Update -> Apply from ADB (This must be done between each zip file)
- sudo adb sideload NikGapps-core-arm64-11-20210501-signed.zip
- sudo adb sideload NikGapps-Addon-11-SetupWizard-signed.zip
- sudo adb sideload Magisk-v22.1.zip
If you get a warning about them not being signed, choose flash anyways.
Then reboot to system. If you were using a hosts file for adblocking you will need to put that back as well when it boots. This gets replaced during the update.
Cliff Notes
Hopefully you've backed up EFS and persist partition.
Fastboot and ADB must be current version. You will have issues if they are old.
If you are using Windows remove "sudo" from the commands. This is for Linux only.
Once you install Gapps you need to continuing installing Gapps. If you want to go without Gapps after installing them, do a clean install.
Installing Lineage
sudo adb reboot bootloader
sudo fastboot flash recovery lineage-18.1-20210506-recovery-kebab.img
Apply Update --> Apply From ADB
- sudo adb sideload copy-partitions-20210323_1922.zip (assuming this is a new install) (you can skip wiping data if you are updating)
Reboot to Recovery (This option is in the Advanced Menu of LOS Recovery)
Choose factory reset, and format data (assuming this is a new install) (you can skip wiping data if you are updating)
Apply Update --> Apply From ADB
- sudo adb sideload lineage-18.1-20210506-nightly-kebab-signed.zip
If you want to sideload Gapps / Magisk you must reboot recovery now (This option is in the Advanced Menu of LOS Recovery). If you are only installing Lineage, you are ready to reboot to system.
In LOS recovery choose:
- Apply update
- Apply from ADB
Now in the terminal on the PC:
- sudo adb sideload NikGapps-core-arm64-11-20210501-signed.zip
- sudo adb sideload NikGapps-Addon-11-SetupWizard-signed.zip
- sudo adb sideload Magisk-v22.1.zip
If you get a warning about them not being signed, choose flash anyways. We should be ready to reboot to the system now.
Updating Lineage
Using LOS Recovery:
Apply Update --> Apply From ADB
- sudo adb sideload lineage-18.1-20210506-nightly-kebab-signed.zip
If you use Gapps or Magisk, you also need to sideload these. Once again you still need to reboot recovery. Hit the back button, choose advanced, and then reboot to recovery.
Apply Update -> Apply from ADB (This must be done between each zip file)
- sudo adb sideload NikGapps-core-arm64-11-20210501-signed.zip
- sudo adb sideload NikGapps-Addon-11-SetupWizard-signed.zip
- sudo adb sideload Magisk-v22.1.zip
If you get a warning about them not being signed, choose flash anyways.
Then reboot to system. If you were using a hosts file for adblocking you will need to put that back as well when it boots. This gets replaced during the update.
Woah, this is awesome, moving from my old Note 5 to a OP8T very soon (Currently in shipping, I'll have it in hand in a week or so if all goes well, very excited). This will be my first time poking around with Oneplus, or any new device for that matter (I've never dabbled in the AB system and stuff yet) and a guide like this is exactly what I need. Thank you so much!
Guide is updated, with update instructions, and cliff notes. I updated to the new build today. No issues.
For adblock you should add Adaway in there for an easier/safer option. You also get automatic host file updates then too
Very nice sir, very nice indeed!
Are these commands the same for windows?
I have been out of development for a long time. Last roms I built was Windows mobile 5. Probably around 2009. I must admit I'm a little lost in all the new terminology.
I have a T-mobile 8T+5G and SIM is unlocked and waiting on Boot loader unlock token to arrive tomorrow.
If anyone is interested in helping hold my hand through install, root etc I will gladly give a tip for your time. I have windows and and fastboot working. PM me for contact information.
bobsbbq said:
Are these commands the same for windows?
I have been out of development for a long time. Last roms I built was Windows mobile 5. Probably around 2009. I must admit I'm a little lost in all the new terminology.
I have a T-mobile 8T+5G and SIM is unlocked and waiting on Boot loader unlock token to arrive tomorrow.
If anyone is interested in helping hold my hand through install, root etc I will gladly give a tip for your time. I have windows and and fastboot working. PM me for contact information.
Click to expand...
Click to collapse
It is the same commands for windows. Just need to install the proper fastboot and adb binaries and drivers for windows (can easily be found by searching).
bobsbbq said:
Are these commands the same for windows
Click to expand...
Click to collapse
Just remove "sudo" from them. The distro I'm using requires fastboot / ADB to be run as root. Sudo obviously won't work and isn't needed in Windows. Everything else is the same.
Could you add "Revert Back to OOS from Lineage Guide" too ? Just in case people want to restore OOS !
rohanhole said:
Could you add "Revert Back to OOS from Lineage Guide" too ? Just in case people want to restore OOS !
Click to expand...
Click to collapse
This I should probably mention as this device doesn't really have an easy way to return back to stock at the moment. At least without using the MSM Tool, that I know of? At the moment you will need to use the MSM tool.
MSM / Unbrick Tool Thread <-- Instructions / Guide Included in that thread. * Remember using this tool will wipe your data, and it will relock your bootloader.
Also that is the regular 8T thread, TMobile users wanting the TMobile version would use the TMobile Thread.
jwarrior319 said:
For adblock you should add Adaway in there for an easier/safer option. You also get automatic host file updates then too
Click to expand...
Click to collapse
I'm not sure about safer? Again I'm making some assumptions I guess... I've never used Adaway, always used a hosts file. For what it's worth there is an adway add on in the NikGapps addon folder. At some point maybe I'll try and test this.
OhioYJ said:
This I should probably mention as this device doesn't really have an easy way to return back to stock at the moment. At least without using the MSM Tool, that I know of? At the moment you will need to use the MSM tool.
MSM / Unbrick Tool Thread <-- Instructions / Guide Included in that thread. * Remember using this tool will wipe your data, and it will relock your bootloader.
Also that is the regular 8T thread, TMobile users wanting the TMobile version would use the TMobile Thread.
I'm not sure about safer? Again I'm making some assumptions I guess... I've never used Adaway, always used a hosts file. For what it's worth there is an adway add on in the NikGapps addon folder. At some point maybe I'll try and test this.
Click to expand...
Click to collapse
Another way to revert back to OOS is to use the payload dumpster tool with a full ota zip and flash all the images. There's a thread already with instructions on that.
Edit: https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/
Under manually in post 1
jwarrior319 said:
Another way to revert back to OOS is to use the payload dumpster tool with a full ota zip and flash all the images. There's a thread already with instructions on that.
Edit: https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/
Under manually in post 1
Click to expand...
Click to collapse
I figured this might be possible, but I hadn't tried yet. Very helpful. MSM should always be a last resort.
I had already rooted and flashed the LOS ROM. I forgot to come back to this guide. I did not back up the persist and modem files. Is it too late for that now?
bobsbbq said:
I had already rooted and flashed the LOS ROM. I forgot to come back to this guide. I did not back up the persist and modem files. Is it too late for that now?
Click to expand...
Click to collapse
I don't think linage touch these paritions (at least not the persist one), but I might be wrong. In either case I would take a back up of persist and the modems now, as a backup from now is probably better than no backup if you get any problems later on.
Is there supposed to be F-Droid and Micro-G in the base LOS Rom? I don't have either. Sorry still trying to get use to this.
bobsbbq said:
Is there supposed to be F-Droid and Micro-G in the base LOS Rom? I don't have either. Sorry still trying to get use to this.
Click to expand...
Click to collapse
No it is not.
Got LOS installed, still does fastboot loop. Sideloaded Magisk 21.4, failed. Can't get past fastboot....hasn't booted to LOS even once
.
Anyone? No sense in trying it again until there's some feedback.
Device is NOT bricked. Can still reinstall the ROM, just will not boot to LOS...
Success!
You have to use r31.0.0 platform-tools
Linux users run commands as ROOT & add ./ before fastboot (./fastboot)