***How To ROOT 4.3 & NC4 OTA, Install Recovery & Roms - Verizon RETAIL Note 3***

[straykat]

Here's a good starting point for you!

http://www.droidforums.net/threads/...rade-your-verizon-note-3s-modem-radio.267875/

If you're not familiar with ODIN, there is an ODIN link in my sig

Thanks az_biker! I read through all that and learned some cool stuff. - one thing may help jelly head who recently posted here about poor reception with his non-rooted n3 that runs 4.4. According to those guys, he can still odin his radio back to mje...that may help him a lot. Btw, I have used odin and am pretty familiar with it.

So for me, I think I'll leave things "as-is" with my mje radio as that seems to be most people's favorite.

Do you use or have a good recommendation for a signal strength app? I found out that "real signal" wasn't accurate. I currently have xposed NetStrength and "Network Signal Info". I'm trying to keep an eye on my signal strength. One thing I know for sure is two blocks from my house is the worst coverage in our area ...lol. Verizon shares a Sprint Tower there. So, my phone definitely comes out of my aluminum phone holder there!!!

Thanks again az_biker for all your help!

 

[Az Biker]

Thanks az_biker! I read through all that and learned some cool stuff. - one thing may help jelly head who recently posted here about poor reception with his non-rooted n3 that runs 4.4. According to those guys, he can still odin his radio back to mje...that may help him a lot. Btw, I have used odin and am pretty familiar with it.

So for me, I think I'll leave things "as-is" with my mje radio as that seems to be most people's favorite.

Do you use or have a good recommendation for a signal strength app? I found out that "real signal" wasn't accurate. I currently have xposed NetStrength and "Network Signal Info". I'm trying to keep an eye on my signal strength. One thing I know for sure is two blocks from my house is the worst coverage in our area ...lol. Verizon shares a Sprint Tower there. So, my phone definitely comes out of my aluminum phone holder there!!!

Thanks again az_biker for all your help!

I've always used OPEN SIGNAL with pretty accurate results!

 

[straykat]

I've always used OPEN SIGNAL with pretty accurate results!

Thanks! I'll give that one a try.

 

[ArtfulDodger]

The Note 3 is a great phone. It IS outdated I realize, but that doesn't change the fact that you still can't enjoy it and have it do whatever you need. You all need to consider the bigger picture. There are not a lot of current phones that offer the flexibility, under right circumstances, of your what you have in your hands right now. Trust me. Even if you're willing to drop retail 700 per year on every new phone that comes out, something will plague you. Best bet is to accept limitations which all phones have and work around them.

Sent from my XT1575 using Tapatalk 2

I think hardware wise this phone is not outdated by any means, many of the new models (especially no contract) are equal to or less than this phone. They don't have the screen size, RAM or CPU this one offers. All the Samsung variants not named Note, S3, S4, S5 or S6 are complete garbage and I would know based on what I previously owned and what people I know have.

What is a reality is that this phone and many of the new ones will no longer have root capability, that is if you buy a carrier version of them. In 2 to 3 years time XDA will shrink considerably and mainly consist of OPO and Nexus users. It really is a disappointment that the carriers have been able to stay ahead of any developers here.

 

[straykat]

I think hardware wise this phone is not outdated by any means, many of the new models (especially no contract) are equal to or less than this phone. They don't have the screen size, RAM or CPU this one offers. All the Samsung variants not named Note, S3, S4, S5 or S6 are complete garbage and I would know based on what I previously owned and what people I know have.

What is a reality is that this phone and many of the new ones will no longer have root capability, that is if you buy a carrier version of them. In 2 to 3 years time XDA will shrink considerably and mainly consist of OPO and Nexus users. It really is a disappointment that the carriers have been able to stay ahead of any developers here.

AD- interesting/insightful post.... when I bought the Note 3 recently, I did so because I could buy as rooted phone and keep it that way. Needless to say, the advantages of that capability are huge. - I did not see any advantage getting a N4 or the recently released N5. (I'm fairly certain a n4 cannot be rooted.) I am very happy with the N3 and will use it for a couple years or more... when it's time to transition, it seems like the Nexus 6P is a good choice based on what I've heard from some of the guys on this thread (az_biker, Milski, etc...). I am not crazy about buying a phone that cannot be rooted and will continue to stay on the root-track as long as possible. - Btw, up until recently, I was using an S3 which was still a great phone...

 

[ArtfulDodger]

AD- interesting/insightful post.... when I bought the Note 3 recently, I did so because I could buy as rooted phone and keep it that way. Needless to say, the advantages of that capability are huge. - I did not see any advantage getting a N4 or the recently released N5. (I'm fairly certain a n4 cannot be rooted.) I am very happy with the N3 and will use it for a couple years or more... when it's time to transition, it seems like the Nexus 6P is a good choice based on what I've heard from some of the guys on this thread (az_biker, Milski, etc...). I am not crazy about buying a phone that cannot be rooted and will continue to stay on the root-track as long as possible. - Btw, up until recently, I was using an S3 which was still a great phone...

Thanks. I just got done with the old S2 variant from T-Mobile which was easily rooted but horrible hardware for today's standards, same with the Galaxy "Exhibit 4G" before that. Even up to a couple years ago the carriers weren't being so aggressive but now with ad blocking being so popular they are cracking down, plus they don't want you getting rid of their bloatware. Even the new Asus Zenfone 2 Laser has a locked bootloader as of now. I sense rooting is about to come to a slow demise for most new (even some popular old ones like this one) devices unless someone out there is smart enough to unlock the new bootloaders. You can bet T-Mobile and Sprint will soon join AT&T and Verizon. Then guess what? Phones like the OPO and Nexus will soar even further in price. I would have gotten an OPO 2 but $400 for a phone? No way.

Really I am OK with stock ROM as it is so stable but I want rid of Samsung's bloat and all the ads. Plus I miss Viper, but I guess it is what it is. I tried two different root methods and both failed of course. Wasted my time as people smarter than me couldn't get it done either.

 

[straykat]

Need a little help...

I could use some help guys... I am trying to flash Alliance b-2 and have run into a problem. I flashed the Alliance b-2 rom to the stock slot and flashed the n900v_kk_firmware.tar.md5 file via Odin; I disconnected the usb cable and meanwhile my n3 has booted into the black & white screen that says "AllianceROM - Est 2012 - "Often Imitated*Never Duplictated* - & the circle around the droids goes around & around.... - looks pretty cool, but obviously something is wrong... Pushing the power key or volume keys doesn't make anything happen...

Any advice on best next steps to get out of this would be greatly appreciated. I'm sure I could do a battery pull and reboot into recovery download mode, but thought I better wait for someone smarter than me (which is probably everyone on this thread...lol) on what to do next. Thanks for any help! :crying:

 

[Az Biker]

I could use some help guys... I am trying to flash Alliance b-2 and have run into a problem. I flashed the Alliance b-2 rom to the stock slot and flashed the n900v_kk_firmware.tar.md5 file via Odin; I disconnected the usb cable and meanwhile my n3 has booted into the black & white screen that says "AllianceROM - Est 2012 - "Often Imitated*Never Duplictated* - & the circle around the droids goes around & around.... - looks pretty cool, but obviously something is wrong... Pushing the power key or volume keys doesn't make anything happen...

Any advice on best next steps to get out of this would be greatly appreciated. I'm sure I could do a battery pull and reboot into recovery download mode, but thought I better wait for someone smarter than me (which is probably everyone on this thread...lol) on what to do next. Thanks for any help! :crying:

If you are just stuck in a boot loop, pull the batt and power up as usual. If you're still looping, see below:

Pull batt... Replace the batt. Hold power, home and vol up simultaneously. This will take you to Android recovery. Wipe cache and reboot to system. If this doesn't work, see below:

Maybe I'm too OCD, but IF you have to start over, might as well start from scratch (see OP) to ensure there are no corrupt, broken files hanging around from whatever caused the loop in the first place.

Every file you need should be at the Dev Host link in my sig!

Let me know what you decide, and how things turn out!

 

[straykat]

If you are just stuck in a boot loop, pull the batt and power up as usual. If you're still looping, see below:

Pull batt... Replace the batt. Hold power, home and vol up simultaneously. This will take you to Android recovery. Wipe cache and reboot to system. If this doesn't work, see below:

Maybe I'm too OCD, but IF you have to start over, might as well start from scratch (see OP) to ensure there are no corrupt, broken files hanging around from whatever caused the loop in the first place.

Every file you need should be at the Dev Host link in my sig!

Let me know what you decide, and how things turn out!

az_biker-

Thanks a lot for your reply. I restarted and I go right into the boot loop with the screen mentioned above. - Question: I had SS 3.65 and your directions talk about installing ss 3.75; I haven't done that yet and assume I can't until I'm up and running on this Alliance b_2. - Do I have that wrong? Should I have already installed ss 3.75? If so, how & when do I do that? - btw, it's clear that the phone is not going through safestrap at this point. Thanks again for your help!

Edit: follow-up: I hope I'm not in more trouble than can be handled! - I know these things usually have a way of working out, but as of now, I'm pretty stuck!!! - - - When pulling the battery and restarting, I get the "loop".... When doing vol. up, home & power, I get the "loop"; And when I do vol. down, home & re-flash the kk.tar.md5 file, I get the "loop"...

Can I flash via Odin the mje...stock rom? - Is that what I need to do, or is there an easier way around all this???

I'm thinking I was supposed to have put ss 3.75 on the root directory of the sd card before I started....??? I didn't do that.... there doesn't appear to be any way for me to get that on the sd card at this point...??? - Thanks for any ideas you have on getting me out of this jam!

 

[Az Biker]

az_biker-

Thanks a lot for your reply. I restarted and I go right into the boot loop with the screen mentioned above. - Question: I had SS 3.65 and your directions talk about installing ss 3.75; I haven't done that yet and assume I can't until I'm up and running on this Alliance b_2. - Do I have that wrong? Should I have already installed ss 3.75? If so, how & when do I do that? - btw, it's clear that the phone is not going through safestrap at this point. Thanks again for your help!

Edit: follow-up: I hope I'm not in more trouble than can be handled! - I know these things usually have a way of working out, but as of now, I'm pretty stuck!!! - - - When pulling the battery and restarting, I get the "loop".... When doing vol. up, home & power, I get the "loop"; And when I do vol. down, home & re-flash the kk.tar.md5 file, I get the "loop"...

Can I flash via Odin the mje...stock rom? - Is that what I need to do, or is there an easier way around all this???

I'm thinking I was supposed to have put ss 3.75 on the root directory of the sd card before I started....??? I didn't do that.... there doesn't appear to be any way for me to get that on the sd card at this point...??? - Thanks for any ideas you have on getting me out of this jam!

Best bet is to ODIN the MJE STOCK tar, then start the process over. Follow the instructions, I always suggest reading all the steps in the paragraph to be sure you understand them and don't skip any steps.

You should be good... Tired, but good

 

[straykat]

Best bet is to ODIN the MJE STOCK tar, then start the process over. Follow the instructions, I always suggest reading all the steps in the paragraph to be sure you understand them and don't skip any steps.

You should be good... Tired, but good

az-biker,

Thanks, I'll do that... 2 questions: Do I end up losing my SS 3.65 slots in doing this? Probably not that big of deal if I do; all I had was MJE rooted in Stock Rom; of course, that's before I wiped it! lol... and I had Jelly Beans b_6 in Rom Slot 1; - Will I have to redo those?

Question #2, which is what may have got me in this jam (my fault of course)... Am I suppose to install 3.75 ss instead of 3.65 on the rooted stock mje (replace it) or do they both stay on the sd card? And more importantly, do I want to install ss 3.75 on the sd card before I resume flashing Alliance b-2? I want to make sure I do this right this time! - Thanks.

 

[Az Biker]

az-biker,

Thanks, I'll do that... 2 questions: Do I end up losing my SS 3.65 slots in doing this? Probably not that big of deal if I do; all I had was MJE rooted in Stock Rom; of course, that's before I wiped it! lol... and I had Jelly Beans b_6 in Rom Slot 1; - Will I have to redo those?

Question #2, which is what may have got me in this jam (my fault of course)... Am I suppose to install 3.75 ss instead of 3.65 on the rooted stock mje (replace it) or do they both stay on the sd card? And more importantly, do I want to install ss 3.75 on the sd card before I resume flashing Alliance b-2? I want to make sure I do this right this time! - Thanks.

When you ODIN the MJE tar, you'll lose everything, you're going back to OEM stock.

Install SS 3.65 MJE first, then, upgrade 3.75 after flashing Beans KK as the instructions show, and follow the instructions exactly. .

Put all the files on the sdcard after you're back to MJE, BEFORE you start the process

 

[straykat]

az-biker,

Thanks, I'll do that... 2 questions: Do I end up losing my SS 3.65 slots in doing this? Probably not that big of deal if I do; all I had was MJE rooted in Stock Rom; of course, that's before I wiped it! lol... and I had Jelly Beans b_6 in Rom Slot 1; - Will I have to redo those?

Question #2, which is what may have got me in this jam (my fault of course)... Am I suppose to install 3.75 ss instead of 3.65 on the rooted stock mje (replace it) or do they both stay on the sd card? And more importantly, do I want to install ss 3.75 on the sd card before I resume flashing Alliance b-2? I want to make sure I do this right this time! - Thanks.

..

---------- Post added at 07:32 AM ---------- Previous post was at 07:29 AM ----------

When you ODIN the MJE tar, you'll lose everything, you're going back to OEM stock.

Install SS 3.65 MJE first, then, upgrade 3.75 after flashing Beans KK as the instructions show, and follow the instructions exactly. .

Put all the files on the sdcard after you're back to MJE, BEFORE you start the process

Thanks very much!!! I'll let you know how things go... :good:

 

[Az Biker]

..

---------- Post added at 07:32 AM ---------- Previous post was at 07:29 AM ----------



Thanks very much!!! I'll let you know how things go... :good:

No problem. I'm up for a few more hours. I look forward to good news!

 

[straykat]

No problem. I'm up for a few more hours. I look forward to good news!

az-biker-

I wish I had good news, but I don't....

I went through each & every step carefully (twice) and at the end I get stuck in the loop with the Alliance Rom Screen (Circle going around, etc...);

I use ss 3.65 to load Alliance Rom b-2; I do the wipe prior to that install... - I do the odin from desktop of N900V_kk_firmware.tar.md5

Instructions at end says "Boot into NC2 (or in my case Alliance b-2) , but I never get ss to designate that..... however, I end up in the boot-looop screen, so I would assume I'm in the stock slot at this point.

I skip the PIT step (partition stuff) per the instructions....

So, I'm not sure where the problem lies... Do you have any suggestions. - btw, I'm sure I did each & every step correctly, per the instructions.

 

[Az Biker]

az-biker-

I wish I had good news, but I don't....

I went through each & every step carefully (twice) and at the end I get stuck in the loop with the Alliance Rom Screen (Circle going around, etc...);

I use ss 3.65 to load Alliance Rom b-2; I do the wipe prior to that install... - I do the odin from desktop of N900V_kk_firmware.tar.md5

Instructions at end says "Boot into NC2 (or in my case Alliance b-2) , but I never get ss to designate that..... however, I end up in the boot-looop screen, so I would assume I'm in the stock slot at this point.

I skip the PIT step (partition stuff) per the instructions....

So, I'm not sure where the problem lies... Do you have any suggestions. - btw, I'm sure I did each & every step correctly, per the instructions.

Okay. Back to basics. What was your original OEM firmware? IF it was NC4, I think I know the issue.

 

[straykat]

Okay. Back to basics. What was your original OEM firmware? IF it was NC4, I think I know the issue.

Thanks for writing back... I was just going to resign myself to going back to Jelly Beans b-6.... I've spent way too many hours on this.... ???

btw, a couple times, after pulling the battery & rebooting, I got beyond the loop screen and got the message: "AllianceRom is updgrading" " x files of 298"
"Optimizing app x of 298;" "Starting Apps"... - But it never went beyond those messages, so it was basically stuck for some reason.

So, back to basics, I've attached a screenshot of my phone. I'm on 4.3. I'd appreciate any more ideas.

 

[Az Biker]

Thanks for writing back... I was just going to resign myself to going back to Jelly Beans b-6.... I've spent way too many hours on this.... ???

btw, a couple times, after pulling the battery & rebooting, I got beyond the loop screen and got the message: "AllianceRom is updgrading" " x files of 298"
"Optimizing app x of 298;" "Starting Apps"... - But it never went beyond those messages, so it was basically stuck for some reason.

So, back to basics, I've attached a screenshot of my phone. I'm on 4.3. I'd appreciate any more ideas.

If you were optimizing apps, you were in! Did it just take a lot of time? Sometimes it can take >15 min if you have a lot of apps.

What happened when you got to the optimizing apps? Did it start to count down the apps?

If you are starting off with MJE, I can not figure out what is wrong with your install... I thought you might be on NC4 which is a different process.

 

[straykat]

One more try!....

If you were optimizing apps, you were in! Did it just take a lot of time? Sometimes it can take >15 min if you have a lot of apps.

What happened when you got to the optimizing apps? Did it start to count down the apps?

If you are starting off with MJE, I can not figure out what is wrong with your install... I thought you might be on NC4 which is a different process.

Well, it spent 15 minutes or so in total saying, "Alliance ROM is Upgrading" - - x of 298 apps; I believe next it went to "Optimizing App x of 298"; and finally it went onto "Starting Apps" and this continued for quite a while on its own: Maybe 10 - 15 minutes (in the starting apps mode") before I gave up.... Maybe I should've waited a tad longer, huh???

Well, on the light side, I can pretty much do this process in my sleep now! lol....So, I'll give it another try to see what happens. Who knows, maybe I'll be on Alliance 2.0 in time for the year.! I'll let you know what happens. Thanks!

 

[Az Biker]

Well, it spent 15 minutes or so in total saying, "Alliance ROM is Upgrading" - - x of 298 apps; I believe next it went to "Optimizing App x of 298"; and finally it went onto "Starting Apps" and this continued for quite a while on its own: Maybe 10 - 15 minutes (in the starting apps mode") before I gave up.... Maybe I should've waited a tad longer, huh???

Well, on the light side, I can pretty much do this process in my sleep now! lol....So, I'll give it another try to see what happens. Who knows, maybe I'll be on Alliance 2.0 in time for the year.! I'll let you know what happens. Thanks!

Are you using the steps to update from 4.3 to 4.4 here http://forum.xda-developers.com/showthread.php?t=2740466

OR are you using these in the OP


* * * ATTN: PRIOR to flashing a Rom built on MJE update, you should be running MJE (take OTA update or install MJE tar via Odin) then reroot via Kingo/Vroot, install Safestrap * * *

EASY Steps To Update To MJE: (Factory Stock)
- Download MJE tar file from Beanstown106's Firmware Collection Thread
- Flash MJE tar in Odin (for added safety, REMOVE sdcard) For DETAILED Odin instructions click HERE
- Reboot
- Go To Install Kingo (Google Kingo root 1.1.5 or 1.1.6 download) or Vroot (Google Vroot)

FOR ROOT PRIVILEGES- Install KINGO/Vroot
***Kingo 1.2 is having issues Rooting MJE Firmware, Google Kingo 1.1.5 or .6 OR see HERE, OR use Vroot***
I used the Kingo root app - links to Kingo are not currently allowed on XDA but it's very easy to search and find. It's just like a "one click" toolkit - meaning it's a no-brain operation. Download the app and follow the instructions. Currently Kingo & Vroot are the only known methods to root the MJ7/MJE builds for the Verizon Note 3 so it's one of these or no root for you. IF ROOT FAILS, KEEP TRYING (it took me 3 attempts)
TIP- make sure display timeout is set for 10 minutes & temporarily disable PC anti-virus (thanks RypeDub for the catch)
***If Kingo fails to root your device after several attempts: Try Vroot (some users reported success with Vroot after Kingo failed ROOT)....................

The reason I ask is I just reread that you said you were flashing Alliance build 2 which is an NC4 based rom. IF you were doing that using the Install custom Rom on 4.3, it wouldn't work.

You have to flash a MJE cust Rom first (this OP), then you go to the (Update from 4.3 to 4.4.2 OP)