Related
^^This
Probably NO its an old device but i still like it so there is still a change of it and maybe CM13.0 too it just need time.
Working on Lineage OS 13.0 Rom for this device with TWRP 3.0.2.0 but new CM 12.1 got already new version so maybe i can try to grab 3.1.1 twrp source and compile for our device but dont know if it will work
Tried not possible our devices have too much modified TWRP that the branch don't wanna to merge.
I would greatly recommend checking galaxy nexus TWRP thread, where they also had a lot of problems with 3.1.0.0.
Situation is remarkably kind of similar to ours: they are stuck to 3.0 kernel, and they haven't QCOM hardware (they have support for nougat though)
I had ported it to our device but it doesn't compile because of sdk it showed errors always about sdk i have it on my GitHub branch 7.1 I may create new branch and try again because you are not the only one who want latest stuff if there were moreeeeeee time and more people we might be able to Port android 7.1 but this device is not much used anymore there is lot less devs. But if anybody wants to try download android 6.0 source add our vendors and all our device stuff and add my TWRP and try to build only TWRP without android you might get successful build
Sent from my nypon using XDA Labs
---------- Post added at 07:19 PM ---------- Previous post was at 07:16 PM ----------
In few days i will create new thread In p general and will post there stuff about my porting diary maybe more devs will add and will be help me
Sent from my nypon using XDA Labs
---------- Post added at 07:30 PM ---------- Previous post was at 07:19 PM ----------
And I don't think sdk problems are releated to my porting since android 6.0 don't compile on 5.1.1 but it does on 6.0 so I don't know guys about that
Sent from my nypon using XDA Labs
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
mirhl said:
I would greatly recommend checking galaxy nexus TWRP thread, where they also had a lot of problems with 3.1.0.0.
Situation is remarkably kind of similar to ours: they are stuck to 3.0 kernel, and they haven't QCOM hardware (they have support for nougat though)
Click to expand...
Click to collapse
Also would you help me post some stuff if you have this device ?
Sent from my nypon using XDA Labs
Sorry, I don't.
mirhl said:
Sorry, I don't.
Click to expand...
Click to collapse
Oh ok Then i will try to port it on my own. But thanks still.
I have done it i build TWRP 3.1.1 for xperia P its on my LineageOS thread but its build from omni tree so it will not boot CM roms yet im going to build on CM tree somehow(CM doesnt support TWRP officialy omni do so thats why i build it first in omni).
It's kindish confusing to say that "recovery cannot boot rom", for as much as yes, kernel and recovery are physically the same atm.
Wouldn't be a problem if we had FOTA as I was talking about (or an universal kernel like they have on gnex.. but I'm digressing)
mirhl said:
It's kindish confusing to say that "recovery cannot boot rom", for as much as yes, kernel and recovery are physically the same atm.
Wouldn't be a problem if we had FOTA as I was talking about (or an universal kernel like they have on gnex.. but I'm digressing)
Click to expand...
Click to collapse
It wasn't booting because it was built using omni tree now I compiled using cm tree and its working and yes I'm writing with adrianDC about FOTAkernel I want to do that one mainly now and then official support.
---------- Post added at 11:01 PM ---------- Previous post was at 10:55 PM ----------
mirhl said:
It's kindish confusing to say that "recovery cannot boot rom", for as much as yes, kernel and recovery are physically the same atm.
Wouldn't be a problem if we had FOTA as I was talking about (or an universal kernel like they have on gnex.. but I'm digressing)
Click to expand...
Click to collapse
But idk if we don't need to make the fota partition or does Nypon have it already ?
---------- Post added at 11:07 PM ---------- Previous post was at 11:01 PM ----------
mirhl said:
It's kindish confusing to say that "recovery cannot boot rom", for as much as yes, kernel and recovery are physically the same atm.
Wouldn't be a problem if we had FOTA as I was talking about (or an universal kernel like they have on gnex.. but I'm digressing)
Click to expand...
Click to collapse
And I meant kernel cannot boot the ROM because it was built for omni ROM.
Haxk20 said:
But idk if we don't need to make the fota partition or does Nypon have it already ?
Click to expand...
Click to collapse
Every sony phone should have it.
That was exactly the secret of the smart idea.
Supposedly, I think at least on XU that should correspond to /dev/block/mmcblk0p13
mirhl said:
Every sony phone should have it.
That was exactly the secret of the smart idea.
Supposedly, I think at least on XU that should correspond to /dev/block/mmcblk0p13
Click to expand...
Click to collapse
And how can we check which one it is on XP ?
After I know which partition it is I can start working on it.
First add it to TWRP as FOTA (just to addone line )
Then well edit few files in device tree and then well we would have fota partition used by recovery yayyy.
It shouldn't be too hard to do .
I just need to know what files should I edit from adrianDC I will write him.
Sony devices can't boot into FOTA partition once the bootloader is unlocked, what newer devices do is just load the recovery ramdisk from the FOTA partition (which can still store data and be accessed) into the boot partition, it's not a real recovery partition, what our devices do is just the same but the recovery ramdisk is stored in the boot.img.
The only benefit of using the FOTA partition to store the recovery is that it can be updated more easily, in newer Sony devices you can just use fastboot to flash the image, but our devices can't use fastboot to flash the FOTA partition so you would have to use the dd command, which isn't as convenient as fastboot. Also AGONTUK already made a script that replaces the recovery ramdisk in a boot.img, so updating the recovery is not a big hassle.
That's why we didn't bother porting the method newer Sony devices use to boot into the recovery, the benefits are non-existent (because our FOTA partition is not recognised as a recovery partition by fastboot).
Garcia98 said:
Sony devices can't boot into FOTA partition once the bootloader is unlocked, what newer devices do is just load the recovery ramdisk from the FOTA partition (which can still store data and be accessed) into the boot partition, it's not a real recovery partition, what our devices do is just the same but the recovery ramdisk is stored in the boot.img.
The only benefit of using the FOTA partition to store the recovery is that it can be updated more easily, in newer Sony devices you can just use fastboot to flash the image, but our devices can't use fastboot to flash the FOTA partition so you would have to use the dd command, which isn't as convenient as fastboot. Also AGONTUK already made a script that replaces the recovery ramdisk in a boot.img, so updating the recovery is not a big hassle.
That's why we didn't bother porting the method newer Sony devices use to boot into the recovery, the benefits are non-existent (because our FOTA partition is not recognised as a recovery partition by fastboot).
Click to expand...
Click to collapse
Yes I know all of this but still thanks and the benefit here is that with the new method I can request official support for xperia P from twrp team.
Cause if I must build a boot.IMG still when new commit comes in twrp I would have a ton of boot.IMG and users will not use them cause they would have to flash every new version. And also if users use omni and I build cm boot.IMG they cannot boot to system.
If we add fota then users could update twrp just from twrp app ifimwrong about this please correct me.
Also why is not our FOTA recognized as recovery then ?
---------- Post added at 10:00 PM ---------- Previous post was at 09:53 PM ----------
Garcia98 said:
Sony devices can't boot into FOTA partition once the bootloader is unlocked, what newer devices do is just load the recovery ramdisk from the FOTA partition (which can still store data and be accessed) into the boot partition, it's not a real recovery partition, what our devices do is just the same but the recovery ramdisk is stored in the boot.img.
The only benefit of using the FOTA partition to store the recovery is that it can be updated more easily, in newer Sony devices you can just use fastboot to flash the image, but our devices can't use fastboot to flash the FOTA partition so you would have to use the dd command, which isn't as convenient as fastboot. Also AGONTUK already made a script that replaces the recovery ramdisk in a boot.img, so updating the recovery is not a big hassle.
That's why we didn't bother porting the method newer Sony devices use to boot into the recovery, the benefits are non-existent (because our FOTA partition is not recognised as a recovery partition by fastboot).
Click to expand...
Click to collapse
And also which partition is FOTA on xperia P ?
Haxk20 said:
Yes I know all of this but still thanks and the benefit here is that with the new method I can request official support for xperia P from twrp team.
Cause if I must build a boot.IMG still when new commit comes in twrp I would have a ton of boot.IMG and users will not use them cause they would have to flash every new version. And also if users use omni and I build cm boot.IMG they cannot boot to system.
If we add fota then users could update twrp just from twrp app ifimwrong about this please correct me.
Also why is not our FOTA recognized as recovery then ?
---------- Post added at 10:00 PM ---------- Previous post was at 09:53 PM ----------
And also which partition is FOTA on xperia P ?
Click to expand...
Click to collapse
The FOTA partition is the 13, the same as Xperia U, Go and Sola.
Our bootloader doesn't flag the FOTA partition as a recovery partition, that's why fastboot can't access to it, and only Sony could solve that through a firmware update.
I don't really know how the TWRP official app works, but if they accept devices with boot.img based recoveries the current method would be fine. If the recovery ramdisk has to be on a separate image then you would need to use the newer method, ask them about that.
Also it doesn't matter whether you're building TWRP on Omni or CM sources, the recovery ramdisk will be the same and that's everything that matters, you can then use that recovery ramdisk in a boot.img for CM, Omni or whatever ROM you want.
Garcia98 said:
The FOTA partition is the 13, the same as Xperia U, Go and Sola.
Our bootloader doesn't flag the FOTA partition as a recovery partition, that's why fastboot can't access to it, and only Sony could solve that through a firmware update.
I don't really know how the TWRP official app works, but if they accept devices with boot.img based recoveries the current method would be fine. If the recovery ramdisk has to be on a separate image then you would need to use the newer method, ask them about that.
Also it doesn't matter whether you're building TWRP on Omni or CM sources, the recovery ramdisk will be the same and that's everything that matters, you can then use that recovery ramdisk in a boot.img for CM, Omni or whatever ROM you want.
Click to expand...
Click to collapse
Yes recoveryramdisk is same of course but the boot.img itself isn't and tested it doesn't boot with omni one.
I will lookup if current method will work but I don't think so
Haxk20 said:
Yes recoveryramdisk is same of course but the boot.img itself isn't and tested it doesn't boot with omni one.
I will lookup if current method will work but I don't think so
Click to expand...
Click to collapse
You have to take only the recovery ramdisk you get after compiling the recovery and swap it with the old recovery ramdisk in the target boot.img, check AGONTUK script, you can throw the boot.img you get after compiling the recovery to the recycle bin.
Garcia98 said:
You have to take only the recovery ramdisk you get after compiling the recovery and swap it with the old recovery ramdisk in the target boot.img, check AGONTUK script, you can throw the boot.img you get after compiling the recovery to the recycle bin.
Click to expand...
Click to collapse
Hi well the link to download doesn't work and well now im going to makethefota working.
Haxk20 said:
Hi well the link to download doesn't work and well now im going to makethefota working.
Click to expand...
Click to collapse
Check the attached files of this post
Hello everyone ! I have a big issue :
I installed the following rom OpenKirin's AOSP Treble Oreo For Honor 9. But, the capacity buttons didn't work at all.
So I went to the following topic [Oreo] [TWRP 3.2.1-0] [0.3] [+Capacitive fix].
This topic said that I "just" had to flash the kernel to get my capacitive buttons working again, but now, my phone can't boot at all. It keeps on restarting and shows me the honor disclaimer then the honor blue starting screen and it loops.
So can you guys tell me is there any fix or is my phone a brick, knowing that I still can access the fastboot and TWRP?
Thanks
You flash a B360's kernel over a build which is not B360 ; So bootloops.
What stock firmware were you on before flashing AOSP system ?
---------- Post added at 23:36 ---------- Previous post was at 23:34 ----------
Just flash back the stock kernel from your firmware version before AOSP.
oslo83 said:
You flash a B360's kernel over a build which is not B360 ; So bootloops.
What stock firmware were you on before flashing AOSP system ?
---------- Post added at 23:36 ---------- Previous post was at 23:34 ----------
Just flash back the stock kernel from your firmware version before AOSP.
Click to expand...
Click to collapse
Thank you for being that fast, I had the STF-L09C432B365 firmware.
So extract the stock kernel img (ramdisk) from the Update.app file included in the file update.zip from this firmware.
Use a windows app called HuaweiUpdateExtractor
---------- Post added at 23:43 ---------- Previous post was at 23:41 ----------
Then wait for a B365 kernel that fixes buttons.
(Or go back to stock B360 for applying the b360 kernel fix)
oslo83 said:
So extract the stock kernel img (ramdisk) from the Update.app file included in the file update.zip from this firmware.
Use a windows app called HuaweiUpdateExtractor
---------- Post added at 23:43 ---------- Previous post was at 23:41 ----------
Then wait for a B365 kernel that fixes buttons.
(Or go back to stock B360 for applying the b360 kernel fix)
Click to expand...
Click to collapse
OK, so once it's extracted I just have to do a ./fastboot flash kernel <my_extracted_stock_kernel>.img right?
I'll try it, once I finish to install my VM (I have a mac ><)
dandas said:
OK, so once it's extracted I just have to do a ./fastboot flash kernel <my_extracted_stock_kernel>.img right?
I'll try it, once I finish to install my VM (I have a mac ><)
Click to expand...
Click to collapse
Well it didn't work :/
Code:
./fastboot flash kernel KERNEL.img
does not work ? What does it output ?
(By the way adb and fastboot are working just fine on osx without need of a VM for those.)
oslo83 said:
So extract the stock kernel img (ramdisk) from the Update.app file included in the file update.zip from this firmware.
Use a windows app called HuaweiUpdateExtractor
---------- Post added at 23:43 ---------- Previous post was at 23:41 ----------
Then wait for a B365 kernel that fixes buttons.
(Or go back to stock B360 for applying the b360 kernel fix)
Click to expand...
Click to collapse
Really? I have made a thread on Guides with all stock EMUI8 kernels, ramdisks and recoveries for easy access to people but i guess no one noticed... why do i bother...
JBolho said:
Really? I have made a thread on Guides with all stock EMUI8 kernels, ramdisks and recoveries for easy access to people but i guess no one noticed... why do i bother...
Click to expand...
Click to collapse
No need to be offended mate, I tried all your files with the exact same commands, and none is working on my device
oslo said:
Code:
./fastboot flash kernel KERNEL.img
does not work ? What does it output ?
(By the way adb and fastboot are working just fine on osx without need of a VM for those.)
Click to expand...
Click to collapse
I did the same command, here's the log :
Code:
➜ platform-tools ./fastboot flash kernel ~/foo/KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.650s]
writing 'kernel'...
OKAY [ 0.262s]
I still have a bootloop... And thanks for the VM advice, but you told me to use HuaweiUpdateExtractor which only works on Windows, so I still had to use a VM. Anyway, my previous message wasn't clear about that point, sorry for the misunderstanding.
Do you have any other suggestion? I start to doubt about my original build number, do you know if I can cat the original stock kernel with the adb shell, or if I can get out of the loop with some others kernel and ramdisks imgs?
Thank you guys
You'll need stock kernel of your actual build.
So it's seems you were not STF-L09C432B365 kernel as you still are bootlooping.
Try with stock kernels from :
STF-L09C432B364
STF-L09C432B363
STF-L09C432B362
STF-L09C432B360
You could try with images provided by JBolho : https://androidfilehost.com/?w=files&flid=266088
oslo83 said:
You'll need stock kernel of your actual build.
So it's seems you were not STF-L09C432B365 kernel as you still are bootlooping.
Try with stock kernels from :
STF-L09C432B364
STF-L09C432B363
STF-L09C432B362
STF-L09C432B360
You could try with images provided by JBolho : https://androidfilehost.com/?w=files&flid=266088
Click to expand...
Click to collapse
As I said, I tried them already, but I'll try again. BTW the B360_kernel.img is missing inside JBolho's repo
Maybe he messed something when uploading them.
Maybe you were not on one of those.
Ok, is there any other version I can try? Or maybe my process is wrong, I do the same commands, and in the same order as Jbolho describes in his post.
Except for the recovery flash, does it matter? Because since that I don't have the erecovery anymore, before I still had it in combination with the twrp.
Thanks
oslo83 said:
Maybe he messed something when uploading them.
Maybe you were not on one of those.
Click to expand...
Click to collapse
No, I didn't mess anything, checked them already, all in the same folder on AFH and properly uploaded.
And I never stated that the B360 fixed kernel was in my repo, I point it to zxz0O0's thread.
What I would recommend is to flash recovery and ramdisk too, not just kernel (corresponding to previously installed firmware of course)
@dandas Please note that recovery & erecovery are two differents mode.
help !!
did you find a solution for this problem
i have the same problem after flashing kernel to my honor 9 STF-AL10 please help me
kalilou23000 said:
did you find a solution for this problem
i have the same problem after flashing kernel to my honor 9 STF-AL10 please help me
Click to expand...
Click to collapse
What version did you flash specifically, on what firmware?
help honor STF-AL10
my phone was on
STF-AL10C00B172 the capacitive botton wont work when i google the problem xda team have solved the problem with flashing kernel
when i have flashed kernel the phone bootloop and reboot into e-recovery mode
i tried to download emergency software from erecovery with wifi but it didnt work ''failed ''
when i trie to flash the honor with his one version again onlly system.img flashed seccessfully via fastboot mode with cmd
other img wont pass it saise failed
i have tried other ways like flashing stock rom 5GB via upgrade mode with sd card but the flash failed and it write failed to install software
in my case i dont have money to activate dc unlocker and unbrick my device with dc-phoenix so i downloaded a board software '' xml file '' for my honor 9 and installed acm and handset driver but the device when i install acm device it is connected on com 11 huawei mobile connect Fake acm interface i cant flash my honor 9 via IDT tool what should i do !!!
kalilou23000 said:
my phone was on
STF-AL10C00B172 the capacitive botton wont work when i google the problem xda team have solved the problem with flashing kernel
when i have flashed kernel the phone bootloop and reboot into e-recovery mode
i tried to download emergency software from erecovery with wifi but it didnt work ''failed ''
when i trie to flash the honor with his one version again onlly system.img flashed seccessfully via fastboot mode with cmd
other img wont pass it saise failed
i have tried other ways like flashing stock rom 5GB via upgrade mode with sd card but the flash failed and it write failed to install software
in my case i dont have money to activate dc unlocker and unbrick my device with dc-phoenix so i downloaded a board software '' xml file '' for my honor 9 and installed acm and handset driver but the device when i install acm device it is connected on com 11 huawei mobile connect Fake acm interface i cant flash my honor 9 via IDT tool what should i do !!!
Click to expand...
Click to collapse
That's confusing to say the least. You flashed the kernel on B172 firmware??? That's Nougat firmware! No wonder you screwed everything up. Don't mess with board software and stuff like that, you have to install the firmware with dload method probably.
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
How did you prepare this?
Do you also have flashable .img of TWRP for G6 Plus?
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
Click to expand...
Click to collapse
Simple Great!
For me adb sideload dont work, even when i type "adb devices" or "sudo adb devices" just appear "no devices/emulators detected" but when I use twrp via "sudo fastboot boot twrp.img" all works propertly. Although i type adb kill-server and sudo adb start-server no fix that than in the another method it works. I think maybe is for version (3.2.3-0) works and in your (3.2.1-0) dont (?) or Is by in one Is installed on the devices and the another not (?)
Thanks in advance for an posible solution. Grettings from México
Many thanks in advance segra246x.
Unfortunately for me, every time I´ve flashed TWRP, then I do not know what may i do to reboot the phone. My phone is unlocked and I am root with Magisk, so I do not know which boot should I flash at the end, so that it starts again and does not stay in a loop with TWRP or in brick.
Couls you tell wich procedure are you using to can start the device normally?
i flashed patched boot image, Should i flash boot patched boot image and re-start again Magisck instalation? Should i flash boot boot.image from the regarding stocke version without loosing root satus?
Thank you, the twrp works fine installed with stock Oreo 8.0.
Worked on G6+ with Pie. Thank you!
thump said:
Worked on G6+ with Pie. Thank you!
Click to expand...
Click to collapse
Please explain your process & is it still working? What version are you on with 9.0?
---------- Post added at 10:04 PM ---------- Previous post was at 10:00 PM ----------
thump said:
Worked on G6+ with Pie. Thank you!
Click to expand...
Click to collapse
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
Click to expand...
Click to collapse
This method still working for you?? And I don't see any credits so did you create this installer??
I used the exact file and the 5 step method outlined in the original post.
Hey did you create this?
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooed with magisk!!
Click to expand...
Click to collapse
I can't find any credits.
---------- Post added at 08:11 AM ---------- Previous post was at 08:02 AM ----------
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
Click to expand...
Click to collapse
**I noticed that you have not been logged in here for
about a month. When you get back please inform me.
I have an error to flash the twrp, how did you do it?
Instructions..
HorryStorm said:
I have an error to flash the twrp, how did you do it?
Click to expand...
Click to collapse
Follow the directions. Couldn't be more simple.
First use our official TWRP 3-2-3-0 to BOOT into
There you flash this installer.
I have used this installer and can say it's good.
MPT works.. you can then reboot to recovery at
Anytime. Hope that's helpful. Good luck.
--Ken
the question is that when I try to make the flash it appears a maximum size error.
This is only for Moto G6 Plus. If that's your device
Then idk. I've installed it several times and never had
An issue.
Ok, thanks.
I dont have OS Pie9 after flashing twrp
My step was,
1. flashing Pie9 with cmd in fastboot
2. then i boot in twrp.img and install zip twrp ...
---------- Post added at 01:29 PM ---------- Previous post was at 01:10 PM ----------
lavriiga said:
My step was,
1. flashing Pie9 with cmd in fastboot
2. then i boot in twrp.img and install zip twrp ...
Click to expand...
Click to collapse
I fix it, First i flash PIE 9.0
Then i boot in twrp.img in fastboot
Then zip TWRP.zip and after that i install MAGISK 17.1 And it works ! Thanks for posts !!!:good::laugh::laugh::laugh:
Secure Startup Password
First off thank you segra246x for making this. I had no problem following the instructions and got TWRP installed with no issue. I have also been able to successfully flash a bunch of different Pie GSIs (phhTreble, AOSP Extended) successfully.
I do however have a question that I cannot seem to find the answer too anywhere for the Moto G6 Plus. On past devices (i.e. Moto G5 Plus) I was able to configure the device to require a password or pin or pattern before the device would boot. Similarly TWRP would require this in order to mount /data. Depending on where you are looking online this could be called Secure Boot or Secure Startup. On this device however I cannot find the option when I set the password with any version of Android to require the boot password. This means that all it takes to decrypt and copy my data partition is a hard reset into recovery.
I have done a fair bit of research into this to see if I was just missing a step or a missed step with no luck. I saw some posts from Motorolla / Lenovo that indicate this is no longer an option, I will post links below for the interested. I also saw a Moto G6 post talking about having to format, reboot into recovery, format again to get the decryption to work. I knew that it would be long shot but I gave this a try just in case but it did not help.
Does anyone have any information about this device, TWRP and secure boot? I know that decrypting /data in TWRP can be difficult but if I had to choose I would rather data partition is never mountable by TWRP over mountable with no password. Any information would be greatly appreciated. Thanks.
Motorolla Post indicating that Moto G6 Plus uses direct boot instead of secure boot
https://forums.lenovo.com/t5/Moto-G6-Moto-G6-Plus-Moto-G6/G6-Plus-can-t-find-Secure-Startup/m-p/4311477
Motorolla Post indicating this is new encryption method
https://support.motorola.com/uk/en/solution/MS129140
roomfool said:
First off thank you segra246x for making this. I had no problem following the instructions and got TWRP installed with no issue. I have also been able to successfully flash a bunch of different Pie GSIs (phhTreble, AOSP Extended) successfully.
I do however have a question that I cannot seem to find the answer too anywhere for the Moto G6 Plus. On past devices (i.e. Moto G5 Plus) I was able to configure the device to require a password or pin or pattern before the device would boot. Similarly TWRP would require this in order to mount /data. Depending on where you are looking online this could be called Secure Boot or Secure Startup. On this device however I cannot find the option when I set the password with any version of Android to require the boot password. This means that all it takes to decrypt and copy my data partition is a hard reset into recovery.
I have done a fair bit of research into this to see if I was just missing a step or a missed step with no luck. I saw some posts from Motorolla / Lenovo that indicate this is no longer an option, I will post links below for the interested. I also saw a Moto G6 post talking about having to format, reboot into recovery, format again to get the decryption to work. I knew that it would be long shot but I gave this a try just in case but it did not help.
Does anyone have any information about this device, TWRP and secure boot? I know that decrypting /data in TWRP can be difficult but if I had to choose I would rather data partition is never mountable by TWRP over mountable with no password. Any information would be greatly appreciated. Thanks.
Motorolla Post indicating that Moto G6 Plus uses direct boot instead of secure boot
https://forums.lenovo.com/t5/Moto-G...G6-Plus-can-t-find-Secure-Startup/m-p/4311477
Motorolla Post indicating this is new encryption method
https://support.motorola.com/uk/en/solution/MS129140
Click to expand...
Click to collapse
Hi, this has to do with the rom I think. I had LineageOS 15.1 installed and I had to decrypt the data with my password before I could do anything in twrp. I currently have the option to encrypt my phone on HavocOS under the security tab, but it doesn't work for now =))). On LOS15.1 it was enabled by default, so give it a try if this concerns you so much.
Thanks
randomanonymousname said:
Hi, this has to do with the rom I think. I had LineageOS 15.1 installed and I had to decrypt the data with my password before I could do anything in twrp. I currently have the option to encrypt my phone on HavocOS under the security tab, but it doesn't work for now =))). On LOS15.1 it was enabled by default, so give it a try if this concerns you so much.
Click to expand...
Click to collapse
OK I was not sure if this was more related to the ROM or TWRP, my bad for posting in the wrong place. I have tried the AOSPExtended 9 ROM and all 3 flavors of the phh treble 9 ROM with the same result. Have not had any luck installing Lineage or any of the 8.1 phh treble ROMs. I will keep digging to see if I can't find some info about this. Thanks.
Hi, my backups get stuck at 80-90% sometimes, does anyone have the same issue?
rooted kernel hiding bootloader unlock
with working sony stock fw fota updates
for Sony Xperia XZ1
Firmware Over the Air system updates have been disabled/not working with sony xperia phones with unlocked bootloader.
Also many sony drm functions are disabled if fw detects unlocked bootloader even if device master key was recovered.
I've implemented a kernel patch for xperia XZ1 Compact / XZ1 / XZ Premium phones that properly masks bootloader unlock status so it appears as still locked for sony stock firmwares.
This allows FOTA updates to be installed if running completely unmodified stock firmware. This is possible if this kernel is just booted from usb via fastboot instead of flashing it.
The kernel is pre-rooted, so you can have root as usual with magisk when running this kernel (you can use magisk system less patching to make changes to system/vendor partitions without actually modifying them).
For oreo fw the boot process is patched to hide magisk from sony ric daemon that stops the boot in case it thinks the bootloader is still locked. This special patch allows to pass safetynet including cts while having properly working magisk.
This kernel may be used (flashed) just to properly enable sony drm features, like video image enhancements, if device master key was recovered via locked state TA restore.
The bellow described way to install FOTA system update works with both - phone with TA restored and phone with drm keys lost. Both variants have been tested with xz1c.
How to use this kernel while planning to do FOTA system update eventually
Update: please see here for the latest usage instructions for kernels in flashable zip archive.
Please see screenshots bellow for this kernel in action (with xz1c) doing fota system update from oreo to pie and from pie to next pie version. There is also a video documenting this here. Few longer waiting parts have been cut out to fit the video under 15 minutes of youtube limit for not verified accounts.
if your bootloader is still locked
Use renoroot exploit to backup your TA, unlock your bootloader and restore TA-locked to recover device master key as described in
[XZ1c/XZ1/XZp] temp root exploit to backup drm keys implemented thread.
select one of the prepared kernels and download it
make sure you are running unmodified stock firmware
You need the version corresponding to the selected kernel - reflash the firmware to make sure it is unmodified.
Please note: any mount of /system or /vendor partitions in write mode would result with modifications even if nothing is copied there.
Be aware that some zip packages flashed from twrp may mount the partitions for write access even when that is not needed.
reboot the phone to fastboot mode
Use either "adb reboot bootloader" or
enter fastboot by holding powered off phone's volume up key while connecting it to PC via usb cable and use 'fastboot reboot bootloader' command.
boot the downloaded kernel via fastboot
For example (xz1c):
Code:
fastboot boot boot-G8441-47.1.A.16.20-hideunlock-rooted.img
enjoy your rooted phone which thinks it is still locked
Sony apps will be offered to install/update. System FOTA update may come.
Magisk will provide your root when magisk manager app is installed (offered on the first boot).
if you need to use a custom recovery, like TWRP
Do not flash it. If you do, FOTA update verification will fail.
Instead use 'fastboot boot' the same way as with the kernel above, but instead of the kernel, boot the twrp image without flashing it.
to install a FOTA system update
just start the update as usual
let it run until it finishes the installation
try to catch the restart then and hold volume up that time to enter fastboot
you need to use following command to make next boot working
Code:
fastboot reboot bootloader
use 'fastboot boot' to boot kernel for fw to which fota updating to,
for example (xz1c):
Code:
fastboot boot boot-G8441-47.2.A.4.45-hideunlock-rooted.img
if you miss the restart (or do not have the right kernel version),
it does not matter, the installation will finish even when bootloader unlock is detected with the last reboot to updated system,
so just 'fastboot boot' the corresponding 'hideunlock-rooted' kernel then
Alternative use of this kernel
If you do not like booting from usb via fastboot to startup your phone, you can flash the kernel and boot normally.
But if you like to install FOTA system update then, you would need to flash the stock kernel first in order to make the fw untouched again (assuming no other changes to the fw, like system or vendor partitions, have been done) and boot the patched kernel via 'fastboot boot' as described above.
You can backup stock kernel (and recovery) to avoid need to download full stock fw when you need to restore stock kernel & recovery when you decide to install fota system update - see here and following post for more details please.
If you do not care about FOTA, just do not install it.
And use this kernel just to enable all sony drm features that are available on a locked phone (assuming locked state TA has been restored).
In case you like to make some modifications to system or vendor partitions (as you do not care about fota), you would need to disable verity in the kernel - please see post#3 for noverity variants of oreo kernels and linked post describing howto switch verity off via magisk in all pie kernels.
Downloads
See the post#2 please.
Source code
patched kernel sources to hide bootloader unlock (my-bluhide/* branches)
https://github.com/j4nn/sonyxperiadev-kernel-copyleft
patched magisk sources to hide magisk from sony ric daemon on early boot phase (v19.1-manager-v7.1.2-ric branch)
https://github.com/j4nn/Magisk/tree/v19.1-manager-v7.1.2-ric
The patches are provided under GPL (that means you may include them in your builds, but you need to provide buildable source of released binaries /true for any kernel change btw/).
Credits
Thanks to @tonsofquestions for lot of initial testing of this concept when I did not have a phone with unlocked bootloader and for discovering the need to reboot to fastboot by a command to make the 'fastboot boot' command properly boot the supplied kernel image.
Thanks to @topjohnwu for his excelent magisk tool.
If you find my work useful, consider donating here please:
https://j4nn.github.io/donate/
Thank you.
XDA:DevDB Information
kernel_bluhide_poplar, Kernel for the Sony Xperia XZ1
Contributors
j4nn
Source Code: https://github.com/j4nn/sonyxperiadev-kernel-copyleft
Kernel Special Features: proper hiding of bootloader unlock, sony ric with magisk hack
Version Information
Status: Stable
Stable Release Date: 2019-02-10
Created 2019-02-10
Last Updated 2019-08-07
Downloads
- hideunlock kernel pre-rooted boot images:
Xperia XZ1 (G8341/G8343)
boot-G8341-47.1.A.16.20-hideunlock-magisk-19.1.img
boot-G8341-47.2.A.4.45-hideunlock-rooted.img
boot-G8341-47.2.A.6.30-hideunlock-rooted.img
boot-G8341-47.2.A.8.24-hideunlock-rooted.img
boot-G8341-47.2.A.10.28-hideunlock-rooted.img
boot-G8341-47.2.A.10.45-hideunlock-rooted.img
boot-G8341-47.2.A.10.62-hideunlock-magisk-19.3.img
Xperia XZ1 Dual (G8342)
boot-G8342-47.1.A.16.20-hideunlock-magisk-19.1.img
boot-G8342-47.2.A.4.45-hideunlock-rooted.img
boot-G8342-47.2.A.6.30-hideunlock-rooted.img
boot-G8342-47.2.A.8.24-hideunlock-rooted.img
boot-G8342-47.2.A.10.28-hideunlock-rooted.img
boot-G8342-47.2.A.10.45-hideunlock-rooted.img
boot-G8342-47.2.A.10.62-hideunlock-magisk-19.3.img
- hideunlock kernels flashable to multi fw versions (see here for usage howto):
Xperia XZ1 (G8341/G8343)
kernel-G8341-47.1.A.16.20-hideunlock.zip
kernel-G8341-47.2.A.10.62-hideunlock.zip
kernel-G8341-47.2.A.10.80-hideunlock.zip
kernel-G8341-47.2.A.10.107-hideunlock.zip
kernel-G8341-47.2.A.11.228-hideunlock.zip
Xperia XZ1 Dual (G8342)
kernel-G8342-47.1.A.16.20-hideunlock.zip
kernel-G8342-47.2.A.10.62-hideunlock.zip
kernel-G8342-47.2.A.10.80-hideunlock.zip
kernel-G8342-47.2.A.10.107-hideunlock.zip
kernel-G8142-47.2.A.11.228-hideunlock.zip
Screenshots of XZ1c FOTA system update from oreo 47.1.A.16.20 to pie 47.2.A.4.45
(video available here)
Downloads
This is for alternative use only - please see post#10 for more details.
boot-G8341-47.1.A.16.20-hideunlock-magisk-19.1-noverity.img
boot-G8342-47.1.A.16.20-hideunlock-magisk-19.1-noverity.img
Screenshots of XZ1c FOTA system update from pie 47.2.A.4.45 to pie 47.2.A.6.30 version
(video available here since 08:10 time)
This should be the first paragraph!
j4nn said:
[...] use this kernel just to enable all sony drm features that are available on a locked phone (assuming locked state TA has been restored).
Click to expand...
Click to collapse
Since I do not care about OTA updates, because we can download every firmware via XperiFirm and flash it via newflasher, I will use your modded kernel in the 'alternative' way! :good:
j4nn said:
Alternative use of this kernel
If you do not like booting from usb via fastboot to startup your phone, you can flash the kernel and boot normally.
Click to expand...
Click to collapse
@j4nn - I flashed "boot-G8341-47.2.A.6.30-hideunlock-rooted.img" on my G8341 which has the latest Pie firmware (G8341_47.2.A.6.30_Customized DE_1310-4290_R6C) installed, but the device did not boot into Android after that! :crying: I flashed the latest official Magisk before your kernel. Do I need to use your patched Magisk instead?
Did you forgot to add the patched magisk flashable img file? "hide magisk from sony ric daemon on early boot phase (v18.1-manager-v7.0.0-ric branch)"
j4nn said:
Downloads
Click to expand...
Click to collapse
Maybe the firmware version is not compatible with the one you took the kernel from? The firmware folder includes:
kernel_X-FLASH-ALL-C93B.sin
boot/bootloader_X_BOOT_MSM8998_LA2_0_P_107_X-FLASH-ALL-C93B.sin
...
Click to expand...
Click to collapse
@SGH-i200, I just compared the stock kernel boot image extracted from G8341_Customized DE_1310-4290_47.2.A.6.30_R6C (which I have used to create it) and it seems all good to me:
- os version and patch level match
- device tree blobs are the same
- kernel command line is the same
- extracted kernel config is (except few comments as it is usual) the same, with poplar target (i.e. single sim XZ1)
- ramdisk is the same except changes that are expected (integrated magisk in order to provide root when booted from usb having unmodified stock fw)
Did it result with an infinite hang during boot (which phase of the boot splash animation)?
Or did it reboot during boot (a boot-loop) - which phase?
I am sorry I forgot to mention the kernels for other targets than xz1c have not been tested (I have only xz1c for testing).
But it should be safe to test the above howto as described. Even if the kernel was flashed (instead of just fastboot booted), recovering from this should be as simple flashing stock kernel back.
Anybody else tested this with XZ1?
j4nn said:
Did it result with an infinite hang during boot (which phase of the boot splash animation)?
Or did it reboot during boot (a boot-loop) - which phase?
Click to expand...
Click to collapse
The SONY white splash screen appeared (with only black SONY text) and then it hang forever.
j4nn said:
Even if the kernel was flashed (instead of just fastboot booted), recovering from this should be as simple flashing stock kernel back.
Click to expand...
Click to collapse
I flashed the kernel_X-FLASH-ALL-C93B.sin (and everything else as I did to upgrade to latest Pie) from the stock fw to recover.
After the XZ1 was booting again, I executed the fastboot booting, without problems!
adb reboot bootloader
fastboot boot boot-G8341-47.2.A.6.30-hideunlock-rooted.img
Click to expand...
Click to collapse
@SGH-i200, that sounds good. Now just flash it:
Code:
adb reboot bootloader
fastboot flash boot boot-G8341-47.2.A.6.30-hideunlock-rooted.img
disconnect from usb and power on.
If it booted from usb, I believe it should boot just fine if flashed as above too.
j4nn said:
If it booted from usb, I believe it should boot just fine if flashed as above too.
Click to expand...
Click to collapse
I flashed your patched kernel again and got into a bootloop: Bootloader unlocked warning and white SONY splash screen in an endless loop.
Since my XZ1 was connected to my Windows workstation already, I simply long pressed the volume up button till the notification light went blue, and booted into twrp to restore the stock kernel (rooted by Magisk to remove the dmverity stuff).
@SGH-i200, you are right, it is the verity thing.
I've assumed that verity is ignored when kernel detects unlocked bootloader, because the dm-android-verity kernel component used that is_unlocked() call to:
/* Allow invalid metadata when the device is unlocked */
- that comment is in the dm-android-verity.c source code.
But it looks like that is only a corner case and if verity metadata is valid, verity is active (if not disabled in device tree) even with unlocked bootloader.
Now I am wondering: for OTA updates we need untouched system, so having verity enabled in the kernel is good for this purpose - when you flash something that writes to system or vendor, you may detect it soon enough to be able to tell what it was. The main feature of magisk is that you should be able to "modify" system "systemlessly", i.e. without really writing to system or vendor partitions.
From this point of view it should be all good then.
But I understand that the "alternative" use of this kernel, i.e. not planning to do FOTA at all, just using only the unlock hide feature restoring drm functionality and using root the old way (with real writes to system) may be liked.
For this, just use magisk manager main screen, in "Advanced Settings" unselect the "Preserve AVB 2.0/dm-verity" option and then use the "Magisk INSTALL" button, confirm install of Magisk-v*.zip, select "Patch Boot Image File", browse to sdcard where you put my kernel image and select it.
Magisk will repack the boot image disabling dm-verity in device tree blobs, noting where you can find patched_boot.img.
Flash that and you should be good to go.
This procedure is valid for all my pie kernel builds.
I will repack the oreo 16.20 build as using magisk manager gui would not keep the magisk patch for sony ric daemon.
-- edit --
Updated post#3 with downloads of oreo kernels noverity repacks.
Thanks for the kernel but after flashing the kernel the phone don't go into doze (deep sleep). Any suggestions on this?
j4nn said:
Now I am wondering: for OTA updates we need untouched system, so having verity enabled in the kernel is good for this purpose - when you flash something that writes to system or vendor, you may detect it soon enough to be able to tell what it was. The main feature of magisk is that you should be able to "modify" system "systemlessly", i.e. without really writing to system or vendor partitions. From this point of view it should be all good then.
Click to expand...
Click to collapse
I use AdAway and activated NightLight by copying a apk to /vendor/overlay .
Thanks for creating the noverity Oreo kernel versions! :good:
---------- Post added at 09:04 AM ---------- Previous post was at 08:57 AM ----------
j4nn said:
The main feature of magisk is that you should be able to "modify" system "systemlessly", i.e. without really writing to system or vendor partitions.
But I understand that the "alternative" use of this kernel, i.e. not planning to do FOTA at all, just using only the unlock hide feature restoring drm functionality and using root the old way (with real writes to system) may be liked.
For this, just use magisk manager main screen, in "Advanced Settings" unselect the "Preserve AVB 2.0/dm-verity" option and then use the "Magisk INSTALL" button, confirm install of Magisk-v*.zip, select "Patch Boot Image File", browse to sdcard where you put my kernel image and select it.
Magisk will repack the boot image disabling dm-verity in device tree blobs, noting where you can find patched_boot.img. Flash that and you should be good to go. This procedure is valid for all my pie kernel builds.
Click to expand...
Click to collapse
If I flash your patched Pie kernel via TWRP and flash Magisk right after, this should have the same effect as patching your kernel via the Magisk app, right?
@j4nn - "using root the old way (with real writes to system)" - will flashing Magisk via TWRP change this to system-less root?
sinkoo1979 said:
Thanks for the kernel but after flashing the kernel the phone don't go into doze (deep sleep). Any suggestions on this?
Click to expand...
Click to collapse
I have no idea. In my opinion, if you get such behaviour with my kernel, you will get exactly the same behaviour with stock kernel of the same version.
My kernel is compiled from sony's open source kernel package, with kernel config that's identical (except few comment lines) to the one compiled in stock kernel.
My kernel patch only fixes kernel command line that comes from bootloader and hijacks trust zone api to mask the bootloader status to appear as still locked to firmware's userspace.
These changes hardly could have any influence on power saving behaviour.
Please flash the same version stock kernel and test again for deep sleep.
Could not be that caused by some app you've installed?
SGH-i200 said:
If I flash your patched Pie kernel via TWRP and flash Magisk right after, this should have the same effect as patching your kernel via the Magisk app, right?
@j4nn - "using root the old way (with real writes to system)" - will flashing Magisk via TWRP change this to system-less root?
Click to expand...
Click to collapse
Most likely flashing magisk via twrp after flashing the patched pie kernel would disable verity too.
Using the image file - you have it under your control.
Flashing from twrp - some magisk scripting tries to detect if verity should be disabled or not.
Also a kernel image already containing magisk contains the setting of verity and encryption - not sure how that is used when flashing magisk again over it.
I tried it with my xz1c and verity was flipped from enabled to disabled - so the same effect (this time).
But as described, some detection is used, so the results might not always be the same.
j4nn said:
I have no idea. In my opinion, if you get such behaviour with my kernel, you will get exactly the same behaviour with stock kernel of the same version.
My kernel is compiled from sony's open source kernel package, with kernel config that's identical (except few comment lines) to the one compiled in stock kernel.
My kernel patch only fixes kernel command line that comes from bootloader and hijacks trust zone api to mask the bootloader status to appear as still locked to firmware's userspace.
These changes hardly could have any influence on power saving behaviour.
Please flash the same version stock kernel and test again for deep sleep.
Could not be that caused by some app you've installed?
reflashed stock firmware and everything is fine. Thanks for the kernel.
Click to expand...
Click to collapse
j4nn said:
Downloads
This is for alternative use only - please see post#10 for more details.
boot-G8341-47.1.A.16.20-hideunlock-rooted-noverity.img
boot-G8342-47.1.A.16.20-hideunlock-rooted-noverity.img
Screenshots of XZ1c FOTA system update from pie 47.2.A.4.45 to pie 47.2.A.6.30 version
(video available here since 08:10 time)
Click to expand...
Click to collapse
Hi j4nn
I unlocked my bootloader on 47.1.A.16.20 and lost my drm keys. I upgraded via newflasher_v13 to 47.2.A.4.45 Customised SG as that is where i am based and where my phone is from. Unfortunately when I flash boot-G8342-47.2.A.4.45-hideunlock-rooted.img my phone still boots up showing the device has been unlocked and the Backup and Restore feature of Xperia devices does not work. Am I correct to say if I lost my drm keys that I am unable to use this kernel to hide my bootloader unlock?
Thank you for answering me.
Working fine on xz1 pie 47.2.A.6.30 with blx firmware, Kernel flashed with twrp, widevine is L1 now, and Bravia engine working
@leonaheidern, the kernel would hide the unlocked bootloader regardless you lost drm keys or restored locked TA.
Please check you kernel build date when you boot your phone in about menu.
@j4nn, I have a quick question and a bit off topic, I'm still tinkering a bit but I did manage to backup my ta. and I flashed janjan's so things may seem a bit off, (see pic).. but I did restore my ta. before flashing Jan's kernel, any idea what may happen if I flashed yours on top?
oh and everything is working..
@lilbrat, I guess that the result would be the same if you flashed my kernel without flashing janjan's before it.
Just note please, my kernels as they are have verity enabled, so you need to have unmodified stock fw.
Or disable verity as hinted for alternative use.
With my kernel and restored TA your security screen would look perfect as with a still locked phone.
j4nn said:
@lilbrat, I guess that the result would be the same if you flashed my kernel without flashing janjan's before it.
Just note please, my kernels as they are have verity enabled, so you need to have unmodified stock fw.
Or disable verity as hinted for alternative use.
With my kernel and restored TA your security screen would look perfect as with a still locked phone.
Click to expand...
Click to collapse
OK.. thanks for the info... now I have another question, now that xz1 has a new update out and granted it will take you a bit to catch up if you need to redo all your kernels you have going... (great work by the way) Will I need to reflash my ta. backup for the new firmware and or just your kernel?
Hi all,
I made a huuuuuuge mistake : after a failing update of Magisk (don't know why, I already made zillion of updates), my phone is stuck in fastboot mode. And now is the big mistake : I performed a "fastboot lock" (don't ask why, stupid is stupid).
=> I can't boot in recovery because TWRP is not official
=> I can't unlock it as to unlock, I have to boot a full image and select "allow OEM unlock" in the system preferences
=> I can't even flash stock boot.img or system.img (I could find stock firmware), beacause I receive this error :
$ fastboot flash boot boot.img
Sending 'boot' (18472 KB) OKAY [ 0.551s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
Any idea on how to recovery my phone ? :crying:
gbetous said:
Hi all,
I made a huuuuuuge mistake : after a failing update of Magisk (don't know why, I already made zillion of updates), my phone is stuck in fastboot mode. And now is the big mistake : I performed a "fastboot lock" (don't ask why, stupid is stupid).
=> I can't boot in recovery because TWRP is not official
=> I can't unlock it as to unlock, I have to boot a full image and select "allow OEM unlock" in the system preferences
=> I can't even flash stock boot.img or system.img (I could find stock firmware), beacause I receive this error :
$ fastboot flash boot boot.img
Sending 'boot' (18472 KB) OKAY [ 0.551s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
Any idea on how to recovery my phone ? :crying:
Click to expand...
Click to collapse
You should be able to flash a stock kdz
Sent from my LG-H850 using XDA Labs
To others who have still the phone unlocked: just flash twrp to boot partition. Then boot, you will be in twrp. From there, copy the backup files in /data/ folder to the pc and flash them back with fastboot flash boot boot.img. Tha backups are gz compressed, so you need to extract them before flashing. At the end you will have back Magisk 20.1 and everything else working.
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
totalnoob34 said:
You should be able to flash a stock kdz
Sent from my LG-H850 using XDA Labs
Click to expand...
Click to collapse
Yes !
I used the official LG tool for recovery (see www.lg.com). The magic key is "vol UP + USB plug" and the phone switches in some specific recovery mode. Nothing particular to do, the tool is automatically downloading the latest offical firmware and flash it.
Thanks !!!
tremalnaik said:
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
Heck. I just upgraded but didn't reboot yet, can I install 20.1 via magisk manager and be safe?
Sent from my LG-H850 using XDA Labs
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
tremalnaik said:
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
Heck. I just upgraded but didn't reboot yet, can I install 20.1 via magisk manager and be safe?
Sent from my LG-H850 using XDA Labs
I think that Magisk Manager already patched the boot image, I don't know whst will happen if you patch the 20.2 version with the 20.1. I would suggest you to check in /data/ folder for the boot image backup, copying them to pc if they are there, and then trying to reboot directly into recovery (Magisk Manager>Modules>Menu>Reboot to recovery) and from there flash back the old boot image. In case after reboot you get into fastboot, you can just flash the backup boot image with fastboot flash boot boot.img
tremalnaik said:
Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
My G5 (H830) didn't go into fastboot mode. Are you on stock ROM?
My H850 was stuck in fastboot mode after magisk update. I entered in TWRP and reinstall the kernel. Now, it is stuck on LG logo It seems that System is damaged too. Does someone know what magisk have changed in the System partition? Probably it can be fixed somehow...
For the future, my plan is to cut magisk internet access from the firewall settings, so it will be updated just never.
---------- Post added at 10:25 PM ---------- Previous post was at 10:09 PM ----------
tremalnaik said:
To others who have still the phone unlocked: just flash twrp to boot partition. Then boot, you will be in twrp. From there, copy the backup files in /data/ folder to the pc and flash them back with fastboot flash boot boot.img. Tha backups are gz compressed, so you need to extract them before flashing. At the end you will have back Magisk 20.1 and everything else working.
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
Can you please provide more details about what is backed up in /data and how it can restore the System? I looked in /data and /data/backups but I can't find something like a system backup...
SrZambie said:
My G5 (H830) didn't go into fastboot mode. Are you on stock ROM?
Click to expand...
Click to collapse
Yes, stock Oreo ROM with MK2000 kernel.
tinyspeck said:
My H850 was stuck in fastboot mode after magisk update. I entered in TWRP and reinstall the kernel. Now, it is stuck on LG logo It seems that System is damaged too. Does someone know what magisk have changed in the System partition? Probably it can be fixed somehow...
For the future, my plan is to cut magisk internet access from the firewall settings, so it will be updated just never.
---------- Post added at 10:25 PM ---------- Previous post was at 10:09 PM ----------
Can you please provide more details about what is backed up in /data and how it can restore the System? I looked in /data and /data/backups but I can't find something like a system backup...
Click to expand...
Click to collapse
System is by definition what Magisk shouldn't touch. Are you stuck on the static LG logo or the animated one?
In /data/ folder you should find at least one folder named "magisk" with others letters following. Inside of it you will find a compressed archive with the boot image inside. You can flash it back with both TWRP or fastboot.
tremalnaik said:
Yes, stock Oreo ROM with MK2000 kernel.
Click to expand...
Click to collapse
I looked around and found that this isn't LG specific. Someone with the Razor Phone 2 had their partitions wiped aswell. It sounds like it's having issues installing with certain ROMs which would explain why I wasn't affected. It's best to stay with 20.1 on stock ROMs for right now until it's fixed.
tremalnaik said:
Yes, stock Oreo ROM with MK2000 kernel.
System is by definition what Magisk shouldn't touch. Are you stuck on the static LG logo or the animated one?
In /data/ folder you should find at least one folder named "magisk" with others letters following. Inside of it you will find a compressed archive with the boot image inside. You can flash it back with both TWRP or fastboot.
Click to expand...
Click to collapse
It was stuck on static LG logo. I reflashed the same kernel which I installed last July (mk2000 v2.1). I also wiped cache and dalvik (kernel shouldn't need this but just in case...). It is strange that it stuck on static LG logo because later, I followed your advice and I installed the boot.img from /data/magisk_123... and the phone is back, working as new
So magisk is not so bad as it has a backup solution.
Thanks for your support
Static logo is loaded before system, so the problem wasn't the system partition. Probably my phone couldn't load boot partition at all, falling back to fastboot, while yours was loading boot partition but an error was occourring the meanwhile, leaving it at the logo. I'm glad that you solved the problem.
While reinstalling Magisk after the kernel, don't forget to check if the torch is still working: if it's not working, just flash once again the kernel and it should be ok.