Develop Bugs

[REF][GUIDE]CWM md5 mismatch problem solved

So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
WARNING!​
I'm no dev, just someone, that knows linux.
If you follow this path, you do it on your own. I'm not responsible for bricked devices, lost data or whatsoever, including the future the past and the present.​
Click to expand...
Click to collapse
There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).
Meeshka said:
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
Click to expand...
Click to collapse
If I helped, don't hesitate to push the Thanks button.

Thanks... a very useful guide. Bookmarked

WORKED!!! Tho I'm from a different device the first (adb) method saved my AOKP backup!!! Daysaver I'd say!!

I keep getting "md5sum: not found"

Put this in the general android section as it works across most devices. ..
Sent from my One V

Nevell said:
I keep getting "md5sum: not found"
Click to expand...
Click to collapse
if you send me the 2 img files i can create an appropirate md5 image of them, but send the one you did, so I can guess what the problem is.
send them to the email of my usr here, or in pm. and mainly, the md5 image has the name "nandroid.md5" like small caption all the way, even the md5? If it is there where it must, it must work, ad absurd it will be "wrong checksum error", but that is another version.
General android section has this, I have learned this from there, but it had only 1st option, and was "discovered" when cwm had generated wrong md5s, the V, in the V the problem is a tad bit different, but the solution is the same.

I fixed it in adb
Sent from my SPH-L710 using xda premium

Nevell said:
I fixed it in adb
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Can you explain what did you do to fix md5sum: not found error??
please i need it!

thatsgamer said:
Can you explain what did you do to fix md5sum: not found error??
please i need it!
Click to expand...
Click to collapse
Just created an md5sum manualy from the img files with the name of nandroid.md5, because on the V the recovery doesn't creates them because of cache mount problem.
The recovery process will end in an error message, because cache cannot be recovered, but the main thing will be recovered this way.

i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone

haky1988 said:
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
Click to expand...
Click to collapse
See : http://forum.xda-developers.com/showpost.php?p=32248108&postcount=7

unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup

CWM showing different versions
-Delete-

maranello69 said:
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
Click to expand...
Click to collapse
You do know that the first method is exactly like the one you linked right?
Aside that, I'm happy that the community could help you out

Loir can u help me. I can't locate the boot.img inside the downloads for cyanogen mod u provided. Forgive me but can you post a directory to this kernel file? Tks
Sent from my HTC Desire X using xda app-developers app

Thank you so much. You saved my phone.

For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me

no * 's
Ken-Shi_Kun said:
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
​
There are two ways for you, to make an md5 sum of the img files, the good and the bad one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
If I helped, don't hesitate to push the Thanks button.
Click to expand...
Click to collapse
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.

Beastben13 said:
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Click to expand...
Click to collapse
I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)

plz provide touch recovery for karbon a9+ plz and ther is bugs in cwm recovery 5.0.2.8 plz

[Tools][How-To][Guides] Backup & Restore EFS + Get out from Permanent Safe mode

Note to forum managers: Please make it a Sticky Thread, It should help to all users and there is no use for this tutorial if it is in page 3
Hello XDA Users,
I think some people here know who I am, so I will jump on the "Introduction of myself" for now.
Recently, I have faced many questions & problem of fake IMEI, of damaged EFS folder. So I made a little experiment on my device(GN2).
First, I backuped my EFS folder in 2 types - one is .img and the second is tar.gz.
Then, I deleted my EFS folder using ES Root Explorer. Which made my device to be on somethine called "Permanent Safe Mode" - You can not get out untill you fix your EFS folder and change some values.
This is permanent safe mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After I did my "research" I have managed to make several methods to backup & restore EFS, which should make your life easier and better.
First of all, Disclaimer:
I'm not responsible for any damage caused by using these methods, all methods tested by me, so it should work on your device too.
This is for I9505 Only!!!!!!!
Let's continue.
What you must have:
Latest base with latest modem and latest kernel - very important since in the latest versions samsung prevented the option to install old modems/kernels, so if you install old kernell/modem it can show you wrong IMEI.
Rooted device with the latest Super User
Latest busybox
PhilZ Recovery
Terminal Emulator
Root explorer - Can be ES File Explorer with working root option or just a root explorer from the market
A working EFS backup(In order to restore it...)
Time & Patient.
Important Notes:
When installing/downgrading firmwares, several people suffered from Fake IMEI. This is because the new firmware messed up your EFS folder, which means that you can not restore EFS backup until you are on the latest version, latest modem and latest stock kernel, recommended is XXUBMH1(right to 05/09/2013)
Some custom roms include modem installation in their rom installer. Due to modem flashing in recovery, some devices might get Fake IMEI. My recommendation is before even starting to use this guide, please try to install the latest modem via odin from this thread:
http://forum.xda-developers.com/showthread.php?t=2192025
When installing modem via odin, make sure you select PHONE and not PDA
You will find at least one method that works on your device, so don't give up after one method.
Read all guide and pay attention to all small details.
Backup methods
Method 1 - .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
The software:
I9505 EFS Backup / Restore
Help to preserve and restore the image of EFS partition:
* Need Root
For Windows
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run selected .bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run RUN_ME into terminal (double click), select option...
What is EFS, Why it is necessary to backup
Click to expand...
Click to collapse
Method 2 - .img backup
Method number 2 will create you efs.img backup on your internal sd. After that you can copy it to your computer.
What you have to do is this:
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.img bs=4096
Then click enter.
When it finishes, check if you have efs.img on your phone memory. If so, copy it to comupter, if not, you did something wrong try again.
Click to expand...
Click to collapse
Method 3 - .tar.gz backup
This method will compress your efs folder into tar.gz file. This method is the same as choosing backup EFS folder in my rom(PhoeniX ROM)/Omega/Wanam/etc.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
What you have to do is this:
Download this and copy it to your device:
http://d-h.st/SaK
Reboot into recovery
Flash the zip
Reboot your device.
Connect your device to your pc, and copy the backup in "efs_backup" folder.
Click to expand...
Click to collapse
Restore methods
Now the fun begins
You will have to restore your backup when you have one or more of the folowing problem:
Fake IMEI (usually 004999010640000) or "null" IMEI
Blinking SIM card icon on the top tray… ETC
Unable to unlock your SIM card using your PIN
Fake Serial Number (usually 0000000) or "null" Serial
Unable to register to the network (usually comes with Fake IMEI & Fake Serial so check them.)
Attention please,
If you are 100% that your EFS folder is damaged and you have a working EFS backup with the right IMEI number, my recommendation is this:
With root explorer, go to your efs folder and delete all files inside
Long press on power button will turn off your device.
Then turn on the device, you will be in "Permanent Safe Mode".
Continue to one of the following methods.
Click to expand...
Click to collapse
Method 1 - restore .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
The software:
I9505 EFS Backup / Restore
Help to preserve and restore the image of EFS partition:
* Need Root
For Windows
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run selected .bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run RUN_ME into terminal (double click), select option...
What is EFS, Why it is necessary to backup
Click to expand...
Click to collapse
Method 2 - Restore .img backup
Method number 2 will restore your efs.img backup from your internal sd.
What you have to do is this:
Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p10 bs=4096
Then click enter.
Now, reboot your device. If you still don't have IMEI/You are still in Safe Mod, reboot again.
In the second reboot, the bootanimation might stuck and the device will reboot automatically again. Don't worry, it is ok because it installs your efs.img.
Click to expand...
Click to collapse
Method 3 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Create on your Phone Memory(Not Extrenal sd!!) a folder called "efsbackup"(without quotes)
Copy all files & folders from the EFS backup into "efsbackup" folder(The files are like in the picture)
Download this script & copy it to your device:
http://d-h.st/zwR
Reboot into recovery
Go to mount section and click on(Very important!):
Mount /efs
Click to expand...
Click to collapse
Now install the script you have downloaded.
After it finishes, reboot.
Now everything should be fixed, of course if your backup is 100% ok.
If it doesn't work, try method 4.
Click to expand...
Click to collapse
Method 4 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taked from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Create on your Phone Memory(Not Extrenal sd!!) a folder called "efsbackup"(without quotes)
Copy all files & folders from the EFS backup into "efsbackup" folder(The files are like in the picture)
Using root explorer, go to "efsbackup folder, select all files & folders there, and click Copy.
Still in root explorer, go to "efs" folder of your device(It is located where all main folders like data, system, etc.).
In "efs" folder, click paste. It will ask you if you want to replace your files, select replace to all files(So all your files from "efsbackup" folder will be in "efs" folder)
Now open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Now write:
Code:
busybox chown 1001:1001 /efs/nv_data.bin
Then click enter.
Now write:
Code:
busybox chmod 06755 /efs/nv_data.bin
Then click enter.
Reboot device. Now everything should work.
Click to expand...
Click to collapse
Exit "Permanent Safe Mode"
When you in "Permanent Safe Mode" situation, it means that your EFS folder is broken.
If you succeeded in restoring your IMEI and you still stuck in this Safe Mode, use this guide:
Method 1
Open root explorer.
Navigate to /efs/FactoryApp/
Open "factorymode" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Open "keystr" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Reboot device.
Click to expand...
Click to collapse
Method 2
Open Terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Write the following & click enter:
Code:
rm /efs/FactoryApp/keystr
Write the following & click enter:
Code:
rm /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/keystr
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/factorymode
Reboot your device
Click to expand...
Click to collapse
This is all I can do for you friends, Worked alot on these methods to give you the best information.
Each method was tested by me and fully works.
If this helped you please press the "Thanks" button & Rate this thread 5 Stars.
If you like & appreciate my work please consider a donation!
Credits:
shnizlon
Candanga
A.S._id
dhiru1602
UtkarshGupta
P.M If you think that I forgot you
XDA:DevDB Information
Backup & Restore EFS + Get out from Permanent Safe mode - I9505, a Tool/Utility for the Samsung Galaxy S 4
Contributors
tamirda
Version Information
Status: Stable
Created 2013-09-05
Last Updated 2013-09-05

Amm i guess no one need it?

they do need it and i for one would like to thank you for the guide and time and effort in sharing ..mods and fixes are always welcome on xda thanks man:thumbup::thumbup:
Sent from my GT-I9505 using XDA Premium 4 mobile app

port76 said:
they do need it and i for one would like to thank you for the guide and time and effort in sharing ..mods and fixes are always welcome on xda thanks man:thumbup::thumbup:
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks first real comment in the thread
Sent from my GT-N7100 boosted by PhoeniX ROM

:thumbup:its ok any time my friend ....iv told my friends about the fix and I'm sure they will pop into this very useful and informative thread .. Thanks again iv added it to my subscribed topics and I'm sure people will be popping in to view and post on the thread thanks :thumbup::thumbup:
Sent from my GT-I9505 using XDA Premium 4 mobile app

Nice guide, the command line is the best! :good:

Will heimdall work as an alternative to restore the efs.img? Like this: heimdall flash --efs efs.img ?
It is used from download mode, like odin, so would work even if you cannot boot.

This Method, in Moto x?
tamirda said:
Note to forum managers: Please make it a Sticky Thread, It should help to all users and there is no use for this tutorial if it is in page 3
Hello XDA Users,
I think some people here know who I am, so I will jump on the "Introduction of myself" for now.
Recently, I have faced many questions & problem of fake IMEI, of damaged EFS folder. So I made a little experiment on my device(GN2).
First, I backuped my EFS folder in 2 types - one is .img and the second is tar.gz.
Then, I deleted my EFS folder using ES Root Explorer. Which made my device to be on somethine called "Permanent Safe Mode" - You can not get out untill you fix your EFS folder and change some values.
This is permanent safe mode:
After I did my "research" I have managed to make several methods to backup & restore EFS, which should make your life easier and better.
First of all, Disclaimer:
I'm not responsible for any damage caused by using these methods, all methods tested by me, so it should work on your device too.
This is for I9505 Only!!!!!!!
Let's continue.
What you must have:
Latest base with latest modem and latest kernel - very important since in the latest versions samsung prevented the option to install old modems/kernels, so if you install old kernell/modem it can show you wrong IMEI.
Rooted device with the latest Super User
Latest busybox
PhilZ Recovery
Terminal Emulator
Root explorer - Can be ES File Explorer with working root option or just a root explorer from the market
A working EFS backup(In order to restore it...)
Time & Patient.
Important Notes:
When installing/downgrading firmwares, several people suffered from Fake IMEI. This is because the new firmware messed up your EFS folder, which means that you can not restore EFS backup until you are on the latest version, latest modem and latest stock kernel, recommended is XXUBMH1(right to 05/09/2013)
Some custom roms include modem installation in their rom installer. Due to modem flashing in recovery, some devices might get Fake IMEI. My recommendation is before even starting to use this guide, please try to install the latest modem via odin from this thread:
http://forum.xda-developers.com/showthread.php?t=2192025
When installing modem via odin, make sure you select PHONE and not PDA
You will find at least one method that works on your device, so don't give up after one method.
Read all guide and pay attention to all small details.
Backup methods
Method 1 - .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
The software:
Method 2 - .img backup
Method number 2 will create you efs.img backup on your internal sd. After that you can copy it to your computer.
What you have to do is this:
Method 3 - .tar.gz backup
This method will compress your efs folder into tar.gz file. This method is the same as choosing backup EFS folder in my rom(PhoeniX ROM)/Omega/Wanam/etc.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
What you have to do is this:
Restore methods
Now the fun begins
You will have to restore your backup when you have one or more of the folowing problem:
Fake IMEI (usually 004999010640000) or "null" IMEI
Blinking SIM card icon on the top tray… ETC
Unable to unlock your SIM card using your PIN
Fake Serial Number (usually 0000000) or "null" Serial
Unable to register to the network (usually comes with Fake IMEI & Fake Serial so check them.)
Attention please,
If you are 100% that your EFS folder is damaged and you have a working EFS backup with the right IMEI number, my recommendation is this:
Method 1 - restore .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
The software:
Method 2 - Restore .img backup
Method number 2 will restore your efs.img backup from your internal sd.
What you have to do is this:
Method 3 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Method 4 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taked from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Exit "Permanent Safe Mode"
When you in "Permanent Safe Mode" situation, it means that your EFS folder is broken.
If you succeeded in restoring your IMEI and you still stuck in this Safe Mode, use this guide:
Method 1
Method 2
This is all I can do for you friends, Worked alot on these methods to give you the best information.
Each method was tested by me and fully works.
If this helped you please press the "Thanks" button & Rate this thread 5 Stars.
If you like & appreciate my work please consider a donation!
Credits:
shnizlon
Candanga
A.S._id
dhiru1602
UtkarshGupta
P.M If you think that I forgot you
XDA:DevDB Information
Backup & Restore EFS + Get out from Permanent Safe mode - I9505, a Tool/Utility for the Samsung Galaxy S 4
Contributors
tamirda
Version Information
Status: Stable
Created 2013-09-05
Last Updated 2013-09-05
Click to expand...
Click to collapse
Mr Tamirda
The method this, made in terminal, working in one moto x? it's my question

Pika71 said:
Mr Tamirda
The method this, made in terminal, working in one moto x? it's my question
Click to expand...
Click to collapse
?????

slugthru said:
Will heimdall work as an alternative to restore the efs.img? Like this: heimdall flash --efs efs.img ?
It is used from download mode, like odin, so would work even if you cannot boot.
Click to expand...
Click to collapse
You can try and share your experiences.
From my personal experience with another device the dd method in terminal works just fine

Sorry but null IMEI isn't fake IMEI
Difference:
Null IMEI means you don't even have any data for the IMEI oh and it's bad!
fake IMEI means you do have a data which is corrupt. Nothing more only digits has been changed.
There's a different between those
I remember having null IMEI and my backup didn't help at all service center was forced to swap motherboard to get IMEI working.
---------- Post added at 02:26 PM ---------- Previous post was at 02:26 PM ----------
Pika71 said:
Mr Tamirda
The method this, made in terminal, working in one moto x? it's my question
Click to expand...
Click to collapse
It depends if it uses same permission. Also there is a way to fix a corrupt IMEI while in recovery
Also don't quote whole op

My brothers phone is in safe mode could i backup my efs folder and restore onto his device?

ok, i am stuck in factory mode but none of the methods described work because there is nothing in my efs folder - it is empty so there are no files to actually edit.

modem DME4, DMF1

Hello everyone I have a problem with note 2
he flashed the modem DMF1, DME4 and recognizes them with the restore efs folder but when I reboot is imei null and baseband unknown
Solutions?

héllo
in first sorry for my english :silly:
backup your efs file
I made a RAR file with the 2 modem inside
unzip it on the pc or the phone
put the zip files in the sd card
flash via recovery
DMF1_MODEM modem_XXDME4 rar

jioan62 said:
héllo
in first sorry for my english :silly:
backup your efs file
I made a RAR file with the 2 modem inside
unzip it on the pc or the phone
put the zip files in the sd card
flash via recovery
DMF1_MODEM modem_XXDME4 rar
Click to expand...
Click to collapse
thanks for the reply
I will try to flash them, she takes it but when I restart then returns null imei
I do not understand why

mysterionTM said:
thanks for the reply
I will try to flash them, she takes it but when I restart then returns null imei
I do not understand why
Click to expand...
Click to collapse
I already discuseed this, you need to restore your EFS backup after you flash the ROM that you made the backup with.
so flash XXDMF1 with ROM XXDME6 (or DXDMF1) and then restore EFS.
if that didn't work. then flash XXDME4 then OTA update will give you XXDMF1.
If you can't recieve OTA updates and you have Root, then tell me so I send you my XXDMF1 and DME6. (dr.ketan has DXDMF1 which you must try first).
After every flash restore efs then restart to see if it is fixed.

thethiny said:
I already discuseed this, you need to restore your EFS backup after you flash the ROM that you made the backup with.
so flash XXDMF1 with ROM XXDME6 (or DXDMF1) and then restore EFS.
if that didn't work. then flash XXDME4 then OTA update will give you XXDMF1.
If you can't recieve OTA updates and you have Root, then tell me so I send you my XXDMF1 and DME6. (dr.ketan has DXDMF1 which you must try first).
After every flash restore efs then restart to see if it is fixed.
Click to expand...
Click to collapse
if you can put him I would be grateful
but then there is no way to have permanent XXDME4?
With the other note 2 had managed to get it going with this I can not

@mysterionTM
hello
take this and flash via odin pc and updates via OTA or KIES but after do backup efs file
/N7100XXDMB6_N7100OXADMB1_XEF.zip

mysterionTM said:
if you can put him I would be grateful
but then there is no way to have permanent XXDME4?
With the other note 2 had managed to get it going with this I can not
Click to expand...
Click to collapse
first of all make sure your phone is rooted. then download mobile odin Pro (you need Pro version to maintain root or simply root again). then download this file:
http://www.mediafire.com/download/ena68zhyjhwpc78/update.zip
Edit: this will make your mobile a french mobile, so don't flash it just get someone to convert it to a modem.bin or modify it for your country.
now open mobile odin pro and flash the Stock ROM XXDME6.
after it finishes open mobile odin pro again and go to update file, and choose the file you downloaded above. then flash it.
you you have build number XXDME6 and buildbase XXDMF1
now restore EFS by using this app: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Code:
Put your EFS file on your mobile (External SD Card is preferred on the Root of the Card, so its location should be /storage/extSdCard/efs.img).
name it efs.img for easier use (if it was an img file).
now in the terminal type this:
SU
then grant it superuser permissions.
then type this:
dd if=/storage/extSdCard/efs.img of=/dev/block/mmcblk0p3 bs=4096
it will show you numbers if it was done correctly.
then reboot your phone and everything should work correctly. Reboot again to make sure.
In case it didn't work, then Flash the DME6 ROM, it should come with DXDMF1 , then try restoring EFS again.
tell me what happens with you.

@mysterionTM
what is your configuration of your phone? (your rom)

I put thanks to you both
thethiny said:
first of all make sure your phone is rooted. then download mobile odin Pro (you need Pro version to maintain root or simply root again). then download this file:
http://www.mediafire.com/download/ena68zhyjhwpc78/update.zip
Edit: this will make your mobile a french mobile, so don't flash it just get someone to convert it to a modem.bin or modify it for your country.
now open mobile odin pro and flash the Stock ROM XXDME6.
after it finishes open mobile odin pro again and go to update file, and choose the file you downloaded above. then flash it.
you you have build number XXDME6 and buildbase XXDMF1
now restore EFS by using this app: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Code:
Put your EFS file on your mobile (External SD Card is preferred on the Root of the Card, so its location should be /storage/extSdCard/efs.img).
name it efs.img for easier use (if it was an img file).
now in the terminal type this:
SU
then grant it superuser permissions.
then type this:
dd if=/storage/extSdCard/efs.img of=/dev/block/mmcblk0p3 bs=4096
it will show you numbers if it was done correctly.
then reboot your phone and everything should work correctly. Reboot again to make sure.
In case it didn't work, then Flash the DME6 ROM, it should come with DXDMF1 , then try restoring EFS again.
tell me what happens with you.
Click to expand...
Click to collapse
excellent guide compliments
but to have the modem DME4 there is no permanent way?
jioan62 said:
@mysterionTM
what is your configuration of your phone? (your rom)
Click to expand...
Click to collapse
DME6

your CSC ?

jioan62 said:
your CSC ?
Click to expand...
Click to collapse
ITVDMF1

go here
http://forum.xda-developers.com/showthread.php?t=1896696

jioan62 said:
go here
http://forum.xda-developers.com/showthread.php?t=1896696
Click to expand...
Click to collapse
I saw it but I was looking for a way to install the modem DME4
I do not understand why it goes and then restart imei returns null
should be something inherent in the nv_data.bin or nv_data.bin.md5
I was looking for a way to fix the folder efs

ITV N7100XXDME6 is this your rom ?
flash via odin pc
download this your stock rom http://hotfile.com/dl/229491057/c20905b/ITV-N7100XXDME6-20130605085627.zip.html

mysterionTM said:
I put thanks to you both
excellent guide compliments
but to have the modem DME4 there is no permanent way?
Click to expand...
Click to collapse
what do you mean permanent way? why would you need DME4 if you have a higher better one?
you can flash DME4 (it comes with ROM DMB4) modem alone and keep it permanently, but if your EFS backup was when you had anything other than DME4 then you can't use it anymore, you have to recover EFS everytime.
just use XXDMF1 (since your CSC is DMF1) and restore EFS. don't see any reason to use an old modem.

jioan62 said:
ITV N7100XXDME6 is this your rom ?
flash via odin pc
download this your stock rom http://hotfile.com/dl/229491057/c20905b/ITV-N7100XXDME6-20130605085627.zip.html
Click to expand...
Click to collapse
yes, it is my rom
but by flashing the stock rom does not solve anything......
thethiny said:
what do you mean permanent way? why would you need DME4 if you have a higher better one?
you can flash DME4 (it comes with ROM DMB4) modem alone and keep it permanently, but if your EFS backup was when you had anything other than DME4 then you can't use it anymore, you have to recover EFS everytime.
just use XXDMF1 (since your CSC is DMF1) and restore EFS. don't see any reason to use an old modem.
Click to expand...
Click to collapse
you're right but with the other note 2 that I had was in the same condition and and I managed to do it !
with this I can not ....
I was leaving the modem DMF1 and I was able to go to the modem DME4 without any problems

mysterionTM said:
yes, it is my rom
but by flashing the stock rom does not solve anything......
you're right but with the other note 2 that I had was in the same condition and and I managed to do it !
with this I can not ....
I was leaving the modem DMF1 and I was able to go to the modem DME4 without any problems
Click to expand...
Click to collapse
on your other phone , you had EFS backup on DME4. on this phone, your backup is on DMF1. DMF can read DME backups, but DME can't read DMF backups because samsung changed the EFS read type on DMF1. so once you go DMF1, your EFS partition is changed permanently!

thethiny said:
on your other phone , you had EFS backup on DME4. on this phone, your backup is on DMF1. DMF can read DME backups, but DME can't read DMF backups because samsung changed the EFS read type on DMF1. so once you go DMF1, your EFS partition is changed permanently!
Click to expand...
Click to collapse
you're wrong
I was only backup on DMF1 on the other note 2
I followed this procedure and are able to put DME4 :
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.
5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
but on this note I can not!

mysterionTM said:
you're wrong
I was only backup on DMF1 on the other note 2
I followed this procedure and are able to put DME4 :
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.
5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
but on this note I can not!
Click to expand...
Click to collapse
oh, you followed the folder method! then yeah it works, but not recommended as it messed up permissions.
I was speaking about the mmcblk0p3 method.

how to know which modem i need? Im on stock firmware 4.4.2, Malaysia. Have the imei issue/corrupted efs and no backup

[TUT] [ROOT] Backup restore IMEI manually

Automatic Backup Restore IMEI TOOL by Sector1369 is HERE .
(Only Require Custom recovery)
Automatic backup restore CMD script added by "deadlyindian" at Post#5
(Require PC ,ADB drivers & Root permissions )
If you still want to do this manually, look below
IMEI backup of redmi 1s
Require ROOT permissions
We all known that EFS partition holds the imei,sn ,wifi mac & other important data.
In Snapdragon the EFS partition are modemst1 ,modemst2 & FSG partitions. so it's important to take backup of these partitions.
1.connect your phone to PC , adb debugging enabled & goto adb shell by,
Code:
adb shell su
OR
Open terminal emulator app in your phone & take super user permissions, by
Code:
su
2.type following commands to backup imei partitions.
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcblk0p16_modemst1
dd if=/dev/block/mmcblk0p17 of=/sdcard/mmcblk0p17_modemst2
dd if=/dev/block/mmcblk0p20 of=/sdcard/mmcblk0p20_fsg
also these are some important partition you should consider to backup.
modem, fsc, bk1, ddr.
Code:
dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23_modem
dd if=/dev/block/mmcblk0p9 of=/sdcard/mmcblk0p9_DDR
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12_bk1
dd if=/dev/block/mmcblk0p18 of=/sdcard/mmcblk0p18_fsc
Now the backup is stored in you internal storage ,store these files in safe place.
in case u get invalid imei or unknown, restore these partitions.
To restore these partitions,
Code:
dd if=/sdcard/mmcblk0p16_modemst1 of=/dev/block/mmcblk0p16
dd if=/sdcard/mmcblk0p17_modemst2 of=/dev/block/mmcblk0p17
dd if=/sdcard/mmcblk0p20_fsg of=/dev/block/mmcblk0p20
dd if=/sdcard/mmcblk0p23_modem of=/dev/block/mmcblk0p23
dd if=/sdcard/mmcblk0p9_DDR of=/dev/block/mmcblk0p9
dd if=/sdcard/mmcblk0p12_bk1 of=/dev/block/mmcblk0p12
dd if=/sdcard/mmcblk0p18_fsc of=/dev/block/mmcblk0p18
Working on Aroma EFS backup restore tool..
NOTE:-
Don't use tools or commands from other device because different devices has different partition address, that will result in wrong backups.
To use this method to backup other phones EFS , u should find your partition info.
Redmi 1s Partition tables can be found HERE
ENJOY,

Thanks man...it would be alot helpful if i gone to any trouble [emoji7]

But the problem with lost imei is for Redmi with MediaTek processor. Redmi Qualcomm don't suffer from this problem.

pgreed said:
But the problem with lost imei is for Redmi with MediaTek processor. Redmi Qualcomm don't suffer from this problem.
Click to expand...
Click to collapse
i know but it's always better to take bakup,who knows what 'll happen...
there is no way to generate imei,wifi mac data for qualcomm (as far as i know) ...
so it will come handy...

Auto IMEI Backup & Restore Tool
Backup restore IMEI Automatically
FIRST INSTALL THE ADB DRIVERS FOR THE 1S ► GO HERE ◄
Requires Phone to be ROOTED & USB Debugging turned ON
This is for Xiaomi Redmi 1S Only
I've created a CMD script that will automatically backup the IMEI & Also Restore it back again if you want to...
Backed Up files are inside MYIMEI folder of your selected backup storage.
NOTE : Enable root access for adb if you're on Custom ROM based on CyanogenMod
to do that ► Open Settings ► Superuser ► Superuser Access ► Select Apps and ADB ► done
► Download it from attachment
► Extract it
► Run R1SBAR.exe & follow instructions.
While restoring make sure the backed up files are inside the MYIMEI folder of either Internal Memory or External or it wont work.
If you face any error do tell me!
AGAIN ITS ONLY FOR REDMI 1S

deadlyindian said:
Backup restore IMEI Automatically
Requires Phone to be ROOTED & USB Debugging turned ON
This is for Xiaomi Redmi 1S Only
I've created a CMD script that will automatically backup the IMEI & Also Restore it back again if you want to...
Backed Up files are inside MYIMEI folder of your selected backup storage.
► Download it from attachment
► Extract it
► Run R1SBAR.exe & follow instructions.
While restoring make sure the backed up files are inside the MYIMEI folder of either Internal Memory or External or it wont work.
If you face any error do tell me!
AGAIN ITS ONLY FOR REDMI 1S
Click to expand...
Click to collapse
It working perfectly.Thank you.

pgreed said:
It working perfectly.Thank you.
Click to expand...
Click to collapse
You're Welcome :good:

[Backup restore IMEI Automatically] works like charm. thanks :good:

lavizta said:
[Backup restore IMEI Automatically] works like charm. thanks :good:
Click to expand...
Click to collapse
im glad it help :good:

deadlyindian said:
Backup restore IMEI Automatically
Requires Phone to be ROOTED & USB Debugging turned ON
This is for Xiaomi Redmi 1S Only
I've created a CMD script that will automatically backup the IMEI & Also Restore it back again if you want to...
Backed Up files are inside MYIMEI folder of your selected backup storage.
► Download it from attachment
► Extract it
► Run R1SBAR.exe & follow instructions.
While restoring make sure the backed up files are inside the MYIMEI folder of either Internal Memory or External or it wont work.
If you face any error do tell me!
AGAIN ITS ONLY FOR REDMI 1S
Click to expand...
Click to collapse
Great work :good::good:

None of the usual ROM / kernel flashing result in loss of these partitions .
If someone is able to screw up partitions, chances are that he will remove the partition table too ..
and with that he will not be able to fastboot anymore , to use backups made here.
Don't get me wrong, but its of little use imo.
Sector1369 said:
Code:
dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23_modem
dd if=/dev/block/mmcblk0p9 of=/sdcard/mmcblk0p9_DDR
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12_bk1
dd if=/dev/block/mmcblk0p18 of=/sdcard/mmcblk0p18_fsc
ENJOY,
Click to expand...
Click to collapse

kapil.git said:
None of the usual ROM / kernel flashing result in loss of these partitions .
If someone is able to screw up partitions, chances are that he will remove the partition table too ..
and with that he will not be able to fastboot anymore , to use backups made here.
Don't get me wrong, but its of little use imo.
Click to expand...
Click to collapse
U never know when sh*t happens there is no harm in taking the backup. Had personally lost imei on couple of Samsung phone while flashing roms and was able to restore it with the efs backup.

rkkaranrk said:
U never know when sh*t happens there is no harm in taking the backup. Had personally lost imei on couple of Samsung phone while flashing roms and was able to restore it with the efs backup.
Click to expand...
Click to collapse
I mean backing up DRM keys and TA partitions made sense since they are wiped in some bootloader unlocking..
You almost make it sound like, I can restore someone else's IMEI too :silly: ..
I still have my old nokia phones with me of which I can rob their identities ?
Some random Redmi dev can give surprise to actually make an app for this..
Chinese phones have already been a pain in a$$ for Indian Govt due to lack / duplicate of this IMEI modules.

kapil.git said:
I mean backing up DRM keys and TA partitions made sense since they are wiped in some bootloader unlocking..
You almost make it sound like, I can restore someone else's IMEI too :silly: ..
I still have my old nokia phones with me of which I can rob their identities ?
Some random Redmi dev can give surprise to actually make an app for this..
Chinese phones have already been a pain in a$$ for Indian Govt due to lack / duplicate of this IMEI modules.
Click to expand...
Click to collapse
I'm pretty sure u have been using a Sony phone and have limited knowledge so don't jump and compare the phones with the same thing.
As for the imei take help of google and search for z3x/cyclone/nspro/magma what are they used for:silly:

it might come in handy or it might not
nevertheless i'm putting it in safekeeping.
thanks for the work & effort.
:good:

rkkaranrk said:
I'm pretty sure u have been using a Sony phone and have limited knowledge so don't jump and compare the phones with the same thing.
Click to expand...
Click to collapse
Yes you are correct , been using Sony for a while
As for the imei take help of google and search for z3x/cyclone/nspro/magma what are they used for:silly:
Click to expand...
Click to collapse
mmmkaay..

@deadlyindian,
Thanks for providing the automated script to back up imie.
I did go through your post and did as per the instructions mentioned step by step. However, I am unable to proceed after getting the message "Please connect usb cable now" after running R1SBAR. I do have root access(checked from root checker app) and have also enabled USB Debugging. I also inserted cable after getting the message.
Does it take a lot of time(more than 5 mins) to backup imei cause I continued till 5 mins before closing the cmd prompt.
Hope you can help me here.
PS: I am using MIUI v45 global version "JHCCNBH45.0 （V5） " in case if you need.

ADB Drivers & instructions...
fanboy_android said:
@deadlyindian,
Thanks for providing the automated script to back up imie.
I did go through your post and did as per the instructions mentioned step by step. However, I am unable to proceed after getting the message "Please connect usb cable now" after running R1SBAR. I do have root access(checked from root checker app) and have also enabled USB Debugging. I also inserted cable after getting the message.
Does it take a lot of time(more than 5 mins) to backup imei cause I continued till 5 mins before closing the cmd prompt.
Hope you can help me here.
PS: I am using MIUI v45 global version "JHCCNBH45.0 （V5） " in case if you need.
Click to expand...
Click to collapse
Have you installed the ADB drivers for the 1S? ► ADB Drivers ◄
After installing Run R1SBAR.exe & follow the below screens
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

deadlyindian said:
Have you installed the ADB drivers for the 1S? ► ADB Drivers ◄
After installing Run R1SBAR.exe & follow the below screens
Click to expand...
Click to collapse
Yes, it seems adb drivers were missing after which I was able to successfully backup my IMIE. Thanks for your help.
Perhaps you could add this link in your earlier post as a pre-requisite so that newcomers won't face this issue. Just a suggestion
Kudos and keep rocking.

fanboy_android said:
Yes, it seems adb drivers were missing after which I was able to successfully backup my IMIE. Thanks for your help.
Perhaps you could add this link in your earlier post as a pre-requisite so that newcomers won't face this issue. Just a suggestion
Kudos and keep rocking.
Click to expand...
Click to collapse
Done!!

[Q&A] UNA ROM, Secure, Private And Fast

Q&A for UNA ROM, Secure, Private And Fast
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for UNA ROM, Secure, Private And Fast. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Screenshots
hey guys can you post some screenshots as that would make it clear for the people who wish to download it and it seems to be a great work broda excited to use it

installation problem
i tried as u said in the op but got stuck up with installation error can you help me with this?

subscribed.:thumbup:
"all I can really do , is stay out of my own way and let the will of heaven be done"

@hemant4409
4.1 is jellybean bro and y won't people give a try to it its an absolutely secure and different is then the daily ones I am trying to install it but didn't get any success hope the developer replies soon m on 5.0.2 cm12

jenchheda said:
@hemant4409
4.1 is jellybean bro and y won't people give a try to it its an absolutely secure and different is then the daily ones I am trying to install it but didn't get any success hope the developer replies soon m on 5.0.2 cm12
Click to expand...
Click to collapse
What custom recovery do you use?
And what does exactly the message say?
Did you unzip the downloaded fle?
It s not a flashable zip, it s backup from my wife's grand so you have to restore it like any backup...

installation problem
@unclefab
i am using philz recovery and yeah i extracted the zip saves it in clockworkmod folder but i couldnt find any way to restore it can you please elaborate the steps for a beiginner like me as no doubt your work seems to be damn fantastic as its way different from other custom roms hats off to you broda

In the clockworkmod folder you must make a folder called backup, then put the unzipped file there.
Then, you restore it as any backup.
Maybe the file didn t download propery, when you unzip it, what do you see inside the 2015-03-23.10.56.05 folder?
There should be :
boot.img
cache.ext4
cache.ext4.a
data.ext4
data.ext4.a
nandroid.md5
recovery.img
system.ext4.tar
system.ext4.tar.a
Do backup your efs folder (VERY IMPORTANT).
Open an android terminal from your phone, first type "su" (without the quotes), enter, then type:
busybox dd if=/dev/block/mmcblk0p17 of=/sdcard/efs.img
This will create an efs backup caled efs.img in your sd card.
If you need to restore it type:
busybox dd if=/sdcard/efs.img of=/dev/block/mmcblk0p17
Now, backup your current ROM.
Then, on philz' settings choose clean install for a new rom, then flash Una by restoring the 2015-03-23.10.56.05 folder.

@unclefab
i will post the link to the files extracted and i downloaded the whole for the second time and still while restoring m getting an system error the link for the image is below
https://drive.google.com/open?id=0B81npVXrcH4XLWh6US15Q3MzSFU&authuser=0

jenchheda said:
@unclefab
i will post the link to the files extracted and i downloaded the whole for the second time and still while restoring m getting an system error the link for the image is below
https://drive.google.com/open?id=0B81npVXrcH4XLWh6US15Q3MzSFU&authuser=0
Click to expand...
Click to collapse
I m sorry, I don t have any google account so I can t access your picture with the error message.
But it s really strange, it should restore.
Or maybe it s because the backup has been done with CWM?
Normally that shouldn t be a problem, but anyway, you can flash CWM from here:
http://forum.xda-developers.com/showthread.php?t=2315529
and use it to restore Una.
But before to do that you have to backup your efs folder (VERY IMPORTANT).
Open an android terminal from your phone, first type "su" (without the quotes), enter, then type:
busybox dd if=/dev/block/mmcblk0p17 of=/sdcard/efs.img
This will create an efs backup caled efs.img in your sd card.
If you need to restore it type:
busybox dd if=/sdcard/efs.img of=/dev/block/mmcblk0p17
Now, backup your current ROM and then restore Una with CWM.
Or, you can explore Philz' settings, because there are options to backup/restore with different formats, and I guess the problem comes from there, Una is maybe in a format that Philz can t read depending on its current settings.
In Philz, go to Misc Nandroid Settings, select use TWRP mode, and try again.
If the restoring fails, untick md5 sum check, again in Misc Nandroid Settings, and try again.
If if it still doesn t work go once more in Misc Nandroid Settings and this time select Regenerate md5 sum.
Or just flash CWM and use it to restore Una, maybe that s easier)
In any case let us know, in order us to edit the installation section in OP if needed.

bootloop T_T

omar0alaa said:
bootloop T_T
Click to expand...
Click to collapse
It s not a bootloop, in some cases you have to restart the phone a second time.
I mean, after you have installed Una you reboot, then if it doesn t start you press the power button and restart the phone (I had it a few times at the time I was working on the ROM).
Please do report here if it works.
@jenchheda:
did you manage to install Una?
A feedback would be nice, thanks in advance

is this rom single sim or dual sim

aneel0301 said:
Click to expand...
Click to collapse
This rom should be dual sim as it modified stock based.
I also got the bootloop
Tried 21 reboots even with factory reset/ clean cache etc it doesn't boot.

RichyE said:
This rom should be dual sim as it modified stock based.
I also got the bootloop
Tried 21 reboots even with factory reset/ clean cache etc it doesn't boot.
Click to expand...
Click to collapse
Sorry for the late reply, I havent been very much on the forum lately...
The rom is dual sim of course.
Are you guys on 4.2.2?
I don t remember very well since I did it nearly 2 years ago, but if I m not mistaken if you are coming from 4.2.2 and want to restore a 4.1.2 cwm backup you have to odin flash stock 4.1.2 first.
So you odin flash 4.1.2, then you can restore Una using the recovery mentionned in OP.
Good luck, and let me know if it works, thanks in advance!