yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Surge1223:
Okay, first update busybox, I suggest installing "Busybox on Rails" from the playstore. Then make sure SuperSu is up to date and open the SuperSu app and place a check in the box that says something like "enable su at boot"

then download and unzip the create_firmware_symlinks file ive attached and connect your phone to your pc and try to replicate what I did below (I used my touchpad but the commands are still the same) make sure the id of sh is the same the output below.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
I am studying this. I have busybox v1.21.1-kk static. Since I can't boot (bootloops), I looked into sideloading latest binaries. Busybox doesn't have v1.22.1.bin posted yet, just source.

I normally have Super SU pro. Philz CWM gives and option to install his version.

Thank You, I'm learning

C:\Users\Alan>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # busybox
busybox
BusyBox v1.21.1-kk static (2013-11-24 11:52 +0100) multi-call binary.

~ # whoami
whoami
root

~ # id
id
uid=0(root) gid=0(root)

~ # $ su
$ su
/sbin/sh: $: not found
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
My latest logcat snip after spending the day with my note 3. I think I'm going to wear out 3 buttons, or get carpal tunnel :)

?:??: W/?(?): --------- beginning of /dev/log/main
01-01 01:10:48.599: D/(3477): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.599: D/(3477): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 01:10:48.609: D/QSEECOMAPI:(3477): QSEECom_get_handle sb_length = 0x104e80
01-01 01:10:48.609: E/QSEECOMAPI:(3477): Error::Failed to open /dev/qseecom device
01-01 01:10:48.609: E/(3477): TIMA: tima-pkm--Unable to start TZ app; errno = 9
01-01 01:10:48.609: D/(3477): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 01:10:48.609: D/QSEECOMAPI:(3477): QSEECom_get_handle sb_length = 0x104e80
01-01 01:10:48.609: E/QSEECOMAPI:(3477): Error::Failed to open /dev/qseecom device
01-01 01:10:48.609: E/(3477): TIMA: tima-pkm--Unable to start TZ app; errno = 9
01-01 01:10:48.609: D/(3477): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 01:10:48.609: D/QSEECOMAPI:(3477): QSEECom_get_handle sb_length = 0x104e80
01-01 01:10:48.609: E/QSEECOMAPI:(3477): Error::Failed to open /dev/qseecom device
01-01 01:10:48.609: E/(3477): TIMA: tima-pkm--Unable to start TZ app; errno = 9
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Surge1223:
You don't need to upadate Busybox linux style. Just download the app I mentioned in my last post, and it will update and repair your busybox binaries without rebooting. Also SuperSu pro is a donation version, I think your problem would be solved if you just updated supersu and busybox and then mounted /dev thats why I suggested it. You can download the latest SuperSu binary from Chainfire's thread but im assuming you have wifi you can use to connect to your note 3 to update those apps right? I think your making this too hard on yourself lol. Did you run all the commands I posted above? If so what if anything is currently in the /efs folder?

Edit: there seems to be an issue with su binary are you still rooted? Check the id on su, if its anything other than 0 then under adb shell

root@android:/ # mount -o remount, rw /system
root@android:/ # chown 0.0 /system/bin/su
root@android:/ # chmod 06755 /system/bin/su
root@android:/ # ln -s /system/bin/su /system/xbin/su

After this you would still need to update/reinstall busybox and supersu in order for the "sh" issue to be fixed
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Surge1223:
Also if they arent mounting right try doing it like this and type su even if you have the #

su

mount -o remount,rw -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] ryanbg:
These are HLOS applications from your NON-HLOS image. What's really interesting is the dates on these files. Can you do a dd backup of your NON-HLOS partition? I haven't seen a release from JAN 28 yet...
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Surge1223:
I know su and busybox are present in sbin. However whether or not busybox is properly linked to /system upon boot remains to be seen. Is there a particular reason your adverse to following my recommendations on usinf the playstore etc? Just wondering...regardless of what sbin shows the fact is that sh and su dont have the proper permissions.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Surge,

Not at all, I totally appreciate your help, I'm stuck without it. I just don't know how I can install it, or run it for that matter all I have is recovery mode. I have SDK. Can it run in recovery mode?

Thanks Man!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Surge1223:
What happens if you open the google playstore then search for Supersu, select it and select update? Then search for busybox and try install a busybox app?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
I don't know how to get the apk into my bricked phone.???

I have installed supersu ver193.zip from Philz CWM recovery (It's in my external SD). Also tried the cwm superSU that is imbedded in Philz recovery. Neither allow me to run su. I get" /sbin/sh: $: not found". I must be missing something on googleplay. Can I download the apk to my computer, then sideload it?

When I get home from work I will try again.

Thanks for you patience.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] northmendo:
I think you may also be having a problem because you flashed the retail radio. I was chatting with [MENTION=4243514]Hashcode[/MENTION] about the radios earlier and it doesn't sound like they are compatible. Also the TMO aokp you flashed doesn't have the right RIL. Try flashing this one - https://us1.dl.carbon-rom.com/files/hlte/nightly/CARBON-KK-NIGHTLY-20140227-1110-hlte.zip

It has all the correct files for the VZW DE. I am running it without a problem right now. I don't know if it will fix your issue but it will lay the correct system base.

If you need help let me know.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
I flashed the DE back to "DE stock" followed this

Used Bean106 DE stock DevEdition_P900v_MJE_StockRestore.tar.md5.7z and PIT.

I have lost IMEI, and IMEI SV after trying to back up NV using EFS Pro. I looked at my efs block in hex editor, it looks pretty hosed up, mostly empty with the same /efs files repeated over and over. Going to try to compare known good mount blocks 11 and 12 with mine.

I have more resent logcats. I will post

I will try the ROM, need to wipe again anyway :)

Thanks,
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] northmendo:
Damn. I just backed up my efs - modem - boot & recovery if you want to try and restore mine. I don't know if there could be repercussions from that or not but it may get you a better starting point. I can pgp you the files.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] cam30era:
FWIW: I flashed the MJE radio on my DE back when beans put the file up on his development thread. I have not had any problems. Works well with stock MJE ROM, Beans 6, and now CM11.

With that said, this is only anecdotal evidence. I have the utmost respect for Hashcode, and he sure is the expert....
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] northmendo:
Your right. I flashed MJE a little while ago and all is well.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Surge1223:
Try what this thread outlined http://xdaforums.com/showthread.php?t=2683454
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Thanks Surge, My phone is on it's way back from Texas, it went on a wild goose chase to samsung repair.

I am putting some more links here about "reboot nvbackup"

The link below explains my problem. I clicked "NV backup" in EFS Pro, my mount12 modemst1 had been corrupted a month earlier by a bad restore done with TWRP 2.6.3.0-hltetmo, efs was pointed to mount12 in that version. The phone still worked until I clicked "backup nv" in efs pro. I Think the phone wrote the bad or blank backup to fsg, and restarted into bootloops.

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

http://xdaforums.com/showpost.php?p=30679924&postcount=5735

good reference:

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

http://xdaforums.com/showthread.php?t=2517657
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] en11gma:
add another disater to the list

i have us cellular note 3 (SM-N900R4) on android 4.4.2 stock NAB

i was trying to create a "backup" with efs pro 2.0.91 and i selected to the top selections where it selects all the checkmarks and when i would try to make a backup it would fail at some of those partitions so i would just uncheck the failed partition and re-run backup

i probably had to run backup close to 10x and probably had to uncheck about 6-8 items until i got it to complete.

after i did that i decided to checkout the qualcom nv items box or w/e it is and my phone rebooted.

i didnt think anything of it because it says if it dont work phone will reboot.

i then noticed i cant get into anything that requires my spc/msl and my baseband is unknown

i re oding the stock tw rom nam back to phone and still same thing.

should i restore the backup i made?

when i goto try to restore it copies the 5GB file to device ok but it cant restore because there is no partitions i can select for it to restore too.

re-installed busybox

---------- Hardware Information ----------

Connected Device SN.: 746e5dca

Device Manufacturer: SAMSUNG

Device Model: SM-N900R4

Product Code: Unknown

Hardware Version: Unknown

---------- Firmware Information ----------

PDA Version: N900R4TYUCNAB

Baseband Version: Unknown

CSC Version: N900R4USCCNAB

---------- Software Information ----------

Kernel Release: 3.4.0-447319

Kernel Version: #1 SMP PREEMPT Tue Jan 28 20:32:28 KST 2014

ROM Build: hlteusc-user 4.4.2 KOT49H N900R4TYUCNAB release-keys

Android Version: 4.4.2

BusyBox Version: 1.22.1-Stericson

SU Binary Version: 1.93:SUPERSU

i can now see all the partitions that i created before i did the nv backup where it rebooted and messed things up.

what do i do at this point?

is there anything i can do to help?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] en11gma:
form efs pro 2.0.91 screen capture of nab from twrp recovery

taken from menu of efs pro 2.0.91 where it shows 25 partitions

device and mounts

/dev/block/mmcblk0p1	apnhlos

/dev/block/mmcblk0p2	modem

/dev/block/mmcblk0p3	sbl1

/dev/block/mmcblk0p4	dbi

/dev/block/mmcblk0p5	ddr

/dev/block/mmcblk0p6	aboot

/dev/block/mmcblk0p7	rpm

/dev/block/mmcblk0p8	tz

/dev/block/mmcblk0p9	pad

/dev/block/mmcblk0p10	param

/dev/block/mmcblk0p11	efs

/dev/block/mmcblk0p12	modemst1

/dev/block/mmcblk0p13	modemst2

/dev/block/mmcblk0p14	boot

/dev/block/mmcblk0p15	recovery

/dev/block/mmcblk0p16	fota

/dev/block/mmcblk0p17	backup

/dev/block/mmcblk0p18	fsg

/dev/block/mmcblk0p19	fsc

/dev/block/mmcblk0p20	ssd

/dev/block/mmcblk0p21	persist

/dev/block/mmcblk0p22	persdata

/dev/block/mmcblk0p23	system

/dev/block/mmcblk0p24	cache

/dev/block/mmcblk0p25	userdata

from cm11 (android 4.4.2) that im on now

exactly the same as above but located here

/dev/block/platform/msm_sdcc.1/by-name

---------- Post added at 04:07 AM ---------- Previous post was at 03:14 AM ----------

efs pro didnt backup /fsg during full partition back up it dont look like

op of efs pro isnt answering us cause he knows we are screwed

thanks op
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Here is mine:

ls -la

__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!

__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!

__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!

drwxr-xr-x 22 root root 0 Jan 1 00:32 .

drwxr-xr-x 22 root root 0 Jan 1 00:32 ..

-rw-rw-rw- 1 root root 717 Jan 1 00:32 adb_keys

drwxr-xr-x 2 root root 0 Jan 1 00:32 boot

drwxrwx--x 6 system cache 4096 Jan 1 1970 cache

-rwxr-x--- 1 root root 284276 Jan 1 00:00 charger

drwxr-xr-x 2 root root 0 Jan 1 00:00 data

drwxr-xr-x 2 root root 0 Jan 1 00:32 datadata

-rw-r--r-- 1 root root 4316 Jan 1 00:00 default.prop

drwxr-xr-x 10 root root 15400 Jan 1 00:32 dev

drwxr-xr-x 2 root root 0 Jan 1 00:32 emmc

drwxr-xr-x 2 root root 0 Jan 1 00:32 etc

drwxr-xr-x 2 root root 0 Jan 1 00:32 external_sd

-rw-r--r-- 1 root root 10953 Jan 1 00:00 file_contexts

-rw-r----- 1 root root 1722 Jan 1 00:00 fstab.qcom

-rwxr-x--- 1 root root 183820 Jan 1 00:00 init

-rwxr-x--- 1 root root 7064 Jan 1 00:00 init.qcom.class_core.sh

-rwxr-x--- 1 root root 2530 Jan 1 00:00 init.qcom.class_main.sh

-rwxr-x--- 1 root root 3326 Jan 1 00:00 init.qcom.early_boot.sh

-rwxr-x--- 1 root root 5451 Jan 1 00:00 init.qcom.lpm_boot.sh

-rwxr-x--- 1 root root 7100 Jan 1 00:00 init.qcom.sh

-rwxr-x--- 1 root root 3265 Jan 1 00:00 init.qcom.syspart_fixup

.sh

-rwxr-x--- 1 root root 6959 Jan 1 00:00 init.qcom.usb.sh

-rwxr-x--- 1 root root 2721 Jan 1 00:00 init.rc

-rwxr-x--- 1 root root 2115 Jan 1 00:00 init.recovery.qcom.rc

drwxr-xr-x 2 root root 0 Jan 1 00:32 internal_sd

-rw-r--r-- 1 root root 2988 Jan 1 00:00 lpm.rc

drwxrwxr-x 5 root system 0 Jan 1 00:32 mnt

dr-xr-xr-x 167 root root 0 Jan 1 00:00 proc

-rw-r--r-- 1 root root 2161 Jan 1 00:00 property_contexts

drwxr-xr-x 2 root root 0 Jan 1 00:32 recovery

drwxr-xr-x 3 root root 0 Jan 1 00:00 res

drwx------ 2 root root 0 Jan 30 2014 root

drwxr-x--- 3 root root 0 Jan 1 00:00 sbin

drwxr-xr-x 2 root root 0 Jan 1 00:32 sd-ext

lrwxrwxrwx 1 root root 13 Jan 1 00:32 sdcard -> /data/media/0

-rw-r--r-- 1 root root 711 Jan 1 00:00 seapp_contexts

-rw-r--r-- 1 root root 77118 Jan 1 00:00 sepolicy

d---r-x--- 2 root sdcard_r 40 Jan 1 00:32 storage

dr-xr-xr-x 12 root root 0 Jan 1 00:32 sys

drwxr-xr-x 3 root root 0 Jan 1 00:00 system

drwxrwxr-x 2 root shell 60 Jan 1 00:32 tmp

-rw-r--r-- 1 root root 6534 Jan 1 00:00 ueventd.qcom.rc

-rw-r--r-- 1 root root 5896 Jan 1 00:00 ueventd.rc

~ #
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] en11gma:
well thats interesting

mine are all 1969
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
It's BACK!

Got it going, my IMEI is back.

Got a good copy of FSG, and backup partition's from a friend with the same DE phone, Dropped them in, and IMEI appeared even before reboot.

:cool:
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] en11gma:
can you get them for mine?

i dont have DE version

i have US Cellular SM-N900R4 on stock android 4.4.2

this ships off to ebay buyer in the morning

what partitions exactly did you have to get off the same note 3 and what was command to back them up and restore them?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] en11gma:
radionerd you are the man

but for real thankkkkkk-yoooooouuuu so much man!

this thing was sold and ready to ship

i have to cancel the paypal transaction and hope buyer dont leave me bad feedback but even if i get it...it is worth it

i get to keeps my note 3

:)

thank-you so much radionerd.

donation coming on the 1st and no its not april fools joke
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
I am so glad your up and running again!

did you put in both files or just FSG?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] en11gma:
yes i did

i put the /backup partition first

then i did /fsg

then i checked about status and all was good

i was in ruim_only with no sim so some stuff wasnt in there but my imei and meid are there

the other stuff is because i have wiped the phone so much and no sim inserted

dude i just can tell you are a good person

you could have kept this info to yourself like alot of people would

people like you that share are so helpful to others and much needed in this world

cant say thanks enough man

thank-you

i had us cellular note 3 that i had backed attempted to do a nvrestore reboot basically (another app called the command) but that is basically what happened and it looks like /fsg and /backup must be directly from sammy therefore those must be same exact files across all devices

at least it was with my us cellular and your verizon de

worked

thank you again

how i did it (after i i got a hold of /fsg and /backup partitions)

i was on us cellular stock NAB (android 4.4.2)

i odin over TWRP and used that to install super su 1.93

i then installed es file manager

my phone had all radios off and in airplane mode (dont know if that matters but thats how i had it)

i copied the partitions to /dev/block and checked about device>status and BAM there was my IMEI and BAM there was my MEID

so this method does work 100% as far as i can tell
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] lyriquidperfection:
Now do a proper backup in efs professional as it now supports fsg and backup partitions!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] naife:
Please explain how to backup fsg then modify to read correct imei then how pack it again and flash it

I used efs pro 2.0.104 to backup except create archive .tar.gz

please see log

Checking device connection... Device is connected!

Checking for block device: '/dev/block/mmcblk0'... Okay.

Extracting PIT from device for mapping... Skipped, already exists.

Checking backup folder location... Okay.

Backing up selected partition(s)...

tz - read: /dev/block/mmcblk0p8 - write: tz.mbn... Okay.

524288 bytes transferred in 0.021 secs (24966095 bytes/sec)

Verifying MD5 Checksum... Okay.

Device MD5 Hash: 925b777f3a0755de7899d0392408ad89

Backup Data MD5 Hash: 925b777f3a0755de7899d0392408ad89

param - read: /dev/block/mmcblk0p10 - write: param.bin... Okay.

10485760 bytes transferred in 0.243 secs (43151275 bytes/sec)

Verifying MD5 Checksum... Okay.

Device MD5 Hash: 8f0193d2f0c629c213a94ccafbfd92e8

Backup Data MD5 Hash: 8f0193d2f0c629c213a94ccafbfd92e8

efs - read: /dev/block/mmcblk0p11 - write: efs.img.ext4... Okay.

14680064 bytes transferred in 0.196 secs (74898285 bytes/sec)

Verifying MD5 Checksum... Okay.

Device MD5 Hash: e1c5de6c2f32651b127591f794d70ee4

Backup Data MD5 Hash: e1c5de6c2f32651b127591f794d70ee4

modemst1 - read: /dev/block/mmcblk0p12 - write: nvrebuild1.bin... Okay.

3145728 bytes transferred in 0.044 secs (71493818 bytes/sec)

Verifying MD5 Checksum... Okay.

Device MD5 Hash: 4a4e83ddc41fd07b61ae6395ff936a78

Backup Data MD5 Hash: 4a4e83ddc41fd07b61ae6395ff936a78

modemst2 - read: /dev/block/mmcblk0p13 - write: nvrebuild2.bin... Okay.

3145728 bytes transferred in 0.042 secs (74898285 bytes/sec)

Verifying MD5 Checksum... Okay.

Device MD5 Hash: 5f7fc5acc5ef62121e43823ac1178a0d

Backup Data MD5 Hash: 5f7fc5acc5ef62121e43823ac1178a0d

backup - read: /dev/block/mmcblk0p17 - write: ... Okay.

7330816 bytes transferred in 0.098 secs (74804244 bytes/sec)

Verifying MD5 Checksum... Okay.

Device MD5 Hash: 3e76c6b2efbaf149fb23e87784637dc7

Backup Data MD5 Hash: 3e76c6b2efbaf149fb23e87784637dc7

fsg - read: /dev/block/mmcblk0p18 - write: ... Okay.

3145728 bytes transferred in 0.053 secs (59353358 bytes/sec)

Verifying MD5 Checksum... Okay.

Device MD5 Hash: 4a4e83ddc41fd07b61ae6395ff936a78

Backup Data MD5 Hash: 4a4e83ddc41fd07b61ae6395ff936a78

fsc - read: /dev/block/mmcblk0p19 - write: ... Okay.

1024 bytes transferred in 0.004 secs (256000 bytes/sec)

Verifying MD5 Checksum... Okay.

Device MD5 Hash: 0f343b0931126a20f133d67c2b018a3b

Backup Data MD5 Hash: 0f343b0931126a20f133d67c2b018a3b

Creating archive: SM-N9005_20140324_222453.tar.gz...

Operation failed!

---------- Post added at 08:08 PM ---------- Previous post was at 07:26 PM ----------

sorry after read again and again :)

understand there is two file or folder called fsg & partition we have to put it in Dev/Block while phone in airplane mode using es file explorer .

we should have root .

my phone is note .3 N9005 please send me two file

Appreciate your help
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Confirm with me that you lost IMEI after sending command reboot nvbackup? This will only help with this problem

Your IMEI is "Missing"?

I haven't had anyone confirm yet that the MD5 on FSG is the same on all note 3's yet. Hopefully a nice XDA member will check that for us on their good note3.

EFS Pro can now backup FSG, yours is backed up now good!,

Your MD5 is different, so it might be the problem. If you have hex editor look at the FSG file in Hex (mmblk0p18) . It should have IMGEFSG near the top of the partition. See picture posted in 1st post comparing good FSG to one that was over written.

. As soon as some nice person with a note-3 can confirm MD5 is same on all our note-3's, we can make a clean copy of FSG available for everyone that needs it.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] naife:
My imei is missing and show null (unkown) so there is nothing to lose please send my the two files to test it.

Regards

---------- Post added at 09:39 PM ---------- Previous post was at 09:02 PM ----------

First need root , install root explorer.apk in phone and remove SIM card

http://www.1mobile.com/root-explorer-94072.html

I received two files name mmcblk0p17 & mmcblk0p18 from genius Man ( Radionerd ) copy it to my phone memory then open root explorer and change mount to R/O instead of R/W

Copy two file mmcblk0p17 & mmcblk0p18 to dev/block accept overwrite.

turn off your note 3 put your SIM card turn on your mobile :)

That is it my original imei is back and baseband.

All thanks goes to Man of the day Mr.Radionerd

Mr.Radionerd please add your email to donate so at least me and other guys can buy you a beer ")

thanks for saving my phone live .
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Sweet!!!

I am happy for you!:cool:
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] codecxbox:
Please send me these files. I will test them on a Latin American Note 3 . I lost imei and baseband by reboot nv too. I also opened my fsg and backub, both have been Samsunged...I will tell results asap. Thank you
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] codecxbox:
I did the same procedure as the other visitor said, but sadly it didnt help. I noticed that when I turned on the phone, these block were almost empty.

Indeed, the Note somehow modified your backup and FGS files.

I would suggest you to replace the backup and FSG from a EFS PRO backup, and then restore the backup, with the files you sent us.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Sorry it didn't work, can you post your model number? Maybe it is not a Qualcomm version Note 3.

If you open your fsg in WordPad it should have IMGFSG in the first line.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] codecxbox:
it is

its a Qualcom .
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] codecxbox:
FINALLY!!!

RADIO Your the man!!I

IT WORKED! the reason it didnt stick was that before my /efs had a mount failure. So after doing the fire script manually with block 11, today just for playing around, i applied both 17 and 18 blocks to my /dev/block and immedialtly I got BASEBAND AND IMEI!!! thanks A LOT!!!!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Yaaah!

Glad your phone is working!!!

Please post your model number and carrier. I will add to the successful list in 1st post..
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] codecxbox:
Claro Puerto Rico SM-N900W8