Develop Bugs

[KERNEL][STOCK/AOSP][JB] LG Optimus F3Q

JB sediKERNEL for the LG F3Q (codenames: FX3Q, D520)
This is the JB stock Kernel build from the LG source code.
It is modified to be able to boot on a unlocked bootloader (loki) and may contain other features in the near future.
Current features (always for the latest version):
Same as stock but build from the sources
Compatible with the locked bootloader (means loki'ed)
XATTR enabled
SELinux enabled
dmesg will provide human readable timestamps (too)
KEXEC patches available (but not applied(anymore))
Will ignore crappy LG bootloader args
Will not do a AUTOMATIC HIDDEN factory reset when kernel panics occur
Will not enforce LG signed image anymore
AROMA flashing ZIP file available! This will flash the sediKERNEL into the right place (boot partition of course ) and wipe dalvik cache for you.
With this no "adb shell + dd" etc are needed anymore. Just flash the ZIP in twrp (read the instructions at the bottom of this post).
Take a preview look at the attached images (see bottom of this post!) of the installer process - as you can see this is really easy and straight forward, isn't it?
magic key feature for booting into recovery instead of normal boot! This superseedes all the problems regarding how to reach the recovery mode when the system is damaged!!
Usage instructions:
Power on the device
when you see the LG logo the first time do NOTHING!!
When the screen goes black THEN press Volume UP + Volume DOWN. Both the same time and hold them pressed.
Release the buttons when the screen goes black again
Wait. You will see the LG logo a third time and then you will see the recovery screen!
If you see a kernel crash then you have pressed the magic keys too early! Read and follow the above steps carefully and you should be fine.
No hacks anymore, no special installation instructions to workaround things, not breaking or damaging data or anything. Just using those keys and be happy!
Known issues (always for the latest version):
High (always for the latest version):
None (known)
Medium (always for the latest version):
None (known)
Minor (always for the latest version):
When booting up while the USB cable is connected you will see the charger image instead of boot directly - even when there is enough battery capacity. Simply press power button or boot without the cable connected.
Version >= 2.0: in rare situation when you use the magic key press (vol up+down) to boot into recovery a kernel crash can occur when you have not followed the instructions step by step. This is not a problem of the kernel! It is because of a timing issue of the hook used to get into recovery when you press the magic keys too early. Simply follow the instructions and you should be fine. If you still see a crash let me know and try it again it should really work the described way.
Development progress
sediKERNEL v3.0
Current progress:
Building a custom kernel without stock initrd (that means building an own initrd which works. atm I use the custom compiled Kernel + stock initrd)
Latest stable version: sediKERNEL v2.0
Download:
USE THAT ON YOUR OWN RISK!
ZIP flashable file (see instructions at the OP thread): sediKERNEL
DD Image file (see instructions at the OP thread): really? ok if you don't like AROMA open the ZIP and use the /kernel/sediKERNEL...lok file
Changelog:
For changelog see Changelog post
Previous versions:
see Changelog post
Installation Instructions (all versions)
Pre-Requirements (both methods)
Bravery & the will to change things for a better world
You should have rooted the device
You need either CWM (not my preferred choice) or TWRP installed (TWRP is highly recommended)
Method1: Based on ZIP (AROMA installer)
DO A BACKUP! For example execute: dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/STOCK_boot.img <- This will backup your current boot partition to your external SD card.
If you have adb installed (install it here if you like: @lifehacker) the command would be:
adb shell "su -c dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/STOCK_boot.img"
Download the sediKERNEL ZIP file
Extract that ZIP on your PC.
Copy or push BOTH files to your F3Q (the ZIP you extracted + the MD5 file).
You can do this by mount the F3Q normally and use MTP or adb if you like:
e.g when in booted stock ROM: "adb push ZIPfile /storage/external_SD/" & once again for the md5 file: "adb push MD5file /storage/external_SD/"
Reboot into recovery (e.g. execute: "adb reboot recovery")
Flash the ZIP & enjoy the magic
Done
Method2: Based on DD
DO A BACKUP! For example execute: dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/STOCK_boot.img <- This will backup your current boot partition to your external SD card.
If you have adb installed (install it here if you like: @lifehacker) the command would be:
adb shell "su -c dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/STOCK_boot.img"
Download the sediKERNEL Image file
Put that image file to your F3Q (e.g when in booted stock ROM: "adb push imagefile /storage/external_SD/")
Reboot into recovery (e.g. execute: "adb reboot recovery")
execute: dd if=/storage/external_SD/your-uploaded-imagefile of=/dev/block/platform/msm_sdcc.1/by-name/boot
wipe dalvik cache (IMPORTANT!). Example: "adb shell mount /data and then: adb shell 'rm -R /data/dalvik-cache' " when recovery has booted up.
Done
Sources:
My current kernel setup of the fx3q sediKERNEL build can be found here: kernel_lge_fx3q_aosp
.
XDA:DevDB Information
[KERNEL][STOCK/AOSP][JB] sediKERNEL for LG Optimus F3Q, Kernel for the General Discussion
Contributors
xdajog, joel.maxuel
Source Code: https://github.com/xdajog/kernel_fx3q_aosp
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v2.0_build28
Stable Release Date: 2015-05-13
Created 2015-05-19
Last Updated 2015-05-19

Changelog
sediKERNEL v2.0 (build28)
Enhancements:
Busybox (busybox_nonselinux_1.23.1) added to initial ramdisk (to get all the commands needed for the magic recovery boot keys)
Toolbox added (to get a working reboot command for the magic recovery boot keys)
added magic key press detection for booting into recovery! This superseedes all the problems regarding how to reach the recovery mode when the system is damaged!!
Usage instructions:
Power on the device
when you see the LG logo the first time do NOTHING!!
When the screen goes black THEN press Volume UP + Volume DOWN. Both the same time and hold them pressed.
Release the buttons when the screen goes black again
Wait. You will see the LG logo a third time and then you will see the recovery screen!
If you see a kernel crash then you have pressed the magic keys too early! Read and follow the above steps carefully and you should be fine.
ing those keys and be happy!
AROMA flashing ZIP file available! This will flash the sediKERNEL into the right place (boot partition of course ) and wipe dalvik cache for you. Enjoy
Fixes:
sediKERNEL version string was not optimal
Version was "Unavailable" at "About Phone" --> "Software Version" --> "Kernel Version". This was because the regex awaits "()" to filter out the correct version string. So the fix was to add build details into brakes and double escape CONFIG_LOCALVERSION string. Using EXTRAVERSION within the Makefile brakes Kernel module build when used.
Download:
USE THAT ON YOUR OWN RISK!
ZIP flashable file (see instructions at the OP thread): sediKERNEL v2.0
DD Image file (see instructions at the OP thread): open the ZIP and use the /kernel/sediKERNEL...lok file
sediKERNEL v1.5
Enhancements:
removed all kexec patches and kexec support because we do not need it atm (I want to avoid issues)
added version string to kernel (uname -a)
Fixes:
may fixes kernel crash in rare situations (kexec related)
Download:
USE THAT ON YOUR OWN RISK!
DD Image file (see instructions at the OP thread): sediKERNEL_JB-v1.5_build6.img
ZIP flashable file (see instructions at the OP thread): N / A
sediKERNEL v1.2
Enhancements:
Will ignore crappy LG bootloader args
Will not do a factory reset when kernel panics occur
Will not enforce LG signed image
Fixes:
This may fixes LG security errors (need feedback..)
May fixes a problem booting custom ROMs
Download:
USE THAT ON YOUR OWN RISK!
DD Image file (see instructions at the OP thread): sediKERNEL_JB-v1.2_26.img
ZIP flashable file (see instructions at the OP thread): N / A
sediKERNEL v1.0
Enhancements:
Same as stock but build from the sources
Compatible with the locked bootloader (means loki'ed)
XATTR enabled
KEXEC patches applied !
SELinux capable
Booting successful (tested on stock ROM)
Wi-Fi (tested on stock ROM)
Fixes:
TWRP is not unhappy anymore because of missing xattr and selinux
Download:
USE THAT ON YOUR OWN RISK!
DD Image file (see instructions at the OP thread): sediKERNEL_JB-v1.0.1.img

Reserved 2
IN THE MEANTIME YOU COULD USE THIS POST FOR ANOTHER THANKS CLICK

I appreciate all the work being done.
Would this be a solution to "Security Error" bootloops I am getting with my de-bloated ROM?

joel.maxuel said:
I appreciate all the work being done.
Would this be a solution to "Security Error" bootloops I am getting with my de-bloated ROM?
Click to expand...
Click to collapse
Possible but if you still getting security error bootloops when using this kernel then it may has something to do with a removed LG app.
It depends at which stage that security error occurs. If it appears directly when booting up it should not occur with sediKERNEL but if it booting up and you see the error then first it should be app related.
-----
Sent from my SGH-I927 using XDA Android mobile app

xdajog said:
Possible but if you still getting security error bootloops when using this kernel then it may has something to do with a removed LG app.
It depends at which stage that security error occurs. If it appears directly when booting up it should not occur with sediKERNEL but if it booting up and you see the error then first it should be app related.
Click to expand...
Click to collapse
Yeah, the error I received using the stock kernel threw before the boot animation occurred, but after the LG logo.
I read somewhere that the Security Error comes up when you even remove Videos.apk. Hopefully that is kernel related and will go away with sediKERNEL.

joel.maxuel said:
Yeah, the error I received using the stock kernel threw before the boot animation occurred, but after the LG logo.
I read somewhere that the Security Error comes up when you even remove Videos.apk. Hopefully that is kernel related and will go away with sediKERNEL.
Click to expand...
Click to collapse
Well there are 2 stages where the LG logo will be displayed:
1) When powering on the device -> that is a static LG Logo and is shown shortly after powering on
2) When booting the Kernel -> that is the same looking LG Logo but there is a little little animation on it
I think that you will receive that Security Error after stage 1 and before stage 2 so when booting the kernel and that should be fixed using sediKERNEL.

xdajog said:
Well there are 2 stages where the LG logo will be displayed:
1) When powering on the device -> that is a static LG Logo and is shown shortly after powering on
2) When booting the Kernel -> that is the same looking LG Logo but there is a little little animation on it
I think that you will receive that Security Error after stage 1 and before stage 2 so when booting the kernel and that should be fixed using sediKERNEL.
Click to expand...
Click to collapse
Oh okay. It must be ROM based then. Because I think I did get to stage 2 before the security error threw.

joel.maxuel said:
Oh okay. It must be ROM based then. Because I think I did get to stage 2 before the security error threw.
Click to expand...
Click to collapse
nevertheless it would worth to try the sediKERNEL

xdajog said:
nevertheless it would worth to try the sediKERNEL
Click to expand...
Click to collapse
Agreed. I will hold off until v1.5 is released since that one looks more promising.

joel.maxuel said:
Agreed. I will hold off until v1.5 is released since that one looks more promising.
Click to expand...
Click to collapse
Code:
Latest available version
sediKERNEL v1.2
Enhancements:
Will ignore crappy LG bootloader args
Will not do a factory reset when kernel panics occur
Will not enforce LG signed image
Fixes:
This may fixes LG security errors (need feedback..)
May fixes a problem booting custom ROMs
Ok no appologies anymore try it

So I noticed a couple things over the past few days with the kernel.
The first is minor. When doing a reboot from recovery you need to make sure the USB cable is disconnected. The impact is that the phone goes to charge mode if the cable is still connected.
The other, well, gives a real good reason to have the really bulletproof method with TWRP. The hotkeys to the bootloader no longer work. I was testing an AOSP keyboard with my ROM (think I know what to do now) when the setup wizard crashed continually, leaving me soft bricked. Luckily download mode still works.
So tonight I am using the spare, until I get the F3Q rooted, recoveried, and restored (again).
Not to complain, I really appreciate all the work done, thought you would want to know any drawbacks with the current version.
Sent from my MyTouch 4G Slide

joel.maxuel said:
The other, well, gives a real good reason to have the really bulletproof method with TWRP. The hotkeys to the bootloader no longer work.
Click to expand...
Click to collapse
Many thx for your feedback!
Hm interesting. I use method 2 and the hotkeys are still working. AFAIK those hotkeys are integrated in the bootloader and that one will never be touched by any method. Strange..
-----
Sent from my SGH-I927 using XDA Android mobile app

xdajog said:
Hm interesting. I use method 2 and the hotkeys are still working. AFAIK those hotkeys are integrated in the bootloader and that one will never be touched by any method. Strange..
Click to expand...
Click to collapse
There are so many hotkey variations across brands I lose track of the combo (keys pressed, how long). But I did try pwr +vol-dn, pwr + vol-up, even the three finger salute. Sometimes holding until the first LG logo shows, other times until the boot animation comes up (that's when I know I am screwed). I could still be doing it wrong...
Where is the bootloader stored anyway? Could it be that the opportunity for loading the bootloaders factory reset is during the kernel loading stage? TWRP kernel could still have those functions/flags. With a flipped boot and recovery image noted in method 2, that would make sense why your setup works.
Sent from my MyTouch 4G Slide

joel.maxuel said:
There are so many hotkey variations across brands I lose track of the combo (keys pressed, how long). But I did try pwr +vol-dn, pwr + vol-up, even the three finger salute. Sometimes holding until the first LG logo shows, other times until the boot animation comes up (that's when I know I am screwed). I could still be doing it wrong...
Where is the bootloader stored anyway? Could it be that the opportunity for loading the bootloaders factory reset is during the kernel loading stage? TWRP kernel could still have those functions/flags. With a flipped boot and recovery image noted in method 2, that would make sense why your setup works.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
The trick is to take out the battery , pressing vol+down and power while putting back the battery again. This will work 100%.
Any tries without putting out the battery may not work.
The bootloader is in "aboot" partition and i do not think it will have to do with the kernel. The reason why I can say that for near sure is that:
I tried to grab the key pressed while booting up which will be done in the init process. You can define things within an init script also key presses but they do not work while _booting_! They will work when booted up only so I tried to find out any other methods. The most meaningful would be to do that manually by writing a program to grab the key events. But at least I can say that I found no ressources about doing that other then described.
Because of that and because the bootloader steps into factory reset before kernel loads I do not think that there is anything kernel related. I think that the battery pull out will work in any case...
-----
Sent from my SGH-I927 using XDA Android mobile app

xdajog said:
The trick is to take out the battery , pressing vol+down and power while putting back the battery again. This will work 100%.
Any tries without putting out the battery may not work.
The bootloader is in "aboot" partition and i do not think it will have to do with the kernel. The reason why I can say that for near sure is that:
I tried to grab the key pressed while booting up which will be done in the init process. You can define things within an init script also key presses but they do not work while _booting_! They will work when booted up only so I tried to find out any other methods. The most meaningful would be to do that manually by writing a program to grab the key events. But at least I can say that I found no ressources about doing that other then described.
Because of that and because the bootloader steps into factory reset before kernel loads I do not think that there is anything kernel related. I think that the battery pull out will work in any case...
Click to expand...
Click to collapse
Okay, just to make things weird, I had an opportunity to do the trick. It did not work, and I had to use the LG tool again.
It seems to bypass those keys pressed. Luckily download mode still works, or else I'd be screwed royally.
So going off-topic, why did I kill my phone again? Well, it all has to do with the LG Keyboard (onscreen) failing. With the ROM I have posted, it's "Unfortunately, LG Keyboard has stopped" over and over again. Yesterday, I made a version of the ROM with the AOSP Keyboard APK replacing the Lucky Goldstar version. Same problem, except this time it's "Unfortunately, AOSP Keyboard has stopped" over and over again. Okay, so I finished the setup wizard, turned on developer mode, fired up ADB, deleted the AOSP Keyboard from the /system/app folder and installed it as a userapp. No problem. So I thought, hmmm, would this APK work if I fire it in the /system/apps/bootup folder and let it install as a userapp when the ROM first boots?
I was going to test that theory, but when I rebooted into recovery (with the debloated ROM without any keyboard apps), wiped userdata and cache, I mispelled recovery when I issued the adb shell command "reboot recovery". That made it reboot into system, and things went downhill once I could not get past the LG Setup Wizard that was continually crashing.
So, LG tool'ed back to stock, rooted, recoveried and I thought, before I restore my precious backup I should try the ROM I created, answer that question once and for all. I wiped userdata and cache, rebooted back into recovery (spelling correct this time), flashed it, rebooted, and....
AOSP Keyboard crashed once (or more), in between all the LG Setup Wizard force closes. So I backed out and restored everything (again). I now have two pieces of homework:
Find a way to have developer mode on by default, so I can make (potentially) changes to the ROM if I am in this situation again.
Investigate if LG Setup Wizard is even needed, as it is really annoying me right now. If it's not, consider it gone!
Solve these two, and I should have something a lot closer to beta.

joel.maxuel said:
Okay, just to make things weird, I had an opportunity to do the trick. It did not work, and I had to use the LG tool again.
It seems to bypass those keys pressed. Luckily download mode still works, or else I'd be screwed royally.
Click to expand...
Click to collapse
hm... yea download mode should work always as this is totally independent from that. But the main difference in the latest sediKERNEL is that it completely ignores the bootloader arguments.
I thought always that the "Factory Hard Reset" screen was/is hardcoded within the bootloader but your tests showing that this can not be (fully) true. You should at least SEE the screen where you need to confirm the factory reset then. Well that could mean it either checks for the existence of kernel or this screen IS from the kernel itself! At least the last one could be tracked I will investigate that theory because if that is the case then there would be a hook where we could load TWRP instead e.g...
...
Update: Ok search is over. There is no trace found withing the kernel sources or the end result which contains the factory hard reset strings.
That said I think the LG factory reset needs a working kernel available...
That is my theory but could be "easy" verified/declined by following those steps. Maybe if you get into that situation again you could try?
deleting partition "boot" (dd /dev/zero..). If factory reset is still showing fine (it could be enough to still have a kernel in recovery). If not well then we need a working kernel/boot image to reach factory reset and you can ABORT HERE..
Then flash sediKERNEL to the boot partition and verify that it is booting.
from there delete the recovery partition (dd /dev/zero..).
Try to get into the factory reset again. If the screen "Factory Hard Reset" is displayed fine (it could be enough to either have a kernel in recovery or in boot). If not then we need a working kernel/recovery image to reach factory reset and you can ABORT HERE..
boot into system again
Now the wicked part: delete recovery partition and boot partition (dd ..) --> THIS MEANS: SOFT-BRICKING! but it is the only way to say it for absolutely sure (if the above both tries still showing the factory reset)..
turn out the battery. try to open the factory reset.
If the screen "Factory Hard Reset" is displayed that would be a clear decline of my theory!
If you do not see the screen "Factory Hard Reset" then it means we need a working kernel / boot / recovery partition in order to reach the factory reset screen!
well and now you need to use the download mode again to unbrick the device of course..
So going off-topic, why did I kill my phone again? Well, it all has to do with the LG Keyboard (onscreen) failing. With the ROM I have posted, it's "Unfortunately, LG Keyboard has stopped" over and over again. Yesterday, I made a version of the ROM with the AOSP Keyboard APK replacing the Lucky Goldstar version. Same problem, except this time it's "Unfortunately, AOSP Keyboard has stopped" over and over again. Okay, so I finished the setup wizard, turned on developer mode, fired up ADB, deleted the AOSP Keyboard from the /system/app folder and installed it as a userapp. No problem. So I thought, hmmm, would this APK work if I fire it in the /system/apps/bootup folder and let it install as a userapp when the ROM first boots?
I was going to test that theory, but when I rebooted into recovery (with the debloated ROM without any keyboard apps), wiped userdata and cache, I mispelled recovery when I issued the adb shell command "reboot recovery". That made it reboot into system, and things went downhill once I could not get past the LG Setup Wizard that was continually crashing.
So, LG tool'ed back to stock, rooted, recoveried and I thought, before I restore my precious backup I should try the ROM I created, answer that question once and for all. I wiped userdata and cache, rebooted back into recovery (spelling correct this time), flashed it, rebooted, and....
AOSP Keyboard crashed once (or more), in between all the LG Setup Wizard force closes. So I backed out and restored everything (again). I now have two pieces of homework:
Find a way to have developer mode on by default, so I can make (potentially) changes to the ROM if I am in this situation again.
Investigate if LG Setup Wizard is even needed, as it is really annoying me right now. If it's not, consider it gone!
Solve these two, and I should have something a lot closer to beta.
Click to expand...
Click to collapse
In order to turn on the usb debugger mode: within your ROM zip file modify this file "/system/build.prop"
Code:
persist.service.adb.enable=1
Optionally:
if you want to do root commands over adb I/you could modify in the "default.prop" file which is within the kernel's initrd:
Code:
ADD: ro.secure=0
REMOVE (if exist): ro.debuggable=0
Regarding your keyboard FCs:
I remember that I had the same issues within my Captivate ROM I build. There I tried to add the Kii Keyboard to the stock ROM image and that resulting in the same FC's you describing. My solution was to use another keyboard (in my case it was a samsung one) so I would suggest that you could try around with another keyboard instead of the AOSP one...
Good luck

xdajog said:
hm... yea download mode should work always as this is totally independent from that. But the main difference in the latest sediKERNEL is that it completely ignores the bootloader arguments.
I thought always that the "Factory Hard Reset" screen was/is hardcoded within the bootloader but your tests showing that this can not be (fully) true. You should at least SEE the screen where you need to confirm the factory reset then. Well that could mean it either checks for the existence of kernel or this screen IS from the kernel itself! At least the last one could be tracked I will investigate that theory because if that is the case then there would be a hook where we could load TWRP instead e.g...
...
Update: Ok search is over. There is no trace found withing the kernel sources or the end result which contains the factory hard reset strings.
That said I think the LG factory reset needs a working kernel available...
That is my theory but could be "easy" verified/declined by following those steps. Maybe if you get into that situation again you could try?
deleting partition "boot" (dd /dev/zero..). If factory reset is still showing fine (it could be enough to still have a kernel in recovery). If not well then we need a working kernel/boot image to reach factory reset and you can ABORT HERE..
Then flash sediKERNEL to the boot partition and verify that it is booting.
from there delete the recovery partition (dd /dev/zero..).
Try to get into the factory reset again. If the screen "Factory Hard Reset" is displayed fine (it could be enough to either have a kernel in recovery or in boot). If not then we need a working kernel/recovery image to reach factory reset and you can ABORT HERE..
boot into system again
Now the wicked part: delete recovery partition and boot partition (dd ..) --> THIS MEANS: SOFT-BRICKING! but it is the only way to say it for absolutely sure (if the above both tries still showing the factory reset)..
turn out the battery. try to open the factory reset.
If the screen "Factory Hard Reset" is displayed that would be a clear decline of my theory!
If you do not see the screen "Factory Hard Reset" then it means we need a working kernel / boot / recovery partition in order to reach the factory reset screen!
well and now you need to use the download mode again to unbrick the device of course..
Click to expand...
Click to collapse
Hopefully I don't end up in that situation again. However if I do, I still wouldn't be able to complete the test anyway because I would have no way of issuing (root) console commands. If I did, I could just execute my backup (I dd my partitions for this reason) restore plan (and get out of the mess easily).
Then I re-familiarized myself with this:
Code:
Enhancements:
Will ignore crappy LG bootloader args
Will not do a factory reset when kernel panics occur
Click to expand...
Click to collapse
What if the strings are in aboot, but the kernel flags merely throw the kernel into aboot if triggered by the hot-keys?
xdajog said:
In order to turn on the usb debugger mode: within your ROM zip file modify this file "/system/build.prop"
Code:
persist.service.adb.enable=1
Optionally:
if you want to do root commands over adb I/you could modify in the "default.prop" file which is within the kernel's initrd:
Code:
ADD: ro.secure=0
REMOVE (if exist): ro.debuggable=0
Regarding your keyboard FCs:
I remember that I had the same issues within my Captivate ROM I build. There I tried to add the Kii Keyboard to the stock ROM image and that resulting in the same FC's you describing. My solution was to use another keyboard (in my case it was a samsung one) so I would suggest that you could try around with another keyboard instead of the AOSP one...
Good luck
Click to expand...
Click to collapse
I will try the build.prop suggestion. It won't give me superuser (maybe you could do the default.prop modification?), but I could still install apks, which would have gotten me out of at least one mess. Although su would be nice. Could you integrate the modified default.prop into your kernel? :fingers-crossed:
As for the keyboards, I wonder if it's a permission thing. I will have to look at that when I get home. To be honest, I didn't look at what the permissions are set to (should be rw-r--r--), and I could/should rename the file to LatinIME.apk. There may also be a old library that is getting in the way. I also have a line on a different keyboard. Looks nice, just in the process of asking permission to use it first (based off of Google Keyboard).

sediKERNEL v1.5 released
Maybe the last version I release because no testing device anymore from now on:
sediKERNEL v1.5
Enhancements:
removed all kexec patches and kexec support because we do not need it atm (I want to avoid issues)
added version string to kernel (uname -a)
Fixes:
may fixes kernel crash in rare situations (kexec related)
Download:
see OP !
cheers
xdajog

i have LG Optimus L5 last year for 3 month. and some developed on him.
Not good phone the L3-L5-L7 phones LCD Quality is very low

[SOLVED] Help Flashing Lineage OS

EDIT:SOLVED -- READ BELOW:
I finally got it flashed by following a few guides here which I will link, and try to break it down easier for someone else to come across and follow. I thought I bricked my phone (flashed LineageOS then rebooted, phone did not show anything on screen, full black screen) but after following a few guides I got it solved.
If you get bricked, or just want to follow a clean perfect install, please start below (Skip to step 2 if you are starting fresh, if you have soft-bricked your device start from step 1)
1. Bricked it and had to execute QDLoader 9008 fix again.
Tutorial is easier than it looks, do not fear, if you have soft-bricked your device and see a black screen, go ahead and go through the qdloader brick solution.
2. From factory recovery updated to Version WW-16.1220.1909.193.
If you have started fresh, I would highly recommend updating to the more updated firmware first. For me this worked, and I suggest updating to get a more current kernel, which may play better with Lineage OS install. To install a newer stock firmware linked above, download the ~2GB Firmware above, and save it to your Minimal ADB / Fastboot folder. Power off your device, after it has been successfully restored (if you bricked it) or you want to start off fresh and get the install right the first time. With your device powered off, Hold Volume UP and then Hold Power Button until the Fastboot menu appears. Use your volume keys to select Recovery, then press Power button to enter the STOCK Recovery (we are still on stock firmware with stock recovery). When in stock recovery select install from ADB. We are going to push the install via ADB (I tried dragging the firmware to the internal and selecting install ZIP and that didnt work).
Go into your Minimal ADB / Fastboot folder on your computer and open command prompt by holding Shift+Control and Right clicking and then selecting open command prompt here.
Now, enter the following command in the command prompt and hit enter:
adb devices
This command will show if any fastboot device is connected. If it doesn’t show, then please check the drivers are installed properly and try again.
If your device is listed, then type the command given below and press enter:
adb sideload File_name.zip
^^This will be the ~2GB Firmware file downloaded above
Wait until the installation process completes.
Once the installation process is complete, restart your device.
Done. You have successfully upgraded the Asus ZenFone 6 to the newer firmware, please continue.
3. Downloaded OTA 16.1220.1909.193 to 16.1220.1909.194, renamed it to UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip and placed into root of internal memory.
When I disconnected USB cable (or rebooted, not sure), I was prompted with update notification. I have updated it. Either way, reboot your device if you don't see the notification, and look in your notifications to see something saying: System Update Detected Proceed with Update - and select it and update.
4. Now that your phone is 100% Updated with the newest firmware, let's follow another guide I found here:
I assume you're on a fresh Android 9 stock ROM, or just finished restoring your phone with the Flashall_AFT.cmd from this tutorial.
You should at least boot once on the system, and disable any PIN or password to unlock your phone (hence putting a default password for the FBE).
Download the latest OFFICIAL TWRP.x.x.img (which we'll use to boot on it), and it's installer to install it later (TWRP.x.x.zip) if you want to use it.
LineageOS installation steps :
Reboot to bootloader (=fastboot mode), connect to your PC and boot on TWRP :
Command:
fastboot boot TWRP.x.x.img
Once on TWRP, you can see that we're on slot A (Menu > Reboot). Now go to wipe > factory reset and then wipe system (technically I suspect this only wipes slot A, but do it anyway, don't worry about the errors!)
Now go to Install > flash the newest official LOS_latest.zip. What happens here is that the LOS installer will flash LOS on the inactive slot (slot B in our case). And will also install the LOS recovery (on both slots it seems).
Reboot to recovery : your phone automatically switches slots and will boot the LineageOS recovery (Don't fear, we don't need TWRP right now, just go along with this step) on slot B.
On the LineageOS recovery, do factory reset (which seems to be a full /data format in fact, thus removing any previous encryption AND all your data on internal storage). If you want to use Magisk, go to the recovery's install menu and sideload it now
Use code:
adb sideload Magisk-v20.3.zip
Now reboot to system. It might take a while (one or 2 loops in my case), but your phone should boot, or in some cases will end up on LOS recovery asking for a 'factory data reset' (then do it and reboot again).
Once booted on your LOS rom, you can define a pin or password to lock your phone (that'll be the FBE decryption password).
Now if you want to use TWRP, reboot to bootloader and boot again on TWRP.img (step 1)
From TWRP > Install > flash TWRP.x.x.zip (that is, the TWRP installer). It installs on both slots by default. If you had installed Magisk, you have to flash it again (because anything modifying the boot.img - like the TWRP installer in our case - will erase it).
You can now reboot to system and enjoy LOS

Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.

abprie said:
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
Click to expand...
Click to collapse
Haven't actually put my sim in yet to make calls, will let you know later today, sorry about the delay!

I had previously attempted this a number of months ago, and managed to soft brick my Zenfone 6 several times, eventually kind of giving up and just using the stock firmware.
I tried again back on Memorial Day in the US. This time around, I bricked it hard. Could not get device to power on in any fashion. PC would not "see" USB connection at all.
I returned it to ASUS for service, and they've charged me a little over $200 to repair it. The only problem they noted was, "Device is rooted/unlock". So I have no way of knowing if their diagnosis is based on actual inspection of the device, or if they're just replacing the SOC on the basis that I used their official bootloader unlock tool, thus registering my phone's S/N.
Just a little caveat emptor for anyone attempting to use this guide. I was able to get TWRP to load, and succesfully updated the stock firmware, but any and all attempts to load the Lineage image failed.
Eventually one of them soft bricked my phone as before, and I think my mistake was interrupting the soft brick rewrite procedure by prematurely unplugging my phone from the PC.

I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realised the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I couldn't switch completely off, access recovery/fastboot, and my computer wouldn't recognise the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.

~SilverLad~ said:
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realized the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I could switch completely off, access recovery/fastboot, and my computer wouldn't recognize the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
Click to expand...
Click to collapse
Can you post a link to where you purchased the cable?

abprie said:
Can you post a link to where you purchased the cable?
Click to expand...
Click to collapse
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18

Since the thread is already on topic, could I flash lineage os while being on a custom rom? I have Bliss ROM on partition A and stock on B. Is it possible to have both Bliss and Lineage in dual boot?
Also, maybe a little off topic, the partition A/B scheme was intended to be used as a dual OS boot like normal PCs? Because right now I can select A and boot Bliss, select B and boot stock, I don't get why the procedure for flashing Lineage OS is so convoluted(requires having stock both on B and A?!) since both partition seems to be standalone and separated from each other.

~SilverLad~ said:
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Click to expand...
Click to collapse
Hey there, what's the process around using this cable?

vikashhero said:
Hey there, what's the process around using this cable?
Click to expand...
Click to collapse
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.

~SilverLad~ said:
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
Click to expand...
Click to collapse
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.

vikashhero said:
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
Click to expand...
Click to collapse
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...

~SilverLad~ said:
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
Click to expand...
Click to collapse
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.

vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
Click to expand...
Click to collapse
Happy to hear that Indeed be careful - this is a tricky phone...
vikashhero said:
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
Same here. It was so easy to do the Samsungs "back in the day", and you always had ODIN as a fallback if things went south. But this "A/B" partition nonsense (as well as other useless changes they introduce every time they "upgrade" Android, or certain structure modifications every so often when a new phone comes out) are a pain in the butt! Changes clearly aimed at making things more annoying/difficult for us people who don't want standard/corporate/unnecessarily bloated phones... Actually (as a former Blackberry user) I was tempted to get one of these Android based Blackberrys (the KEY2), but I didn't in the end precisely due to the fact that the bootloader can't be touched, and it can be rooted...

vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
I want to switch to because the latest security update (August 2020) by Asus is soft bricking the phone for many users,
but I am seeing a few reports about some bugs (like the phone is stuck in the lineage boot symbol and cellular errors) in lineage os and also seeing few post with a lot of installation errors (like soft and total bricking) etc. and for me in developers options I'm not seeing the OEM and advanced boot options.(in my asus stock os) I just found out that I have to download the Unlock Boot loader apk separately from asus and install it using command prompt so I don't know how to proceed.
Can you please elaborate on how you actually did it with your Asus Zenfone 6(2019), I am a total noob in this and I also couldn't understand the partition a and b parts too.

[GUIDE] [ROOT] Fix the Qualcomm CrashDump: Keep your data, apps and retain root.

This will not work if your phone bricked after updating to Android 12. You should use the MSM in this case. This guide details downgrading to an earlier version of Android 11 FROM a newer Android 11. You have been warned.
This evening after updating my phone (installing to inactive slot + flashing with Magisk as I have done many times before), I restarted only to receive a Qualcomm CrashDump.
Unlike what I've read online, my one seemed to be a bit more severe. I could not boot into recovery mode (black screen; had to power phone off) and entering Fastboot did not fix the issue. After spending several hours reading through XDA, Stack Overflow, various other sites etc I finally managed to get it fixed. Not only that, but I kept ALL my data AND my root. It's like nothing ever happened.
The issues I faced:
- Mistakenly had USB debugging off (which cannot be enabled when your phone is soft bricked). This made using ADB for initial diagnostics virtually impossible
- Recovery mode showed a black screen; not accessible.
- Installing TWRP, only to find my device passcode (PIN) wasn't allowing me to decrypt my phone data so I could make a backup
- My phone was buggered
How I solved it: Given recovery mode was blank, I flashed TWRP to my recovery drive via Fastboot to bring it back. Because USB debugging was OFF and TWRP wasn't decrypting my data (meaning I couldn't back up any data or download the ROM to my internal storage without wiping it), I activated ADB Sideload within TWRP and then used this to downgrade my version of OxygenOS! After a reboot I received the Qualcomm error one more time, before it continued to boot into OxygenOS with all my data intact.
Your bootloader should already be unlocked. If it isn't, chances are you will be saying goodbye to your data
These steps may not work for everybody, but I wanted to give back what I learned from this, and it was rather unconventional and against the grain of what others have suggested. With that said, do so at your own risk.
This is a simple guide. I will explain the tools you will need and how to fix the issue. Anything beyond that (i.e. installing SDK platform tools) can be researched.
This is written assuming you are on Windows, although the steps are generally quite similar.
Tools Needed:
A computer to download and install:
- SDK Platform Tools/ADB (https://developer.android.com/studio/releases/platform-tools)
- TWRP for OnePlus 8 Pro (https://forum.xda-developers.com/t/...wrp-for-oneplus-8-8pro-official-beta.4341707/)
- OnePlus 8 Pro Drivers (You will need this installed if it isn't already for your phone to appear in SDK Platform Tools. You may need to disable driver signature enforcement on Windows 10)
- The version of OxygenOS you were running before the CrashDump occurred (https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315/)
Steps to take - Initial Setup and Installation of TWRP:
1. Download everything above and then install SDK Platform Tools + OnePlus 8 Pro Drivers if you don't already have them.
2. Enter Fastboot mode on your phone and then connect it to the computer.
3. Ensure the TWRP .img file is in the same directory as your SDK Platform Tools install
4. Open up command prompt with SDK Platform Tools installed and type in
Code:
fastboot devices
Confirm your device ID appears along with "fastboot" beside it.
4. If the device is being recognised, we're ready to install TWRP. Note: Remember your Bootloader must be unlocked for the next steps. While in Fastboot mode, your phone will tell you if your bootloader is locked or unlocked. Now that we've confirmed it is unlocked, Type in:
Code:
fastboot flash recovery_a twrpname.img
followed by:
Code:
fastboot flash recovery_b twrpname.img
5. You can now boot into recovery mode! On your phone, use the volume keys to navigate and choose Recovery so you can enter TWRP
Downgrading to an older version:
When I installed TWRP, I was horrified to see that I couldn't decrypt my phone with my pin code. Apparently this is an ongoing problem with TWRP and the ability to decrypt your phone data varies between devices and builds of TWRP.
1. Now that you have entered TWRP, enter the "Advanced" settings and enable "ADB Sideload".
2. On the computer, type in
Code:
adb devices
. You should see your device appear.
3. Ensure the OxygenOS file is in the same directory as your SDK Platform Tools install
4. Type in
Code:
adb sideload updatename.zip
and let it flash to your phone.
And that's it! Reboot your phone. You may receive the Qualcomm error one last time, so kiss that sucker goodbye with a final reboot (I pressed power + volume up but then it continued to boot as normal; much to my surprise) and you should be good to go.
Hope this helps. This is my first ever guide, but my phone bricked itself this afternoon and it took me 3-4 hours of research to figure out what to do. This community played its role in helping me, and I'm sure someone out there will appreciate this information - definitely wanted to give back. I didn't see any information like this outside of wiping the phone entirely... I'm pretty stubborn and didn't want to do that.
This is definitely a "dirty flash", although given I couldn't even boot into the updated version, I would say a downgrade is definitely just fine in this instance.

I assume that you where using Android 11?
Because in the current situation with android 12 and hard bricking your phone with fastboot flashing this guide is potentially dangerous. As far as i know you should not flash twrp to android 12 right now.
Please correct me if i mixed things up here or if i am wrong. Its better to loose data and use MSM if you are concerned.
You might wanna include this guide in case someone needs to read it before doing anything.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Anyway thanks for your effort here.

xtcislove said:
I assume that you where using Android 11?
Because in the current situation with android 12 and hard bricking your phone with fastboot flashing this guide is potentially dangerous. As far as i know you should not flash twrp to android 12 right now.
Please correct me if i mixed things up here or if i am wrong. Its better to loose data and use MSM if you are concerned.
You might wanna include this guide in case someone needs to read it before doing anything.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Anyway thanks for your effort here.
Click to expand...
Click to collapse
Thank you and you're right. I've added this warning to the top of the post!

Looking for assistance, UNLOCKED dev test point

AT THE END OF THE DAY (week actually) this won't work for U.S. based phones as far as I could find. Huawei partitions etc. are all ****y and I can't update firmware beyond EMUI 8 because the sites are all down/gone so RIP me and my week of working on this dumb ****. Save yourselves, don't attempt if within the U.S.
I tried a billion things, but eventually I ended up taking my phone apart and getting access through the dev test point and potatoNV. Once fully unlocked I attempted to flash various images, but end up in boot loops until I reinstall EMUI. I'm presuming my problem is with finding a proper image? Let me know if you know otherwise, but I'm looking for latest Android version with GAPPS that will work on the Honor 7x please!
If you're reading this, just ditch the phone or deal with what you have. Leaving the following info in case anyone is stubborn enough to give it a shot, but I highly do not recommend it.

Taking notes for myself if no one comes out of the woodwork
I managed to reach the 313 logo (ducks), but froze there with https://github.com/phhusson/treble_experimentations/releases/tag/v313 (aonly GAPPS)

Still would love assistance/input. I've tried a bunch of different images including 'a only' and android 10, but still hitting issues. Not sure if SparseConverter is helping or hurting either

Tried
system-squeak-arm64-ab-gapps.img.xz
system-roar-arm64-aonly-GAPPS (chunked and not)
system-arm64-aonly-gapps-su.img
dotOS-R-v5.2-arm64-ab-GAPPS-OFFICIAL
system-quack-arm64-aonly-gapps = new android logo boot screen loading forever
Havoc-OS-v3.12-20201230-Official-a64-aonly - spooky, never got out of bootloader
For anyone else doing this, items I've read say that factory reset should be done before AND after flashing system.
I feel like there is a RAM limitation on some of these later android OS, but here's some more info
honor7x is KIRIN 659 arm64 a-only partition
POST FLASH INSTRUCTIONS
After entering the reboot command, your 7x will reboot and you will see the warning screen where it tells you that your device is unlocked. On that screen "PRESS AND HOLD THE VOLUME UP KEY" to boot into erecovery to perform a Factory Reset. If you do not, the phone will boot loop until it forces you too.
per https://github.com/phhusson/treble_experimentations/wiki/Huawei-Honor-7X#post-flash-instructions

I have been scrubbing the asshole of the internet to find this information.
honor7x is KIRIN 659 arm64 a-only partition
adb shell getprop ro.treble.enabled = true
HOWEVER
the device isn't fully VNDK-compliant (https://source.android.com/devices/architecture/vndk), and the device can use only the GSI for the same on-device OS version. For example, an Android 9 (API version 28) device that isn't VNDK-compliant can load only an Android 9 GSI image.
per https://developer.android.com/topic/generic-system-image
so we're (allegedly although I've seen otherwise) stuck with android 8 Oreo (in my case U.S.)
no TWRP download for 7x specifically...using 7 = 3.1.10 then
installed magisk https://forum.xda-developers.com/t/...10-mate-10-pro-huawei-treble-devices.3749280/ is a useful guide
Installation
The Magic Mask for Android
topjohnwu.github.io
https://androidfilehost.com/?fid=673956719939832043 = boot.img
adb push -p BOOT.img /sdcard/
(on the pull they ****ed up the _ and -)
device does not have a separate vbmeta partition, JUST KIDDING found one at /dev/block/platform/hi_mci.0/by_name when checking for boot
adb reboot fastboot
trying with recov because boot gave me partition length get error...
(img1)
idk at this point because a lot of people have TWRP that I'm unable to get because of this^ and I don't think this garbage phone even has a boot partiton? (img2) but has two recovery partitions per https://forum.xda-developers.com/t/honor-7x-bricked.3973247/

aw this: https://forum.xda-developers.com/t/oreo-twrp-complete-backup.3764500/
but also saw:
https://www.reddit.com/r/honor7x/comments/ao2qkd
(large comment about spending 36 hours from currently named user PMmeYourFlipFlops)
Android Booting Shenanigans
The Magic Mask for Android
topjohnwu.github.io
probably a type III device for magisk...
adb pull recovery_ramdisk
adb pull ramdisk
didn't work
grab path for twrp
/storage/sdcard0/Download/twrp-3.1.1-0-plank.img
flashing recovery gives same partition length get error
fastboot flash recovery_ramdisk twrp.img
STOP HERE pretty sure this is the step where I screw myself and at least my phone still uses safe mode, but I don't have a recovery.img
imagine drowning phone by holding vol +, vol -, and pow. get spooky err screen (no recovery img failed)
got emui screen
hold pwr vol + to get normal (not ereco) recovery. Still ****ing boned so trust pmMeYourFlipFlops at this point.

I'm currently on emui 8 vendor
TWRP For Emui 8: https://forum.xda-developers.com/t/...e-unofficial-twrp-3-2-1-0-28-04-2018.3783447/
ROMS I have tried:
Havoc OS Arm64-aonly: https://forum.xda-developers.com/t/...ab-arm-arm32binder64-updt-2019-09-14.3930030/
AOSP 9.0 v123 -- system-arm64-aonly-vanilla-nosu.img.xz: https://github.com/phhusson/treble_experimentations/releases/tag/v123

Descendant OS 4.0.1: https://forum.xda-developers.com/t/sp-aug-r47-descendant-4-0-1-for-treble-enabled-devices.3840578/

You can also try this roms: https://github.com/erfanoabdi/ErfanGSIs
Remember to download arm64-aonly for emui 8 and arm64-ab for emui 9

How To Guide Asus ROG Phone 6 / 6 Pro [ROOT GUIDE/SUP]

Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.

Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?

leathan said:
Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.
Click to expand...
Click to collapse
Sorry, I messed with the reply: it's my previous post.

fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?

fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.

leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course)

leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
leathan said:
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.
Click to expand...
Click to collapse
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?

fux1976 said:
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?
Click to expand...
Click to collapse
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.

leathan said:
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.
Click to expand...
Click to collapse
Phone looks certified, country WW, safetynet passed and upgraded to .160. Only 2 problema left: voice dictation of GBoaed and Android auto not working.
I tried several ways but they didn't solve. Voice dictation worked and then stopped: I guess something interferes... Android Auto app crashes although phone connects to car and is recognised.
Very strange behaviour...
Do you have any idea on how to reflash last .160 zip without twrp? Once installed it gets ignored by system when saved in home directory...
Everything else is working properly.

Isn't Android Auto no more (i.e discontinued).....?

elmor0 said:
Isn't Android Auto no more (i.e discontinued).....?
Click to expand...
Click to collapse
what?!? where did you hear that? It'just something causing problems (compatibility issues with app or setting: magisk, modules, adaway, skipad, disabled system apps and so on). If I could manage to reflash the stock rom it'll work again (I hope)

fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly

finallau said:
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly
Click to expand...
Click to collapse
I only have raw for .143 but I updated to .160*...can I use the previous version or do I get bricked? I don't trust anti roll back mechanism. I can live with this 2 "limitations" waiting for twrp and then be able to flash zip with no hassle.
*I downloaded source code from the Asus site but not sure how to use it (and unzipped is around 10 gb )

Thank you for this! I've been out of the root game for years but noticed with your post that I can hide root from Google Pay and my banking apps, so thinking of trying this. One question though - you mentioned that official updates need to be manually downloaded and the phone re-rooted. Would this wipe the phone each time?

fastboot driver doesnt support win64

Will the phone do a factory reset after unlocking the bootloader?

Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route

MrKioFLow said:
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
Click to expand...
Click to collapse
Yes, if you unlock the bootloader using the bootloader unlock app (which is a step that is missing in the original post), your phone will perform factory reset.

Troubleshooting​
Once you boot into the bootloader with the adb reboot bootloader command, stay on the screen with the green START. Do not navigate to the fastbootd.
Use the side USB port to connect to your computer - not the bottom one.
Run the adb and fastboot commands in Command Prompt as Administrator.
Before you reboot into bootloader, remove Lock screen in Settings.
If you execute fastboot flashing unlock and you got FAILED (remote: 'permission denied'), just ignore it.
It's always better to install the latest updates, then download the firmware to your PC from ASUS Webpage and extract the boot.img and patch it in Magisk in the phone using this tutorial.

Thanks for the guide! Should add that you have to use the side port for fastboot to see the device. Was stuck for a while trying to figure out why neither mac nor pc couldn't find it when it was in bootloader mode - it was because I was using the bottom port lol!
Also if you want to disable verity and verification for the verified boot images, you have to do for both vbmeta.img and vbmeta_system.img. Didn't boot for me until I did that, and had to do an additional factory reset from recovery because of this.