I'm interested in the new ROMs that are out but before I start playing I want to have my odin and root steps up to date. I notice that there have been several folks have had kingo fail and have had to use vroot. Is this the standard to use now? Just want to be sure I'm doing this correctly.
I'm on the current baseband and kernel, if that helps.
Thanks in advance.
Oh_wow said:
I'm interested in the new ROMs that are out but before I start playing I want to have my odin and root steps up to date. I notice that there have been several folks have had kingo fail and have had to use vroot. Is this the standard to use now? Just want to be sure I'm doing this correctly.
I'm on the current baseband and kernel, if that helps.
Thanks in advance.
Click to expand...
Click to collapse
I am one of the folks who had to use Vroot. I would try Kingo first and if that does not work then switch to Vroot.
oconnell84 said:
I am one of the folks who had to use Vroot. I would try Kingo first and if that does not work then switch to Vroot.
Click to expand...
Click to collapse
Great! Thanks for the quick reply!
I tried everything under the sun to get kingo to work and it never did. I went to vroot and it worked first try
Sent from my SM-N900V using Tapatalk
I used vroot about a week ago. Super easy, took maybe 30 seconds, and my knox WAS NOT tripped. I couldn't be happier.
Kevins89notch said:
I used vroot about a week ago. Super easy, took maybe 30 seconds, and my knox WAS NOT tripped. I couldn't be happier.
Click to expand...
Click to collapse
Are you using the chinese super user app?
Sent from my SM-N900V using Tapatalk 2
I used Vroot the other day to re root my phone after a reset and replaced the Chinese superuser with Chainfires supersu. You can install it either via Playstore or flash it in safestrap witch I prefer. Also be sure to uninstall whatever other Chinese app gets installed. I have no idea what it is because I can't read it. As a added precaution I also removed my sim card during root. As for Kingo It didn't work for me but there is activity on their twitter account.
recDNA said:
Are you using the chinese super user app?
Sent from my SM-N900V using Tapatalk 2
Click to expand...
Click to collapse
No, right away I installed the proper english version, and then deleted the chinese one.
Just tried Kingo and it's working again.
Misterxtc said:
I used Vroot the other day to re root my phone after a reset and replaced the Chinese superuser with Chainfires supersu. You can install it either via Playstore or flash it in safestrap witch I prefer. Also be sure to uninstall whatever other Chinese app gets installed. I have no idea what it is because I can't read it. As a added precaution I also removed my sim card during root. As for Kingo It didn't work for me but there is activity on their twitter account.
Click to expand...
Click to collapse
Removing the simm card during root sounds like a great idea.
Sent from my SM-N900V using Tapatalk 2
---------- Post added at 09:40 AM ---------- Previous post was at 09:38 AM ----------
Misterxtc said:
I used Vroot the other day to re root my phone after a reset and replaced the Chinese superuser with Chainfires supersu. You can install it either via Playstore or flash it in safestrap witch I prefer. Also be sure to uninstall whatever other Chinese app gets installed. I have no idea what it is because I can't read it. As a added precaution I also removed my sim card during root. As for Kingo It didn't work for me but there is activity on their twitter account.
Click to expand...
Click to collapse
I miss the good old days when there would be a separate thread for each rooting process with suggestions and questions. Now it's search here, search there, search everywhere!
Sent from my SM-N900V using Tapatalk 2
Turmin said:
Thank you.
Click to expand...
Click to collapse
Your welcome. It did take a few tries but it went. Be sure to update supersu when you finish, Kingo is out of date a couple of versions.
I tried 1000000 times last night and it did not work. I used Vroot and it worked great. But remember to do I factory reset to get rid of all the bad crap it loads.
Sent from my SM-N900P using Tapatalk
NissanNick said:
I tried 1000000 times last night and it did not work. I used Vroot and it worked great. But remember to do I factory reset to get rid of all the bad crap it loads.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
They must have just got Kingo working because I used it twice today. The second time worked on the first try. I tried it a second time after a full Oden reset just to make sure. Had some extra time today to play around.
Misterxtc said:
They must have just got Kingo working because I used it twice today. The second time worked on the first try. I tried it a second time after a full Oden reset just to make sure. Had some extra time today to play around.
Click to expand...
Click to collapse
What firmware are you on? MJE?
Sent from my SM-N900V using Tapatalk
Yes, MJE.
Misterxtc said:
Yes, MJE.
Click to expand...
Click to collapse
Worked for me too with MJE. Used USB 3.0 cable in USB 3.0 mode MTP. Prior to that failed in ODIN mode and in MTP mode without USB 3.0. But may be just random luck. Now have Supersu app.
Questions:
1. Should I use that Supersu or change. Looks like same old Supersu, but the version with yellow superman shield and red # sign.
2. Also, it asks if I want to disable Knox. Should I do that? Does that risk tripping know counter?
Sent from my SM-N900V using Tapatalk
yearn2burn said:
Worked for me too with MJE. Used USB 3.0 cable in USB 3.0 mode MTP. Prior to that failed in ODIN mode and in MTP mode without USB 3.0. But may be just random luck. Now have Supersu app.
Questions:
1. Should I use that Supersu or change. Looks like same old Supersu, but the version with yellow superman shield and red # sign.
2. Also, it asks if I want to disable Knox. Should I do that? Does that risk tripping know counter?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Keep supersu but update it to the current v1.93 either by Play Store or flashing in safestrap and yes disable Knox it will not trip the counter. Enjoy.
Yes K works even though it says it fails. I posted my experience back on Feb 3 in another similar thread or look via my profile. In short it will say that it failed but su app shows up and use a root checker to verify. Removal of sd card and pulling and replacing the sim card before root might help. Also watch you phone for a security permission to add an app. I sat an extra five minutes before realizing it.
danthepunman said:
Yes K works even though it says it fails. I posted my experience back on Feb 3 in another similar thread In short it will say that it failed but su app shows up and use a root checker to verify.
Click to expand...
Click to collapse
For me it realized it succeeded.
Sent from my SM-N900V using Tapatalk
Related
I just tried getting root access via this guide using Odin, but although I've already updated the firmware first, it just doesn't take. It installs the superSU app, but not the binary it seems. Any idea where I can get it from? I also tried superuser instead, which allows me to get an up to date binary, but when it then tries to install the binary it fails.
Here's the guide I followed:
http://m.ibtimes.co.uk/galaxys4-gti9505-official-android422-xxuadmn-jellybean-firmware-464478.html
Any ideas?
XXUAMDM Root not possible?
Hi,
have done the same, tried to root the I9505 XXUAMDM (European LTE model) - there was no SU installed.
Therefore I installed the SuperSU from the market and checked, but it says that the SU Binaries are missing...
So what went wrong with rooting? Any suggestions
BTW: After the start of Titanium Backup the window asking about root for the app appeared.
Now starting Super SU I can see Titanium in the list, but short after start the mentioned "SU-Binary missing" window appears...
jochenthomas said:
Hi,
have done the same, tried to root the I9505 XXUAMDM (European LTE model) - there was no SU installed.
Therefore I installed the SuperSU from the market and checked, but it says that the SU Binaries are missing...
So what went wrong with rooting? Any suggestions
Click to expand...
Click to collapse
Exactly the same as me, the update went fine, the rooting seemed to go fine too, but the binary is supposedly missing.
Just been pointed to this thread, which works a treat:
http://forum.xda-developers.com/showthread.php?t=2255190&nocache=1
It seems the method we used isn't compatible with the MDM and MDN firmware updates, so need to use a modified version of CF auto root instead. In that thread it also shows you how to reset the flash counter too! Result!
StuartTheFish said:
I just tried getting root access via this guide using Odin, but although I've already updated the firmware first, it just doesn't take. It installs the superSU app, but not the binary it seems. Any idea where I can get it from? I also tried superuser instead, which allows me to get an up to date binary, but when it then tries to install the binary it fails.
Here's the guide I followed:
http://m.ibtimes.co.uk/galaxys4-gti9505-official-android422-xxuadmn-jellybean-firmware-464478.html
Click to expand...
Click to collapse
I know your sorted ow but out of interest before were you using steps outlined here when it didn't work on mdm
http://androidjinn.com/root-xxuamdm-android-4-2-2-on-galaxy-s4-i9505-official-firmware.html/2
Sent from my GT-I9505 using xda app-developers app
topcat07 said:
I know your sorted ow but out of interest before were you using steps outlined here when it didn't work on mdm
http://androidjinn.com/root-xxuamdm-android-4-2-2-on-galaxy-s4-i9505-official-firmware.html/2
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Different guide, but same method. We simply needed a modified file t work on the newer firmware.
StuartTheFish said:
Different guide, but same method. We simply needed a modified file t work on the newer firmware.
Click to expand...
Click to collapse
Strange someone has got it working with normal file
Sent from my GT-I9505 using xda app-developers app
topcat07 said:
Strange someone has got it working with normal file
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Pass, don't know! All I do know is the regular cf auto root didn't work for me on this firmware, but the modified one did.
StuartTheFish said:
Just been pointed to this thread, which works a treat:
http://forum.xda-developers.com/showthread.php?t=2255190&nocache=1
It seems the method we used isn't compatible with the MDM and MDN firmware updates, so need to use a modified version of CF auto root instead. In that thread it also shows you how to reset the flash counter too! Result!
Click to expand...
Click to collapse
OMFG I have googled and torn my hair our for hours and hours as I just could not get root on my MDM S4 using the methods detailed on this site, this modified file rooted it straight away with no problems. It REALLY needs to be shouted a bit louder lol !
Thanks all.
this doesnt work for i9500
this kernel does not root i9500.
anyway i have a different problem and its about bluetooth. is this the proper place or should i search elsewhere?
No, there's a different method to rooting for a gt19500.
Thanks
For those who have taken the MJ7 update and realized that you can't regain root. Kingo is working on a solution. Verizon likes to lock their loaders so it takes a little time to break them. I had to take my note to a Best Buy store about an hour from where I live to have them reset my phone from what is being labeled a Softbrick. If anyone knows a way to root the SM-900V with MJ7 please let me know.
Thanks,
GoNavyMike
I took the update a week ago and just rooted with kingo yesterday..all I did was follow instructions withing the app and was rooted minutes later . ... Installed safe strap with beans on slot 2..all is well except I can't get the custom logo to go away from the boot up screen but I don't really care
Sent from my SM-N900V using Tapatalk
I have no idea why people claim kingo doesn't work. It works fine, I and many others have used it on newest update without issue. Also, this isn't development.
Sent from my SM-N900V using xda app-developers app
custom logo
gcforreal said:
I took the update a week ago and just rooted with kingo yesterday..all I did was follow instructions withing the app and was rooted minutes later . ... Installed safe strap with beans on slot 2..all is well except I can't get the custom logo to go away from the boot up screen but I don't really care
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
If you run Triangle Away app, from App Store, it will get rid of custom lock logo on boot up screen
GoNavyMike said:
For those who have taken the MJ7 update and realized that you can't regain root. Kingo is working on a solution. Verizon likes to lock their loaders so it takes a little time to break them. I had to take my note to a Best Buy store about an hour from where I live to have them reset my phone from what is being labeled a Softbrick. If anyone knows a way to root the SM-900V with MJ7 please let me know.
Thanks,
GoNavyMike
Click to expand...
Click to collapse
The Kingo does work for the Verizon Note 3. I literally just did it. At first, it kept saying not supported, but I tried it again with my screen timeout off and I saw that when my phone was connected to Kingo, something popped up warning me something was trying to exploit my phone, click on the box and hit install. Then not long after that your phone will reboot and grant permission stuff will come up. You can either do it this way, or under security uncheck verify apps located under unknown sources.
So on the kingo screen,when selecting the OS mine only goes up to 4.2.2. I am obviously running 4.3 on the note 3. Do I pull the trigger? Or am I missing an update?
Sent from my SM-N900V using Tapatalk
mtnbst said:
So on the kingo screen,when selecting the OS mine only goes up to 4.2.2. I am obviously running 4.3 on the note 3. Do I pull the trigger? Or am I missing an update?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Worked for me and mine said the same thing. "4.2.2" Took me a couple minutes or so and all is good!
I have been hung up on "waiting for device" (after fetching scripts) for about 10 minutes now. Wondering when I should pull the plug. ...
It's a no go... Maybe because it's VZ?
Sent from my SM-N900V using Tapatalk
Kingo works for mj7, if you get hung up on waiting for device, close the kingo app restart computer, open kingo, plug phone into a different usb port.
Sent from my SM-N900V using Xparent Green Tapatalk 2
YES guys, you can root your phone VIA Kingo even if you updated to the newer firmware. My scenario, got my N3 bone stock, rooted it on MJ9 via kingo and worked. Applied OTA update to version to MJ7 and lost root. Used kingo again and gained root. Works totally fine and SS works fine as well.
Still nothing. .I am running win 8 through VM firmware. I wonder if that's my prob. I get all the way to the last step and it hangs. I rooted my Galaxy nexus with this virtual win machine. I might have to borrow a windows laptop
Sent from my SM-N900V using Tapatalk
Kingo
Does anyone have a link to Kingo. I can't get mine to go in Odin, I click to import the file, hit start, and it doesn't do anything. Does the De la Vega file have to be renamed? I'm usually pretty good at getting these things rooted, this seems to be dealing me fits. I NEED ROOT lol
Other issue is that 7zip will not extract the de la Vega file, says it can't open as a archive
Why is this thread so long? Kingo works with MJ7. Nuff said. If the OP would of read the Verizon Note 3 threads for 10-15 minutes he/she would of found this out.
It works for most. I am not most
Sent from my SM-N900V using Tapatalk
mtnbst said:
Still nothing. .I am running win 8 through VM firmware. I wonder if that's my prob. I get all the way to the last step and it hangs. I rooted my Galaxy nexus with this virtual win machine. I might have to borrow a windows laptop
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
VM could definitely be part of your problem, especially if you do not have Internet access through it. USB connections can sometimes be flaky as well.
musicman625 said:
Does anyone have a link to Kingo. I can't get mine to go in Odin, I click to import the file, hit start, and it doesn't do anything. Does the De la Vega file have to be renamed? I'm usually pretty good at getting these things rooted, this seems to be dealing me fits. I NEED ROOT lol
Other issue is that 7zip will not extract the de la Vega file, says it can't open as a archive
Click to expand...
Click to collapse
RDLV does not work on MJ7, unless they have released an update.
http://lmgtfy.com/?q=kingo+root
Sent from my SM-N900V using Tapatalk
I have Internet through it. .. But the USB connection is extremely flakey. I wonder if I try 100 times. .. It's bound to take
Edit: Using the original USB cable for my galaxy nexus gets me 95% through the process vs 50% through the process with the Note 3 cable.
Siiiiiigh,
perhaps my nexus 7 cable will be the ticket...
This will be my first android device that does not have root privileges. $#%@
Sent from my SM-N900V using Tapatalk
The kingo app will do it, make take a few tries and you'll probably have to do it from an actual Windows PC, but it should work. I'd probably try to use a USB 2.0 port rather than a 3.0, if possible.
Sent from my SM-N900V using Tapatalk
Thanks, I won't have access to a PC for a few weeks. I will patiently wait
Sent from my SM-N900V using Tapatalk
Kingo does work. I tried literally 40 times no luck on new ota. Battery pull took out sd card rebooted. First try rooted.
Sent from my SM-N900V using Tapatalk
Ahhh, so there is hope! As soon as I get home I'm trying. Fingers crossed
Nope, tried all that. .. Nothing
Edit: I think Im on at least my 85th attempt...battery pulls, SD pulls computer reboots, different usb cables (note 3 cable is the least effective) Im even alternating USB inputs. anything I'm leaving out?
Sent from my SM-N900V using Tapatalk
I was on MJE rooted and safestrapped. No problems. I put SuperSu in survival mode, took the OTA...knowing full well the bootloader issue (I had played with NC2 with NC4 modem for a while and had tons of issues)...I am still rooted on NC4 no problems doing anything rootlike...except Safestrap 3.72 will not set the boot up to give me the choice to recover or continue no matter what. So I even tried Safestrap 3.73...when I install the recovery...3.73 says it completed and shows "installed" But still no choice at boot time.
Has anyone gotten this to work?
Sent from my Note 3 via Tapatalk
This is like playing with fire lol
Root is to precious to me to mess around like this. Good luck tho!
Inkedadrenaline said:
This is like playing with fire lol
Root is to precious to me to mess around like this. Good luck tho!
Click to expand...
Click to collapse
Yea...I am for sure still rooted, just not safestrapped, I am still playing with it and was just wondering if anyone had already done so.
Sent from my Note 3 via Tapatalk
donc113 said:
Yea...I am for sure still rooted, just not safestrapped, I am still playing with it and was just wondering if anyone had already done so.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
That's pretty cool. I respect you for taking the plunge. Def have more testicular fortitude than me
donc113 said:
I was on MJE rooted and safestrapped. No problems. I put SuperSu in survival mode, took the OTA...knowing full well the bootloader issue (I had played with NC2 with NC4 modem for a while and had tons of issues)...I am still rooted on NC4 no problems doing anything rootlike...except Safestrap 3.72 will not set the boot up to give me the choice to recover or continue no matter what. So I even tried Safestrap 3.73...when I install the recovery...3.73 says it completed and shows "installed" But still no choice at boot time.
Has anyone gotten this to work?
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
How did you get SS 3.73? It's not even listed in Hash's thread...
LeftyGR said:
How did you get SS 3.73? It's not even listed in Hash's thread...
Click to expand...
Click to collapse
Google search...it was actually for a different phone....but what the heck...tried it anyway.
Sent from my Note 3 via Tapatalk
Please see the mini guide I just posted at http://forum.xda-developers.com/showthread.php?t=2762999 for information on how to go from a STOCK MJE non rooted phone to one with KitKat 4.4.2 rooted (odex or deodex). As well as move to a custom non stock rom.
donc113 said:
I was on MJE rooted and safestrapped. No problems. I put SuperSu in survival mode, took the OTA...knowing full well the bootloader issue (I had played with NC2 with NC4 modem for a while and had tons of issues)...I am still rooted on NC4 no problems doing anything rootlike...except Safestrap 3.72 will not set the boot up to give me the choice to recover or continue no matter what. So I even tried Safestrap 3.73...when I install the recovery...3.73 says it completed and shows "installed" But still no choice at boot time.
Has anyone gotten this to work?
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
U need to have busybox installed for kitkat safestrap
donc113 said:
Google search...it was actually for a different phone....but what the heck...tried it anyway.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Why on earth would you try one that was deved for a different phone?
SirBindy said:
Why on earth would you try one that was deved for a different phone?
Click to expand...
Click to collapse
Because I was thinking I would try a reflash with Odin if needed. I've been "trying stuff" with UNIX based servers since the early 80's. I have no problem reflashing a phone.
Sent from my Note 3 via Tapatalk
RomsWell said:
U need to have busybox installed for kitkat safestrap
Click to expand...
Click to collapse
BusyBox is installed, and active, and SafeStrap checks for it and Safestrap says it's installed...but even hitting the Reboot to Recovery button does a "normal" reboot and I don't get the recover/continue option.
Sent from my Note 3 via Tapatalk
donc113 said:
Yea...I am for sure still rooted, just not safestrapped, I am still playing with it and was just wondering if anyone had already done so.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
After reading your post I went ahead and tried to take the NC4 OWA with supersu in survival mode. It Worked! I was on stock mje, rooted with kingo and had a modded framework for tethering. I restored the backup of my stock framework file, then unfroze all of my apps. I put supersu in survival mode, disabled superuser, and turned default access to deny. I then enabled the install of the OWA and after the reboot I enabled supersu and just like that I still had root. So far no issues.
As far as safestrap goes, I didn't have safestrap before but I may try to install it to see if it works now. I'll let you know.
donc113 said:
BusyBox is installed, and active, and SafeStrap checks for it and Safestrap says it's installed...but even hitting the Reboot to Recovery button does a "normal" reboot and I don't get the recover/continue option.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Third time is a charm I guess. I uninstalled the recovery, rebooted, reinstalled the recovery, hit the reboot to recovery and got to Safestrap just fine. And it now gives me the choice during reboot.
Sent from my Note 3 via Tapatalk
RicksROMbuild8/NC4
Im on "RicksROMbuild8" with NC4,root and safestrap still.
Hi all, thank you for reading this. I'm sure I'm not the only one here that has this problem;
I've got a Samsung Galaxy S5 SM-G900H and I've tried countless times to root it. It rooted halfway. How? Well, being a n00b in a developer's forum is really tough but I'll try to exemplify:
So I succesfully rooted my phone via Philz CWM to later install Chainfire's Root App from Google Play store. But I can't run "Game Killer" without it posting "Root access needed" when I THOUGHT I rooted my phone. So I downloaded Root Checker Pro and then I kinda understood why.
Has this happened to anyone before? I've never had this rooting problem (used to own a Galaxy S4 before this one and a Samsung S2 before that one)..
PLEASE HELP!
Oh, and I can't use CF-Auto-Root method because it get's stuck at CACHE and I can't make it past there (EVEN if I change the Odin versions). My guess is that it's got something to do with Philz being there. I dunno..
HOW CAN I COMPLETELY ROOT MY BELOVED S5 G900H?
Thank you in advance!
Bump?
Sent from my SM-G900H using XDA Premium 4 mobile app
RBucci said:
I can't run "Game Killer" without it posting "Root access needed" when I THOUGHT I rooted my phone. So I downloaded Root Checker Pro and then I kinda understood why.
Has this happened to anyone before?
Click to expand...
Click to collapse
Yes and yes. Incomplete roots are a common issue and happen to many people. It can happen because you missed a step, because the rooting method is out of date or perhaps some app is interfering. You simply need to root again.
It would probably suffice to update SuperSU and update or install busybox. But if you prefer, uninstall SuperSU, then run your root again. If you run into difficulties, then look for advice on how to disable Knox, use one of the newer rooting methods or flash a stock firmware image and start from scratch.
RBucci said:
Oh, and I can't use CF-Auto-Root method because it get's stuck at CACHE and I can't make it past there (EVEN if I change the Odin versions). My guess is that it's got something to do with Philz being there. I dunno..
Click to expand...
Click to collapse
2 ways:
1) This has been noted before. If you get stuck on the cache during the flash process, you should remove battery + sim + sd and re insert them and flash again.
2) Not being able to flash with Philz usually is caused because of the recovery version. Since you have G900H it could very be that problem, so if you didn't try my advice from above, I would try to use a different recovery (CWM / TWRP).
Thank you YMatrix for taking the time to respond. I will reply as soon as I'm able to do so and post a reply with the steps for the successful alternatives.
Sent from my SM-G900H using XDA Premium 4 mobile app
And fffft for the quick response! Thank you both. I will post feedback ASAP.
Sent from my SM-G900H using XDA Premium 4 mobile app
Nope. Did not work. I made a full wipe, formatted system, formatted data, formatted media, formatted cache, made a full full wipe of everything, flashed original unbranded firmware and then followed the CF-AUTOROOT method to encounter the same fail...
Sent from my SM-G900H using XDA Premium 4 mobile app
Is there a manual way that I can copy the su file into system and set the setuid permissions?
I'm doing my best and tried everything and nothing and no way seems to grant me core root like it's supposed to..
Sent from my SM-G900H using XDA Premium 4 mobile app
Just an idea,, why not unroot then use towel root? I didn't need to go to all that trouble to root my device. Just a couple of clicks with towelroot app.
Because when I attempt to root with Towelroot it says that my device is not currently supported..
I've tried almost every combination/steps.. It gets rooted but it doesn't root the core.. I don't know how to put it in words. N00b disadvantages..
Sent from my SM-G900H using XDA Premium 4 mobile app
Hmm in that case I would post a message on the xda-dev forum. Oh wait
Sorry I'm not much help here. I'm not sure why my Australian S5 is supported and yours is not (towelroot).
Well, I'm not sure either. One very strange thing as well is that in Terminal Emulator, when I type "whoami" it says unknown.
I still can't access full root.
I do, however, have SuperSU installed and working properly but it's like a fake root or something..
Sent from my SM-G900H using XDA Premium 4 mobile app
The result is still the same.. Help? Please?
Well RBucci, i'm with the exact same problem. thought semi-root, happenned to me before, with the S4 and S3, i ve simply fixed it, re rooting with another version of CF-AUTOROOT.
But now, there's no other version of it, for S5. i have the same varian (G900H) as you. CF-ROOT get stuck after writing Cache.img, and throwing "Write error".
please, let me know if you find a work around for it, i'll be doing the same.
i guess we have the same phone, i'm from argentina, probably we have the same variant of "H" version..
---------- Post added at 04:11 PM ---------- Previous post was at 04:06 PM ----------
Question, have you tried downloading busybox from market and trying to install it?
does it erease itself after rebooting?
Finally working full root!
as you asked here is what i've done.
put a sim card in the phone, (never put a simcard in the phone before), enter developers options, marked USB debbuging, unmarked verify potencial risky apps pushed by ADB (sorry if the translation isnt exact i have the phone in spanish) is right below USB Debuggin Option.
-turn off phone
-Remove SIMCARD
-Enter Download mode
-Flash via Odin 3.09 Chainfire CF-AUTOROOT for G900H
-and enjoy.
try it mate. it worked for me
here some screenshots, one checking root, another one checking busybox.
pelpa87 said:
Well RBucci, i'm with the exact same problem. thought semi-root, happenned to me before, with the S4 and S3, i ve simply fixed it, re rooting with another version of CF-AUTOROOT.
But now, there's no other version of it, for S5. i have the same varian (G900H) as you. CF-ROOT get stuck after writing Cache.img, and throwing "Write error".
please, let me know if you find a work around for it, i'll be doing the same.
i guess we have the same phone, i'm from argentina, probably we have the same variant of "H" version..
---------- Post added at 04:11 PM ---------- Previous post was at 04:06 PM ----------
Question, have you tried downloading busybox from market and trying to install it?
does it erease itself after rebooting?
Click to expand...
Click to collapse
pelpa87 said:
Finally working full root!
as you asked here is what i've done.
put a sim card in the phone, (never put a simcard in the phone before), enter developers options, marked USB debbuging, unmarked verify potencial risky apps pushed by ADB (sorry if the translation isnt exact i have the phone in spanish) is right below USB Debuggin Option.
-turn off phone
-Remove SIMCARD
-Enter Download mode
-Flash via Odin 3.09 Chainfire CF-AUTOROOT for G900H
-and enjoy.
try it mate. it worked for me
Click to expand...
Click to collapse
pelpa87 said:
here some screenshots, one checking root, another one checking busybox.
Click to expand...
Click to collapse
You're the man!
I'm going to delete everything (FULL WIPE) and reinstall stock firmware to test it from scratch. I'll let you know how it goes.
Hopefully I'll be posting back from a fully rooted phone.
Thanks, bro!
I had the same issue, got stuch on cache, so i turned it off, removed the battery, took the sim AND the sd card away, and tried the cf-autoroot again, it worked, have full root on the s5
OMG
I've found the problem !!!
Hi everyone
You have to use CF-Root with Odin 1.85 ! It works perfectly :laugh:
Samsung SM-G900H
A Panda French.
But, what about Towelroot?
http://forum.xda-developers.com/showthread.php?t=2783157
CF-Root will trip the Knox to 0x01!
Be the way if the knox is trip to 0x01
can I still go back to rom stock from samsung and still get OTA?
what about if i chace to ASOP non-stock rom can I still get back and keep the OTA?
The knox dons't block me to get OTA or flash back rom stock?
Thank you!
So, I just found out where the link was hiding. Working great so far.
How about if you click on the big (Greek) lambda symbol?
https://towelroot.com/tr.apk
Sent from my SM-N900V using XDA Free mobile app
How do you unroot the towel root
monkeyjjk said:
Sent from my SM-N900V using XDA Free mobile app
How do you unroot the towel root
Click to expand...
Click to collapse
You have to go to SuperSu and unroot from there.
Setttings > Full Unroot > Continue.
Wait for it to prompt you to reboot and you're done
SuperSU issue
So... the root worked fine. I checked with Root Checker, and it's all good in the 'hood. HOWEVER, when I installed SuperSU, it tells me that the "Installation Failed"... second "however", though, is that when I run an app requiring elevated permissions, SuperSU pops up just like it should, and everything works. Very curious.
Foetus said:
So... the root worked fine. I checked with Root Checker, and it's all good in the 'hood. HOWEVER, when I installed SuperSU, it tells me that the "Installation Failed"... second "however", though, is that when I run an app requiring elevated permissions, SuperSU pops up just like it should, and everything works. Very curious.
Click to expand...
Click to collapse
It's a known issue, as long as you have SuperSU popping up asking for permissions and your root checker shows green, I wouldn't worry. It happened to the wife's S5, and that was 3 months ago, and she's still rooted.
You could also try and re-dl the latest, I believe 2.01, in the playstore and see if that helps if you are that worried about it.
_don't forget to hit thanks to anyone that helps ya out_
Does Towelroot trigger Knox and cause a CUSTOM notice when booting?
mkuhl2000 said:
Does Towelroot trigger Knox and cause a CUSTOM notice when booting?
Click to expand...
Click to collapse
Does not trigger know, but may cause custom notice.
LeftyGR said:
Does not trigger know, but may cause custom notice.
Click to expand...
Click to collapse
Caused custom notice on mine.
Question: can I uninstall after rooting and keep root? Google keeps warning me about it.
oatlord said:
Caused custom notice on mine.
Question: can I uninstall after rooting and keep root? Google keeps warning me about it.
Click to expand...
Click to collapse
Yes. Once rooted, the app doesn't have to be installed.