Database Users

[SOLVED] BASEBAND "unkown" EMEI "unkown" - EFS Backup available

Hi all,
i had to use "Clear Phone EFS" in Odin to get my 9005 back working - i thought: "Hey no problem i have multiple EFS backups..."
But now even if i restore my backup in TWRP or via the Windows Batch Backup Script, my Baseband and EMEI and EMEISV is still "unkown"
Can s.o tell me the steps i need to do, to rewrite my Baseband and EMEI with my available EFS backups?
What i have:
- EFS Professional
- 2 different EFS backups in TWRP
- 2 windows back tool EFS backups (i mean this script: http://forum.xda-developers.com/showthread.php?t=2447342)
- Working WIFI
- Working BT
- Stock N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX file(s)
- Stock N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME file(s)
- Stock N9005XXUENB7_N9005DBTENB2_DBT file(s)
- Odin + 9005 PIT Files
- Correct SerialNumber in DeviceInformation->Status
I'm on the new Bootloader and KitKat OS
Thank you very much for all your help!
Best regards,
Chris
PROBLEM SOLVED!
Look here http://forum.xda-developers.com/showpost.php?p=51152510&postcount=4

Hundsbuah said:
Hi all,
i had to use "Clear Phone EFS" in Odin to get my 9005 back working - i thought: "Hey no problem i have multiple EFS backups..."
But now even if i restore my backup in TWRP or via the Windows Batch Backup Script, my Baseband and EMEI and EMEISV is still "unkown"
Can s.o tell me the steps i need to do, to rewrite my Baseband and EMEI with my available EFS backups?
...
Click to expand...
Click to collapse
On the N9005 the IMEI is no longer on the EFS partition (mmcblk0p11) but instead in some other partition - I think mainly in MS1 (mmcblk0p12) with something else (backup?) in MS2 (mmcblk0p13). There might be something else in mmcblk0p17, mmcblk0p18 and mmcblk0p19.
If you do not have any backup (including a larger "debrick backup" - search for that post) you can try to see which one of the partitions I listed above was supposed to be the backup of what; and if that fails there is a more complex procedure described somewhere in a thread on XDA - involving manually hex-editing your SN and IMEI from under the battery or the original box of the phone.

xclub_101 said:
On the N9005 the IMEI is no longer on the EFS partition (mmcblk0p11) but instead in some other partition - I think mainly in MS1 (mmcblk0p12) with something else (backup?) in MS2 (mmcblk0p13). There might be something else in mmcblk0p17, mmcblk0p18 and mmcblk0p19.
If you do not have any backup (including a larger "debrick backup" - search for that post) you can try to see which one of the partitions I listed above was supposed to be the backup of what; and if that fails there is a more complex procedure described somewhere in a thread on XDA - involving manually hex-editing your SN and IMEI from under the battery or the original box of the phone.
Click to expand...
Click to collapse
ok thank you - bad news
Ill try this guide: (Can this guide be used with KK 4.4.2 ?)
http://forum.xda-developers.com/showthread.php?t=2567133
What about the "unkown baseband"? How can this be fixed?

Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again

Bro whats a twrp efs backup?

Team win recovery Project. Its a revovery and a twrp efs Backup is a Backup from the 3 efs partitions in twrp
Gesendet von meinem SM-N9005 mit Tapatalk

Hundsbuah said:
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Click to expand...
Click to collapse
Will a TWRP boot ,data and system backup work as well for restoring baseband? I have the same problem -> http://forum.xda-developers.com/showthread.php?t=2796948&page=6

No u need an efs backup
Gesendet von meinem SM-N9005 mit Tapatalk

Hundsbuah said:
No u need an efs backup
Gesendet von meinem SM-N9005 mit Tapatalk
Click to expand...
Click to collapse
So have I run out of options? Please have a look at my thread. The last few posts especially . Any help would be appreciated.

Please help sm-n900
Hundsbuah said:
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Click to expand...
Click to collapse
just went to the above mentioned link but none of the multiupload files link work.
could you upload the NOTE 3 - Fix soft bricked.rar and the Samsung drivers.
I want to extract the NOTE 3 - Fix soft bricked.rar and modify it for use in sm-n900

Sorry I don't have these files anymore try to get them from the thread owner
Gesendet von meinem SM-N9005 mit Tapatalk

Hundsbuah said:
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Click to expand...
Click to collapse
Hi, I have the same problem as you did, my baseband is showing unknown and the imei is showing null. This happened when I was installing a different modem via ODIN. I do have a EFS backup, however, it was done with philz recovery instead of TWRP and has 4 files ('efs.ext4.tar'; 'efs.ext4.tar.a'; 'nandroid.md5'; and 'recovery.log'). Are these the same that you would get with a TWRP?
I also have another efs backup that I did which is one file only, 'efs_20140531_122400.img'. Would I be able to use this for anything?
The phone is an N9005 on Kitkat.
Thanks for any help in advance and please let me know if you need any other info.
Cheers
--------------------------
Just to let you know,
I had tried flashing flash latest full UK NF4 system before and it didn't work. However, desperate as I was, I went again and gave it another shot and incredibly enough, it worked!!!! Phone is back together again!!!! Yeeahh!!! There goes an incredible load off my shoulders. I guess I did something in between that actually helped, we may never know.
Cheerio

Hundsbuah said:
Hi all,
i had to use "Clear Phone EFS" in Odin to get my 9005 back working - i thought: "Hey no problem i have multiple EFS backups..."
But now even if i restore my backup in TWRP or via the Windows Batch Backup Script, my Baseband and EMEI and EMEISV is still "unkown"
Can s.o tell me the steps i need to do, to rewrite my Baseband and EMEI with my available EFS backups?
What i have:
- EFS Professional
- 2 different EFS backups in TWRP
- 2 windows back tool EFS backups (i mean this script: http://forum.xda-developers.com/showthread.php?t=2447342)
- Working WIFI
- Working BT
- Stock N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX file(s)
- Stock N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME file(s)
- Stock N9005XXUENB7_N9005DBTENB2_DBT file(s)
- Odin + 9005 PIT Files
- Correct SerialNumber in DeviceInformation->Status
I'm on the new Bootloader and KitKat OS
Thank you very much for all your help!
Best regards,
Chris
PROBLEM SOLVED!
Look here http://forum.xda-developers.com/showpost.php?p=51152510&postcount=4
Click to expand...
Click to collapse
Hi Hundsbuah,
I upgraded my Note 3 9005 Hong Kong Version 32 GB from Jelly Bean to KitKat without taking backup of EFS and now I have IMEI Null and Baseband unknown. I found backup of other user's note3 EFS at "http://forum.xda-developers.com/showthread.php?t=2447342". So, if I tried EFS restore from above link will it resolve my IMEI null and baseband unknown issue?
Regards,
Asif

[Q&A] Restore EFS from Nandroid Failed (Solved)

Hi Everybody,
I'm really disappointed. For the second Times, I've corrupted my EFS partition. IMEI is empty, as the baseband...
The first time that I had this problem, I could restore the EFS using the fabulous fix from Fireasusman : http://forum.xda-developers.com/showthread.php?p=47014662#post47014662
But this time, It didn't work.... I'm really really sad.
Before trying to restore the stock firmware ( My problem was coming when i tried to restore stock firmware before to sell it) i made a Nandroid backup with TWRP recovery. I've an EFS/MODEM backup in this Nandroid.
When I reboot into recovery, and go to restore, I can select EFS, and it seems restore It. It wrote : Restoring 2 partitions/Restoring EFS/restoring EFS2/restoring EFS3/EFS Done/Restoring Modem/ Modem Done...
But after reboot the problem is Still There...
I'm really Angry, I lost 400$ and I don't understand why my Nandroid Restore of EFS failed...
I also try to flash modem with ODIN but it still Failed.
Note: I was an temasek CM12 (android lollipop).
Thank you very much for every help.

1. Flash STOCK ROM and take a look how it works. Sometimes only flashing it recovers the EFS folder.
2. Next time use this APP for backup/restore your EFS.

Really thanks for your help.
But i've allready try to restore stock ROM. At least twice. But efs is still corrupt. And the phone never arrive to boot...

About how many time I can consider that flash stock ROM will not repair my EFS partition ?
I've allready done twice...

Ok... I solved my problem.
As I explain in first post, I'had a EFS backup with a Nandroid Backup. But when I restore with TWRP, the problem was still there. No pin, No baseband etc...
I only delete the EFS folder using root explorer. I reboot, and it was OK. EFS folder was rebuilt automatically.... No more complicated than that...

Good finding

pystolero said:
Ok... I solved my problem.
As I explain in first post, I'had a EFS backup with a Nandroid Backup. But when I restore with TWRP, the problem was still there. No pin, No baseband etc...
I only delete the EFS folder using root explorer. I reboot, and it was OK. EFS folder was rebuilt automatically.... No more complicated than that...
Click to expand...
Click to collapse
Because the IMEI is not stored in the EFS folder.

IMEI null. Unknown baseband. EFS IMEI Backup by Wanam and Nandroid Backup didn't work

I lost my phone's IMEI trying to do a backup of it, and also lost my baseband. Backups of IMEI didn't work, and also the backup of the rom made with Nandroid backup.
I wanted to copy the folder EFS, cauase someone recommended to backup the IMEI this way. I did it by ES File Explorer, but when copying the folder EFS, appeared an error message like this: "Failed to copy NVRAM" or something like that.
I do not know if it happened in this process or if the EFS folder had already corrupted with other IMEI backups made with various applications (backups that did not serve me at all). Considering that my IMEI continued null / null when I tried to restore them with a lot of applications (Partitions Backup & Restore, Samsung Tools etc)
Maybe it's important to say that before attempting to restore the IMEI by several backups I had done before tried to install other modems to see if the network appears again. But did not.
Finally, I reinstalled the rom stock by Odin and nothing resolved. I continue with the IMEI issue null/null and unknown baseband.
My last attempt was to restore the backup I made the rom the first day I picked up the phone.
The backup I made with Online Nandroid Backup application. Be safe with this backup because on any topic roms here from XDA, the developers says "Do a nandroid backup first." And that's what I did.
In momement when I did the backup with this application, my recovery installed was Philz Recovery (which is based on CWM), it may be important to say that.
But anyway, the backup is saved on my PC, and I had not needed to use it, and thought it would work when I needed it, but it did'nt work.
Once installed the rom again by Odin, did root, and installed the same Philz Recovery (to have less doubt that the backup can be restored without problems with Nandroid Manager), but it didn't work.
I created a folder called "backup" in the clockworkmod folder "and put my backup there (one who has the time and date of creation in the name).
And when I tried to restore the backup by Nandroid Manager application, the only thing that happens is the phone to reboot, without even access at first the recovery. So the backup can't be restored again.
Then I converted the file to ".zip" and I went to recovery and tried to install it, also failed. It appeared some problem related to the "MD5".
So I installed CWM Recovery (not Philz) and tried to restore the backup with Nandroid Manager, did not work, the phone again, just restarted. So I tried to install the backup as a ".zip" from CWM Recovery, and again, there was a new message regarding the "MD5".
So I installed TWRM Recovery, and tried to restore the backup by Nandroid Manager (but the application said the backup was originated by CWM and it could not be restored by another recovery) then I tried installing the ".zip" file by TWRM recovery, and gave some kind of failure, can not remember exactly what, but I think also related to "MD5".
So I tried to fix the problem related to MD5, I saw some threads on XDA saying how to do ... basically tried two methods.
The first attempt was to delete the file "Nandroid.MD5" by Root Explorer and create a new file with the same name and with the same extension.
So I tried again to restore the backup by Nandroid Manager (with Philz Recovery and CWM Recovery), but also failed. Also failed to install a ".zip" file driectly by the recovery with the new file "nandroid.MD5" created. This file ".zip" with MD5 file "probably fixed" I tried to install with the 3 recoveries already mentioned. Did not work. It continued an error related to "MD5".
The second attempt was to try to correct the "MD5" file with the Terminal Emulator, by this commands:
su
# Mount -o remount rw / sdcard
#cd /sdcard/clockworkmod/backup/2012-04-17.10.09.36
#rm nandroid.md5
# md5sum * img> nandroid.md5
Again, I tried to restore the file by Nandroid Manager (with philz Recovery and CWM Recovery) ... And also tried to restore the file ".zip" by both recoveries,includint TWRP Recovery. Nothing worked.
In the backup name has no spaces. And the files inside it are:
boot.img
cache.ext4.tar
data.ext4.tar
efs.ext4.tar
modem.img
recovery.img
recovery.log
system.ext4.tar
I have a backup intact without modification for future experiments.
I do not know what else to do, I just want to restore the backup to see if the network went back, with my IMEI and my baseband losted.
-
I tried to do the right things and looks like it was worse than if I had done nothing.
For example, trying to save the EFS folder by ES Explorer, apparently that destroyed this folder.
But before It had already made a backup of the rom, but I can not restore it.
It would was better If I did nothing to try to forearm... Cause for now I do not know what to do whit these problems...
My last step will be to gather cash to buy a box to put my IMEI back to the phone... = (
Sorry for my Inglês... Translated by Google Translator.
My phone is SM-N9005.

LeandritoG said:
I lost my phone's IMEI trying to do a backup of it, and also lost my baseband. Backups of IMEI didn't work, and also the backup of the rom made with Nandroid backup.
I wanted to copy the folder EFS, cauase someone recommended to backup the IMEI this way. I did it by ES File Explorer, but when copying the folder EFS, appeared an error message like this: "Failed to copy NVRAM" or something like that.
I do not know if it happened in this process or if the EFS folder had already corrupted with other IMEI backups made with various applications (backups that did not serve me at all). Considering that my IMEI continued null / null when I tried to restore them with a lot of applications (Partitions Backup & Restore, Samsung Tools etc)
Maybe it's important to say that before attempting to restore the IMEI by several backups I had done before tried to install other modems to see if the network appears again. But did not.
Finally, I reinstalled the rom stock by Odin and nothing resolved. I continue with the IMEI issue null/null and unknown baseband.
My last attempt was to restore the backup I made the rom the first day I picked up the phone.
The backup I made with Online Nandroid Backup application. Be safe with this backup because on any topic roms here from XDA, the developers says "Do a nandroid backup first." And that's what I did.
In momement when I did the backup with this application, my recovery installed was Philz Recovery (which is based on CWM), it may be important to say that.
But anyway, the backup is saved on my PC, and I had not needed to use it, and thought it would work when I needed it, but it did'nt work.
Once installed the rom again by Odin, did root, and installed the same Philz Recovery (to have less doubt that the backup can be restored without problems with Nandroid Manager), but it didn't work.
I created a folder called "backup" in the clockworkmod folder "and put my backup there (one who has the time and date of creation in the name).
And when I tried to restore the backup by Nandroid Manager application, the only thing that happens is the phone to reboot, without even access at first the recovery. So the backup can't be restored again.
Then I converted the file to ".zip" and I went to recovery and tried to install it, also failed. It appeared some problem related to the "MD5".
So I installed CWM Recovery (not Philz) and tried to restore the backup with Nandroid Manager, did not work, the phone again, just restarted. So I tried to install the backup as a ".zip" from CWM Recovery, and again, there was a new message regarding the "MD5".
So I installed TWRM Recovery, and tried to restore the backup by Nandroid Manager (but the application said the backup was originated by CWM and it could not be restored by another recovery) then I tried installing the ".zip" file by TWRM recovery, and gave some kind of failure, can not remember exactly what, but I think also related to "MD5".
So I tried to fix the problem related to MD5, I saw some threads on XDA saying how to do ... basically tried two methods.
The first attempt was to delete the file "Nandroid.MD5" by Root Explorer and create a new file with the same name and with the same extension.
So I tried again to restore the backup by Nandroid Manager (with Philz Recovery and CWM Recovery), but also failed. Also failed to install a ".zip" file driectly by the recovery with the new file "nandroid.MD5" created. This file ".zip" with MD5 file "probably fixed" I tried to install with the 3 recoveries already mentioned. Did not work. It continued an error related to "MD5".
The second attempt was to try to correct the "MD5" file with the Terminal Emulator, by this commands:
su
# Mount -o remount rw / sdcard
#cd /sdcard/clockworkmod/backup/2012-04-17.10.09.36
#rm nandroid.md5
# md5sum * img> nandroid.md5
Again, I tried to restore the file by Nandroid Manager (with philz Recovery and CWM Recovery) ... And also tried to restore the file ".zip" by both recoveries,includint TWRP Recovery. Nothing worked.
In the backup name has no spaces. And the files inside it are:
boot.img
cache.ext4.tar
data.ext4.tar
efs.ext4.tar
modem.img
recovery.img
recovery.log
system.ext4.tar
I have a backup intact without modification for future experiments.
I do not know what else to do, I just want to restore the backup to see if the network went back, with my IMEI and my baseband losted.
-
I tried to do the right things and looks like it was worse than if I had done nothing.
For example, trying to save the EFS folder by ES Explorer, apparently that destroyed this folder.
But before It had already made a backup of the rom, but I can not restore it.
It would was better If I did nothing to try to forearm... Cause for now I do not know what to do whit these problems...
My last step will be to gather cash to buy a box to put my IMEI back to the phone... = (
Sorry for my Inglês... Translated by Google Translator.
My phone is SM-N9005.
Click to expand...
Click to collapse
try this

plumzup67 said:
try this
Click to expand...
Click to collapse
This is for what?

LeandritoG said:
This is for what?
Click to expand...
Click to collapse
It will restore things you lost just try it you got nothing to lose
Sent from my SM-A800F using Tapatalk

plumzup67 said:
It will restore things you lost just try it you got nothing to lose
Sent from my SM-A800F using Tapatalk
Click to expand...
Click to collapse
Hi friend, reading this thread I think it isn't my case...
http://forum.xda-developers.com/showthread.php?t=2507403
Buy thanks anyway... =)

plumzup67 said:
It will restore things you lost just try it you got nothing to lose
Sent from my SM-A800F using Tapatalk
Click to expand...
Click to collapse
Well, I tried flash it two times... Continues with imei null and unknown baseband...
Now I will try this...
http://forum.xda-developers.com/showthread.php?t=2567133

You never backed up the EFS originally ??
Or if you did what tool did you use ??

Save internal storage from i9505 software brick/stuck on bootlogo

Hello,
since one week my device, a samsung galaxy s4 i9505, is software bricked and stuck on bootlogo and I've been tryin to save my internal storage, but I'm close to giving up. I hope someone here can help me.
My situation:
1. Updated my TWRP to version 3.0.1-0-jfltexx with odin 3.10.0
2. Flashed new ROM "OMEGA ROM", that worked good.
3. Backup with TWRP, successfull, reboot, galaxy logo appears, flash, again -> bootloop
4. Flashed firmware "i9505XXUHOB8" BL and modem, with odin 3.10.0 in BL and CP
5. No bootloop anymore, but stuck on ROM Logo with normal start and with recovery start blue text "recovery booting..." on galaxy screen but nothing happens.
6. Saw that TWRP 2.8.7.0-i9500 is the recommended TWRP for the i9505, flashed the .img.tar with odin 3.09 in AP (is the .img a problem?) but still same problem, with TWRP 2.8.6.0-i9500.tar too.
6. Tried different firmwares: i9505XXUHOB7, i9505XXUHOF2, i9505XXUHOJ4 -> I thought the problem is the bootloader -> odin error: complete (write) operation failed or NAND write error (->problem was usb port)
7. Tried different odin versions: 1.85, 3.10.6, 3.09
8. Tried different usb cables
9. Flashed cf-auto-root to mount the data partition, but theres no option. Recovery mode is now working, but the samsung recovery, not TWRP.
10. Tried to copy internal storage with ADB, can navigate the directory but can't pull or cd /storage/sdcard0 -> no such file or directory, same with /mnt/sdcard (ADB only works during the ROM logo)
11. Flashed stock samsung firmware "i9505XXUHOJ2_i9505AUTHXXUHOJ1_i9505XXUHOJ2" with odin 3.09 -> now stuck on samsung boot logo. My ROM is now deleted, right?
12. Wipe cache don't help
13. Could wipe data/factory reset or repartition with odin but then I will lost my internal storage.....
I have a backup from the successfull backup with TWRP, but can't open the data.ext4.win001 after rename it (the .win000 is ok)....
Can anyone help me or have an idea how can I save my data and repair the system?
-Mr.Tea

use TWRP to copy files from internal storage over to external SDcard for stuff you wanna keep.
if you manage to backup the data partition you're supposed to be able to extract apps and data from a nandroid with titanium backup pro (never tried it though).
this data you wanna save, if it wasn't created while running omega rom then it wasn't likely to work with it anyway. that could be the source of your bootloops. if that data came from a previous custom rom then try to go back to it, and if successful backup apps with titanium and files to SDcard. you can't keep your data partition and go into a new rom with it.
if the data came from a stock rom you'll loose it trying to go back so extracting from a nandroid is probably your best bet there or restoring once back to stock.

3mel said:
use TWRP to copy files from internal storage over to external SDcard for stuff you wanna keep.
if you manage to backup the data partition you're supposed to be able to extract apps and data from a nandroid with titanium backup pro (never tried it though).
this data you wanna save, if it wasn't created while running omega rom then it wasn't likely to work with it anyway. that could be the source of your bootloops. if that data came from a previous custom rom then try to go back to it, and if successful backup apps with titanium and files to SDcard. you can't keep your data partition and go into a new rom with it.
if the data came from a stock rom you'll loose it trying to go back so extracting from a nandroid is probably your best bet there or restoring once back to stock.
Click to expand...
Click to collapse
TWRP is not working anymore -> blue text "Recovery booting..." on galaxy logo
In many forums they mean TWRP backup not includes the internal storage (/sdcard partition)?!
Can extract my "data.ext4.win000" and "data.ext4.win001" but not find the /sdcard location or my userdata.

Mr.Tea said:
TWRP is not working anymore -> blue text "Recovery booting..." on galaxy logo
In many forums they mean TWRP backup not includes the internal storage (/sdcard partition)?!
Can extract my "data.ext4.win000" and "data.ext4.win001" but not find the /sdcard location or my userdata.
Click to expand...
Click to collapse
try TWRP 3.0.0 by JDCteam, hundreds of happy users there. if it works first time make sure to try backing up your data partition and then wiping it. you can copy your media storage with the built-in file browser as mentioned.
you've got bigger problems if it's not data causing your problems...

EFS folder deleted and not recoverable from TWRP backup - Verizon Note 4 N910V

Guys i need help as I have lost my EFS folder. Summary of how it happened is as below:
Initially I had Note 4 Verizon version running Lollipop 5.0.1
I used a method to turn it into Developer Edition (DE) and I was successful in doing that.
Once got through that I installed customer Recovery (TWRP) and made a backup for it (including EFS folder and everything else)
After that I got SUPERSU installed and root access to my mobile.
Everything until this point was smooth and no issues until I installed XPOSED FRAMEWORK and my mobile got stuck on the boot screen.
After alot of hit and tries I used TWRP for Factory reset and WiPE DATA.
Since then I was totally lost in a boot loop.
I used ODIN with official ROM (downloaded through SAMMOBILE) for my variant and restored the boot but again my mobile went back to stock version.
Now the problem is that my phone gives me a message "FACTORY MODE IS ON ........................................."
Now my WiFi turns OFF automatically and everytime I bootup my mobile I have to enter passcodes for WiFi every single time.
I have again got it into Developer Mode and got the root access as well but when I check the EFS folder using TWRP, ROOT EXPLORER or any other software which has access to root files I can see that EFS folder is empty.
I even tried restoring the backup through TWRP (first time complete and 2nd time only EFS folder). It shows success but still EFS folder is empty.
Now I need support if anyone can either help me with the EFS file or help me restore the EFS file that I have available through TWRP backup.
In desperate need of help because I have tried every method I can find on this forum or after google results but none is working...
Any support to help it work will be very helpful and save me from losing my only source of mobile communication.
ThankS!!!

Try this:
https://play.google.com/store/apps/details?id=ma.wanam.efs
It saved me before =)

ledzpg said:
Try this:
https://play.google.com/store/apps/details?id=ma.wanam.efs
It saved me before =)
Click to expand...
Click to collapse
Dear this is a software to backup already existing EFS folder whereas my efs folder is totally empty...
Need someone to help me either with Verizon note 4 efs folder or help me on how to recover already backed up efs folder through TWRP..

Hello, I have the same problem with my sm-n910t. have you found the solution.. it would be a big help. thanks in advance.

Find the efs file compatible for your phone from google and install it into your phone using Odin