yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] vipersinu2:
I have note3 n900p 4.4.2 kitkat, I did reboot nvbackup I now am in boot loop, I odin stock rom, and rooted, and have twrp recovery, b/c I am on boost mobile, I have to downgrade the modem.tar, to get the radio to work, so I did not downgrade modem yet so it is not rebooting I can work on phone, when I downgrade it starts to boot loop, I read all these pages in forum, using efs pro 2.1.5 backup are coming back 0 mb in size and corrupt, I do not know where to find mmcblk0p17 & mmcblk0p18, can anyone help?

##data# not working, I can view there is no meid imie baseband unknown

##3424# not working either stuck on mtp adb

would kies help this problem?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Post or send me the 1st 6 lines of mmcblk0p18. You can use notepad. Then I can confirm the problem and help you fix.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] vipersinu2:
ok I will google how to get the 1st 6 lines of mmcblk0p18, B/c I not sure how to get that information. I will post back thank you.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Just read the 1st post in this thread. It's at the bottom of 1st post.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] vipersinu2:
is this correct?

EFS Professional 2.1.8 or 2.1.5 will not backup any files, it give me a zip.tar file but the file size is 0

I remember that the nvm and efs folders were lock on the sprint note 3 probably why I cant get a read on efs
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] vipersinu2:
/dev/block/platform/msm_sdcc.1/by-name:

lrwxrwxrwx root root 1970-01-17 21:20 aboot -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 1970-01-17 21:20 apnhlos -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 1970-01-17 21:20 backup -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 1970-01-17 21:20 boot -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 1970-01-17 21:20 cache -> /dev/block/mmcblk0p24

lrwxrwxrwx root root 1970-01-17 21:20 carrier -> /dev/block/mmcblk0p25

lrwxrwxrwx root root 1970-01-17 21:20 dbi -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 1970-01-17 21:20 ddr -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 1970-01-17 21:20 efs -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 1970-01-17 21:20 fota -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 1970-01-17 21:20 fsc -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 1970-01-17 21:20 fsg -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 1970-01-17 21:20 modem -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 1970-01-17 21:20 modemst1 -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 1970-01-17 21:20 modemst2 -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 1970-01-17 21:20 pad -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 1970-01-17 21:20 param -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 1970-01-17 21:20 persdata -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 1970-01-17 21:20 persist -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 1970-01-17 21:20 recovery -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 1970-01-17 21:20 rpm -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 1970-01-17 21:20 sbl1 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 1970-01-17 21:20 ssd -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 1970-01-17 21:20 system -> /dev/block/mmcblk0p23

lrwxrwxrwx root root 1970-01-17 21:20 tz -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 1970-01-17 21:20 userdata -> /dev/block/mmcblk0p26

shell@hltespr:/ $
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] lyriquidperfection:
Hi I am the author of EFS Professional. What version of busybox are you using?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] vipersinu2:
busybox is 1.20.2
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] lyriquidperfection:
Are you able to backup other partitions okay or is it just one particular partition causing issues?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] vipersinu2:
screen shot of winhex /dev/block/platform/msm_sdcc.1 /mmcblk0p18 and mmcblk0p17,
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] vipersinu2:
I tried all partitions. but it will save partitions on the l710 without any problems.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] lyriquidperfection:
Sounds like a device specific issue then. Maybe a locked bootloader preventing reading the partitions.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] vipersinu2:
Screenshots of n900p not backing up efs .zip.tar size 0

Screenshots of n900p not backing up efs .zip.tar size 0, pretty sure I did everything correct?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
I tested the latest EFS Professional, and backup works for me.

One thing that could cause problems is if you leave all the boxes checked.The backup gets huge, mine usually chokes above 23. Try doing a backup of just: 11, 12, 13, 17, and 18 to start with.

I also save to external Sdcard
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] vipersinu2:
Radionerd you are a genius backing up 11,12,13,17,18 worked I have a zip.tar with files in folder.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Tips on how to get the clean FSG in

There are many ways to replaced the two corrupt mounts (mmcblk0p17, and mmcblk0p18). If you are familiar with adb or push/pull commands, go for it. Using any method you might run into problems with permissions, ROOT, USB debugging, or other hoops to be able to copy & paste.

I recommend that you make two folders on your external sd. One for your backup of original FSG , and the other folder paste the clean FSG. If your stuck in bootloops, just remove the sd and hook it to a sd card reader on the computer. Make folder "bakfsg" later you will copy your existing FSG here. Make a second folder "cleanfsg", and place the clean FSG into it. Copy your original mmcblk0p18 to bakfsg folder, and then copy the cleanfsg mmcblk0p18 and overwrite the corrupt one. That's it.

TWRP and CWM Recovery programs have file managers:

TWRP file manager, is under Advanced, File Manager: Goto /dev/block/mmcblk0p18 press on mmcblk0p18 to open options, press "copy file" now go (Up A Level) goto external sd, (/external_sd/bakfsg) Press select, then paste. Now do the opposite, goto cleanfsg, Copy clean mmcblk0p18 to /dev/block ,paste, Done.

PhilzCWM has the Aroma plugin that is easy to use.

In Aroma I see the blocks (mmcblk0p17, and mmcblk0p18) in folder /dev/block/platform/msm_sdcc.1 (copy originals to safe place, then copy clean to same folder and over-right your original. It will prompt: "overwrite?" Yes... Done

Root Explorer If you are lucky and can get past boot. Root Explorer worked easy for me. (I have the $4 paid version from speed software, not tested on free versions)

goto preferences "show hidden files" is checked Root Explorer will ask for root, grant root.

goto external_sd (+) make a new folder "bakfsg"

make another folder "cleanfsg"

goto root, then /dev/block mmcblk0p17 and 18 should be visible. (If not, look in /dev/block/platform/msm_sdcc.1)

check both boxes, then go back to folder "bakfsg", press "copy here". Now you have a backup, just in case.

At this point you can copy the backup to computer for safe keeping and paste the clean FSG onto the SD card.

copy the clean / paste it on top of the existing /dev/block It will prompt "Overwrite?" yes. My phone blinked and IMEI was restored without even rebooting.

ADB

A great guide on how to backup your mounts using adb.

http://xdaforums.com/showthread.php?t=2450045

Backup your existing mounts (put in path to your sdcard, and make a folder bakfsg)

Send original FSG and backup blocks to ext-sd

adb shell
su
dd if=/dev/block/mmcblk0p17 of=/external_sd/bakfsg/mmcblk0p17
dd if=/dev/block/mmcblk0p18 of=/external_sd/bakfsg/mmcblk0p18

Send clean FSG to /dev/block from sd folder cleanfsg

adb shell
su
dd if=/external_sd/cleanfsg/mmcblk0p17 of=/dev/block/mmcblk0p17
dd if=/external_sd/cleanfsg/mmcblk0p18 of=/dev/block/mmcblk0p18
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] codecxbox:
Check if your EFS folder is there first.I had the same problem and

the problem was that the EfS folder was not mounted therefore EFS Professional always retrieved a 0 EFS file.

Do this

ODIN a stock rom

Go to the Samsung Recovery and check if you have a EFS not mounted illegal argument

If you have this then download the Fire script and replace 12 with 11

Then ODIN Chenguas CWM and use the sideload function

Go to command prompt and CD to your ADB folder

Then copy the fire script and execute adb sideload each line of the script

Then reboot the cel and the EFS error should be gone

ODIN cf autoroot

Now you will be able to go the Android OS

Download ES File Manager and slide for Root and hidden files

Then copy Radionerds 17 and 18 file to /system/dev/block

Thats it! Imei and baseband will appear.

---------- Post added at 08:33 AM ---------- Previous post was at 08:30 AM ----------

I would like to suggest the EFS Pro dev to include a modified fire script within the app to clean the EFS mount error..it seems to happen when a incorrect firmware formats incorrectly the phone storage.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] lyriquidperfection:
I have just had a look at the fire script and it doesnt overwrite mmcblk0p12 with 11 it simply reformats and recreates the mount.

I have an option already in EFS Pro on the restore tab to Format EFS. If you boot into recovery after starting EFS Pro and click the Format EFS button, it should do the same thing.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] codecxbox:
Thats the idea, to reformat and correcty format the EFS parttition.

I know tbere is a Erase EFS option in your app, however, it just stays grey, cant be checked.

Everything works, but not function never ticks on
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] lyriquidperfection:
No its not a checkbox its an actual button just above the restore button in the restore options group. That does what you are asking.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] vipersinu2:
Did a stock odin, went to recovery vol+,home key,Pwr, same time brought me to stock recovery with no errors.

maybe mmcblk0p17, and mmcblk0p18 is not writing properly or the permissions are not correct
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] codecxbox:
Where did you get 17 and 18? it cant be from your own backup. The files I have were donated by Radio and I root copied to /dev/block

---------- Post added at 12:38 AM ---------- Previous post was at 12:36 AM ----------

This is done in recovery? we really need a guide on using your app, which is perhaps the best dev app for samsung
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] lyriquidperfection:
Yes as long as you can use adb on your device it will work and I know Samsung devices have adb enabled in recovery. I will put together a proper guide at some point but at the moment I am updating EFS Professional to support non Samsung devices.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] vipersinu2:
Oh my, I got it fixed just now PhilzCWM Aroma plugin did the trick of coping the mmcblk0p17, and mmcblk0p18 file.

twrp, and root explorer would not copy files properly.

I would like to thank all of you for taking time for your thoughts and Ideas.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] codecxbox:
This should be recapped and stickied...
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] fatalfury:
ok i put the wrong NVM on the n900v 4.3 how can i put the original nvm on this phone the phone keeps boot looping io tried restoring rom via odin no go
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
First make backups of your existing mounts From Recovery. So you don't get stuck any worse, use adb, or recovery file manager.

adb shell
su
ls -l /dev/block/platform/msm_sdcc.1/by-name/

After you make backups

Use recovery file manager to copy contents of /efs to extsd, then delete folder /efs

then

mke2fs /dev/block/mmcblk0p11
mkdir /efs
~ # mount -t ext4 /dev/block/mmcblk0p11 /efs

reboot

Some other tips:

Did you follow instructions from this thread? Try to oden back to stock http://xdaforums.com/showthread.php?t=2483380

Try to get into safe mode

EFS pro has NV tools. http://xdaforums.com/galaxy-s2/orig-development/tool-updated-08-12-13-efs-professional-t1308546

Good luck
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] ownmart:
here's my corrupt N900T how do I clean it up
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
I sent you a PM
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] ownmart:
lifesaver, it worked 900T fixable.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Glad you got your phone working! Thank you for confirming that just fsg needs to be replaced.

Can you post you're steps taken to replace corrupt fsg?

Cheers!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] ownmart:
sure thing, what I did was:

loaded twrp (newest) went to file manager

copied the 2 corrupt files, posted here, OP fixed them

copied those to external sd card or if you're adb savvy adb push XXXX /sdcard/

Then went here

entered in info

it booted up with errors, hard reset. fixed
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] dabar7:
hey can you or the OP send me the files that were fixed so I can try them on my 900T? this is driving me crazy! thanks in advance...I will read the post you linked in a moment, just getting a head start
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
This will fix it. I think at least three 900t's worked. Just the FSG is all you need, backup mount is not used by these phones, so it doesn't need to be replaced. If you have any problems or success, please post back to here.

I will be traveling tomorrow (650 Mile drive).

Good Luck!

Alan
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] napster007:
Help Me

Note 3 Model : SM-N9005

What triggered problem :

I was about to install a new ROM, the instructions asked to backup EFS. I searched how to do it and end up using "reboot nvbackup" :( . Once the device restarted I realized that there's no network what so ever. I though something went wrong during the process, and tried to restore everything by "reboot nvrestore". Then things got much worse. EFS folder became empty, and now I don't have wifi either. :crying:

How to fix this?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Did you fix it?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] napster007:
Wow man. You are a life saver.

Omg. I can't believe it. This really fixed my device.

Followed http://xdaforums.com/showpost.php?p=52037611&postcount=67 and replaced mmcblk0p18 with the one you provided.

Thank you very much. :highfive:

PS : Wifi doesn't seems to working though :(
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
That's great!!!

"wifi doesn't seems to be working. It happened after I ran "reboot nvrestore" at the beginning".

Lets fix your Wifi, probably lost mac address: "reboot nvrestore" corrupted your Modemst 1 and 2. So now you should 1st download liquid perfection's EFS Professional. Backup the following:

aboot -> /dev/block/mmcblk0p6

efs -> /dev/block/mmcblk0p11

modemst1 -> /dev/block/mmcblk0p12

modemst2 -> /dev/block/mmcblk0p13

fsg -> /dev/block/mmcblk0p18

Use editor and look at the first few lines of code in "modemst1 -> /dev/block/mmcblk0p12" If it has "FSG" in it, it's corrupted. If "modemst2 -> /dev/block/mmcblk0p13" is empty than it is also corrupted. Please report back your findings, and I will try to help you.

If modemst1 and 2 are still good they will look the same as the screen shots you posted of fsg and backup. "IMGEFS1" and "IMGEFS2" should be on the first few lines of code.

If that's the case do this using recovery's file manager:

make copy of "/efs" using file manager (just in case).

Then delete /efs

Then paste these lines of code:

mke2fs /dev/block/mmcblk0p11
mkdir /efs
~ # mount -t ext4 /dev/block/mmcblk0p11 /efs

If you have adb, this is very easy:

adb shell
su
mke2fs /dev/block/mmcblk0p11
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p11 /efs

That should rebuild /efs and fix wifi and bluetooth Mac, and a few other things too.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] napster007:
You are a genius man.

Wow. this fixed my wifi issue too.. you are really a genius. I've attached the first lines of mmcblk0p12, mmcblk0p13. Since it had "IMGEFS1" and "IMGEFS2" I rebuilt the /efs as your guide. And It fixed it. Thanks mate :good:
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
That's great! I'm glad you got your phone back up and running Cheers
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Moltavia:
I had the same problem with IMEI being null/null ...Baseband Unknown and EFS folder being empty..!!!

I tried following the tutorial but couldn't find the necessary files, However.....

Finially repaired my SM-N9005 UK Note 3 by downloading mmcblk0p17 and mmcblk0p18 from here

ce4arab.com/vb7/showthread.php?t=558527 (file download is labelled N9005)

These files were then copied to the following folder /dev/block as describedin this tutorial and everything is back to normal.. :)
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] dabar7:
[MENTION=5609185]radionerd[/MENTION] was right, FSG was all I needed to boot back into Android on my n900t. I'm back in, but no IMEI, it says "UNKNOWN", my baseband shows and is MI7, I don't want to change to the 4.4 bootloader and I'm having trouble finidng the Mi7 modem for TMO online.

Before I forget, I have to mention I'm in linux. (due to my laptop eating up hard drives, 3 total have failed in this used laptop, smh..another story..) so I'm running on a live USB, with persistance = information is saved between boots..a few gigs, and I have an SD card I put in my laptop to store other information. I use Heimdall which windows also has, but this is the alternative for Odin. I load the mmcblk0p18 that radionerd provided and used any pit (if you click partition it doesn't check out, it fails, so I saved two different ones from different times, even from when the phone was acting up). There is even a pit file from a brick repair kit for this same problem that formats block 12 (modemst1) which doesn't solve the problem for me. No commands or anything fixed my block 18 FSG either....besides the following..

I loaded FSG, and flashed it to the phone...lo and behold, it worked! It booted quickly into android, but again I don't have an IMEI, I have an empty /efs folder, and so does a friend's healthy n900v
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Please search the forums "Heimdall lost IMEI Note-3" I think I have read the some folks have had similar problems. ( http://xdaforums.com/showthread.php?t=1813559 ) might help

You might read from Tips to make FSG stick . I asked everyone that was able to fix their phone to right a narrative how they were able to fix FSG. Several guys did good right ups.

The files that you did send me didn't show the "reboot nvbackup" corruptions. If you look at mount 11, 12, 17, and 18 in a text editor you can confirm if "reboot nvbackup" corrupted by just looking at the 1st line of code.

Hope you get it figured out, good luck man!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] dabar7:
Thanks for all your help [MENTION=5609185]radionerd[/MENTION], I haven't gotten the chance to try recently but I was reading up on the first link you gave and when I get the phone back in my hands today I'll try that method and let you all know

---------- Post added at 02:25 PM ---------- Previous post was at 01:41 PM ----------

The method in the first link didn't work as I flashed the "efs.rfs" to the efs partition, so I tried the efs rebuild again, this is what I get..

255|root@hltetmo:/ # ~ # mount -t ext4 /dev/block/mmcblk0p11 /efs
tmp-mksh: /: can't execute: Is a directory
126|root@hltetmo:/ # # mount -t ext4 /dev/block/mmcblk0p11 /efs
126|root@hltetmo:/ # mount -t ext4 /dev/block/mmcblk0p11 /efs
root@hltetmo:/ # adb reboot

it sounds really noobish but I'm not too familiar with the mount command and wasn't sure about the use of the characters (which I will google those commands very soon). How will I know if it executed properly? I rebooted and nothing's changed, is there another way to go about it?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] dabar7:
great so now I have an EFS folder that is rebuilt it just doesn't have nv_data.bin and the other .nv_data file..still no imei
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Attached screen shots of my healthy /efs folder. No nv_data.bin or other .nv folder. That stuff isn't in our North America snapdragon note-3's /efs folder.

EFS Pro might help you. Backup important blocks prior to doing anything.

I don't think your phone was corrupted by "reboot nvbackup" command. I am finally home after over two weeks on the road. Looked again at your blocks 12, 13 , and 17. Compared to mine, They don't show the corruption. Block 17 is supposed to be empty, and yours is empty. "Reboot nvbackup" would have filled up block 17 with block12 data. 12 and 13 have similar hex structure as mine.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] dabar7:
It seems you have a few more files than me after those directories,..man I don't know what to do
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
I feel sorry for you man, mine was bricked for over 6 weeks. If you can post the specifics on how your phone started having problems I will try to help steer you back on track: The software used, steps taken, commands... The more info posted could unveil the problem.

Does the 900t still bootloop? Can you get to the google store? Logcat apk might reveal the problem i the startup logs.

Have you tried to factory restore? Read up on these

http://xdaforums.com/showthread.php?t=2470599

http://xdaforums.com/showthread.php?t=2488431
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] mharleston:
Ok I have a verizon note 3 (SM-N900V) and have ran into a bit of a problem. I had experienced the same symptoms as those stated in this thread (null imei, unknown baseband, and most importantly my data connection and service was non existent) I didn't know whether to consider my phone bricked or temporarily disabled or what. After days of trying my some what okay skills at fixing the phone I gave up. And yes believe me I know the information on this topic is very limited and very hard to find. I think I read through this thread by radionerd at least 5 times. After confirming my FSG and EFS partitions were corrupted I simply requested the new files from radionerd. I didn't expect to receive a reply or the files i needed right away so i was very surprised when i received feedback and steps to fix my phone within a couple of hours. Here is a no hassle process of how my phone was brought back to life.

• Simply copied my partitions from /dev/block/ to my SD Card (mmcblk0p18, mmcblk0p17, mmcblk0p11) I used ES File Explorer.

• Opened each file up in a text viewer to verify that they were indeed corrupted.

• Sent the corrupted files with a brief summary of my issues and the correct model of my phone to radionerd

• After receiving confirmation that my files were corrupted and a very much appreciated copy of the correct partition file...In my case I received a clean copy of mmcblk0p18.

• At this point I wanted to be hesitant on how I replaced the new file into the /dev/block folder but how much more damage could I do....so I just made sure I had a backup of the original file and then literally I did a copy/paste of the clean mmcblk0p18 file into dev/block folder overwriting the corrupted partition.

•Yes that's it, it was that easy! My data services were restored immediately as well as my IMEI and baseband info.

I can't say enough how thankful I am for this thread being created and the help from others chiming in. Please don't use me solely as a guide, I'm only writing about what I did to fix my particular issues. However, if your issues are similar to mine at least attempt to check out your partitions for errors. That's a good place to start to save yourself a lot of headache and time.

Thanks again radionerd you are the man!