Somehow the EFS partition on my P5WIFI got damaged and everything was lost. Is it possible someone has a dump of the files stored in there? The loss of the data in this partition causes strange problems with the stock Android.....
I managed to recreate some amount of the EFS partition by using "EFS Professional". The Wifi MAC is incorrect (looks like a generic one) but hey whatever.
http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546
swaaye said:
Somehow the EFS partition on my P5WIFI got damaged and everything was lost. Is it possible someone has a dump of the files stored in there? The loss of the data in this partition causes strange problems with the stock Android.....
Click to expand...
Click to collapse
You have got a Wifi Tab , and Wifi Tab does nt have got a EFS Partion.
I think you need a PIT file.
Normaly if you flash a Stock Rom this will restore a EFS Partion in Phones.
On the WiFi tablets, the EFS partition stores unique data like your WiFi MAC address.
I'm not sure what happened to this tablet. It was my mother's until last week. Somehow it wiped itself. All of her data was gone. It seems as if something caused the tablet to wipe the data partition, and that the EFS partition was also damaged. The EFS partition was not mountable in recovery and errors were displayed. Nothing actually formats EFS though, including PIT, so I had to go in with ADB shell and format it myself.
But without the EFS data, strange things happen like the stock ROM will go into factory mode. It puts a "factory mode" icon on the homescreen, the lockscreen and power menus don't work, and the initial setup wizard is never shown. Fortunately "EFS Professional" has a function that recreates various files within the EFS partition and this restores normal functionality.
Related
My best bud was complaining about how slow his stock SGS was so I decided to help as I've fixed about 20 phones now without any issues! Until now!
Problem
Lost Contacts which were stored to phone memory
Lost memos
Almost all programs are Force Closing
History
Installed clockwork recovery as per Cyanogen Wiki page (http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide)
Then using the new SpeedMod kernel by Hardcore, I rooted the phone and also converted the file system to EXT4 to ensure the lagfix worked nicely
The Recovery automaticalled generated a Nandroid back-up before the file system conversion took place.
When phone started, a lot of programs Force Closed, so we ran a Fix Permissions and this solved most problems. However, a few days have passed and now the phone is constantly FC. The loss of contacts and memo's was annoying but he wasn't too bothered as had various back-ups
So I tried a Nandroid restore which works apart from system.img which it cannot find.
I wonder if the system.img backup doesn't work since the file system was changed to EXT4? Do you think if I push the nandroid backup using ADB, it will successfully restore the phone with contacts and memo's too?
That's why I never touch someone else's phone. Always something goes wrong that never gone on my phone.
Sounds like you need to do...
Wipe data/factory reset
Wipe cache partition
...in clockworkmod to make a clean install.
If your friend didn't set up a syncronisation in "Accounts and sync" between google and the phone, AFAIK you cannot revert back contacts and memos
After turning the file system to EXT4, it removes backups.Because its not a nandroid backup. Just backing up your files before the partition formatting. So, no luck.
I'm not a android expert, so I might be wrong about it.
So, somehow I got my phone into a bootloop, and I made a backup of my data partition with TWRP. I reset it, and tried to restore the data partition, and the corrupted file is in there (was trying to edit settings.db for hotspot on Sprint). Anyways, when I restore the data partition, it bootloops again. So I want to get into the backup, and replace the bad settings.db file so I can restore the partition and have all my data back. How can I browse the backup using my windows 8.1 pc?
i dot imgur dot com/evfiO6Z.png
you cant. why are you restoring your data partition? that wont boot up, since its system that you edited. restore the whole nandroid backup, boot, system, and data. and if you didnt make a backup of boot or system, then reflash your rom to fix it. flash it dirty, as to not lose your data. and if you dont have a rom to flash, then youre stuck having to flash the factory img.
simms22 said:
you cant. why are you restoring your data partition? that wont boot up, since its system that you edited. restore the whole nandroid backup, boot, system, and data.
Click to expand...
Click to collapse
I only did data. The backup was AFTER it was in the bootloop, so I only backed up data.
ilarson008 said:
I only did data. The backup was AFTER it was in the bootloop, so I only backed up data.
Click to expand...
Click to collapse
ahh.. then in no way will it get restored, since its the system partion that you actually messed with. data just holds all your user data, thats all.
simms22 said:
ahh.. then in no way will it get restored, since its the system partion that you actually messed with. data just holds all your user data, thats all.
Click to expand...
Click to collapse
That is EXACTLY what I want to restore. All my apps, settings, pictures, etc etc etc.
I've got the phone factory reset, on and working.
ilarson008 said:
That is EXACTLY what I want to restore. All my apps, settings, pictures, etc etc etc.
I've got the phone factory reset, on and working.
Click to expand...
Click to collapse
now you can try to restore your data. your sd card stugf, like photos, dont get deleted until you wipe or format your storage.
simms22 said:
now you can try to restore your data. your sd card stugf, like photos, dont get deleted until you wipe or format your storage.
Click to expand...
Click to collapse
When i restore the data backup, the phone goes into a bootloop and will not boot.
ilarson008 said:
When i restore the data backup, the phone goes into a bootloop and will not boot.
Click to expand...
Click to collapse
well, unfortunately, it doesnt seem to be a good back up
if you factory rest again, have google restore your stuff. itll restore your apps, and main settings, and even wallpaper. and your photos are in your storage already. unless you didnt have it enabled to back up everything in the main settings.
simms22 said:
well, unfortunately, it doesnt seem to be a good back up
if you factory rest again, have google restore your stuff. itll restore your apps, and main settings, and even wallpaper. and your photos are in your storage already. unless you didnt have it enabled to back up everything in the main settings.
Click to expand...
Click to collapse
I have never had luck with auto backup. It doesn't seem to capture everything. Plus there were things that I stored on internal storage (used to be my SD card on my Samsung phones ) that wouldn't have been backed up, like my Pokemon saved game. I knew I should have copied my internal storage before trying to restore, but I thought the data backup would have done it. Great.
Not sure if this is what your looking for but try nandroid manager: https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore
Edit: thats on device only, sorry about that. I had an issue in the past where I didn't have any apps saved via TiBu and had only a TWRP backup. Installed a clean ROM, rooted and then used the app posted to browse the backup on my phone and restore the vital apps that I needed. (Like google authenticator)... Good luck
I'm panicking very much right now.
I did a big, big stupid and accidentally wiped my entire /data partition, including /sdcard (!!) in TWRP 3.0.4.1 while attempting to change the filesystem of my /data partition from F2FS to EXT4. I did a full backup of my phone, including /data partition (but excluding /data/media/0/ which is the location for /sdcard of course) on my phone prior to attempting to change the filesystem.
I didn't think that this would also wipe /sdcard, and ALL MY FILES INCLUDING MY BACKUP...
I'm frantically searching through Google as we speak for guides to clone these formatted sectors over USB (I'd imagine using ADB shell) to a PC and use Windows file or partition recovery tools to try and save every, if not most files.
Please lend me your knowledge and links to fixing this issue, Android community. <3
In older Android versions the /sdcard partition was it's own partition, which is why I didn't think of copying all my files over to a PC before making changes to /data.
well, when you wipe data from any partition in twrp it sort of resets all space to be overwritten. The data that is marked for overwrite doesn't remain when you full wipe. Since you changed the file system, the data was removed and overwritten by the wipe with blank space.... i hope you had at least some of it backed up on your pc. I never use those apps personally, i always hard backup all my things with a drag and drop onto my pc. I highly recommend it, saves you a disaster. Im very sorry.... i hope you didnt lose anything really important.
OcazPrime said:
well, when you wipe data from any partition in twrp it sort of resets all space to be overwritten. The data that is marked for overwrite doesn't remain when you full wipe. Since you changed the file system, the data was removed and overwritten by the wipe with blank space.... i hope you had at least some of it backed up on your pc. I never use those apps personally, i always hard backup all my things with a drag and drop onto my pc. I highly recommend it, saves you a disaster. Im very sorry.... i hope you didnt lose anything really important.
Click to expand...
Click to collapse
Heh, that's exactly what happened. I'm gonna attempt this guide: https://forum.xda-developers.com/ga...de-internal-memory-data-recovery-yes-t1994705
Basically try to use "dd" to make a RAW copy of "dev/block/dm-0" which according to the mount command I ran in TWRP's terminal shell, is what block /data is used on OnePlus 3T (OOS 4.1.3).
Wish me luck.
So basically I dont have my efs backup..
and twrp messed up my efs partition..
Is it possible to use another efs?
(°_o) said:
So basically I dont have my efs backup..
and twrp messed up my efs partition..
Is it possible to use another efs?
Click to expand...
Click to collapse
I have had a similar problem recently: I corrupted my EFS partition
and I didn't have a buckup but I kind of solved the issue
I advice you to do a TWRP backup including only the /data partition as the screenshot below shows
Then you should install a stock rom ( then flash cf-auto root through Odin), reinstall your daily rom and before letting it boot for the first time, make sure to restore the /data backup you made earlier
Hopefully this should fix your issue
MYEUHD said:
I have had a similar problem recently: I corrupted my EFS partition
and I didn't have a buckup but I kind of solved the issue
I advice you to do a TWRP backup including only the /data partition as the screenshot below shows
Then you should install a stock rom ( then flash cf-auto root through Odin), reinstall your daily rom and before letting it boot for the first time, make sure to restore the /data backup you made earlier
Hopefully this should fix your issue
Click to expand...
Click to collapse
Does the stock rom have efs? Afaik.. efs is device specific?
I can just flash the efs if theres one on the stock rom.
Which stock rom did you download.
(°_o) said:
Does the stock rom have efs? Afaik.. efs is device specific?
I can just flash the efs if theres one on the stock rom.
Which stock rom did you download.
Click to expand...
Click to collapse
According to @xc-racer99 , When you install a custom ROM for the first time, it actually copies the EFS partition and leaves the original untouched. This way, when you go back to stock and then re-install a custom ROM it, takes a copy again from the original
I downloaded Gingerbread 2.3.6 for XXJVT from this thread: https://forum.xda-developers.com/showthread.php?t=1102881
(replace XXJVT with your baseband version which can be found under settings>about phone in your current rom)
when I have corrupted my EFS partiton, I flashed the stock rom and then it solved half the issue
My phone generated a generic IMEI adress and it's functioning as well as it did in the past
There's only one problem : each time I boot, I get the following message "A problem was detected with your device. Your device IMEI number is invalid. An invalid IMEI number could cause network issues including the inability to call emergency numbers." yet everything works fine as I said earlier
So here's my current EFS backup, I made it through TWRP
You have to uncompress it and copy it to the folder where your TWRP backups are kept
that is /sdcard/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your internal storage
and /external_sd/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your external MicroSd card
Finally, Restore it! (through TWRP of course)
MYEUHD said:
According to @xc-racer99 , When you install a custom ROM for the first time, it actually copies the EFS partition and leaves the original untouched. This way, when you go back to stock and then re-install a custom ROM it, takes a copy again from the original
I downloaded Gingerbread 2.3.6 for XXJVT from this thread: https://forum.xda-developers.com/showthread.php?t=1102881
(replace XXJVT with your baseband version which can be found under settings>about phone in your current rom)
when I have corrupted my EFS partiton, I flashed the stock rom and then it solved half the issue
My phone generated a generic IMEI adress and it's functioning as well as it did in the past
There's only one problem : each time I boot, I get the following message "A problem was detected with your device. Your device IMEI number is invalid. An invalid IMEI number could cause network issues including the inability to call emergency numbers." yet everything works fine as I said earlier
So here's my current EFS backup, I made it through TWRP
You have to uncompress it and copy it to the folder where your TWRP backups are kept
that is /sdcard/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your internal storage
and /external_sd/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your external MicroSd card
Finally, Restore it! (through TWRP of course)
Click to expand...
Click to collapse
(°_o) said:
Does the stock rom have efs? Afaik.. efs is device specific?
I can just flash the efs if theres one on the stock rom.
Which stock rom did you download.
Click to expand...
Click to collapse
Nope, a stock ROM won't have it - it's device specific and holds the IMEI. If you've corrupted the original (BML) partition then you're probably out of luck. I'm not sure what would happen if you used somebody elses. It might work, it might not. Can only try If you're on an MTD ROM (4.0+), then you should revert to stock and things should be fixed, assuming the original partition is still intact...
xc-racer99 said:
Nope, a stock ROM won't have it - it's device specific and holds the IMEI. If you've corrupted the original (BML) partition then you're probably out of luck. I'm not sure what would happen if you used somebody elses. It might work, it might not. Can only try If you're on an MTD ROM (4.0+), then you should revert to stock and things should be fixed, assuming the original partition is still intact...
Click to expand...
Click to collapse
His TWRP backup is just the normal one that the device creates.. so it has the generic IMEI..
But I'm kind of lazy so instead of flashing it through TWRP.. i pushed it via adb and flashed with flash_image..
And it said some bad blocks error.. which means mtd efs partition needs to be flashed with bml_over_mtd... probably the reason why i lost my imei in the first place..
do you know any way of getting the bml parition from mtd? perhaps some offset where i can directly raw read it..
(°_o) said:
His TWRP backup is just the normal one that the device creates.. so it has the generic IMEI..
But I'm kind of lazy so instead of flashing it through TWRP.. i pushed it via adb and flashed with flash_image..
And it said some bad blocks error.. which means mtd efs partition needs to be flashed with bml_over_mtd... probably the reason why i lost my imei in the first place..
do you know any way of getting the bml parition from mtd? perhaps some offset where i can directly raw read it..
Click to expand...
Click to collapse
Well, according to the updater.sh it reads it from a mounted partition at https://github.com/xc-racer99/android_device_samsung_aries-common/blob/aosp-7.1/updater.sh#L198. The actual BML partition is at the offset specified in https://github.com/xc-racer99/andro...aosp-7.1/drivers/mtd/onenand/samsung_gsm.h#L9 - if you can dump it, mount it as vfat on your computer and then move the files over. Be very careful as the bootloaders are also around this offset...
xc-racer99 said:
Well, according to the updater.sh it reads it from a mounted partition at https://github.com/xc-racer99/android_device_samsung_aries-common/blob/aosp-7.1/updater.sh#L198. The actual BML partition is at the offset specified in https://github.com/xc-racer99/andro...aosp-7.1/drivers/mtd/onenand/samsung_gsm.h#L9 - if you can dump it, mount it as vfat on your computer and then move the files over. Be very careful as the bootloaders are also around this offset...
Click to expand...
Click to collapse
The mtd doesnt interface the whole NAND storage.. so i'm gonna have to rebuild the kernel exposing the original efs partition..
Let's see how it goes.
@xc-racer99
I dumped the 10mb parition but it wasnt mountable by any means..
Then I hex viewed it and it showed.. FSR_STL in beginning..
Which lead me to, https://github.com/Benjamin-Dobell/Samsung-Read-Only-FSR/blob/master/Inc/FSR_STL.h
So unless I check out the STL implementation or use one that is I guess I have to go back to stock :\
I cannot get any valid data from the dump.
I've attached the dump of it, if youre intrested.
Finally I've got everything installed and set up and logged in, etc, after reviving from brick. But then I just realized... This is a 128GB phone and things are saying I'm low on space (kinda)...
Anyone have any idea what can cause this or how to fix? The only thing in my mind that might be relevant is that the Data partition is in F2FS when before my huge issue I had it in EXT4? The OP level 2 support guy used a 7.1.1 factory image to revive my device. Can this matter?
Settings/Storage it's showing SYSTEM is taking up 89GB?!?!?!
Mixplorer says all of Internal Storage is only using 1.62GB or so
Desktop shows the phone as having 24.8GB storage in TOTAL with 6.9GB used
I don't know how to interpret these screenshots at all or what to do about it...
Edit: A full TWRP backup of every partition checked in the options is 7.75GB in total (as displayed in Windows), system image & all!
Edit2: Also in TWRP, there is no option for resizing the Data partition (which is f2fs, every other partition is EXT4) ...
If no one has any ideas... This is the only thing that seems like it makes sense to try doing to switch data from f2fs to ext4 and hopefully not have to clean flash? https://forums.oneplus.net/threads/...-without-losing-internal-storage-data.439999/
But if that doesn't work, and a regular clean flash doesn't work, that's what I'm most concerned about before even messing with it... JUST got it all set up perfectly after reviving from bricked state...
Switch to ext4, as its the most common Linux' file system. f2fs seems to be the culprit. And you'd better done a clean flash.
Erase userdata partition from fastboot and then format it (also via fastboot). Should work.
Don't forget to make a backup of you existing data (including internal).
As warned by many, F2FS is unstable and causes many errors. Try switching to Ext4, via ADB. This ought to give you the corrected partitions.
Confirmed
Just posting to confirm the above messages.
i converted my system to ff2fs and my system was taking up a little over 40Gb.
Reverting back to ext4 sorted it