my galaxy note 2 (GT-N7105) is no service and not available storage :crying: how can i fix it pls anyone help me
PS: this videos phone exactly sama as mine phone
ibizadesert said:
my galaxy note 2 (GT-N7105) is no service and not available storage :crying: how can i fix it pls anyone help me
PS: this videos phone exactly sama as mine phone
Click to expand...
Click to collapse
What did you. Havent looked at the vid so far, but it woud be nice to have a few more facts.
Did you tried to install a custom rom (modified Android-Software) or you are on the original Andrid Software? Since when you having the Probems?
No Service sounds like an EFS Problem, if you did a SW Change and it doesnt worked out well. Having no storage (if you mean ext. SD-Card) could be also a sign of a non proberly installation.
Same here maybe efs as you have imei unknown
Sent from my GT-N7105 using xda app-developers app
thedadio said:
Same here maybe efs as you have imei unknown
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Agreed, looks like a fried efs partition. And that usually happenes after trying to flash an OLD ROM aftetr flashing a new one. As the new ROM does something to the EFS partition(i am not a dev so have not clue what) that makes it screwed when you try to flash old ROMS.
I would try to flash a new ROM again and see what happenes. And do search for invalid IMEI Note 2 and you will find ALOT of help.
If you did flash a new ROM and having these issues then, take your efs.img (which you should have backup after rooting your device on the official Android Software -> also called Stock Rom) copy it on a SD-Card, insert that card to your Note 2 and copy it to the SDCard0 folder (the internal storage), then do the following:
- Start in Recovery Mode
- wipe cache
- factory reset
- format /system (under adv. settings -> Storage...then you see it)
- flash the Rom again
- wipe cache
- wipe Dalvik Cache (under adv. settngs in Recovery)
- Reboot
Now check your IMMEI and your Service. IMMEI should be ok now and Service available and running. At least your SD-Card should be mounted now and available. I believe you tried to flash from a 4.1/4.2 System to a 4.3 System and you didn`t wiped the Dalvik-Cache, which is the System tree of Android, which got changed with Android 4.3. I think something went wrong in your installation, so this "tree" mght be corrupted. Be sure that you also install the right GAPPS (Google Services for Android 4.3, such as Google Play Store). You can flash it as .zip also over Recovery-Mode, after you flashed the ROM (Software).
If you didn`t save your EFS on any proberly running System before, you might get hard times recovering it.
SunShiner said:
What did you. Havent looked at the vid so far, but it woud be nice to have a few more facts.
Did you tried to install a custom rom (modified Android-Software) or you are on the original Andrid Software? Since when you having the Probems?
No Service sounds like an EFS Problem, if you did a SW Change and it doesnt worked out well. Having no storage (if you mean ext. SD-Card) could be also a sign of a non proberly installation.
Click to expand...
Click to collapse
thanks for trying helping me dude my IMEI / baseband version is UNKNOWN that is problem :crying: how can i repair my imei back ?
SunShiner said:
If you did flash a new ROM and having these issues then, take your efs.img (which you should have backup after rooting your device on the official Android Software -> also called Stock Rom) copy it on a SD-Card, insert that card to your Note 2 and copy it to the SDCard0 folder (the internal storage), then do the following:
- Start in Recovery Mode
- wipe cache
- factory reset
- format /system (under adv. settings -> Storage...then you see it)
- flash the Rom again
- wipe cache
- wipe Dalvik Cache (under adv. settngs in Recovery)
- Reboot
Now check your IMMEI and your Service. IMMEI should be ok now and Service available and running. At least your SD-Card should be mounted now and available. I believe you tried to flash from a 4.1/4.2 System to a 4.3 System and you didn`t wiped the Dalvik-Cache, which is the System tree of Android, which got changed with Android 4.3. I think something went wrong in your installation, so this "tree" mght be corrupted. Be sure that you also install the right GAPPS (Google Services for Android 4.3, such as Google Play Store). You can flash it as .zip also over Recovery-Mode, after you flashed the ROM (Software).
If you didn`t save your EFS on any proberly running System before, you might get hard times recovering it.
Click to expand...
Click to collapse
my internal storage is not available and i tried to copied stock rom to my Sd-card but when i do step by step (factory data reset , wipe cache , wipe dalvik cache , fix permission) rom will not be installed
thedadio said:
Same here maybe efs as you have imei unknown
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
my imei is unknown too. any ideas ? did you know fix that ?
Did you a backup of your EFS?..... that's what your IMMEI needs.
If not, try to download Stock ROM from a Source you know and maybe the immei will be rebuild. I don't know much about how to rebuild immei without EFS. Only thing I know is that there are not much ways. It's pretty difficult.
---------- Post added at 09:39 PM ---------- Previous post was at 09:32 PM ----------
Which ROM and Kernel you flashed?
BTW try to copy the files to thr phone without SDCard available thru a USB Cable to your PC. The phone should appear in the explorer list then.
SunShiner said:
Did you a backup of your EFS?..... that's what your IMMEI needs.
If not, try to download Stock ROM from a Source you know and maybe the immei will be rebuild. I don't know much about how to rebuild immei without EFS. Only thing I know is that there are not much ways. It's pretty difficult.
---------- Post added at 09:39 PM ---------- Previous post was at 09:32 PM ----------
Which ROM and Kernel you flashed?
BTW try to copy the files to thr phone without SDCard available thru a USB Cable to your PC. The phone should appear in the explorer list then.
Click to expand...
Click to collapse
i've flashed an old firmware and gone my imei. and now not available storage if i connect to PC storage is hidden.
ibizadesert said:
i've flashed an old firmware and gone my imei. and now not available storage if i connect to PC storage is hidden.
Click to expand...
Click to collapse
What you mean by old firmware? Like official firmware or modified (custom ROM)?
Maybe you have flashed an n7100 rom? I know the n7105 stored nv data in a different way to the n7100 so a standard efs backup using cwm or twrp will not suffice
Sent from my GT-N7105 using xda app-developers app
The 7105 posts in this forum are mixed with the posts for problems with the 7100 hence the title "Samsung Galaxy Note II GT-N7100 , N7105 " above
but the 7105 does have a different and way of storing data responsible for the correct operation of the IMEI and baseband along with other items
The backup programs provided by other members of the forums backup the efs partitions of the file system.... this is VITAL and allows user of the 7100 to restore their lost baseband and IMEI more easily than the on the 7105 Model.
It is possible to damage items in the NVram of the 7105 which can result in Baseband Unknown , IMEI unknown , lost of GPS functionality and also the loss of the internal storage file system making it appear as 0 bytes available which crashes applications as Android thinks there is no space on the emulated file system which presents its self as /storage/sdcard0 and other linked directories.
As a result of flashing the N7105 may users risk NVRAM corruption and may think they have a backup ... but they have no way of backing up the NVRAM only the EFS , as a result luck is the only thing between a phone with working IMEI , Baseband , GPS and internal storage becoming a tablet with WIFI only !!!!!
Their are some programs out on the net which claim to read and write the NVRAM such as QPST and NV-Reader Writer but Samsung use a modification to the
Qualcom message set which means that not all loacations are read and also writing the data back when a phone does have a corrupt NVRAM is a hit or miss affair.
the worst button on ODIN is the ERASE NVRAM button ..... if you have a 7105 model make sure you do NOT have this box ticked as it may not make you day a happy one !!!!
I would ask the Mods to separate the GT-N7105 posts into a separate forum as the 7100 and the 7105 share are lot but are different enough to make a big issue when people read posts on how to recover from
My BaseBand is UNKNOWN
My IMEI is UNKNOWN
My internal storage is 0Kb or doesnt mount properly as /Storage/sdcard0 ..../emulated/legacy etc
My GPS has stopped working
all of the above on the N7105 can point to a corruption of some data stored on the EMMC chip which we can call NVRAM within the device.
The 7100 is different as you have data in the /efs partition which MAY fix the problem
THE 7105 does NOT
As a result the 7105 at present has a good chance of taking a trip back to Samsung if you are unlucky enough to get a NVRAM problem...
Comments Please :
Am I right in thinking normal efs backups dont work with n7105?
Sent from my GT-N7105 using xda app-developers app
The normal EFS backups do contain what is in the EFS directory which is mounted BUT
BUT the 7105 carries addition data in the NVRAM and this is NOT repeat NOT backed up by
the backup programs or utilities in the forums.
As a result if you loose the IMEI and the Baseband you may be lucky and just damaged the efs directory and have a backup
BUT their is a good chance you may not get back to a working phone from and EFS backup as damaged NVRAM will not be fixed
by restoring an EFS backup
so if you have a GT-N7105 and you have 0kb of internal storage
or /and Baseband Unknown
or /and IMEI Unknown
or /and GPS not working
then you may be in a suitation which nobody on the forums has really got into that is full restore of N7105 NVRAM
from scratch.
As this contains the IMEI then nobody is going to post their own backup for you to use
and the NV reader Writer or QPST or the Pro Qualcom reader tools are old and have read errors in them
If anyone has performed a full backup of N7105 NVRAM then erased it ,,,, then restored from backup
please let us know as nobody appears to have proved to have tested a NVram backup and restore cycle.
Related
First what is efs-folder?
This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location.
"xda"
So I want to make a backup on my Samsung Galaxy Tab,Samsung Galaxy S and Galaxy Y with Rootexplorer.(easy way)
Created a .tar file works on my Tab and Galaxy S, but on my Galaxy Y the folder is empty!!! flashed my Galaxy Y a few times with customs roms.
So whats going on
Is there anyone out there with same problems???
Phone calls works fine on my Galaxy Y, IMEI still there but the efs folder is empty, flashed a few times to stock but still empty.
Phone rooted tryied a few version with Rootexplorer and Terminal Emulator.
demir02 said:
First what is efs-folder?
This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location.
"xda"
So I want to make a backup on my Samsung Galaxy Tab,Samsung Galaxy S and Galaxy Y with Rootexplorer.(easy way)
Created a .tar file works on my Tab and Galaxy S, but on my Galaxy Y the folder is empty!!! flashed my Galaxy Y a few times with customs roms.
So whats going on
Is there anyone out there with same problems???
Phone calls works fine on my Galaxy Y, IMEI still there but the efs folder is empty, flashed a few times to stock but still empty.
Phone rooted tryied a few version with Rootexplorer and Terminal Emulator.
Click to expand...
Click to collapse
The /efs partition is encrypted and hidden in SGY
Is there a way to save it??
I tried this tool a for a minute
http://forum.xda-developers.com/showthread.php?t=1308546
backup .tar and .img failed
anyone found a solution how to backup the EFS?
Have tried several tools and backup was always empty
MrButcher said:
anyone found a solution how to backup the EFS?
Have tried several tools and backup was always empty
Click to expand...
Click to collapse
There's a good chance, that /dev/bml15 is the efs or equivalent partition.
Sent from my SGSII using Tapatalk 2 & Swype
(I've found this old topic, which is not answered yet)
After examining a lot of bml15 dumps I conclude, SGY and companion does not have EFS folder, but have let's-call EFS partition, which is actually bml15 partition.
I'ts not so easy to loosing your EFS data (eg IMEI), but using Odin, accidentally you can (by clicking wrong option)
For safety reasons it's a good advice to install Galaxy Toolbox and have a bml15 backup in a safe place!
Try efs pro ...software backup u efs data ...
Sent from my GT-S5360 using xda premium
Doky73 said:
(I've found this old topic, which is not answered yet)
After examining a lot of bml15 dumps I conclude, SGY and companion does not have EFS folder, but have let's-call EFS partition, which is actually bml15 partition.
Click to expand...
Click to collapse
/efs , however, does exist on SGY, but is empty
Hey!
I am new here on xda.
I flashed a lot of custom roms on my SGY.
Finally, i saw that my efs was empty.
The IMEI was still correct, but the phone didn't detect any sim card.
I tried restoring it to the stock firmware, but the results were the same.
I flashed the CSC, PDA, etc for my country but the phone didn't detect any sim card.
Please Help.
sarthakmital8g said:
Hey!
I am new here on xda.
I flashed a lot of custom roms on my SGY.
Finally, i saw that my efs was empty.
The IMEI was still correct, but the phone didn't detect any sim card.
I tried restoring it to the stock firmware, but the results were the same.
I flashed the CSC, PDA, etc for my country but the phone didn't detect any sim card.
Please Help.
Click to expand...
Click to collapse
Did you flash the firmware from my firmware thread?
The efs partition in a galaxy y is not mountable and is untouched
Flashing a rom will not change it
The only reason you would loose imei is if your baseband didn't match the kernel ramdisk ril file but you can just flash the correct ril but this only effects custom stock based roms based on new firmware whilst you are using an old kernel ramdisk
Anyway - to cut a long story short - flashing a rom has no effect on efs partition
Goto my firmware thread and flash the firmware from there
If it doesn't work after that check the sim card works - Remove it & put it back in again & check there isn't a problem with your operator
http://forum.xda-developers.com/showthread.php?t=2568853
Hi all,
I have had my Note II for a day now and I love it but I seem to have an issue. I rooted and installed CWM 6.0.1.5 (modified version by Phil I believe) using Odin and I of course made a backup of my stock rooted ROM before I started flashing anything but when I tried to restore my Nand it says that it cant find the files and cant open the location. The CWM backup file IS there cause I can see it when I plug my phone into my computer but it wont restore and yes... I've tried EVERY restore option there is in CWM - Restore, Advanced Restore, Restore from External, Advanced Restore from External, so on and so on...
Can anyone tell my why I cant restore my Nandroid? This concerns me as well should I ever need to restore my backed up EFS as again, it just wont restore anything from CWM.
Anyone else with this issue or know what to do about it?
Also,
When I choose to flash anything from Internal SD it is now taking me to a list that shows /0, /obb and /legacy (or something like that) and then I have to choose /0 in order to gain access to my actual Internal files.
I actually have 2 of these sets of folders some how after flashing so now when I try and flash from Internal SD I have to choose /0 AND THEN ANOTHER /0 to access the internal card from CWM. This is quite weird and annoying to say the least. This behavior is also shown when searching my device using ANY file explorer and when I connect my phone to my computer as well - IE. I have all of these extra folders showing.
Can ANYONE explain why this is happening and how to avoid it if at all possible? Is this just something new in 4.2? I am currently running Jellybam 3.52 - 4.2.1 ROM.
Thanks,
Is your Nandroid backup from CWM or TWRP?
I've seen articles regarding the backup function of CWM, the backup files have to be in the following path on either the Internal or External SD Card. I'll use the below path as an example for an external SD card.
externalsdcard/clockworkmod/backup/[What ever you want the backup to be]
When you use the restore function from CWM and navigate to Restore from External/Internal SD Card. It should come up with the name of the folder you chose in [What ever you want the backup to be] and be able to restore your Nandroid backup.
Jonnit said:
Is your Nandroid backup from CWM or TWRP?
I've seen articles regarding the backup function of CWM, the backup files have to be in the following path on either the Internal or External SD Card. I'll use the below path as an example for an external SD card.
externalsdcard/clockworkmod/backup/[What ever you want the backup to be]
When you use the restore function from CWM and navigate to Restore from External/Internal SD Card. It should come up with the name of the folder you chose in [What ever you want the backup to be] and be able to restore your Nandroid backup.
Click to expand...
Click to collapse
My Nand is in CWM. I dont use TWRP.
As I said... My backup is on my internal sd card in the exact same format as you described but when I go to CWM and try to restore it first says "cannot open directory" and then immediately says "no files found"
Ive been using CWM since my original SGS and I have never seen this happen before. I can see it in my File Explorer, I can see it on my computer when I plug in the device but I cant get CWM to find the file to restore it.
Im about as confused as it gets...
Im testing something right now... I am making a new backup of my Jellybeer ROM to my External SD card to see what happens. IF it will find the files after its done I will advise but I still dont get why it wont restore from my internal card...?
*EDIT* So it seems to have backed up to the ext. sd card and I can see this file when I choose to restore from ext. sd but... it was the FASTEST backup Ive ever seen. It literally took like 45 seconds if that so I hope its a full back up!
IF my memory serves me correctly... When I backed up my stock ROM (my initial back up), I checked for the restore when it was done and it was there but then I flashed Hyperdroid and then I flashed PACman and then tried to restore my original Nand and it wouldn't let me so I wonder if I flash something else (which i don't want to do right now cause Jellybeer is serving me well at the moment) am I going to lose the ability to flash my Nand again?
Small bump...
yiannisthegreek said:
Small bump...
Click to expand...
Click to collapse
Ok so... NEW ISSUE!!!
I tried to restore the nand I made yesterday to my ext sd card (as I mentioned 2 posts back) and it said MD5 mismatch?! WTF?! How is that even possible? Can anyone please advise why my CWM is acting so weird?! Is there another version I can download perhaps? I am at a complete loss...
yiannisthegreek said:
Ok so... NEW ISSUE!!!
I tried to restore the nand I made yesterday to my ext sd card (as I mentioned 2 posts back) and it said MD5 mismatch?! WTF?! How is that even possible? Can anyone please advise why my CWM is acting so weird?! Is there another version I can download perhaps? I am at a complete loss...
Click to expand...
Click to collapse
Is there really no one who can help me with on this or give me some advice?
Md5 corrupted. ..
I.e your backup are corrupted.
Do factory reset then flash stock rom
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Md5 corrupted. ..
I.e your backup are corrupted.
Do factory reset then flash stock rom
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply but... What would cause this to happen? Did you read my post where I backed up to my external sd card? Like I said... The backup literally only took like 45 seconds to complete which is weird unto itself.
What will flashing a stock ROM do to fix this? And when you say "stock" do you mean like "stock - unrooted"?
did u install cm 10. just read it propyl with cm 10.1 ie jb 4.2 creates a 0 folder all ur files get put in there
put anither rom on card delete the 0 folder then go to this link http://forum.xda-developers.com/showthread.php?t=1896696
every thing there you need to flash another rom or recovery
try chenglu recovery
dr ketan has done a very good usefull thread
hope it helps,,sounds like your backup is corrupt
sloppy1 said:
did u install cm 10. just read it propyl with cm 10.1 ie jb 4.2 creates a 0 folder all ur files get put in there
put anither rom on card delete the 0 folder then go to this link http://forum.xda-developers.com/showthread.php?t=1896696
every thing there you need to flash another rom or recovery
try chenglu recovery
dr ketan has done a very good usefull thread
hope it helps,,sounds like your backup is corrupt
Click to expand...
Click to collapse
Chenglu is the one I used when I rooted my device by using Dr. Ketans guide and now I cant get ANY of my NAND backups to restore...
With regard to the /0 file issue - Yes... I am running a 4.2.+ CM10.1 based ROM so I understand that it creates those /0 files but it just keeps on creating them after flashing anything new!!!
Your issue is related to the new JB 4.2 and multi-user feature. CWM cannot find backups since they are moved to a different folder
The day you need your backup, just install a JB 4.1.2, move your /0 folder to root of sdcard and run your nandroid
Phil3759 said:
Your issue is related to the new JB 4.2 and multi-user feature. CWM cannot find backups since they are moved to a different folder
The day you need your backup, just install a JB 4.1.2, move your /0 folder to root of sdcard and run your nandroid
Click to expand...
Click to collapse
Hi Phil,
Thanks for the reply my friend! So...you're saying that IF and when I need to restore my nand that I will have to install a 4.1.2 ROM first and then follow your instructions to move the /0 folder to the root of my sd card (i assume by using a file explorer of some kind in the 4.1.2 ROM itself?) and then flash my nand? Is that correct? Should I keep just any old 4.1.2 ROM on my device at all times for this purpose?
If so then what if I have multiple /0 files created as I do now? Currently I have 2 /0 folders and this seems to grow as I flash anything new. Do I then move ALL of the /0 folders to the root of my sd card before I can restore my nandroid backup?
Also... Why was I not able to restore from my external sd card using the option in your recovery either? I made a simple backup of my current 4.2.+ ROM to my external card and when I tried to restore it last night to test it said MD5 mismatch. Is this related to the 4.2 ROM issue as well?
yiannisthegreek said:
Chenglu is the one I used when I rooted my device by using Dr. Ketans guide and now I cant get ANY of my NAND backups to restore...
With regard to the /0 file issue - Yes... I am running a 4.2.+ CM10.1 based ROM so I understand that it creates those /0 files but it just keeps on creating them after flashing anything new!!!
Click to expand...
Click to collapse
delete 0 folder
flash cwm recovery with odin go into mounts
wipe caches and format system when done
power down then go into download mode
then flash stock img
that worked for me
sloppy1 said:
delete 0 folder
flash cwm recovery with odin go into mounts
wipe caches and format system when done
power down then go into download mode
then flash stock img
that worked for me
Click to expand...
Click to collapse
Im sorry but I dont know if I understand you completely...
Flash CWM with odin and then go into mounts? Firstly, what version of CWM are you saying to flash and then I assume you mean once thats done that I should then boot into recovery and then go into mounts? And then wipe caches, format system?
Can you clarify?
yiannisthegreek said:
Im sorry but I dont know if I understand you completely...
Flash CWM with odin and then go into mounts? Firstly, what version of CWM are you saying to flash and then I assume you mean once thats done that I should then boot into recovery and then go into mounts? And then wipe caches, format system?
Can you clarify?
Click to expand...
Click to collapse
re-dload chenglu recovery
when in recovery wipe data n dalvik then go into mounts then format system
then power down,
then download mode,
use odin to flash stock img
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
try this 1st
connect fone to pc,
open up 0 folder inside 0 fokder will be clockwork folder, drag it to root of sd card,
try restore it from there that might work
sloppy1 said:
re-dload chenglu recovery
when in recovery wipe data n dalvik then go into mounts then format system
then power down,
then download mode,
use odin to flash stock img
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
try this 1st
connect fone to pc,
open up 0 folder inside 0 fokder will be clockwork folder, drag it to root of sd card,
try restore it from there that might work
Click to expand...
Click to collapse
What I did was... I flashed v6.0.2.7 via ODIN (which has 4.2.+ ROM support) and I am now FINALLY able to restore my Nand back ups!!! The only thing now is that I apparently have 3 /0 folders on my device and I REALLY just want to know how to get rid of the extra folders and to know how to keep them from being created altogether!!!
I have one that has ALL of the original .zip files, gapps, etc that I installed on my device, then I have one that has an efs backup on it somehow and has a couple of application folders in it and then I have one that is like stock.
Why are these being created and how can I get rid of them? This is driving me CRAZY!!!
I had the same issue this morning.
I fixed it by installing the aroma file manager addon in Phil's CWM recovery and using aroma to copy the clockworkmod folder out of the /0 folder and back to the root of the sd card.
Then when I went into backup and restore the backup was visible again.
Once you have a rom installed you shoudl just be able to plug in via usb and just browse the sd card on your computer to move everything back out of the /0 folder
yiannisthegreek said:
Ok so... NEW ISSUE!!!
I tried to restore the nand I made yesterday to my ext sd card (as I mentioned 2 posts back) and it said MD5 mismatch?! WTF?! How is that even possible? Can anyone please advise why my CWM is acting so weird?! Is there another version I can download perhaps? I am at a complete loss...
Click to expand...
Click to collapse
You can install nandroid manager from playstore and you can fix nandroid md5 mismatch there or you can use terminal emulator to generate new md5 file in your nandroid (google it because i cant remember the command)
yiannisthegreek said:
Hi all,
I have had my Note II for a day now and I love it but I seem to have an issue. I rooted and installed CWM 6.0.1.5 (modified version by Phil I believe) using Odin and I of course made a backup of my stock rooted ROM before I started flashing anything but when I tried to restore my Nand it says that it cant find the files and cant open the location. The CWM backup file IS there cause I can see it when I plug my phone into my computer but it wont restore and yes... I've tried EVERY restore option there is in CWM - Restore, Advanced Restore, Restore from External, Advanced Restore from External, so on and so on...
Can anyone tell my why I cant restore my Nandroid? This concerns me as well should I ever need to restore my backed up EFS as again, it just wont restore anything from CWM.
Anyone else with this issue or know what to do about it?
Also,
When I choose to flash anything from Internal SD it is now taking me to a list that shows /0, /obb and /legacy (or something like that) and then I have to choose /0 in order to gain access to my actual Internal files.
I actually have 2 of these sets of folders some how after flashing so now when I try and flash from Internal SD I have to choose /0 AND THEN ANOTHER /0 to access the internal card from CWM. This is quite weird and annoying to say the least. This behavior is also shown when searching my device using ANY file explorer and when I connect my phone to my computer as well - IE. I have all of these extra folders showing.
Can ANYONE explain why this is happening and how to avoid it if at all possible? Is this just something new in 4.2? I am currently running Jellybam 3.52 - 4.2.1 ROM.
Thanks,
Click to expand...
Click to collapse
Is that cwm recovery on sdcard??? Please move it on your ext card and recover .
Or you got an md5 mismatch ? Use mismatch fixer or see my thread http://forum.xda-developers.com/showthread.php?t=2681072
Sent from my GT-S7562 using XDA Premium 4 mobile app
Hi all, I'm a new I9195GT owner (for a week already) and have been researching and having some satisfaction rooting and restoring all my apps with Titanium from my previous smartphone.
The phone works fine and I'm quite happy with it. I've already done a full backup with CWM recovery for any trouble I might come across in future but I don't know if a full backup from recovery contains all important and sensible data like EFS and NV data. Those two things are totally new for me as I'm coming from a HTC Desire which didn't require attention to those sensible points.
So I would be very grateful if anybody clears some doubts I have relating EFS and NV data:
- Does a full backup from recovery contain EFS and NV data, so in case that flashing a custom ROM results in corrupted EFS data, I would fix it just by restoring the full backup from recovery?
- What is the best and safest way for backup EFS and NV?
I've seen this post from arco68 which states a command I guess should be executed from Terminal directly in the smartphone, but I don't know how should that .img file restored to the phone in case it becomes corrupted.
I've also seen this post about the EFS Professional tool from lyriquidperfection but in the whole post I havent found anybody confirming it works in the S4 Mini i9195.... so it sounds good but I don't want to brick my new device being the first one to run the tool with the i9195
Thank you very much
As far as I know CWM does not back up EFS.
The good idea is to use TWRP recovery instead of CWM. TWRP does backup EFS.
You can get TWRP for 9195 here
http://forum.xda-developers.com/showthread.php?t=2449107
Thanks for the idea. I'm ready to install TWRP recovery but, before installing it and replacing CWM,
Is it possible to launch TWRP recovery from CWM recovery, as temporary? And when rebooting CWM is back.
I remember doing something like this in my previous device: from 4EXT recovery launching a CWM recovery for some particular reason I don't remember
Sent from my GT-I9195 using xda app-developers app
batareikin51 said:
As far as I know CWM does not back up EFS.
The good idea is to use TWRP recovery instead of CWM. TWRP does backup EFS.
You can get TWRP for 9195 here
http://forum.xda-developers.com/showthread.php?t=2449107
Click to expand...
Click to collapse
TWRP Recovery does not backup full EFS. IMEI is not included at least. Even though it lists a possibility of EFS backup, all it does is backups /efs partition. which does not contain IMEI in it. This concerns specifically I9195, which I own too and am researching this issue and also lost IMEI issue.
farewellartist said:
TWRP Recovery does not backup full EFS. IMEI is not included at least. Even though it lists a possibility of EFS backup, all it does is backups /efs partition. which does not contain IMEI in it.
Click to expand...
Click to collapse
I already had installed TWRP and made backups and nandroids....
So how can we safely backup IMEI in a way we can restore it in case it gets corrupted?
sergiosch said:
I already had installed TWRP and made backups and nandroids....
So how can we safely backup IMEI in a way we can restore it in case it gets corrupted?
Click to expand...
Click to collapse
Good question, I've been looking for answer for weeks.
sergiosch said:
I already had installed TWRP and made backups and nandroids....
So how can we safely backup IMEI in a way we can restore it in case it gets corrupted?
Click to expand...
Click to collapse
Guys!
The most simple method to backup our IMEI (efs folder) is:
1.Install rootexplorer
2.open it with superuser permission
3. Copy efs folder from root main folder to your sd card.
4.Upload from sd card to clouds to be sure you have a backup a different places.
5. Push thx for me
radicspeter said:
Guys!
The most simple method to backup our IMEI (efs folder) is:
1.Install rootexplorer
2.open it with superuser permission
3. Copy efs folder from root main folder to your sd card.
4.Upload from sd card to clouds to be sure you have a backup a different places.
5. Push thx for me
Click to expand...
Click to collapse
I did already that too, not with rootexplorer but TotalCommander which also has root access to any partition, I guess it performs the same backup just copying everything.
But then I don't know why it is valid to do "raw" directory/file copy with root explorer but it is not valid an EFS partition backup with TWRP recovery. I'm a newbie with this but, it seems the same to me....
Can anyone tell exactly in which file is stored imei? Isn't the same structure/process valid for other Galaxy brand smartphones so we can follow them?
radicspeter said:
Guys!
The most simple method to backup our IMEI (efs folder) is:
1.Install rootexplorer
2.open it with superuser permission
3. Copy efs folder from root main folder to your sd card.
4.Upload from sd card to clouds to be sure you have a backup a different places.
5. Push thx for me
Click to expand...
Click to collapse
I repeat, EFS FOLDER / PARTITION even on a raw byte level DOESN'T CONTAIN phones IMEI. This concerns specifically Samsung Galaxy S4 Mini LTE (I9195).
---------- Post added at 03:45 PM ---------- Previous post was at 03:31 PM ----------
sergiosch said:
I did already that too, not with rootexplorer but TotalCommander which also has root access to any partition, I guess it performs the same backup just copying everything.
But then I don't know why it is valid to do "raw" directory/file copy with root explorer but it is not valid an EFS partition backup with TWRP recovery. I'm a newbie with this but, it seems the same to me....
Can anyone tell exactly in which file is stored imei? Isn't the same structure/process valid for other Galaxy brand smartphones so we can follow them?
Click to expand...
Click to collapse
Normally, phones IMEI in previous galaxy devices (don't know about current S4, I own S4 Mini LTE), was stored in nv_data.bin file which was located in /efs folder on root. (which is a mount point for mmcblk0p10 partition in S4 Mini LTE). But, in this device, there is no nv_data bin file and IMEI is not stored nowhere close to efs partition. Not too many people own S4 Mini's and almost everybody whom I asked an information based their knowdledge on another devices and were feeding me false information I heard over and over again.
To clarify something, I know, that EFS partition doesn't contain IMEI, because:
No file in efs mount point contains IMEI.
No IMEI found checking EFS Professional backup (tar) on HEX level using various search methods. Even through-looked it, file is not that big.
No IMEI found through-looking .raw backup made using cygwin (which contains every single byte of partition, even though it is not a part of a file), which is 95+% warrant, that IMEI is not in EFS partition.
farewellartist said:
I repeat, EFS FOLDER / PARTITION even on a raw byte level DOESN'T CONTAIN phones IMEI. This concerns specifically Samsung Galaxy S4 Mini LTE (I9195).
---------- Post added at 03:45 PM ---------- Previous post was at 03:31 PM ----------
Normally, phones IMEI in previous galaxy devices (don't know about current S4, I own S4 Mini LTE), was stored in nv_data.bin file which was located in /efs folder on root. (which is a mount point for mmcblk0p10 partition in S4 Mini LTE). But, in this device, there is no nv_data bin file and IMEI is not stored nowhere close to efs partition. Not too many people own S4 Mini's and almost everybody whom I asked an information based their knowdledge on another devices and were feeding me false information I heard over and over again.
To clarify something, I know, that EFS partition doesn't contain IMEI, because:
No file in efs mount point contains IMEI.
No IMEI found checking EFS Professional backup (tar) on HEX level using various search methods. Even through-looked it, file is not that big.
No IMEI found through-looking .raw backup made using cygwin (which contains every single byte of partition, even though it is not a part of a file), which is 95+% warrant, that IMEI is not in EFS partition.
Click to expand...
Click to collapse
Thanks mate. Pretty clear :good:
I was also not confident about some tutorials I read in other forums claiming that just doing a copy of file structure from /EFS folder would backup our IMEI. Your explanation is appreciated.
Hope to find some way to effectively backup sensitive data as IMEI is....
sergiosch said:
Thanks mate. Pretty clear :good:
I was also not confident about some tutorials I read in other forums claiming that just doing a copy of file structure from /EFS folder would backup our IMEI. Your explanation is appreciated.
Hope to find some way to effectively backup sensitive data as IMEI is....
Click to expand...
Click to collapse
Found it! Making guide right now. Basically IMEI is contained in both mmcblk0p11 and mmcblk0p12 partitions. Samsung apparently has developed a new error-safe phone nv data preservation system, I'll explain in details in tutorial.
farewellartist said:
Found it! Making guide right now. Basically IMEI is contained in both mmcblk0p11 and mmcblk0p12 partitions. Samsung apparently has developed a new error-safe phone nv data preservation system, I'll explain in details in tutorial.
Click to expand...
Click to collapse
Great news! looking forward to read that guide :good::good:
sergiosch said:
Great news! looking forward to read that guide :good::good:
Click to expand...
Click to collapse
How do you mount those partitions? I've tried with no success. All I get is "mount: No such device".
deliog said:
How do you mount those partitions? I've tried with no success. All I get is "mount: No such device".
Click to expand...
Click to collapse
Don't mount, just backup.
Through terminal emulator, enter commands
su
dd if=/dev/block/mmcblk0p11 of=/dev/block/mmcblk0p12
And how to restore later if IMEI gets corrupted/null?
Sent from my GT-I9195 using xda app-developers app
sergiosch said:
And how to restore later if IMEI gets corrupted/null?
Sent from my GT-I9195 using xda app-developers app
Click to expand...
Click to collapse
See this: http://forum.xda-developers.com/showthread.php?t=2569532
sergiosch said:
Great news! looking forward to read that guide :good::good:
Click to expand...
Click to collapse
Could you (or someone) PLEASE post or send PM with backups of partition mmcblk0p11 and mmcblk0p12? While researching this issue, I trashed 2 OF MY PHONES and nulled my IMEIs because of delusion caused by memory of having a backup, which I didn't. It's a pity to give away such a fortune for spares. I need NV blocks to hex compare them with blocks I got from another healthy I9195. Since IMEI numbers of different phone blocks will be different, difference will show on hex level too, which will help me determine exact address of IMEI location, after which I could modify my trashed NV blocks at determined memory address with my original IMEI, which could save me from watching at useless brick. And also would help me at development of I9195 IMEI Restore tool.
Disclaimer: I am not modifying my IMEI nor doing any actions which end-target is modification of original IMEI and differing it from original one. I am modifying nulled (trashed, unoriginal) IMEI to its ORIGINAL state which ultimately couldn't be called nothing else but RESTORING. I won't use IMEI from gathered NV blocks. I just need a another healthy block to fix my issue and help develop tools so others could be able to sleep at nights without issue that causes me sleepless nights.
farewellartist said:
Could you (or someone) PLEASE post or send PM with backups of partition mmcblk0p11 and mmcblk0p12? While researching this issue, I trashed 2 OF MY PHONES and nulled my IMEIs because of delusion caused by memory of having a backup, which I didn't. It's a pity to give away such a fortune for spares. I need NV blocks to hex compare them with blocks I got from another healthy I9195. Since IMEI numbers of different phone blocks will be different, difference will show on hex level too, which will help me determine exact address of IMEI location, after which I could modify my trashed NV blocks at determined memory address with my original IMEI, which could save me from watching at useless brick. And also would help me at development of I9195 IMEI Restore tool.
Disclaimer: I am not modifying my IMEI nor doing any actions which end-target is modification of original IMEI and differing it from original one. I am modifying nulled (trashed, unoriginal) IMEI to its ORIGINAL state which ultimately couldn't be called nothing else but RESTORING. I won't use IMEI from gathered NV blocks. I just need a another healthy block to fix my issue and help develop tools so others could be able to sleep at nights without issue that causes me sleepless nights.
Click to expand...
Click to collapse
I haven't done yet any of the backup processes you explain, so I don't even have the files you're asking for, but with all the gratitude and admiration I feel for the developers I wouldn't feel any confortable sending sensible data from part of a nandroid backup.... speaking just for myself of course, if I could choose how to help a developer I would preferr doing a donation to help him recover the hardware he has broken to help others. Some months ago I heard a friend telling that he had been scammed with a phone he bought in some cash converter and only worked for one day, then it became with null IMEI, and he suspected someone had "stolen" or "shutdown" his IMEI for unknown reasons...
sorry to say that, maybe I'm an ignorant but I just don't feel confortable with what you are asking directly to me
So I found myself wondering how can I make life difficult for myself... I did a software upgrade in Kies on my T805 and now I have a default IMEI...
I was on cm11 before doing the upgrade to 5.0.2
Has this happened to anyone or does anyone have any idea how to fix it?
Many thanks for any reply.
That shouldnt have happened but youre not the first person to state that cm has messed with the partitions. Id stick with stock based roms in future.
Download EFS professional then under the samsung tools tab select other tools then 'Repair NV data from internal file backup'
If youre lucky it will be restored.
Now some friendly advice, ALWAYS make a full backup via recovery before messing with anything custom on your device, especially make sure the EFS partition is backed up.
ashyx said:
That shouldnt have happened but youre not the first person to state that cm has messed with the partitions. Id stick with stock based roms in future.
Download EFS professional then under the samsung tools tab select other tools then 'Repair NV data from internal file backup'
If youre lucky it will be restored.
Now some friendly advice, ALWAYS make a full backup via recovery before messing with anything custom on your device, especially make sure the EFS partition is backed up.
Click to expand...
Click to collapse
Thanks for the reply, sadly it restore a different default IMEI ending in /01 instead of /17.
I was 100% sure I had backed-up my efs, turns out I did but on my phone x(.
Any other suggestions?
Try this. Make a backup in recovery of the efs partition.
Boot into android then using a root file explorer open the efs folder then delete nv_data.bin and nv_data.bin.md5 then reboot.
See if this replaces the deleted files with the backup.
ashyx said:
Try this. Make a backup in recovery of the efs partition.
Boot into android then using a root file explorer open the efs folder then delete nv_data.bin and nv_data.bin.md5 then reboot.
See if this replaces the deleted files with the backup.
Click to expand...
Click to collapse
It does but not with the correct imei. Thanks for the reply!
What IMEI does it give?
ashyx said:
What IMEI does it give?
Click to expand...
Click to collapse
A default imei ending in / 17 instead of / 01
DieZz said:
A default imei ending in / 17 instead of / 01
Click to expand...
Click to collapse
You may as well post it as its not a valid imei, it's a generic imei.
Is it 004999010640000?
Dear,
I think that my question was raised many-time in this forum, and i really tried to read any thread similar to my issue, and i tried all solutions but no luck, and I am feeling that i am missing something, here my story :
Problems started with me when i bought a new battery for my phone ( i don't think that this cause the problem, because as my knowledge imei has nothing to do with battery), please correct me if i am wrong.
So, when i putted the new battery, I got this silly issue 'not registered on network', and then i knew that i lost my imei as well (it is dummy number like 0049... )
So what i did is i tried to flash the modem, i tried many version, but this did not resolve my problem.
Then i tried to install the firmware from the beginning and rested all data and wipe all data and cache, (here i think i missed to take backup of my efs files). does flashing a new firmware,reset or wipe data will remove the efs files?
Installing new firmware didn't work also.
So i tried to backup and restore efs files, but it did not work also.
Please can you help me resolving this issue, since now i am out of idea and i don't know what to do.
Thank you in advance
here
Thank you for your answer,
But i already tried to install many modem, and i did tried this one XXDME4 modem, but not luck.
i am struggling here,
Please help me
Please help :crying:
did you use odin and thr newest stock firmware from i.e. sammobile?
Hi,
Yes i did, but it did not solve the issue
EFS
I have been trying to understand the phone system. I could not locate the detailed information on net but have guessed based on my experience and if I would have designed the phone.
1. Downloader area: I think this is fused when the system is fabricated and cannot be changed. It's job is to receive the image and flash into phone's bootloader area. (This is equivalent to EEPROM in PC mother boards)
2. Bootloader area: This is where recovery gets loaded. This is where root of file system is created "/". and basic directories are created. Both 1 and 2 are located separately from 3.
3. Internal Storage: This is separate memory chip. This is usually partitioned in multiple partitions and one of them is EFS (encrypted file system). These partitions are formatted and mounted on various directories in basic file system. The /system mountpoint contains the OS. This is the reason, why we format it and then install the system files from partition mounted at /sdcard mountpoint. Normally this is known as usb storage (internal storage).
4. External sdcard: It is external storage card which is mounted on /external_sdcard or something similar.
I have galaxy note 2. It started rebooting once in a while for last two months. In August, it refused to boot up. I could boot up the bootloader and downloader section both. At that time, the memory areas were getting corrupted. Probably, my galaxy note 2 was one of those initial one with bad memory chip. Later in bootloader section, I could figure out that the EFS could not be mounted. In service center as well as with other technicians, it was told that memory chip is bad. One of the technician replaced the chip. I opted for this repair insted of mother board replacement as it was far cheaper. He also got the EFS restored from samsung service.
My understanding of EFS is that this file system is encrypted with a key. This key is encrypted further with private key of certificate of manufacturer. All programmes can use public key to get the key and hence the IMEI and other information. The certificate containing public key should be part of EFS filesystem header. At OS level, this whole process can be bypassed and you can have a mechanism for any IMEI or any other parameter. It is the OS which controls the radio and transmits the information to network.
So, get your phone checked if the memory has not gone bad. Even if you can reformat and use it, it will fail soon. Further, if you are not using customized OS (which bypasses EFS protection), or you have a tool to create an EFS on your own with your own certificate and information, than you need to get in touch with Samsung service. They will create the EFS image and put it back in your phone or give it to you for putting it back.
If certain memory area is bad and system is able to boot, then it creates the default EFS that is where you get changed IMEI.
aj1m said:
Dear,
I think that my question was raised many-time in this forum, and i really tried to read any thread similar to my issue, and i tried all solutions but no luck, and I am feeling that i am missing something, here my story :
Problems started with me when i bought a new battery for my phone ( i don't think that this cause the problem, because as my knowledge imei has nothing to do with battery), please correct me if i am wrong.
So, when i putted the new battery, I got this silly issue 'not registered on network', and then i knew that i lost my imei as well (it is dummy number like 0049... )
So what i did is i tried to flash the modem, i tried many version, but this did not resolve my problem.
Then i tried to install the firmware from the beginning and rested all data and wipe all data and cache, (here i think i missed to take backup of my efs files). does flashing a new firmware,reset or wipe data will remove the efs files?
Installing new firmware didn't work also.
So i tried to backup and restore efs files, but it did not work also.
Please can you help me resolving this issue, since now i am out of idea and i don't know what to do.
Thank you in advance
Click to expand...
Click to collapse