[SOLVED] Note 3 SM-N900V DE "reboot nvbackup" Samsung's bomb

[radionerd]

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!

Glad you got your phone back
Excellent Writeup!

Thanks,

 

[Heimish]

No signal after OTA

Glad you got your phone back
Excellent Writeup!

Thanks,

Not sure if this is related, but hope you can point me in the right direction. I'm using a Galaxy S3 SCH-S968c which is a Straight Talk phone that works on Verizon. The phone is running on Page Plus which also works on Verizon and it OTA'd perfectly and got everything till one day when I put in a SIM and did an OTA and it rebooted with no signal at all. When I do nvbackup I get back the signal without MDN etc., but after I OTA it gets the MDN and all but reboots without any signal. Any help would be much appreciated.

 

[radionerd]

Not sure if this is related, but hope you can point me in the right direction. I'm using a Galaxy S3 SCH-S968c which is a Straight Talk phone that works on Verizon. The phone is running on Page Plus which also works on Verizon and it OTA'd perfectly and got everything till one day when I put in a SIM and did an OTA and it rebooted with no signal at all. When I do nvbackup I get back the signal without MDN etc., but after I OTA it gets the MDN and all but reboots without any signal. Any help would be much appreciated.

The S-3 and other older Samsung phones don't have this problem.
Sorry I can't help

 

[Heimish]

The S-3 and other older Samsung phones don't have this problem.
Sorry I can't help

OK thanks anyway

Do you happen to know in which part or the system the prl is stored?

 

[dabar7]

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://forum.xda-developers.com/showthread.php?t=2470599
http://forum.xda-developers.com/showthread.php?t=2488431

Sorry, I left this alone once I was finished and rid of this phone, but I found a guy with an octoplus unlock box and he repaired the phone if you know what I mean, but this is what solved it..of course I don't know what trick he used specifically with the box and not many know exactly how, but hey I can't complain..it fixed the null problem and got things up and running

 

[radionerd]

Sorry, I left this alone once I was finished and rid of this phone, but I found a guy with an octoplus unlock box and he repaired the phone if you know what I mean, but this is what solved it..of course I don't know what trick he used specifically with the box and not many know exactly how, but hey I can't complain..it fixed the null problem and got things up and running

Raib_dabar,
Thanks for the update, glad your phone is working

 

[metriod]

my n900v have same issues, null imei, baseband,etc

here is attach mmcblk 17 and 18

 

[radionerd]

my n900v have same issues, null imei, baseband,etc

here is attach mmcblk 17 and 18

Did you get it going yet?

 

[agera007]

I'm having the same issue with no Radio on SM-N900V (4.4.2) after doing the "reboot nvbackup".
Can someone please send/post the clean mmc* files to replace the corrupt files?

 

[agera007]

Thanks to Radionerd! You are the man
My phone (SM-N900V) radio started working after replacing the two corrupt files with the cleanfsg files from Radionerd.
Donation is on the way...

 

[radionerd]

Thanks to Radionerd! You are the man
My phone (SM-N900V) radio started working after replacing the two corrupt files with the cleanfsg files from Radionerd.
Donation is on the way...

That's great, I'm glad it worked for you

If you get a chance maybe you can share how you put the files in successfully. Several others had to try a few ways before the files actually stuck.
:good:

 

[agera007]

Sure.
For some reason overwriting the corrupt files via Safestrap didn't work. I had to use FX Filemanager (root) to replace the corrupt fsg's (mmcblk0p17 & mmcblk0p18) with clean fsg's
Steps:
====
1) Backup the existing mmc*17 and mmc*18 to SDcard/backfsg
2) Copied the cleanfsg(mmcblk0p17 & mmcblk0p18) files from Radionerd to SDcard/cleanfsg
3) Overwrite the mmc*17 and mmc*18 in /dev/block/ with the two files from SDCard/cleanfsg/
4) The radio started working immediately after replacing the two corrupt files
5) Data started working after restarting the device

Thanks again Radionerd! :good:

 

[Sobaro]

hello guys, i just read every single line in the last 12 pages and i have done all the operation successfully in two ways . through root explorer and philzcwm aroma fm method but nothing is fixed. i have null imei and baseband. the phone is not mine but the owner said that he did alot of flashing to the phone. he upgraded to lollipop then downgraded to kitkat . he has flashed lots of modems and lots of kitkat firmwares but in vain.
please any one tell me where to start,and if someone share a clean backup for me that will be appreciated . the phone is note3 n9005.
thanks in advance

 

[radionerd]

hello guys, i just read every single line in the last 12 pages and i have done all the operation successfully in two ways . through root explorer and philzcwm aroma fm method but nothing is fixed. i have null imei and baseband. the phone is not mine but the owner said that he did alot of flashing to the phone. he upgraded to lollipop then downgraded to kitkat . he has flashed lots of modems and lots of kitkat firmwares but in vain.
please any one tell me where to start,and if someone share a clean backup for me that will be appreciated . the phone is note3 n9005.
thanks in advance

This will ony fix devices that mistakenly had the command "reboot nvbackup" sent to the device.
The device you have has lost imea by some other means. There are a few other threads that address problems simular to what you discribe. When I get to a computer I will try to find the link and post.

Sorry, but this fix won't help you.

Sent from my SM-N910V using Tapatalk

 

[huchka]

solved! my N900V restored after "adb reboot nvrestore"

I bricked my N900V same way by running (adb reboot nvrestore)
I used EFS professional to read my rooted G900T (tmobile s5) by selecting note3 otion.
to restore your N900V
Phone has to be rooted, or EFS will not talk to it.
Do backup your bricked note3 ( it will create backup file)
Now select restore and uncheck (enable md5 verification...)
take attached file and rename it to one in EFSProBackup
then you will see all files is selected, deselect all except on FSG
run restore, phone will reboot and you will see cell signal !
that all I did to restore my N900V by using file from G900T

 

[radionerd]

I bricked my N900V same way by running (adb reboot nvrestore)
I used EFS professional to read my rooted G900T (tmobile s5) by selecting note3 otion.
to restore your N900V
Phone has to be rooted, or EFS will not talk to it.
Do backup your bricked note3 ( it will create backup file)
Now select restore and uncheck (enable md5 verification...)
take attached file and rename it to one in EFSProBackup
then you will see all files is selected, deselect all except on FSG
run restore, phone will reboot and you will see cell signal !
that all I did to restore my N900V by using file from G900T

Glad you were able to use efspro to restore with a clean FSG! EFS pro is a great backup tool, just need root and busybox.

 

[tariqyosef]

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

can this work with SM-G900v Samsung galaxy s5 verzion

 

[radionerd]

can this work with SM-G900v Samsung galaxy s5 verzion

S5 doesn't have this problem, Samsung disabled the bad command "reboot nvbackup" in S5.

 

[asadnow2k]

i have n900v 4.4.4 how to root as efs repair not working.. on it

 

[supreme83]

Sprint Note 3 (SM-N900P) constant loop triggered by adb reboot nvbackup command

mmblk0p17 first four lines
11 00 00 00 03 00 00 00 D8 01 00 00 00 02 D8 0F 00 FE 17 00 00 FE 17 00 00 00 F0 0F 00 00 00 00 00 00 F0 0F 00 00 00 00 49 4D 47 45 46 53 32 EF 5B 01 00 06 F4 80 29 50 01 00 00 00 02 01 00 00
mmblk0p18 first four lines
10 00 00 00 03 00 00 00 D8 01 00 00 F8 A2 7D 0B 00 FE 17 00 00 FE 17 00 F8 A0 95 0B 00 00 00 00 F8 A0 95 0B 00 00 00 00 49 4D 47 45 46 53 31 F0 5B 01 00 55 93 82 29 50 01 00 00 00 02 01 00 00

PMing you now. I appreciate your help in fixing this issue