Related
I'm looking to root my Note 3, and I'm curious what the safe guidelines are, I can't seem to find a definitive answer on this.
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
My current details are as follows:
Model: SM-N900V
Build: JSS15J.N900VVRUBMJ7
Am I SoL?
Thanks for the help.
NOTE: I tried searching , but it seems the search function is temporarily unavailable :crying:
crizznaig said:
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
Click to expand...
Click to collapse
Yes, you can either use the Kingo root tool or wait until "Root de la Vega" gets a fix.
Personally, I would wait instead of using Kingo: there is some privacy concerns with using Kingo since we don't actually know how/what it does.
DroidModderX said:
The verdict is still out as to whether Kingo App is anything other than a malicious virus ridden software, or an innocent one click root method for many devices. If you do decide to use this app you should do so at your own risk. This root method is completely close sourced so we aren't sure of everything contained with in it. If this bothers you then steer clear. If you don't mind your data potentially being at risk this method is a one click method that works for a long list of devices. It has been confirmed via an XDA thread that this method will work with the Verizon Galaxy Note 3 after the latest OTA update.
Click to expand...
Click to collapse
Yeah I've read the recent situations with Kingo and Vroot as well. I'm cool with waiting, I'd prefer to not have my IMEI data mined for root
I've waited thus far.
So basically I should be following developments on the Root de la Vega stuff.
Appreciate the response
Yeah I've read the recent situations with Kingo and Vroot as well. I'm cool with waiting, I'd prefer to not have my IMEI data mined for root
I've waited thus far.
So basically I should be following developments on the Root de la Vega stuff.
Appreciate the response
Bricked
bummer, i didnt see this yesterday, and i am now bricked and looking to restore somehow back to factory via odin or whatever
crizznaig said:
I'm looking to root my Note 3, and I'm curious what the safe guidelines are, I can't seem to find a definitive answer on this.
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
My current details are as follows:
Model: SM-N900V
Build: JSS15J.N900VVRUBMJ7
Am I SoL?
Thanks for the help.
NOTE: I tried searching , but it seems the search function is temporarily unavailable :crying:
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2498850
I also just received my Note3 with that build number. Any update yet on root?
lieutenantglorp said:
I also just received my Note3 with that build number. Any update yet on root?
Click to expand...
Click to collapse
I have MJ7 and used Kingo
http://forum.xda-developers.com/showthread.php?t=2521581
Kingo Can't Connect
I have just tested Kingo with a Note 3 Verizon (N900V Firmware MJ7) and can't connect.
Thing is, I can see it find in ADB and I can issue commands via ADB. Of course USB debugging is enabled and working fine through ADB.
I'm running the latest version of Kingo 1.1.2.1770, and it just reads "Connecting service" in the bottom-right and the big "Not Connected" in the middle.
I've also attempted to connect my G-III phone which I access via ADB with no problem, and Kingo doesn't see that either.
This is my first test with a one-click root solution. I haven't found any instructions for rooting the N900V any other way (eg directly via command line) .. Anyone have any idea what I could be doing wrong, or how to root the N900V running MJ7 without Kingo?
Thank you in advance
RKM
I would assume you can use odin with stock original firmware and pit file to downgrade your phone from MJ7, use de la vega, use supersu+ "preserve superuser" functionality, then OTA update. Using supersu+/preserve option/OTA/re-enable is how I updated and kept root.
I'd be willing to bet it's your anti-virus or firewall software and that you are doing this on either Win 7 or Win 8.
Sent from my SM-N900V using Tapatalk
Also, having just read up on the latest Kingo stuff, just use it. It's fine. The latest versions don't send your IMEI. I'd still use it if they did, personally. IMEI+serials are sent around all the time when you buy/sell phones online since you need to confirm clean IMEI before paying to be sure the phone hasn't been reported stolen. Nothing bad to worry about. It's your phone, if someone could possibly do anything weird, Verizon would swap you a new one.
bigillz said:
I would assume you can use odin with stock original firmware and pit file to downgrade your phone from MJ7, use de la vega, use supersu+ "preserve superuser" functionality, then OTA update. Using supersu+/preserve option/OTA/re-enable is how I updated and kept root.
Click to expand...
Click to collapse
Doing this will soft brick your device. You cannot go back to MI9 if you are already on MJ7. Do not try to flash back to stock MI9 if you are already on MJ7.
HAZA12D_HYPERDRIVE_NOTE3
haza12d said:
Doing this will soft brick your device. You cannot go back to MI9 if you are already on MJ7. Do not try to flash back to stock MI9 if you are already on MJ7.
HAZA12D_HYPERDRIVE_NOTE3
Click to expand...
Click to collapse
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.
bigillz said:
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.
Click to expand...
Click to collapse
Not positive, but I think they were having to use the pit file with MJ7 after they had tried MI9. Just flashing MJ7 wouldn't work. I've been wrong before though.
G8orDroid said:
Not positive, but I think they were having to use the pit file with MJ7 after they had tried MI9. Just flashing MJ7 wouldn't work. I've been wrong before though.
Click to expand...
Click to collapse
Yes, that's what I've read too.
I'd be willing to bet it's your anti-virus or firewall software and that you are doing this on either Win 7 or Win 8.
Click to expand...
Click to collapse
Unfortunately I don't run any AV software other than the intrinsic Win7, and I had already setup exceptions for the app, disabled, it -- and I've been running Kingo "As Administrator" explicitly in each case.
It just seems so weird that ADB works flawless, and Kingo does not. They're basically the same thing (I believe Kingo is just running everything through ADB, right?)
Ugh .. so I can't downgrade to root, and I can't get Kingo to connect despite it not being related to AV apps and ADB working fine. Leave it to tech to turn a thirty minute project into days!!
Thanks again for any ideas
bigillz said:
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.
Click to expand...
Click to collapse
Yes, even with the pit. You cannot go back to MI9 once you update.
HAZA12D_HYPERDRIVE_NOTE3
---------- Post added at 01:50 PM ---------- Previous post was at 01:46 PM ----------
rkmFL said:
Yes, that's what I've read too.
Unfortunately I don't run any AV software other than the intrinsic Win7, and I had already setup exceptions for the app, disabled, it -- and I've been running Kingo "As Administrator" explicitly in each case.
It just seems so weird that ADB works flawless, and Kingo does not. They're basically the same thing (I believe Kingo is just running everything through ADB, right?)
Ugh .. so I can't downgrade to root, and I can't get Kingo to connect despite it not being related to AV apps and ADB working fine. Leave it to tech to turn a thirty minute project into days!!
Thanks again for any ideas
Click to expand...
Click to collapse
Do you have developer options enabled and have USB debugging enabled?
HAZA12D_HYPERDRIVE_NOTE3
haza12d said:
Do you have developer options enabled and have USB debugging enabled?
Click to expand...
Click to collapse
Absolutely, yes.
I mentioned back in the original thread, I have USB debugging enabled and successfully using ADB, which requires this along with the cert approval (required as of Android 4.2 or 4.3, can't remember now).
As a developer, I use ADB on a daily basis and have never had any issue connecting to the phones.
I've re-installed Kingo, etc -- nothing. I can even fire up a command prompt while Kingo is running and send an ADB devices to see my phone successfully connected with the (with the latest Samsung drivers, right from Kingo's site stating the requirement).
Thanks again for the ideas
rkmFL said:
Absolutely, yes.
I mentioned back in the original thread, I have USB debugging enabled and successfully using ADB, which requires this along with the cert approval (required as of Android 4.2 or 4.3, can't remember now).
As a developer, I use ADB on a daily basis and have never had any issue connecting to the phones.
I've re-installed Kingo, etc -- nothing. I can even fire up a command prompt while Kingo is running and send an ADB devices to see my phone successfully connected with the (with the latest Samsung drivers, right from Kingo's site stating the requirement).
Thanks again for the ideas
Click to expand...
Click to collapse
I agree, it doesn't make a lot of sense that Kingo wouldn't connect if you can connect manually thru ADB. I believe it does use ADB to communicate. The software will take a while to run especially on a slow connection, but I am assuming from what you've said that it never gives you a "Device Connected" status, correct?
I mentioned firewall and AV earlier because some of them will block either the app or the communication. I had Trend Micro running on one of the computers I used and it wouldn't connect until I uninstalled it.
hello there
i did a mistake and buy note 3 n900v
my rom is based on mje
and my device is very slow and the tw luncher is not smooth like n9005 even that they share the same cpu and gpu
i want to change my rom to one is clean from everyrhing from verizon (like apps and bootanimation)
i have root access and i dont want to brick my device
can i install n9005 rom?
someone can help me please ?
lidor578 said:
hello there
i did a mistake and buy note 3 n900v
my rom is based on mje
and my device is very slow and the tw luncher is not smooth like n9005 even that they share the same cpu and gpu
i want to change my rom to one is clean from everyrhing from verizon (like apps and bootanimation)
i have root access and i dont want to brick my device
can i install n9005 rom?
someone can help me please ?
Click to expand...
Click to collapse
Questions should be in Q & A. That's what its there for.
Buying a 900V is a big mistake if your not on Verizon. No, you cannot flash N9005 roms on this device. Your best bet would be installing one of the roms in the development section here. http://forum.xda-developers.com/verizon-galaxy-note-3/development
lidor578 said:
hello there
i did a mistake and buy note 3 n900v
my rom is based on mje
and my device is very slow and the tw luncher is not smooth like n9005 even that they share the same cpu and gpu
i want to change my rom to one is clean from everyrhing from verizon (like apps and bootanimation)
i have root access and i dont want to brick my device
can i install n9005 rom?
someone can help me please ?
Click to expand...
Click to collapse
how do you rooted your mje n990v? i can't
huess113 said:
how do you rooted your mje n990v? i can't
Click to expand...
Click to collapse
Kingo... worked on mine
shiftr182 said:
Kingo... worked on mine
Click to expand...
Click to collapse
I don't know if there is a scamware version of Kingo going around or something, but I've never been able to get it to work.
I can use ADB without any problems on my SM-N900V. I then run Kingo and it does nothing, just sits there "waiting" for the devices. Windows Firewall disabled, No AV software, Trying Kingo w/Admin permissions and without. Nothing works.
After wasting hours with this, I finally decided I'd try a vanilla Windows 8 install, nothing on it but Kingo. Still didn't work.
Brought my phone back to my PC, ADB works just fine -- tried Kingo again -- nothing.
...On a related note...
After searching the forums for some time, there is one question I just can't determine definitively:
Can the SM-N900V (Verizon Galaxy Note 3) be truly "unlocked" with a custom recover (or) are we still limited to Safestrap options?
Thank you in advance,
RKM
rkmFL said:
I don't know if there is a scamware version of Kingo going around or something, but I've never been able to get it to work.
I can use ADB without any problems on my SM-N900V. I then run Kingo and it does nothing, just sits there "waiting" for the devices. Windows Firewall disabled, No AV software, Trying Kingo w/Admin permissions and without. Nothing works.
After wasting hours with this, I finally decided I'd try a vanilla Windows 8 install, nothing on it but Kingo. Still didn't work.
Brought my phone back to my PC, ADB works just fine -- tried Kingo again -- nothing.
...On a related note...
After searching the forums for some time, there is one question I just can't determine definitively:
Can the SM-N900V (Verizon Galaxy Note 3) be truly "unlocked" with a custom recover (or) are we still limited to Safestrap options?
Thank you in advance,
RKM
Click to expand...
Click to collapse
I had the same problem with Kingo initially. I don't remember how I fixed it, but it was a simple fix.... something stupid. Now it works with no problem.
In regard to the recovery, if you have a retail Note 3 from Verizon you will brick it if you flash a recovery other than safestrap. The bootloader will recognize the recovery is not stock, your knox will void you warranty and the phone will not boot. The only available recovery option for retail is safestrap.
shiftr182 said:
I had the same problem with Kingo initially. I don't remember how I fixed it, but it was a simple fix.... something stupid. Now it works with no problem.
Click to expand...
Click to collapse
I've tried all of the crazy suggestions that people have claimed will make it work. Setting screen timeout to 10 minutes, allowing untrusted & disabling app inspection, everything.
I can even use ADB directly from the Kingo directory, no problem.
And here's the real kicker .. if I delete the token allowing ADB access to my phone, Kingo will not trigger the phone to prompt for one. So Kingo is *not* even attempting to run ADB.
Not to mention, if you look at the logs, the entire time Kingo is communicating with Chinese servers. Sure, it might not be doing anything to root the phone, but that's not going to stop them from sending loads of data to China in the process.
At this point I think I think I'm best to chalk up the 12+ wasted hours on Kingo and give vRoot a try. What a nightmare, I've never had such a bad experience with an Android tool, whether it be for S-OFF, Rooting, etc.
rkmFL said:
I've tried all of the crazy suggestions that people have claimed will make it work. Setting screen timeout to 10 minutes, allowing untrusted & disabling app inspection, everything.
I can even use ADB directly from the Kingo directory, no problem.
And here's the real kicker .. if I delete the token allowing ADB access to my phone, Kingo will not trigger the phone to prompt for one. So Kingo is *not* even attempting to run ADB.
Not to mention, if you look at the logs, the entire time Kingo is communicating with Chinese servers. Sure, it might not be doing anything to root the phone, but that's not going to stop them from sending loads of data to China in the process.
At this point I think I think I'm best to chalk up the 12+ wasted hours on Kingo and give vRoot a try. What a nightmare, I've never had such a bad experience with an Android tool, whether it be for S-OFF, Rooting, etc.
Click to expand...
Click to collapse
Any luck with vroot?
I wish you could recall the "something simple" to make Kingo work. Where can I get "Safestrap?"
I just got a Verizon SM-900V with MJE yesterday. I need root to be able to use ARUnchained with my AppRadio 2. I tried Kingo, and it just kept switching between "connecting" and "downloading drivers" it never would connect to the phone. At this point, I'm not to concerned about custom ROMs, nor am I concerned about voiding the warranty. I just need to be able to obtain ROOT without bricking my phone. All of the threads on successful rooting of this device are from around November of last year. So, is there a way to successfully root any more? Thanks in advance!
please help.. I have 900v upgraded to 5.0.1....lost pics and voice recorded files...
please help with my note 3
rkmFL said:
I've tried all of the crazy suggestions that people have claimed will make it work. Setting screen timeout to 10 minutes, allowing untrusted & disabling app inspection, everything.
I can even use ADB directly from the Kingo directory, no problem.
And here's the real kicker .. if I delete the token allowing ADB access to my phone, Kingo will not trigger the phone to prompt for one. So Kingo is *not* even attempting to run ADB.
Not to mention, if you look at the logs, the entire time Kingo is communicating with Chinese servers. Sure, it might not be doing anything to root the phone, but that's not going to stop them from sending loads of data to China in the process.
At this point I think I think I'm best to chalk up the 12+ wasted hours on Kingo and give vRoot a try. What a nightmare, I've never had such a bad experience with an Android tool, whether it be for S-OFF, Rooting, etc.
Click to expand...
Click to collapse
Ok. So I've tried to ask this question before, and every time I get people telling me to do things I just don't understand. Sorry. Not trying to spam. If this question goes unanswered I will not post another and I apologize if this is too stupid. Just a noob trying to get help.
All I want is to update my phone (SM-G900F) to the most recent Android version. Like 3 weeks ago I got the prompt to update OTA because a new update was available. I've haven't modified my phone other than Towelrooting in July and having SuperSU and Titanium. Had planned to get way more root stuff but so far I haven't had the time.
OTA Update failed, told me my phone was modified in an unauthorized way and suggested to update through Kies.
Here's my question: What's the simplest, easiest way to update correctly? I'd rather do it one way or the other: Either, I unroot with SuperSU and remove Titanium, then download Kies and try to update, if successful I reroot with Towelroot OR: I can manage to update WITH Towelroot and SuperSU still there, if so, how?
That's all I'm asking. Would the first option work best? Is there a better way? I don't want to use Odin or anything like that, I don't want to use custom roms or anything, I'd just like to have the most recent update and root, that's it. Please put me out of my misery.
tempest22 said:
What's the simplest, easiest way to update correctly?
I don't want to use Odin or anything like that
Click to expand...
Click to collapse
You can't have it both ways. Odin is the easiest, otherwise try Kies.
Download NeatRom and you will get the latest Rom.
http://forum.xda-developers.com/showthread.php?t=2828562
Verstuurd vanaf mijn SM-G900F met Tapatalk
BLuFeNiX said:
You can't have it both ways. Odin is the easiest, otherwise try Kies.
Click to expand...
Click to collapse
So would it work if I unroot with SuperSU, then install Kies on my pc and update to most recent Anroid version?
Or, if I'm already going to unroot first with SuperSU, can I then just try the OTA update and if successful, can I reroot with Towelroot or will that be outdated with the most recent Android version?
Download odin 3.09. Download the latest official firmware for your device, search the forums to find the latest one. Extract the .tar file inside the firmware zip u downloaded. Make sure you have the drivers installed for your phone on your computer. Extract Odin and run the .exe to open the Odin program. Put your phone into download mode> While Powered off hold volume down.. Home.. And power button. Press continue when given the warning plug in your phone to the PC.. Within Odin click the ap slot. Load the .Tar file which is your firmware. Make sure Odin recognizes your phone is plugged. Hit start. Sit back and watch it flash.
Sent from my SM-G900T using XDA Free mobile app
Ok. I hope this does not sound arrogant. But I honestly can't believe why anyone on this forum can't directly answer my question instead of giving me other suggestions. I don't want to use Odin, it's too complex for me and I don't want to mod my phone to hell and back. I just want to get the most recent update released 2 or so weeks ago.
Nobody has said whether the Kies method works (letting Towelroot remain on my phone and trying to download most recent Android version with Kies on my pc), or whether I unroot with SuperSU, remove all root apps (I only have 3), then try the OTA update just with my phone and see if that works. Can somebody please just answer that? PLEASE
..
I think I'm correct in saying the most recent ota comprised on little more than minor tweaks and security updates.
The world's not going to come to an end if you don't have the very latest update.
Perhaps more research BEFORE choosing the root route would have been wise, at least then you would be more informed as to the outcome of your chosen option.
Having read the last few posts it's clear to me, even as a relative S5 noob that your questions been answered quite comprehensively. Just not the install an app and reboot option you were hoping for.
sent from SGS5 running NeatRom 0X1
---------- Post added at 08:07 PM ---------- Previous post was at 08:02 PM ----------
Just before I get stuck into my pizza. .....
.......did you by any chance select ART rather than running a DALVIK system?
I did that before rooting and I got the same can't install ota due to modified yada yada.....
I reverted back to Dalvik and the ota installed no problem. As I said.... This was pre rooting so might not be relevant.
sent from SGS5 running NeatRom 0X1
does.the kies method i asked about.work.
tempest22 said:
does.the kies method i asked about.work.
Click to expand...
Click to collapse
from reading the replies above i think the answer is no it wont but why not just give it a try, if its not going to work it will just tell you so (like the ota update did)
your options as stated above are to either use odin and install the latest update or take it to a shop or find someone who is close to you who knows how to use odin and ask them if they wouldnt mind doing it for you and buy them a beer as a thankyou,
odin isnt hard to use in fact it couldnt be any easier to use for a noob just follow a couple of simple steps and your done
i hope you get this sorted
tempest22 said:
does.the kies method i asked about.work.
Click to expand...
Click to collapse
It should work as I have done that on my old device before but you have to re-root your s5 again after the update.
Sent from my SM-G900F using Tapatalk
Towelroot after latest OTA-Update doesn't work!
I don't know if the idea of an update is so good.
My SM-900F was Towelrooted to run Titanium, too.
My setup was "OTA when in a WIFI network" and clicked "update yes" - I was typing some notes very late,
the message box popped up and --- swoosh --- the Update was running. No need to say my notes weren't saved?
I don't even know what that update contained and what it was good for.
Now I run 4.4.2 ,
Baseband G900FXXU1ANG2
Kernel 3.4.0-2089850 [email protected] #1 July 3rd 2014
Build KOT49H.G900FFXXU1ANG2.
Root access has gone, Towelroot says "device not supported", Titanium doesn't work anymore.
No I have to start Windows only to run KIES - waf.
So be careful.
Dirk
Ok, so I have unrooted with supersu and removed Titanium. Supersu is still there. I've tried to do an OTA update, and surprisingly this time it actually went so far as to actually download the updates. Then after I press install, it goes into boot mode and says like 20% or more installed, then it goes black and reboots, everything is normal but the update failed.
What. Now.
They should really start telling people that rooting will cause updates to become a nightmare. Please help me, this is ridiculous.
tempest22 said:
They should really start telling people that rooting will cause updates to become a nightmare. Please help me, this is ridiculous.
Click to expand...
Click to collapse
Lack of common sense is my diagnosis.
Of course it's not always going to be plain sailing. And early days with any new handset means there are answers we just don't know yet.
That's why pretty much every thread has a precursor from the Dev that says "use at your own risk","read instructions fully before flashing" or " it's not my fault if your dog gets fleas or your nan pegs it" etc etc etc. If you have any doubts rooting your phone wasnt for you..... you shouldn't have rooted.
sent from SGS5 running NeatRom 0X1
tempest22 said:
They should really start telling people that rooting will cause updates to become a nightmare. Please help me, this is ridiculous.
Click to expand...
Click to collapse
Lack of common sense is my diagnosis.
Of course it's not always going to be plain sailing. And early days with any new handset means there are answers we just don't know yet.
That's why pretty much every thread has a precursor from the Dev that says "use at your own risk","read instructions fully before flashing" or " it's not my fault if your dog gets fleas or your nan pegs it" etc etc etc. If you have any doubts rooting your phone wasnt for you..... you shouldn't have rooted.
sent from SGS5 running NeatRom
bump, can somebody tell me conclusively for once and for all if the following will work: I have unrooted with supersu (originally rooted with Towelroot in July) supersu and titanium are removed, OTA update still doesn't work. if i install Kies on my pc, will an update work, AND will I be able to use towelroot again to reroot.
thank you.
please?
tempest22 said:
bump, can somebody tell me conclusively for once and for all if the following will work: I have unrooted with supersu (originally rooted with Towelroot in July) supersu and titanium are removed, OTA update still doesn't work. if i install Kies on my pc, will an update work, AND will I be able to use towelroot again to reroot.
thank you.
Click to expand...
Click to collapse
Did you use Triangle Away to reset the system status and binaries to official? If not reroot with Towelroot again, use Triangle Away to reset the counters (besides the KNOX flag), unroot with the superSU app, then flash a stock rom with Odin and after that factory reset. Your device is official now.
gee2012 said:
Did you use Triangle Away to reset the system status and binaries to official? If not reroot with Towelroot again, use Triangle Away to reset the counters (besides the KNOX flag), unroot with the superSU app, then flash a stock rom with Odin and after that factory reset. Your device is official now.
Click to expand...
Click to collapse
jesus ****ing christ. i'm not that kind of a phone pro guy. I just want to know if updating with Kies with allow me to reroot afterwards again (whether or not with Towelroot or ****ing Odin isn't important anyway). I rooted with towelroot in july, know isn't tripped or whatever. I have unrooted with supersu. Now I just want to know whether or not updating with Kies on my pc will be successful, and if it will allow me to reroot again, like with Towelroot...
PLEASE
tempest22 said:
jesus ****ing christ. i'm not that kind of a phone pro guy. I just want to know if updating with Kies with allow me to reroot afterwards again (whether or not with Towelroot or ****ing Odin isn't important anyway). I rooted with towelroot in july, know isn't tripped or whatever. I have unrooted with supersu. Now I just want to know whether or not updating with Kies on my pc will be successful, and if it will allow me to reroot again, like with Towelroot...
PLEASE
Click to expand...
Click to collapse
Well I know why no one can answer that simple question. Because no one has done it that way. That is why you can't get the answer you seek. So you have a choice, give up and stop asking, or be the first to try it. Then post here if it works or not.
Sent from my HTC One_M8 using Tapatalk
I'm looking to root my s4, I just upgraded to lollipop and love it but there are some things I would like to do that require root. Hoping that someone can walk me through the process. Thanks in advance
Interested in this as well. Just need a point in the right direction. Thanks
I may be incorrect, but at the moment root for I337UCUGOC3 is only available via Flashfire.
http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
motobiz said:
I may be incorrect, but at the moment root for I337UCUGOC3 is only available via Flashfire.
http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
Click to expand...
Click to collapse
So there is no straight root from 5.0.1 at the moment?
Aranace said:
So there is no straight root from 5.0.1 at the moment?
Click to expand...
Click to collapse
No. You have to downgrade to 4.4.2 first, root, then flash up to 5.0
Sent from my SAMSUNG-SGH-I337
Bumping an older thread.
I've been searching around the forums for a guide to downgrade and a link to the Stock 4.4.2 ROM. AT&T Upgrade happened inadvertently. I either wasn't paying attention or it happened automatically.
Found plenty of post saying the same thing but no trustworthy guide on how to downgrade effectively from 5.0.1 on the i337 to 4.4.2. Normally I'd be up for experimenting but a newborn has me a little sleep deprived and looking for an idiot guide.
TIA
smtelegadis said:
Bumping an older thread.
I've been searching around the forums for a guide to downgrade and a link to the Stock 4.4.2 ROM. AT&T Upgrade happened inadvertently. I either wasn't paying attention or it happened automatically.
Found plenty of post saying the same thing but no trustworthy guide on how to downgrade effectively from 5.0.1 on the i337 to 4.4.2. Normally I'd be up for experimenting but a newborn has me a little sleep deprived and looking for an idiot guide.
TIA
Click to expand...
Click to collapse
Are you trying to get back to 4.4.2 then attempt to upgrade too 5.0.1 root?
Yes, but it sounds like from the tone of that question that I might be screwed.
You can flash back to nb1, root with towelroot, and go to lollipop with the keeproot method. Look in the general forum for [GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap by guut13 and [How-To] Update to I337_OC3 - 5.0.1 and KeepRoot (4/7/2015) by muniz_ri.
schhy said:
No. You have to downgrade to 4.4.2 first, root, then flash up to 5.0
Click to expand...
Click to collapse
I also have a I337UCUGOC3 running 5.0.1.
Unfortunately yesterday my phone got messed up (I'll spare you all the details) and I had to do a factory reset. I am really unhappy about this because I wasn't able to backup properly with Titanium Backup since I'm not rooted. As a result, I now need to spend a bunch of hours getting my phone back to the way I like it. I am honestly not interested in flashing custom ROMs. I simply want to root so I can run Titanium Backup.
Based on your experience, how long might it typically take for a root guide to come out for this model? I'm trying to decide whether I should try to wait it out with my phone feeling "unfamiliar" to me - or if I should just go ahead and give up the idea of rooting / backing up.
Also, is there one site or forum (this thread???) where I would be able to find out how to root this model when it comes out? If so, where?
I would very much appreciate your advice!
Eliezer
EliezerB said:
I also have a I337UCUGOC3 running 5.0.1.
Unfortunately yesterday my phone got messed up (I'll spare you all the details) and I had to do a factory reset. I am really unhappy about this because I wasn't able to backup properly with Titanium Backup since I'm not rooted. As a result, I now need to spend a bunch of hours getting my phone back to the way I like it. I am honestly not interested in flashing custom ROMs. I simply want to root so I can run Titanium Backup.
Based on your experience, how long might it typically take for a root guide to come out for this model? I'm trying to decide whether I should try to wait it out with my phone feeling "unfamiliar" to me - or if I should just go ahead and give up the idea of rooting / backing up.
Also, is there one site or forum (this thread???) where I would be able to find out how to root this model when it comes out? If so, where?
I would very much appreciate your advice!
Eliezer
Click to expand...
Click to collapse
There is no way to root on OC3 at the moment. No clue on how long it'll take if a method even gets found. I recommend downgrading to NB1 using Odin then following the steps on herehttp://forum.xda-developers.com/showthread.php?t=3075814
. All downgrade file are on there too. Read through all steps and warning to prevent any problems
Sent from my SAMSUNG-SGH-I337
smtelegadis said:
Bumping an older thread.
I've been searching around the forums for a guide to downgrade and a link to the Stock 4.4.2 ROM. AT&T Upgrade happened inadvertently. I either wasn't paying attention or it happened automatically.
Found plenty of post saying the same thing but no trustworthy guide on how to downgrade effectively from 5.0.1 on the i337 to 4.4.2. Normally I'd be up for experimenting but a newborn has me a little sleep deprived and looking for an idiot guide.
TIA
Click to expand...
Click to collapse
FWIW my wife noted the user interface on her S4 suddenly completely changed. Looking at it when I got a chance I saw it was 5.0.1 (OC3). I actually don't know what it was previously. So AT&T is definitely pushing out the update.
Already on 5.0.1
I bought this ATT phone used, unlocked, and already on 5.0.1. We use it on the GoSmart Mobile network (owned/operated by T-Mobile). Today (a few weeks after the purchase), I get this message saying that there's an ATT software update available. How can ATT push an update to a phone not on their network? Will this update screw anything up? Will it re-network-lock it? I don't want to update this phone and, since it's my wife's phone, I don't want to risk a brick (I am in a similar situation with a baby and am quite sleep deprived). Previously, she had an HTC First (ATT phone use on GoSmart) and it notified us of an available update, but would not actually update (thank goodness). Do I actually have anything to worry about with this ATT update? Or is the notification just an annoyance? Thanks in advance.
>Joe
joeskippyxda said:
I bought this ATT phone used, unlocked, and already on 5.0.1. We use it on the GoSmart Mobile network (owned/operated by T-Mobile). Today (a few weeks after the purchase), I get this message saying that there's an ATT software update available. How can ATT push an update to a phone not on their network? Will this update screw anything up? Will it re-network-lock it? I don't want to update this phone and, since it's my wife's phone, I don't want to risk a brick (I am in a similar situation with a baby and am quite sleep deprived). Previously, she had an HTC First (ATT phone use on GoSmart) and it notified us of an available update, but would not actually update (thank goodness). Do I actually have anything to worry about with this ATT update? Or is the notification just an annoyance? Thanks in advance.
>Joe
Click to expand...
Click to collapse
The latest update, from 5.0.1, OC3 to 5.0.1 OC4 is a security update which is believed to be a response to the stagefreight bug. The update is relatively small, and should not "screw anything up." It will not affect network unlock.
As to why you're getting it on a non AT&T network, I'd guess that the update server determines the phone is an SGH-I337 and pushes the correct update for the phone.
How to root
Okay, so I have 5.0.1 with i337ucugoc3 and finally rooted it quite easily (after many failures).
I used WonderShare's MobileGo.
The process was actually very simple, but it was very confusing as to what the software actually wanted from me.
To make it easy, here's all you need:
1. Go to Settings->more->About Device
2. Tap on "Build number" seven (or more) times quicly
-- this will unlock the developer tools
3. Tap the back arrow
4. Tap "Developer options"
5. Tap on "USB debugging" to enable
6. Go to wondershare.com, download MobileGo, install
7. Run MobileGo
8. Connect your phone to your computer with a USB cable.
9. In MobileGo, click on the "One-Clock Root" button
You should be rooted quickly.
Not only that, it only installs SuperSU, and no malware.
10. Uninstall MobileGo if you don't want to keep it.
LoonCraz, thank you for your post. I have two questions about what you wrote:
looncraz said:
Okay, so I have 5.0.1 with i337ucugoc3 and finally rooted it quite easily (after many failures).
Click to expand...
Click to collapse
Would this work also for i337ucugoc4?
When you say "after many failures" - were there ever any negative consequences (something broken or bricking, etc.) from one of those failures - or just not getting root?
Thanks,
Eliezer
EliezerB said:
LoonCraz, thank you for your post. I have two questions about what you wrote:
Would this work also for i337ucugoc4?
When you say "after many failures" - were there ever any negative consequences (something broken or bricking, etc.) from one of those failures - or just not getting root?
Thanks,
Eliezer
Click to expand...
Click to collapse
I don't know, but supposedly it works very well with most versions.
None of my failed attempts left any bad effects, this program worked first shot :good:
Does the phone get wiped in the process - or does everything stay intact / in place?
The Wondershare MobileGo One-Click Root process successfully rooted my unlocked GS4 i337 (OC4) today, and confirmed by Root Checker. So easy!
looncraz said:
Okay, so I have 5.0.1 with i337ucugoc3 and finally rooted it quite easily (after many failures).
I used WonderShare's MobileGo.
The process was actually very simple, but it was very confusing as to what the software actually wanted from me.
To make it easy, here's all you need:
1. Go to Settings->more->About Device
2. Tap on "Build number" seven (or more) times quicly
-- this will unlock the developer tools
3. Tap the back arrow
4. Tap "Developer options"
5. Tap on "USB debugging" to enable
6. Go to wondershare.com, download MobileGo, install
7. Run MobileGo
8. Connect your phone to your computer with a USB cable.
9. In MobileGo, click on the "One-Clock Root" button
You should be rooted quickly.
Not only that, it only installs SuperSU, and no malware.
10. Uninstall MobileGo if you don't want to keep it.
Click to expand...
Click to collapse
this worked just fine....
I did it in my S4 i377 with 5.0.1 OC3
just download the trial and root it...
thanks!!!
Wondering if anyone in the know has heard of any development going on for this device? I recently bought one and it's not a bad phone for the price, but I've seen absolutely -nothing- on it anywhere online for the most part. It's barely root-able with what I've been able to find, and no custom recovery or really anything custom has popped up that I've seen.
Not sure if it's just that it's been only a few months since the phone came out, or if it's just not that great a phone. I upgraded from an HTC Desire 510 to this, and it was heavily customized/rooted/etc, and I want so badly to get back to where I was with it on this phone I cant stand it!
I also want to root my Galaxy J3! I just want to root it so I can use AdAway and Titanium Backup.
triiuzii said:
I also want to root my Galaxy J3! I just want to root it so I can use AdAway and Titanium Backup.
Click to expand...
Click to collapse
Right now rooting isn't the problem so much as keeping root. Because apparently the colonel has protection and will remove root whenever you reboot. That means things that require root on boot like backups, Xposed and a lot of other things won't work for us until someone complies a kernel with root protection removed. You can do some debloating and possibly the AdAway but that's about it right now.
*kernel. Damn voice to text.
That sucks. I upgraded from an LG Volt and I was able to do a whole bunch of stuff on it. The J3 is still very new, so hopefully development will happen soon.
I just got this phone if there is anything i can do to help move this along let me know. I have the virgin mobile one.
mallamike said:
I just got this phone if there is anything i can do to help move this along let me know. I have the virgin mobile one.
Click to expand...
Click to collapse
I guess that would depend on what you have experience with and what you can do. Thus-far root has been able to be achieved with Kingroot, though it wont stick through a power cycle (reboot/power off/etc), and using any of the methods available (at least that I'm aware of, only found two legitimate ones) to replace Kingroot with SuperSU (to facilitate having root stick past the reboot hopefully) causes a soft-brick every time forcing a re-flash of stock firmware through Odin.
At the very least make your voice heard, if nothing else hopefully more popularity will come this devices way and we'll see some development for it. My roommate is considering writing something for it, but it is a long process working solo, so anyone who has experience working with kernels or editing stock rom/writing custom roms feels up to helping out, shoot me a message and I'll get it over to him. He's a fairly experienced programmer and picks up what he doesn't already know pretty quickly.
Got one recently too. Would also appreciate any more information on rooting.
I have a J320A (AT&T) came stock with 6.0.1, can help test if needed
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
coolbeans2016 said:
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
Click to expand...
Click to collapse
Will this version of TWRP work on the Att variant running 6.0.1? Is there a way to root that device yet?
coolbeans2016 said:
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
Click to expand...
Click to collapse
Anything yet for J320A/Z models? (AT&T/cricket)
This version of TWRP won't work will it? Totally different phone?
EDIT: just realized the guy above has the same question... something tells me we won't see root on the ATT/cricket variants for a while.
TechShui said:
Anything yet for J320A/Z models? (AT&T/cricket)
This version of TWRP won't work will it? Totally different phone?
EDIT: just realized the guy above has the same question... something tells me we won't see root on the ATT/cricket variants for a while.
Click to expand...
Click to collapse
Try official TWRP of galaxy J2. Your variant shares the same specs as J2. Others also did this to galaxy On5, it works 100%.
what about the
SM-J320VPP = the verizon pre paid planversion. any working roots for me yet?
oh pretty pleeeeeez
Azhero said:
Try official TWRP of galaxy J2. Your variant shares the same specs as J2. Others also did this to galaxy On5, it works 100%.
Click to expand...
Click to collapse
So can you confirm this method works? Does OEM unlock setting in dev options unlock the bootloader on AT&T variant? If so couldn't I temp root and flash TWRP via Flashify?
AnierinB said:
So can you confirm this method works? Does OEM unlock setting in dev options unlock the bootloader on AT&T variant? If so couldn't I temp root and flash TWRP via Flashify?
Click to expand...
Click to collapse
It doesn't work tried it 3 times. I even tried other ones no luck. They locked this thing down. Im surprise chainfire haven't tried this phone yet.
Hi, guys! I understand it was an old thread, but I was referred here from Reddit. I have a Galaxy J3 (SM-J3109) purchased in Mainland China (Service provider is China Telecom). I rooted it with Kingo Root. Kingo Root stated that it successfully rooted the device, but the phone OS had given me warnings about unauthorized access to the device or something.
One week later (I did *not* reflash the phone nor install any applications after I rooted the phone) I found the phone stuck in an annoying bootloop. The device status is still "official" and the Knox counter is still set at 0x0.
Now that it's bootlooping I'd like to know if it's possible to take the applications and files off the phone before I factory reset it. It's not looking hopeful as I read similar threads from 2012 saying that once other Android devices bootloop, getting stuff off of them is impossible. I tried using ADB to take data off the phone (while Odin3 was detecting it being connected to the PC) but ADB doesn't detect the phone. Should I try a different cable?
Gotbootloopedtoomuch said:
Hi, guys! I understand it was an old thread, but I was referred here from Reddit. I have a Galaxy J3 (SM-J3109) purchased in Mainland China (Service provider is China Telecom). I rooted it with Kingo Root. Kingo Root stated that it successfully rooted the device, but the phone OS had given me warnings about unauthorized access to the device or something.
One week later (I did *not* reflash the phone nor install any applications after I rooted the phone) I found the phone stuck in an annoying bootloop. The device status is still "official" and the Knox counter is still set at 0x0.
Now that it's bootlooping I'd like to know if it's possible to take the applications and files off the phone before I factory reset it. It's not looking hopeful as I read similar threads from 2012 saying that once other Android devices bootloop, getting stuff off of them is impossible. I tried using ADB to take data off the phone (while Odin3 was detecting it being connected to the PC) but ADB doesn't detect the phone. Should I try a different cable?
Click to expand...
Click to collapse
Best advice would be to try flashing the stock firmware with odin. That shouldn't delete any of your data and will usually fix a bootloop. You can Google your phones stock firmware and see if you can download it.
darknaio said:
Best advice would be to try flashing the stock firmware with odin. That shouldn't delete any of your data and will usually fix a bootloop. You can Google your phones stock firmware and see if you can download it.
Click to expand...
Click to collapse
Thank you so much! I tried using Odin to flash a software update and it worked perfectly. The phone is back up and running and all of the files are still there!
Right now i have TWRP 3.0.2 with supersu and i havent lost root yet also had no problem switching between backups, xposed working fine and also overclock too with setcpu, im currently running 5.1.1 using j320FN but TWRP was from j320F, i will put up links to the files if any of you are willing to try its up to you.
TWRP flash through odin : http://www.mediafire.com/download/blk7qa90vs6wik3/TWRP_3.0.2-0_SM-J320F.tar.tar
Supersu flash through recovery then update through playstore then install busybox after through playstore : http://www.mediafire.com/download/cpv2c71cp11x41f/UPDATE-SuperSU-v2.76-20160630161323.zip
Remember to turn on usb debugging and turn on oem unlock before flashing recovery, also if you manage to get recovery press they grey box on the right to change language to english. Hope this might help somebody on here because we really need full root for everyone.