Nexus 6 / boot loader / LineageOS 15.1 - Nexus 6 Q&A, Help & Troubleshooting

Hi folks.
I have a Nexus 6 (shamu) with an unlocked boot loader. I have been dirty flashing up since LineageOS 14 > 15 and now to 15.1 (lineageos beta 4). I know I need to wipe my phone to get to the official release track of LineageOS 15.1 but would also like to re-lock the boot loader to mitigate physical attacks on my phone.
What is the proper order to get to 15.1 and re-lock the boot loader given my scenario? If you have the proper steps around the re-locking the boot loader and tools required please let me know those as well.
JJ

I dont think you can relock the bootloader with lineage 15.1 on your phone I believe you have to be on stock in order to do that which is 7.1.1 and I always used Wugs Toolkit

Related

[GUIDE] [F.A.Q.] [chef] [TREBLE] Common Hurdles and Solutions for First Timers!

This thread is meant to address all the common hurdles that are commonly faced by people who are new to treble devices (chef to be specific) and help them to troubleshoot/avoid some small yet critical steps during flashing new ROMs and working with fastboot and recovery in general. It will be continually updated with new stuff as it goes along.
I will be referring to the Motorola One Power and Moto P30 Note as chef only from now on.
The unlocking guide is available in This XDA Thread!
IMPORTANT:
1. Flashing refers to the process of doing a clean flash, with the inclusion of fastboot -w command
2. Latest ADB and Fastboot drivers are required to be installed, else the installation may halt mid-way.
3. Stock ROM refers to the Android One ROM for the Motorola One Power [XT 1942-2]
IMPORTANT: AS OF RIGHT NOW, PEOPLE WHO HAVE INSTALLED STOCK PIE (EITHER VIA UPDATE OR FIRMWARE) WILL NOT BE ABLE TO USE ANY OTHER ROM OTHER THAN THE STOCK PIE ROM. RADIO INTERFACE LAYER IS BROKEN IN OREO SOURCE BUILT ROMS AND THAT CURRENTLY INCLUDES LINEAGE 16 SO PLEASE WAIT FOR PIE SOURCE CODE FROM MOTOROLA FOR THAT TO BE FIXED.
1. I unlocked my chef . How do I flash TWRP in place of the stock recovery?
Solution:Currently you cannot as there is no recovery partition in the device. You have to manually boot TWRP onto the device using fastboot to use it. Follow as directed:
Boot the device into fastboot mode
Use command fastboot boot <path/to/TWRP.img> to boot TWRP temporarily.
2. I am done with TWRP and I want to flash Lineage OS 16 on my chef. I simply flash the .zip archive right?
Solution:No. Before you flash anything,
Take a backup of atleast your EFS and PERSIST partitions using TWRP and off-load it for safekeeping to restore in future if needed. You can also trigger a full backup if you require.
SUPER IMPORTANT: Flash this .zip file to copy the System A/B partitions. If this step is skipped, you will be responsible to brick your own device. THIS STEP IS ONLY REQUIRED ONCE AND ONLY ONCE IN THE LIFETIME OF YOUR DEVICE! YOU WON'T BE NEEDING THIS THE NEXT TIME YOU FLASH ANY ROM. .
After that, flash your dearest custom ROM and get going.
For Lineage OS 16, follow This XDA Thread.​
3. I am done testing LOS 16, I want to flash a GSI. Shall I use a stock Vendor Image for the GSI on my chef?
Solution:No. The stock Vendor image is causing bootloop issue in most GSIs. It is recommended to use Lineage OS Vendor to flash a GSI on chef. So flash LOS and then flash your favourite GSI.
Also, Super Important: for those who haven't used lineage before flahing a GSI, it is required to boot Lineage OS first before flashing a GSI. ​
4. I am done experimenting, I want to go back to the stock image. How do I proceed?
Solution:Follow this XDA thread for it. And don't install OTA updates directly from the device. It will come in the next step.​
5. I want to install OTA updates on the stock ROM. How do I proceed?
Solution:Follow this XDA post for it. The installation process is described here. You have to be clever enough to get the appropriate OTA update. ​
Credits:
@erfanoabdi : TWRP, LOS 16, AB partition management
@rushiranpise : Unlocking guide
@dayask : Testing the process, guide for reflashing stock ROM
@nageen9211 : Testing ROMs
For any additional queries, feel free to contact us at our Telegram Group
For more regular updates, follow our Telegram Channel
Always remember: You have to be smarter than your smartphone to be able to use it!
Cheers and Happy Flashing!​
Note to readers
The above guide is for stock kernels only (including lineage)
The custom Darkone Kernel has constant updates and fixes major bugs often. Please follow the linked thread to test it out if you want to. Cheers!
Anyone have flashed GSI ROM? FOr me after flash GSI HavocOS have bootloop :/
DIdn't flash copy system A/B partitions, stuck on bootloop with custom roms.
Watched some youtube videos and didn't read this post before flashing custom ROM. Flashed Custom ROM without flashing A/B partitions. Now I have a phone stuck on bootloop when done anything in TWRP. or I can use my phone with stock ROM installed by fastboot method.
Installing or restoring anything from TWRP results in boot loop.
Restoring the backup I made before flashing, completes the restoration process normally. But when rebooting to system, TWRP prompts me that no OS is installed. If I reboot anyway, its either stuck on bootloop or reboots to recovery and asks me to try again or factory reset, or boots into bootloader mode.
Installing custom ROM begins with Step 1, takes a bit time and starts step 2 and shows completed. Doesn't echos any comments. But when i reboot, same prompt shows saying no OS installed. Reboot anyway and stuck on bootloop or reboots to recovery and aks me to try again or factory reset, or boots into bootloader mode.
Now I installed stock ROM with fastboot method and phone is boots up into system just fine.
Sometimes TWRP can't mount anything.
So am I stuck with stock rom or is there any solutions?
Also, installing stock ROM with fastboot mode showed this error in between scripts
(bootloader) is-logical:xxx_a: not found
and
(bootloader) is-logical:xxx_b: not found
but is able to use the phone just fine with stock ROM.

Flashing a GSI

So I followed the steps here to get TWRP on my phone and then flash the unofficial lineage OS ali on my motorola g6 and I got it done but it's not booting into the new OS but instead TWRP. How do I get rid of TWRP so that I can use my new system image?
Removing a recovery is always a bad idea and if you want to try a custom ROM you can always go for phussson's treble builds
I myself use AOSP 8.1 [V25] and it seems to be a daily driver material.
Either way if you want to remove TWRP, you can flash the stock recovery via fastboot.
trashprogrammer said:
So I followed the steps here to get TWRP on my phone and then flash the unofficial lineage OS ali on my motorola g6 and I got it done but it's not booting into the new OS but instead TWRP. How do I get rid of TWRP so that I can use my new system image?
Click to expand...
Click to collapse
You might have not cleared the PCB properly when you formatted data. You don't get rid of your recovery. While in TWRP have you tried selecting reboot system. Or reboot bootloader and then in bootloader select start.

[GUIDE] From stock to Lineage OS as easy as Pie Note 4 SM-N910V

This is a guide to get you from stock marshmallow on the SM-N910v all the way to Lineage OS 16.0 on Android Pie none of the work in this guide is my own end credits go to all respective Developers. I wrote this guide because I purchased a Galaxy Note 4 on eBay, and while I have some basic experience with android modding before I had never used Odin and found the instructions to be scattered and not noob friendly.
*WARNING THIS WILL WIPE ALL DATA*
*I am not responsible if you brick your phone, however if you do you can always try the verizon recovery utility which will download and flash the latest version of stock marshmallow*
Step 1: Marshmallow to Lollipop: In order to unlock the bootloader you must be on Android Lollipop if your phone has already been upgraded to Marshmallow you must downgrade using Odin the first step is to download the stock ROM from this forum post https://forum.xda-developers.com/note-4-verizon/development/firmware-firmware-kernel-modem-recovery-t2942937
YOU MUST DOWNLOAD THE BUILD ENDING IN BPA1
The next step is to download Odin: https://forum.xda-developers.com/showthread.php?t=2711451
Once you have downloaded Odin install the Samsung USB drivers and confirm your phone is recognized in Odin. once your phone is recognized disable reboot after flash and click on the AP button and select the ROM you just downloaded then boot your device into download mode (power/vol down) and flash your device. after flashing your device it will boot loop in order to resolve this you must put it into recovery mode by pressing power and volume up and clear the cache and user data.
Step 2: Bootloader unlock
now you can follow this tutorial to unlock the bootloader, however don’t flash anything wiht odin just yet https://forum.xda-developers.com/note-4-verizon/general/stabilized-process-to-unlock-bootloader-t3375527 (this guide uses this software https://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913)
Step 3: TWRP
Download the latest version of TWRP from here https://twrp.me/samsung/samsunggalaxynote4qualcomm.html make sure you download the .tar file and not the .img flash this in Odin by selecting AP and choicing the TWRP file, once again make sure auto reboot is not checked when this is done your recovery should be replace by TWRP
Step 4: Lineage OS 16
According to the post on XDA you must be on marshmallow in order to install lineage OS 16 however I didn't upgrade to marshmallow for fear of losing my unlocked bootloader and it works just fine this makes sense because you were flashing over all of the stock firmware and I assume it just said this because that's what it was tested on. Use https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-16-0-t3900807 make sure to download the correct modem file and flash it using AP in odin, then just flash lineage and opengapps pico 9 ARM in TWRP, clear cache between each flash, follow any guides on the original post, this part is relatively straightforward.
Step 5: success!
Everything should be working now and you can begin to configure Lineage OS however you want!
Thanks for nice concise guide. Lot of what's on XDA discussion assume good deal of prior knowledge on the reader and it's easy to get lost. Yes I can confirm that even after unlocking boot loader on lollipop, flashing marshmallow stock rom will put you back on stock locked bootloader. It's good to know that lineageOS 16 works fine on verizon Note 4 when flashed on lollipop firmware with unlocked bootloader. I followed thread for lineageOS 18 for verizon Note 4 and there are many issues which looks like has not been resolved and debug efforts have mostly ended. There is only so much time someone could devote to sustaining volunteer projects such as lineageOS ports for Note 4. I tried lineageOS 18 on my Note 4 N910V and couldn't get it to recognize my sim. So best bet is still older lineageOS based roms flashed on lollipop firmware with unlocked bootloader.

Lenovo Z5s - SECURE BOOT-yes = won't boot with LineageOS ?

I have unlocked bootloader and installed TWRP 3.4 for my Lenovo Z5s.
I wiped partitions and installed LineageOS 17, 16, and other ROMs.
My phone doesn't want boot any system I got reset loop.
In bootloader I see SECURE BOOT - yes - is it problem with secure boot ? How to disable it ?
You installed vendor firmware update?

twrp

TWRP
I can't seem to get TWRP to install on my pixel 5 I boot it then use the installer and it just loops to fastboot mode and I'm in an awwl of why,I've done this many times on my pixel 1 and 2.,also I have bugs with it in the Lineage 19.1 official builds and I can never get TWRP to get pass the splash screen with lineage as lineage has it's own recovery.
idk ive been having real issues with twrp since i put droid 13 on my pixel 5 keep in mind ive thrown almost every custom rom on here once with twrp as my recovery bro idk think it may have to do it droid 13
TWRP isn't offically out for Android 12 or Android 13 for Pixel 5.
However Android 12.1 support is coming soon with A13 WIP,
see here
Aside from custom ROMs, TWRP isn't really necessary on Pixel devices due to the ability to flash partitions directly.
It's also worth noting that the recovery kernel lives in the boot image, which also contains the system kernel, so any time /boot is flashed, TWRP would be wiped out.

Categories

Resources