Not able to root N900V, Pls Help

[ecrudragon]

I am trying to root my N900V via many many methods and yes i studied everything first before asking this question which is asked thousands of times before, i tried yemen tool, CWM, TWRP, TR, Farmaroot nothing works for me i don't know why, i am on OF1 5.0 Lollipop,.

Please advice, thank you

 

[bftb0]

Did you buy a SM-N900V?

I see this is your first post in this sub-forum, and you have many posts in the "Xiomi Red Note 3" (kenzo) forum.

(There isn't much reason to believe that a root method for one device will work on a completely different device.)

Anyway, your root options for the SM-N900V on either OB6 or OF1 are only the Yemen tools - no other choices.

Using Odin, you can flash any of the factory stock firmwares for NK1, OB6, OF1, or PL1 without hitting the anti-rollback prevention... but only OB6 and OF1 have publicly available rooting methods (the two Yemen threads). Towelroot v3 has not worked since the NC4 release; that is now five releases in the past.

The only other method (much much harder) would be for you to research and implement your own root exploit. (The PL1 release was a security bug patch release, suggesting that one or more severe vulns exist in those older releases)

So go back and try the Yemen tools again - either with OF1, or with OB6. And if you get nothing but failures, describe the setup and observed behaviors during those failures - more than just "it didn't work". No-one wants to play a game of "twenty questions" back-and-forth across the Internet.

 

[ecrudragon]

Did you buy a SM-N900V?

I see this is your first post in this sub-forum, and you have many posts in the "Xiomi Red Note 3" (kenzo) forum.

(There isn't much reason to believe that a root method for one device will work on a completely different device.)

Anyway, your root options for the SM-N900V on either OB6 or OF1 are only the Yemen tools - no other choices.

Using Odin, you can flash any of the factory stock firmwares for NK1, OB6, OF1, or PL1 without hitting the anti-rollback prevention... but only OB6 and OF1 have publicly available rooting methods (the two Yemen threads). Towelroot v3 has not worked since the NC4 release; that is now five releases in the past.

The only other method (much much harder) would be for you to research and implement your own root exploit. (The PL1 release was a security bug patch release, suggesting that one or more severe vulns exist in those older releases)

So go back and try the Yemen tools again - either with OF1, or with OB6. And if you get nothing but failures, describe the setup and observed behaviors during those failures - more than just "it didn't work". No-one wants to play a game of "twenty questions" back-and-forth across the Internet.

First of all thank you for your detailed answer.
No I didn't bought N900V it's my little brother who snatched Redmi Note 3 from me and gave me this piece of work.
Today I will try to downgrade the firmware to OB6 and try Yemen tools again and see if it works, I will get back to you with the report. Sighhhhh I hope it will work on OB6.

P.S how long should Yemen tools take to root the phone? Because I gave it good 15 mins and it was still running in download mode with no progress bar so I thought it's not working.

Update: Didn't worked on OB6 even

 

[bftb0]

First of all thank you for your detailed answer.
No I didn't bought N900V it's my little brother who snatched Redmi Note 3 from me and gave me this piece of work.
Today I will try to downgrade the firmware to OB6 and try Yemen tools again and see if it works, I will get back to you with the report. Sighhhhh I hope it will work on OB6.

P.S how long should Yemen tools take to root the phone? Because I gave it good 15 mins and it was still running in download mode with no progress bar so I thought it's not working.

Update: Didn't worked on OB6 even

Dang. I wrote you a long reply and it didn't take and disappeared out of my cache when I hit the back button.

Anyway, I see you are on one of those two yemen threads. That's the right place to continue this discussion.

I'm not much help as I am still on NC4 and have never used either of those methods. So I am not of much technical help.

I did just read both of those threads - every last post - and I can conclude this:

What a mess.

and... you symptoms sound a lot like what everyone else with troubles reports.

Obviously both methods are very fragile. Because they involve a Windows PC, I imagine that a first thing to suspect is Antivirus Programs / Driver version Issues / USB3 vs. USB2.

Since it appears that both methods cause the phone to reboot into different phone modes, at a minimum I would:

(a) verify that the PC's drivers recognize the phone in all modes (adb, Odin)
(b) perhaps toggle the default storage setting (MTP vs PTP) in addition to enabling ADB

maybe even clear the ADB certificate cache before starting.

The thing to be cautious about in both those threads is jumping to conclusions that are not warranted. A lot of people in there are insisting (for instance) "Windows 10 only", despite the fact that there are success reports on Win7, Win8.1 (and even someone reporting success on Win Vista!). Usually they come to those conclusions erroneously because of "post-hoc fallacy": they assume that "the last thing that I changed right before I succeeded" was the critical factor involved in success.

(If the exploit relies on a race condition it could be possible to succeed in seconds ... or never at all. If that is what makes the successes random, then all the fiddling with the PC may not have anything to do with the outcomes.)

good luck

 

[Gundie]

I just happened across this thread after having problems rooting a SM-900V on NK1. Coincidentally enough, the Note 3 in question also belongs to my younger brother. (He is 50, so I will stop short of calling him my 'little' brother).

I have kept my own Note 3 rooted and am currently running Temasek CM13, but he was/is still using KK, and it has been so long that I had lost track of how to root it. I was using Arabic Tools, but it only appeared to work with OB6 and OF1.

I read somewhere that NK1 cannot be downgraded, but what I am gathering from this thread is that it is possible to just apply OB6 or OF1 using Odin then use the Arabic Tools to root? If true, that would make my weekend.

Is the best upgrade route (recognizing that best is subjective) to CM13 going to be using Odin to apply OB6 or OF1, root, unlock bootloader and apply CM13?

Thanks for any advice. I hope I am not hijacking your thread, ecrudragon, but our situations sound similar.

 

[bftb0]

I read somewhere that NK1 cannot be downgraded, but what I am gathering from this thread is that it is possible to just apply OB6 or OF1 using Odin then use the Arabic Tools to root? If true, that would make my weekend.

That is possible, yes. As you see from not only this thread but also the two Yemen threads, some people succeed at getting root (on OB6 or OF1) with those tools and some people don't The rooting method seems to be sort of fragile at best.

Before you go racing off though, remember something else: CM13 needs a custom kernel - so even if you can root, you would still need to unlock the bootloader afterwards in order to be able to boot a custom kernel. An additioinal prerequisite of the unlock method is that the CID value of the eMMC flash memory chip on the phone needs to start with 0x15 (indicating manufacture by Samsung)

==> You don't need to be rooted to check the CID value - just download the "eMMC Brickbug (Vinagre)" app to find out what your CID value is before you do anything else. If you are 0x11, you aren't going to get CM13 running whether you can root or not. Only a little value in rooting if you can't unlock the bootloader IMO.

Is the best upgrade route (recognizing that best is subjective) to CM13 going to be using Odin to apply OB6 or OF1, root, unlock bootloader and apply CM13?

Yes, more or less. "best" here really only means "the only way that is available without developing some brand new rooting method".

The incrementing of the firmware anti-rollback occurs at certain trip points, which appear to be the releases: MJ7, NC4, and NK1.*

You can not revert backwards prior to the nearest previous (to your currently installed release) of any of these three. Of course, you can always flash forward - possibly going beyond and establishing a new trip point.

(* Because of a lack of reporting, It is possible that NJ6 is the actual trip point, meaning that someone on NK1 could Odin flash back to NJ6 at the earliest. Unfortunately, after I put together all those recovery-flashable Stock ROMs, I installed NJ6 and tried using Towelroot v3 - and no joy. It works on MJ7 through NC4, but not beyond that. So while that possibility (of Odin back-flashing to NJ6) still remains, there doesn't seem to be much of a reason to attempt it.)

For your NK1 unit, that means you can flash forward or backward at will (using Odin) among this group of releases:

NK1 OB6 OF1 PL1

At this point in time - since that device is on NK1, and there are no trip points above NK1 (yet as of 4/2/2017) you can Odin flash whatever you want within the above group.


good luck


PS Note something else that falls out of the above analysis: If for whatever reason you can't root or you can't unlock (CID starting with 0x11), it is probably the right thing to do to flash the PL1 firmware. Might as well as it has the most recent security patches available if the device is to continue to be in use as a daily driver. You can always flash back to NK1 - right where you are now - in the event of some new development or rooting opportunity.

 

[Gundie]

Thank you very kindly for all of your help bftb0, I am gratified. I remember being relieved when I ran EMMC Check and seeing the 15. I am running a tweaked kernel (and Kernel Adiutor) with CM13 now, but my brother is still on KitKat. He runs a tethering program that he apparently couldn't get to work under Lollipop, so he unrooted and went back to KK and never thought about it again. I want to get him onto CM while I am visiting him this week.

I will locate those firmwares (thank you for assembling them!) and start working. I fully agree about PL1 - worst case scenario, I would like to see him there. I'll find another way for him to do his damned tethering even if I have to buy him a hotspot.

Major thanks again,

G

 

[ecrudragon]

Dear @bftb0 didn't read a word you said, kidding read everything and thank you for kind answer.
Arabic Tools didn't worked for me i tried 100 times but fortunately "SM-N900V_FI_ROOTE BY Dr.Android" worked for me like a charm then i replaced Kingroot with SuperSu via some commands, running Stock LP with all the bloatware disabled. Happy now

 

[note3newbie]

Hey Guys, I'm having trouble rooting my Note 3. It is an SM-900V (verizon) on PL1. I've tried Yemen and Arabic tools, but I receive error messages on both. Yemen states "not compatible" and Arabic continues to say, 'Enable USB debugging" (which I have). From what I understand, these tools shouldn't work because I'm not on OB6 or OF1. What can I do to get rid of all this bloatware!? Help is appreciated!

 

[ecrudragon]

Hey Guys, I'm having trouble rooting my Note 3. It is an SM-900V (verizon) on PL1. I've tried Yemen and Arabic tools, but I receive error messages on both. Yemen states "not compatible" and Arabic continues to say, 'Enable USB debugging" (which I have). From what I understand, these tools shouldn't work because I'm not on OB6 or OF1. What can I do to get rid of all this bloatware!? Help is appreciated!

Oh man you're seriously messed up, there's no way until now for PL1 to be rooted whatsoever, wait n watch maybe it will come or find your own cure.

 

[bftb0]

Oh man you're seriously messed up, there's no way until now for PL1 to be rooted whatsoever, wait n watch maybe it will come or find your own cure.

Not true. He can Odin flash back to OB6 or OF1 stock firmware.

The bootloader RP SWREV flags did not increment between OF1 and PL1 (or so I am told), so there shouldnt be an issue back-rev'ing. (Kind of a surprise actually; I expect Big Red to try and screw us at every turn.)

 

[ecrudragon]

Not true. He can Odin flash back to OB6 or OF1 stock firmware.

The bootloader RP SWREV flags did not increment between OF1 and PL1 (or so I am told), so there shouldnt be an issue back-rev'ing. (Kind of a surprise actually; I expect Big Red to try and screw us at every turn.)

Oh, i thought there's no going back from PL1, if so then he can work twice as hard as i did and now i am running AryaMod 6.0.1 MM, Rooted & Bootloader unlocked, Learn learn & learn :fingers-crossed:

P.S if anybody want i can share my whole journey from rooting stock to TWRP/AryaMod MM.

 

[CZ Eddie]

Hey guys, non Note 3 user here.
My buddy has a 900V with EOF1 and is on one of the cheaper AT&T LTE alternative plans.
He's still in "official" status and has never rooted before.

I'd like to get him onto an AOSP or CM (LOS) ROM.
Can anyone recommend a super stable one where everything works?
Doesn't need to be the fastest or have most options or best battery.
Just... everything works and is better than stock.

Can anyone recommend a root/TWRP/ROM plan for me?
I won't need heavy details.
I'm a heavy flasher, familiar with ADB/Odin/Fastboot.
Just the quick details and then I can figure it out from there.

Am not however, familiar with non SuperSU rooting methods.

Would like to stay with 5.X or maybe 6.X.
Not at all interested in 7.X.

 

[akosha13]

I'm Verizon N900V on version 5.0 - Build N900VVRSERPL1 Dec 2016 update. From what I'm reading, my bootloader is locked. If I flash and roll back to OF1, OB6 or NK1, can the bootloader be unlocked? I do not use this phone as a primary phone. It's only used when connected to WiFi. It's an old phone that I want to root and don't care if any Verizon service works on it at all. Any advice? On and my CID starts with 15, not 0x11.

 

[donc113]

I'm Verizon N900V on version 5.0 - Build N900VVRSERPL1 Dec 2016 update. From what I'm reading, my bootloader is locked. If I flash and roll back to OF1, OB6 or NK1, can the bootloader be unlocked? I do not use this phone as a primary phone. It's only used when connected to WiFi. It's an old phone that I want to root and don't care if any Verizon service works on it at all. Any advice? On and my CID starts with 15, not 0x11.

You can only roll back to OF1 but yes, then it can be rooted and bootloader unlocked.


Sent from my SM-N900V using Tapatalk

 

[tbonedude]

You can only roll back to OF1 but yes, then it can be rooted and bootloader unlocked.


Sent from my SM-N900V using Tapatalk

I'm in a very similar situation and odin'd ob6... which was previously root able but not now (seeking help in my own thread aswell).

Does my device also qualify for of1? I'm pretty sure I grabbed that Img last night and for what ever reason clicked ob6 :/ as it was what I was running before.

 

[donc113]

I'm in a very similar situation and odin'd ob6... which was previously root able but not now (seeking help in my own thread aswell).

Does my device also qualify for of1? I'm pretty sure I grabbed that Img last night and for what ever reason clicked ob6 :/ as it was what I was running before.

OF1 is what you need, NOT ob6



Sent from my SM-N900V using Tapatalk