Hey guys! This thread for such difficult cases when IMEI (CSPSA parittion) is lost and you don't have any backups for this partition.
It's a long story, how exactly I recently turned my phone into a tablet without RIL working but the long story short - both EFS and CSPSA parrtitions were messed up without any obvious ways to recover the latter, since I had no backup.
First of all, I should thank @ace2nutzer since he first found in JB firmware utility, that sets the IMEI to default one (15 zeros). The below is code taken from one of JB codinap firmware:
Code:
#TA Loader to write default IMEI
service ta_load /system/bin/ta_loader recovery
user root
group radio
oneshot
The legality of the use of this I'll leave out the scopes of this topic (and thus this is up to Samsung / ST-Ericcson vendors since this utility was developed by them) - remember that this guide is not about how to change IMEI, but only to recover your original one. Also remember that changing IMEI is illegal in many of countries.
Ok, let's go to the work, but remember, any even more serious damage that you can do to your phone is not my responsibility!
There are some of prerequisites that must be met in order to recover IMEI:
at least JB 4.1.2 or any newer firmware (2.3.6 is not tested) - device must be rooted
your phone is still able to boot the system (the described below is likely not to work in recovery mode)
baseband and signal level are showed in settings, but *#06# combination shows nothing and thus your phone can't be registered in the network
Android terminal emulator installed or adb
stock CSPSA partition from XXLK2 codina / codinap . The below linked this parittion for codina (I'm not sure if codinap users can use it as well, in such case you need to download XXLK2 2.3.6 firmware and extract this partition manually): http://www.xda.mister-freeze.eu/XDA-files/ChronoMonochrome/misc/cspsa/cspsa_stock.img
proper EFS partition (or backup) - I'll leave EFS recovery out of this topic, since I haven't found much variants of recovery of this parittion other than to ask someone to upload their EFS parition. Over the Internet, you can also find some EFS partitions for Ace 2, but I haven't tested them.
ta_loader binary - can be taken from any 4.1.2 (or higher) firmware (see the path above)
Below is how I finally managed to recover IMEI: (attention! everything listed below is only for those who have messed up CSPSA partition. If you're not sure that this is the case for you - don't follow steps written below.)
firstly, backup your CSPSA partition just in case (if you are sure that this is not usable at all and is not useful anymore for anything - you can skip this step):
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/cspsa_backup.img bs=512000
flash cspsa partition from XXLK2 stock:
Code:
dd if=/sdcard/cspsa_stock.img of=/dev/block/mmcblk0p6 bs=512000
and reboot the phone
backup /system/bin/ta_loader to some place (e.g. /sdcard or /ramdisk) and replace sequence of 15 zeroes to your original IMEI (can be found back under the battery) using sed:
Code:
sed -ie "s,000000000000000,<15_digits>," /ramdisk/ta_loader
sed -ie "s,<15_digits>0,<16_zeroes>," /ramdisk/ta_loader
I've used sed twice, because there are two occurences of 15 zeroes in ta_loader binary and we want to change only one of them (the rest occurence is not related to IMEI at all),
<15_digits> stands for your IMEI -> second sed command reverts an unwanted change.
Warning! Don't ever try to change IMEI to a non-original this way, it won't work!
now just type
Code:
/ramdisk/ta_loader recovery
, this will reboot your phone to recovery
reboot to system and voila! Original IMEI is there!
If this guide have saved your bacon then please consider donating to @ace2nutzer or me!
Permission denied
When I try to flash the cspsa_stock.img using terminal emulator, it say permission denied.. please help me..
Try
Code:
su
or:
Code:
sudo -i
Confused the 3rd step
You said to replace 15 zeroes to my imei, then you said that <15_digits> stand for my imei, so do i have to change the <15_digits> with my imei? If yes, which one? the first sed or the second? And what should I do for the <16_digits> ? Thanks
Primen2000 said:
When I try to flash the cspsa_stock.img using terminal emulator, it say permission denied.. please help me..
Click to expand...
Click to collapse
Since you're unfamiliar with image flashing, are you sure you're in the right topic? This one is for these unlike cases where CSPSA partition is broken, you might want to check first if this is not the case before you continue.
Primen2000 said:
You said to replace 15 zeroes to my imei, then you said that <15_digits> stand for my imei, so do i have to change the <15_digits> with my imei? If yes, which one? the first sed or the second? And what should I do for the <16_digits> ? Thanks
Click to expand...
Click to collapse
If yes, which one?
Click to expand...
Click to collapse
Both, consider both commands like one.
And what should I do for the <16_digits> ?
Click to expand...
Click to collapse
there is no <16_digits> mentioned in OP, <16_zeros> stands for the sequence of 16 zeroes.
Worked 100%
Oh Man... I've already give up to this old phone because no sim card detected due to IMEI issue for 1 week. And after buy new smartphone last night (Xiaomi Note 4), Now your tutorial worked. I feel sad and happy.. Thanks a lot you guys..
Permission denied
I have entered the following in an adb shell without any error message
cp /system/bin/ta_loader /sdcard
sed -ie "s,000000000000000,my imei," /sdcard/ta_loader
sed -ie "s,my imei+0,0000000000000000," /sdcard/ta_loader
but when I then try
/sdcard/ta_loader recovery
I get a "permission denied". Shell says I am root and the ta_loader's permissions are -rwxrwx---.
Any ideas? (sorry I am not quite familiar with android...)
andi_ypsilon said:
I have entered the following in an adb shell without any error message
cp /system/bin/ta_loader /sdcard
sed -ie "s,000000000000000,my imei," /sdcard/ta_loader
sed -ie "s,my imei+0,0000000000000000," /sdcard/ta_loader
but when I then try
/sdcard/ta_loader recovery
I get a "permission denied". Shell says I am root and the ta_loader's permissions are -rwxrwx---.
Any ideas? (sorry I am not quite familiar with android...)
Click to expand...
Click to collapse
That command just for rebooting to recovery. You can do it yourself.
bien2004official said:
That command just for rebooting to recovery. You can do it yourself.
Click to expand...
Click to collapse
Obviously, it's not just rebooting to recovery but also writes IMEI to a stock CSPSA partition. If CSPSA partition is already recovered (or not broken) then it will just reboot to recovery.
andi_ypsilon said:
but when I then try
/sdcard/ta_loader recovery
I get a "permission denied". Shell says I am root and the ta_loader's permissions are -rwxrwx---.
Any ideas? (sorry I am not quite familiar with android...)
Click to expand...
Click to collapse
Binaries cannot be run from sdcard partition. Copy binary to e.g. /data/local and retry.
ChronoMonochrome said:
Obviously, it's not just rebooting to recovery but also writes IMEI to a stock CSPSA partition. If CSPSA partition is already recovered (or not broken) then it will just reboot to recovery.
Binaries cannot be run from sdcard partition. Copy binary to e.g. /data/local and retry.
Click to expand...
Click to collapse
Thanks ChronoMonochrome, this has worked. Android now shows the correct IMEI.
But SIM card is still not detected even though its working in another phone (and it worked in the ACE2 before installing CustomROM). In "SIM status" all the points are "not available". Can you give me some ideas how to tackle this?
BTW, ta_loader showed some errors (don't know if relevant)
https://imgur.com/a/HsJQU6P
andi_ypsilon said:
Thanks ChronoMonochrome, this has worked. Android now shows the correct IMEI.
But SIM card is still not detected even though its working in another phone (and it worked in the ACE2 before installing CustomROM). In "SIM status" all the points are "not available". Can you give me some ideas how to tackle this?
BTW, ta_loader showed some errors (don't know if relevant)
https://imgur.com/a/HsJQU6P
Click to expand...
Click to collapse
Have you followed all the steps of this guide?
ChronoMonochrome said:
Have you followed all the steps of this guide?
Click to expand...
Click to collapse
What I did using adb:
1) Took cspsa_stock.img from the download link, copied it to sdcard, and typed dd if=/sdcard/cspsa_stock.img of=/dev/block/mmcblk0p6 bs=512000
2) sed -ie "s,000000000000000,123456789....," /local/data/ta_loader
sed -ie "s,1234567890...0,0000000000000000," /local/data/ta_loader
This gave me a modified ta_loader (pulled it to computer and found my IMEI within) and a second file called "ta_loadere". (Don't know why. Same size, contains my IMEI twice)
3) /local/data/ta_loader recovery
4) Select reboot in recovery
andi_ypsilon said:
What I did using adb:
1) Took cspsa_stock.img from the download link, copied it to sdcard, and typed dd if=/sdcard/cspsa_stock.img of=/dev/block/mmcblk0p6 bs=512000
2) sed -ie "s,000000000000000,123456789....," /local/data/ta_loader
sed -ie "s,1234567890...0,0000000000000000," /local/data/ta_loader
This gave me a modified ta_loader (pulled it to computer and found my IMEI within) and a second file called "ta_loadere". (Don't know why. Same size, contains my IMEI twice)
3) /local/data/ta_loader recovery
4) Select reboot in recovery
Click to expand...
Click to collapse
Hmm, then it might depend on what exactly happened to phone. On mine EFS and CSPSA partitions both were broken, but that was not problem (an EFS partition doesn't contains anything irrecoverable, a backup image can be found here). Flashing a full stock image might help as well (I had MF1 4.1.2 stock ROM installed at the moment I broke CSPSA & EFS partitions).
ChronoMonochrome said:
Hmm, then it might depend on what exactly happened to phone. On mine EFS and CSPSA partitions both were broken, but that was not problem (an EFS partition doesn't contains anything irrecoverable, a backup image can be found here). Flashing a full stock image might help as well (I had MF1 4.1.2 stock ROM installed at the moment I broke CSPSA & EFS partitions).
Click to expand...
Click to collapse
SOLUTION: Flashing the phone with Odin 3.2.1.4 and i8160XXNB1_OXXNB4_Android_4.1.2_service.zip from https://service-gsm.net/Samsung/I8160/i8160XXNB1_OXXNB4_Android_4.1.2_service.zip/ restored SIM card detection.
Related
I saw a thread on the international S2 forum regarding the importance of backing up the /efs folder on the phone so you don't lose the phones imei. I was wondering if this is still a necessity on our phone as well? And if so is there a different process to do it than what they used? They used terminal commands to back it up using terminal Emulator or ADB.
This is the thread:
http://forum.xda-developers.com/showthread.php?t=1068193
Its very important..ask me..i lost my IMEI and dint have a back up of the efs folder..had to go to the store and get a new phone under warranty.
Please make a backup of it.
After 2 months, someone just had EFS corruption last week - so yes, now I think it's a good idea to back it up.
IMO it would be a good idea to image the partition too...
Entropy512 said:
IMO it would be a good idea to image the partition too...
Click to expand...
Click to collapse
Can you verify the partition? Is 0p3 the right one, or is it 0p1? I coundn't find a definitive answer by searching.
For some reason I thought it was p3, but I was wrong. It's p1:
Code:
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered)
To back it up, get ADB working, and run the following using ADB while the phone is in CWM recovery and /sdcard is mounted (It often is not when you first enter CWM, mount it in the Mounts and Storage menu if it is not) (If you do this when the phone is running, you may back it up as it is getting written to, which could result in a bogus backup)
Code:
adb shell dd if=/dev/block/mmcblk0p1 of=/sdcard/efs_backup.img
Thanks for the verification entropy!
Sent from my SAMSUNG-SGH-I777 using XDA App
Entropy512 said:
Code:
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered)
Click to expand...
Click to collapse
I don't know much about linux commands. Is this how you verified the partition?
Also, am I correct in assuming that if the partition is backed up, it would not be necessary to back up the efs directory using a file explorer? Or is there a reason to have both?
You can also run the command from entropy in terminal emulator on your phone. Do su first to get root and enter the dd command to do your backup.
Sent from my SGH-I777
creepyncrawly said:
I don't know much about linux commands. Is this how you verified the partition?
Also, am I correct in assuming that if the partition is backed up, it would not be necessary to back up the efs directory using a file explorer? Or is there a reason to have both?
Click to expand...
Click to collapse
I verified it by executing the following command and looking at the output:
Code:
mount
It may be easier to restore a folder backup - not sure. A partition backup is the best way to guarantee you got EVERYTHING in that partition, byte-for-byte.
That's crazy. Cause I don't understand how you learn stuff like that but thanks(aka I'm gonna go do this since I mess with my phone alot.) I followed amk28's troubles. What's the difference between efs backup pro and this mehod? They both backup images
Entropy512 said:
For some reason I thought it was p3, but I was wrong. It's p1:
Code:
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered)
To back it up, get ADB working, and run the following using ADB while the phone is in CWM recovery and /sdcard is mounted (It often is not when you first enter CWM, mount it in the Mounts and Storage menu if it is not) (If you do this when the phone is running, you may back it up as it is getting written to, which could result in a bogus backup)
Code:
adb shell dd if=/dev/block/mmcblk0p1 of=/sdcard/efs_backup.img
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I777 using XDA App
My phone lost his Imei after restoring to factory settings. I have root, and I was trying to do it because I have root so unrooted&wipe but after wipe my imei lost again, (once happened again, that time i sent it to service and came in good condition) but I found the EFS backup ing and editing with a hex editor will set things to order but even I have root and giving permissions to any program wont see SU.
Galaxy Toolbox prog. can't find any EFS and I could not be able to edit it. There is no Galaxytoolbox folder (or YGSxyz folder) in sdcard. And if I look with root explorers, there is no things in efs folder.
I mean to use this method but I do not have anything in my efs folder.
Any Ideas?
SweetyVolty said:
My phone lost his Imei after restoring to factory settings. I have root, and I was trying to do it because I have root so unrooted&wipe but after wipe my imei lost again, (once happened again, that time i sent it to service and came in good condition) but I found the EFS backup ing and editing with a hex editor will set things to order but even I have root and giving permissions to any program wont see SU.
Galaxy Toolbox prog. can't find any EFS and I could not be able to edit it. There is no Galaxytoolbox folder (or YGSxyz folder) in sdcard. And if I look with root explorers, there is no things in efs folder.
I mean to use this method but I do not have anything in my efs folder.
Any Ideas?
Click to expand...
Click to collapse
try to do this tutorial http://forum.xda-developers.com/showthread.php?t=1968360 there is a
guide with adb but you have to root youe device then for me it?s normal that root explorer doesn't see
efs partition for security i think and so you see that is empty...
flash stock kernel..u will get your imei back..works for me every time
Sent from my GT-S5830i using xda app-developers app
angel.sea said:
try to do this tutorial http://forum.xda-developers.com/showthread.php?t=1968360 there is a
guide with adb but you have to root youe device then for me it?s normal that root explorer doesn't see
efs partition for security i think and so you see that is empty...
Click to expand...
Click to collapse
My device is rooted and its giving permission to applications but applications can't read the given SU permission. Somehow weird situation, oh by the way my phone could not connect to wifi on by own, i have to enter values of my wifis parimeters of ip gateway etc. and I could not update SU binary.
srt99 I'm not a professional android user, not linux anyway, so I dont want to interact with changing roms because there is no Turkish rom in sammobile or any like (I do not use Turkish language on my phone, but still my guarantine is continue and will send if I could not make it. )
AW: Can't Backup'ing EFS Partition
SweetyVolty said:
I'm not a professional android user, not linux anyway, so I dont want to interact with changing roms because there is no Turkish rom in sammobile or any like (I do not use Turkish language on my phone, but still my guarantine is continue and will send if I could not make it. )
Click to expand...
Click to collapse
You don't have to be a professional, like everybody can do this. Just flash this through cwm and you have stock kernel again.
¿U mad bro¿
SweetyVolty said:
My phone lost his Imei after restoring to factory settings. I have root, and I was trying to do it because I have root so unrooted&wipe but after wipe my imei lost again, (once happened again, that time i sent it to service and came in good condition) but I found the EFS backup ing and editing with a hex editor will set things to order but even I have root and giving permissions to any program wont see SU.
Galaxy Toolbox prog. can't find any EFS and I could not be able to edit it. There is no Galaxytoolbox folder (or YGSxyz folder) in sdcard. And if I look with root explorers, there is no things in efs folder.
I mean to use this method but I do not have anything in my efs folder.
Any Ideas?
Click to expand...
Click to collapse
try this new script http://forum.xda-developers.com/showthread.php?t=2177118..bml15 is the partition that contain the imei
or write this code on terminal emulator
su press enter
busybox dd if=/dev/bml15 of=/sdcard/bml15.img press enter
a line at a time
and see the sd card try with hexeditor like the guide http://forum.xda-developers.com/show....php?t=1968360
Thanks for posting with this much helpful contains. But my device can not gain root acces even have the app superuser in main menu. I couldnt figure out why, while I'm trying to update binary it couldn't gain root access even given permission to superuser inself. Tried to install SuperSU from chainfire but it does not install it. even with ccw mod installer.
SweetyVolty said:
Thanks for posting with this much helpful contains. But my device can not gain root acces even have the app superuser in main menu. I couldnt figure out why, while I'm trying to update binary it couldn't gain root access even given permission to superuser inself. Tried to install SuperSU from chainfire but it does not install it. even with ccw mod installer.
Click to expand...
Click to collapse
you tried to do the Unroot with cwm and redo the root process?
if you type in terminal emulator su on what you said?
angel.sea said:
you tried to do the Unroot with cwm and redo the root process?
if you type in terminal emulator su on what you said?
Click to expand...
Click to collapse
Uhm i do with normal recovery mode, not with cwm. If I write "su" "$" changes to "#" but if I write "whoami" returns with this line "whoami: not found"
SweetyVolty said:
Uhm i do with normal recovery mode, not with cwm. If I write "su" "$" changes to "#" but if I write "whoami" returns with this line "whoami: not found"
Click to expand...
Click to collapse
what is whoami?
so if with su changes with # you are in root.....so try the command that wrote before for bml15
and to upgrade su bin try super user fix by chainsdd in playstore if forse fix then you have to remove the battery
angel.sea said:
what is whoami?
so if with su changes with # you are in root.....so try the command that wrote before for bml15
and to upgrade su bin try super user fix by chainsdd in playstore if forse fix then you have to remove the battery
Click to expand...
Click to collapse
whoami - who am i
However, this is used on Linux to check the username of the User
It is useless for s5830i
If your phone gets #
Then it's rooted
Try my Tool In Development section for backing up EFS partition
angel.sea said:
what is whoami?
so if with su changes with # you are in root.....so try the command that wrote before for bml15
and to upgrade su bin try super user fix by chainsdd in playstore if forse fix then you have to remove the battery
Click to expand...
Click to collapse
Yes i have the bml15 and when open it with hex editor at line 0x80000 I can see my imei number, what should I do now?
dd if=/sdcard/bml15.img of=/dev/block/bml15 line prints "dd: not found" how ever, the opposite command token the bml15.img to sd card.
SweetyVolty said:
Yes i have the bml15 and when open it with hex editor at line 0x80000 I can see my imei number, what should I do now?
dd if=/sdcard/bml15.img of=/dev/block/bml15 line prints "dd: not found" how ever, the opposite command token the bml15.img to sd card.
Click to expand...
Click to collapse
if you can see your emei that's a problem of incompatibility between your firmware....but you had installed cronemode's scripts?
try to reflash stock kernel and will see that your emei wiill come back....LINK [STOCK KERNEL] ----- http://www.mediafire.com/?8amfqkqq28v1h9f
stock kernel modules ---- http://www.mediafire.com/?7tckgiclaq80aoc
flash with cwm that take from this thread http://forum.xda-developers.com/showthread.php?t=1551156
angel.sea said:
if you can see your emei that's a problem of incompatibility between your firmware....but you had installed cronemode's scripts
Click to expand...
Click to collapse
Hm.. My firmware is in its orginal state, I only rooted my phone and OS started to flikering so I decided to wipe data, delvik clean cache wipe etc. after that my imei is became unknown...
Edit: I didnt install any scripts, or cronemode?
SweetyVolty said:
Hm.. My firmware is in its orginal state, I only rooted my phone and OS started to flikering so I decided to wipe data, delvik clean cache wipe etc. after that my imei is became unknown...
Edit: I didnt install any scripts, or cronemode?
Click to expand...
Click to collapse
try to use the file of this thread http://forum.xda-developers.com/show....php?t=1551156 to unroot and root then reflash stock kernel that there were a mistake in os
your rom will be the same....try and tell me if work fine...for me work fine
no you have to use a little apk bmlunlock and then to use the command to mount the partition or viceversa and then
busybox dd if=/sdcard/bml15.img of=/dev/block/bml15 but i don t remember if you have to use chmod command also
My dear sir, I have complated my mission with odin and lastest sammobile rom. Thank you all for your greatest effords and helps. :angel:
SweetyVolty said:
My dear sir, I have complated my mission with odin and lastest sammobile rom. Thank you all for your greatest effords and helps. :angel:
Click to expand...
Click to collapse
iM happy to you....
I have a weird problem
I tried restoring IMEI with every possible method
But it didn't get restored
Even flashed stock firmware
Didn't help
Though after some retries, I was able to restore it back but then too, I disappears after some reboots
iamareebjamal said:
I have a weird problem
I tried restoring IMEI with every possible method
But it didn't get restored
Even flashed stock firmware
Didn't help
Though after some retries, I was able to restore it back but then too, I disappears after some reboots
Click to expand...
Click to collapse
Using any cronmod scripts?
Sent from my GT-S5830i using xda premium
uchihachi said:
Using any cronmod scripts?
Sent from my GT-S5830i using xda premium
Click to expand...
Click to collapse
Yes
But I was using them for last 5 months without a problem
I'm just writting this because i've recently had this problem. I managed to sort it out by my own but didn't really find it written anywhere, just bits and pieces scavenged from so many pages that might point to a solution (granted, part of my problem was also finding what was really my problem since the phone stopped working so fast i didn't really had the time to get what happened)
I was trying out swap for my S3, i had created a swap partition in my external card and then followed a guide here from xda to use an app called swapper2 (from market) to enable swap. I must have done something wrong because what it did was format my /efs partition instead as if it was a swap partition. Phone stopped working on the spot, obviously, and wouldn't past samsung's bootscreen.
Also, keep in mind while this worked for me there might be other ways of doing this which may be simpler. This is just what i figured for a solution.
When this helps:
- you accidentally formated your /efs partition
- you have a backup from your /efs partition, files copied with root explorer but not an image you can just flash back to the partition.
- your phone boots to download and to recovery but not to main system (which every tutorial i found seemed to assume to be able to do, i just figured their /efs was not as screwed as mine was)
- your recovery won't mount the /efs partition because it expects it to be ext4 but it's formated to something else and it showing the message:
"e: failed to mount /efs (Invalid argument)"
What doesn't work:
- any kind of standard solution like reflashing a stock rom with odin, with or without .pit file, clear EFS, whatever. It will flash, just won't solve since, apparently, nothing touches the /efs partition because it's so sensible. Even custom recoveries do mount it and apparently format and replace every single other partition but the /efs, which is why i had to do it manually.
Solution:
- simply format the /efs partition back to ext4 and copy your backup files there
What's needed:
- phone drivers installed on the computer. If you had kies installed, this should be covered already. Think you can't have it running while doing this though. Also, for what's worth, i've done this with windows 8 x64.
- updated android sdk tool, mainly adb. If adb is saying device not connected or not found, you may be using an outdated adb.exe (i was). I used adb.exe that came with this software here:
http://forum.xda-developers.com/showthread.php?t=1308546
- root. If your rom isn't rooted you can always flash CF-root from odin in download mode.
http://forum.xda-developers.com/showthread.php?t=1695238
- busybox, am not really sure if i actually got to need this, think so for the formating tool. Can't hurt to have more options though. This is how to install:
http://www.omappedia.com/wiki/Android_Installing_Busybox_Command_Line_Tools
- custom recovery that allows root through adb, i used Philz which is pretty awesome
http://forum.xda-developers.com/showthread.php?t=2002953
- backup files from your /efs. I had mine unzipped and copied to my externalsd while in windows. They were in an efs folder in the sd card. You can push this through adb to the phone later, but i found this way simpler.
How to:
- get into recovery (vol up+home+power button) and plug your phone to the computer. You'll hear an usb connected sound from windows after a bit.
- in recovery, navigate to Mounts and try the "mount /efs". It'll fail. Now, navigate to advanced and "view log". You'll see below that the phone tried to mount a partition and failed, in my case, it had unsucessfully tried to mount /dev/block/mmcblk0p3 which is the partition /efs uses. Take note of this partition name.
- On windows, open a command line (type cmd on you start menu), navigate to where you have adb.exe and type:
adb shell
If all went well, command prompt has changed. You can now issue commands directly to your phone from terminal.
- type "su" to get root permissions. Your command line should change to something like [email protected] Before i had this working i needed to use "Fix permissions". It's an option in the recovery menus on the phone.
- this step is optional but i did it anyway. I created an image of the partition i was going to mess with. If anything went wrong i could always flash it back even if it was broken. By the way, this is what i should have done in the first place instead of just copying /efs files. Would have made the process so much simpler... also, do this if you ever get the phone back working again. Type:
dd if=/dev/block/mmcblk0p3 of=/externalsd/efs.img
The /externalsd/efs.img is just a place you can save stuff to, like your external sd card. You can check what's your mounting point for the card with the command "mount" and look for something relevant like "externalsd".
Also, you may want to copy that efs.img to somewhere else from your phone (like your computer) for safekeeping. Literally remove card from phone, put in computer and copy files there. Notice you may need to reboot phone to recovery if you remove your card so it detects and mounts your card again. Sure, you can also do that from the command line, but it's just easier to reboot the phone.
- Now, we'll format the partition to something your phone can mount (ext4) and is expecting. Be careful, by doing this, you're actually erasing what's left of your partition and replacing by something clean. Type:
mk2fs /dev/block/mmcblk0p3
If all went well, you should see some kind of small report about what was just done.
- To mount this we'll need a mounting point. Type:
mkdir /efs
this will create an /efs folder in root, if it doesn't exist already, and to mount, type:
mount -t ext4 /dev/block/mmcblk0p3 /efs
- if all went well, you now have access to the /efs folder and can copy you files back:
cp -r /externalsd/efs/* /efs
where externalsd was my external sd card mounted on my phone.
- Check if your /efs folder has it's contents properly
ls /efs
I had to reboot the phone to recovery once more at this point and use the "fix permissions" option again.
After this, my phone booted up normally again.
I'm getting Segmentation fault, I guess there's some kinda hardware error on my phone. Gonna take it to Sammy's tomorrow.
Code:
mke2fs -F /dev/block/mmcblk0p11
Segmentation fault
sh-4.2#
Hi thnx for your Guide. I have the EFS problem, after installin 4 diferent rom in 2 hours my imei and baseband lost.( dont now why) i dont have a backup. I was thinking if it take the EFS from another S3 does it work?
Will this work with a Galaxy S4? I545
Enea307 said:
Hi thnx for your Guide. I have the EFS problem, after installin 4 diferent rom in 2 hours my imei and baseband lost.( dont now why) i dont have a backup. I was thinking if it take the EFS from another S3 does it work?
Click to expand...
Click to collapse
No. Read General > Sticky roll-up thread > "IMEI / EFS - Know this stuff"
is normal this output? (i'm meaning the tar.gz unfinding file)
Code:
*****************************************
* BACKUP EFS *
*****************************************
WARNING: Do you wish to Continue? (This will make EFS BACKUP) [Y,N]?Y
--- STARTING ----
--- WAITING FOR DEVICE
--- Backup efs image ---
761 KB/s (9357 bytes in 0.012s)
7 KB/s (39 bytes in 0.005s)
SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_
Creating filesystem with parameters:
Size: 20971520
Block size: 4096
Blocks per group: 32768
Inodes per group: 1280
Inode size: 256
Journal blocks: 1024
Label:
FLEX_BG size: 0
Blocks: 5120
Block groups: 1
Reserved block group size: 0
Created filesystem with 59/1280 inodes and 2432/5120 blocks
40960+0 records in
40960+0 records out
20971520 bytes transferred in 7.271 secs (2884269 bytes/sec)
unknown option -- ZBusyBox v1.19.4-cm9 bionic (2012-02-05 18:40 +0100) multi-cal
l binary.
Usage: tar -[cxtzjahmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
z (De)compress using gzip
j (De)compress using bzip2
a (De)compress using lzma
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
2684 KB/s (9962352 bytes in 3.623s)
2805 KB/s (20971520 bytes in 7.299s)
remote object '/sdcard/SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.gz' does n
ot exist
7-Zip (A) 4.65 Copyright (c) 1999-2009 Igor Pavlov 2009-02-03
Scanning
SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.gz: WARNING: Impossibile trovare
il file specificato. [COLOR=Red](impossible to find the specify file)[/COLOR]
Creating archive SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.zip
Compressing getprop.txt
Compressing SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.raw.img
Compressing SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.md5
WARNINGS for files:
SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.gz : Impossibile trovare il file
specificato.[COLOR=Red] (impossible to find the specify file)[/COLOR]
----------------
WARNING: Cannot find 1 file
-
-
Finished. Output file is SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS BACKUP
Premere un tasto per continuare . . .
well in the zip there are only the txt + md5 + .raw.img
Thanks for this great tutorial. It was my final step to recover my efs partition, without any backup. I copied the efs folder from another device and modified the files according my devices info (bluetooth mac, serial etc). Worked great on my SGS4
By the way I had the same error:
Code:
mke2fs /dev/block/mmcblk0p10
Segmentation fault
You get this error if you run adb shell when you booted to your ROM.
You need to run adb shell in recovery mode
Great tutorial but i hope you can help me, I can't seem to properly find the SDcard. When I type cp -r /externalsd/efs/* /efs
it comes back with cp: can't stat '/sdcard/efs*' : No such file or directory
I cleared my whole sdcard card except for efs directory. I also tried sdcard instead of externalsd but same thing.
I am getting stuck trying to fix this as I have a boot loop or corrupt /efs or something. I have tried to get my phone working by installing my ROM ( Omega v58 ) and also by trying to flash the latest stock 4.3 through Odin v3.09. I havent tried total stock 4.0.3 yet. No matter what I have done though I can't get past the boot logo ( or the walking Omega droid ). My phone just sits there and hangs
I have followed your steps and I have Philz ( 6.07.9.19 ) installed ( but not busybox unless it is sat there somehow from the Omega install ) but when i try to get adb shell running nothing happens or works..as you can see
What am i doing wrong? OR is my phone totally borked?
hi..
Blackwatch said:
I am getting stuck trying to fix this as I have a boot loop or corrupt /efs or something. I have tried to get my phone working by installing my ROM ( Omega v58 ) and also by trying to flash the latest stock 4.3 through Odin v3.09. I havent tried total stock 4.0.3 yet. No matter what I have done though I can't get past the boot logo ( or the walking Omega droid ). My phone just sits there and hangs
I have followed your steps and I have Philz ( 6.07.9.19 ) installed ( but not busybox unless it is sat there somehow from the Omega install ) but when i try to get adb shell running nothing happens or works..as you can see
What am i doing wrong? OR is my phone totally borked?
Click to expand...
Click to collapse
I have successfully fix my efs partition follwing this thread.
you are receiving such message in cmd. I faced it too.
Sol: Use Philoz Recovery 5.0.
Fix permissions.
there you are.. done..
Philz 6.0 do not have an option for "fix permission".
hope it helps..
I wrote a script that attempts to recover your nv_data.bin from a corrupted EFS partition for the i9300. Thus if you don't have a backup and your EFS is corrupt, try the script. The script is still in Alpha phase and may not work for other devices. Feedback would be much appreciated.
You can find the script at: https://github.com/chriscz/efs_recover
I dont have /efs backed up
Hi ,
If i dont have /efs backed up , can I copy any other mobile (same model) efs data to my mobile and try?
Thanks and Regards
Vamshi Pulumati
vamshipulumati said:
Hi ,
If i dont have /efs backed up , can I copy any other mobile (same model) efs data to my mobile and try?
Thanks and Regards
Vamshi Pulumati
Click to expand...
Click to collapse
No, it won't work and trying to clone another imei is illegal.
boomboomer said:
No, it won't work and trying to clone another imei is illegal.
Click to expand...
Click to collapse
How to register for a new IMEI ? Is it possible?? Could you please help me with any site or link?? I don't want to replace motherboard..
Any help are highly appreciated.
No, it isn't possible and discussion about changing imei is banned on xda.
Take your phone to a service centre and pay then to recode it for you, make sure it works on 4.3 before you pay.
boomboomer said:
No, it isn't possible and discussion about changing imei is banned on xda.
Take your phone to a service centre and pay then to recode it for you, make sure it works on 4.3 before you pay.
Click to expand...
Click to collapse
Hey I would like to tell you that a miracle happened for my S3. Yesterday i tried to do same as per in this guide. After taking backup of broken efs backup i tried to clear the efs folder with this command "mk2fs /dev/block/mmcblk0p3"
After that i just flashed 4.4.4 based stock ROM and somehow phone booted up perfectly. No network issues. Bluetooth wifi sim card everything works. IMEI & Serial No is there. But when i'm checking network unlock status it is showing as everything locked. But still I can use everything... I'm amazed.!!!!
Do you have any idea how this happened??
@boomboomer
Same problem with a Samsung gt-i9070 - Galaxy S Advance
Hi!
My i9070 has the same problem, but when i run the command: "mke2fs /dev/block/mmcblk0p3" shows the "Segmentation fault" error message.
Some one can help?
Thanks.
Bro U stated to format but How to format /efs partition
/efs not backed up
boomboomer said:
No, it won't work and trying to clone another imei is illegal.
Click to expand...
Click to collapse
I Dont have efs backed up and I also have formatted efs partition from adb shell and using that Dev type commands now i am in factory mode and my network is not working please give me any solution.
kaynpayn said:
I'm just writting this because i've recently had this problem. I managed to sort it out by my own but didn't really find it written anywhere, just bits and pieces scavenged from so many pages that might point to a solution (granted, part of my problem was also finding what was really my problem since the phone stopped working so fast i didn't really had the time to get what happened)
I was trying out swap for my S3, i had created a swap partition in my external card and then followed a guide here from xda to use an app called swapper2 (from market) to enable swap. I must have done something wrong because what it did was format my /efs partition instead as if it was a swap partition. Phone stopped working on the spot, obviously, and wouldn't past samsung's bootscreen.
Also, keep in mind while this worked for me there might be other ways of doing this which may be simpler. This is just what i figured for a solution.
When this helps:
- you accidentally formated your /efs partition
- you have a backup from your /efs partition, files copied with root explorer but not an image you can just flash back to the partition.
- your phone boots to download and to recovery but not to main system (which every tutorial i found seemed to assume to be able to do, i just figured their /efs was not as screwed as mine was)
- your recovery won't mount the /efs partition because it expects it to be ext4 but it's formated to something else and it showing the message:
"e: failed to mount /efs (Invalid argument)"
What doesn't work:
- any kind of standard solution like reflashing a stock rom with odin, with or without .pit file, clear EFS, whatever. It will flash, just won't solve since, apparently, nothing touches the /efs partition because it's so sensible. Even custom recoveries do mount it and apparently format and replace every single other partition but the /efs, which is why i had to do it manually.
Solution:
- simply format the /efs partition back to ext4 and copy your backup files there
What's needed:
- phone drivers installed on the computer. If you had kies installed, this should be covered already. Think you can't have it running while doing this though. Also, for what's worth, i've done this with windows 8 x64.
- updated android sdk tool, mainly adb. If adb is saying device not connected or not found, you may be using an outdated adb.exe (i was). I used adb.exe that came with this software here:
http://forum.xda-developers.com/showthread.php?t=1308546
- root. If your rom isn't rooted you can always flash CF-root from odin in download mode.
http://forum.xda-developers.com/showthread.php?t=1695238
- busybox, am not really sure if i actually got to need this, think so for the formating tool. Can't hurt to have more options though. This is how to install:
http://www.omappedia.com/wiki/Android_Installing_Busybox_Command_Line_Tools
- custom recovery that allows root through adb, i used Philz which is pretty awesome
http://forum.xda-developers.com/showthread.php?t=2002953
- backup files from your /efs. I had mine unzipped and copied to my externalsd while in windows. They were in an efs folder in the sd card. You can push this through adb to the phone later, but i found this way simpler.
How to:
- get into recovery (vol up+home+power button) and plug your phone to the computer. You'll hear an usb connected sound from windows after a bit.
- in recovery, navigate to Mounts and try the "mount /efs". It'll fail. Now, navigate to advanced and "view log". You'll see below that the phone tried to mount a partition and failed, in my case, it had unsucessfully tried to mount /dev/block/mmcblk0p3 which is the partition /efs uses. Take note of this partition name.
- On windows, open a command line (type cmd on you start menu), navigate to where you have adb.exe and type:
adb shell
If all went well, command prompt has changed. You can now issue commands directly to your phone from terminal.
- type "su" to get root permissions. Your command line should change to something like [email protected] Before i had this working i needed to use "Fix permissions". It's an option in the recovery menus on the phone.
- this step is optional but i did it anyway. I created an image of the partition i was going to mess with. If anything went wrong i could always flash it back even if it was broken. By the way, this is what i should have done in the first place instead of just copying /efs files. Would have made the process so much simpler... also, do this if you ever get the phone back working again. Type:
dd if=/dev/block/mmcblk0p3 of=/externalsd/efs.img
The /externalsd/efs.img is just a place you can save stuff to, like your external sd card. You can check what's your mounting point for the card with the command "mount" and look for something relevant like "externalsd".
Also, you may want to copy that efs.img to somewhere else from your phone (like your computer) for safekeeping. Literally remove card from phone, put in computer and copy files there. Notice you may need to reboot phone to recovery if you remove your card so it detects and mounts your card again. Sure, you can also do that from the command line, but it's just easier to reboot the phone.
- Now, we'll format the partition to something your phone can mount (ext4) and is expecting. Be careful, by doing this, you're actually erasing what's left of your partition and replacing by something clean. Type:
mk2fs /dev/block/mmcblk0p3
If all went well, you should see some kind of small report about what was just done.
- To mount this we'll need a mounting point. Type:
mkdir /efs
this will create an /efs folder in root, if it doesn't exist already, and to mount, type:
mount -t ext4 /dev/block/mmcblk0p3 /efs
- if all went well, you now have access to the /efs folder and can copy you files back:
cp -r /externalsd/efs/* /efs
where externalsd was my external sd card mounted on my phone.
- Check if your /efs folder has it's contents properly
ls /efs
I had to reboot the phone to recovery once more at this point and use the "fix permissions" option again.
After this, my phone booted up normally again.
Click to expand...
Click to collapse
I have restored my s6 edge by following this method. The EFS partition name is "sda3" for s6 edge if anyone want to restore s6 edge. There is typo in command "mk2fs /dev/block/mmcblk0p3" it should be mke2fs i think.
After restoring EFS my phone recovered from boot loop. But the imei is still invalid. Do you know any method to repair imei for s6 edge?. Thank You
---------- Post added at 02:18 PM ---------- Previous post was at 02:14 PM ----------
Blackwatch said:
I am getting stuck trying to fix this as I have a boot loop or corrupt /efs or something. I have tried to get my phone working by installing my ROM ( Omega v58 ) and also by trying to flash the latest stock 4.3 through Odin v3.09. I havent tried total stock 4.0.3 yet. No matter what I have done though I can't get past the boot logo ( or the walking Omega droid ). My phone just sits there and hangs
I have followed your steps and I have Philz ( 6.07.9.19 ) installed ( but not busybox unless it is sat there somehow from the Omega install ) but when i try to get adb shell running nothing happens or works..as you can see
What am i doing wrong? OR is my phone totally borked?
Click to expand...
Click to collapse
You don't have to run "su" command. "#" shows you already have root access.
Dear Friends,
Need help please. I have installed another custom rom that was not meant for I9300 and now the EFS is corrupted. I tried installing orignal rom using ODIN but geting boot loop and the phone is not booting. On going into recovery i can see an error efs/ corupted or something like that. I have the backup of my EFS folder in tar.gz format however dont know how to install the same and recover my phone as not able to boot to android.
Please help me if someone can work it out. My phone has just 3 days of warranty left and it does not shows rooted anywhere except the count of installation is about 32 and rom says official and kernel says custom.
Please if someone can help me restore my phone back in working condition i shall always remain thankfull.
Regards,
Mush
mush2004 said:
Dear Friends,
Need help please. I have installed another custom rom that was not meant for I9300 and now the EFS is corrupted. I tried installing orignal rom using ODIN but geting boot loop and the phone is not booting. On going into recovery i can see an error efs/ corupted or something like that. I have the backup of my EFS folder in tar.gz format however dont know how to install the same and recover my phone as not able to boot to android.
Please help me if someone can work it out. My phone has just 3 days of warranty left and it does not shows rooted anywhere except the count of installation is about 32 and rom says official and kernel says custom.
Please if someone can help me restore my phone back in working condition i shall always remain thankfull.
Regards,
Mush
Click to expand...
Click to collapse
It is essential that you have a backup of the EFS partition and a way to place it back - the first two ways that I would think about are:
a) use a good recovery - like Philz recovery, that has commands to restore EFS
b) if the format of the backup is not exactly right you might be able to boot in recovery and use ADB commands.
xclub_101 said:
It is essential that you have a backup of the EFS partition and a way to place it back - the first two ways that I would think about are:
a) use a good recovery - like Philz recovery, that has commands to restore EFS
b) if the format of the backup is not exactly right you might be able to boot in recovery and use ADB commands.
Click to expand...
Click to collapse
Code:
su
umount /efs
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
reboot
Ver3go said:
Code:
su
umount /efs
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
reboot
Click to expand...
Click to collapse
I am new to adb commands. Will phylz recovery help me enter the commands? if yes then i shall be replying with the sd card efs tar file name. Will then you be able to guide me with the commands based on the tar file?
Thanks all of you in advance.
Mush
mush2004 said:
I am new to adb commands. Will phylz recovery help me enter the commands? if yes then i shall be replying with the sd card efs tar file name. Will then you be able to guide me with the commands based on the tar file?
Thanks all of you in advance.
Mush
Click to expand...
Click to collapse
No for ADB you boot into recovery, connect your computer via USB and run the ADB commands from either Linux Terminal or Windows Command Prompt.
The tool here:
http://forum.xda-developers.com/showthread.php?t=1703488
May help if you're new to adb.
Otherwise it's a case of downloading and installing the drivers for your phone and the Android SDK http://developer.android.com/sdk/index.html
Thanks for all your replies.
Just wanted to confirm if i have the efs backup in sd card as under folder backup_efs and there are two files in tar.gz format will i be able to use the phylz recovery to use this replace my efs folder? if yes then can you guide me the steps please.
Regards,
Mush
mush2004 said:
Thanks for all your replies.
Just wanted to confirm if i have the efs backup in sd card as under folder backup_efs and there are two files in tar.gz format will i be able to use the phylz recovery to use this replace my efs folder? if yes then can you guide me the steps please.
Regards,
Mush
Click to expand...
Click to collapse
I do not remember right now what creates an backup_efs folder but it really does not matter that much - the tar.gz is a "file archive" and .img is usually a partition image. Each could have minor advantages - the .img also contains the entire filesystem of the partition (and will work easier if the filesystem is bonked) but a tar.gz backup is more versatile when you have bad sectors or a changed partition.
Under an advanced recovery like Philz you would just navigate some menus and try to restore the EFS - see the info in those specific threads.
Under ADB you need to have stuff (drivers and some programs) installed in your PC, you connect the phone on USB and you run ADB commands from the command line.
Hi all,
Did something stupid that erased my /persist folder. The folder exists now and most of the sensors and data has been restored but for wifi. The wifi bin files are missing, so if someone is kind enough to share the contents of their /persist it will be really helpful thanks.
On a rooted device, use a root capable File manager to access the /root folder of your moto z.
in system/persist, copy the contents and share it here.?
XT 1650 3
And also their system/etc/firmware/wlan folder please?
That doesn't work. The binaries are bound to the device serial number and the whole thing is then signed by motorola.
For now, don't do anything more to your persist folder! First, you need to save what's left to save.
Try this: connect your phone with the PC, boot into TWRP recovery..
Code:
adb shell "dd if=/dev/block/sda3 of=/tmp/sda3_persist.bin"
adb pull /tmp/sda3_persist.bin
This is the current partition image. You may be able to reconstruct the missing files and filenames.
However, chance is that you removed just the mount point of the persist partition.
Reinstall system partition and see if that brings back the persist folder...
benzinerwin said:
That doesn't work. The binaries are bound to the device serial number and the whole thing is then signed by motorola.
For now, don't do anything more to your persist folder! First, you need to save what's left to save.
Try this: connect your phone with the PC, boot into TWRP recovery..
Code:
adb shell "dd if=/dev/block/sda3 of=/tmp/sda3_persist.bin"
adb pull /tmp/sda3_persist.bin
This is the current partition image. You may be able to reconstruct the missing files and filenames.
However, chance is that you removed just the mount point of the persist partition.
Reinstall system partition and see if that brings back the persist folder...
Click to expand...
Click to collapse
Thanks for the reply.
/persist is now mounted and phone is booting and everything else is working (bluetooth connects, sensors are working etc) only wifi is not working.
Log Cat is not too helpful, just says wifi driver cannot load. System status gives IMEI number, bluetooth MAC address are shown. But Wifi is shown as 02:00:00:00. Not sure what is wrong! Hardware gone?
Thanks
Hm, you should backup your modem partition:
Code:
adb shell "dd if=/dev/block/sda16 of=/tmp/sda16_modem.bin"
adb pull /tmp/sda16_modem.bin
Afterwards, maybe you want to try this modem backup image from another moto-z...
I have no idea wheather that's locked a serial number or if it is just genereic. Make sure you have a backup of your current modem parition!
Flashing is just the commands slightly reversed...
Code:
adb push other_modem.bin /tmp/other_modem.bin
adb shell "dd if=/tmp/other_modem.bin of=/dev/block/sda16"
No Luck
thanks, can you confirm what is the contents of the /persist/wifi and /system/etc/firmware/wifi/?
Just want to check
anilisanil said:
No Luck
thanks, can you confirm what is the contents of the /persist/wifi and /system/etc/firmware/wifi/?
Just want to check
Click to expand...
Click to collapse
My booted system contains a /persist/wifi folder, but with no content
/system/etc/wifi contains 5 files: p2p_supplicant.conf, p2p_supplicant_overlay.conf, WCNSS_qcom_cfg.ini, wpa_suuplicant.conf, wpa_supplicant_overlay.conf.
Are you sure, you redtored all partitions properly? Maybe FSG as well, though I think it's just cellphone related & erased modemst1/2+cache?
benzinerwin said:
My booted system contains a /persist/wifi folder, but with no content
/system/etc/wifi contains 5 files: p2p_supplicant.conf, p2p_supplicant_overlay.conf, WCNSS_qcom_cfg.ini, wpa_suuplicant.conf, wpa_supplicant_overlay.conf.
Are you sure, you redtored all partitions properly? Maybe FSG as well, though I think it's just cellphone related & erased modemst1/2+cache?
Click to expand...
Click to collapse
The phone is booting without any errors at all, so I am not sure!
Same for me, so issue is not with persist. The etc/firmware/wifi is different for different people? I have 3 files, one .ini and 2 bin files- one for 2G and other for 5G- both are empty! Beats me!
I dont suspect wifi hardware going kaput so easily! But there are quite a few people who raised this in other device forums, but no one seem to have succeeded!
edit: I am assuming /etc/firmware are changed when we flash a new rom and the fact that I flashed the stock ROM a couple of times did not help means that the problem is not with /etc/firmware folder? Really clueless!
benzinerwin said:
My booted system contains a /persist/wifi folder, but with no content
/system/etc/wifi contains 5 files: p2p_supplicant.conf, p2p_supplicant_overlay.conf, WCNSS_qcom_cfg.ini, wpa_suuplicant.conf, wpa_supplicant_overlay.conf.
Are you sure, you redtored all partitions properly? Maybe FSG as well, though I think it's just cellphone related & erased modemst1/2+cache?
Click to expand...
Click to collapse
just realised, the contents are hidden, can you please ensure you are looking for hidden files as well?
anilisanil said:
just realised, the contents are hidden, can you please ensure you are looking for hidden files as well?
Click to expand...
Click to collapse
Yes & I did..
BTW, my phone runs on LineageOS.