[Q] Safe Build for Root on SM-N900V

[crizznaig]

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:

 

[tschrock123]

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?

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.

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.

 

[crizznaig]

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

 

[crizznaig]

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

 

[kididaho]

Bricked

bummer, i didnt see this yesterday, and i am now bricked and looking to restore somehow back to factory via odin or whatever

 

[scoobysnack]

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:

Try this: http://forum.xda-developers.com/showthread.php?t=2498850

 

[lieutenantglorp]

I also just received my Note3 with that build number. Any update yet on root?

 

[weedahoe]

I also just received my Note3 with that build number. Any update yet on root?

I have MJ7 and used Kingo

http://forum.xda-developers.com/showthread.php?t=2521581

 

[rkmFL]

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

 

[bigillz]

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.

 

[G8orDroid]

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

 

[bigillz]

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.

 

[haza12d]

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.

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

 

[bigillz]

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

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.

 

[G8orDroid]

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.

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.

 

[rkmFL]

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.

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.

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

 

[haza12d]

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.

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 ----------

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

Do you have developer options enabled and have USB debugging enabled?

HAZA12D_HYPERDRIVE_NOTE3

 

[rkmFL]

Do you have developer options enabled and have USB debugging enabled?

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

 

[G8orDroid]

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

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.