Hi all,
After hours of search and work I'm happy to share with you my guide on how to convert stock ROM for XA Dual Sim from EXT4 to F2FS File System.
## Introduction
What is the difference between EXT4 and F2FS filesystem and why changing it ?
https://forum.xda-developers.com/showthread.php?t=2697069
On Xa the Antutu Bechmark score jump from near 48000 to a little more than 50000 points. It's not incredible but you really feel the difference.
The way to make it possible was to implement F2FS support to the kernel (I don't know why Sony doesn't use it), after it was to modify some files in the boot and the recovery.
It's experimental because in the kernel sources the feature is written like this.
This guide is not noob friendly, I recommend to follow my root guide first: https://forum.xda-developers.com/xperia-xa/how-to/f31xx-how-to-root-xperia-xa-noob-t3430170
## Prerequisites
- Have a brain to follow carefuly the guide.
- Have a XA Dual Sim (F3112 or F3116)
- Have an unlocked bootloader
- Have an unencrypted Data partition if you don't want to loose data
- Be on 33.2.B.4.70, if you don't have the firmware for your customization you can flash an other customization without problems.
- Have TWRP 3.1.0 flashed on the device from here: https://forum.xda-developers.com/xp...3112-f3116-twrp-recovery-xa-dual-sim-t3606232
## Method without loosing data
1) Make a backup of Data partition with TWRP 3.1.0 on Micro SD (skip this if you want a clean install). If your Data partition is encrypted make a backup with an app like Titanium Backup and
restore it after step 9.
2) Copy the content of your internal SD to a safe place (Mico SD, USB stick, Computer)
3) Download the "F2FS Edition" of the boot: https://mega.nz/#!V1ARXJAZ!21WG1GLvxM4gH9I7tExG7ZrCWwqkSXaTLMln2IcFdBs
4) Download the "F2FS Edition" of TWRP: https://mega.nz/#!Q9QAkYpa!Cz4U_fbDIzH8Wex1i_V-hhJUqQoqHBf3OtGfUAOuq9U
5) Boot in fastboot mode and flash boot and recovery (don't hotboot)
6) Boot to TWRP, go to: Wipe -> tap "Advanced Wipe" -> Check box "Data" -> tap "Repair or change File System" -> tap "Change File System" -> Select "F2FS" -> Swipe to Change.
7) Power off the device, boot in fastboot mode and enter command "fastboot format cache" without quotes.
8) Boot to TWRP, go to: Wipe -> tap "Advanced Wipe" -> Check box "Cache" -> tap "Repair or change File System" -> tap "Change File System" -> Select "F2FS" -> Swipe to Change.
9) Go back and restore your Data backup. (Skip this for a clean install)
10) Reboot to Android and enjoy !! (It can takes 10 minutes to boot on clean install)
11) Root the device with Magisk or SuperSu.
## Conclusion
If you have a bootloop on the Sony logo or if Android ask for a password to boot, you missed something and you must follow the guide again.
By following this guide your Data partition will not be encrypted.
If you want to revert to EXT4 file system you have to follow the guide again but flash "normal" boot and TWRP, at steps 6 and 8 select "EXT4" instead of "F2FS"
Please don't ask for other models, the answer is NO.
Have a nice day
It's alright to step 9 and all function normal. But after I flash SuperSU 2.76 or 2.79 or 2.82, the device have a bootloop on the sony logo. I tried three times all stuck at step 10.
By the way, thanks for your kernel and recovery (XA and XA Ultra) all works fine.
Arakawa. said:
It's alright to step 9 and all function normal. But after I flash SuperSU 2.76 or 2.79 or 2.82, the device have a bootloop on the sony logo. I tried three times all stuck at step 10.
By the way, thanks for your kernel and recovery (XA and XA Ultra) all works fine.
Click to expand...
Click to collapse
Hi, use Magisk it should works.
My device is rooted, do i need to do step 11?
okhayko said:
My device is rooted, do i need to do step 11?
Click to expand...
Click to collapse
Yes you need to root it again because you have to flash a new boot.img. You must have 33.2.B.4.70 firmware on your device.
rrvuhpg said:
Yes you need to root it again because you have to flash a new boot.img. You must have 33.2.B.4.70 firmware on your device.
Click to expand...
Click to collapse
33.2.B.4.70 firmware is MM, right? I just got 33.2.B.2.93, is it ok?
How about my data? it will be lost?
okhayko said:
33.2.B.4.70 firmware is MM, right? I just got 33.2.B.2.93, is it ok?
How about my data? it will be lost?
Click to expand...
Click to collapse
Files are for 4.70 firmware but you can try with 2.93, if you are lucky it will be OK. Yes it's MM firmware. In the guide you have to make backup of your data and internal memory so yes if you don't do it data will be lost
rrvuhpg said:
Files are for 4.70 firmware but you can try with 2.93, if you are lucky it will be OK. Yes it's MM firmware. In the guide you have to make backup of your data and internal memory so yes if you don't do it data will be lost
Click to expand...
Click to collapse
So that is for MM? what about Nougat? i don't want to back to MM
okhayko said:
So that is for MM? what about Nougat? i don't want to back to MM
Click to expand...
Click to collapse
As you can see I have 3 thanks so only 3 users used F2FS on dual sim XA. Nobody is interested to have a faster device and no requests to have it on single sim or on XA Ultra. Sorry but I will not update it for Nougat firmware(s).
rrvuhpg said:
As you can see I have 3 thanks so only 3 users used F2FS on dual sim XA. Nobody is interested to have a faster device and no requests to have it on single sim or on XA Ultra. Sorry but I will not update it for Nougat firmware(s).
Click to expand...
Click to collapse
Nah, so sad thank you for your hard work!
rrvuhpg said:
As you can see I have 3 thanks so only 3 users used F2FS on dual sim XA. Nobody is interested to have a faster device and no requests to have it on single sim or on XA Ultra. Sorry but I will not update it for Nougat firmware(s).
Click to expand...
Click to collapse
We need Volte and only that feature we really need in nougat that is not giving us in india by sony in F3116
i thanked to your post regardless of that i am not using your good work for working fast our devices
But i dont really need it cause it can improve performance but it can not become snapdragon 835 by that's tweaks
I really appreciates your work and other developers cause they do not work for money
But sometimes you shoud focus on what normal feature is demanded by users
I know that it will be very easy to make VOLTE working for F3116
If it was possible in z2 and z3 than it is xoeria xa
If you will create that volte patch many users will thank you
In every 2 to 3 days i chek xda xperia xa forum
Only for that feature
I will Unlock my phone only for that feature
And many indian users will thank you for your work
altmash mirza said:
We need Volte and only that feature we really need in nougat that is not giving us in india by sony in F3116
i thanked to your post regardless of that i am not using your good work for working fast our devices
But i dont really need it cause it can improve performance but it can not become snapdragon 835 by that's tweaks
I really appreciates your work and other developers cause they do not work for money
But sometimes you shoud focus on what normal feature is demanded by users
I know that it will be very easy to make VOLTE working for F3116
If it was possible in z2 and z3 than it is xoeria xa
If you will create that volte patch many users will thank you
In every 2 to 3 days i chek xda xperia xa forum
Only for that feature
I will Unlock my phone only for that feature
And many indian users will thank you for your work
Click to expand...
Click to collapse
Thank you for encouraging me I know that Indian users need VOLTE and I understand why but the biggest problem for me to make it working is that we don't have it in France so how can I understand where is the problem and try to fix it?
I'm really surprised that almost nobody want a lag free device, nothing more. Now I know that's useless to try to implement new CPU governors for the same thing and I will use my time for other things but for VOLTE I don't know what to do. I will take a look at how z2 and z3 was patched but I can't be sure that I will be able to fix it for XA.
As you probably know I'm working on Lineage14 and I hope that VOLTE will work on it "out of the box".
rrvuhpg said:
Thank you for encouraging me I know that Indian users need VOLTE and I understand why but the biggest problem for me to make it working is that we don't have it in France so how can I understand where is the problem and try to fix it?
I'm really surprised that almost nobody want a lag free device, nothing more. Now I know that's useless to try to implement new CPU governors for the same thing and I will use my time for other things but for VOLTE I don't know what to do. I will take a look at how z2 and z3 was patched but I can't be sure that I will be able to fix it for XA.
As you probably know I'm working on Lineage14 and I hope that VOLTE will work on it "out of the box".
Click to expand...
Click to collapse
Make it for dual sim please, we want a lag free device
rrvuhpg said:
Thank you for encouraging me I know that Indian users need VOLTE and I understand why but the biggest problem for me to make it working is that we don't have it in France so how can I understand where is the problem and try to fix it?
I'm really surprised that almost nobody want a lag free device, nothing more. Now I know that's useless to try to implement new CPU governors for the same thing and I will use my time for other things but for VOLTE I don't know what to do. I will take a look at how z2 and z3 was patched but I can't be sure that I will be able to fix it for XA.
As you probably know I'm working on Lineage14 and I hope that VOLTE will work on it "out of the box".
Click to expand...
Click to collapse
Thnks bro your intention is enough to us
And we will support your work always whether we get VOLTE or not it does not matter
Thnks again i think you will do something innovative in this complex mediatek device (the chipset that has little scope of development)
That's why your efforts are really thankful for us
Hi again! Is There any tutorials about show to modify the kernel the way you did? I want to start to develop myself but I don't know where to start.
Thanks!
vraciu' said:
Hi again! Is There any tutorials about show to modify the kernel the way you did? I want to start to develop myself but I don't know where to start.
Thanks!
Click to expand...
Click to collapse
Hi, I don't use any tutorials to modify the kernel. Look at similar defconfigs, kernel commits on Github and available settings in the menuconfig.
Related
This method successfully worked for me & @lysm bre (Thanks to him for the guiding)!
Your phone will be unencrypted after folllowing this guide and successfully rooted too if I didn't mention that
To flash ROMs in future you have to disable encryption so this method will make you ready for that too
Here is my video in which I explained in detailed and I've done all the steps from beginning! So you can follow this guide too here- https://youtu.be/mUq1xdJ-7-E
To Boot into Bootloader mode use command adb reboot bootloader or hold power and volume down button once its switched off!
I'll modify & beutify the guide in future so stay tuned for that!
1] Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
6] Boot into TWRP & select allow modifications !
7] Goto Wipe & select format data !
8] After that is done, reboot into system without rooting& skip through setup again!
9] Now if you check the encryption status of your phone (Settings -> Security - Encrypt phone), it won't be encrypted anymore as it'll give you the option of encrypting it, which means it currently isn't encrypted.
10] Now transfer the SuperSU zip file in the internal storage of the phone, reboot into TWRP, and flash SuperSU!
BOOM! You have successfully rooted with encryption disabled.! Congratulations!
Just a reminder that for video explanation watch this- https://youtu.be/mUq1xdJ-7-E
Downloads-
Modified boot.img- http://bit.ly/1MVtrNr Thanks to @Chainfire ONLY FOR build no mdb08i as of now! Do not flash on any other build!
TWRP recovery image- https://dl.twrp.me/bullhead Thanks to @Dees_Troy
SuperSU zip- https://download.chainfire.eu/743/SuperSU Thanks to @Chainfire
Modified boot images for all nexus devices- http://bit.ly/modifiedbootimages Thanks to @Chainfire
Thanks for posting! Unfortunately the link for the modified boot image is broken.
johnpwu said:
Thanks for posting! Unfortunately the link for the modified boot image is broken.
Click to expand...
Click to collapse
Updated! Here- http://bit.ly/1MVtrNr
Else you can always download the boot.img file from here- http://bit.ly/modifiedbootimages [Select "bullhead" for Nexus 5X]
Thanks!
Thank you OP and @lysm bre, great job. Might I suggest that you include the build number in your instructions as you have clearly stated in your video. I watched it and it was very helpful to learn that your boot image was from a specific build number. Thanks again
Might be worth mentioning it's build specific (only for mdb08i currently) and will save someone the time I wasted figuring that out [emoji14]
Sent from my Nexus 5X using Tapatalk
Hayth said:
Might be worth mentioning it's build specific (only for mdb08i currently) and will save someone the time I wasted figuring that out [emoji14]
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
just flash that build number then flash the modified version, thats what i did and its working fine ( i came from build number MDA89E)
hawkins95 said:
just flash that build number then flash the modified version, thats what i did and its working fine ( i came from build number MDA89E)
Click to expand...
Click to collapse
I was thinking of doing that but wasn't sure if the builds are region specific and could affect something I wasn't aware of?
Sent from my Nexus 5X using Tapatalk
Hayth said:
I was thinking of doing that but wasn't sure if the builds are region specific and could affect something I wasn't aware of?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Im in the uk and it is working great for me, im rooted and my data is working, just make sure to flash normal version from google first because when i did it with the modified version is came up with some weird bootloop image. and im pretty sure MDBO8I is an update everyone is getting saw a few articals saying it was.
Worked for me!! Thanks a million!:good::good:
hawkins95 said:
Im in the uk and it is working great for me, im rooted and my data is working, just make sure to flash normal version from google first because when i did it with the modified version is came up with some weird bootloop image. and im pretty sure MDBO8I is an update everyone is getting saw a few articals saying it was.
Click to expand...
Click to collapse
Cool, that's good to know I saw those articles too but as they made reference to enabling band 12 in the US I wasn't sure. I've wiped and restored my phone that many times today I'm going to give it a few days to see if the OTA comes through [emoji14]
Sent from my Nexus 5X using Tapatalk
Thanks. Was too lazy to properly make a post about it. Good work on the video!
Thanks you! How's the device after you have disabled the encryption? I guess faster.....
Can someone verify two things?
Finger print reader is functional
Android Pay is working, by actually making a purchase successfully
EDit: figured that one out...
johnpwu said:
So this is not a complaint about the OP's awesome work, and sorry if I should start a new thread, but I just got a message I've never seen before attempting to unlock the bootloader...
Click to expand...
Click to collapse
Before attempting to unlock the bootloader, go into developer options and tick the option "OEM Unlocking"
xtentual said:
Before attempting to unlock the bootloader, go into developer options and tick the option "OEM Unlocking"
Click to expand...
Click to collapse
Thanks, just figured it out about 15 seconds before you posted.
*deleted* replied to wrong thread
Trinity86 said:
Thanks you! How's the device after you have disabled the encryption? I guess faster.....
Click to expand...
Click to collapse
This. Can someone please comment on performance after disabling encryption?
xtentual said:
Can someone verify two things?
Finger print reader is functional
Android Pay is working, by actually making a purchase successfully
Click to expand...
Click to collapse
I can confirm the Finger print reader is working
Requirements:
Sony Xperia Z2 Tablet (SGP521) with root and recovery.
Instructions:
Download: SGP521_23.4.A.1.264_1282-2019_R3C_flashable-prerooted.zip ( 1.39 GB ):
cloud.mail.ru
mega
Copy zip-file on SDCARD.
Go to recovery.
Factory Reset (recommended).
Install zip-file.
Reboot the system.
Thanks @Bird40 once again anything new in this update or just bugs and security fixes
azeez77 said:
Thanks @Bird40 once again anything new in this update or just bugs and security fixes
Click to expand...
Click to collapse
Just a Full Stagefright fix...
http://www.xperiablog.net/2015/11/27/new-update-23-4-a-1-264-hits-the-xperia-z2-and-z2-tablet-with-full-stagefright-fix/
Thanks @Bird40 for on-time new updates!
Thank you good Sir
Excuse my ignorance as this is my very first Android device (working one that is)
Read quite a bit of articles & tuts Still afraid I'll mess up, so I have a few questions regarding above files & compatibility with my devices in it's current state
Currently at stock 23.4.A.1.264 (Netherlands Customized) updated via OTA from .200
"Bootloader unlock allowed = No", not rooted. Originally was on Croatia (VIP carrier, KitKat)
Am I good to go with such setup?
OR before doing steps above do I need to enable:
Debugging
Disabled apps (some google ones)
Format my SDXC card since I have a lots of things there, If so to which format since it's SDXC card
Backup my device to PC with Sony Software or any other method/tool
Reason I'm this scared is guy who owned it before me flashed it to another countrys ROM. I do not know which tool/method he used and in which way now does this effect doing step 4 If something goes wrong I have no idea how to take further actions.
Disclaimer
**** All flashing is done at your own risk! ****
**** While this recovery should not break your device, don't come back here blaming anyone if it does! ****
This is a TWRP 3.2.3 build based on Android 7.1.2 source kernel for the Galaxy Tab Active 2 (codename: gtactive2lte) - Exynos. The "tar" file should be installed using Odin (tested on Odin 3.12.3).
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options, if its not there, you may have to wait for a few days to access that option, some users claim that its within 10 days before this option appears).
2. KNOX will be tripped once you flashed custom binaries to your phone.
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.(DO NOT GET FOOLED.)
Installation process:
1. Flash Stock ROM.
2. Flash recovery using Odin (AP = recovery.tar).
3. Load recovery immediately after flashing.
4. Format data (Will erase /data partition).
5. Reboot to recovery.
6. ADB push SuperSU to internal storage / insert SD-Card with SuperSU.zip.
7. Flash SuperSU using TWRP install option.
8. Reboot to system (May bootloop several times. Wait untill system loads).
Bugs:
1. ADB sometimes doesn't work in MTP mode. Need to manually change to PTP in order to get adb usage.
2. Bad label in ADB shell + bad characters appearing while writing through AD. Works well out of recovery and on recovery's terminal.
Sources:
Device tree - Device tree
Kernel - Kernel
TWRP sources - platform_manifest_twrp_omni
SuperSU - SuperSU-2.82-SR5
Recovery download:
Recovery
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 08/19/2018 (DD/MM/YYYY)
Contributors:
Many thanks to TWRP's developers for the support on building this recovery.
Special thanks to CaptainThrowback, Bigbiff and Dees_Troy on TWRP-freenode and Ashyx on xda-developers.
Please post any bugs you encounter. I will try to fix any issues that come up.
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
slomo2 said:
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
Click to expand...
Click to collapse
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Shedaim said:
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Click to expand...
Click to collapse
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
slomo2 said:
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
Click to expand...
Click to collapse
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Shedaim said:
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Click to expand...
Click to collapse
This will be great, let me know if I can help, perhaps document.
slomo2 said:
This will be great, let me know if I can help, perhaps document.
Click to expand...
Click to collapse
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Shedaim said:
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Click to expand...
Click to collapse
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
Click to expand...
Click to collapse
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
7.1.1 is what The T397U should have already been on before you started. Mine is and I have not installed this recovery as of yet. Just wanted to let you know it's where it should be.
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
Click to expand...
Click to collapse
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Shedaim said:
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Click to expand...
Click to collapse
Sorry for delay. I've done the following tests all with the expected results. The only thing I noticed compared to previous installations of TWRP that I've performed ( some years ago ) is that the load time of recovery seems long at 1:15. Also a message about "RECOVERY NOT SEANDROID ENFORCING" which I suspect is normal. Tablet has been working without incident. Thanks again.
Blocking checks
- Correct screen/recovery size
- Working Touch, screen
- Backup to internal/microSD
- Restore from internal/microSD
- reboot to system
-ADB ( yes, if this means being able to access from ADB while in recovery )
Medium checks
- Screen goes off (and on )
- F2FS/EXT4 Support, exFAT/NTFS where supported
- all important partitions listed in mount/backup lists
===> define important ? - depends on the device, i guess
= Assume we can still boot a recovery (aboot/lk is still there for fastboot), can restore everything left ?
- backup/restore to/from external (USB-OTG) storage
- Correct date
Minor checks
- MTP export
- reboot to bootloader
- reboot to recovery
- poweroff
- battery level
- USB mass storage export
- set brightness
- vibrate
Security Policy Updates should not be applied to this system ?
Since this is stock Samsung OS that is rooted I'm guessing this system is still SELinux "enforcing" so does this mean that I can/should say yes to Security Enhancements automatic updates from Samsung ? Any explanation or link on this matter appreciated.
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
maddada said:
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
Click to expand...
Click to collapse
Hey, sorry for the very late answer.
I'm currently not working on Android and I've never tried on OREO, so my politically correct answer would be: "Right now there is no plan to work the same magic on OREO, but whoever wants, can try to use the device tree I created with a new official OREO kernel (didn't know they have one already)".
Anyway, keep checking the forum from time to time, I may have found the time to work on it
Links to the device tree and other tools used are in the main page of this thread.
Thank you,
Shedaim
I Pay 100$ for making my Galaxy Tab Active 2 booting when its charging
Hey guys,
i hope somebody can help me.
Im trying since 2 Weeks to make my Galaxy Tab Active 2 booting when its charging.
I try all the ways i found (fastboot, LPM change and Autoboot App) and nothing was successful.
So i hope to find with this way somebody who would help me to get the feature.
I need it because i installed the Active 2 on my Harley Davidson as my navigation.
And the problem is that i make a Novalauncher thats looking like the original Harley Davidson one and starts without a code.
So when i put the Tablet in the Mask i dont get a method to press to power button and when i make a method (hole trough the mask or something) then everybody can start up my tablet and use it.
So if somebody can help me with that i will pay them 100$ for helping!
you can contact me at [email protected].
thanks alot
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
sCOTTN916 said:
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
Click to expand...
Click to collapse
I used the methods and recovery here for my tablet which is a T397U...works flawlessly. The same should work for the wifi T390 you have aswell.
Flash process
I am new to the rooting process. This will be my first time. What is the actual flash process? How do I flash the rom on my tablet?
All the links are dead can anyone please post this recovery
i can Flash this twrp-3.2.3-0-gtactive2lte-7.1.2.tar, Odin says pass, but there is no TWRP. it boots into System. when i stop and boot to recovery, there is stll custom recovery from T395XXU5CSH2.
Any hints?
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty could be void if you tamper with any part of your device / software.
* Same statement for XDA.
Click to expand...
Click to collapse
This is my first time posting here on xda if i miss some rules please let me know
Installing drivers & Preparing PC (Thanks to balazs312)
- Download this file and extract it
- Open and install "adb-setup-1.4.3.exe"
- When it is done, go to "Drivers" folder and start "miflash_unlock.exe"
- Click on the gear icon top right corner and click on "Check" next to "Click the button to install the drive"
- Do as the installer says
- Hopefully the drivers has been installed so we're done with it
NOW Unlock Bootloader (It will wipe ur data! so backup before doing it)
-Open the Settings app on ur phone
-Go to System.
-Tap on About phone.
-Scroll down and tap on Build number 7 times until it says you’re now a developer.
-Go back one page you should see “Developer options.” click it
-then you should see an “OEM unlocking” option. Enable it.
-Scroll down a bit until you see “USB debugging.” Enable it.
-Disable automatic updates
-now turn off your phone
-now turn on ur phone in fastboot mode by pressing volume down + power key in will boot in fastboot mode
- Download zip and extract it on your PC
- Open it and type "cmd" (without the quotations) in the file manager header where you see (This computer>somethingsomething>Mi A2 fastboot), don't be afraid just type it in, and hit enter and you'll enter into command prompt
- Now we are ready for action
- Type these commands one by one:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
done now pop up will show on your phone select unlock bootloader with volume key n power
it will reboot set up ur phone again
2. Installing Magisk
To Install Magisk you need patched boot image you can have one from here
{always use img that matches exactly to ur build no}
OR
{OPTIONAL}
you can make own boot img
download fastboot rom and get boot.img from there
or download untouched img from here
so now ur phone is unlocked download magisk manager and install it from HERE
copy that untouched boot image from ur pc to phone
open magisk manager >install >patch boot image select ur boot img u just transferred
magisk manager will create a patch image in same directory or download folder
Fastboot patch img
Now if u have created ur own patch img transfer it to pc from ur phone n put it in adb folder
or if u have simply downloaded the patch image copy it to adb folder
Open a fastboot command prompt on your pc.
Type "fastboot boot {patched boot image name}.img"
Your phone will reboot
Install the magisk apk.
Now open Magisk Manager app
Click Install, direct install. Wait for the process
And click reboot.
HOW TO APPLY OTA UPDATES
IMPORTANT: it will only work if you do not alter system yourself like build.prop (try altering system just using magisk modules)
{if u created ur own patch img}
When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images"
{if u have not created ur own img put untouched downloaded build.img in magisk folder then}
When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images"
Close Magisk Manager and go to "Settings" > "About Phone" > "System update" and install the OTA update. Dont Reboot
Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot" and after that you can tap on "Reboot".
alternatively
Magisk could alert you that it cannot restore the original boot.img when you trying to uninstall
To fix this, you can flash directly the untouched boot.img through fastboot
Code:
fastboot getvar current-slot
then you will get ur active slot it might be a or b
if its a then use
Code:
fastboot flash boot_a boot.img
If its b then use
Code:
fastboot flash boot_b boot.img
Now We Have Mi A2 Telegram Group get in if u want to help or need some help
OffTopic Group HERE
Development Group HERE
-reserved-
i have just created this account to reply here it
i used to read here alot but i dont reply here
as i found this thread has no reply but the best method i was searching for on internet for my mi a2
i just got my mi a2 was highly confused how to root because of a/b partition and no official twrp
i found this method among the best no confusion straight on point
and seriously a noob guide
thank you for the this !
geekh said:
i have just created this account to reply here it
i used to read here alot but i dont reply here
as i found this thread has no reply but the best method i was searching for on internet for my mi a2
i just got my mi a2 was highly confused how to root because of a/b partition and no official twrp
i found this method among the best no confusion straight on point
and seriously a noob guide
thank you for the this !
Click to expand...
Click to collapse
I personally think that there are at times some confusion. but it remains a more reliable method. (in terms of ease this method (https://forum.xda-developers.com/mi-a2/how-to/guide-2-minutes-magisk-installation-t3856980/amp/) is by far the fatest, try it after your next ota)
Atlas/ML said:
I personally think that there are at times some confusion. but it remains a reliable method. in terms of ease this method (https://forum.xda-developers.com/mi-a2/how-to/guide-2-minutes-magisk-installation-t3856980/amp/) is by far the easiest, try it after your next ota
Click to expand...
Click to collapse
I have just checked your linked thread first of all its wrong to promote your own thread like this
u are fishing people to come to your thread thats completely wrong and unprofessional you are on xda maintain some professionalism !
if someone wants to use your thread he/she will use it by themselves ,its visible to all !
and about your method i didnt wanted to use ur method i have looked into it you are using temp twrp method using unoffical twrp which i dont want to use thats personal preference i will wait for official twrp before flashing !
this method is best for me(noob here might be not as good as you but i know basic stuff) i can easily flash twrp permanenlty as soon as it is released without any further steps
Not everyone wants to use that temp twrp method
It is not fair to @Adinid who has taken so much time writing this great noob friendly thread
coming to his thread and telling people that ur thread is best or easiest is isnt good my friend !
in OTA part，"put untouched downloaded build.img in magisk folder"，This is invalid，I test it on V9.6.13，It always prompts that the backup image was not found.
geekh said:
I have just checked your linked thread first of all its wrong to promote your own thread like this
u are fishing people to come to your thread thats completely wrong and unprofessional you are on xda maintain some professionalism !
if someone wants to use your thread he/she will use it by themselves ,its visible to all !
and about your method i didnt wanted to use ur method i have looked into it you are using temp twrp method using unoffical twrp which i dont want to use thats personal preference i will wait for official twrp before flashing !
this method is best for me(noob here might be not as good as you but i know basic stuff) i can easily flash twrp permanenlty as soon as it is released without any further steps
Not everyone wants to use that temp twrp method
It is not fair to @Adinid who has taken so much time writing this great noob friendly thread
coming to his thread and telling people that ur thread is best or easiest is isnt good my friend !
Click to expand...
Click to collapse
I personally think that official twrp will never support boot, because At first glance the beta does'nt support it. So my method will be the simplest for a while.
As for the sharing of MY guide, it is a simpler and faster method. And it will allow more people to root their phone without following 50,000 steps and without fear of brick their phone ...
If @@Adinidhas a problem with sharing my guide, he can tell me privately on Telgram, and I'll delete it.
Have nice day,
Matteo
I don't really care which method people use to do one thing or another. It's up to them, whatever they feel most comfortable doing.
But, I do care when someone misuses the 'code' functionality box. It's not used for 'further description'... it's used for CODE... ie, actual code:
like: fastboot boot bootloader
like: adb shell setprop persist (etc)
It's meant to be something someone can copy and paste it to the command line, to avoid typing errors, not for 'further descriptions...'
Atlas/ML said:
I personally think that official twrp will never support boot, because At first glance the beta does'nt support it. So my method will be the simplest for a while.
As for the sharing of MY guide, it is a simpler and faster method. And it will allow more people to root their phone without following 50,000 steps and without fear of brick their phone ...
If @@Adinidhas a problem with sharing my guide, he can tell me privately on Telgram, and I'll delete it.
Have nice day,
Matteo
Click to expand...
Click to collapse
Your Reply shows your arrogance and unprofessionalism nothing else
you think the method you have is best u dont want to even think that someone can have other method n others might prefer it
you are just boasting about your method as best n what not lol !
instead of accepting that you did wrong by sharing your thread here , you are trying pull down op thread by shamelessly telling people that op method might brick phone n needs 50k steps(that is completely NOT true ) when ur method CAN also brick it !
you both have given options to users its their pick which one they want to use !
I dont want to waste my time here to educate you about how to behave in public forum !
Just want to say calm down put ur arrogance on side,show some maturity and even please try to change ur attitude
you might be good but try to learn as it doesnt matter how good you are there is always someone who is better than you n others might prefer it more !
different people have diff use cases preferences always remember that
peace !
AsItLies said:
I don't really care which method people use to do one thing or another. It's up to them, whatever they feel most comfortable doing.
But, I do care when someone misuses the 'code' functionality box. It's not used for 'further description'... it's used for CODE... ie, actual code:
like: fastboot boot bootloader
like: adb shell setprop persist (etc)
It's meant to be something someone can copy and paste it to the command line, to avoid typing errors, not for 'further descriptions...'
Click to expand...
Click to collapse
Thank you for your feedback sir, i have just started posting here as i wrote it in my initial post
my apologies will try to format it properly
tianma163 said:
in OTA part，"put untouched downloaded build.img in magisk folder"，This is invalid，I test it on V9.6.13，It always prompts that the backup image was not found.
Click to expand...
Click to collapse
looking into it
till then i just added alternate method use that !
geekh said:
Your Reply shows your arrogance and unprofessionalism nothing else
you think the method you have is best u dont want to even think that someone can have other method n others might prefer it
you are just boasting about your method as best n what not lol !
instead of accepting that you did wrong by sharing your thread here , you are trying pull down op thread by shamelessly telling people that op method might brick phone n needs 50k steps(that is completely NOT true ) when ur method CAN also brick it !
you both have given options to users its their pick which one they want to use !
I dont want to waste my time here to educate you about how to behave in public forum !
Just want to say calm down put ur arrogance on side,show some maturity and even please try to change ur attitude
you might be good but try to learn as it doesnt matter how good you are there is always someone who is better than you n others might prefer it more !
different people have diff use cases preferences always remember that
peace !
Click to expand...
Click to collapse
That's why i add a warranty part lmao, and for brick not possible, because magisk support A/B, and Twrp is BOOT only. So after reboot it's gone.
I just say that my method is the simplest, not the better. As for the arrogance I only share my link for you to win time if needs after any ota, if you do not want to use it. You say that I lower his method, etc. I have already done one with these same methods, and I will soon hold a repo. You're totally wrong. No luck You judge me without knowing me and give me orders and I'm arrogant. OwO
As for the answers, personally I do not have anything to do with it, it makes go up this thread in the list, hoping that it has more visibility.
Matteo
If i enable camera2api does it count as altering system for ota?
Ajakazema said:
If i enable camera2api does it count as altering system for ota?
Click to expand...
Click to collapse
it depends on how you activated it. if you activate it using a magisk module it will be fine, if you activate it using an adb command it's a system modification. so it should alter the ota.
Ajakazema said:
If i enable camera2api does it count as altering system for ota?
Click to expand...
Click to collapse
if u do that by build.prop edit it will count for altering system
but if u use magisk module to do that it will not
let me know if u have any more confusion
happy to help !
I'm currently in august security patch, with an unlocked device + root (magisk) and i've altered the build.prop to enable cameraapi2. How can I update safely to the new october patch?
Thanks in advance
hugopg said:
I'm currently in august security patch, with an unlocked device + root (magisk) and i've altered the build.prop to enable cameraapi2. How can I update safely to the new october patch?
Thanks in advance
Click to expand...
Click to collapse
if u want everything clean u can flash fastboot rom
after uninstalling magisk through magisk manager
or just uninstall magisk then fastboot flash boot img
u can check it in my how to get ota part in my initial post (alternative method)
then apply ota
root again if u want
adinid
Adinid said:
if u want everything clean u can flash fastboot rom
after uninstalling magisk through magisk manager
or just uninstall magisk then fastboot flash boot img
u can check it in my how to get ota part in my initial post (alternative method)
then apply ota
root again if u want
adinid
Click to expand...
Click to collapse
Hey, thanks for your fast reply!
In your post you said that the OTA can be done if I didn't altered the system.prop, but I did! So I would need to restore boot.img (through magisk, to remove root) and also flash system.img (to restore the prop)? Is that it?
Thanks
Atlas/ML said:
it depends on how you activated it. if you activate it using a magisk module it will be fine, if you activate it using an adb command it's a system modification. so it should alter the ota.
Click to expand...
Click to collapse
This is COMPLETELY inaccurate information! YOU are setting a very bad precedent.
Magisk is a SYSTEMLESS root, which means what it does with system is HIDDEN (very hard to detect), but that does NOT mean it doesn't modify system!!
The ADB command to set the cam2api is a setprop persist command WHICH DOES NOT MODIFY SYSTEM! EVER!
PLEASE DO NOT SPREAD COMPLETELY INACCURATE INFORMATION!! YOU WILL BE MISLEADING POTENTIAL FUTURE OWNERS OF THIS DEVICE!!
AsItLies said:
This is COMPLETELY inaccurate information! YOU are setting a very bad precedent.
Magisk is a SYSTEMLESS root, which means what it does with system is HIDDEN (very hard to detect), but that does NOT mean it doesn't modify system!!
The ADB command to set the cam2api is a setprop persist command WHICH DOES NOT MODIFY SYSTEM! EVER!
PLEASE DO NOT SPREAD COMPLETELY INACCURATE INFORMATION!! YOU WILL BE MISLEADING POTENTIAL FUTURE OWNERS OF THIS DEVICE!!
Click to expand...
Click to collapse
So, first shut a up.
Next i never say that magisk doesn't modify system, i just say that if use magisk for enable it it's fine.
For the second information, my bad , i try but with the adb command ota failed so i'm not totally false.
Have a bad day,
Matteo
Ok my friends, it's true that family moto g6 (specifically g6 play) will receive android 10? if it's possitive... When will we have news about this?
Also ... does anyone know if there is any rom in development with android 10 for this model (lineage, RR, etc.)?
If anyone knows about this, I think several would appreciate this valuable information.
Answer 1, just wait for Moto to announce it, usually they announce when there gonna do a soak test of a new Android version so whenever Moto does that will be some sort of answer however soak test usually go on for a few months basically it's prolly gonna be almost another year before we hear anything I mean we just got official pie about 2 months ago now after they did soak test for months.
Answer 2, there is not even a custom rom like rr or anything for this device for Oreo or pie so doubtable. Best you can do is try out gsi A only builds, custom rom means it's made specifically for this device where as gsi is compatible with any phone that shipped with Android 8. There is a gsi thread you can out
Answer 3: Motorola has already confirmed that the Moto G6 Play will only get one major OS upgrade, and being that we got Pie now that's all it will get unless a DEV figures out how to make a custom rom for Android 10.
PimpMy5Ton said:
Answer 3: Motorola has already confirmed that the Moto G6 Play will only get one major OS upgrade, and being that we got Pie now that's all it will get unless a DEV figures out how to make a custom rom for Android 10.
Click to expand...
Click to collapse
I have no WiFi right now or I'd already be trying to build for us. They finally fixed the sources for our phone. Phh has Android 10 GSIs out. They'll boot if you flash the Oreo vendor, oem, and boot images first but it's very alpha at the moment. You also need to flash phh's modified magisk from his first Android 10 release. LTE is broken (3G works), and it has some graphics glitches. Most everything else is working fine though. It's not a daily driver yet but it's getting there fast. It will break LTE on stock. To fix that just flash your firmware and let it setup until it reactivates, then you can restore a backup like normal.
Spaceminer said:
I have no WiFi right now or I'd already be trying to build for us. They finally fixed the sources for our phone. Phh has Android 10 GSIs out. They'll boot if you flash the Oreo vendor, oem, and boot images first but it's very alpha at the moment. You also need to flash phh's modified magisk from his first Android 10 release. LTE is broken (3G works), and it has some graphics glitches. Most everything else is working fine though. It's not a daily driver yet but it's getting there fast. It will break LTE on stock. To fix that just flash your firmware and let it setup until it reactivates, then you can restore a backup like normal.
Click to expand...
Click to collapse
That's cool, I was just adding to the answer as to the number of os upgrades that Moto phones get, as far as Phh's android 10 you should be fine as long as you include vendor partition with your stock backup.
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
@Spaceminer Could you link to the sources for the Moto G6 Play?? I have the XT1922-7 Boost Mobile variant.
PimpMy5Ton said:
That's cool, I was just adding to the answer as to the number of os upgrades that Moto phones get, as far as Phh's android 10 you should be fine as long as you include vendor partition with your stock backup.
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
@Spaceminer Could you link to the sources for the Moto G6 Play?? I have the XT1922-7 Boost Mobile variant.
Click to expand...
Click to collapse
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PCP29.118-41
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
ry755 said:
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
Click to expand...
Click to collapse
Glad to have it running with Pie and more stable, those are great news
ry755 said:
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
Click to expand...
Click to collapse
Can you guide us? I install the test img but cant boot on pie vendor
Grom9A said:
Can you guide us? I install the test img but cant boot on pie vendor
Click to expand...
Click to collapse
First flash the latest stock boot.img to remove any leftover traces of Magisk, which is now incompatible with phh's AOSP 10 builds.
After that you'll need to disable encryption and dm-verity, if you haven't already done that:
- Download the dm-verity + forced encryption disabler zip here
- Boot into TWRP, go to Wipe, and press Format Data. This will wipe everything from the internal storage! Make sure you have backups stored somewhere else.
- Reboot > Reboot Recovery
- Copy the disabler zip to your phone and flash it
Now the test image should be able to boot on Pie vendor.
(There might be other/better ways of doing this, but those are the steps that worked for me)
ry755 said:
First flash the latest stock boot.img to remove any leftover traces of Magisk, which is now incompatible with phh's AOSP 10 builds.
After that you'll need to disable encryption and dm-verity, if you haven't already done that:
- Download the dm-verity + forced encryption disabler zip here
- Boot into TWRP, go to Wipe, and press Format Data. This will wipe everything from the internal storage! Make sure you have backups stored somewhere else.
- Reboot > Reboot Recovery
- Copy the disabler zip to your phone and flash it
Now the test image should be able to boot on Pie vendor.
(There might be other/better ways of doing this, but those are the steps that worked for me)
Click to expand...
Click to collapse
Thanks, it works. We need to find a way to restore the sound. I try a few zips they send on the telegram group but nothing.
Grom9A said:
Thanks, it works. We need to find a way to restore the sound. I try a few zips they send on the telegram group but nothing.
Click to expand...
Click to collapse
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Spaceminer said:
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Click to expand...
Click to collapse
Did you flash the stock boot.img? That's all I had to do to make it work, I didn't have to format data since I already have it decrypted.
Spaceminer said:
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Click to expand...
Click to collapse
I want to try but can't root this rom
Grom9A said:
I want to try but can't root this rom
Click to expand...
Click to collapse
Under phh's v200 build there's a special magisk he made for his Android 10 GSI.
---------- Post added at 08:11 PM ---------- Previous post was at 08:07 PM ----------
ry755 said:
Did you flash the stock boot.img? That's all I had to do to make it work, I didn't have to format data since I already have it decrypted.
Click to expand...
Click to collapse
Maybe I flashed the wrong boot.img... I might've mixed up Oreo and Pie boot images. I have both firmwares sitting right next to each other.
Spaceminer said:
Under phh's v200 build there's a special magisk he made for his Android 10 GSI.
Click to expand...
Click to collapse
I've tried that along with a few other people in the Moto G6 Telegram group, flashing it just causes bootloops.
ry755 said:
I've tried that along with a few other people in the Moto G6 Telegram group, flashing it just causes bootloops.
Click to expand...
Click to collapse
That explains my problem. I definitely flashed his magisk. Have you guys tried magisk v20 yet?
Spaceminer said:
That explains my problem. I definitely flashed his magisk. Have you guys tried magisk v20 yet?
Click to expand...
Click to collapse
Yep, any kind of Magisk makes it bootloop. Someone reported it to phh and his response was "well don't use magisk then" lol
ry755 said:
Yep, any kind of Magisk makes it bootloop. Someone reported it to phh and his response was "well don't use magisk then" lol
Click to expand...
Click to collapse
I'll check it out and see what I can do. That's not surprising though. It's extremely alpha, so he's probably just prioritizing stock functionality over everything else right now.
I can't get it rooted, but v202 just went up, so I'm going to try my luck with it.