How can I tell I'm on ND2 vs NCB - Sprint Galaxy S 5 Q&A, Help & Troubleshooting

I rooted my Sisters S5 the other day and followed the directions.
The directions recommended I apply updates before.
So we did and it downloaded like a 50MB file and all went fine.
Next day I bought my S5.
I went to check for Updates and it Said no Updates. So I think it may have done it in the store or on the way home.
But I remember it being a rather explicit process.
So I rooted and then installed R.O.D.T. ROM but had not noticed he has NCB and ND2.
I installed NCB.
So how can I tell if I'm on ND2. Was there firmware that was updated as well?
I plan to reflash R.O.D.T ND2. But I want to be sure I have the correct firmware.
In the About window I see G900PVPU1AND2 (is this the firmware/radio)? And does this mean it's ND2?
Thanks for any advice for this former HTC owner and Samsung Newbie.

On that rom, the dev decided to keep the NCB radio version, but in "about phone" it saids ND2 under the build number. You have the ND2 updates, just not the radio.

Shad Stang said:
On that rom, the dev decided to keep the NCB radio version, but in "about phone" it saids ND2 under the build number. You have the ND2 updates, just not the radio.
Click to expand...
Click to collapse
So how do I get the Radio?
I just switched to his ND2 DeOdex ROM.

I don't think anyone has made a flashable radio yet. You would do it by backing up everything on an sd card, flashing the ND2 tar file, re-rooting, and restoring the data. Personally though that's not worth the effort for such insignificant changes. I would wait for a flashable radio.

Related

How I Got To a Rooted EE4

This stuff is not for the faint of heart !! Bricking a $300.00 phone is stressfull !!
Okay ... after much trial and error, this is what I did and I have what looks to me to be a stock rooted EE4. I am sure it is not stock as I used imnuts' debloated tar but that's fine, it is working and not trying to send me an update.
Okay, regardless of what I went thru to get to this point, these are the steps I took to have the phone updated to EE4 and rooted.
via Odin 3 I rolled the phone back to ED1 using the [ODIN] Stock Rooted ED1 (downgrade from ED2) [2011.05.18] file found in the Dev forum.
The phone re-booted and was again a stock rooted ED1 and it was trying to push me the EE4 update. I DID NOT update the phone OTA.
I immediately took the battery back out and went back into Odin and flashed imnuts' debloated ee4 file found at [ROM][06-10-2011] EE4 Debloated V4.2.1 in the dev forum.
When re-booting after this flash, the Samsung logo stayed on the screen for what must have been a good 8+ minutes. There was a sexy female voice that would occasionally talk to me and soothe my nerves during this process. The phone rebooted !!
After flashing I rebooted and the phone was trying to push the ee4 update to me. I went into 'about phone' and checked and what it showed was
Baseband Version
i510.06.V.EE4
SCH-I510.EE1
Build number
SCH-I510.ED1
I then went into the build.prop editor using SGS Tools and changed all instances of ED1 to EE4. I believe there are 5 of them to change.
After saving the changes I rebooted the phone. Upon re-start, I went back in and checked the build number and it is
SCH-I510.EE4
The phone is not attempting to send any system updates and it IS rooted.
I then went into it with Titanium and deleted a lot of the useless pre-installed apps.
So far so good. It looks to me like it's where I wanted it.
Dude, that's complicated. But if it works, then it works. Cant complain against that, huh?
Here is what I did.
Flash back to stock ED1 rooted. Take the OTA update, flash droidxcon's ee4 package 3, flash kejar's sdcard fix, flash imnuts debloated v4.2.1, and boom. You're rooted EE4 with EE4 basebands.
After that, I flashed Gummy.
LOL... I think it's actually less complicated than I am wordy !!!
Rollback to ED1
Flash imnuts debloated EE4
Edit build.prop
That's all there really was to it.
That gives EE4 Basebands and EE4 Build
The rest of the book was just me explaining the process I took in checking everything.
But like ya said, it's the end result that matters !!

[Q] is VRBLJ1 world ready?

I am a little confused....normal state. I installed OpenYourEyes "no wipe" version of VRBLJ1. That, as I understand it, rewrote all the partitions including the new J1 radio & J1 RPM file. I then flashed Clean Rom 4.5 and liked it but for some reason "media" was draining the battery so I have restored a nandroid I made right after the "no wipe" install.
So, a pair of questions.
1. Is VRALJ1 still a leak or has there been an OTA?
2. In one of the installs it set my phone to global and I'm under the impression it is now a global phone capable of accepting prepaid SIMs when out of the country?
junksecret said:
I am a little confused....normal state. I installed OpenYourEyes "no wipe" version of VRBLJ1. That, as I understand it, rewrote all the partitions including the new J1 radio & J1 RPM file. I then flashed Clean Rom 4.5 and liked it but for some reason "media" was draining the battery so I have restored a nandroid I made right after the "no wipe" install.
So, a pair of questions.
1. Is VRALJ1 still a leak or has there been an OTA?
2. In one of the installs it set my phone to global and I'm under the impression it is now a global phone capable of accepting prepaid SIMs when out of the country?
Click to expand...
Click to collapse
1) it's still just a leak, nobody has confirmed an actual ota update yet coming straight from verizon
2) i'm noticing on other roms based off the VRALJ1 leak, and even on the leak before, that there was a global setting as well, so i really can't state yay or nay on that
I can verify leaks work out of the country. I'm using 3 Web (Drei) in Austria right now running beans JB build 2. You still have to edit APNs though, see lair22's thread in Android Development for an excellent guide on how to do that.
Sent from me to you

[Q] Did updating to the latest CleanROM handle everything with regard to my baseband?

This is a little confusing so bear with me.
I installed CM for my S3 and ended up reflashing the modem to fix SMS. Eventually I noticed there were a lot more issues(GPS, signal, etc) with the phone and have went back to CleanRom (Stock-Root-I535VRUCML1-De-Odex-V2.zip) though the bars still seem a little low. I'm guessing I need to update my modem and I saw a few threads in the archives over at Scott's about the ML1 modem (d2vzw_ML1_modem.zip) can I just flash that file and everything will be fine?
Right now the baseband is I535VRBMB1. If I need to update it what should I update too? Also are there any good 4.4 alternatives? Could I go back to CM mod and flash this ML1 modem and have a good experience? Or are the modem issues I experience with CM mod just unavoidable?
Bump. Anyone have an answer?
MF1 is the commonly recommended latest unlocked radio/firmware. (You MB1 is clearly much older.) You can add the ML1 radio on top of this, but don't add the entire ML1 firmware (which includes the locked bootloader).
mastamoon has the MF1 firmware (which includes radio) on his ROM thread here: http://forum.xda-developers.com/showthread.php?t=2569769 I would suggest starting there, and then you can consider applying the ML1 radio-only which can be found here: http://forum.xda-developers.com/showpost.php?p=54520377&postcount=1343 (since invisiblek.org is down)...
At least this is how I understand it to be. I'm running the ML1 radio on the MF1 firmware on stock, rooted, BL-unlocked...
EDIT: Mind you, this assumes you're staying unlocked. Putting in an older FW/baseband on a locked BL phone can cause a brick. I expect you don't have this situation, as you were running CM (natively? or on safeboot?)... so you need to be clear on what you have, and where you want to go...
schwinn8 said:
MF1 is the commonly recommended latest unlocked radio/firmware. (You MB1 is clearly much older.) You can add the ML1 radio on top of this, but don't add the entire ML1 firmware (which includes the locked bootloader).
mastamoon has the MF1 firmware (which includes radio) on his ROM thread here: http://forum.xda-developers.com/showthread.php?t=2569769 I would suggest starting there, and then you can consider applying the ML1 radio-only which can be found here: http://forum.xda-developers.com/showpost.php?p=54520377&postcount=1343 (since invisiblek.org is down)...
At least this is how I understand it to be. I'm running the ML1 radio on the MF1 firmware on stock, rooted, BL-unlocked...
EDIT: Mind you, this assumes you're staying unlocked. Putting in an older FW/baseband on a locked BL phone can cause a brick. I expect you don't have this situation, as you were running CM (natively? or on safeboot?)... so you need to be clear on what you have, and where you want to go...
Click to expand...
Click to collapse
Thanks a ton. Yes I'm staying unlocked and I was running CM natively. Downgrading the radio was a fix to a problem a lot of people in my area had with CMs radio. I'll look into it more I guess. Going back to CleanRom was just an attempt to solve the problems CM seemed to be causing me.
Presently I have Cleanrom 8.2 http://forum.xda-developers.com/showthread.php?t=1832070 I'd like to go back to 4.4 since it felt like I got better battery life. So I'll take a look at some of the various things on the forum. I don't know if putting 4.4 on the S3 at this point is just going to cause issues or what exactly.

Need to activate used S5 that came with custom ROM, unrooted, etc.

**Edit: TITLE SHOULD BE ROOTED NOT UNROOTED.
I'm coming over from an S3 so I'm a bit out of touch. I tried to do some reading around. Here's the situation:
* I got a clean S5 that I need to activate on my account.
* S5 came from a friend that was rooted and running RWilco's OG1 Almost Stock ROM.
* I went into Philz Recovery and flashed the Stock OK4 zip from metalfan78 ( thread here: http://forum.xda-developers.com/spr...rom-ok4-stock-rooted-zips-12-16-2015-t3272692 )
Should I flash a TAR through Odin instead? Is OK4 what I'm looking for as far as the latest version?
I want to make sure it can be activated via phone by Sprint tomorrow, since I'm on SERO-P and online is screwing up. I also just want the stock experience straight up along with ability to get OTA updates from Sprint. I'll tinker later.
Is there something different I should be flashing? Should I care about Knox or anything? I'm not going to take this Sprint nor do I care about a warranty that's probably long expired.
The Big Question: All I want is to revert this thing back to stock everything, be able to receive OTA updates, and activate it through Sprint on the phone. I will re-root, flash custom ROMs, etc. later. How do I get there from where I'm at?
You should be able to activate on my rom, possibly rwilcos as well. If you want to go to complete stock there is a link in my OP to the stock tar file for Odin.
Thanks! It seemed much more complicated for some reason than all the S3 stuff. I guess I just have to get used to it a bit. Thanks so much!

Rooting and Custom ROM Problems

So, I'm sure I'm probably doing something incredibly stupid..
I just got my Note 5 today. I've been trying to flash a custom ROM, TEKXodus first and then Dr Ketan's ROM. I managed to get them to boot up (at least Ketans, I've been trying so long today at this point I'm not sure if I ever got TEKXodus to load).
However, after finally getting in, my SIM card isn't being detected, neither is the baseband and IMEI. The phone registers as a N290I instead of N290T.
Did I flash something wrong? Would the wrong version of recovery cause this? Kernels?
This isn't my first time rooting and flashing ROMs, but I can't figure out what I'm doing wrong this time.
Any help would be greatly appreciated.
re: N920T issues
nightfire55 said:
So, I'm sure I'm probably doing something incredibly stupid..
I just got my Note 5 today. I've been trying to flash a custom ROM, TEKXodus first and then Dr Ketan's ROM. I managed to get them to boot up (at least Ketans, I've been trying so long today at this point I'm not sure if I ever got TEKXodus to load).
However, after finally getting in, my SIM card isn't being detected, neither is the baseband and IMEI. The phone registers as a N290I instead of N290T.
Did I flash something wrong? Would the wrong version of recovery cause this? Kernels?
This isn't my first time rooting and flashing ROMs, but I can't figure out what I'm doing wrong this time.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You need to start from scratch (square one) and odin flash the
official stock Samsung N920T Tmobile Marshmallow 6.0 firmware
before doing anything else.
You can find the N920T Marshmallow 6.0 firmware here:
http://sammobile.com
Good luck,
Have a great day!
The phone came with Marshmallow already installed I believe. Either way I've currently got the stock TMobile installed now and am still having the same problem.
re: phone issues
nightfire55 said:
The phone came with Marshmallow already installed I believe. Either way I've currently got the stock TMobile installed now and am still having the same problem.
Click to expand...
Click to collapse
Perhaps your phone came with the wrong version of Marshmallow 6.0 if the phone was not new when you got it.
Either way I bet you still have NOT Odin flashed the full official stock samsung N920T 6.0 Marshmallow firmware
which can be found at http://sammobile.com
If you finally decide to do the above be sure to do a full wipe and factory data reset before you odin flash.
And forget about roms until you get the phone working properly with the stock N920T odin flash firmware.
Will definitely double check and retry that when I get off of work.
And that worked!
Thank you so much, I was working off a different MM build apparently. Probably would never have figured that out by myself.

Categories

Resources