I don't have any need for systemless root, but in reading the SuperSU threads, several versions are not working right with Marshmallow. Problem is, it is unclear which versions or if its the systemless part that is broken on marshmallow or the normal SuperSU or whatever else. So I was wondering, if I just want to flash normal SuperSU, what version (and a link if possible) is working with Marshmallow?
If its relevant, XT1575 64GB currently trying to get TruPure 2.2 working but having a lot of problems with Xprivacy and boot loops.
Thanks!
Both work fine for me
if you are not systemless, beta 2.64 works just fine http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Thanks Naddict! I just flash it in TWRP like always?
i am using truepurex 2.1 as i dont care for Android pay and i didnt update further because there is no need.
no boot loops. didnt wipe just updated over 5.1 and xposed working too
silkshadow said:
Thanks Naddict! I just flash it in TWRP like always?
Click to expand...
Click to collapse
Pretty sure there is one more step
Naddict said:
if you are not systemless, beta 2.64 works just fine http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
Hey i am also confused by reading so many different threads. I just want to know which version works with MM.
Currently i am on stock L (rooted+xposed) on my xt1572 indian retasia_ds.
I am gonna flash ota then flash the latest twrp by hashbang and then boot in twrp and if TWRP asks to keep /system read-only, i'll keep read only. And then will flash supersu and xposed cause i guess now there is no need to flash modified boot.img
So i am really confused which supersu to flash, some say 2.62-3 is working and some say it's not. So should i flash 2.62-3 or 2.64
Also please confirm there is no need to flash modified boot_img
sorry asking so many question because i want to avoid flashing firmware for which i have to wipe the device completely
amit.lohar said:
Hey i am also confused by reading so many different threads. I just want to know which version works with MM.
Currently i am on stock L (rooted+xposed) on my xt1572 indian retasia_ds.
I am gonna flash ota then flash the latest twrp by hashbang and then boot in twrp and if TWRP asks to keep /system read-only, i'll keep read only. And then will flash supersu and xposed cause i guess now there is no need to flash modified boot.img
So i am really confused which supersu to flash, some say 2.62-3 is working and some say it's not. So should i flash 2.62-3 or 2.64
Also please confirm there is no need to flash modified boot_img
sorry asking so many question because i want to avoid flashing firmware for which i have to wipe the device completely
Click to expand...
Click to collapse
if you use 2.62 or higher you do not need to flash anything other than that. No boot.img file or anything else. http://forum.xda-developers.com/showpost.php?p=64161125
---------- Post added at 06:22 AM ---------- Previous post was at 06:21 AM ----------
silkshadow said:
Thanks Naddict! I just flash it in TWRP like always?
Click to expand...
Click to collapse
lafester said:
Pretty sure there is one more step
Click to expand...
Click to collapse
all you do is flash in TWRP, as long as you do not have a modified boot image! See here http://forum.xda-developers.com/showpost.php?p=64161125
Naddict said:
if you use 2.62 or higher you do not need to flash anything other than that. No boot.img file or anything else. http://forum.xda-developers.com/showpost.php?p=64161125
---------- Post added at 06:22 AM ---------- Previous post was at 06:21 AM ----------
all you do is flash in TWRP, as long as you do not have a modified boot image! See here http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
I followed the instructions on that post, keeping TWRP read only and flashing the 2.64 zip and now a ton of system processes are crashing and my sim isn't recognized. Is there a more stable version for the X Pure? This is a fresh MM install, so it shouldn't be conflicting with anything.
DesolateTen said:
I followed the instructions on that post, keeping TWRP read only and flashing the 2.64 zip and now a ton of system processes are crashing and my sim isn't recognized. Is there a more stable version for the X Pure? This is a fresh MM install, so it shouldn't be conflicting with anything.
Click to expand...
Click to collapse
Did you wipe caches? Which ROM did you install? Did you ignore the "install su" while in twrp?
Same for me, after stock MM upgrade, I installed latest supersu beta 2.64, also did wipe both caches, after rebooting there was ton of services just FC's.
BooBzi said:
Same for me, after stock MM upgrade, I installed latest supersu beta 2.64, also did wipe both caches, after rebooting there was ton of services just FC's.
Click to expand...
Click to collapse
Your post states you upgraded, so I assume you did not flash a complete ROM? If not, why not try that?
Naddict said:
Your post states you upgraded, so I assume you did not flash a complete ROM? If not, why not try that?
Click to expand...
Click to collapse
I am using XT1572, so there is not a lot of custom ROMS out there, so I am on STOCK MM. Now I am looking for supersu version that boots, 2.64 just do a lot of FC, 2.62.3 / 2.62 goes into bootloop.
BooBzi said:
I am using XT1572, so there is not a lot of custom ROMS out there, so I am on STOCK MM. Now I am looking for supersu version that boots, 2.64 just do a lot of FC, 2.62.3 / 2.62 goes into bootloop.
Click to expand...
Click to collapse
You could try this one, http://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155....I have not tried it, but it appears to be a popular one and it might do the trick for you. Just a thought.
Naddict said:
You could try this one, http://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155....I have not tried it, but it appears to be a popular one and it might do the trick for you. Just a thought.
Click to expand...
Click to collapse
I have used it for some hours. Didnt like it. Kernel modifications on that ROM was killing my battery. But thanks for help!
---------- Post added at 11:02 PM ---------- Previous post was at 10:52 PM ----------
OK! 2.62 did the trick, no bootloop anymore.
Download it from this thread: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
My device boot up, and I tested it. Root is working.
BooBzi said:
I have used it for some hours. Didnt like it. Kernel modifications on that ROM was killing my battery. But thanks for help!
---------- Post added at 11:02 PM ---------- Previous post was at 10:52 PM ----------
OK! 2.62 did the trick, no bootloop anymore.
Download it from this thread: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
My device boot up, and I tested it. Root is working.
Click to expand...
Click to collapse
Using 2.62 worked for me as well. Thanks for the help ☺
Related
Hello everyone! I have manually installed Lollipop 5.0.2 in my Nexus 7 wifi but I don't know how to root it. I have been reading in google that to root Lollipop is a little more complicated than KitKat. Can I flash SuperSu from the recovery or I need to flash a custom kernel first?
Thanks!
You should probably try the NRT (Nexus Root Toolkit) by WugFresh. I rooted my tablet in 2 minutes with that!
---------- Post added at 10:40 PM ---------- Previous post was at 10:40 PM ----------
lkeops said:
Hello everyone! I have manually installed Lollipop 5.0.2 in my Nexus 7 wifi but I don't know how to root it. I have been reading in google that to root Lollipop is a little more complicated than KitKat. Can I flash SuperSu from the recovery or I need to flash a custom kernel first?
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1766475
gyorgyszemok said:
You should probably try the NRT (Nexus Root Toolkit) by WugFresh. I rooted my tablet in 2 minutes with that!
---------- Post added at 10:40 PM ---------- Previous post was at 10:40 PM ----------
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
I know but I don't like the toolkits. I prefer to use fastboot command line.
lkeops said:
I know but I don't like the toolkits. I prefer to use fastboot command line.
Click to expand...
Click to collapse
Geez.
Throw on TWRP with fastboot then use it to flash ChainFire SuperSU update, update the binaries from there.
wtherrell said:
Geez.
Throw on TWRP with fastboot then use it to flash ChainFire SuperSU update, update the binaries from there.
Click to expand...
Click to collapse
Ok! I used this method with KitKat. Are you sure that it works in Lollipop too? What about the modified kernel? Is it necessary?
SuperSu v2.45 is ok?
Thanks!
lkeops said:
Ok! I used this method with KitKat. Are you sure that it works in Lollipop too? What about the modified kernel? Is it necessary?
SuperSu v2.45 is ok?
Thanks!
Click to expand...
Click to collapse
Worked for me. Shouldn't affect the kernel you already have.
Don't know what chainfires current version is.
Or you could try CF Autoroot.
I used UPDATE-SuperSU-v2.37.zip but there's probably a later one by now.
wtherrell said:
Worked for me. Shouldn't affect the kernel you already have.
Don't know what chainfires current version is.
Or you could try CF Autoroot.
I used UPDATE-SuperSU-v2.37.zip but there's probably a later one by now.
Click to expand...
Click to collapse
Thank! It worked. Flashed SuperSu v2.40 directly from TWRP.
I install TWRP and next i am going to install SuperSU v2.46 and the cellphone never enter to the firmware and stays in boot logo of motorola
Please Help
Cmora24 said:
I install TWRP and next i am going to install SuperSU v2.46 and the cellphone never enter to the firmware and stays in boot logo of motorola
Please Help
Click to expand...
Click to collapse
SuperSU isn't working great for our device for root access so that's why it's stuck where it's at. Read up here http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242 and restore your phone and install one of these backups and do not use SuperSU to root for now. Hope this helps.
shojus said:
SuperSU isn't working great for our device for root access so that's why it's stuck where it's at. Read up here http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242 and restore your phone and install one of these backups and do not use SuperSU to root for now. Hope this helps.
Click to expand...
Click to collapse
Oh men thanks a lot for that link i am going to install one of that link
Thanks
Su 2.65 works fine assuming you are unlocked and using modified kernel.
lafester said:
Su 2.65 works fine assuming you are unlocked and using modified kernel.
Click to expand...
Click to collapse
Sure does! I also just read that... But this way is a safer bet for people that don't wanna mess with flashing multiple files. I myself just want a systemless root with stock recovery which I have obtained finally. Problem is LOTS of posts in these forums are giving different instructions and there is no clear method for everyone unless you end up reading the proper one first.
---------- Post added at 11:34 PM ---------- Previous post was at 11:31 PM ----------
Cmora24 said:
Oh men thanks a lot for that link i am going to install one of that link
Thanks
Click to expand...
Click to collapse
BTW: Here is another link to the thread for which he is referring to about the kernel. http://forum.xda-developers.com/moto-x-style/development/wip-systemless-root-t3263405 (if you want systemless root like I did)
Well all i want is Pure Android 6.0 with root jajaja i dont know if i want change the kernel
Cmora24 said:
Well all i want is Pure Android 6.0 with root jajaja i dont know if i want change the kernel
Click to expand...
Click to collapse
Do you still need help? I'm going for the same type of build - stock/rooted (with Xposed)
Sent from my XT1575 using Tapatalk
SR3TLAW said:
Do you still need help? I'm going for the same type of build - stock/rooted (with Xposed)
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Well that sounds good but i dont kwon the meaning of Xposed and y dont know if deodex or odexed
Can you tell me your build(all thinks you are going to install) please
Hi, I'm new to Lenovo A6000. I have a relative that has a softbricked A6000. I wiped the phone via stock recovery, and no problems afterwards.
I wanted to flash custom ROMs for my relatives A6000, but I can't seem to flash the latest custom recovery (TWRP). It always fails. Never boots to recovery. I did some research here and there by reading in XDA and found some interesting things.
The question is:
What is the device that I'm using? How do I find out what it is? is it WT86518 or WT86528?
The phone's running on Stock KK ROM Kraft S037, Is there a problem on flashing custom recovery via fastboot when using this version of stockrom? Or there's something else wrong? Should I update it via OTA then try flashing it or is there an easier way of flashing it?
It's the old 2015 A6000. With 1 GB RAM and 8 GB ROM.
I'm pretty familiar with fastboot commands, so it's just weird that I can't flash TWRP in it. I even can't hotboot it (fastboot boot blabla.img).
Thanks before, please do reply.
So on which ROM are you just now
---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------
And if you are running KitKat then only CWM RECOVERY WORKS FINE
---------- Post added at 10:29 AM ---------- Previous post was at 10:28 AM ----------
http://www.itechaditya.com/how-to-root-install-cwm-recovery-on-lenovo-a6000plus/
---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------
ezrawk said:
Hi, I'm new to Lenovo A6000. I have a relative that has a softbricked A6000. I wiped the phone via stock recovery, and no problems afterwards.
I wanted to flash custom ROMs for my relatives A6000, but I can't seem to flash the latest custom recovery (TWRP). It always fails. Never boots to recovery. I did some research here and there by reading in XDA and found some interesting things.
The question is:
What is the device that I'm using? How do I find out what it is? is it WT86518 or WT86528?
The phone's running on Stock KK ROM Kraft S037, Is there a problem on flashing custom recovery via fastboot when using this version of stockrom? Or there's something else wrong? Should I update it via OTA then try flashing it or is there an easier way of flashing it?
It's the old 2015 A6000. With 1 GB RAM and 8 GB ROM.
I'm pretty familiar with fastboot commands, so it's just weird that I can't flash TWRP in it. I even can't hotboot it (fastboot boot blabla.img).
Thanks before, please do reply.
Click to expand...
Click to collapse
Follow this it works every time
http://www.itechaditya.com/how-to-root-install-cwm-recovery-on-lenovo-a6000plus/
The Hard Gamer said:
So on which ROM are you just now
---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------
And if you are running KitKat then only CWM RECOVERY WORKS FINE
---------- Post added at 10:29 AM ---------- Previous post was at 10:28 AM ----------
http://www.itechaditya.com/how-to-root-install-cwm-recovery-on-lenovo-a6000plus/
---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------
Follow this it works every time
http://www.itechaditya.com/how-to-root-install-cwm-recovery-on-lenovo-a6000plus/
Click to expand...
Click to collapse
Thanks for the reply, mate! Thanks for the links too! But I'd prefer using TWRP than CWM. So what do I have to do to be able to use TWRP? Do I have to update stock rom to Lollipop first? Or does it mean TWRP isn't compatible at all?
ezrawk said:
Thanks for the reply, mate! Thanks for the links too! But I'd prefer using TWRP than CWM. So what do I have to do to be able to use TWRP? Do I have to update stock rom to Lollipop first? Or does it mean TWRP isn't compatible at all?
Click to expand...
Click to collapse
Listen..
First anyhow update to lollipop
Then you can use twrp from here
https://www.androidfilehost.com/?fid=457095661767133940
The Hard Gamer said:
Listen..
First anyhow update to lollipop
Then you can use twrp from here
https://www.androidfilehost.com/?fid=457095661767133940
Click to expand...
Click to collapse
One more question, do I have to like.. update the stock rom to lollipop or can I just use the 'Kitkat-lolipop firmware base switcher for a6000' method by @rahulsnair ? Thanks a lot mate for the info! :good:
*PS. I tried that version of TWRP firsthand before I posted this thread, so it means what made TWRP incompatible was because of the HH itself was still on old KK right?
ezrawk said:
do I have to like.. update the stock rom to lollipop or can I just use the 'Kitkat-lolipop firmware base switcher for a6000' method
Click to expand...
Click to collapse
Yeah exactly. Flash the firmware base switcher (for A6000 by rahulsnair and for A6000plus by me, sasukay).
Steps:
0. Flash the cwm or twrp 2.6.x (i guess) which works on KK
1. Then boot into custom recovery you've installed.
2. Then flash the firmware base switcher.
3. Now you can flash the latest twrp using fastboot which is meant for Lollipop and newer versions.
sasukay said:
Yeah exactly. Flash the firmware base switcher (for A6000 by rahulsnair and for A6000plus by me, sasukay).
Steps:
0. Flash the cwm or twrp 2.6.x (i guess) which works on KK
1. Then boot into custom recovery you've installed.
2. Then flash the firmware base switcher.
3. Now you can flash the latest twrp using fastboot which is meant for Lollipop and newer versions.
Click to expand...
Click to collapse
Thanks for the reply sasukay! Yeah! I had a hunch that the latest TWRP didn't boot was because of stock KK! I consulted to a friend that was using A6000 Plus before I did all of this, he told me he was on stock 'LP' when he flashed latest TWRP and he didn't tell me (or more like he didn't know) that the A6000 has to be on LP before flashing latest TWRP. Hope nothing goes wrong now. Wish me luck! :laugh: :good: :highfive: :fingers-crossed:
sasukay said:
Yeah exactly. Flash the firmware base switcher (for A6000 by rahulsnair and for A6000plus by me, sasukay).
Steps:
0. Flash the cwm or twrp 2.6.x (i guess) which works on KK
1. Then boot into custom recovery you've installed.
2. Then flash the firmware base switcher.
3. Now you can flash the latest twrp using fastboot which is meant for Lollipop and newer versions.
Click to expand...
Click to collapse
ezrawk said:
One more question, do I have to like.. update the stock rom to lollipop or can I just use the 'Kitkat-lolipop firmware base switcher for a6000' method by @rahulsnair ? Thanks a lot mate for the info! :good:
*PS. I tried that version of TWRP firsthand before I posted this thread, so it means what made TWRP incompatible was because of the HH itself was still on old KK right?
Click to expand...
Click to collapse
Thanks sauskay you are awesome:highfive:
The Hard Gamer said:
Thanks sauskay you are awesome:highfive:
Click to expand...
Click to collapse
Thanks to you too mate! Both you guys are totally awesome! :good: :good: :highfive:
@The Hard Gamer, @ezrawk ==>> I think you guys are getting too much dramatic. It was just a lil' advice
sasukay said:
@The Hard Gamer, @ezrawk ==>> I think you guys are getting too much dramatic. It was just a lil' advice
Click to expand...
Click to collapse
Yeah too much of cinema haha
SevenMaxs 2.66 works fine on kitkat
Has anyone successfully, and without subsequent issues, rooted the g4 XT1622?
I have unlocked the bootloader and installed TWRP. Have tried flashing two separate versions of Super SU (version 2.78 and 2.82) .
Each appears to flash successfully and complete but when rebooting phone stays on a black screen.
I then have to reboot into recovery and restore the Nandroid backup.
I tried Kingroot but that says no solution for this device.
If anyone has managed it I'd be grateful for the detail.
uneed the elemental x kernel to root nougat as far as i know, other wise it wont work
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672
skastream said:
uneed the elemental x kernel to root nougat as far as i know, other wise it wont work
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672
Click to expand...
Click to collapse
Indeed you are correct. The stock kernel does not have an exploit for root access, that's why SuperSU and Magisk leave you at a black screen upon flashing the zip file. Having any custom kernel should fix the problem(Vegito or ElementalX).
Ytim08 said:
Indeed you are correct. The stock kernel does not have an exploit for root access, that's why SuperSU and Magisk leave you at a black screen upon flashing the zip file. Having any custom kernel should fix the problem(Vegito or ElementalX).
Click to expand...
Click to collapse
Thanks - I may be trying to do something wrong but when I tried to flash ElementalX from the app it returned a message that the device needed to be rooted to install ElementalX. I wasn't sure where to go from there.
yes, i am running rooted G4 (xt1622) with TWRP and super su 2.78 now. as far as I can remember, there is one line of code like 'systemless=true' (or something similar, it's easy to search online) to enter via the Linux terminal. Then it can be rooted successfully. without that line, i got a soft-bricked mogo g4 as well (black screen forever).
it's a shame that the rooted phone cannot install OTA updates at all. I am still on Android 6.0.1 (which is the stock rom and very old). I am planning to restore to stock then upgrade to Nougat recently.
actomox said:
Thanks - I may be trying to do something wrong but when I tried to flash ElementalX from the app it returned a message that the device needed to be rooted to install ElementalX. I wasn't sure where to go from there.
Click to expand...
Click to collapse
You must download the latest Elemntal X version for your device and flash via recovery(TWRP)
---------- Post added at 08:24 AM ---------- Previous post was at 08:22 AM ----------
libralibra said:
yes, i am running rooted G4 (xt1622) with TWRP and super su 2.78 now. as far as I can remember, there is one line of code like 'systemless=true' (or something similar, it's easy to search online) to enter via the Linux terminal. Then it can be rooted successfully. without that line, i got a soft-bricked mogo g4 as well (black screen forever).
it's a shame that the rooted phone cannot install OTA updates at all. I am still on Android 6.0.1 (which is the stock rom and very old). I am planning to restore to stock then upgrade to Nougat recently.
Click to expand...
Click to collapse
Just download your devices latest firmware from androidfilehost.com and flash through adb & fastboot or RSDLite
Ytim08 said:
Just download your devices latest firmware from androidfilehost.com and flash through adb & fastboot or RSDLite
Click to expand...
Click to collapse
thanks for your suggestion. no luck on androidfilehost.com for xt1622.
libralibra said:
thanks for your suggestion. no luck on androidfilehost.com for xt1622.
Click to expand...
Click to collapse
Here, I'll find your firmware.
---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------
libralibra said:
thanks for your suggestion. no luck on androidfilehost.com for xt1622.
Click to expand...
Click to collapse
Try this: https://androidfilehost.com/?fid=673368273298955218
Ytim08 said:
Here, I'll find your firmware.
---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------
Try this: https://androidfilehost.com/?fid=673368273298955218
Click to expand...
Click to collapse
I really appreciate your great help. still confused about the procedure that needs to take:
plan a:
1. go back to ATHENE_MPJ24.139.23.4(the current one, 6.0.1), everything including the stock recovery
2. wait for OTA, update a couple times to the latest nougat
plan b:
1. flash the file from your link which is ATHENE_NPJS25.93-14-4,
2. is this the end?
I do notice the difference in the name: MPJ vs. NPJS, does that matter? I flashed several phones, but never figure out what the names meant.
libralibra said:
I really appreciate your great help. still confused about the procedure that needs to take:
plan a:
1. go back to ATHENE_MPJ24.139.23.4(the current one, 6.0.1), everything including the stock recovery
2. wait for OTA, update a couple times to the latest nougat
plan b:
1. flash the file from your link which is ATHENE_NPJS25.93-14-4,
2. is this the end?
I do notice the difference in the name: MPJ vs. NPJS, does that matter? I flashed several phones, but never figure out what the names meant.
Click to expand...
Click to collapse
MPJ = Marshmallow
NPJS = Nougat
I think flashing last firmware is the best thing to do in your case. I have a batch file you can use if you want
Ytim08 said:
MPJ = Marshmallow
NPJS = Nougat
I think flashing last firmware is the best thing to do in your case. I have a batch file you can use if you want
Click to expand...
Click to collapse
thanks for the clarification. please post your batch script for me.
flashing is planned in the next couple of weeks.
libralibra said:
thanks for the clarification. please post your batch script for me.
flashing is planned in the next couple of weeks.
Click to expand...
Click to collapse
Happy flashing
https://drive.google.com/file/d/0BxA_NTGSyBmaWkI2Y1pOMEhUNWM/view?usp=sharing
Note: You do need minimal adb & fastboot files inside flashing folder (You probably already know that but just to be sure)
I have rooted the S8. If I flash a custom kernel now, no matter which one (TGP, NX, NOTORIOUS) I can not turn on the WLAN afterwards, - the slider always jumps out. With and without Wipe, - does not work.
Flash original firmware from sammobile then test it.
osama bhatti0 said:
Flash original firmware from sammobile then test it.
Click to expand...
Click to collapse
Have an original firmware flashed, there goes wireless.
Even after Rooten goes wireless.
bininga59 said:
Have an original firmware flashed, there goes wireless.
Even after Rooten goes wireless.
Click to expand...
Click to collapse
Sir flash latest firmware then root it only by twrp and when you flash twrp you have to wipe data typing yes for complete functionality and them root it by magisk. I hope you wont get any issues. Seriosuly did to my s8 same many times didnt face the issue once.
osama bhatti0 said:
Sir flash latest firmware then root it only by twrp and when you flash twrp you have to wipe data typing yes for complete functionality and them root it by magisk. I hope you wont get any issues. Seriosuly did to my s8 same many times didnt face the issue once.
Click to expand...
Click to collapse
I flashed TWRP with Odin.
Then in the TWRP SuperSU flashed, nothing else.
As soon as I take a custom kernel - no Wi-Fi
Or did I misunderstand you?
bininga59 said:
I flashed TWRP with Odin.
Then in the TWRP SuperSU flashed, nothing else.
As soon as I take a custom kernel - no Wi-Fi
Or did I misunderstand you?
Click to expand...
Click to collapse
Maybe maybe sir its because if supersu maybe, with all due respect repeat process and this time root using Magisk i use it and installed NX kernel worked fine i know kernel provide features but if it doesnt help make compromise with stock kernel and keep using it.
---------- Post added at 09:56 PM ---------- Previous post was at 09:52 PM ----------
And sir dont rush into aything whenever you install twrp after flashing origi al firmware, when twrp boots for the first time you have to keep it read only dont allow modifications then go to wipe and wipe data type yes then reboot your phone compkete setup then install magisk then reboot and again boot into twrp now flash custom kernel. I explained everything what i do and i am fine everythings fine running custom kernel without issue.
osama bhatti0 said:
Maybe maybe sir its because if supersu maybe, with all due respect repeat process and this time root using Magisk i use it and installed NX kernel worked fine i know kernel provide features but if it doesnt help make compromise with stock kernel and keep using it.
---------- Post added at 09:56 PM ---------- Previous post was at 09:52 PM ----------
And sir dont rush into aything whenever you install twrp after flashing origi al firmware, when twrp boots for the first time you have to keep it read only dont allow modifications then go to wipe and wipe data type yes then reboot your phone compkete setup then install magisk then reboot and again boot into twrp now flash custom kernel. I explained everything what i do and i am fine everythings fine running custom kernel without issue.
Click to expand...
Click to collapse
Alright. I'll try Magisk again
I know its a long process but sir told you the same i did to my s8 really hope that this time it works out for you?
---------- Post added at 10:12 PM ---------- Previous post was at 10:03 PM ----------
Sir wait i did a little searching and found this
https://forum.xda-developers.com/ga...elopment/kernel-nox-kernel-v1-t3721469/page18
Post number 174 this will definitely help u.
osama bhatti0 said:
I know its a long process but sir told you the same i did to my s8 really hope that this time it works out for you
---------- Post added at 10:12 PM ---------- Previous post was at 10:03 PM ----------
Sir wait i did a little searching and found this
https://forum.xda-developers.com/ga...elopment/kernel-nox-kernel-v1-t3721469/page18
Post number 174 this will definitely help u.
Click to expand...
Click to collapse
Thank you, - it works.:good::good::good:
bininga59 said:
Thank you, - it works.:good::good::good:
Click to expand...
Click to collapse