Related
Hey there everyone,
Just picked up my first smartphone, and obviously the first thing I had to do with it is install a different rom. I was able to get the one from here:
http://forum.xda-developers.com/showthread.php?t=2349077
To install just fine on my Canada SGH-I337m phone. It says one of the features of it is root privileges, and I can see SuperSU installed on the phone, but any app that actually tries to access root functions seem to just get turned away. I've tried both OpenVPN Installer and AdAway and OpenVPN is the only app that gives any helpful logs.
When I try to install it, it just fails and in the logs it's saying that /system/ is still read only even after being granted privileges by SuperSU.
Just wondering if I'm making a mistake or if I needed to do something on the phone before the root will work. I've already tried reinstalling SuperSU to no avail, and using the Motochopper root app ended up with a boot loop after it finished.
Open SuperSU and update binaries see if that doesn't cure your issue
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Yep, one of the first things I did when it didn't work was update SuperSU where it has you download/install it again from the store, which put me on version 1.65 which I believe is the latest version.
For a Canadian phone you will need to use CF-Auto root. However, trying to root a phone that is already supposed to be rooted can cause problems. I suggest you go to the CF Auto Root thread in the Original Development section and read the thread to see if any additional information or tips are given for your situation. Also, depending on the ROM you installed, you might need to install a Kernel specific for your phone to get full functionality. Again, this can be determines by reading the thread from where you got the ROM from. Good luck.
I've been reading the forum for few hours Friday night and yesterday and found lots of help but and videos but not on how to run this Universal De La Vega script which is where I think I'mscewing it up. I downloaded the N900VVRUBMJE_N900VVZWMJE_N900VVRUBMJE_HOME.tar.md5 from SamMobile. I ran the Universal De La Vega script using Cygwin. After a couple of attempts I figured out to move everything to the c:/ root to reduce typing errors. It produced a file with a Vega in the name as the instructions say, but I not sure I ran the script correctly. More on that in a second. I flashed the NOTE3 with the file using ODin and got a soft brick. I then flashed it with the HOME_tar.md5 I got from SamMobile and the phone rebooted and worked ok, but I'm back to stock and not yet rooted. Happy I downloaded the correct stock file and flashing it save my xss, but I still need to root.
Can I please get a little help on how the De La Vega script is executed.
These are the instructions:
Usage: ./URDLV.sh [full|csc] [stock firmware file path]
Example: ./URDLV.sh csc F:\N900PVPUBMI3_N900PSPTBMI3_SPR.tar.md5
Example: ./URDLV.sh full F:\OneClick_I537UCUBMI2.exe
full = AP and CSC (Creates a single file with both AP and CSC, no bootloaders, modems, etc.)
csc = CSC only
[stock firmware file path] - needs to be the full file path!
Drag and drop the file into the terminal window to get the full path.
I'm having trouble undertanding the second line entry. the ./URDLV.sh full ... where is the OneClick_I537?UCBM12.exe file? When I ran it I just ran the URDLV..sh csc and the URDLV.sh full both on the same N900VVRUBMJE_N900VVZWMJE_N900VVRUBMJE_HOME.tar.md5 from SamMobile. Do I only run one of the two lines on the script? And then set up Odin depending on one or two files?
I trust that this makes sense to someone, I am not Lenix command line savvy...
Thanks in advance!
I rooted my note 3 verizon via Kingo.
Was easy and quick.
Look in the Root via Kingo forum if you want to go a different route~
OneClick_I537?UCBM12.exe ="equal to" grab and drop your N900VVRUBMJE_N900VVZWMJE_N900VVRUBMJE_HOME.tar.md5
but i try it 10+ time not working for me neither....i have the OEM MJE not OTA
tigersfa8 said:
I rooted my note 3 verizon via Kingo.
Was easy and quick.
Look in the Root via Kingo forum if you want to go a different route~
Click to expand...
Click to collapse
Just looked at Kingo looks easy but I'd rather stay with sda if there's a solution. These guys are very trust worthy!
I think I figured it out. Am going to try running the script with [full] only and it generates a tar.md5 and I'll try it. But that's tomorrow, now it's SuperBowl. Thanks all.
Is Kingo chinese spyware?
I too need root help
I just got the Verizon Note 3 today and it came out of the box with build MJE on it. I tried Kingo's app to root it and it said unsupported after it tried to root it. I cannot find a method of rooting the device with this build number. I am hesitant about moving everything to the new phone just to have to wipe it again.
wizard62777 said:
I just got the Verizon Note 3 today and it came out of the box with build MJE on it. I tried Kingo's app to root it and it said unsupported after it tried to root it. I cannot find a method of rooting the device with this build number. I am hesitant about moving everything to the new phone just to have to wipe it again.
Click to expand...
Click to collapse
use "vroot"
remember disable all firewall and anti virus.
i was rooting my phone for 5 days now. finally got it rooted.
I follow all the instructions for vroot, but when I install SuperSU it tries to disable KNOX but it says failed, and root checker says I still don't have root access.
wizard62777 said:
I follow all the instructions for vroot, but when I install SuperSU it tries to disable KNOX but it says failed, and root checker says I still don't have root access.
Click to expand...
Click to collapse
try run vroot as administrator. i happened to me yesterday.
I finally got vroot to give me root access on my phone, but now I cant get SuperSU to install and update and get rid of the chinese root.
WOW
I posted the original post asking for help rooting using dela vega and still no help. Everyone says use kingo and that's apparently not working now either. So I'm going to go read up on vroot as many have suggested.
This is not the type of help that I got the last time I posted for help on my S2.
ADMIN you can close this thread it went no where.
ansel1 said:
I posted the original post asking for help rooting using dela vega and still no help. Everyone says use kingo and that's apparently not working now either. So I'm going to go read up on vroot as many have suggested.
This is not the type of help that I got the last time I posted for help on my S2.
ADMIN you can close this thread it went no where.
Click to expand...
Click to collapse
de la vega won't work with mje - there are a slew of posts stating such.
Sent from my SM-N900V using XDA Premium 4 mobile app
Reilly1812 said:
de la vega won't work with mje - there are a slew of posts stating such.
Click to expand...
Click to collapse
Correct. De la vega no longer works on the latest Verizon builds. Samsung patched the exploit up. Kingo has been having very slow website and server problems, so people have not been able to root using that either. The only one that's working correctly at the moment is vRoot.
Once you root with vRoot, do a search for chainfire's SU 1.00 apk and flash that in SafeStrap. That will get rid of the Chinese SU app. Then you can also uninstall the other Chinese app that gets installed.
-BoneZ- said:
Correct. De la vega no longer works on the latest Verizon builds. Samsung patched the exploit up. Kingo has been having very slow website and server problems, so people have not been able to root using that either. The only one that's working correctly at the moment is vRoot.
Once you root with vRoot, do a search for chainfire's SU 1.00 apk and flash that in SafeStrap. That will get rid of the Chinese SU app. Then you can also uninstall the other Chinese app that gets installed.
Click to expand...
Click to collapse
Just bought a VZW Note 3 (N 9000V UD) and I could swear it came with MJE but I still got an OTA and since I was reading that Kingo worked with MJE, I took it. Kingo didn't work before as far as I could tell, but I had only tried a few times. After, I can say definitively that Kingo is useless.
Tried De La Vega next and can also confirm that it's useless on OTA MJE. Got an error during ODIN upload and was soft-bricked at that point. ODIN'd back to OEM MJE, tried De la Vega again and got the same result; soft-brick.
As of 20140209, I cannot find a way to root a new VZW Note 3 but I'm still looking because as nice as this hardware is, I couldn't care less if I can't even restore my apps/data (backed up with TB).
I have looked at vroot, but since it's not in English, I'm not sure how far I'd get and I'm nervous as hell relying on something that's such a clear security risk.
rainabba said:
I have looked at vroot, but since it's not in English, I'm not sure how far I'd get and I'm nervous as hell relying on something that's such a clear security risk.
Click to expand...
Click to collapse
The vRoot software for your PC is in English. Only the SU app is in Chinese, but you need to overwrite that SU app with a secure one like chainefire's anyway.
The security risk is minimal if you have good security software on your PC and if you replace the Chinese SU with a more secure one. And the security risk is virtually eliminated if you install Safestrap and then use a different ROM.
-BoneZ- said:
The vRoot software for your PC is in English. Only the SU app is in Chinese, but you need to overwrite that SU app with a secure one like chainefire's anyway.
The security risk is minimal if you have good security software on your PC and if you replace the Chinese SU with a more secure one. And the security risk is virtually eliminated if you install Safestrap and then use a different ROM.
Click to expand...
Click to collapse
I did get rooted after some 3 hours of sifting through old posts and figuring out how to get through the Chinese interface of vroot but I saw some warnings while installing that I don't like (mtkcamera) and so far, I've had to re-root at least 6 times while trying to get SuperSU in place.
All the directions indicate that I need to launch SuperSU, grant it permissions, then continue but when I open it, I immediately get the "outdate binary" prompt and no superuser prompt so I can't move forward with this one. I'm going to try an older version of SuperSU in the hopes that it will be less agressive with the binary update and perhaps give me a shot at authorizing it.
UPDATE:
Thanks to cubarican84, I used the following SIMPLE solution to clean up the chinese superuser mess: http://www.w0lfdroid.com/2013/11/How-to-Remove-Replace-VRoot-Chinese-superuser-with-SuperSU.html?m=1
Reilly1812 said:
de la vega won't work with mje - there are a slew of posts stating such.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought it worked but tripped knox.
Sent from my SM-N900V using Tapatalk 2
recDNA said:
I thought it worked but tripped knox.
Sent from my SM-N900V using Tapatalk 2
Click to expand...
Click to collapse
With MJE just soft bricks. Unless there's a trick like repartitioning or something. But nobody has chimed in on that thread despite numerous help requests.
Just got Kingo working again tonight. May have to try a few times. I succeeded using USB 3 cable in MTP USB 3.0 mode.
Sent from my SM-N900V using Tapatalk
Were you able to update supersu in the playstore?
Sent from my SM-N900V using Tapatalk 2
Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?
This is my problem too. Hopefully there is a way.
Sent from my LG-D800 using xda app-developers app
Maybe doing a factory reset from stock recovery?
Sent from my LG-D805 using xda app-developers app
rohan611 said:
Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?
Click to expand...
Click to collapse
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help
antawnm26 said:
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help
Click to expand...
Click to collapse
nope. as i said in the OP< i have a stock recovery.
rohan611 said:
nope. as i said in the OP< i have a stock recovery.
Click to expand...
Click to collapse
then try root keeper it will disable root but back up root path and reinstate it once the update is done
antawnm26 said:
then try root keeper it will disable root but back up root path and reinstate it once the update is done
Click to expand...
Click to collapse
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.
rohan611 said:
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.
Click to expand...
Click to collapse
lol..yeah i read each statement in your OP just wanted to get to that last part of you saying your going back to stock and going from there, because thats your next option....
Let us know if you went back to stock then did the update and it worked.
I've read that some people kept root through their OTA. Why are some people able to update and others aren't. I've been reading up on this for the VZW update whenever that happens. I hope I haven't kept all this bloatware on my phone for no reason!!
Sent from my VS980 4G using Tapatalk
hinduboy74 said:
Let us know if you went back to stock then did the update and it worked.
Click to expand...
Click to collapse
I reverted back to stock using the instructions in the Stickied post. I was then able to update to D80010o. I had to call to request a rep to push out the D80010q update again though. They're calling it a "security update" so you should use that phrase when talking to the rep so that they don't get confused and think that you're just requesting that they push out the KitKat update.
Once I got the D80010q update, the KitKat update was available and I was able to update. Unfortunately, I didn't try to root it prior to updating - though to be honest, I don't really feel the need to root anymore. Only reason I had it rooted before was to get the multitasking button, but I'm okay with using an S3 layout (Menu, Home, Back) since that's the phone I'm coming from.
I have posted this in Other thread too.. may be this helps (Or save some time)
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
streetsmart999 said:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o
rohan611 said:
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o
Click to expand...
Click to collapse
That is correct. I was on D80010o all four times I updated to Kit-kat and kept root everytime.
streetsmart999 said:
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
Same thing happened to me. I followed your advice in the other thread and did a reset using the LG flash tool, following rootjunky's guide on youtube and using the files from his website. Everything went smoothly except for at the end I got the same check flag error thing, but it completed the reset perfectly.
I then chatted with ATT and had him push the update to my phone which brought me up to d80010o. It finally went through the update and didn't get me the root error. So I think I'm in the green now. He said that he didn't have an option to push the kit kat update to my phone but it told him to have me do it through the software update in the settings. Which I tried and it said it was up to date. But he said that since they roll out in batches my phone might just not be ready for it yet. I will keep trying though and I'm one step further than I was before. At least it let me update. Shout out to ATT though, chat service is on point.
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Used it installed safestrap and when it reboots get the unlock symbol on the boot screen
Sent from my SM-N900V using XDA Premium 4 mobile app
Works fine on my device. For the unlock symbol, download latest SU and updated binaries. That will go away.
Sent from my SM-N900V using Tapatalk
Definitely works for getting root. Rooted, installed SuperSU, Xposed, SafeStrap all successfully. Now struggling to get a rom to work (tried Eclipse & Hyperdrive). Both say they install successfully via SafeStrap and then hangs on boot up. I've seen one other post on the Eclipse thread for the same problem, so it might be something to keep an eye on.
i can verify that this method works. i just installed superuser and it works flawlessly. the only thing is make sure to download the superuser app from here so you have the updated binaries: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
re
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
lazygregg said:
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
Click to expand...
Click to collapse
Rerun towelroot
re
drewcam888 said:
Rerun towelroot
Click to expand...
Click to collapse
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
lazygregg said:
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
Click to expand...
Click to collapse
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
exaltedgod said:
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
Click to expand...
Click to collapse
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Sent from my SM-N900V using XDA Premium HD app
Dc4479 said:
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Click to expand...
Click to collapse
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
exaltedgod said:
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
Click to expand...
Click to collapse
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
pmt223 said:
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
Click to expand...
Click to collapse
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
emtownsend said:
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
Click to expand...
Click to collapse
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
pmt223 said:
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
Click to expand...
Click to collapse
Ah. Got it. Thanks!
* I successfully used SafeStrap to install HyperROM 8 on slot 1 only, so I had to lose my stock ROM, but I'm OK with that.
cnotes2019 said:
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
i rooted today with towelroot. i have a verizon note 3 on 4.4.2
I am using an old samsung galaxy s4 that my grandma bought from a pawn shop. It was rooted when she bought it. I want to unroot the phone because I really have no interest/experience in having a rooted phone, and one of the apps I use frequently is Snapchat and I can't log into Snapchat when my phone is rooted for some reason? So I looked up a tutorial on how to unroot using Odin and it seemed fairly simple so I tried it and I keep getting a red "failed!" in the box. Am I missing a step? am I doing something wrong? I don't understand. I am new to this I have no experience rooting phones what so ever and I'm scared I'm going to mess it up but it's been fine all 3 times I've tried, it just keeps failing. Please help me. I mean I don't absolutely need to have snapchat so if there's no way I can unroot it successfully I'll just give up, but it would be nice to be able to use it again.
cowgirlbebop said:
I am using an old samsung galaxy s4 that my grandma bought from a pawn shop. It was rooted when she bought it. I want to unroot the phone because I really have no interest/experience in having a rooted phone, and one of the apps I use frequently is Snapchat and I can't log into Snapchat when my phone is rooted for some reason? So I looked up a tutorial on how to unroot using Odin and it seemed fairly simple so I tried it and I keep getting a red "failed!" in the box. Am I missing a step? am I doing something wrong? I don't understand. I am new to this I have no experience rooting phones what so ever and I'm scared I'm going to mess it up but it's been fine all 3 times I've tried, it just keeps failing. Please help me. I mean I don't absolutely need to have snapchat so if there's no way I can unroot it successfully I'll just give up, but it would be nice to be able to use it again.
Click to expand...
Click to collapse
Having root is like having administrator rights on Windows, it does not harm your phone or anything unless you do something like flash a file that is not made for it. Snapchat probably just needs to be uninstalled then reinstalled.
Anyway...
There are 2 ways to unroot. The first method is to download the superSU app from the Google play store. SuperSU is a root management app and has an unroot option built into it. The next method is using ODIN like you are using, however you have to find the right ODIN stock .tar file for the bootloader you're on (or a compatible .tar that lets you downgrade like NB1). Once you have the right .tar file, just flash over what you have and it should get you back to 100% stock without root.
StoneyJSG said:
Having root is like having administrator rights on Windows, it does not harm your phone or anything unless you do something like flash a file that is not made for it. Snapchat probably just needs to be uninstalled then reinstalled.
Anyway...
There are 2 ways to unroot. The first method is to download the superSU app from the Google play store. SuperSU is a root management app and has an unroot option built into it. The next method is using ODIN like you are using, however you have to find the right ODIN stock .tar file for the bootloader you're on (or a compatible .tar that lets you downgrade like NB1). Once you have the right .tar file, just flash over what you have and it should get you back to 100% stock without root.
Click to expand...
Click to collapse
Okay, so I downloaded SuperSU and did the unroot option. It loaded for a few minutes, then the app closed, I rebooted my phone and SuperSU was gone. I really don't know how to tell if it's still rooted or not? but I think it is because snapchat STILL won't let me login. in order to tell if it was still rooted or not I redownloaded SuperSU (bc Idk any other way of knowing if it's rooted or not) and now when I open the app it gives me an alert saying "root undetected" and the only option it gives me is "how to root" and I can't do anything on the app. Thanks for the help.
cowgirlbebop said:
Okay, so I downloaded SuperSU and did the unroot option. It loaded for a few minutes, then the app closed, I rebooted my phone and SuperSU was gone. I really don't know how to tell if it's still rooted or not? but I think it is because snapchat STILL won't let me login. in order to tell if it was still rooted or not I redownloaded SuperSU (bc Idk any other way of knowing if it's rooted or not) and now when I open the app it gives me an alert saying "root undetected" and the only option it gives me is "how to root" and I can't do anything on the app. Thanks for the help.
Click to expand...
Click to collapse
No problem, always glad to help. You can check to see if your phone is still rooted by getting the app called "root checker" from the Google play store. Since you did the unroot via superSU and it disappeared, I am guessing you're now unrooted. However, you should go download root checker to be sure.