Database Users

[HOW-TO][DEV EDITION ONLY]Root on 4.4 KitKat

https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!

What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app

Jexx11 said:
What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it

alex94kumar said:
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it
Click to expand...
Click to collapse
That's odd, I used the TWRP version in Hashcodes thread, flashed with the Motorola Fastboot. When I went to restart from TWRP it asked me if I wanted to root and I let it. Now I'm rooted.
Sent from my XT1060 using Tapatalk

Stranger things have happened, I guess. Regardless of which method you use, you'll end up with root either way

This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.

chaoslimits said:
This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.
Click to expand...
Click to collapse
same here but i have 85% battery
so i guess we will have to re-flash and push the supersu

The only advice I can give to either of you is to try reflashing TWRP again

Actually i did it again and it worked, guess we can't just skip steps.
Sent from my Nexus 7 using Tapatalk 4

Well im glad it worked out for you in the end

It worked after I charged the phone.
Thanks
Sent from my XT1060 using Tapatalk 2

How do I return my phone to default in order to install OTA
I have already flashed the stock recovery but my phone is still rooted. Do I need to unroot? I tried installing the OTA and it said it failed.

This method should work on any version with with an unlocked bootloader such as Sprint and T-Mobile - not just the dev editions.

alex94kumar said:
https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
Click to expand...
Click to collapse
Anyone knows how to do UNROOT if I used this method to get root?

I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.

1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.

s0nic69 said:
1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.
Click to expand...
Click to collapse
If we're already on 4.4, how do we know if we have the first OTA?
Thanks

chillmeow said:
I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.
Click to expand...
Click to collapse
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
---------- Post added at 03:45 PM ---------- Previous post was at 03:28 PM ----------
doctor_evil said:
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
Click to expand...
Click to collapse
OK I feel like an idiot. I just noticed that in the fastboot screen it shows that it's locked. I thought developer phones were unlocked by default?
ok after unlocking it I was able to install twrp recovery with no problems

Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?

pphi said:
Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?
Click to expand...
Click to collapse
Are you selecting recovery with the power button or the volume up button? Volume up selects. If you use the power button, the phone just boots normally.

[Q] SuperSu not working (not a Knox issue)

Dear all, I recently tried rooting my device (i5905) and run into some trouble. Here is what I did:
1) I followed this guide a guide called how-to-root-galaxy-s4-using-twrp-method such that I now have a working TWRP installed.
2) When I rebooted I noticed the message "SuperSu has stopped". I found out that I was using an old version of SuperSu (0.99) and updated the version through the play store. After that I was able to open the App but it said that it wasn't set up correctly - I don't remember the exact message.
3) I closed SuperSu, downloaded the newest version from the web to my device and installed the zip file with TWRP. Unfortunately, this brought me back to the state where every time I want to start the App I get the error "Unfortunately, SuperSu has stopped".
4) Some people claimed that it could be a Knox issue, even though I never got any security warning, I decided to download a "Knox" remover script which I ran through TWRP. This removed Knox (it is no longer listed under Apps) but it does not stop the error message from SuperSu poping up.
5) I'm unable to update SuperSu because I'm already on the newest version and I can't remove it either.
Any ideas how I should progress?
Thank you very much!

Try touch philz method

RubbaBand said:
Try touch philz method
Click to expand...
Click to collapse
Could you give a little bit more context on why I should try this and what it would fix? I'm new to this so I don't have a lot of knowledge.
Also couldn't that give me some problem because I already installed TWRP...

S4 have alot of updates NB3, NB4, NC1, NC2, elc...
Some of the updates lets the method you want to use useless
The touch philz custom recovery lets you root your device from recovery
You chould try it out

RubbaBand said:
S4 have alot of updates NB3, NB4, NC1, NC2, elc...
Some of the updates lets the method you want to use useless
The touch philz custom recovery lets you root your device from recovery
You chould try it out
Click to expand...
Click to collapse
Okay so I would assume I just follow these instructions:
http://forum.xda-developers.com/showthread.php?p=39433857#post39433857
Then I ignore the fact that I already installed TWRP and just install it? And once I installed it, there will be an option to root without using SuperSu?
Thanks.

After going to recovery go to philz options > reroot
The system will be rooted
If you didnt find SuperSu after boot
Download it from google play

RubbaBand said:
After going to recovery go to philz options > reroot
The system will be rooted
If you didnt find SuperSu after boot
Download it from google play
Click to expand...
Click to collapse
Sorry but I have trouble following the instructions. I downloaded Odin 309 and was able to put Philz Recovery on my phone. I restarted my phone and it seems like I'm unable to enter the recovery mode. I hold down all three keys (VolUp) and the blue font in the corner appears but after a few second the phone just shuts down. I'm still able to boot normal, just not into recovery mode. I thought it might be because of my low battery but even after charging (70%) the problem persists.
I also noted that it was hard to get into Download mode (needed 3 attempts). Maybe removing Knox caused some problems - although it should really affect this? Any ideas?

Sy1vus said:
Sorry but I have trouble following the instructions. I downloaded Odin 309 and was able to put Philz Recovery on my phone. I restarted my phone and it seems like I'm unable to enter the recovery mode. I hold down all three keys (VolUp) and the blue font in the corner appears but after a few second the phone just shuts down. I'm still able to boot normal, just not into recovery mode. I thought it might be because of my low battery but even after charging (70%) the problem persists.
I also noted that it was hard to get into Download mode (needed 3 attempts). Maybe removing Knox caused some problems - although it should really affect this? Any ideas?
Click to expand...
Click to collapse
Just hold volume up & power buttons til it says booting recovery then release both & should boot up ? I occasionally have probably entering recovery but that always works

11calcal said:
Just hold volume up & power buttons til it says booting recovery then release both & should boot up ? I occasionally have probably entering recovery but that always works
Click to expand...
Click to collapse
I did exactly that, somehow it worked after the 11th try - seriously. But thanks!!
I downloaded SuperSu from the play store. It now ask me to install the SU binary. Should I click "Normal" or "TWRP/CWM"?
Thanks once again!

Hit normal !!

Root stock 5.1 - Ub only

I'm no expert, so maybe a better way, but it worked for me, so try if you want...
Needed: stock ftf, (I used this https://shry.me/9L9OQ); CM boot img; TWRP img; Flashtool; fastboot, Supersu flashable zip.
1. Flash stock ftf with Flashtool, boot phone, and check 'android debugging ' and 'unknown sources'
2. Power off, hold volume up, and connect in fastboot mode
3. cd to adb directory on PC, type 'fastboot flash boot (CM file).img', and 'fastboot flash recovery (TWRP file).img'
4. disconnect phone, power on, volume up when you see led to enter recovery. Install > Supersu zip.
5. Power off, open Flashtool, and again flash ftf, but in 'exclude' box on right side, check everything except 'boot bundle, kernel, and fotakernel. (hopefully I'm remembering right).
When done, reboot, and you're rooted.

@levone1 link isn't working! pls fix.

itskapil said:
@levone1 link isn't working! pls fix.
Click to expand...
Click to collapse
Sorry, the parentheses got included in link. It's better now. By the way, I got it from here http://forum.xda-developers.com/son...al/ftf-xperia-z1-compact-d5503-5-1-1-t3201650.
Also, here's a couple more links to make it easier...
https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
https://mega.nz/#!k5E0kQpC!XdTudAe5ISAVyfQAHHMkgvjmNuY6TDxm62HzyOAEgmU
I'll post a CM boot link later if needed, or just download one.

http://forum.xda-developers.com/son...root-init-d-support-recovery-busybox-t3202799 is a nice addition to this method, (to get recovery and busybox after root). You can flash it with Rashr app on phone with root, (version 2.2.8).

levone1 said:
I'm no expert, so maybe a better way, but it worked for me, so try if you want...
Needed: stock ftf, (I used this https://shry.me/9L9OQ); CM boot img; TWRP img; Flashtool; fastboot, Supersu flashable zip.
1. Flash stock ftf with Flashtool, boot phone, and check 'android debugging ' and 'unknown sources'
2. Power off, hold volume up, and connect in fastboot mode
3. cd to adb directory on PC, type 'fastboot flash boot (CM file).img', and 'fastboot flash recovery (TWRP file).img'
4. disconnect phone, power on, volume up when you see led to enter recovery. Install > Supersu zip.
5. Power off, open Flashtool, and again flash ftf, but in 'exclude' box on right side, check everything except 'boot bundle, kernel, and fotakernel. (hopefully I'm remembering right).
When done, reboot, and you're rooted.
Click to expand...
Click to collapse
Links to these files?

NRG1975 said:
Links to these files?
Click to expand...
Click to collapse
3rd post has everything but CM boot. I'll post it if you need it. Or you could just download a ROM and extract.

NRG1975 said:
Links to these files?
Click to expand...
Click to collapse
This should work for boot IMG - https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM

This really is not that easy .... While it may be the easiest way, it is far from easy with Win 8 or Win 10. I am gonna forego root till an easier way is found. Thank you for your efforts.

No Busybox
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!

aravindclpy said:
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
Click to expand...
Click to collapse
Use stericson busybox from play store. I tried the other one and it didn't work, but that one worked for me. You can also manual push busybox if you have to.

aravindclpy said:
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
Click to expand...
Click to collapse
You can also use this - http://forum.xda-developers.com/son...root-init-d-support-recovery-busybox-t3202799
Since this came out, I recommend it over my method, since everything is included, and it's faster than using FT a second time.

Hey,
Usually this kind of stuff isn't a problem for me, but here I'm stuck at step 4.
When I try to flash superSU.zip, TWRP reboots by itself.
Also when TWRP boots, I'm asked to choose "keep read only" or "allow modifications" for the system partition. Both choices results in a reboot of TWRP.
Any idea ?
(I tried with the method in the link above, same thing happens)

Jackhass said:
Hey,
Usually this kind of stuff isn't a problem for me, but here I'm stuck at step 4.
When I try to flash superSU.zip, TWRP reboots by itself.
Also when TWRP boots, I'm asked to choose "keep read only" or "allow modifications" for the system partition. Both choices results in a reboot of TWRP.
Any idea ?
(I tried with the method in the link above, same thing happens)
Click to expand...
Click to collapse
Only time I ever got that from twrp was after doing ta update and booting into the new recovery. I just picked 'allow' and everything was fine. Are you booting into recovery the new way, or old? Are you using all of the files I posted, or a different boot, etc? My first shot would be to try a different recovery IMG, like an older twrp,and see if it works. I did all the above with the old recovery method, (wait for LED and vol up). Let me know...

@levone1 Thanks for your answer
I redownloaded all your files, did it again (exactly as it's said in the OP) and... it worked. I've done nothing more or less than last time I tried.. Unexplainable
Thanks anyway

Jackhass said:
@levone1 Thanks for your answer
I redownloaded all your files, did it again (exactly as it's said in the OP) and... it worked. I've done nothing more or less than last time I tried.. Unexplainable
Thanks anyway
Click to expand...
Click to collapse
Great... If you want busybox, etc., see the posts before yours.

Update (.216)
Just bumping thread for new fw. After FT flash, there is no r/w access. Can't use method in this forum without busybox, so to get busybox, just download nut dual recovery 'installer' option, and run on pc. Steps are same otherwise. I posted an ftf here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/216-stock-ftf-read-flashing-t3243728

levone1 said:
Just bumping thread for new fw. After FT flash, there is no r/w access.
Click to expand...
Click to collapse
The steps I took with UL BL...
Used the Flashtool and XperiFirm to download and flash 216.
Hot booted 368 kernel and flashed SU zip, confirmed root with TB and Root Explorer after reboot to stock 216 kernel.
Installed Busybox from Play Store.
Extracted kernel.sin from ftf and used @[NUT]'s Kernel Builder to add XZDualRecovery.
Extracted boot.img from zip and flashed with Fastboot.
Now I'm in the process of removing bloatware then I'm going to theme it.

Can't Root in galaxy Core Prime lte G360FXXU1BPI1

Hello,
i can't root in G360FXXU1BPI1 , i try kingroot or other root apllication and none, someone can help me please ?

https://download.chainfire.eu/767/C...etmo-cprimeltetmo-smg360t.zip?retrieve_file=1
will do the job
goodluck

merfim said:
Hello,
i can't root in G360FXXU1BPI1 , i try kingroot or other root apllication and none, someone can help me please ?
Click to expand...
Click to collapse
Try to find an older firmware version that can be flashed with Odin. Usually system updates patch exploits commonly used by one-click root apps, and only an older build will fix the issue. Hope this helps.

hi,
merfim said:
Hello,
i can't root in G360FXXU1BPI1 , i try kingroot or other root apllication and none, someone can help me please ?
Click to expand...
Click to collapse
I also couldn't root my device (galaxy core prime g361h) until i used TWRP and SuperSU, i tried those crappy one click roots none of them worked for me,TWRP and SuperSU are powerful.
First flash TWRP on your device using Odin then flash SuperSU using TWRP

Esma3elo said:
I also couldn't root my device (galaxy core prime g361h) until i used TWRP and SuperSU, i tried those crappy one click roots none of them worked for me,TWRP and SuperSU are powerful.
First flash TWRP on your device using Odin then flash SuperSU using TWRP
Click to expand...
Click to collapse
What TWRP version? Send me the link if you will

hey
Jrhotrod said:
What TWRP version? Send me the link if you will
Click to expand...
Click to collapse
TWRP 3.0.2-0
https://twrp.me/
What more do u want me to do
Root it for you

Esma3elo said:
TWRP 3.0.2-0
https://twrp.me/
What more do u want me to do
Root it for you
Click to expand...
Click to collapse
Okay thanks ☺

Hello sir
Follow my steps for successful TWRP/ROOT
1.)Download and install Samsung USB Drivers
2.)Download TWRP 3.0.2.0
3.)Download Odin
4.)Download SuperSU.zip file
For download links message me or add me on facebook facebook. com/fRoD.cs
After you complete this 4 steps shutdown your phone and enter into Download Mode
Volume Down + Power + Home
Select continue by Volume Up key
Now connect phone with usb cable into pc and run Odin as administrator
Click on AP box and select the twrp.tar file you download before
Go to Options tab and uncheck Auto Reboot, make sure that only F, Reset Time is checked and click start
After successfully installed TWRP , remove the battery, put it back and make sure that you go into recovery mode immediately!!! Volume Up + Power + Home
If you boot up the phone it will restore the original recovery. Thats why you need to go to recovery mode first.
First time you boot in recovery it will be shown a TWRP screen asking to allow modifications to system partition. Swipe to accept that.
Now select Install option and select SuperSU.zip file. By default it should be in Download folder, and swipe to start install
After installing click reboot and your SM-G361F will be rooted. You should have SuperSU app in the menu

Magisk on Oreo

I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.

I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...

GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?

+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)

+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?

kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!

+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?

GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.

kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)

I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.

kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?

GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good: