[ GUIDE ] How to backup IMEI on MIcromax Canvas Knight A350 - Micromax Canvas Knight Guides, News, & Discussion

This guide will help you easily backup / restore your IMEI on Micromax Canvas Knight A350
NOTE :
* This guide is applicable for many other * Mediatek * devices ( Mediatek only).
* Easiest method (There are other methods too).
* This will only backup your IMEI alone and not the whole NVRAM !
* Only applicable if the NVRAM is not corrupted (If the Baseband version is not shown ' UNKNOWN ' ).
* ROOT access necessary.
PROCESS :
BACKUP ​
* Download Mobile Uncle Tools from Playstore.
* Open the app and grant SuperUser permission.
* Now navigate to ' IMEI Backup Restore (MTK) ' option and click on it.
* Click on the ' Backup IMEI to SDCARD (MTK) '
* The backup will be found in the SD Card ! ( will look like this ' imei.tar' )
RESTORE​
* Download Mobile Uncle Tools from Playstore.
* Open the app and grant SuperUser permission.
* Now navigate to ' IMEI Backup Restore (MTK) ' option and click on it.
* Click on the ' Restore IMEI from SDCARD (MTK) '
* Reboot !
​
​

Related

Please develop some custom rom for micromax a52 android mobile

hi this phone was rooted on 25th sept(after many months of launch).i request the devs here someone to please develop an custom rom for the mobile or just mod the current one.
How to root?
By this time, many users may get rooted but there is no tutorial for that in androidforums so posting here.
Plus, I have modded original boot.img of A52 myself and added init.d support plus support for initializing ext2,3,4 modules on boot.
DOWNLOADS:
1) Unsecured boot.img (zip contains unsecured boot.img + A52 scatter file)
http://www.mediafire.com/?h9ubm9dhq9n7jjd
2) SP.FlashTool
http://forum.xda-developers.com/attachment.php?attachmentid=1353992&d=1348592592
3) Drivers
http://forum.xda-developers.com/attachment.php?attachmentid=1353943&d=1348591411
4) UnlockRoot
http://www.unlockroot.com/
Note: Usemastermind1024 as password to download above files.
Advantages of my boot.img:
I have added init.d support plus ext2.ko,ext3.ko & ext4.ko modules initialization on boot.Just place this ko files in /system/lib/modules/ after rooting the device, u will be able to use Link2SD with ext2,3 or 4 filesystems on your 2nd sdcard partition.
Press thanks if helped
Reference for flashing: MT65x3 flashing tutorial
Read the above tutorial first so u get idea how to flash an img file using SP FlashTool.
STEPS TO FLASH BOOT.IMG:
1) First install the drivers you downloaded & then run SPFlashTool, preferably as administrator (not mandatory)
2) Select USB mode under Options
3) Click Scatter-loading & select scatter file you downloaded from above links.
4) It will automatically load boot.img if it's in the same folder with scatter file otherwise click BOOTIMG & select the downloaded unsecured boot.img
5) Turn off the device fully, remove the battery for 5 seconds to be sure n re-insert the battery but do not power on device.
6) Attach the usb cable with PC but not with device
7) Now click on "Download" button on SPFlashTool, it will show searching for device in lower panel.
8) At this time, attach the cable with device in power off state
9) Now as soon as u attach the cable to device in power off state it will show a progress bar in lower panel n then a dialogue which states successfully flashed n another dialogue showing green colored ring n stating Download OK.
12) Close the dialogues, close the program n reboot the device by pressing power key.
STEPS TO ROOT DEVICE:
1. Power on device.
2. Enable USB Debugging.
- Settings > Application tab > Applications > Development > USB Debugging
3. Install UnlockRoot in pc
4. Attach device using usb cable in debugging mode(u just enabled it in step-2) to pc.
5. Now Run UnlockRoot program and click Root button
6. Confirm online device Micromax A52 in the list which pop-up.
7. Let in finish the procedure and Restart device when is asks.
8. See new Superuser app in app drawer
9. Viola...!!! Your A52 is now rooted.
UnlockRoot does not install Busybox on device so after u rooted the device install busybox to work with many root apps.Search Play Store for Busybox Installer by Jrummy OR BusyBox free by Stericson...
DISCLAIMER:
I am not responsible for bricked devices, dead SD cards, . Please do some research if you have any concerns before flashing! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device
Press thanks if helped

Xolo Q1000 Rooting and Flushing CWM Method.

Xolo Q1000 Stock Nanodroid Backup, Rooting and Flushing CWM Method. (Tested on my own Phone)with Xolo Q1000 Stock Nandroid Backup
Read everything or risk a brick standard disclaimer. Your warranty is now void. Use at your own risk. In other words, it is your choice to use this method; I am not responsible for any damage or problems. (Well this method will definitely work). Don’t do it if you don’t know what is rooting and CWM.
1. Go to Settings > About Phone.
2. Next, scroll all the way down and tap on About Phone, and you will notice a segment detailing your device’s build number (XOLO
_Q1000_S105_130411).
3. Repeatedly tap on Build Number (seven taps should do the trick) until you’re met with a message that reads: “you are now a developer!”
4. Developer Options will now be available in within the Settings app.
5. Go to settings > developer options > enable USB debugging.
6. Download AND Install MTK Drivers h t t p : / / w w w . m e d I a f I r e . c o m /download/nv96xclhjmaiclu/Mobistel_Cynus_T1_Drivers_x86.exeDownload Here)
7. Reboot your PC.
8. Download and extract the MTK6589 Auto Root folder from the .rar download. H t t p : / / w w w . s e n d s p a c e . c o m /file/v9np38 Download Here)
9. Connect your phone to PC visa USB.
10. Run run.bat from the extracted MTK6589 Auto Root folder.
11. Press any key and wait while it roots your phone
12. After finished, now reboot
13. Now you’re rooted. Verify root with a ‘Root Checker’ app from Play, or run any app you know requires root and you should see a root permissions request.
14. Reboot your phone.
15. Now download Recovery Image and put it in to sd card. H t t p s : / / w w w . b o x . c o m/s/ymebwi7p7s6aegy0cunx Download Here)
16. Download Mobile uncle from play store.
17. Open Mobile uncle and Grand root access to it.
18. There is an option to flush recovery. Select it.
19. It will search the recovery image that is in sd card. Also if you are online then it will show more recovery from internet. I never tried that but they should also work but probably in Chinese language.
20. Select recovery it will ask for permission. Hit ok.
21. It will reboot your phone. Now CWM has been flushed.
22. Now you can do any CWM operations including flushing Touch wiz launcher and xperia keyboard as I already did.
Download: Stock Nandroid Backup for Xolo Q1000 (Untoched) from h t t p : / / d - h . s t / W k T
sizariya said:
Xolo Q1000 Rooting and Flushing CWM Method. (Tested on my own Phone)
Read everything or risk a brick standard disclaimer. Your warranty is now void. Use at your own risk. In other words, it is your choice to use this method; I am not responsible for any damage or problems. (Well this method will definitely work). Don’t do it if you don’t know what is rooting and CWM.
1. Go to Settings > About Phone.
2. Next, scroll all the way down and tap on About Phone, and you will notice a segment detailing your device’s build number (XOLO
_Q1000_S105_130411).
3. Repeatedly tap on Build Number (seven taps should do the trick) until you’re met with a message that reads: “you are now a developer!”
4. Developer Options will now be available in within the Settings app.
5. Go to settings > developer options > enable USB debugging.
6. Download AND Install MTK Drivers h t t p : / / w w w . m e d I a f I r e . c o m /download/nv96xclhjmaiclu/Mobistel_Cynus_T1_Drivers_x86.exeDownload Here)
7. Reboot your PC.
8. Download and extract the MTK6589 Auto Root folder from the .rar download. H t t p : / / w w w . s e n d s p a c e . c o m /file/v9np38 Download Here)
9. Connect your phone to PC visa USB.
10. Run run.bat from the extracted MTK6589 Auto Root folder.
11. Press any key and wait while it roots your phone
12. After finished, now reboot
13. Now you’re rooted. Verify root with a ‘Root Checker’ app from Play, or run any app you know requires root and you should see a root permissions request.
14. Reboot your phone.
15. Now download Recovery Image and put it in to sd card. H t t p s : / / w w w . b o x . c o m/s/ymebwi7p7s6aegy0cunx Download Here)
16. Download Mobile uncle from play store.
17. Open Mobile uncle and Grand root access to it.
18. There is an option to flush recovery. Select it.
19. It will search the recovery image that is in sd card. Also if you are online then it will show more recovery from internet. I never tried that but they should also work but probably in Chinese language.
20. Select recovery it will ask for permission. Hit ok.
21. It will reboot your phone. Now CWM has been flushed.
22. Now you can do any CWM operations including flushing Touch wiz launcher and xperia keyboard as I already did.
23. If you want to flush stock recovery back then same method can be applied. H t t p : / / d – h . s t /N8n Download Here)
Click to expand...
Click to collapse
good show chap! but i would recommend renaming it so it would be easier for newbies to find this. requesting it should be moved also.
what it should be?
Rename what? Please explain sir
I've rooted my XOLO Q1000 already.
Forgot to make a backup :| but hey! Thanks for the stock ROM!
Thanks button pressed.
Sent from my Q1000 using xda app-developers app
How do i flash the nandroid backup which i took from the internet
I might sound like a total noob.. that is because iam still in 9th grade..
guys.. could anyone help me to get to the stock rom of xolo q1000
i installed the nandroid backup that was given above..but when i go into recovery, and flash the nanadroid zip the instalation is aborted all the fricking time..:crying:
please help me..iam in need of help..
P.S iam new to xda..
Good start Dude..
BhavyaBirla said:
I might sound like a total noob.. that is because iam still in 9th grade..
guys.. could anyone help me to get to the stock rom of xolo q1000
i installed the nandroid backup that was given above..but when i go into recovery, and flash the nanadroid zip the instalation is aborted all the fricking time..:crying:
please help me..iam in need of help..
P.S iam new to xda..
Click to expand...
Click to collapse
Actually you have to unzip the nandroid backup given by me. Then place it in your SD card. Don't change the structure of directory. then go to CWM recovery. then backup and restore then restore the backup. Done. If any problem then pleas PM me or call me (Zero Nine Four Two Five Four Five One One Eight Six Or Zero Seven Three Eight Nine Nine Two Six Zero One Eight) any time dude. We will learn many things new also.
ROM please?
sizariya said:
Actually you have to unzip the nandroid backup given by me. Then place it in your SD card. Don't change the structure of directory. then go to CWM recovery. then backup and restore then restore the backup. Done. If any problem then pleas PM me or call me (Zero Nine Four Two Five Four Five One One Eight Six Or Zero Seven Three Eight Nine Nine Two Six Zero One Eight) any time dude. We will learn many things new also.
Click to expand...
Click to collapse
Thanks man.. hey.. could you please help me find a good rom for my phone? i didnt like the miui or the lewa os.. is there any other rom like cm or anything good enough..P.S also could u help me get the z1 walkman app on my phone..that would be great man..Thanks in advance!!:laugh:
Unable to find the nandroid backup!!
sizariya said:
Actually you have to unzip the nandroid backup given by me. Then place it in your SD card. Don't change the structure of directory. then go to CWM recovery. then backup and restore then restore the backup. Done. If any problem then pleas PM me or call me (Zero Nine Four Two Five Four Five One One Eight Six Or Zero Seven Three Eight Nine Nine Two Six Zero One Eight) any time dude. We will learn many things new also.
Click to expand...
Click to collapse
DUDE... I UNZIPPED THE NANDROID BACKUP AND PLACED IT ON MY SD card..but when i go in to restore it says no files found ...what do i do now..iam stuck between roms..:crying::crying::crying:
please reply quick
BhavyaBirla said:
DUDE... I UNZIPPED THE NANDROID BACKUP AND PLACED IT ON MY SD card..but when i go in to restore it says no files found ...what do i do now..iam stuck between roms..:crying::crying::crying:
please reply quick
Click to expand...
Click to collapse
Please tell me the full structure of unzipped file. Also send me the property view of this folder.
I did it!!
sizariya said:
Please tell me the full structure of unzipped file. Also send me the property view of this folder.
Click to expand...
Click to collapse
I did it.. Thanks..
But I want a god rom.. Like Cyanogenmod..
Could u suggest me some.. I don't pike Miui or lewa
Please help me
hai Sizariya.........thanks buddy....its a nice one......i rooted my xolo q1000.Hope new roms will be available in future.
A small problem is that its taking much time to recharge.Why that happening?
Have anyone noticed in our battery it is written as Li-Polymer. but actuallly it is Li-ion.How that happened??
Hi Sizariya...
Does this one apply on to Xolo Q1000s as well? If not, can you please guide me to something on that?!?
I need to install a recovery module on my phone - either of CWM or TWRP would do.
Thanks,
BhavyaBirla said:
I did it.. Thanks..
But I want a god rom.. Like Cyanogenmod..
Could u suggest me some.. I don't pike Miui or lewa
Please help me
Click to expand...
Click to collapse
OK i dont know if you will understand this but I will just try to explain a little
For making roms like CM, Pac , PA and stuff, You need kernel source code of that device
Without that it is impossible to build CM ( Even the Kitkat CM 11 )
Xolo never gives out kernel source code nor does Mediatek (MTK)
q1000 is Mt6589, so you can try to port from other devices too but building such good roms from scratch without bugs ?? It is impossible
So cheers and wait until someone does that himself
And yeah being in 9th doesnt make you a n00b
The reason you are n00b is that you just never reached out to know more about it
Cheers, have a good one
Protox 109,
Senior Member - Xda Dev
Read the resrt in my Signature
sizariya said:
Xolo Q1000 Stock Nanodroid Backup, Rooting and Flushing CWM Method. (Tested on my own Phone)with Xolo Q1000 Stock Nandroid Backup
Read everything or risk a brick standard disclaimer. Your warranty is now void. Use at your own risk. In other words, it is your choice to use this method; I am not responsible for any damage or problems. (Well this method will definitely work). Don’t do it if you don’t know what is rooting and CWM.
1. Go to Settings > About Phone.
2. Next, scroll all the way down and tap on About Phone, and you will notice a segment detailing your device’s build number (XOLO
_Q1000_S105_130411).
3. Repeatedly tap on Build Number (seven taps should do the trick) until you’re met with a message that reads: “you are now a developer!”
4. Developer Options will now be available in within the Settings app.
5. Go to settings > developer options > enable USB debugging.
6. Download AND Install MTK Drivers h t t p : / / w w w . m e d I a f I r e . c o m /download/nv96xclhjmaiclu/Mobistel_Cynus_T1_Drivers_x86.exeDownload Here)
7. Reboot your PC.
8. Download and extract the MTK6589 Auto Root folder from the .rar download. H t t p : / / w w w . s e n d s p a c e . c o m /file/v9np38 Download Here)
9. Connect your phone to PC visa USB.
10. Run run.bat from the extracted MTK6589 Auto Root folder.
11. Press any key and wait while it roots your phone
12. After finished, now reboot
13. Now you’re rooted. Verify root with a ‘Root Checker’ app from Play, or run any app you know requires root and you should see a root permissions request.
14. Reboot your phone.
15. Now download Recovery Image and put it in to sd card. H t t p s : / / w w w . b o x . c o m/s/ymebwi7p7s6aegy0cunx Download Here)
16. Download Mobile uncle from play store.
17. Open Mobile uncle and Grand root access to it.
18. There is an option to flush recovery. Select it.
19. It will search the recovery image that is in sd card. Also if you are online then it will show more recovery from internet. I never tried that but they should also work but probably in Chinese language.
20. Select recovery it will ask for permission. Hit ok.
21. It will reboot your phone. Now CWM has been flushed.
22. Now you can do any CWM operations including flushing Touch wiz launcher and xperia keyboard as I already did.
Download: Stock Nandroid Backup for Xolo Q1000 (Untoched) from h t t p : / / d - h . s t / W k T
Click to expand...
Click to collapse
Typo check : It is cwm flashing and touchwiz flashing... Not FLUSHING
cant enter into recovery mode shows option for
recovery
fastboot
normal
but cant select either of them plz urgent help required
Stock Firmware
BhavyaBirla said:
I might sound like a total noob.. that is because iam still in 9th grade..
guys.. could anyone help me to get to the stock rom of xolo q1000
i installed the nandroid backup that was given above..but when i go into recovery, and flash the nanadroid zip the instalation is aborted all the fricking time..:crying:
please help me..iam in need of help..
P.S iam new to xda..
Click to expand...
Click to collapse
Here u go :
http://androidxda.com/download-xolo-stock-rom-model
Dont mention the 9th grade
I am a dev nd im in 10th
njoyy!!
gladiator9120 said:
file not found can u re-upload it please.
Click to expand...
Click to collapse
did you try removing the spaces from the URL given?
those links worked for me
gladiator9120 said:
please find attachment.
Click to expand...
Click to collapse
I guess he must have removed the file.
try this link http://www.needrom.com/download/xolo-q1000/

[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.

[TIP/TRICK] - How to enable app/screen pinning on MIUI [works for other devices]

Code:
/*
* I am not responsible for bricked devices, dead SD cards, data loss,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about tips provided here.
* Before making any alteration to your system make sure you know what you
* are doing and have previously made a backup of all sensitive data!
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will just laugh at you.
*/
BEWARE THE APP LINKED IN THIS THREAD ALLOW YOU TO MAKE MODIFICATIONS TO YOUR OPERATING SYSTEM WHICH CAN SERIOUSLY MESS UP YOUR DEVICE, SOME YOU MIGHT NOT BE ABLE TO RECOVER FROM
Credits for this trick goes to those two threads here and here where I found the technique.
As being said by @Thakur here are the steps to reproduce to enable app pinning.
[email protected] said:
Steps to activate/disable Screen pinning:
- Install Settings Database Editor
- Open App and go to "System Table"
- Find or Create a key (it didn't exist in my case, so I created it) with name "lock_to_app_enabled" and set value "1" (ON) or "0" (OFF)
Tested in miui global beta 9.3.21 and works flawlessly.
Credits: VAGR2018
Click to expand...
Click to collapse
Despite being last updated in 2018 the app Settings Database Editor by 4A, I can confirm this application works flawlessly on my EEA RN8PRO running MIUI 11.0.2.0 PGGEUXM.
The app being a bit similar to like regedit on Windows, dong go mess up with everything or it might end up with cries and tears.
At this point you already have App Pinning enabled. But only this.
If like for me it was enough, you may want to proceed with the next step which will enable screenlock on unpinning.
Assuming I would find the matching setting for that from a phone running stock android, I grabbed my old non MIUI phone and went to dig for the corresponding setting to lock screen when unpinning.
Turns out we can enable lock on unpinning by just adding an other simple value key in the Secure table.
To be allowed to do so, you first need to grant extra permission to app through adb:
It may not be the case for all devices but for my RN8PRO I needed root (su) to apply the adb command.
Code:
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Once permission granted, select Secure table in the Settings Database Editor application , and add the following new key:
Code:
lock_in_app_exit_locked 1
All set, you will now be asked to unlock screen once you unpin pinned app by long pressing back.
Hope this helps.
Regards.

How To Guide Enable 5G NSA on OOS 11 and OOS 11 based Custom ROMs.

Hi there!
OnePlus didn't enable/add 5G in the modem's Carrier Policy files. This is a quick guide on how to enable it.
This guide will work on both OnePlus 9 and OnePlus 9 Pro devices.
Requirements
Root (Magisk)
QPST
Qualcomm drivers installed (EDL ones should do)
Attached .zip file.
USB Cable, of course.
Code:
/*
* Your warranty is now maybe void.
*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or you getting fired because the alarm app failed. Please do some
* research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Got all the things required? Now let's go ahead.
Steps -
1. Root your phone running on OOS 11.
2. Enable USB Debugging
3. Connect your device to your PC in MTP mode and execute the following through cmd
Code:
adb shell
su
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
4. Now open Device Manager to see the connected device. It would be recognized as Unknown if not configured in the past.
5. Right click on the device, select Update Driver -> browse my computer drivers -> Let me pick form a list of available drivers -> click on Have Disk -> show all devices browse then go to the Qualcomm Drivers that you downloaded earlier. Then do the same to the other unknown Driver (if exists). Choose 9018 for both unknown drivers.
6. Open the QPST application. Click on Add new port from the right corner. if it shows 2 add them both. (Skip this step if you already see the ports).
7. Open QPST EFS Explorer and select your device. You should now be able to see your device files.
8. Search for policyman/ directory and enter it.
9. Extract the files in the attached zip. Drag and drop all the files inside the zip to the already open policyman/ directory in QPST EFS Explorer.
10. Overwrite all the files and copy them.
11. Reboot your device
12. Dial *#*#4636#*#*. Select Phone Information -> Set Preferred Network -> Choose NR/LTE/TDSCDMA/CDMA/EvDo/GSM/WCDMA.
PS :- You might need to select preferred network on every reboot in OOS11.
This guide will also work with Custom ROMs. Assuming the Custom ROM already has 5G enabled in the Carrierconfig (Like AOSPA), you can skip step 12 and 13.
These files in policyman/ directory have been taken from OOS 13 (F.20) modem.
Please don't bite on me if this guide doesn't work. I tried it personally on my local carrier in India (Airtel), it is working fine. (AOSPA and also OOS 11).
Cheers if this works for you as well!
Like my work? Buy me a coffee
PayPal
Thank you very much! Will test ASAP.
EDIT: Does anyone know why my device does not show up in Device Manager after setprop in adb shell? Any fix for that?

Categories

Resources