Nandroid and baseband. - Verizon Samsung Galaxy Note II

Ok i tried to do my homework first but I am not completely sure for my given situation......
I made a nandroid backup using VRALJB. updated baseband to VRAMC3.
Questions:
can i flash to the nandroid backup i made using VRALJB?
Or will it not work because baseband is different?
What is are my options to flash back to the nandroid made with VRALJB?
Would it be a good (or even possible) option to... flash baseband back to VRALJB .......flash back to that nandroid backup.....flash back to VRAMC3.... then make a new nandroid on the new baseband?
Sorry if these questions are very basic or if i am not grasping simple problems.. trying to get the hang of this. Most of the threads i read are about other phones and i did not see one that even had the same problem.

crash613 said:
Ok i tried to do my homework first but I am not completely sure for my given situation......
I made a nandroid backup using VRALJB. updated baseband to VRAMC3.
Questions:
can i flash to the nandroid backup i made using VRALJB?
Or will it not work because baseband is different?
What is are my options to flash back to the nandroid made with VRALJB?
Would it be a good (or even possible) option to... flash baseband back to VRALJB .......flash back to that nandroid backup.....flash back to VRAMC3.... then make a new nandroid on the new baseband?
Sorry if these questions are very basic or if i am not grasping simple problems.. trying to get the hang of this. Most of the threads i read are about other phones and i did not see one that even had the same problem.
Click to expand...
Click to collapse
The libs are not compatible. If you flash back you will be on VRALJB. To be able to use the VRAMC3 you need a C3 compatible rom. Suggestion. Wipe, install a C3 compatible or C3 rom and re-setup your device. Also make sure if you use a C3 rom, update your radios to C3.

dragonstalker said:
The libs are not compatible. If you flash back you will be on VRALJB. To be able to use the VRAMC3 you need a C3 compatible rom. Suggestion. Wipe, install a C3 compatible or C3 rom and re-setup your device. Also make sure if you use a C3 rom, update your radios to C3.
Click to expand...
Click to collapse
I believe the baseband/modems are independent of the ROM. I understand VZW packages them so that they install together but when I updated to Jelly Bean 4.1.2 as an unlocked bootloader user, I was still using the I605VRAL4 baseband/modem before I performed a second flash to install I605VRAC3.
Check out this thread http://forum.xda-developers.com/showthread.php?t=2108510 as you will be presented with the 3 available baseband/modem options to flash. Post 14 of this thread is the OP indicating that he has flashed back and forth between JB and L4 baseband/modems without any negative side affects.

larry_thagr81 said:
I believe the baseband/modems are independent of the ROM. I understand VZW packages them so that they install together but when I updated to Jelly Bean 4.1.2 as an unlocked bootloader user, I was still using the I605VRAL4 baseband/modem before I performed a second flash to install I605VRAC3.
Check out this thread http://forum.xda-developers.com/showthread.php?t=2108510 as you will be presented with the 3 available baseband/modem options to flash. Post 14 of this thread is the OP indicating that he has flashed back and forth between JB and L4 baseband/modems without any negative side affects.
Click to expand...
Click to collapse
You are correct on the radio being independent of the rom but it all depends on if the OP used the feature in his recovery to back up the radio with his rom. If he backed up the radio then when he uses his nandroid it will put him back on the older radio but he can flash the new one again and will be golden.
OP, if you backed up the radio/modem with your rom in you nandroid the when you use that nandroid to go back you will be on the older radio. If you didnt back up your radio/modem with the rom in the nandroid then you will still be on the newest radio when you go back. Even if you did back up the radio in your nandroid it wont really matter, all you'd have to do is reflash it once you go back ti that nandroid. It isnt really a big deal and won't cause you any issues.
Sent from my SCH-I605 using XDA Premium HD app

Related

[Q] Question about flashing a froyo rom

I am currently running bionix fusion which i know is an eclair rom however i want to flash obsidian, my question was can i flash a froyo rom just as i would any other rom or do i have to install a kernel for 2.2 and when going back to a 2.1 rom do i have to do anything? Sorry if my question is confusing...
Flash it like anything else (depending on the rom), instructions should be in the first post, most flash just like any other rom.
In going from 2.1 to 2.2, you can use CWR to flash the new ROM. The ROMs come with the kernels. But you will want to be sure to follow the install instructions of the ROM you've selected.
Now, if you should decide to go from 2.2 back to 2.1, you will need to flash a 2.1 ROM first. If all if you is a Nandroid recovery without flashing a 2.1 ROM first, you'll have to introduce yourself to ODIN.
so i should be good if say i go from obsidian to bionix as long as i dont do a nandroid backup first thanks for the quick reply by the way
reyese24 said:
so i should be good if say i go from obsidian to bionix as long as i dont do a nandroid backup first thanks for the quick reply by the way
Click to expand...
Click to collapse
The key word there is *should*.
From what I can tell, if you do a nandroid backup & restore, you want that to be to the same version of the OS. So, you probably don't want to do a backup from a 2.2 ROM and then recover to a 2.1 ROM, or visa-versa. No harm in doing the backup, however. The thing to avoid is the recovery into the wrong ROM.
As long as you flash a ROM that includes the kernel, you *should* be fine. That said, it is possible that something could go wrong, in which case having ODIN around can save you. (It took me several hours to figure out how to get the right drivers to connect my PC to my phone using ODIN. But once I figured that out, flashing JFD on the phone takes only a few minutes. But I don't flash "in the field", only at home - so if something goes wrong, I'm in a position to repair it).
EDIT: I'm not sure why you'd want to go from a 2.2 ROM back to 2.1 if you've already ventured into the custom ROM world. If you're not happy with the Obsidian performance, you might try Onyx or another ROM, like Axura.
ScratchSF said:
The key word there is *should*.
From what I can tell, if you do a nandroid backup & restore, you want that to be to the same version of the OS. So, you probably don't want to do a backup from a 2.2 ROM and then recover to a 2.1 ROM, or visa-versa. No harm in doing the backup, however. The thing to avoid is the recovery into the wrong ROM.
As long as you flash a ROM that includes the kernel, you *should* be fine. That said, it is possible that something could go wrong, in which case having ODIN around can save you. (It took me several hours to figure out how to get the right drivers to connect my PC to my phone using ODIN. But once I figured that out, flashing JFD on the phone takes only a few minutes. But I don't flash "in the field", only at home - so if something goes wrong, I'm in a position to repair it).
EDIT: I'm not sure why you'd want to go from a 2.2 ROM back to 2.1 if you've already ventured into the custom ROM world. If you're not happy with the Obsidian performance, you might try Onyx or another ROM, like Axura.
Click to expand...
Click to collapse
Just to summarize, followed by a question of my own.
Correct me if any of this is wrong. These are the points I gathered from reading this thread.
-Ok Nandroid backup is a program which can be used to backup and at a later time restore your stock firmware, i.e. stock 2.1.
-Backing up your current 2.1 ROM is safe, restoring might get you in trouble if you don't have the correct 2.1 kernal to match.
-Any of the popular 2.2 ROMS (Axura, Macnut, Obsidian) all come with the 2.2 kernal coupled.
-Downgrading from a 2.2 ROM, and restoring your Nandroid Backup of 2.1 can get you into trouble, unless you install a 2.1 ROM first which would restore a 2.1 Kernal at the same time.
Now my question is this. How do you backup not only your 2.1 stock ROM, but your stock kernal also? If you decide you don't like custom 2.2 ROMS and want to go back down to your stock 2.1 rom and kernal, how can you avoid having to install another custom 2.1 ROM with kernal, just to be able to put your restore 2.1 back. Confusing question I know, but basically, how can you just go from a custom 2.2 rom/kernal back to your own stock restore of 2.1(ROM and Kernal), will Nandroid backup the kernal also?
SamsungVibrant said:
-Ok Nandroid backup is a program which can be used to backup and at a later time restore your stock firmware, i.e. stock 2.1.
Click to expand...
Click to collapse
Nandroid is the backup/restore component of the ClockworkMod's ROM Manager app. You can use it on any version of the ROM, not only the stock 2.1 version.
SamsungVibrant said:
-Backing up your current 2.1 ROM is safe, restoring might get you in trouble if you don't have the correct 2.1 kernal to match.
Click to expand...
Click to collapse
Backups are safe. And restoring can get you into trouble if you don't restore to the same version of the OS (more specifically, the kernal, as you've indicated) that you made your backup from.
SamsungVibrant said:
-Any of the popular 2.2 ROMS (Axura, Macnut, Obsidian) all come with the 2.2 kernal coupled.
Click to expand...
Click to collapse
For this, you have to read the notes for each build. Yes, as a general rule, the latest works are on 2.2 (which means they come with a 2.2 kernal of some kind).
SamsungVibrant said:
-Downgrading from a 2.2 ROM, and restoring your Nandroid Backup of 2.1 can get you into trouble, unless you install a 2.1 ROM first which would restore a 2.1 Kernal at the same time.
Click to expand...
Click to collapse
Yes. My trick is that if I flash ROMs, I don't do worry about nandroid. If I'm trying to customize my current ROM, then that's where I do a nandroid. But you have to do what works best for you.
SamsungVibrant said:
Now my question is this. How do you backup not only your 2.1 stock ROM, but your stock kernal also? If you decide you don't like custom 2.2 ROMS and want to go back down to your stock 2.1 rom and kernal, how can you avoid having to install another custom 2.1 ROM with kernal, just to be able to put your restore 2.1 back. Confusing question I know, but basically, how can you just go from a custom 2.2 rom/kernal back to your own stock restore of 2.1(ROM and Kernal), will Nandroid backup the kernal also?
Click to expand...
Click to collapse
Good question. I've never backed up the kernal. I only flash ones that others have provided. I'll leave that question for people smarter that me to answer. ;-)
ScratchSF said:
Good question. I've never backed up the kernal. I only flash ones that others have provided. I'll leave that question for people smarter that me to answer. ;-)
Click to expand...
Click to collapse
thanks for the info, anyone know the answer to that last question?
you flash the kernel first and then you restore nandroid for the system that ran on that kernel.
Disclaimer: I am not responsible if you brick your phone
EDIT: don't forget the radio/modem as well, it is not being backed up by NANDROID.
reyese24 said:
I am currently running bionix fusion which i know is an eclair rom however i want to flash obsidian, my question was can i flash a froyo rom just as i would any other rom or do i have to install a kernel for 2.2 and when going back to a 2.1 rom do i have to do anything? Sorry if my question is confusing...
Click to expand...
Click to collapse
Not sure if it was said AND I'm not 100% sure on this but I believe bionix (and a few others) include the kernals in there roms.
and im pretty sure you can just flash over the original fusion you were using and it will also install there kernals.
or you can scope out the bible in the development section to find a kernal.
umm ok so how do you backup your stock kernal, radio and modem?
lqaddict said:
you flash the kernel first and then you restore nandroid for the system that ran on that kernel.
Disclaimer: I am not responsible if you brick your phone
EDIT: don't forget the radio/modem as well, it is not being backed up by NANDROID.
Click to expand...
Click to collapse
So if Nandroid can be used to backup your stock ROM. Then how do you backup your stock kernal, radio, and modem?

[Q] Using Custom ROM, Restoring a Stock based Nandroid Backup

My question:
Is it ok to recover a Nandroid backup that was created on a "Stock Samsung" ROM (meaning right out of the box) while you are currently running a Custom ROM? Or do you have to flash a Stock ROM first?
Same question goes for vice-versa.
Here are the details and why I am asking.
I searched and found an answer, but the poster was not 100% sure.
I have a stock 2.2-based Nandroid backup.
I flashed Biffmod ROM.
I realized I wanted to make a backup of one of my apps from my stock environment.
So, I recovered my stock 2.2 nandroid backup.
Recovery failed in the middle, and "soft-bricked" my phone. << this is why I am asking
I don't know if that is the correct term, but it wouldn't get past vibrant screen and couldn't get into recovery mode.
Incase you're curious, I was able to get into download mode just fine so no actual Bricking here.
Khoaker said:
My question:
Is it ok to recover a Nandroid backup that was created on a "Stock Samsung" ROM (meaning right out of the box) while you are currently running a Custom ROM? Or do you have to flash a Stock ROM first?
Same question goes for vice-versa.
Here are the details and why I am asking.
I searched and found an answer, but the poster was not 100% sure.
I have a stock 2.2-based Nandroid backup.
I flashed Biffmod ROM.
I realized I wanted to make a backup of one of my apps from my stock environment.
So, I recovered my stock 2.2 nandroid backup.
Recovery failed in the middle, and "soft-bricked" my phone. << this is why I am asking
I don't know if that is the correct term, but it wouldn't get past vibrant screen and couldn't get into recovery mode.
Incase you're curious, I was able to get into download mode just fine so no actual Bricking here.
Click to expand...
Click to collapse
you should be able to
im guessing it 'didnt work' because nandoird doesnt back up the kernel i dont think so you'll need to flash a compatible kernel seperatly after for the rom you backed up
You need to odin back to stock when coming back from a CM based (biff mod). I would suggest odining this JK2 rom.
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
This is 2.2 based and already comes prerooted and has busybox. Then restore your nandroid.
Sent from my GingerZen Vibrant using XDA Premium App

[Q] Back to GBE after ICS 3.11.605.22?

I've had bluetooth streaming problems with EVERY ICS custom ROM that I've tried before and after 3.11.605.22, and while on the stock RUU itself. I want to get back to a GBE based ROM, on stock firmware but I wonder how it's going to work after having flashed the 3.11.605.22 RUU.
Has anyone gone back? Is it even possible to get back to the previous firmware, or am I SOL?
I assume that a simple nandroid restore is now out of the question (and probably won't fix the bluetooth problem) given the firmware changes with the RUU
nukeboyt said:
I've had bluetooth streaming problems with EVERY ICS custom ROM that I've tried before and after 3.11.605.22, and while on the stock RUU itself. I want to get back to a GBE based ROM, on stock firmware but I wonder how it's going to work after having flashed the 3.11.605.22 RUU.
Has anyone gone back? Is it even possible to get back to the previous firmware, or am I SOL?
I assume that a simple nandroid restore is now out of the question (and probably won't fix the bluetooth problem) given the firmware changes with the RUU
Click to expand...
Click to collapse
it actually is just that simple, flash your GB nandroid and/or ROM the GB kernel.
you will need to flash this file after flashing back to your nandroid/ROM in order for rom to see SD card.. same fix was applied with old firmware to have sd seen on ics roms. its just doing the reverse.
http://www.mediafire.com/?3b1t2y9i11onm41
andybones said:
it actually is just that simple, flash your GB nandroid and/or ROM the GB kernel.
you will need to flash this file after flashing back to your nandroid/ROM in order for rom to see SD card.. same fix was applied with old firmware to have sd seen on ics roms. its just doing the reverse.
http://www.mediafire.com/?3b1t2y9i11onm41
Click to expand...
Click to collapse
Similar situation. Completely unacceptable power draw is frying my battery on the leak. I'm afraid I'm going to cook my phone, and USB charge can't keep up with the drain unless I put it in airplane mode. I have good nandroid backups of the current OTA release (released February, I think?) but I don't know where to get suitable GB kernel or how to install it. Can you explain?
andybones said:
it actually is just that simple, flash your GB nandroid and/or ROM the GB kernel.
you will need to flash this file after flashing back to your nandroid/ROM in order for rom to see SD card.. same fix was applied with old firmware to have sd seen on ics roms. its just doing the reverse.
http://www.mediafire.com/?3b1t2y9i11onm41
Click to expand...
Click to collapse
Thanks. I'll have to give it a try. So you say I should flash a previous backup / ROM from recovery, then flash the kernel (if it doesn't flash as a part of the ROM installation)
nukeboyt said:
Thanks. I'll have to give it a try. So you say I should flash a previous backup / ROM from recovery, then flash the kernel (if it doesn't flash as a part of the ROM installation)
Click to expand...
Click to collapse
yea do the exact same thing you would do as if you are on still on the old firmware.
the ONLY thing you do differently, is flash the .zip file I attached in my other post anything AFTER flashing the new GB ROM/ and/or old backup.. and kernel(in hboot) if not included in ROM.

Restoring to Stock from CM10 (Whats the Final Word?)

Hey guys,
Wanted to get a sure answer.
Whats the safest way to restore back to the stock firmware fro CM10 (or any rom in general).
There are two answers that i seem to have come across.
Answer 1:
Just download the stock firmware. Extract tar. Load onto PDA, check auto reset the flash reset and then start. Boom done! Everything reverts to stock, modem, firmware, kernel, etc.
Answer 2:
YOU MUST first flash stock kernel. So flash that first via odin then open odin again and flash the rom. If you don't flash the stock kernel first and then just flash the stock firmware, you'll have some issues.
As you can see, both are a bit contradicting. Whats the right method?
You missed one.
Make a nandroid of your stock ROM. then once you're done checking out CM or whatever else, just restore that. A lot less headache.
Docavelli said:
You missed one.
Make a nandroid of your stock ROM. then once you're done checking out CM or whatever else, just restore that. A lot less headache.
Click to expand...
Click to collapse
Yep, nandroid is much much faster. In fact I went to lunch today and restored my CM10 nandroid to show a friend. 10 minutes later I was back to my Samsung ROM. Its much easier than flashing stock, then re-rooting, then loading all your apps and data back on.
I had heard that nandroid restores between stock/CM9/CM10 were causing bugs, or something of the sort.
If it really is working that easily, I might have to give these CM9/CM10 builds a try. I just didn't want to play around with it for a bit and then be forced to set up my stock configuration all again, because I do have a need for a certain level of stability.
Edit: Ah, I was thinking of our Verizon version however. I think it might require an Odin flash back to stock, then you can restore a stock nandroid backup.
While I can't guarantee you won't have problems, I can say that I haven't had any issues while restoring nandroids.
*your experience may differ.
XDA Mobile
What version of CWM or TWRP is working fine for nandroid backup and restore, specially for Tmo version?
Sent from my SGH-T999

[Q] Need Help Not sure where to post

I bought a note 3 thats rooted already and ive rooted a device before but this root or maybe the kitkat version does not give me 4glte i currently have lidroid official v1.5.1 it has a lot of features i like anything similar that comes with kitkat 4.4.4? i tried the freze rom and its not letting me load it to the phone for some reason any help or input is appreciated thanx
P.Dub said:
I bought a note 3 thats rooted already and ive rooted a device before but this root or maybe the kitkat version does not give me 4glte i currently have lidroid official v1.5.1 it has a lot of features i like anything similar that comes with kitkat 4.4.4? i tried the freze rom and its not letting me load it to the phone for some reason any help or input is appreciated thanx
Click to expand...
Click to collapse
It appears you are running an outdated version of this rom here http://forum.xda-developers.com/showthread.php?t=2485607 if you like the rom down load the latest version and flash with odin. Who is your carrier ? This rom is for SM-N9005 which is AT&T ? As far as 4G LTE go settings/general/system update/update PRL then power down and reboot the device.
If your on a Sprint carrier I would get back to stock NC5 rooted, this thread will answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
jimzweb1 said:
It appears you are running an outdated version of this rom here http://forum.xda-developers.com/showthread.php?t=2485607 if you like the rom down load the latest version and flash with odin. Who is your carrier ? This rom is for SM-N9005 which is AT&T ? As far as 4G LTE go settings/general/system update/update PRL then power down and reboot the device.
If your on a Sprint carrier I would get back to stock NC5 rooted, this thread will answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
Click to expand...
Click to collapse
yea i have sprint and already tried to update the prl i tried another rom with kitkat4.4.4 and it gave me 4glte but it kept crashing on me so switched back im going to take a look at the link you suggested thanx
P.Dub said:
yea i have sprint and already tried to update the prl i tried another rom with kitkat4.4.4 and it gave me 4glte but it kept crashing on me so switched back im going to take a look at the link you suggested thanx
Click to expand...
Click to collapse
This is what I would do. First odin flash back to NC5 stock unrooted. Then boot into stock recovery and do a factory reset. Next odin flash NC5 stock unrooted .tar again, then boot into download mode it should look like this
with official on both lines, sometimes it shows official on one line and custom on the other. That will give you headaches later. Now go ahead root, and install a recovery, beloat the stock rooted rom, for use as a daily driver, and make sure nothing crashes. Next make a backup so you have base to work from. Follow the instructions on the thread I listed above. I know this seems like a pain, but somewhere part of that AOSP rom is being left behind and causing your install of a stock rom to crash.
So I searched and found a ROM its nice and simple but now WiFi doesn't work ?
Sent from my SM-N900P using XDA Free mobile app
P.Dub said:
So I searched and found a ROM its nice and simple but now WiFi doesn't work ��
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Well thats no good!!! What are you looking for in a rom functionality for customization? Touch wiz or some like CyanogenMod? Can you upload a screenshot of what your device is running? Like 4.4.2 or 4.4.4? Do you have custom recovery?
Goat1378 said:
Well thats no good!!! What are you looking for in a rom functionality for customization? Touch wiz or some like CyanogenMod?
Click to expand...
Click to collapse
I want something similar to what I have. The rom I just tried was the cyanogen and wifi didn't work with it and it kept rebooting after an 1 hr of trying it on my phone.... main reason I want to switch is to get the 4glte I like the ability of not holding down the buttons to go into recovery
Sent from my SM-N900P using xda app-developers app
P.Dub said:
I want something similar to what I have. The rom I just tried was the cyanogen and wifi didn't work with it and it kept rebooting after an 1 hr of trying it on my phone.... main reason I want to switch is to get the 4glte I like the ability of not holding down the buttons to go into recovery
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
So you like aosp roms? Ok are you on NC5 or NH7? The screenshots in my last post will show you what you look for under setting/general/about device
Yes custom recovery I believe. And 4.4.2
Sent from my SM-N900P using xda app-developers app
P.Dub said:
Yes custom recovery I believe. And 4.4.2
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Do you have a pc with odin?
Yes sir I do
Sent from my SM-N900P using xda app-developers app
P.Dub said:
Yes custom recovery I believe. And 4.4.2
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Do you want update your firmware to NH7 or stay NC5?
Would like to update. I would need a new rom correct?
Sent from my SM-N900P using xda app-developers app
P.Dub said:
Would like to update. I would need a new rom correct?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Hey Pedro,
I put together this post when helping another person out on another thread. I think it'll work as a step-by-step guide for you:
I'll explain how to install a custom ROM and some common things to think about/check prior to installing anything:
Installing a Custom ROM
Step 1 - Gather Information
First off, you need to know what version of Android your phone currently is running. This is easily done by looking in the Settings Menu -> General -> About Device.
The Main things we are looking at on this screen are Software Version, Model Number, Android Version, and Baseband Version. I'll explain these (to the best of my knowledge) below:
Software Version:
This is the "type" of Android that you're running. Rather than quoting the entire name, we typically only refer to the last 3 characters (MJ4, NAB, NC5, etc.). Stock Note 3 devices will (most-likely) be running one of 3 different versions of TouchWiz (TW):
MJ4 - This is the last Jellybean version of TW for the Sprint Note 3​NAB - This is the first KitKat TW version for the Sprint Note 3​NC5 - This is the second KitKat TW version for the Sprint Note 3​NH7 - This is the latest KitKat TW version for the Sprint Note 3​
The reason that we are concerned with the Software Version is that between the MJ4 and NAB versions, there were major changes. So if you're running MJ4, you will have to do additional steps before flashing a custom ROM based on a newer version. And if you're on NAB or NC5, you will not be able to go back to MJ4, so beware what you're flashing.
For the most part, if you're on NH7, you can flash either a NH7 or NC5 custom ROM, but just read the ROM's FAQ to see if there are any issues with doing so.
Model Number:
Most people don't worry about this, but I always do when looking at a new ROM. The Sprint Note 3 is different from the Verizon Note 3, which is also different from the International Note 3. It's always best to double-check that the ROM you're trying to install is truly meant for your device. This simple check will prevent a LOT of potential issues you'll get when installing a ROM.
Android Version:
This is just an additional check to the Software Version. Always best to know.
Baseband Version:
The Baseband is, unless I'm mistaken, the "kernal" for the phone's cellular and 4G radios. Sometimes upgrading (or downgrading) the Baseband can help with signal strength and reception. Some users have noted that they got better reception on older Baseband versions. I haven't personally looked into it and the reports from other users seem somewhat anecdotal, but it's good to know which Baseband you're on.
The Baseband is independent from the ROM version, so you can run an older Baseband (MJ4 or NAB) on a newer ROM (NC5), and vice-versa.
The last bit of information you need to know is the Bootloader Version. The way to find this information is to reboot your device. When you see the text on the screen, you should look for the Bootloader Version. It'll be a long string of characters, but you're only looking for the last 3 (MJ4, NAB, or NC5).
Once you have all the above information, you should be ready to start the fun process of preparing your phone to flash your first ROM.
Step 2 - Backup your Media
First thing: Backup all of your media to your computer. If there's pictures/music/videos/recordings you don't want to lose, back them up. It's just good practice. Don't lose all your cat pictures because you flashed something and it somehow erased your internal storage. I tend to keep everything of importance on the External Storage, but there are times where even external storage can be wiped, so it's best to back up everything to a PC.
Step 3 - Upgrade your Phone to the latest Stock ROM (NH7)
This only is a MUST applies if you're running an older version and want to install a NH7 ROM. Most continually-developed ROMs are either NC5 or NH7 now, so the first things first: Update your phone to NH7.
Go over to micmar's thread and download the One-Click File. It will remove Root, but don't worry, because when you install a new ROM, it will automatically include root access.
Follow the instructions in his thread and your phone will now be fully upgraded.
At this point, your "About Device" should show the following:
Software Version: N900PVPUCNH7
Android Version: 4.4.4
Baseband Version: N900PVPUCNH7
Reboot your phone and let it sit for a minute so it can get it's bearings.
Step 4 - Install a Custom Recovery
So far, we've been flashing everything in ODIN. Now, we're going to use ODIN one last time to flash a custom recovery, so that you can flash custom ROMs without the need of a computer.
The most-commonly used Custom Recovery is TWRP (XDA Link). You'll want to use the latest version, 2.8.0.
Flash this in ODIN. You should use the "PDA" or the "AP" Slot.
Reboot your phone to make sure it works correctly.
Step 5 - Make a Nandroid Backup of your device
If you don't know what a Nandroid backup is, don't worry. It's basically just taking your phone as is and making a backup of it. In case you make a mistake or flash a bad download of a ROM, this allows you to restore your system. I always keep my backups on the External Storage (microSD Card), so in case I have to wipe my internal storage, it's not a big deal. You can also copy the files over to your PC, just to be more paranoind about your nandroid backups (rhyming is fun!).
You do this by restarting into Recovery (power down device, hold down home button and volume up while powering on phone).
Once in TWRP, go to "backup." Make sure the storage selected is "external storage." This screen will have various options of what to backup. I typically choose everything except external storage. Typically, backups range from 1-2 Gigs.
For me, backups typically take 5-10 minutes to do. In my opinion, this is totally worth it, since I can always restore a backup with no issues.
Step 6 - Install a Custom ROM
Once you choose your custom ROM from the Development Section, follow the instructions on the original post to install it. I'll give a general outline of what I do whenever installing a new ROM, but sometimes a custom ROM will have specific instructions, so you want to make sure to read the posts carefully.
Generic Instructions for Installing a ROM:
Download ROM and check the md5
Internet being spotty in my area, I always check the md5 to make sure that the file downloaded correctly. You can check the md5 using this windows program or using a file explorer on your phone like ES File Explorer. I always copy the ROM zip file to my external SDcard.
Reboot to Recovery
Wipe Data, System, Cache, and Dalvik Cache
This is called a "Clean Wipe," meaning it will wipe out your installed Apps and the data associated with them. Some people will claim that "Dirty Flashing" (i.e. not wiping the above) is OK, but I've seen too many apps Force Closing (FC-ing) when dirty flashing. Also, if you dirty-flash and encounter an issue with a ROM, the first piece of advice is to do a clean install. Might as well do that initially and hopefully not run into any issues.
Install the Custom ROM
Pretty straight-forward on how to do this... just click "Install" and then browse to the place your copied the ROM zip file.
Reboot your phone and run through the typical initial start-up information (google account, etc).
Once you get your phone set up the way you like (apps, accounts, wifi passwords, etc), I'd make another Nandroid backup, just so you have one where it's setup with everything you need. This will make any issues less painful, since you'd restore a backup that's already setup.
Step 7 - Further Considerations
If you ever want to try a new ROM, all you have to do is repeat step 6. Beware, though, people easily become flashaholics when they first figure this stuff out.
If you were paying attention to my "Generic Instructions" when installing a ROM, you'd notice that every time you do a Clean Install of a ROM, you lose all your apps... All of your Angry Birds 3-Star levels are gone!
Well, there are ways to get prevent losing that data... One is by "Dirty Flashing" (Not wiping the "system" or "data" partitions before flashing a ROM in TWRP). This is common practice among users here on XDA, but is typically frowned upon by ROM devs. I've noticed that a good number of issues on ROM threads stem from people Dirty Flashing. It typically causes more problems than it solves.
The other way of backup up and restoring app data (prior to wiping) is by using Titanium Backup. I could write up a long post on how to use Titanium Backup (TiBu), but the main things to remember are the following:
White line items are fine to be restored (both Data and Apps).
Restoring Yellow line items is typically OK (Data only).
Restoring system apps or data (red line items in TiBu) is typically a bad idea.
I've been using TiBu for the past 2-3 years and it's typically worked like a charm. Sometimes, when there's a major Android Update (like from JellyBean to KitKat), it can become broken, but the Developer is really responsive and gets it to work within a few weeks. If you upgrade to PRO, you can schedule automatic app backups (I backup all my user apps every night at 3am). You can also restore apps/data from Nandroid Backups (which is great if you do a Nandroid backup but had forgotten to update your TiBu backups).
In Summary
Whew, that was a lot to write... I'm a Structural Engineer, not a Software Engineer, so I don't know the technical side of things like bootloaders or basebands, but hopefully none of the information I provided was false.
Anyways, let me know if you have any problems with the install. I appreciate any feedback!
Click to expand...
Click to collapse
Since you're looking for AOSP ROMs, I'd recommend looking into this section of the forums. You need to make sure whichever ROM you are looking into works for the Sprint version of the phone (HLTESPR).
Alright so I used the last posts links and upgraded to 4.4.4 but now my data doesn't work

Categories

Resources