Hello all, new here. Having a hard time figuring out what my options here are. At one time I had root, unrooted for reasons that escape me, accidentally upgraded... Kinda never messed with it much and did a couple factory data wipes...
Current build 0c1.
Thanks for any help, sorry for being n00bz0rz.
Your bootloader is probably locked, but you can root with king root (Not kingo) and switch to SuperSU. SuperSU is better. Google how to make the transition. That way you'll at least have root.
Thanks @Airsoftjunky
I should have been more clear... I got the kingroot and supersu swap method to root.
BUT
Keep finding info for of1 king root and supersu swap, change kernel to 0c1 and do something so stops spitting out error message....
My question was ment to be, what rom options do I have? Do have any baseband/radio options? Kernel?
So, I don't needed to need mess with kernels right? And can run some mods like hyperdrive? Have to be 5.0 roms, correct?
So, just to be clear, you've rooted with Kingroot, but can't switch to SuperSU? (Where is the error, and what is it exactly?)
Compermised said:
Thanks @Airsoftjunky
I should have been more clear... I got the kingroot and supersu swap method to root.
BUT
Keep finding info for of1 king root and supersu swap, change kernel to 0c1 and do something so stops spitting out error message....
My question was ment to be, what rom options do I have? Do have any baseband/radio options? Kernel?
So, I don't needed to need mess with kernels right? And can run some mods like hyperdrive? Have to be 5.0 roms, correct?
Click to expand...
Click to collapse
Your safest bets are 'Touchwiz' based ROMs as your bootloader is locked on lollipop and there is no fix for that. Search forum for "Albe95'" or Stang5itre roms
Related
Do we know a root procedure that will work after the 4.3 update?
I too am curious to know!
Just root? The old way works. If you want full R/W access to the system folders then as far as I know thats not working right without a customer kernel.
Shane_pcs said:
Just root? The old way works. If you want full R/W access to the system folders then as far as I know thats not working right without a customer kernel.
Click to expand...
Click to collapse
Does it matter if mine is s-off?
Alright, I got mine rooted with no problems.
Just install TWRP, CWM, or CM2 for the recovery and then install SuperSU to get the root.
If you do TWRP like I did, when you go to reboot the system for the first time, it will say that you aren't rooted and ask if you want to run SuperSU to root. Pretty straight forward.
Hi folks,
Ive been having a strange problem with a couple Galaxy Mega I9200. I have rooted both before without any problems using KINGO originally. The i decided to update both of them with version UBUCNA2. When i tried to re root them back, even though the process have run fine a couple times the phone is not rooting. At this point i dont know what else to do to try to root those phones. I have tried every single method around this forum i think not just KINGO this time. And have not been able to reach root the way it should. Titanium backup shows not able to aquire root priviledges, and other root apps also. Can someone please help me on this?? Keep in mind im not a newbie so dont give me the recovery method advice without something new or to use KINGO because ive have done that already. Thanks a lot guys
You upgraded your phones to the latest knox enabled firmware which has the knox bootloader. You cannot go back to an older firmware or flash a custom rom now.
To root, try the directions provided in this thread and use the melius3gxx files instead of meliusltexx.
Silesh.Nair said:
You upgraded your phones to the latest knox enabled firmware which has the knox bootloader. You cannot go back to an older firmware or flash a custom rom now.
To root, try the directions provided in this thread and use the melius3gxx files instead of meliusltexx.
Click to expand...
Click to collapse
Ok thanks, the phones already had the knox apk so my guess was that it was going to be the same thing. Thanks for clarifying that one. And thanks for the advice.
Thanks again, turns out the only thing that is failling root access is when i try to unlock the phone via box. For some reason when its checking for SU access it fails. But thanks anyway i managed to solve the Root problem.
root.
I rooted through Phill touch Recovery.
Hey guys.
Used the HTC All in one toolkit and rooted, installed TWRP, and a new rom on my device. I want to S-off but since my phone is brand new it doesnt seem to work. (This will never work on your phone stop trying - error with firewater) I used the Perm Root method on the All-in-one toolkit but everytime i reboot my device i lose root and need to wait for it to come back up (2-3 Min after bootup). This means its not permanent correct? Maybe this is why firewater is not working?
Another really weird thing, when i reboot with adb reboot, the phone takes literally like 10-15 minutes to power on. What is that about?
TWRP seems as it is permanent, and on the bootloader it says tampered and unlocked with s-on.
Im kinda confused here, I came from a nexus 4 so im not used to things not working.
SOOOOOOO..
(Q) Can someone give me an overview of what is going on so i can go in the right direction? should i unroot to stock and try again? Why would it give me a TEMP root if i used the permanent root method of flashing SuperSU in recovery? If i switch roms, is the perm root method removed?
Thanks in advance guys!
If you flashed a custom ROM, they are already rooted. So if you also flashed SuperSU in addition, you might have some conflict, such as a built-in SU conflicting with the SuperSU you flashed.
I would re-flash the ROM (you can probably "dirty" flash and keep user data, just wipe cache and Dalvik), don't flash any separate SuperSU or SU, and see if the problem persists.
The long boot problem is a known issue if you flashed a 2.xx based ROM (Android 4.4.3) but your phone is still on older firmware (hboot, radio, etc.). You might also experience some other significant bugs like broken WiFi or Bluetooth.
Firewater s-off has been patched for some time now, but Sunshine S-off should work (but costs $25).
You will need s-off to manually update firmware. But the alternative is to return to stock ROM and recovery, accept your latest OTA, which will install the new firmware.
redpoint73 said:
If you flashed a custom ROM, they are already rooted. So if you also flashed SuperSU in addition, you might have some conflict, such as a built-in SU conflicting with the SuperSU you flashed.
I would re-flash the ROM (you can probably "dirty" flash and keep user data, just wipe cache and Dalvik), don't flash any separate SuperSU or SU, and see if the problem persists.
The long boot problem is a known issue if you flashed a 2.xx based ROM (Android 4.4.3) but your phone is still on older firmware (hboot, radio, etc.). You might also experience some other significant bugs like broken WiFi or Bluetooth.
Firewater s-off has been patched for some time now, but Sunshine S-off should work (but costs $25).
You will need s-off to manually update firmware. But the alternative is to return to stock ROM and recovery, accept your latest OTA, which will install the new firmware.
Click to expand...
Click to collapse
Thanks for the speedy response.
I flashed the insertcoin rom. It was supposed to root with that (Chose SuperSU on aroma install) but no SuperSU was installed. It seemed like insert coin was a little buggy. So i installed the SuperSU with perm root option on all-in-one toolkit. And SuperSU was giving me errors of not being supported and need to update through recovery, it wasnt updating. Wiped, Reflashed insertcoin, this time SuperSU installed on the device, tried s-off with firewater and didnt work. Then i did a full wipe again.
This time I flashed M8Rx.v2 and seems like a solid running rom - Minus the fact that Wifi is broken. (It said use a specific kernel if on 1.58 firmware, but my phone came with 2.xx, maybe it went down to 1.58 with insertcoin) Came with SuperSU however now it doesn't have permanent root (I have not done perm root on all-in-one after wiping and flashing M8Rx.v2).
I have read that perm root may not work unless s-off. Is this true?
Also - Worth noting that when i was stock, there was no OTA available. i was on build 2.xx and now with M8rx.v2 im on build 1.58.502.1.
H0rn3t920 said:
I have read that perm root may not work unless s-off. Is this true?
Click to expand...
Click to collapse
No, that is completely false.
How are you determining root or no root?
For Insertcoin, you won't see SuperSU or SU in the app drawer. Its in the Settings>InsertCoin. If not having SuperSU in the app drawer is solely what led you to believe you weren't rooted, I think you may have just been confused about it and were rooted all along.
I don't know about M8Rx, as I've never used it.
redpoint73 said:
No, that is completely false.
How are you determining root or no root?
For Insertcoin, you won't see SuperSU or SU in the app drawer. Its in the Settings>InsertCoin. If not having SuperSU in the app drawer is solely what led you to believe you weren't rooted, I think you may have just been confused about it and were rooted all along.
I don't know about M8Rx, as I've never used it.
Click to expand...
Click to collapse
That was part of it, the other part was when using firewater, i would get no superuser prompts. That is a good piece of info though, thanks!
So how would i go about doing a permanent root and s-off? should i go back to stock and use the 25$ method or should i keep my rom and custom recovery and then do it? Mainly im curious about the permanent root as i have done what i should have for a permanent root and its not permanent. So I dont really understand what to do here.
H0rn3t920 said:
That was part of it, the other part was when using firewater, i would get no superuser prompts. That is a good piece of info though, thanks!
So how would i go about doing a permanent root and s-off? should i go back to stock and use the 25$ method or should i keep my rom and custom recovery and then do it?
Click to expand...
Click to collapse
I think you are perm rooted already. Not getting SU prompt in firewater is likely a different issue.
Make sure debugging is activated. Also, firewater doesn't work with some custom ROMs, not sure about InsertCoin. But you might try a different ROM.
Firewater was patched some time ago, and doesn't work for most M8's at this point. As your device was updated to the 2.xx software, firewater likely won't work. But you should at least get to the "whelp" error message from firewater before concluding that it won't work on your device.
redpoint73 said:
I think you are perm rooted already. Not getting SU prompt in firewater is likely a different issue.
Make sure debugging is activated. Also, firewater doesn't work with some custom ROMs, not sure about InsertCoin. But you might try a different ROM.
Firewater was patched some time ago, and doesn't work for most M8's at this point. As your device was updated to the 2.xx software, firewater likely won't work. But you should at least get to the "whelp" error message from firewater before concluding that it won't work on your device.
Click to expand...
Click to collapse
I did get the whelp message...
My confusion here is if i am perm rooted, why do i lose root on a reboot? All my xposed modules stop working, says version 58 has been installed but only found version 47. I hit install/update, superuser permissions granted and it immedietely says version 58 is found. I need to then soft reboot in order for all modules to activate.
Now its saying SuperSU is having issues updating the binaries. I flash the binaries in TWRP and then after the phone boots, it says the same thing again, to update binaries. I want to get into SuperSU to unroot and then flash SuperSU again in TWRP to see if that works, but i can not get around the update binaries screen. If i hit cancel, app closes.
EDIT: So i updated binaries, and i didnt get the update notification anymore. Got into the app, unrooted, then reinstalled supersu from TWRP, and then installed SuperSU from app store. Asked to update binaries, did it. Enabled SU at boot in SuperSU Settings. Still exactly the same. Even though xposed is granted superuser permissions, i need to go into the app and tinker with it before its auto granted and version 58 of xposed is seen.
I also tried in SuperSU Settings to write to system but it doesnt seem to work.
What am i missing here!?
Did you try to flash the ROM again, and this time not do anything additional to root (aside from the AROMA selection of SU/SuperSU), like I suggested back in Post #2?
I think something with the toolkit or flashing SU otherwise is messing with the built-in root.
I'm on InsertCoin, and have never had any issues with root.
redpoint73 said:
Did you try to flash the ROM again, and this time not do anything additional to root (aside from the AROMA selection of SU/SuperSU), like I suggested back in Post #2?
I think something with the toolkit or flashing SU otherwise is messing with the built-in root.
I'm on InsertCoin, and have never had any issues with root.
Click to expand...
Click to collapse
Thats how i did it to begin with on all my roms that i flashed. Only went and flashed the SuperSU after I realized that the rom itself didnt give a permanent root.
So I wiped the phone fully like 4-5 times before flashing M8Rx.v2 and everything is working super smooth and beautiful now. Thank you to redpoint73 and his help!
H0rn3t920 said:
Thats how i did it to begin with on all my roms that i flashed. Only went and flashed the SuperSU after I realized that the rom itself didnt give a permanent root.
Click to expand...
Click to collapse
Odd, all I can think is that the AROMA option to select SU/SuperSU is a little buggy.
Looks like persistence (or at least vigorous wiping) was the key!
Hi all, thanks in advance for any help on this. I have a few general s5 rooting questions. I'm an experienced 'rooter' having rooted and installed custom ROMs on many previous devices.
- I've ready that the s5 has an 'e-fuse' that gets 'blown' when the device is rooted. this then voids the warranty and prevents things like Fort Knox from running. I get that, and understand the risks. But, I've also read that the lollipop update will remove root. These two things seem to contradict themselves.
- on other devices I've rooted, I've then installed a custom ROM. I don't plan to do this with my s5. I haven't been able to find much written on the experience of a rooted s5 running the samsung stock ROM/firmware. I'd like to use something like xposed to change parts of the ROM (like the white background that's so pervasive in the s5 flavor of lollipop). I'm curious if anyone is running lollipop on an s5 that is rooted but running stock samsung firmware and xposed.
thanks!
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
thanks!
stncldtex said:
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
Click to expand...
Click to collapse
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
scwtech said:
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
Click to expand...
Click to collapse
Right now there are threads that show you how to get rooted lollipop on your phone without tripping Knox which basically involves downgrading the kernel so you can root with towelroot, then using mobile Odin to flash lollipop and inject root in the process. It seems people are able to do this without issues. To this point, I do not think that anyone has found an exploit for lollipop.
The problem you will run into is that Xposed still does not run on lollipop so you cannot do much in the way of customization. Most of the G900F ROMs can run on the G900T so you might poke around in those threads to pick up more info.
Hope this helps a little.
If I or anybody on XDA helps you, please hit the "Thanks" button.
scwtech said:
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
Click to expand...
Click to collapse
System runtime is different. Art for lollipop compared to dalvik.. So it's not compatible as of now
Sent from my SM-G900T using XDA Free mobile app
This does not work with lollipop
---------- Post added at 07:30 PM ---------- Previous post was at 07:25 PM ----------
gspears said:
Right now there are threads that show you how to get rooted lollipop on your phone without tripping Knox which basically involves downgrading the kernel so you can root with towelroot, then using mobile Odin to flash lollipop and inject root in the process. It seems people are able to do this without issues. To this point, I do not think that anyone has found an exploit for lollipop.
The problem you will run into is that Xposed still does not run on lollipop so you cannot do much in the way of customization. Most of the G900F ROMs can run on the G900T so you might poke around in those threads to pick up more info.
Hope this helps a little.
If I or anybody on XDA helps you, please hit the "Thanks" button.
Click to expand...
Click to collapse
are you sure ? I have been able to downgrade. towelroot and flash lollipop and it boots but supersu does not work properly. root apps ask permission and supersu grants permission but the apps dont actually work
stncldtex said:
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
Click to expand...
Click to collapse
I don;t know where you heard that rooting won;'t trip Knox but I beleive you are wrong about that At least I know that Flashing cf auto root - flashing recovery or flashing custom roms all trip knox. If your phone can use Towel Root - that rooting process does not trip knox - but I am not sure if Towel Root works on Lollipop or on the S5 for that matter. (I may be wrong about Towel Root - I have never used that process so I can't say for sure)
Flashing a new rom via ODIN does not trip knox. It is just like getting an UPDATE from the carrier OTA.
BUT, If you are already rooted - you already have tripped knox - flashing Lollipop will remove root - but it will not do anything to change the fact that you tripped knox on your phone already.
As far as I know everything I have said is correct - based on what I have learned thru reading - flashing and using several different samsung phones -
finally, I see a lot of people paranoid as hell about tripping knox - and I can tell you without any hesitation that I have never had a problem getting service or replacements after rooting a phone - there have been a few times back when I first started flashing roms that I had issues with my phone and I took it in and got a replacement without any issue - once I broke my screen and got a replacement then too - both times I was rooted, running custom recovery - etc.
I hope this helps you
I used towel root on NE6. You can downgrade to that via Odin and not trip knox. As far as flashing 5.0 and losing root. I came from Alliance flash Twisted lollipop and kept root. Then used Odin to flash the bootloader and modem for OB1.
Do you still have Knox 0?
How did you flash lollipop?
So I can't tell if this question is moronic and totally obvious, or just not possible at the moment. I'm out of date with everything right now, as I'm just getting back into bricking my phones after taking a break. Months back, I bumped my G3 and am currently running TWRP with CM12 (latest nightly).
My question is, how do I gain root access? I've read about the various current methods, but I'm unable to find one that works. Is it just not possible at the moment on 5.0.2? Why I remember this being easier? Root level attaches to the ROM correct? am I making this up that I thought root was a part of CM flashing in the past? and wasn't in addition too?
jacksheadache said:
So I can't tell if this question is moronic and totally obvious, or just not possible at the moment. I'm out of date with everything right now, as I'm just getting back into bricking my phones after taking a break. Months back, I bumped my G3 and am currently running TWRP with CM12 (latest nightly).
My question is, how do I gain root access? I've read about the various current methods, but I'm unable to find one that works. Is it just not possible at the moment on 5.0.2? Why I remember this being easier? Root level attaches to the ROM correct? am I making this up that I thought root was a part of CM flashing in the past? and wasn't in addition too?
Click to expand...
Click to collapse
I'm not sure why it's not built in, but I do know if you flash the zip then root will come.
http://download.chainfire.eu/695/SuperSU/UPDATE-SuperSU-v2.45.zip
That was my first thought as well, and I had flashed SuperSU, but no root. I forget the version tried, so maybe that is the issue.
That worked. Now that I'm thinking of it, I may have just installed it locally and not flashed it previously.
jacksheadache said:
So I can't tell if this question is moronic and totally obvious, or just not possible at the moment. I'm out of date with everything right now, as I'm just getting back into bricking my phones after taking a break. Months back, I bumped my G3 and am currently running TWRP with CM12 (latest nightly).
My question is, how do I gain root access? I've read about the various current methods, but I'm unable to find one that works. Is it just not possible at the moment on 5.0.2? Why I remember this being easier? Root level attaches to the ROM correct? am I making this up that I thought root was a part of CM flashing in the past? and wasn't in addition too?
Click to expand...
Click to collapse
Check under development options. I thought CM disabled root as a stuck setting. It's on the user to enable it.
Sent from my VS985 4G
maximusmullivan said:
Check under development options. I thought CM disabled root as a stuck setting. It's on the user to enable it.
Sent from my VS985 4G
Click to expand...
Click to collapse
That's correct. It has to be enabled.
The built-in root has to do with permissions thing they added to CM. It's stupid because flashing a nightly wipes out SuperSU. I have CyanDelta set to flash SuperSU as well, and I believe I've been fine after that. However, if you flash a nightly and don't flash SuperSu also, you WILL loose your SuperSu settings, which was quite annoying for me...... I haven't bothered to test out the build in root permissions.