Related
Is there a root procedure for the galaxy s4 that's on the newest lollipop update ? I was able to root with kingroot but read its not safe to use kingroot and try install a custom rom ?
dpmeeks said:
Is there a root procedure for the galaxy s4 that's on the newest lollipop update ? I was able to root with kingroot but read its not safe to use kingroot and try install a custom rom ?
Click to expand...
Click to collapse
CF-autoroot or flash TWRP then in TWRP flash SuperSU
Kingroot and SuperSU_me method works also... Watch the entire process in 2 parts... https://www.youtube.com/watch?v=IWnYFDQ1Vio
K94U said:
Kingroot and SuperSU_me method works also... Watch the entire process in 2 parts... https://www.youtube.com/watch?v=IWnYFDQ1Vio
Click to expand...
Click to collapse
Have you lost root since? I've read a lot about people loosing root after a few hours to a couple of days. Any other issues, like random crashes / freezes / reboots?
Ezintn said:
Have you lost root since? I've read a lot about people loosing root after a few hours to a couple of days. Any other issues, like random crashes / freezes / reboots?
Click to expand...
Click to collapse
That's why flashing TWRP and SuperSU is the safest/easiest way to root, it's about as straightforward as it gets
mattzeller said:
That's why flashing TWRP and SuperSU is the safest/easiest way to root, it's about as straightforward as it gets
Click to expand...
Click to collapse
Wasn't aware I could flash a custom recovery on a stock unrooted phone. I don't use the s4, that's why both of the ones I own aren't rooted already, my personal phones are often rooted before I even get home from the store! I need root and su without tripping knox or making any significant changes to the current set-up on either phone. I would prefer the recovery was stock on at least one of 'em. So how should I go about this? One is a tri band and the other isn't. The dual band one needs to be as stealth as possible. Losing root really won't matter as long as the system permissions remain as is prior to losing root.
Ezintn said:
Wasn't aware I could flash a custom recovery on a stock unrooted phone. I don't use the s4, that's why both of the ones I own aren't rooted already, my personal phones are often rooted before I even get home from the store! I need root and su without tripping knox or making any significant changes to the current set-up on either phone. I would prefer the recovery was stock on at least one of 'em. So how should I go about this? One is a tri band and the other isn't. The dual band one needs to be as stealth as possible. Losing root really won't matter as long as the system permissions remain as is prior to losing root.
Click to expand...
Click to collapse
Flashing a custom recovery is going to trip knox. Why do you care about knox? Triband or not flashing TWRP and SuperSU is the same. If you lose root and have things that require root to operate, you will lose the function of those things, unless it's a one off type of thing
mattzeller said:
Flashing a custom recovery is going to trip knox. Why do you care about knox? Triband or not flashing TWRP and SuperSU is the same. If you lose root and have things that require root to operate, you will lose the function of those things, unless it's a one off type of thing[/QU
It's imperative that root is stealth. Just need to give one app already running su permissions. On one device knox is monitored, that's why I care. I wouldn't care on my s5, but I never tripped it anyway - rooted with modified stock recovery, flashed MOAR, flashed TWRP. Been using MAOR and TWRP since each was first released. Been rooted on my personal devices since 3 days after the Hero was released. I've just never rooted the s4 or "stealth rooted" any device. That's why Kingroot / SSM looks promising. Any help would be appreciated.
Click to expand...
Click to collapse
As the title implies, i wanted to give XT1562_LUX_RETASIA_DS_6.0.1_MPD24.107-70 a shot. Flashing works fine. I can boot the system, SIMs and WLAN work. TWRP 3.0.2-r3 works.
What doesn't work is supersu. I tried 2.62 and 2.76 both, it installs in system mode, then gets stuck while booting. 2.76 on the "M powered by android" boot image, before the "globe" animation started, and 2.62 after the globe animation. I wiped cache/dalvik, tried not wiping it, no-go. Just restarting the MXP doesn't help either.
Are there more things i could try, is anyone using that firmware yet? Which supersu? Do i have to factory reset before using supersu maybe?
Booting into recovery immediatly after flashing in fastboot doesn't work, as the internal sd cannot be mounted by twrp unless the system booted once.
It needs to be systemless, mate
http://forum.xda-developers.com/showpost.php?p=66735900&postcount=126
I have also flashed the same firmware using rsd lite.Then flashed twrp-lux-2.8.7-r4 through adb.After that just flashed supersu 2.62 normally and everything is working fine.I do not know what is systemless root and how it is done.But the normal flashing has worked for me.
situ1962 said:
I have also flashed the same firmware using rsd lite.Then flashed twrp-lux-2.8.7-r4 through adb.After that just flashed supersu 2.62 normally and everything is working fine.I do not know what is systemless root and how it is done.But the normal flashing has worked for me.
Click to expand...
Click to collapse
Um, I'm a noob so may I ask what i systemless?
minimale_ldz said:
It needs to be systemless, mate
http://forum.xda-developers.com/showpost.php?p=66735900&postcount=126
Click to expand...
Click to collapse
Thank you, i had been looking for this. The stupid blogs i googled regarding systemless only said supersu would choose it automatically if it had to. WELL APPARENTLY NOT
@HerySean
Unlike a "system" root the "systemless" approach does not actually modify your rom. It does some trickery while booting to achieve the same. Advantage: There won't be any bootloops ever, if a problem occurs you just won't have root. Also stuff like google pay. Disadvantages: A factory wipe will wipe a systemless root.
AtomicStryker said:
Thank you, i had been looking for this. The stupid blogs i googled regarding systemless only said supersu would choose it automatically if it had to. WELL APPARENTLY NOT
@HerySean
Unlike a "system" root the "systemless" approach does not actually modify your rom. It does some trickery while booting to achieve the same. Advantage: There won't be any bootloops ever, if a problem occurs you just won't have root. Also stuff like google pay. Disadvantages: A factory wipe will wipe a systemless root.
Click to expand...
Click to collapse
Oh I get it, thanks, the same thing I did back then to my Xperia C
Are there more steps to this? The systemless root seems to work fine, i boot, but the supersu app claims the device is not rooted....
btw, does it bring a new baseband? edit: doesn't seem so new actually
After several attempts 2.62 worked after all, in system mode even. I don't even know.
So I have the stock (OTA) MM rom installed and rooted with SuperSU flashed, however Android Pay will not work. I've tried disabling root in SuperSU, but that doesn't work for AP. Is there another method that actually works to allow? All the info I can find about it from last year.
Look around the frankenclark thread in development. I think they might have had a working setup with magisk in the discussion there.
macville said:
So I have the stock (OTA) MM rom installed and rooted with SuperSU flashed, however Android Pay will not work. I've tried disabling root in SuperSU, but that doesn't work for AP. Is there another method that actually works to allow? All the info I can find about it from last year.
Click to expand...
Click to collapse
jason2678 said:
Look around the frankenclark thread in development. I think they might have had a working setup with magisk in the discussion there.
Click to expand...
Click to collapse
It's been a while since others and I posted about that, so that method doesn't work anymore. I don't use Magisk now. It might be working again, but I won't test, so here's my setup without Magisk:
SuperSU flashed as systemless + update SuperSU to 2.78-SR5 + suhide 0.55 + Root Switch 1.3.3.2
Flash in that order.
Use Tasker or Automate to automatically disable and re-enable root when Android Pay and Google Play Services is/is not used, or disable/enable root from within the Root Switch app itself.
Confirmed that it works on stock rooted Marshmallow here.
So, I wanted to use SuperSU as my main root solution(to have the latest magisk, and because it is tested and tried), I attempted rooting with super v2.81 on stock build NPP25.137.72, and to my surprise: it worked!! So now we have SuperSU alongside Magisk as our root solutions
ap4ss3rby said:
So, I wanted to use SuperSU as my main root solution(to have the latest magisk, and because it is tested and tried), I attempted rooting with super v2.81 on stock build NPP25.137.72, and to my surprise: it worked!! So now we have SuperSU alongside Magisk as our root solutions
Click to expand...
Click to collapse
Very cool :good:, could you provide a link and maybe some further informations?
Just flash SuperSu v2.82 on top of the aforementioned build, using twrp
however, I would like to note that even though requesting sure is recorded by the SuperSU app(and reports granting SU access) we don't have root access
Just flash SuperSu v2.82 on top of the aforementioned build, using twrp
however, I would like to note that even though requesting SU is recorded by the SuperSU app(and reports granting SU access) we don't have root access
ap4ss3rby said:
Just flash SuperSu v2.82 on top of the aforementioned build, using twrp
however, I would like to note that even though requesting SU is recorded by the SuperSU app(and reports granting SU access) we don't have root access
Click to expand...
Click to collapse
Hello,
I just received my own, and want to be sure:
did Supersu worked yes or no?
can you explain the different steps from a brand new stock g5?
and does fingerprint still works after all?
thank you
daktary said:
Hello,
I just received my own, and want to be sure:
did Supersu worked yes or no?
can you explain the different steps from a brand new stock g5?
and does fingerprint still works after all?
thank you
Click to expand...
Click to collapse
Fingerprint still works, but root access very rarely works, but SuperSu does install, and for installation:
In a nutshell unlock the bootloader, flash twrp, get supersu v2.82 flashable zip on the sdcard, install the latest available app from apkmirror, and you're done
Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2