Passing Row Index of TableViewCell (custom) to another view controller [on hold]

There are several problems with your code.

First, you should use more descriptive names for your instance variables/properties.

 @interface firstViewController : UIViewController <UITableViewDataSource, UITableViewDelegate>

Class names in Cocoa are conventionally named with a prefix in capitals followed by the name of the class in TitleCase.

 @property NSMutableArray *MasterRecords;   //  Each element in Array is dictionary. 

Names of instance variables and properties should be in camelCase.

    static NSString *columnIdfer = @"items";
StudentCell *cell = (StudentCell *)[tableView dequeueReusableCellWithIdentifier:columnIdfer];
if ( cell == nil)
{
    NSArray *nib = [[NSBundle mainBundle] loadNibNamed:@"StudentCell" owner:self options:nil];
    cell = [nib objectAtIndex:0];
}

You should register the nib of your cell before using your table view. This eliminates the need for instantiating a cell yourself every time it's need, and also does away with if (cell == nil), as dequeueReusableCellWithIdentifier: will always return a valid cell, provided you set the table view up properly. Proper code with these things in mind would be:

- (void)viewDidLoad
{
    [super viewDidLoad];
    . . .
    [self.tblMasterTable registerNib:[UINib nibWithNibName:@"StudentCell" bundle:nil];
}

- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath
{
    StudentCell *cell = (StudentCell *)[tableView dequeueReusableCellWithIdentifier:@"items"];
    . . .
    return cell;
}

- (IBAction)btnSubmitPressed:(id)sender {
    NextViewController *sVC = [[NextViewController alloc]     initWithRecIndex:@"NextViewController" bundle:nil Index:self.iRecordIndex];
    // Pushing NextViewController to NavigationViewController.
}

Following the MVC pattern, your view should know nothing about your controllers. You could reimplement the above using a view controller as the cell's delegate, passing a suitable identifier in a suitable method. The delegate view controller could then manage instantiating and presenting/pushing other view controllers.

- (id)initWithRecIndex:(NSString *)nibNameOrNil bundle:(NSBundle *)nibBundleOrNil  Index:(NSInteger )iRecIndex;

Several problems with this. You're specifying the return type as id, but I assume it always returns a NextViewController. As suggested in the comments, current practice is to use instancetype as the return type instead of id. For more information on id vs instancetype check this answer out.

You do not attempt to make a distinction between RecIndex and Index in the method name. The argument names do not match what the method name tells us. The implementation of this method doesn't help matters.

-(void) viewWillAppear:(BOOL)animated
{
//Get FistViewController.   say  ==> fvc.

NSMutableArray *mRec = [fvc MasterRecords];
NSMutableDictionary *mDict = [mRec objectAtIndex:self.iRecordIndex];

NSLog (@" value1 is %@ ", [mDict valueForKey:@"value1"]);
NSLog (@" value2 is %@ ", [mDict valueForKey:@"value2"]);

// Using value1, and value2 to display MKMapView.
}

Inconsistent spacing. Make up your mind about how you want to space out your method implementations/declarations and use that style consistently throughout your code.

CodeReview does not appreciate pseudo-code. Please post all relevant bits of code.

Again, instance variables are badly named. Use more descriptive names.

This view controller should not know much about it's presenting view controller.

It should declare properties for the information it needs to get from its presenting view controller. The presenting view controller can then set these properties up after instantiating but before presenting this view controller.

NextViewController *vc = . . .;
vc.mRec = . . .;

[self.navigationController pushViewController:vc animated:YES];

Or in the prepareForSegue: method if using storyboards.

Your "next view controller" shouldn't have to know anything about the view controller presenting it ("first view controller"). You should consider just passing your view model to the "next view controller". Also, consider passing something more concrete than just an NSDictionary as your view model.

View models are used to represent the thing you are displaying in the view layer. They typically look something like this.

@interface CatViewModel : NSObject
@property (nonatomic, strong) NSString *name;
@property (nonatomic, strong) NSString *breed;
@property (nonatomic, strong) NSDate *dateOfBirth;
@property (nonatomic, strong) NSArray* treats;
@property (nonatomic) BOOL canHasCheezBurger;
@end