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

Moto G5 XT1676 Rooted - Camera and Flash hardware not even being detected

I got my phone a few days ago and rooted it, installed most stuff etc.. So far I have TWRP and Magisk 14.0 Root active on it, not much else I can think of. The phone is running Android 7.0.
I left the Camera for last to check and when I did I noticed neither the camera nor its flash are responding. ("camera busy" error, other full-fledged cam apps showing black) I went through the initial steps of disabling OK Google's camera settings, disabling a bunch of apps that had cam access, checking safe mode etc. and none of them worked.
Finally I went into Device Helper's hardware list and noticed under "Imaging" there isn't even a camera listed. I don't know how the app works but even with cam busy it would at least be listed. I went through a few other hardware spec listing apps and all of them showed absolutely no camera hardware. Interesting enough, I know the phone has 2 cameras, I'm not sure if they're a single unified piece of hardware or not but there was no such thing as back or front camera even, there was quite simply nothing listed under camera.
At this point I'm left to wonder if the problem is either a setting or something to do with rooting, or actual hardware fault. Unfortunately having rooted the device, I also have no warranty for it.
I welcome any ideas, advices, anything about trying to detect or diagnose camera issues. If there were a TWRP way of checking the camera hardware, I'd be glad to try it out since it would rule out anything having related to the Android OS, or other versions of Magisk. 11.6 was recommended but it never worked for me. This is all before I open up the phone. I can't much afford much to do a factory reset at this point and would like to leave it as the last resort.
In the event of a camera issue, I'm of course hoping it's as simple as a loose connector, but I'd like to know of any known G5 hardware issues with the camera and if there's documented fixes.
Also in the event I DO have to do a hard reset - do I have a reliable way of backing up absolutely everything about the phone's current state(apps settings documents etc.) and restoring it all back?
I just spent good money on this phone, thank you for all advice!

Are you using stock rom or a custom rom?
You can use magisk uninstaller to remove magisk to see if that caused an issue (see magisk v14.0 thread)
In some custom roms some people did report camera stopped working - Iv never had this issue
I'm using LineageOS with the built in superuser via the su add on zip
In terms of the camera itself hardware wise & on unmodified stock there are no reported issues

TheFixItMan said:
Are you using stock rom or a custom rom?
You can use magisk uninstaller to remove magisk to see if that caused an issue (see magisk v14.0 thread)
In some custom roms some people did report camera stopped working - Iv never had this issue
I'm using LineageOS with the built in superuser via the su add on zip
In terms of the camera itself hardware wise & on unmodified stock there are no reported issues
Click to expand...
Click to collapse
Not using a custom ROM.
I went to the Magisk page where I got the install, got "latest uninstaller", ran it. It reported success but warned that no boot image backup was found. On restart it hanged indefinetly at the 5-second untrusted device warning. Did a hard poweroff and on, same result. I ended up installing the 14.0 back and the device again boots. I also did a dump of the boot logs.
In dmesg.log I see this:
Code:
<3>[ 5.684036,2] msm_camera_pinctrl_init:1277 Getting pinctrl handle failed
Code:
<3>[ 5.676660,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676664,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676667,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676710,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676714,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676717,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676760,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676763,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
<3>[ 5.676806,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676810,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
and respectively this:
Code:
<3>[ 5.664800,0] msm_camera_get_dt_vreg_data:1115 number of entries is 0 or not present in dts
I'm no expert reading these logs, is this signalling my issue?
Also this is from the non-working boot, near the end of the log:
Code:
>[ 33.292450,5] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

SearinoxNavras said:
Not using a custom ROM.
I went to the Magisk page where I got the install, got "latest uninstaller", ran it. It reported success but warned that no boot image backup was found. On restart it hanged indefinetly at the 5-second untrusted device warning. Did a hard poweroff and on, same result. I ended up installing the 14.0 back and the device again boots. I also did a dump of the boot logs.
In dmesg.log I see this:
Code:
<3>[ 5.684036,2] msm_camera_pinctrl_init:1277 Getting pinctrl handle failed
Code:
<3>[ 5.676660,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676664,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676667,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676710,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676714,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676717,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676760,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676763,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
<3>[ 5.676806,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676810,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
and respectively this:
Code:
<3>[ 5.664800,0] msm_camera_get_dt_vreg_data:1115 number of entries is 0 or not present in dts
I'm no expert reading these logs, is this signalling my issue?
Also this is from the non-working boot, near the end of the log:
Code:
>[ 33.292450,5] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Click to expand...
Click to collapse
Here is the original stock boot.img if you need to flash it after removing magisk
Stock boot image
You need to put your phone in bootloader mode & connect to pc via usb
Open a command/terminal prompt at your fastboot location
Code:
fastboot flash boot boot.img
Substitute boot.img for the name of your boot.img if different but I think I named it boot.img
You may have to flash the entire stock firmware & start again or try flashing Linageos
You can also try erasing user data by typing
Code:
fastboot erase userdata
But note this will erase all data from phone including anything in internal storage like photos music downloads etc (only data partition not system so phone will boot as if new)

The boot.img you sent me and the one I have both have the same hashes. So I was at least doing that right.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.739s]
finished. total time: 1.258s
Is "bad key" normal? Now the 5-second untlocked untrusted warning says ID: bad key instead of N/A. Sadly, the device behaves the same. It hangs indefinetly at that one screen. Maybe something's off with the uninstaller; if I wanted to manually -disable- magisk by renaming say one file or folder that is an entry point, how would I do that?
I checked the boot logs again, and I'm still seeing the same camera stuff mentioned there, so I don't know if it fixed anything since I can't boot but it doesn't look different.
I uploaded the files here: https://drive.google.com/file/d/0B5_lN_xRgoTVTUZZX0ZaWmZGNkE/view
Please tell me if there's anything there shouldn't be about the camera in them.
Once I reinstall Magisk, the ID at the boot splash warning goes back to N/A. Funny enough it -does- say it's found a stock boot image and it's backing it up when you install, but on uninstall it never finds it.
If I were to try a stock reflash or another fw, do I have a way to image absolutely everything and if I want, to restore it back as if it never changed?
I forgot to mention that when I installed TWRP I also installed no-verity-opt-encrypt-5.1.zip. Does this have anything to do with it?

SearinoxNavras said:
The boot.img you sent me and the one I have both have the same hashes. So I was at least doing that right.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.739s]
finished. total time: 1.258s
Is "bad key" normal? Now the 5-second untlocked untrusted warning says ID: bad key instead of N/A. Sadly, the device behaves the same. It hangs indefinetly at that one screen. Maybe something's off with the uninstaller; if I wanted to manually -disable- magisk by renaming say one file or folder that is an entry point, how would I do that?
I checked the boot logs again, and I'm still seeing the same camera stuff mentioned there, so I don't know if it fixed anything since I can't boot but it doesn't look different.
I uploaded the files here: https://drive.google.com/file/d/0B5_lN_xRgoTVTUZZX0ZaWmZGNkE/view
Please tell me if there's anything there shouldn't be about the camera in them.
Once I reinstall Magisk, the ID at the boot splash warning goes back to N/A. Funny enough it -does- say it's found a stock boot image and it's backing it up when you install, but on uninstall it never finds it.
Click to expand...
Click to collapse
it always says image signed with bad key for me
you can try going into twrp
click advanced
file manager
data
select magisk.img (or something like that)
then delete it
Other than reflashing the entire firmware via fastboot theres not alot else I can suggest
I would erase userdata though if you are trying the uninstall magisk as it does modify the data partition and its best to erase it if you no longer use magisk - but as I mentioned before anything on internal storage will be lost so move it to sd card
But I dont know of anyone else who has used magisk and the camera stops working so I dont even know if thats the problem
Without testing it on a fresh stock rom you wont know

I flashed LineageOS and it's seeing my camera! I haven't yet flashed the google apps, mainly to see if the camera works in as minimal a clean slate as possible. Now with that out of the way, whatever other issues I may encounter I will solve or possibly ask in another thread, but at least this fixed the cam. Now off to the long road of installing stuff.

for me is the same, flashing stock again, update all to august patch, and the camera stop working, if i uninstall magisk the phone not starts, is stuck in the boot logo, after install magisk 14 again, the phone boting but no camera works

woozie.2007 said:
for me is the same, flashing stock again, update all to august patch, and the camera stop working, if i uninstall magisk the phone not starts, is stuck in the boot logo, after install magisk 14 again, the phone boting but no camera works
Click to expand...
Click to collapse
After uninstalling magisk try flashing the kernel for your rom via fastboot

i tried but the phone won't boot
---------- Post added at 05:13 PM ---------- Previous post was at 05:12 PM ----------
the phone started only if i flash system sparsechunk0, 1, 2, 3 and 4, without these flashed the phone not starting

i flashed again the stock firmware, initial is with patch from january, i made ota update to march(the camera still works with magisk 14), and then i updated ota to august....now camera works, but i installed magisk and patched the boot....bang, the camera stops. So i decided is problem with magisk after the august update, i haven't twrp, only flash it via fastboot. I dont know what can i tried to works camera with magisk ((

woozie.2007 said:
i flashed again the stock firmware, initial is with patch from january, i made ota update to march(the camera still works with magisk 14), and then i updated ota to august....now camera works, but i installed magisk and patched the boot....bang, the camera stops. So i decided is problem with magisk after the august update, i haven't twrp, only flash it via fastboot. I dont know what can i tried to works camera with magisk ((
Click to expand...
Click to collapse
Why do you want to use magisk - it doesn't work fully on this device - eg magisk hide & modules do not work
Much better using supersu (either via twrp zip or CF-Auto-Root) or the lineageos root addon

TheFixItMan said:
Why do you want to use magisk - it doesn't work fully on this device - eg magisk hide & modules do not work
Much better using supersu (either via twrp zip or CF-Auto-Root) or the lineageos root addon
Click to expand...
Click to collapse
because i want to update via ota, cf auto root i tried but not works, i want to use stock firmware not lineageos, i have 7.0. Can you tell me how to root moto g5 without modify system, to be able to update ota? Thanks

woozie.2007 said:
because i want to update via ota, cf auto root i tried but not works, i want to use stock firmware not lineageos, i have 7.0. Can you tell me how to root moto g5 without modify system, to be able to update ota? Thanks
Click to expand...
Click to collapse
Then use supersu and flashfire app
https://play.google.com/store/apps/details?id=eu.chainfire.flash
I'm working on CF-Auto-Root - server is down at the moment - once Iv created a working package I'll post it

how? i am on stock now, not twrp, i have full stock

woozie.2007 said:
how? i am on stock now, not twrp, i have full stock
Click to expand...
Click to collapse
Flash twrp root then flash stock recovery
Obviously I presume you have unlocked the bootloader

yes, of course i have

woozie.2007 said:
yes, of course i have
Click to expand...
Click to collapse
hello
he
lp me please i have the same problem: camerera falled

Marie74 said:
hello
he
lp me please i have the same problem: camerera falled
Click to expand...
Click to collapse
i fixed the problem with clean flash stock rom, then update ota then flash twrp and root again with latest version of magisk

camera
woozie.2007 said:
i fixed the problem with clean flash stock rom, then update ota then flash twrp and root again with latest version of magisk
Click to expand...
Click to collapse
thank you for awser give me the link please please please! god bless you!

Twrp can't decrypt data

Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?

Tom403 said:
Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?
Click to expand...
Click to collapse
Why don't you install Magisk by patching Boot image from Magisk Manager and flashing the patched image from Fastboot.
Just for Magisk, you don't need (to bother with) TWRP

zgfg said:
Why don't you install Magisk by patching Boot image from Magisk Manager and flashing the patched image from Fastboot.
Just for Magisk, you don't need (to bother with) TWRP
Click to expand...
Click to collapse
Won't that replace my recovery with the stock one?
I'd like to keep twrp

Tom403 said:
Won't that replace my recovery with the stock one?
I'd like to keep twrp
Click to expand...
Click to collapse
You flash the patched Boot image from Fastboot, so Recovery (and other partitions) remains the one you have currently installed.
Also, just patching in Magisk Manager does not affect either Recovery, Boot (Vendor, etc)
When patching Boot image by Magisk Manager make sure you take the options:
-Preserve ADM dm-verity: YES
-Preserve force encryption: YES
-Recovery mode: NO

zgfg said:
You flash the patched Boot image from Fastboot, so Recovery (and other partitions) remains the one you have currently installed.
Also, just patching in Magisk Manager does not affect either Recovery, Boot (Vendor, etc)
When patching Boot image by Magisk Manager make sure you take the options:
-Preserve ADM dm-verity: YES
-Preserve force encryption: YES
-Recovery mode: NO
Click to expand...
Click to collapse
Ok, I'll do that then
Thanks for the help ?

Tom403 said:
Ok, I'll do that then
Thanks for the help ?
Click to expand...
Click to collapse
For the Boot image you have to patch boot.img extracted from zip/recovery package of your stock ROM
But you can also backup Boot partition by TWRP and then let Magisk Manager patch the backup boot.emmc.win file

Is it safe to assume that Tom403 didn't find any love at the end of the encrypted rainblow? I JUST WANT to verify, This IS the same situation that used to be remedied by deleting locksettings.db and a files with .key extension?? No such luck for anymore, wow, what a setup for future-screwing your users Google!! Dicks

goo. said:
Is it safe to assume that Tom403 didn't find any love at the end of the encrypted rainblow? I JUST WANT to verify, This IS the same situation that used to be remedied by deleting locksettings.db and a files with .key extension?? No such luck for anymore, wow, what a setup for future-screwing your users Google!! Dicks
Click to expand...
Click to collapse
Okay, I may have found a lightbulb somewhere in the tunnel that may be whats required for others as well to unencrypt when deleting .keyfiles is no longer an option having version greater than PIE. It's in the form of in a recovery log from a recent, perhaps backup attempt, that states the version of Orange Fox recovery I had (11.0) and also says fbe encryption in use and info like the following that looks very promising... I'd really appreciate if someone that knows more than me to let me know if I'm on the right path and guide me in if so... heres part of the LOG that gives me hope --
ased Encryption is present
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using SoftwareWrappedKeymaster1Device from Google for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
Added key 90117251 (ext4:72f7ca8ad834ad5d) to keyring 322439018 in process 546
Added key 866183642 (f2fs:72f7ca8ad834ad5d) to keyring 322439018 in process 546
Added key 321684719 (fscrypt:72f7ca8ad834ad5d) to keyring 322439018 in process 546
contents mode 'aes-256-xts' filenames 'aes-256-heh'
Wrote system DE key reference to:/data/unencrypted/ref
e4crypt_ini
Thanks in advance for any help with this

Tom403 said:
Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?
Click to expand...
Click to collapse
thanks for the terminal command

Question Looking for v8.8 boot.img for TMO

I'm having issues applying OTA 9.9 update on T-Mobile ROM. Here is the excerpt from logcat:
Code:
Applying 164 operations to partition "boot"
No ECC data in the passed file
Unable to open ECC source partition boot on slot B, file /dev/block/bootdevice/by-name/boot_b: Invalid argument (22)
The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
Expected: sha256|hex = 261C74F4D2F87BC7B84A1C226A0495BA75B0FFEB6E2A5CCCEC9D8E4B3643E6B1
Calculated: sha256|hex = 60397DF8FAA8B5179F4C0D4DDC2A2ADEE585BAAA7B06E359022D79F0A2C4A90A
Looks like something is wrong with my boot partition and I apparently don't have the correct backup - the one I have does not solve the issue. I think I might've accidentally modified it in some way before making backup. Phone boots and works fine, it's just the OTA that can't update.
Could someone please share v8.8 boot.img from T-Mobile ROM?

I am facing the same issue. But I rooted my phone using the 11.2.8.8 boot img from the Global variant AA since I could not find the ABC TMobile version on that thread. That probably screwed my phone. How did you root your phone? Did you use the [magisk root/keep root] thread on this forum?

cowsquad said:
I am facing the same issue. But I rooted my phone using the 11.2.8.8 boot img from the Global variant AA since I could not find the ABC TMobile version on that thread. That probably screwed my phone. How did you root your phone? Did you use the [magisk root/keep root] thread on this forum?
Click to expand...
Click to collapse
No, I just grabbed my own boot image, fed it to Magisk through "select and patch a file", then flashed the resulting image through fastboot. But apparently, the problem is that the image was already modified somehow prior to patching in Magisk, so it's not restoring to the one that update expects.

...

Question Help!!!!!! Boot failure / stuck in fastboot

Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3

jcp2 said:
Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3
Click to expand...
Click to collapse
Try using Android Flash Tool to get back to stock.

I tried. it failed.
Flash Failed​Device failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure

jcp2 said:
I tried. it failed.
Flash Failed​Device failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure
Click to expand...
Click to collapse
Then just manually flash ROM files in fastboot

jamescable said:
Then just manually flash ROM files in fastboot
Click to expand...
Click to collapse
is there a write up somewhere with adb commands?

Use PixelFlasher and the latest full update.

AlDollaz said:
Use PixelFlasher and the latest full update.
Click to expand...
Click to collapse
tried that as well
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

I'm not sure of the commands. Fastboot flash recovery "recovery.img" , same with the other files inside the zip inside the stock rom zip file
If i ran into this issue I'd try fastboot -w and fastboot update a custom rom.

jcp2 said:
is there a write up somewhere with adb commands?
Click to expand...
Click to collapse
Most need to be flashed in fastbootd I think. So to get there, fastboot reboot fastboot. You can flash recovery( boot, dtbo and vendor boot) in regular fastboot. That should fix everything because it will fully get rid of magisk

I used AFT and forced flashed partitions / wiped (kept bootloader unlock) and it's alive again!

Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?

StanWiz said:
Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?
Click to expand...
Click to collapse
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.

Strephon Alkhalikoi said:
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.
Click to expand...
Click to collapse
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.

StanWiz said:
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.
Click to expand...
Click to collapse
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.

Strephon Alkhalikoi said:
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.
Click to expand...
Click to collapse
It's not a question of knowledge but rather the things that are beyond ones control - possibility of bugs in the code. For example look what happened recently with platform tools.

@jcp2 With all the things you flash, you should also know what that is. Then it would be much easier for you to figure it out why your device is in an unbootable state.
Magisk, Kernel, fastbootd... have one thing in common: your boot.img!
It doesn't make sense to let Magisk patch your boot.img and installing a custom kernel without Magisk installed afterwards. In that case Magisk gets overwritten.
Your fastbootd is only a binary and located in the recovery's /sbin folder. Due to the fact that your P6P is an A/B slot device, your recovery is part of the boot.img.
Flash your stock boot.img from the image-raven-BUILD_NO.zip that you'll find inside your firmware download.

I had already tried flashing stock boot image to both slots. I had to use AFT and force flash all partions. I'm up and running/ rooted. I just have to reinstall apps .

Android flash tool is by far the easiest way to go for sure. Happy you got it fixed

{Mod edit: Quoted post has been deleted. Oswald Boelcke}
6. fast boot flash
That ADB Command does nothing.
The correct command is:
fastboot flash boot boot.img if you want to flash the boot.img

{Mod edit: Quoted post has been deleted. Oswald Boelcke}
You should give us the correct command. The syntax is (see fastboot -h):
Code:
flash PARTITION [FILENAME] Flash given partition, using the image from
$ANDROID_PRODUCT_OUT if no filename is given.
you can't use "fast boot" for a binary that's called "fastboot(.exe)".