Related
Hey everybody!
***New APK editor added! Set the keys to whatever you want, see below!***
****I will not be held responsible if your Nook Color starts eating babies!!****
****Or if it breaks either!!****
****Added a revert, for those who may have issues returning the keylayout to stock (like 1.1 users who can't run the keylayout app)****
****As an added request, if anyone knows how to reload the keylayouts sans reboot, please let me know, as that is really the only thing missing from this little thing. I would love to be able to quickly reload these as needed.****
So after creating the flashable zip file for the keylayouts, and receiving some feedback that implied it would be nice to have more options, I decided to brush up on the coding skills and write a nice little app that can re-write the keylayout files without having to flash anything. This is actually my first android app, so please provide me with any feedback you may have, the more the better. The way I see it, the more I know, the better things I can make.
The keylayout app currently supports mapping the volume keys to these items:
Volume Up
Volume Down
Menu
Back
Search
D-pad Center
and can additionally support wake on press, if desired. Once written, you will need to reboot your device for the keylayout to be effective, but it's still easier than manual edits or multiple flashes.
***Note that using the app requires su access, and also at this point requires that you first flash one of my v5 keylayout zip files***
***I have received notice that the application does not run on stock rooted 1.1.0 I will be looking into this and posting an update, and most likely a revert to stock zip in case anyone needs it.***
Thanks go to whoever first suggested this, I'll be damned if I can't remember who I got this from, but thank you, whoever you are, I'll be sure to give you props when I figure out who you are.
History over, now for the details:
To install: Simply flash either zip file in CWM after flashing your CM7 or Honeycomb build to your eMMC. Once you do this, you can install and use the apk file to make changes to the keylayouts to your heart's content.
The CWM zips have been confirmed to work on most all versions of android for the nook, and in theory, the APK should work as well, however YMMV. If it works, or if it doesn't, please please post your version or build info, and let us all know what works and what doesn't.
Feedback and/or critiques accepted, may be subject to rebuttal. Hope this helps someone else, and thanks to everyone on this forum for all the hard work you do!
FYI: For those who still want an easy way to change the volume when these keys are no longer volume keys, try replacing the longpress home app with Recent Plus, by local forum contributor timoskrempel, which I first found HERE and works very well as a replacement.
Version History
-----------------------
apkv0.1b - Initial version of the keylayout app. Feedback appreciated.
v5: added files that apparently weren't as useless as I assumed. Also created inverted keys zip, use INV zip to switch the buttons.
v4: removed useless files from update zip, cause I'm being a bit too perfectionist.
V3: added files to improve compatibility (HC v4 tested, should work on Froyo, maybe stock)
V2: removed wake on press (thanks jasoraso)
V1: First Version
I definitely prefer hard keys, even with the modifications in CM7. I'll give your zip a try next time I flash a rom (I've already changed my qwerty.kl on this rom).
One other thing - I also prefer to remove the "wake" for those 2 keys, I found that the NC was accidentally waking up from inadvertent keypresses on the volume keys ...
jasoraso said:
One other thing - I also prefer to remove the "wake" for those 2 keys, I found that the NC was accidentally waking up from inadvertent keypresses on the volume keys ...
Click to expand...
Click to collapse
An excellent point. Editing my zip and attaching v2. thanks to you!
success! just flashed this along with nightly#4 and it works like a charm.
I love this. always get stuck in pics in Facebook and can't get back.
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
digitalslacker said:
I love this. always get stuck in pics in Facebook and can't get back.
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
Click to expand...
Click to collapse
Widgetsoid has a volume adjuster that I use, though more often I just use headphones with volume sliders built in, so I skip using the software entirely. Ideally, I would love to be able to mod the framework to add a quick volume adjust button to the status bar like the softkeys, however that involves code editing that I just haven't dug into yet. If I do make the edit, I'll be sure to post what i make though.
EpicFail236 said:
Widgetsoid has a volume adjuster that I use, though more often I just use headphones with volume sliders built in, so I skip using the software entirely. Ideally, I would love to be able to mod the framework to add a quick volume adjust button to the status bar like the softkeys, however that involves code editing that I just haven't dug into yet. If I do make the edit, I'll be sure to post what i make though.
Click to expand...
Click to collapse
thanks, i'll check it out.
What would be really cool and I'm not sure it's possible and I know it's not in the scope of this thread; but a way to change functionality of the buttons per app. So for example when in Pandora (or music app of choice) buttons behave as volume buttons, but under other various apps like gallery it could be home+back button set.
Seems like you'd have to have an app running as a service and monitor the currently running focused app (not in sleep mode) and depending on what has focus do a live update to the qwerty.kl file to change buttons to expected functionality, not sure if a reboot is required after an update to the kl file though?
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Thanks for your work, installed without a hitch..
spikey911 said:
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Thanks for your work, installed without a hitch..
Click to expand...
Click to collapse
change mapping in step 4 from here:
http://nookdevs.com/NookColor_Remap_volume_buttons_for_back_and_menu
adb pull /system/usr/keylayout/TWL4030_Keypad.kl
adb pull /system/usr/keylayout/omap_twl4030keypad.kl
edit 'TWL4030_Keypad.kl' and 'omap_twl4030keypad.kl' with a unix line ending aware text editor (Notepad++, gedit, vi)
replace 'VOLUME_DOWN' with 'BACK' and replace 'VOLUME_UP' with 'MENU' in each (or vice-versa)
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
exit
adb push TWL4030_Keypad.kl /system/usr/keylayout/TWL4030_Keypad.kl
adb push omap_twl4030keypad.kl /system/usr/keylayout/omap_twl4030keypad.kl
adb shell
cd /system/usr/keylayout
chmod 644 omap_twl4030keypad.kl
chmod 644 TWL4030_Keypad.kl
exit
adb reboot
Click to expand...
Click to collapse
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
fattymcdirty said:
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
Click to expand...
Click to collapse
Thanks for the heads up, will review and post v5 sometime today.
my status bar always shows with HoneyComb, so I always have the back menu buttons. are there apps where this is not the case?
Anyone try this on froyo yet?
fattymcdirty said:
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
Click to expand...
Click to collapse
Yeah, I totally deleted an extra file, added to v5 and it should now work with this eMMC build. oops.
spikey911 said:
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Click to expand...
Click to collapse
I will have to put together a stock zip and put it up sometime in the near future. Your swap keys is not easily done directly, but I have posted a new flashable zip that will swap the keys, flash INV-v5 to have the volup function as back and voldown to work as menu. This one I haven't tested, as I don't actually have my nook with me here now, but in theory it should be OK, as all I did was swap the mappings in the kl files.
After setting up CM7 Nightly 4 last night I replaced the SDcard with CWM 3.0.0.6 used to install CM7 with a fat32 8gb for storage.
Afterwards I installed ROM Manager and the latest Recovery included - 3.0.0.5.
I am able to flash Dalingrin's latest kernel through here but when I went to flash todays Nightly CM7 it did not work (probably because of the 3.0.0.5 i figured). I plugged back in the 1GB SD with 3.0.0.6 and successfully flashed todays nightly.
I then tried to flash the Hard Key Mod file using the emmc recovery and it did not work so I copied it to my 1GB SD and that worked.
Anyways...I wrote this just in case someone was having the same problem I had flashing the Hard Key Mod file and to see if there is any method to set up 3.0.0.6 on the emmc so that I don't have to insert the 1GB SD every time I wanna flash CM7 nightlies.
rickpref said:
After setting up CM7 Nightly 4 last night I replaced the SDcard with CWM 3.0.0.6 used to install CM7 with a fat32 8gb for storage.
Afterwards I installed ROM Manager and the latest Recovery included - 3.0.0.5.
I am able to flash Dalingrin's latest kernel through here but when I went to flash todays Nightly CM7 it did not work (probably because of the 3.0.0.5 i figured). I plugged back in the 1GB SD with 3.0.0.6 and successfully flashed todays nightly.
I then tried to flash the Hard Key Mod file using the emmc recovery and it did not work so I copied it to my 1GB SD and that worked.
Anyways...I wrote this just in case someone was having the same problem I had flashing the Hard Key Mod file and to see if there is any method to set up 3.0.0.6 on the emmc so that I don't have to insert the 1GB SD every time I wanna flash CM7 nightlies.
Click to expand...
Click to collapse
My assumption (it may be wrong, as I do not have my nook present with me to confirm) is that the system partition on the CM7 builds is ext4, and as a result, 3.0.0.5 would not be able to access it to flash any data. flashing either the cm7 nightlies or my additions, both of which write to this ext4 partition, needs to be done via 3.0.0.6.
That being said. I personally managed to get 3.0.0.6 to work on my emmc by taking the uImage and uRamdisk from the SD card version, renaming them uRecRam and uRecImg, and copying them to the eMMC boot parition. I would not recommend doing this without knowing *Exactly* what you are doing, as overriding these files with other files could cause bad things to happen, and as I said above, bad things are bad.
EpicFail236 said:
My assumption (it may be wrong, as I do not have my nook present with me to confirm) is that the system partition on the CM7 builds is ext4, and as a result, 3.0.0.5 would not be able to access it to flash any data. flashing either the cm7 nightlies or my additions, both of which write to this ext4 partition, needs to be done via 3.0.0.6.
That being said. I personally managed to get 3.0.0.6 to work on my emmc by taking the uImage and uRamdisk from the SD card version, renaming them uRecRam and uRecImg, and copying them to the eMMC boot parition. I would not recommend doing this without knowing *Exactly* what you are doing, as overriding these files with other files could cause bad things to happen, and as I said above, bad things are bad.
Click to expand...
Click to collapse
Yeah, I figured it had to be that EXT4 partitions are not compatible with 3.0.0.5 but it took me a while to get it. So I take it you need to use ADB in order to rename and copy to boot those files?
rickpref said:
Yeah, I figured it had to be that EXT4 partitions are not compatible with 3.0.0.5 but it took me a while to get it. So I take it you need to use ADB in order to rename and copy to boot those files?
Click to expand...
Click to collapse
My ADB machine was down and out at the time, so I had to do it via ES file manager and the terminal on the nook itself, but yeah, manual replacement was the way to go. sometimes a bit of command-fu is just easier than the alternative.
digitalslacker said:
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
Click to expand...
Click to collapse
I use Volume Widget by Futon Redemption. It gives you two little onscreen +/- buttons to adjust the volume.
Mod Edit: Thread closed by @Darth . Pay per click links are not permitted on XDA.
XPOSED FOR LOLLIPOP (CM 12.1 AND BASED ROMS)
XPOSED FOR LOLLIPOP (CM 12.1 AND BASED ROMS)
Step 1: Download Necessary Files
There are two core elements to Xposed—one is the Xposed Framework, which lays all of the groundwork, and the other is the Xposed Installer app, which allows you to download and manage modules. First up, grab a copy of the Installer from the following link:
Xposed Installer APK
In these early stages of Lollipop development, the Framework will have to be flashed in custom recovery. There are 3 different version of the Framework, and they each correspond to a different type of processor (ARM, ARM 64, x86). If you're not sure about the type of processor your Android device uses, check the spec sheet on a site like GSMArena, then download the corresponding ZIP file from one of these three links:
Xposed Framework ZIP
Step 2: Boot into Custom Recovery
When the files have finished downloading, the next step is to boot into custom recovery. To do that, start by powering your device completely off. This next part may vary, but for most devices, press and hold the volume down and power buttons simultaneously.
This will bring up Android's Bootloader menu. From here, use the volume down button to highlight "Recovery mode," then press the power button to select it.
Step 3: Install the Framework in Custom Recovery
Before you flash anything in custom recovery, it's always a good idea to make a full NANDroid backup. That's extra important in this case, since the Xposed Framework is in its early stages and may cause issues with some devices. Do not skip this step!
Then, to get started, go ahead and tap the "Install" button from TWRP's main menu. Next, navigate to your device's Download folder, then select the Xposed ZIP file that you downloaded in Step 1.
After that, just swipe the slider at the bottom of the screen to install the Framework, and when that's finished, tap "Reboot System."
Your device will take longer than normal to boot up here. This is because the Xposed Framework ZIP had to clear away some library files, which will need to be restored. Expect this process to take at least 10 minutes.
Step 4: Install the Xposed Installer App
When you get back up, it's time to install the actual Xposed Installer app. Tap the Download Complete notification for the "XposedInstaller_3.0-alpha3.apk" file, then press "Install" and "Open" on the next two menus.
At this point, you should be looking at that familiar Xposed interface we all know and love. Head to the "Download" section to begin browsing modules, but keep in mind that some may not work on Lollipop.
links to download
credits : to all those who helped me and xda members who made these files
XDA:DevDB Information
xposed module for cm 12.1 and other based roms, Xposed for all devices (see above for details)
Contributors
manhar2108
Source Code: REMOVED BY MODERATOR
Xposed Package Name:
Version Information
Status: Alpha
Current Beta Version: 4
Created 2015-07-15
Last Updated 2015-08-22
@manhar2108
why do we need another forum page the xposed devs page is here
http://forum.xda-developers.com/showthread.php?t=3034811
toolhas4degrees said:
@manhar2108
why do we need another forum page the xposed devs page is here
http://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
not for sdk 22 devices sir
this is for sdk 22 mtk 6592 and other mtk65** devices
Hello all,
First of all the credit of this mod goes to @nuuits at this forum.
With this mod you can disable or enable the Navbar which is not really needed if you have pie control.
Flash "enableNavbarG4" in TWRP to enable the navbar.
Flash "disableNavbarG4" in TWRP to disable the navbar.
Download and install LMT Launcher from here to get pie control.
Cheers!
You could also disable navigation bar by adding the line "qemu.hw.mainkeys = 1" at the end of the build.prop. If you ever need it back again, just remove the line.
0rigin said:
You could also disable navigation bar by adding the line "qemu.hw.mainkeys = 1" at the end of the build.prop. If you ever need it back again, just remove the line.
Click to expand...
Click to collapse
Sure you can do that - this does the same thing but just with a flash.
Ahh, only now I've checked the links. Yeah I guess it's more or less the same.
Except that I have a phobia and don't wanna flash stuff unless I know exactly what it is and I actually need to. :]
Thank you for crediting me!
0rigin said:
Ahh, only now I've checked the links. Yeah I guess it's more or less the same.
Except that I have a phobia and don't wanna flash stuff unless I know exactly what it is and I actually need to. :]
Click to expand...
Click to collapse
Very understandable. I created this to be an easier (lazier?) way of doing that, and there were extra steps to enabling the navbar (+ disabling capacitive keys) on the HTC One M7, so this actually made the process much quicker for that device.
The navbar enabler zip comments out the physical key layout lines so the capacitive keys on the M7 are effectively disabled. Then I created a script to add the relevant line to build.prop (so nothing else is overwritten or changed) that executes while flashing. The disabler zip replaces the key layout file with the original, re-enabling the capacitive keys. The script removes that line while keeping the build.prop intact.
The G4 doesn't have capacitive keys, so the key layout files are not relevant to this device. I'm attaching a modified zip to this post that has the capacitive key stuff removed. Please feel free to add the attachments to your post, @MrCreel
nuuits said:
Thank you for crediting me!
Very understandable. I created this to be an easier (lazier?) way of doing that, and there were extra steps to enabling the navbar on the HTC One M7.
The navbar enabler zip comments out the physical key layout lines so the capacitive keys on the M7 are effectively disabled. Then I created a script to add the relevant line to build.prop (so nothing else is overwritten or changed) that executes while flashing. The disabler zip replaces the key layout file with the original, re-enabling the capacitive keys. The script removes that line while keeping the build.prop intact.
The G4 doesn't have capacitive keys, so the key layout files are not relevant to this device. I'm attaching a modified zip to this post that has the capacitive key stuff removed. Please feel free to add the attachments to your post, @MrCreel
Click to expand...
Click to collapse
Thank you man, really appreciate it
Build.prop
0rigin said:
You could also disable navigation bar by adding the line "qemu.hw.mainkeys = 1" at the end of the build.prop. If you ever need it back again, just remove the line.
Click to expand...
Click to collapse
How can I do that? Where do I find the build.prop? Do I need root? Thanks!!!
Kleber Ancona
kancona said:
How can I do that? Where do I find the build.prop? Do I need root? Thanks!!!
Kleber Ancona
Click to expand...
Click to collapse
You need Root, You find it in /system
Does the Google swipe up still happen lmt has a hard time opening with that still running
Anyone confirm that its there or is it gone, lmt has a hard time working with Google swipe up
cyan pac said:
Anyone confirm that its there or is it gone, lmt has a hard time working with Google swipe up
Click to expand...
Click to collapse
Install "LG PIE Support" if you have xposed to remove the Google swipe up.
LG Pie Support is working, even when its last update was 2014 [emoji14]
So I'm using lmt pie launcher and tried to make the dual window pop up one of the short cuts but to no avail. Anyone able to do this?
Sent from my LG-H811 using Tapatalk
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
4: Custom Roms
What are custom roms? Simply put they are modified versions of Android containing advanced tweaks, stability, and performance. Custom Roms are device specific for the most part. In other words, a Rom for the Moto G6 Plus will not work on a Moto G6 or G6 Play. There are a few exceptions to this rule, but they do not apply to the Moto G6 family so I won’t get into detail about it here. As of Android 8.0(Codename Oreo), Google has redesigned the framework of Android with a system called Project Treble. I will get in to that more later on in the Generic System Image(GSI) section of this guide, but to quickly summarize, it means Custom Roms that do not have to be built to be device specific. For a more detailed analysis of custom roms you can read the information in the spoiler tags below.
Spoiler
Android is a free open source software(FoSS)! This means anyone, anywhere in the world can help contribute to Android. This allows developers to add, remove, or modify the source code, and even publish there modified source code for others to use. The most popular example of this is called LineageOS(formerly CyanogenMod(CM)). At one point it was reported over 50 Million people ran CM! Why did 50+ million people decide to ditch the standard Android software provided by the phone’s manufacturer? There are a number of reasons such as :
Bloatware: Stock firmware is commonly infested with applications installed by your carrier to generate more revenue. Rom’s do not have this problem.
Updates: Android updates typically require approval by the carriers as they want certain functions disabled (tethering for example), to make you pay extra for this feature. Since carriers have they final say when updates are pushed out to devices, and wanted bloatware installed, etc, users were lucky to receive security updates. Users were even luckier to see a version update (Oreo to Pie for example). Rom’s do not rely on a carrier to be updated.
Stability: Since users were lucky to receive updates, you were forced to live with bugs for a long periods of time. Maybe even the entire life of the device. Since Custom Roms receive regular updates, this means bugs were fixed in a timely manner.
Performance: Custom roms are usually more optimized for the hardware they run on then stock roms. They may overclock your phone’s processor(CPU) to make it function faster then it was originally designed.
There are other various reasons but you get the idea.
For a list of features added to LineageOS (read this). Other roms may or may not include these features and more!
So how do you install a custom rom? Currently Moto G6 Plus users have access to LineageOS 15.1 (Based on Android 8.1). LineageOS 16(Android 9 Pie based) is in the development stage. There is no time line on a release just yet so not ask for an ETA! Let’s get started!
Downloads:
++Download these files to your PC.
*ADB and Fastboot Installer for Windows - (Download) - When prompted to install a driver type the number 0 and hit enter. This will install the latest version of adb and fastboot where it is system-wide. This eliminates the need for adb.exe or fastboot.exe to be in the same folder as the files you will be working with. NOTE: Windows will flag this as a virus! The installer is open source and made by a Moderator here on XDA. It is a False Positive. You can view a VirusTotal report (HERE). 26 out of 67 virus scanners report it as a virus. If your Anti-Virus is one of the ones that flag it as a virus, I would suggest you explore other Anti-Virus software, but that’s not what this guide is about.
* TWRP - (Download) - This is a modified Recovery Software allowing you to flash files that will allow you to fipe your device and install custom roms and other various things. Thanks to XDA Member @erfanoabdi who has ported it to our device.
++Download these files to your phone’s sdcard(Do not place them on the internal storage)
*Magisk - (Download) - Download the Stable version here. While not required, I do suggest you download the Latest Uninstaller and Latest Magisk Manager as well.
*copy-partitions-AB.zip - (Download) – Our phone is what’s known as an A/B device. This translates into slot_a and slot_b. The means we have a system_a partition and a system_b partition for example. By default some of these _b partitions are empty. This will populate these empty partitions with a copy of the data on the respective _a partition to help prevent you from bricking your device!
*LineageOS 15.1 [Unofficial] – You have 2 options:
lineage-15.1-20180811-UNOFFICIAL-evert.zip – This version was built on August 08 2018 by @erfanoabdi and @rahulsnair who are the real developers for the Moto G6 Plus.
lineage-15.1-20181003-UNOFFICIAL-evert.zip – This version was built on October 03 2018 by me Xplorer4x4. This version uses the same device specific binaries and source code @erfanoabdi and @rahulsnair used, but uses updated LineageOS source code. This is a bug fix release and does not include additional features.
Gapps – These are Google Apps like YouTube, PlayStore, Gmail, and more. -Again you have two options:
-OpenGapps – (Download) – Personally I prefer OpenGapps as you can customize which apps you want to install. The only downfall is that when you flash an update to LOS, you will have to flash Gapps again. In the Platform Column choose ARM64, in the Android Column choose 8.1, and then you can choose any Variant. I personally use the Nano Package and manually install the Gapps I want form the Play Store.
-MindTheGapps – (Download) – What you get is what you get. You don’t get to choose which gapps are installed, but if you flash an LOS update in the future, you won’t have to flash them again.
Please keep reading for detailed instructions on how to install LineageOS 15.1.
WARNING: This will wipe out all apps and data stored on your phone! It will not wipe your SD Card. Any apps purchased/installed from the Play Store can be restored using WiFi or LTE when you are done installing a ROM.
Known Bugs: Everything works except making calls with Bluetooth devices.
Instructions:
*On the device:
4A: Open the settings app and navigate it in this order: System -> About.
4B: On the About screen scroll down to Build Number and tap on it 5 times. You will see a notification at the bottom of the screen that says “Developer Options Enabled.”
4C: Tap the back button, and open Developer Options.
4D: Find “Android Debugging” and enable it.
*On your PC:
+Windows:
4E: Using Windows Explorer, navigate to the location of twrp-3.2.3-42-evert.img. Hold the Shift Key on your Keyboard. While holding Shift, Right Click in the window(not on the file). Depending on your windows version you should see either "Open PowerShell Window here" or "Open Command Window here." Select which ever one applies. You will see a black and white screen or a blue and white screen. The steps are the same no matter which screen you see.
copy-partitions-AB.zip
+Linux:
4E: Using your favorite terminal interface, navigate to the location of twrp-3.2.3-42-evert.img.
+Linux + MAC + Windows:
4F: Simply type(or copy and paste) the following command:
Code:
fastboot boot twrp-3.2.3-42-evert.img
*On your device(it should be booted in to TWRP at this point):
Create a TWRP Backup: Tap Backup -> Select Storage -> Micro SD Card - > OK. You will see a section that says "Select Partitions to Backup." Make sure to select all of these boxes. At the bottom of the screen Swipe the Blue Button where it says “Swipe to Backup.” When this is done, tap the Home button.
4G: Now tap on "Select Storage," select Micro SD Card, and tap OK.
4H: Navigate to the location of the copy-partitions-AB.zip and tap on the zip.
4I: Swipe the blue arrows button next to “Swipe to confirm Flash.”
4J: Tap the home button.
4K: Tap Wipe → Format Data(Do not tap Advanced Wipe, or Swipe for Factory Reset).
4L: Type yes
4M: Tap the blue check-mark in the bottom right corner.
4N: Tap Home button.
4O: Tap Install->Select Storage→Micro SD Card→OK
4P: Tap lineage-15.1-20180811-UNOFFICIAL-evert.zip or lineage-15.1-20181003-UNOFFICIAL-evert.zip
4Q: Swipe to install.
4R: When flashing is done, tape the home button.
4S: Tap Wipe→Format Data→Type yes→Tap Blue Check Mark at bottom right corner.
4T: Tape Home button when done.
4U: Tap Reboot → System
Congratulations, you have installed Lineage OS but we are not done yet! Let the device boot until you see the LineageOS Welcome screen. Note that the first time booting up a custom rom will take longer then a typical reboot. It should take no more than 5 minuets to complete!
Once on the LineageOS Welcome Screen, you can complete the setup or reboot back to your bootloader. Once the device powers off, hold the Power Button and Volume Down button until the bootloader displays on the phone screen.
4V: Boot TWRP again:
Code:
fastboot boot twrp-3.2.3-42-evert.img
4X: Tap install and navigate to the directory where you placed your gapps.zip and Magisk.zip.
4Y: Tap the Gapps.zip and choose add More zips.
4Z: Tap the Magisk.zip and Swipe to install.
We need to Wipe->Format Data one last time or else your Gapps will give you multiple errors when you boot LOS again. Once you have Formated Data, you can now reboot to system and enjoy LOS!
Small error?
Thanks for the effort that's gone into this post.
Just a quick editing note: the link to download Magisk (https://androidfilehost.com/?fid=5862345805528069013) seems to point to twrp-.2.1-37-evert.img rather than Magisk.
Detailed excellent guide. Almost everything covered.
Btw what advantage this twrp 42 holds over the one from twrp site?
JaggedPill said:
Detailed excellent guide. Almost everything covered.
Btw what advantage this twrp 42 holds over the one from twrp site?
Click to expand...
Click to collapse
Use the version from twrp website. I haven't had a chance to update the guide. Encryption is supposed to work on official twrp but I think myself and other testers verified encryption is not working right now.
Sent from my Phh-Treble vanilla using Tapatalk
What are the steps to compile for this device? Can you provide that information please? I have compiled for others, but this one is new to me and I think you use some configuration or additional files.
@Xplorer4x4 can you provide me your local_manifest file?
Does anyone know if we have any microg rom options for the Moto G6 plus?
Followed your instructions, after step 4U the device stays completely dark, no bootloader, no volume down + power key helps, nothing.
tmr2020 said:
Followed your instructions, after step 4U the device stays completely dark, no bootloader, no volume down + power key helps, nothing.
Click to expand...
Click to collapse
Try one of the following options:
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/
The second one is the official Rescue Tool from Lenovo. Read the user's guide first. I don't know why your phone is dead, but this might help you.
WoKoschekk said:
Try one of the following options:
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/
The second one is the official Rescue Tool from Lenovo. Read the user's guide first. I don't know why your phone is dead, but this might help you.
Click to expand...
Click to collapse
Thanks, I discovered the first thread after stopping banging my head against the wall. It actually worked. I can now use fastboot and adb etc. again. AFAIK, it is not possible to flash twrp recovery, it has to be booted on demand with adb/fastboot? I tried flashing lineage recovery instead, maybe I should not have done that, idk. Anyways it still booted to fastboot after that. I also seem to be confused by the a/b scheme.
Anyways I started all over with the copy-partitions-a-b (as I had a completely broken system, I cant imagine syncing the gargabe between a and b would help much?) and flashing lineage 17.1 again. It now boots to lineage. I rebooted to fastboot/twrp again to sideload opengapps (are they a/b compatible yet?!).
And how do I get a working recovery system again? I can't flash twrp? Can I flash lineage-recovery? Or something else?
And what does "active a" in twrp actually mean? That it will flash to "b"? Or that it will flash to "a"?
---------- Post added at 07:50 PM ---------- Previous post was at 07:34 PM ----------
I has just booted once to LineageOS, after trying to install Gapps, it's stuck in a bootloop. Going to twrp and selecting either A or B and then clicking on reboot, warns "no os installed"!
What am I doing wrong?
What am I doing wrong?
Click to expand...
Click to collapse
Get informations about A/B partitions (seamless updates) and how it works.
You must flash the GApps before our first boot into system.
bom Diagood morning i am stuck in the boot animation of Lineage 18.1 it does not install at all but other custom good piexel base PE style installs normal what can i do wrong ??
Rafinha863 said:
bom Diagood morning i am stuck in the boot animation of Lineage 18.1 it does not install at all but other custom good piexel base PE style installs normal what can i do wrong ??
Click to expand...
Click to collapse
Did you follow the install instructions on the official LineageOS web page?
WoKoschekk said:
Você seguiu as instruções de instalação na página oficial do LineageOS?
Click to expand...
Click to collapse
sim eu seguiyes I followed everything risks the process by adb sideload and completed but when starting the ROM it does not boot is only in the boot animations of Lineage
Rafinha863 said:
sim eu seguiyes I followed everything risks the process by adb sideload and completed but when starting the ROM it does not boot is only in the boot animations of Lineage
Click to expand...
Click to collapse
if it's an endless bootanimation then try to force reboot the device by holding the power button for 10-15 seconds.
WoKoschekk said:
se para uma animação de inicialização sem fim, tente forçar a reinicialização do dispositivo de bloqueio o botão liga / desliga por 10-15 segundos.
Click to expand...
Click to collapse
I already did this procedure and it didn't work either
Rafinha863 said:
I already did this procedure and it didn't work either
Click to expand...
Click to collapse
Latest stock ROM installed? Did you format (not only wipe!) /data?
WoKoschekk said:
Mais recente ROM de estoque instalada? Você formatou (não apenas limpe!) / Data?
Click to expand...
Click to collapse
yes I did data format every installation process correct but it is in bootanimation
WoKoschekk said:
Mais recente ROM de estoque instalada? Você formatou (não apenas limpe!) / Data?
Click to expand...
Click to collapse
Não te entendiI did not understand you are telling me to just format the date and not clean the system I noticed that in the function mount on the ceiling the actions of system vendor persist are all unchecked is this correct?
Rafinha863 said:
Não te entendiI did not understand you are telling me to just format the date and not clean the system I noticed that in the function mount on the ceiling the actions of system vendor persist are all unchecked is this correct?
Click to expand...
Click to collapse
Your internal storage is devided into several partitions e.g. /system, /vendor, /boot and /(user)data. The option format data is the same as the option factory reset. Both of them delete all your apps, settings and so on.
Your OS and all related Moto stuff is stored on /system (OS) and /vendor (Moto). By default they are unmounted, but could be mounted as r/w. If you delete them, you won't boot because no OS is installed.
So, after an annoying girlfriend and a boring Sunday at work I have pinpointed the solution to a very common issue with LG phones have after being flashed back from custom ROM's.
You're going to need Magisk Manager and Root.
1) Remove all fingerprints from fingerprint & security.
2) Remove lock screen (select none)
3) Download and add Magisk SELinux Manager:
https://forum.xda-developers.com/attachment.php?attachmentid=4440305
4) Open Magisk, go to Modules section hit ( + ) button and long-press the SELinux zip you just download. Now, hit open.
5) Follow the prompt, once asked to enter selection hit Permissive mode. Reboot and re-add lock screen and fingerprint.
Note: you may need to add the same finger twice to get it to work the first time, once working delete all fingerprints and re-enter.