Related
So I thought of installing a new ROM to my XZU today. First I rooted my device using the following guide : https://www.youtube.com/watch?v=BkQT3nX5yWM. (As I had updated my device to Android 4.4.4 and had .108 FW). I successfully rooted the phone and took a TA Backup. Afterwards, I went on to unlock the bootloader and unlocked it successfully as well. As I wanted to install the ParanoidAndroid 4+ ROM, I downloaded it and got the boot.img from the ZIP file, and flashed it using the Flashtool. However, afterwards, when I tried to go the recovery mode, it is stuck on the Sony Logo, and doesn't blink the notification LED in order to do so.
Did I do anything wrong? I am quite a noob when it comes to XZU related stuff..so I would really appreciate if someone can help me out..
Thanks in advance!
EDIT: (Thought of editing this thread rather than deleting it so that it could be an help for someone who faces a similar problem) I was able to make my device up and running again by flashing the FTF found in this thread: http://forum.xda-developers.com/showthread.php?t=2798690.
Now, I have again come to the status where I have installed a recovery successfully and unlocked my bootloader, and I want to install PA 4+ to my device. Would really appreciate if anyone can guide me on how to do this
It doesn't sound like you did any thing wrong.
Do you have [NUT]'s recovery installed now?
Do a nandroid backup if you do, saves the whole flashing a FTF step if something goes wrong
Did you get the correct PA? what date?
PA should install fron [NUT]'s recovery or you could hotboot the boot.img with flashtool (this wont over write you current kernel) this will let you test if it does work
blueether said:
It doesn't sound like you did any thing wrong.
Do you have [NUT]'s recovery installed now?
Do a nandroid backup if you do, saves the whole flashing a FTF step if something goes wrong
Did you get the correct PA? what date?
PA should install fron [NUT]'s recovery or you could hotboot the boot.img with flashtool (this wont over write you current kernel) this will let you test if it does work
Click to expand...
Click to collapse
Thank you. Yes, I read quite a lot yesterday and found out that I have followed the steps properly. So I am wondering if it has got anything to do with the boot.img from the PA ROM?
And yes I did a nandroid backup previously as well, however, I was not aware of how to restore it because I couldn't access the recovery mode. Can I do the restore using the FlashTool? or some other tool in such a scenario?
I downloaded "pa_togari-4.5-BETA1-20140805.zip" available in this link: http://aospal.hostingsharedbox.com/aospal/roms/togari/ . Should I try the last stable release rather than the beta one?
I am sorry for this noobish question, but what exactly is the purpose of "boot.img"? Is it the kernel of the new ROM that I am going to install? or is it something else? I kinda think that the problem might have been with the way I flashed the boot.img previously. I used the option "SELECT SYSTEM TO FLASH" under the fastboot of FlashTool in order to do so. Is it wrong? Should I use the "SELECT KERNEL TO FLASH"?
Thank you again
EDIT: I used the "SELECT KERNEL TO FLASH" option in the Flashtool, to flash the boot.img and I was able to flash the PA 4+ successfully! ..Thank you!
Prabash said:
EDIT: I used the "SELECT KERNEL TO FLASH" option in the Flashtool, to flash the boot.img and I was able to flash the PA 4+ successfully! ..Thank you!
Click to expand...
Click to collapse
Good to hear you got it sorted, but I'll run through what you did wrong...
Thank you. Yes, I read quite a lot yesterday and found out that I have followed the steps properly. So I am wondering if it has got anything to do with the boot.img from the PA ROM?
Click to expand...
Click to collapse
So you now know it wasn't the boot.img :laugh:
And yes I did a nandroid backup previously as well, however, I was not aware of how to restore it because I couldn't access the recovery mode. Can I do the restore using the FlashTool? or some other tool in such a scenario?
Click to expand...
Click to collapse
Normally the way to recover would be to flash a boot.img that works and then enter recovery rand restore, easy when you flash the boot.img correctly
I am sorry for this noobish question, but what exactly is the purpose of "boot.img"? Is it the kernel of the new ROM that I am going to install? or is it something else?
Click to expand...
Click to collapse
The boot image is the kernel and recovery backed into one (it's a Sony thing ) and it belongs on the /boot partition
I kinda think that the problem might have been with the way I flashed the boot.img previously. I used the option "SELECT SYSTEM TO FLASH" under the fastboot of FlashTool in order to do so. Is it wrong? Should I use the "SELECT KERNEL TO FLASH"?
Click to expand...
Click to collapse
I think you have figured that one out now :cyclops:. So what you did was write the kernel and recovery to the /system partition, not to where it belongs ie /boot
You can also use the "select kernel to boot (hotboot)" (or what ever words it uses) to boot a kernel/recovery and not change the one on the /boot partition - can be handy at times
I hope that helps you understand some bits about your new Sony ZU
Yep! thanks a lot for your help! Really appreciate it! :victory:
Here is the last version at the moment of the Maze alpha ROM (tested only in 4GB version)
It's a complete ROM, not an OTA update, it can be flashed using the provided TWRP 3.2.1 version, I ported from a Jemmini (many thanks) version for Bluboo S1.
Unfortunately, the TWRP cannot be flashed (issue with the touch panel), only launched by fastboot.
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
There is also a SPFlashTool clean version of this ROM, useful in case of troubles (as official: no root, no busybox)
1- Reboot you phone in fastboot mode : adb reboot bootloader
2- Flash the provided TWRP : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3- Reboot to TWRP recovery
4- copy in your SDCARD and install, in the running TWRP, the downloaded ROM V09 : Maze_Alpha_4GB_v09_TWRP.zip
The first boot take some minutes so be patient.
Here the SPFlashTool versions :
MAZE_Alpha_4GB_V09_SPFT.zip
Here, if needed, my V09 TWRP backup (new one from 21/04/2018) :
TWRP_BACKUP_MAZE_Alpha_A_V09.zip
Credits to Jemmini and Magisk team.
Can you make this for the 6 gb version?
many thanks gonna ty it soon
Nautilus99 said:
Can you make this for the 6 gb version?
Click to expand...
Click to collapse
I do not have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
dreambo said:
I do note have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
Click to expand...
Click to collapse
Yes i know its sad, i did a backup of mine and root it but it didnt work the backup i had to do clean flash, if we can manage to have a twrp and a source of the stock roms we could make a deabloat and put update apps ( menssages, calendar etc) and put mods for awsome features i dont see RR or lineage putting thier hands on this phone
Thanks for this Rom.
Is there any root for the maze alpha x?
here
WiddleyScudds said:
Is there any root for the maze alpha x?
Click to expand...
Click to collapse
read
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
Click to expand...
Click to collapse
thorfr said:
read
Click to expand...
Click to collapse
I have an alpha x, not alpha.
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
rzoli71 said:
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
Click to expand...
Click to collapse
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
thank you
After I installed this rom, and freezed the hot knot, baidu_location FM Radio, etc, the BT connection did not break.
dreambo said:
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
Click to expand...
Click to collapse
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
ahorntaler said:
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
Click to expand...
Click to collapse
No I not have any source, I am just a simple user like any other.
If I have any source or if I can make a ROM for MAZE Alpha X, I will do it and I will share it with every body, as I do until now for the MAZE Alpha 4/64
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
iBolitN said:
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
Click to expand...
Click to collapse
Unfortunatly no. As you will see repeated times in the forum, people have issue with phone not booting after changing from stock recovery to twrp. This is do (most likely from) to verified boot setting. And by unlocking bootloader we can bypass verified boot. So without unlock you might get a successfull load into twrp, but android will not boot.
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
stargazer78 said:
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
Click to expand...
Click to collapse
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Thanks a lot for your reply....
the problem is that i cant boot into fastboot to unlock bootloader....
the phone bootloops all the time, shows the red state alert and even with vol+ pressed the menu to choose recovery or fastboot doesn't apear... thanks again.
dreambo said:
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Click to expand...
Click to collapse
Is there any way to unlock the bootloader in my situation or/and enter the fastboot mode in order to follow your steps... thanks.
Hello,
I just managed to generate TWRP recovery for S912 Android 9 version, you can install the official TWRP app to flash with in the ROM.
But after reboot the ROM goes back to stock recovery, so for now i am installing everytime i need to use recovery, unless i am able to find a permanent solution.
Link to TWRP
Suggestions welcome if you have for keeping the recovery persistent.
Regards
I was able to keep it persistent but if I go to install all I get for folder names is a mess. Using Superceleron's generic SC normal pie rom. Appeared to install magisk but magisk manager didn't see it and I lost superuser access so I had to reflash rom. I hope you or others can pick up on TWRP for this. Unfortunately I don't have the knowledge so can only test. Liking the Superceleron rom on my T95Z(2/16) much better than poison or stock (so far... still testing...). Glad to see these old devices getting some new love. Hopefully it will continue.
rickpub said:
I was able to keep it persistent but if I go to install all I get for folder names is a mess. Using Superceleron's generic SC normal pie rom. Appeared to install magisk but magisk manager didn't see it and I lost superuser access so I had to reflash rom. I hope you or others can pick up on TWRP for this. Unfortunately I don't have the knowledge so can only test. Liking the Superceleron rom on my T95Z(2/16) much better than poison or stock (so far... still testing...). Glad to see these old devices getting some new love. Hopefully it will continue.
Click to expand...
Click to collapse
Jumbled charcters is because the ROM is encrypted and this recoveery is not able to decrypt it.
Bumping this, going to test this on Aidans rom
Update: could not confirm if it works it looks like the reset button is not mapped on Aidans rom. The weird thing is it works if I use the USB burn tool but not when I do a regular boot.
Doctorbeefy said:
Update: could not confirm if it works it looks like the reset button is not mapped on Aidans rom. The weird thing is it works if I use the USB burn tool but not when I do a regular boot.
Click to expand...
Click to collapse
Do you mean we can flash using amlogic usb burning tool, I am now struggling to install this ROM on khadas 64 android 9 ROM by Highway star
Hi @eagledipesh!
I managed to install your TWRP successfully on Aidan's ROM, thank you very much!
First I unpacked the Aidan' ROM with the Customizatio Tool, then I replaced the original recovery with your TWRP. I repackaged the ROM and flashed it with the AMLogic USB Burning Tool.
With TWRP and I did a full backup and I was also able to restore without errors. However, after restoring and booting the system, it gets stuck on AndroidTV splash screen.
Maybe I need to port the correct TWRP, because when unpacking your recovery with AIK, I saw in one of the files that the model is gxm_q201_2g, but my Android Box is gxm_q200_3g.
1. What base TWRP did you use to create your TWRP?
2. I tried porting TWRP myself from Aidan's ROM recovery, I can even get into recovery, but the letters are all scrambled. Can you help me make my own port?
ulissesemuman said:
Hi @eagledipesh!
I managed to install your TWRP successfully on Aidan's ROM, thank you very much!
First I unpacked the Aidan' ROM with the Customizatio Tool, then I replaced the original recovery with your TWRP. I repackaged the ROM and flashed it with the AMLogic USB Burning Tool.
With TWRP and I did a full backup and I was also able to restore without errors. However, after restoring and booting the system, it gets stuck on AndroidTV splash screen.
Maybe I need to port the correct TWRP, because when unpacking your recovery with AIK, I saw in one of the files that the model is gxm_q201_2g, but my Android Box is gxm_q200_3g.
1. What base TWRP did you use to create your TWRP?
2. I tried porting TWRP myself from Aidan's ROM recovery, I can even get into recovery, but the letters are all scrambled. Can you help me make my own port?
Click to expand...
Click to collapse
I used one of the twrp port guides, twrp was stock one, with stock recovery extracted from initial Android 9 builds by Highway star'
You can use the official twrp as base and then recovery from any of rom for your device
eagledipesh said:
I used one of the twrp port guides, twrp was stock one, with stock recovery extracted from initial Android 9 builds by Highway star'
You can use the official twrp as base and then recovery from any of rom for your device
Click to expand...
Click to collapse
Are you talking about the Wiko Highway Star? Any special reason for using this ROM as a base? How do I know which version of TWRP to use?
i create a twrp for my amlogic T972 but can't boot into it, don't know where to start fix bug
Can you help me build a twrp for this? Or can you teach me do that? Thank you @eagledipesh
Is there now a working TWRP for the Yoka KB2 Pro 3gb on Android 9.0? I would prefer to have an img file, but if there is really no other way, I would also take the zip version.
Thank you and best regards
Hi using latest updated stock rom with root..
Magisk
New August update doesn’t install..
Before i used to install updates in root..
Now cant..
Help..
Do you have twrp installed and if so did you flash any mods to the system?
If no mods were installed just flash the stock boot.img for your firmware version using fastboot and reboot and apply the update
garylawwd said:
Do you have twrp installed and if so did you flash any mods to the system?
If no mods were installed just flash the stock boot.img for your firmware version using fastboot and reboot and apply the update
Click to expand...
Click to collapse
I have only magisk.. I got no mods.. Only by magisk i installed everything... How to get stock boot img? U mean unroot?
I have twrp sharp installed.on slot...
Sami Devo said:
I have only magisk.. I got no mods.. Only by magisk i installed everything... How to get stock boot img? U mean unroot?
I have twrp sharp installed.on slot...
Click to expand...
Click to collapse
Custom recovery that's why you cant install. Ota updates don't usually work with a custom recovery installed. You will have to flash stock boot.img there is a whole thread about this and all versions of the stock boot.img here https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page43
You were even the last person to comment on that thread
My build..
garylawwd said:
Custom recovery that's why you cant install. Ota updates don't usually work with a custom recovery installed. You will have to flash stock boot.img there is a whole thread about this and all versions of the stock boot.img here https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page43
You were even the last person to comment on that thread
Click to expand...
Click to collapse
But i had custom recovery and it installed before..the boot.img have to match with current build? For fastboot flash?? And which slot i have to flash the boot?
This might help (as long as you really read it and follow instructions): https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291
_mysiak_ said:
This might help (as long as you really read it and follow instructions): https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291
Click to expand...
Click to collapse
This link u give is for flash fastboot rom
Should i uninstall magisk and try?
Sami Devo said:
This link u give is for flash fastboot rom
Click to expand...
Click to collapse
Maybe try to read it at least one more time..
same but different problem.
I'm having somewhat similar problem here, but the thing is, I'm using stock mi a3, without any custom bootloader, twrp, rom, etc.
currently in version 11.0.17.0.QFQMIXM
trying to install the august security update that was supposed to be version 11.0.20.0
updater showed the august update as 464mb, which is weird as its supposed to be 34mb or so.
any help from the experts here are kindly appreciated.
I have no custom recovery, or magisk but have same problem
So I solved the problem as I love root .. I had to loose recovery sharp... Now I have no recovery . I flashed stock ROM of Build 19 and installed the latest OTA . After then I extracted the boot image of stock ROM then I patch stock boot image of latest build.i got now root with magisk with no recovery . I hope I can install future OTA with the method..
If u can't install u must have to flash fastboot..
I have tried restoring stock boot.img of build 19.. but doesn't installed.. although I removed custom recovery but still couldn't install OTA..
Sami Devo said:
So I solved the problem as I love root .. I had to loose recovery sharp... Now I have no recovery . I flashed stock ROM offer BL 19 and installed the latest OTA . After then I extracted the boot image of stock ROM then I patch stock boot image of latest build.i got now root with magisk with no recovery . I hope I can install future OTA with the method..
If u can't install u must have to flash fastboot..
I have tried restoring boot.img of build 19.. but doesn't installed.. although I removed custom recovery but still couldn't install OTA..
Click to expand...
Click to collapse
thanks for the great advice. anyone willing to do the needful, might as well do as suggested. but i kind of trying to keep things stock as much as i can, dont have the time to fiddle around as much. this phone is buggy enough as it is
decided to backup everything and reset for now. might root if resetting didnt fix the issue. cheers mate! :good:
weeeeeeeb said:
thanks for the great advice. anyone willing to do the needful, might as well do as suggested. but i kind of trying to keep things stock as much as i can, dont have the time to fiddle around as much. this phone is buggy enough as it is
decided to backup everything and reset for now. might root if resetting didnt fix the issue. cheers mate! :good:
Click to expand...
Click to collapse
???Yah.. i have some apps which i must use! Such as greenify , titanium backup.. those r core of root..
Am looking forward to meet another update challenge. Am ready.
weeeeeeeb said:
I'm having somewhat similar problem here, but the thing is, I'm using stock mi a3, without any custom bootloader, twrp, rom, etc.
currently in version 11.0.17.0.QFQMIXM
trying to install the august security update that was supposed to be version 11.0.20.0
updater showed the august update as 464mb, which is weird as its supposed to be 34mb or so.
any help from the experts here are kindly appreciated.
Click to expand...
Click to collapse
No its not weird. Becoz july update n also August both have to installed by u...thats y its not only 35mb.ur build is too old. It ought to be a big update
Tyrese117 said:
I have no custom recovery, or magisk but have same problem
Click to expand...
Click to collapse
Then u need to flash fastboot rom
Sami Devo said:
Then u need to flash fastboot rom
Click to expand...
Click to collapse
I have installed July patch without any problem
I have solved this problem
Download recovery rom and flash from stock recovery: APPLY UPDATE FROM SD CARD
Tyrese117 said:
I have solved this problem
Download recovery rom and flash from stock recovery: APPLY UPDATE FROM SD CARD
Click to expand...
Click to collapse
this is very hard work.. i cant do that in every month and retaining root again!
Official TWRP is now available: https://twrp.me/asus/zenfone9.html
IMPORTANT NOTES:
CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6).
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2202
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Hermann2306 said:
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Click to expand...
Click to collapse
If you're not on stock kernel, then that's probably the problem. I know the custom kernel situation is different on this device than previous ones. This may be something that @Freak07 & I have to look into together. In the meantime, can you restore back to stock kernel and confirm that TWRP works, and then install Kirisakura and see if everything still works?
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Hermann2306 said:
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Click to expand...
Click to collapse
It doesn't sound like you followed the procedure in the Kirisakura thread FAQ to fully return to stock. Can you confirm exactly what you did?
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Hermann2306 said:
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Click to expand...
Click to collapse
I'm not familiar with that app, sorry. I just know that's not the process mentioned in his thread, so until you do that, I can't really confirm what the problem could be.
ok, im back on stock. flashing following files helped. i will test twrp again later and report. thanks for your replies.
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Hermann2306 said:
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Click to expand...
Click to collapse
From stock, I just flashed the Kirisakura zip in TWRP and my device booted up fine.
EDIT: While the above is true, TWRP no longer functions after installing the kernel, and the device won't reboot again after installing it. So something is definitely wrong somewhere.
For now, I can only suggest not using it with a custom kernel until we figure this out.
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Hermann2306 said:
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Click to expand...
Click to collapse
Yes, there seems to be an issue in the kernel that's preventing TWRP from working. I'm not sure what the issue is, unfortunately.
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
c19932 said:
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
Click to expand...
Click to collapse
Yes.
Quick PSA for anyone using this TWRP that also wants to use a custom kernel:
As of Kirisakura 2.0.6, the custom kernel and TWRP can now co-exist. This is due to the changes that allowed a monolithic kernel build. Presently, CleanSlate has not adopted those changes, but if/when it does, I will remove that disclaimer from the OP.
Thanks to @arter97, @Freak07, & @tbalden for supporting this device!
Is the twrp compatible with android 13?
NisseGurra said:
Is the twrp compatible with android 13?
Click to expand...
Click to collapse
There's a really easy way to find out...
Captain_Throwback said:
There's a really easy way to find out...
Click to expand...
Click to collapse
I getting decrypt errors that why the q
NisseGurra said:
I getting decrypt errors that why the q
Click to expand...
Click to collapse
Then you should post some logs
Will do