Greetings to everyone here.
I have a Nubia Z7 NX506j and tried to flash it with nubia tool. The flash completed successfully but I lost both my IMEIs. Unfortunately I didn't know that nubia tool keeps a QCN backup and coincidentally formatted my pc. I found a guide about how to hex edit a QCN backup and insert both IMEIs but only for Z7 mini and Z7 max. Can someone please post a working QCN backup of a NX506J and I will make sure to erase the previous IMEIs and insert mine. I will also make sure to post a guide on how I restored it if someone is kind enough to share it.
Thank you!
EDIT: Managed to fix it with the precious help of www.androidbrick.com
Guide coming soon!
Ok, so here goes:
1) First of all you need a qcn backup from a working phone of the same model. I had the luck to ask the owner of www.androidbrick.com to share with me one.
2) You need a hex editor to open the qcn backup
3) Based on these two guides http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/ and http://4pda.ru/forum/index.php?showtopic=596441&st=8180#entry40033587 and adapting them to the qcn i had in my hands, I deleted the IMEIs and MEID from the backup and inserted the ones printed in my phone box
4) Because the IMEIs and MEID on my phone were not "0" but "NULL" i couldn't restore the modified QCN backup, and had to first delete the partitions that hold this kind of information. Based on this guide http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/ i found the partitions (modemst1, modemst2 and fsg) according to the partition table on our device (mmcblk0p10, mmcblk0p11 and mmcblk0p20) accordingly and deleted them with the dd commands found on the above guide (I had to first root the device in order to do that).
5) After i deleted I could successfully restore the QCN backup using QPST (more info on the guide above)
6) Reboot, and voila! The IMEIs and MEID have been restored successfully and phones, calls and mobile data working again!
tassos_chry said:
Ok, so here goes:
1) First of all you need a qcn backup from a working phone of the same model. I had the luck to ask the owner of www.androidbrick.com to share with me one.
2) You need a hex editor to open the qcn backup
3) Based on these two guides http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/ and http://4pda.ru/forum/index.php?showtopic=596441&st=8180#entry40033587 and adapting them to the qcn i had in my hands, I deleted the IMEIs and MEID from the backup and inserted the ones printed in my phone box
4) Because the IMEIs and MEID on my phone were not "0" but "NULL" i couldn't restore the modified QCN backup, and had to first delete the partitions that hold this kind of information. Based on this guide http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/ i found the partitions (modemst1, modemst2 and fsg) according to the partition table on our device (mmcblk0p10, mmcblk0p11 and mmcblk0p20) accordingly and deleted them with the dd commands found on the above guide (I had to first root the device in order to do that).
5) After i deleted I could successfully restore the QCN backup using QPST (more info on the guide above)
6) Reboot, and voila! The IMEIs and MEID have been restored successfully and phones, calls and mobile data working again!
Click to expand...
Click to collapse
My IMEIs are "NULL" so I have to follow your guide.
Can you please tell me the commands for the command window?
This isn't working:
ls -al /dev/block/platform/soc/624000.ufshc/by-name
IceTea7 said:
My IMEIs are "NULL" so I have to follow your guide.
Can you please tell me the commands for the command window?
This isn't working:
ls -al /dev/block/platform/soc/624000.ufshc/by-name
Click to expand...
Click to collapse
Type "ls -al /dev/block/platform/" and according to what appears on the terminal continue to that path until you find the partition table of your device
Sent from my Nexus 5X using Tapatalk
tassos_chry said:
Type "ls -al /dev/block/platform/" and according to what appears on the terminal continue to that path until you find the partition table of your device
Click to expand...
Click to collapse
If I type "ls -al /dev/block/platform/"it shows the following result:
drwxr-xr-x root root 1970-01-08 03:04 msm_sdcc.1
But I don't know what to do next.
If I add soc or the other things of that line the result is that there is no such file.
Then you should type "ls -al /dev/block/platform/msm_sdcc.1" and continue accordingly. But if you lack basic terminal knowledge I highly suggest that you shouldn't go on as you could really mess up your device
Sent from my Nexus 5X using Tapatalk
Yes, I lack of basic knowledge but as long as I don't delete anything, I can't do any damage, right?
But that's the point of the tutorial. To delete the partitions needed in order for your IMEIs to become "0". If you by accident delete the wrong partition, the device could possibly never power on again
Sent from my Nexus 5X using Tapatalk
First I have to find the partitions.
The tutorial is pretty clear to me, so I think I will delete the right things.
---------- Post added at 01:37 PM ---------- Previous post was at 01:23 PM ----------
Just to make things clear.
This is my current situation.
{
"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"
}
IMEI and MEID are NULL but they need to be 0, right?
IceTea7 said:
First I have to find the partitions.
The tutorial is pretty clear to me, so I think I will delete the right things.
---------- Post added at 01:37 PM ---------- Previous post was at 01:23 PM ----------
Just to make things clear.
This is my current situation.
IMEI and MEID are NULL but they need to be 0, right?
Click to expand...
Click to collapse
Yes that's right, I just realized I made a typo in my previous post
I have found the lines and have followed the guide but my Z7 still shows null instead of 0.
I have tried it a second time but no change.
Still null instead of 0.
tassos_chry said:
Yes that's right, I just realized I made a typo in my previous post
Click to expand...
Click to collapse
I'm still not able to set my Z7 into DIAG-Mode. Do yu have any advice for me?
Drivers should be installed correctly.
I have no clue why it's not working.
IceTea7 said:
I'm still not able to set my Z7 into DIAG-Mode. Do yu have any advice for me?
Drivers should be installed correctly.
I have no clue why it's not working.
Click to expand...
Click to collapse
I'm pretty sure the command I told you was right, so I guess it's a driver issue.
What OS are you using? Have you disabled driver signature enforcement, if on Windows 8.1 or 10? If neither of the above help try on another computer with driver signature enforcement disabled
Sent from my Nexus 5X using Tapatalk
tassos_chry said:
I'm pretty sure the command I told you was right, so I guess it's a driver issue.
What OS are you using? Have you disabled driver signature enforcement, if on Windows 8.1 or 10? If neither of the above help try on another computer with driver signature enforcement disabled
Click to expand...
Click to collapse
I'm using Windows 10.
Disabling driver signature is a good hint. I will see if I have disabled it.
tassos_chry said:
I'm pretty sure the command I told you was right, so I guess it's a driver issue.
What OS are you using? Have you disabled driver signature enforcement, if on Windows 8.1 or 10? If neither of the above help try on another computer with driver signature enforcement disabled
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Now I have been finally able to set my Z7 into DIAG mode mode but the QPST tool still doesn't recognize my phone.
Hi, I have the same problem with my nx506j, none of the nubia tools will recover my bricked z7 Max. Could you share the qcn file you received so that I can try your guide?
Many thanks
Ade
Hi .please if anyone can help me with a qcn file backup for a nubia z7. i'l be much obliged Thank you
tassos_chry said:
Ok, so here goes:
1) First of all you need a qcn backup from a working phone of the same model. I had the luck to ask the owner of www.androidbrick.com to share with me one.
2) You need a hex editor to open the qcn backup
3) Based on these two guides http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/ and http://4pda.ru/forum/index.php?showtopic=596441&st=8180#entry40033587 and adapting them to the qcn i had in my hands, I deleted the IMEIs and MEID from the backup and inserted the ones printed in my phone box
4) Because the IMEIs and MEID on my phone were not "0" but "NULL" i couldn't restore the modified QCN backup, and had to first delete the partitions that hold this kind of information. Based on this guide http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/ i found the partitions (modemst1, modemst2 and fsg) according to the partition table on our device (mmcblk0p10, mmcblk0p11 and mmcblk0p20) accordingly and deleted them with the dd commands found on the above guide (I had to first root the device in order to do that).
5) After i deleted I could successfully restore the QCN backup using QPST (more info on the guide above)
6) Reboot, and voila! The IMEIs and MEID have been restored successfully and phones, calls and mobile data working again!
Click to expand...
Click to collapse
Hello,
I know this is an old thread, I have the same the problem as you but my device is Z7 mini, can anyone help to have the qcn file of this model so that I can restore my EMEI. Thanks.
isbou said:
Hello,
I know this is an old thread, I have the same the problem as you but my device is Z7 mini, can anyone help to have the qcn file of this model so that I can restore my EMEI. Thanks.
Click to expand...
Click to collapse
Sorry do not have anymore qcn of these phones. Perhaps you can contact androidbrick.com
Related
I am trying (as recommended) to make an EFS backup of my phone.
I have tried EFS Backup Pro but the version of busybox I have (the one from Play Google: 1.21.0) seem to have an applet missing: readlink.
They ask to downgrade to version 1.20.2 but so far I could not find the APK to do that
How can I downgrade busybox ?
I have also tried the tuto for the GS3 i9305 using QPST but when I dial *#7284# I don't get the Menu "Phone util" so I assume this procedure doesn't work for the Galaxy mega ?
Has anybody managed to save the EFS on the mega ??? If yes how ??
Thanks in advance.
Tilagoon said:
.....................
Has anybody managed to save the EFS on the mega ??? If yes how ??
Click to expand...
Click to collapse
For this we must have root:
I have already a backup efs.img from i9205 made like this THREAD but changed the partition efs to 10 (see the screenshot). This command:
dd if=/dev/block/mmcblk0p10 of=/storage/extSdCard/efs.img bs=4096
If I have some efs issue I will try the restore of it. (I'm not sure if this work. Take care, the responsibility is Your's)
PS: For i9200 You must see if the partition efs is the 10 also.
,
Ok, thanks for your fast answer.
My phone is also a I9205, so I'll try.Anyway there is no risk as long as we don't restore the backup.
Dont know if this will work but if you have root, install root explorer and just copy your efs folder to an ext SD card?
or am i thinking too simple about this?
SquirtingCherry said:
Dont know if this will work but if you have root, install root explorer and just copy your efs folder to an ext SD card?
or am i thinking too simple about this?
Click to expand...
Click to collapse
Yes, I confirm this work. I restored the efs twice whit Root Explorer on Galaxy Tab 7" P1000 and one on Note 10.1 N8000.
But we must verify the permissions, I compared whit another device. Can be some issues whit.
I had a look with root explorer and there is nothing after the permissions (rwxrwx) , no -> and no file name.
This is valid for all the directories in the root directories.
By the way the name I don't have the same directories as you ??
How did you get that ? Which file explorer ??
Root Explorer, now 2.21.1 version from Speed Software. On top we must put on R/W to see or change permissions.
For exemple: long touch on efs folder, on next window we have permissions. Touch on permissions, we see it on a new little window.
We can verify, change... or ok/cancel.
I am using Root explorer 3.and this is what I can see:
{
"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"
}
Doesn' really look like what you get !!
PS: Sorry but I did find yet how to put a miniature un the post
Tilagoon said:
I am using Root explorer 3.and this is what I can see:
................................................
Doesn' really look like what you get !!
PS: Sorry but I did find yet how to put a miniature un the post
Click to expand...
Click to collapse
Good, is the new version 3 and You are already on r/w. Now make this:
Long touch on efs folder until you have a new window whit many options (attach1), also permissions (Permissões in Portuguese).
Touch on permissions, we see it on a new little window (attach2). This mean rwxrwx--x = 7,7,1 (my case).
Your is rwxrwxrwx = 7,7,7
(r=Leitura, w=Gravação, x=Executar)
We can verify, change... or ok/cancel.
See attachs:
PS: On version 3 You can mark efs at right and touch on menu. Is same.
Valente
Yes, I have done that already and changed the last part of the permission to rwx (was--x) as you can see in may capture.
But still no indication like yours: -> mmcblk0p10 !!
And as you can see also my root directory is different from yours????
Tilagoon said:
And as you can see also my root directory is different from yours????
Click to expand...
Click to collapse
Because I prefer the Root Explorer old version 2.21.1 and invalidate the update of it on Play Store.
Updated now to vers 3 to test to You but I returned to old version. I like it more.
Ok, I'll try with the same version as yours and see what I get.
But my concern was that the name of the directories in my capture and yours are quite different and I don't think that the other version of Root explorer wil change anything.
I have installed version 2.21.1 and I get the same thing !
But I think I have finally understood what's going on: your first capture is not the capture of the Root directory as what we see are not sub-directories but files !!
Can you tell me the path to get that ??
Tilagoon said:
I have installed version 2.21.1 and I get the same thing !
But I think I have finally understood what's going on: your first capture is not the capture of the Root directory as what we see are not sub-directories but files !!
Can you tell me the path to get that ??
Click to expand...
Click to collapse
Like I wrote. Long touch on efs folder, You have like my first screenshot whit options (Opções in Portuguese).
ValenteL said:
Like I wrote. Long touch on efs folder, You have like my first screenshot whit options (Opções in Portuguese).
Click to expand...
Click to collapse
I must be stupid but I can' get what I want which is show in the attachment below.
I have all the steps: mount R/W, long touch on EFS, then I get the options menu and if I go in permissions I can change them but when I say OK I return to the contents of the root directory.
I have tried to change the permissions but no way. I really don't see what more can be done to get this information.
I think I'll give up and will no longer bother you.
Any way thank you very much for your help and having be so patient.
Tilagoon said:
I must be stupid but I can' get what I want which is show in the attachment below.
I have all the steps: mount R/W, long touch on EFS, then I get the options menu and if I go in permissions I can change them but when I say OK I return to the contents of the root directory.
I have tried to change the permissions but no way. I really don't see what more can be done to get this information.
I think I'll give up and will no longer bother you.
Any way thank you very much for your help and having be so patient.
Click to expand...
Click to collapse
Take care, is not there, this is not the root directory. Is on Your screen post 8 on root you see efs folder. Is here You must try long touch... etc, my screens post 9.
This screen in this Your post is from /dev/block/platform/msm_sdcc.1/by-name/partitions, is not the root directory, the efs here is not a folder is a partition.
PS: Attach root directory whit efs folder, not file.
ValenteL said:
Take care, is not there, this is not the root directory. Is on Your screen post 8 on root you see efs folder. Is here You must try long touch... etc, my screens post 9.
This screen in this post is from /dev/block/platform/msm_sdcc.1/by-name/partitions, is not the root directory, the efs here is not a folder is a partition.
Click to expand...
Click to collapse
Thanks a lot !! I almost kill my self to find this.Now I have it (of course) :victory::victory::laugh:
I will do the save.
Tilagoon said:
Thanks a lot !! I almost kill my self to find this.Now I have it (of course) :victory::victory::laugh:
I will do the save.
Click to expand...
Click to collapse
:laugh::laugh::laugh::victory::victory:
[IMPORTANT] HOW TO DO EFS BACKUP AND RESTORE FOR GT-I8552
I Got PM Very Long Ago For Way To Backup Of "EFS" But In Last Two Weeks I Started Getting Request Again So Here Is The Simple Way I Wanna Share "How To Backup "EFS" For GT-I8552
As There Is No CWM For Our Device That Supports "EFS" Backup And Also Third Party Apps Ain't Working Now What To Do
So Here We Go Then :-
Q :- What is "EFS" ?
A :- "EFS" Folder Is The Very Sensitive System Folder That Contains Phone-Specific Information Such As The IMEI, Wireless Devices MAC Addresses, Product Code, And Much More. If This Thing Not Handled Properly, Can Turn Your Device Completely Useless As It Will No Longer Be Recognized By Your Carrier.
Problem Is, Flashing Custom ROMs Sometime Can Corrupt Contains Within "EFS" Folder. That’s Why Backing Up "EFS" Folder Is Very Important If You Love To Flash New ROM.
NOTE :- ROOT IS REQUIRED..!!
INSTRUCTIONS :-
EFS BACKUP
1. Download Android Terminal Emulator Or Download ROM Toolbox Pro Or ROM Toolbox Lite.
2. Open Terminal Emulator Or Terminal Emulator In ROM Toolbox App.
3. Use This Code To Backup "EFS"
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/efs.img
And hit Enter In Keyboard..
4. You Will Get efs.img In Your SDCard, Copy It To PC Or Upload On Storage Sites Like 4shared.com , Mediafire.com etc
EFS RESTORE
1. Download Android Terminal Emulator Or Download ROM Toolbox Pro Or ROM Toolbox Lite.
2. Open Terminal Emulator Or Terminal Emulator In ROM Toolbox App.
3. Use This Code To Restore "EFS"
Code:
su
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p16
And hit Enter In Keyboard..
4. Guess What You Restored Your "EFS"
Please Hit "THANKS" or "DONATE" To Support.
bro did u try restoring ? r u sure it restore successfully?
tonyjs007 said:
bro did u try restoring ? r u sure it restore successfully?
Click to expand...
Click to collapse
Yes buddy it will restore u need root access for that thats all :good:
I already flashed jasp hd Rom before backing up efs partition now what should I do
ZANKRUT.DOSHI said:
I already flashed jasp hd Rom before backing up efs partition now what should I do
Click to expand...
Click to collapse
Np u can backup now efs.img just in case
We have to put backup of efs (.img file in internal storage or external while restoring it?? :|
Sent from my GT-I8552 using XDA Premium 4 mobile app
Jaspreet_Singh said:
Yes buddy it will restore u need root access for that thats all :good:
Click to expand...
Click to collapse
Bro did u restore it by this way? And can u tell me which information stored on mmcblk0p3 ?
Sent from my GT-I8552 using Tapatalk
kinchit1495 said:
We have to put backup of efs (.img file in internal storage or external while restoring it?? :|
Sent from my GT-I8552 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
internal as above command is for internal only
coolkoushik07 said:
Bro did u restore it by this way? And can u tell me which information stored on mmcblk0p3 ?
Sent from my GT-I8552 using Tapatalk
Click to expand...
Click to collapse
yes its working and p3 is for modem for our device..
Jaspreet_Singh said:
internal as above command is for internal only
yes its working and p3 is for modem for our device..
Click to expand...
Click to collapse
Ur given command is wrong. There is no sdcard directory, it would be sdcard0 or extSdCard. By the way can u tell me what is the work of bs command. Somewhere i saw people use bs=4096 while using dd command. Can u please explain it?
{
"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"
}
Sent from my GT-I8552 using Tapatalk
---------- Post added at 08:42 PM ---------- Previous post was at 07:53 PM ----------
Edit : my bad. Ur code is working too. I did a mistake by /storage/sdcard/ so it gave error. So ignore that part. But if u can please explain bs parameter.
Sent from my GT-I8552 using Tapatalk
I think it ws wrong it should be sdcard0
Sent from my GT-I8552 using XDA Premium 4 mobile app
kinchit1495 said:
I think it ws wrong it should be sdcard0
Sent from my GT-I8552 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. mine works fine, the output should be efs.img
I think bs stands for block size. But can anyone explain what it does?
Sent from my GT-I8552 using Tapatalk
thnxs bro for great in gt-i8552
Gt-i8552 rocksss!!!
coolkoushik07 said:
Ur given command is wrong. There is no sdcard directory, it would be sdcard0 or extSdCard. By the way can u tell me what is the work of bs command. Somewhere i saw people use bs=4096 while using dd command. Can u please explain it?
Sent from my GT-I8552 using Tapatalk
---------- Post added at 08:42 PM ---------- Previous post was at 07:53 PM ----------
Edit : my bad. Ur code is working too. I did a mistake by /storage/sdcard/ so it gave error. So ignore that part. But if u can please explain bs parameter.
Sent from my GT-I8552 using Tapatalk
Click to expand...
Click to collapse
The /sdcard/ *should* be universal on many samsung devices (at least I know it IS like that on the Galaxy Ace and on the Galaxy Win, i8550L that I own).
Regarding the bs operand of the dd command, in this case you don't need it, as you're acting directly over the EFS partition. In the use of this command the bs operand is used for when you're working with a whole disk.
Technical stuff below:
For example, if you don't have the precise /dev/block/mmcblk0pXXX of a partition (taking in consideration that /dev/block/mmcblk0 is the disk you want to read from), you can use dd in this way:
Code:
dd if=/dev/block/mmcblk0 bs=4096 of=/sdcard/kernel.img
In the example, we're backing up the Kernel part of the phone (note that this is not real information, just an example, so don't blame me if you try to dump that command back in the phone assuming things you don't know xD), as you may (or may not) know, a disk is comprised of many blocks, you can google about that later it's quite late and don't wanna go on too deep so i'll try to be brief; if your disk is 512 mb in size, probably the first 32MB would be for boot, kernel, recovery, modem and NVRAM (not to be confused with modem), these 32 MB might be distributed this way:
1-1024MB Bootloader
1024-6144 Kernel+Recovery
6144-18432 Modem
18432-32768 NVRAM
and so on
Long story short, don't mess with DD
Backing Up EFS Partition
Dear Jaspreet,
Myself and CoolKoushik07 tested this procedure long before. However this is not working solution. This is due to the natture of the EFS filesystem.
Please go through my Post # 39,40,41,42,43,44.
http://forum.xda-developers.com/showthread.php?t=2541198&page=5
Please correct me if I am wrong.
Regards
Arinio said:
Dear Jaspreet,
Myself and CoolKoushik07 tested this procedure long before. However this is not working solution. This is due to the natture of the EFS filesystem.
Please go through my Post # 39,40,41,42,43,44.
http://forum.xda-developers.com/showthread.php?t=2541198&page=5
Please correct me if I am wrong.
Regards
Click to expand...
Click to collapse
Check ur command "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img"
and mine "dd if=/dev/block/mmcblk0p16 of=/sdcard/efs.img"
Two mistakes ? first is our mounting point for efs is mmcblk0p16 and there is no storage "of=/storage/extSdCard/efs.img" it shud be either to sdcard directly or of=/extSdCard/efs.img
Jaspreet_Singh said:
Check ur command "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img"
and mine "dd if=/dev/block/mmcblk0p16 of=/sdcard/efs.img"
Two mistakes ? first is our mounting point for efs is mmcblk0p16 and there is no storage "of=/storage/extSdCard/efs.img" it shud be either to sdcard directly or of=/extSdCard/efs.img
Click to expand...
Click to collapse
Just a lil correction.. /storage/extSdCard/ is not wrong directory..
Sent from my GT-I8552 using Tapatalk
Backing Up EFS Partition
Dear Jaspreet,
Please check my Post #43.
Regards
Jaspreet_Singh said:
[IMPORTANT] HOW TO DO EFS BACKUP AND RESTORE FOR GT-I8552
Click to expand...
Click to collapse
hello @Jaspreet_Singh
Im forget to make a backup by my efs folder I8552 again after formated my PC.
Now its empyt cause i had troubles flashing test by custom rom
Important
Except the stock lockscreen and stock setupwizard inicial everything works even empty folder cause I managed to recreate the mac adress, retrieve the IMEI
3G signal ok
calls Ok
IMEI ok
IP/Wi fi ok
Is it something can u do , like send files folders attachment and i using sdk put my mac adress, ip and imei to restore files?
tks
@mjraogr....
Add facebook.
https://m.facebook.com/GlaMsP?ref=bookmark
I also had the same problem, I was looking for solutions to this problem and in one of these search found an EFS file from another machine and tried their luck to restore my folder ..
Following the steps in this link posted by @manojkumar8552 my work out and now is working perfectly.
Download these files, extract the desktop.
https://drive.google.com/file/d/0B6t2vRswL0dHVXRKYXZncGd1WVU/view?usp=sharing
1 - run the Backup_EFS ...
2 - Once completed Backup your EFS.img, rename such as EFS MY or something.
3 - Inside the folder contains another file (efs Restore.img) change the name to EFS.img.
4 - Run the Restore_EFS ...
5 - Restart the device ...
6 - Enter the ROOT folder with Explorer, find the EFS / Factoryapp folder, edit the file (factorymode) will contain OFF switch to ON all upper case, reset the unit ....
Good luck ... these steps have worked in the mine, hope it helps ...
NOT TO THANK !!
[Q&A] [TOOL] Updated! 26/06/14 - EFS Professional v2.1.73 - Also for NON-Samsung dev
Q&A for [TOOL] Updated! 26/06/14 - EFS Professional v2.1.73 - Also for NON-Samsung devices!
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 [TOOL] Updated! 26/06/14 - EFS Professional v2.1.73 - Also for NON-Samsung devices!. 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!
{
"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"
}
Help please
MOTO G XT1033 IMEI issues and EFS Prof
Does EFS Professional supports Moto G XT1033 model? I erased partition with IMEI. Whether it is possible to make a new one or clone existing one from another phone using this software? Thank you!
Downloaded this and I can't open "ESF Professional" it pops up "Error reading App. Config file."
Lyriquidperfection,
I am trying to use EFS Professional v2.1.73 on a rooted Samsung Galaxy S II (SGH-T989) "Hercules" running the stock UVMC6 4.1.2 JellyBean. EFS Professional starts up fine, but as soon as I try anything requiring file system access I get an error:
Code:
Number was less than the array's lower bound in the first dimension. Parameter name: srcIndex
And on the log screen it says:
Code:
Checking PIT file integrity...
Operation failed!"
The pit file that is generated by EFS Professional is 1024KB in size, but looking at it in a hex editor most of that is just forward and trailing '0's. I also did a manual dump by:
Code:
dd if=/dev/block/mmcblk0 of=SGH-T989-JB.pit bs=8 count=131072
Quickly comparing the two I do not see any differences in the file, and the md5sum is the same, so I have high confidence that EFS Professional is getting the right data. It just seems like Samsung may have made significant changes to the format of the pit data when they released JB.
I've attached the pit file that EFS Professional extracted. Any insights?
Rob
samsung galaxy s4 mini gt-i9195 damged imei
I have a samsung galaxy s4 mini gt-i9195 with stock rom rooted with android 4.4.2. The imei is damged lost en shows /01. I read a thread that i could restore/repair imei with efs professional. I connected the device was able to detect/read al partitions. When i try to make a backup of block 11 and 12 with modem tag I get an error ... backup failed tar.gz . I have a sd card in the phone and also use *#0808# to put the phone in adb+modem+dm. I did that because i thought that when te phone is connected in MTP mode maybe acces to the sd card was minimal. I also tried ptp mode but i keep getting the same error.
Can any one help?
thanks for share
thanks for share
thank you
thak
I am new user so pls help
Can I backup my moto g 2nd gen(xt1068) EFS with it or I need terminal emulater command pls help sir thanks in advance and subscribed..
asdfsdf
sdfsd
---------- Post added at 10:11 AM ---------- Previous post was at 10:04 AM ----------
ecause you have less than 10 posts, the developer of this thread has opted to have replies go to a separate questions and answers thread. Placing your question within the Q&A thread will increase its chances of being answered by a member of the community or by the developer. Once you have more than 10 posts, you can post anywhere.
Teşekkürle
Çok güzelk uyguulama
How to write imei to m919
What I have to do to write new IMEI for S4 M919?
Checkbox (IMEI) must be checked, new Imei Entered - hit button "Write"
But IMEI was not updated... Its this working?
thanks my friiend
Hello
Iam trying to backup my T-599N, but constantly getting error
Unable to backup selected partition
dd: cant open /extSdCard/EFSProBackup/temp/efs.img no such file or directory
exictode=1
The process of backup stops on the line
Checking device connection... Device is connected!
Checking backup folder location... Okay.
Backing up selected partition(s)...
efs - read: /dev/block/mmcblk0p9 - write: efs.img...
Operation failed!
the error follows in pop up box...iam using right extSdCard as device storage option, i also manualy created folder EFSProBackup/temp on my card, but still no luck does anyone know what it may be caused by?
Thank you
can i backup s2hd lte (shv e120k)?
thk
thk
for Samsung Galaxy S III [I9300]
It is working on S III GT-I9300?
because i want to backup my EFS/IMEI.
Sm-t705 - imei 004999010640000
Hi,
My Tab S 8.4 SM-T705 is running on Exnoys, after flashing my rom, the IMEI became a dummy.
I do have my IMEI number though I dint back-up the file.
I have tried using the EFS pro but it seems not to work, not sure if i had done it incorrectly?
would really appreciate if can help me out.
Android system recovery <3e>
Backup has been created successfully (see attached screenshots) on running system - Galaxy Note 3 N9005, KK 4.4.2, knox 0x0. Great!
But, EFS Pro does not work in the stock recovery. I have tried a workaround from post #2035:
"Boot your phone normally, start EFS Pro, refresh the partitions, then manually reboot the phone into recovery, then proceed with backup."
After reboot (powered off and started in system recovery), backup operation failed. EFS (and windows 7 too) does not recognize that Note 3 is connected to PC. Windows is able to communicate with device only via adb sideload after selecting in recovery "apply update from ADB".
My questions are
1. Is any chance to get EFS Pro working in stock recovery?
2. How safe to backup and restore(!) partitions on running system?
3. Is it a good idea to use EFS Pro for backup/restore system and data partitions? I am missing an option (in stock recovery) to make nandroid backup very much and creation of update.zip for adb sideload is too complicated for me.
There is also a posibility to write imei's for DUAL sim qualcomm phones?
---------- Post added at 05:25 PM ---------- Previous post was at 05:08 PM ----------
There is also a posibility to write imei's for DUAL sim qualcomm phones?
Hello,
I've been trying to return my CC HAM2 to Huawei Stock HAM2 and according to one user, I need two files; oeminfo partition file and custom.bin from someone with the Huawei Stock HAM2 (not the CC variant) that is rooted. Here are the steps you can use to get these files:
1. oeminfo partition
Connect your device to PC and backup your oeminfo partition with these commands:
Code:
Code:
adb shell su -c "dd if=/dev/block/platform/<device>/by-name/oeminfo of=/sdcard/oeminfo"
adb pull /sdcard/oeminfo oeminfo
adb rm -f /sdcard/oeminfo
Execute them from ADB folder. It's three commands, run them separately. Don't forget to replace <device> with your existing folder.
Now you should get oeminfo file in ADB folder. Check it, if OK, then save it somewhere else.
2. Custom.bin
This file can be located at: /data/custom.bin
medwatt said:
Hello,
I've been trying to return my CC HAM2 to Huawei Stock HAM2 and according to one user, I need two files; oeminfo partition file and custom.bin from someone with the Huawei Stock HAM2 (not the CC variant) that is rooted. Here are the steps you can use to get these files:
1. oeminfo partition
Connect your device to PC and backup your oeminfo partition with these commands:
Code:
Code:
adb shell su -c "dd if=/dev/block/platform//by-name/oeminfo of=/sdcard/oeminfo"
adb pull /sdcard/oeminfo oeminfo
adb rm -f /sdcard/oeminfo
Execute them from ADB folder. It's three commands, run them separately. Don't forget to replace with your existing folder.
Now you should get oeminfo file in ADB folder. Check it, if OK, then save it somewhere else.
2. Custom.bin
This file can be located at: /data/custom.bin
Click to expand...
Click to collapse
I think the OEMInfo Partition (mmcblk0p8, size 67,108,864) contains IMEI and SN info, it is not worth the risk to mess up with them.
Thanks for your reply. I don't really know that much about the internal make up of android devices, so maybe that's why I asked requested that file. I was told by a user [Kostyan_nsk] in one of the threads I created asking how to flash the stock HAM2 OEM over the CC version and the guy said I need the OEMINFO file from someone with a stock phone (not CC). I really had no idea why but in his procedure, getting the OEMINFO file was essential to the process. Now, I wonder how I can get of the CC version !!!!
xordos said:
I think the OEMInfo Partition (mmcblk0p8, size 67,108,864) contains IMEI and SN info, it is not worth the risk to mess up with them.
Click to expand...
Click to collapse
I was replacing whole partition from other device, but my IMEI and SN stayed the same. So it's not in there.
Well, may be in your device its size is 64MB if you are not confused blocks. In mine it's mmcblk0p9 and has 32MB size.
Kostyan_nsk said:
I was replacing whole partition from other device, but my IMEI and SN stayed the same. So it's in there.
Well, may be in your device its size is 64MB if you are not confused blocks. In mine it's mmcblk0p9 and has 32MB size.
Click to expand...
Click to collapse
Its 64MB. Pooffff goes flashing the stock rom !
Let me know about your result.
Kostyan_nsk said:
Let me know about your result.
Click to expand...
Click to collapse
Result ? I don't have the oeminfo file.
xordos said:
I think the OEMInfo Partition (mmcblk0p8, size 67,108,864) contains IMEI and SN info, it is not worth the risk to mess up with them.
Click to expand...
Click to collapse
I always thought it was stored in the phone hardware.
medwatt said:
Result ? I don't have the oeminfo file.
Click to expand...
Click to collapse
Still nobody responded to your request?
Strange. There's no any personal information to be afraid to reveal.
Still kinds of worried because I have seen mixed answered about the OEMInfo partition has sensitive info or not.
My MT2L03 unlocked OEMInfo image:
ls -l : 67108864 Oct 9 00:45 mmcblk0p8.img
md5sum: d9c1a0287bb94b7b0d5d83e0________ mmcblk0p8.img
I have masked the last 8 digit of my md5, if anyone else can confirm the md5sum is same as mine, I will share the image.
Sorry if this looks too much. I just want to be super careful that my phone IMEI/SN will not got flashed to other phone, and maybe lots of phones if it got published.
This is the post that I got scared of:
http://www.modaco.com/topic/362644-is-there-a-way-to-copy-an-officially-unlocked-ics-bootloader/
"The only way to do what you are asking is to use the oeminfo partition from another phone that has unlocked bootloader, and that will make you lose your imei number after installing an update.app."
So, it is possible you may not see any problem right away after flashing, but only found your IMEI lost after an update which maybe months later.
So, anyone can check your vanilla MT2L03 md5sum of the mmcblk0p8.img, please confirm.
Well, and according to this post about successfull backup and restore of IMEI, it seems to be in 'nvme' partition.
And I was not lost my imei after flashing update.app with replaced from other device oeminfo partition.
I'm just curious where was it started from that imei is in oeminfo?
In addition: I have found Board ID, SN, MAC WLAN, MAC Bluetooth, Bootloader unlock code, but IMEI still not found.
I'm starting to think it's stored in hardware and cannot be changed. Seems like it was stored in partition in previous, early devices, but now it's not.
medwatt said:
Hello,
...
1. oeminfo partition
Connect your device to PC and backup your oeminfo partition with these commands:
Code:
Code:
adb shell su -c "dd if=/dev/block/platform/<device>/by-name/oeminfo of=/sdcard/oeminfo"
...
...
Click to expand...
Click to collapse
Code:
C:\Users\User>adb devices
List of devices attached
9cc1722xxxxx device
C:\Users\User>adb shell su -c "dd if=/dev/block/platform/9cc1722xxxxx/by-name/oe
minfo of=/sdcard/oeminfo"
/dev/block/platform/9cc1722xxxxx/by-name/oeminfo: cannot open for read: No such
file or directory
C:\Users\User>
I masked my serial number but that's what I get when I run that.
arcadesdude said:
Code:
I masked my serial number but that's what I get when I run that.[/QUOTE]
The by-device field is a folder name - not your serial number. Its one of the folders in /dev/block/platform/. For example, in my CC variant it is: msm_sdcc.1
It might be the same for your phone. In fact if you have root explorer or some other software just enter /dev/block/platform/<device>/by-name/ and you can copy the oeminfo file without the need for adb. Try it.
Click to expand...
Click to collapse
xordos said:
Still kinds of worried because I have seen mixed answered about the OEMInfo partition has sensitive info or not.
My MT2L03 unlocked OEMInfo image:
ls -l : 67108864 Oct 9 00:45 mmcblk0p8.img
md5sum: d9c1a0287bb94b7b0d5d83e0________ mmcblk0p8.img
I have masked the last 8 digit of my md5, if anyone else can confirm the md5sum is same as mine, I will share the image.
...
Click to expand...
Click to collapse
Used root explorer to copy the files and hashmyfiles to generate the md5:
{
"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"
}
Looks quite different.
By the way, I have found where IMEI is.
So now I can confidently declare that it's not in OEMInfo.
Kostyan_nsk said:
By the way, I have found where IMEI is.
So now I can confidently declare that it's not in OEMInfo.
Click to expand...
Click to collapse
Hey, what phone do you have? I see in the other thread the cc to oem instructions step 1 is get full oem update.app, but I dont think mt2l03 have this.
---------- Post added at 08:06 AM ---------- Previous post was at 07:57 AM ----------
arcadesdude said:
Used root explorer to copy the files and hashmyfiles to generate the md5:
Looks quite different.
Click to expand...
Click to collapse
Can you list the file size as well, I am confused you have oeminfo and p8 different, these two suppose is same thing.
xordos said:
Hey, what phone do you have? I see in the other thread the cc to oem instructions step 1 is get full oem update.app, but I dont think mt2l03 have this.
---------- Post added at 08:06 AM ---------- Previous post was at 07:57 AM ----------
Can you list the file size as well, I am confused you have oeminfo and p8 different, these two suppose is same thing.
Click to expand...
Click to collapse
PHONE:
I have the stock carrier unlocked MT2-L03 from Amazon/Huawei.
SIZE:
12/30/2014 11:48 PM 67,108,864 oeminfo 1 File(s) 67,108,864 bytes
12/30/2014 11:48 PM 67,108,864 mmcblk0p8 1 File(s) 67,108,864 bytes
(64mb)
COMPARED:
I used UltraCompare Lite on the files in binary mode...they are exactly the same except for the names. The contents are identical.
MD5:
I'm not sure why they seemed different before. Maybe a copy error.
arcadesdude said:
PHONE:
I have the stock carrier unlocked MT2-L03 from Amazon/Huawei.
SIZE:
12/30/2014 11:48 PM 67,108,864 oeminfo 1 File(s) 67,108,864 bytes
12/30/2014 11:48 PM 67,108,864 mmcblk0p8 1 File(s) 67,108,864 bytes
(64mb)
COMPARED:
I used UltraCompare Lite on the files in binary mode...they are exactly the same except for the names. The contents are identical.
I'm not sure why they seemed different before. Maybe a copy error.
Click to expand...
Click to collapse
Thanks, actually, Today I tried to fetch the OEM info again, it changes, maybe because one is before update, the newer one is after, but still it is not matching with yours.
819ee97207511c78f1a46dfb________ oeminfo_1231.img
Anyway, read some where that the OEMInfo pretty much is a data storage partition, that it stores different regions/carrier info/settings of the phone. So, how many unique info is stored here, I am not sure, maybe IMEI is not here, but if other MT2L03 image is not same as mine, I am not comfortable to share mine. Sorry.
xordos said:
Hey, what phone do you have? I see in the other thread the cc to oem instructions step 1 is get full oem update.app, but I dont think mt2l03 have this.
Click to expand...
Click to collapse
Well, if there is no full UPDATE.APP for MT2-L03, then the idea of replacing oeminfo is useless.
xordos said:
Thanks, actually, Today I tried to fetch the OEM info again, it changes, maybe because one is before update, the newer one is after, but still it is not matching with yours.
819ee97207511c78f1a46dfb________ oeminfo_1231.img
Anyway, read some where that the OEMInfo pretty much is a data storage partition, that it stores different regions/carrier info/settings of the phone. So, how many unique info is stored here, I am not sure, maybe IMEI is not here, but if other MT2L03 image is not same as mine, I am not comfortable to share mine. Sorry.
Click to expand...
Click to collapse
Yeah I'm not willing either if there is personal info there it's not good to clone that.
Sent from my MT2L03 using Tapatalk
IMEI (EFS) BAckup Tool Note 5
{
"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"
}
This is simple EFS backup tool. We are very well knowing about what EFS is and why it is MUST to backup on every rooted device. If you don't know then Read this.
You needs root access to use this tool otherwise app won't open..
Location of stored file :
Device storage/MyEFS
If you unable to see backup, contact me with details of your device variant
Download :
Pro Version
XDA version (free)- Attached at end of this post.
Difference between Free/Play store
-Both version makes backup in same format and no difference in backup.
-Pro version have option to Restore with single click
-Free version will save file in MyEFS and if you make next backup it will replace older one. While play store version everytime creates new folder with date ,Time and your IMEI stamp so you can keep multiple backup as well no confulsion about which backup is made when and on which device. Also it makes copy of build.prop so you can get idea you were on which ROM when backup created)
-Play store version give notification in case backup not created.
-Weekly Auto backup feature available on play store version.
-PIT creator. Play store V1.1 added option to create PIT file from existing layout
Click to expand...
Click to collapse
This tool using generic name of partition block and you can restore with simple adb shell
dd if=/path of backup files/ of=/partition block according your device
ChangeLog
1.0 - Initial release. (3644)
1.1 - Fixed for systemless root users.
What is EFS
This part of the device contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code (also in the nv_data.bin) and the very main IMEI address (nv_data.bin), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things. So you can guess it's will be different for each device and one can't use others. In latest samsung device this information store in other partition so requires to make backup of that partition too.
How it can corrupt :
- Any bad flashing, mishandling system modification can cause this.
- Also It can be corrupted by downgrading stock ROM. If you flash any old ROM on newer ROM it can corrupt EFS. Basically newer ROM believed to have new kernel that changes EFS data which older Modems can't read and results to fail in reading IMEI.
Impact on device/How I know I have corrupted EFS
When there is EFS partition is corrupted, device loses IMEI and due to this device can't gets connected to network. Baseband info also sometimes shows unknown.
-Check your IMEI in setting / by dialling *#06# if it is null OR if it starts with 0049** then IMEI is generic and corrupted. In Normal case IMEI which you can see in device setting or dialing *#06# is exactly same you can see on bill/box/sticker under battery compartment
-If you are unable to connect to network in spite of correct IMEI, chance are
A. Your device is Locked to specific Network OR
B. Your device is banned due to tempered IMEI
-If your AP,CP,CSC all are correct and even you are getting error (unknown CSC XXX) on kies update, it may be due to corrupt Product code in EFS. Read This for detail.
What care should i take
Before flashing anything, first thing you should do is to make EFS backup. Every person who have rooted device should make EFS backup earliest and place it to safer place on PC and /Cloud.
If you are on older ROM, make EFS backup on older ROM as well make another after upgrading ROM too.
If you have already updated to newer ROM, make backup on current ROM.
Exit "Permanent Safe Mode" This condition represent with loss of IMEI + yellow text box on homescreen with device info.here is Screenshot
Here is different method to remove it.
Method1 :
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:
Code:
OFF
To:
Code:
ON
Reboot device.
Method2:
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
Method3
Install attached safemode_exit apk as regular app. Open from drawer - Grant su permission - Reboot when asked.
e:failed to mount /efs(invalid argument) error with bootloop
This condition usually happens with using unsupported tool (usually from play store).
To recover this, needs to use adb shell
Code:
adb shell
mke2fs / dev/block/mmcblk0p[COLOR="Red"]x[/COLOR]
mount-w-t ext4 / dev/block/mmcblk0p[COLOR="red"]x[/COLOR] / efs
x means your device EFS partition number
PS : It needs CWM and busybox installed.
Reserved 3
Reserved 4
Reserved 5
Thank you
Sent from my SM-N920T using Tapatalk
Yet another useful contribution
Thanks
Nothing happens when i try to launch the app. Is that normal, or should there be a GUI? Also tried pro version.
Sent from my SM-N920T using Tapatalk
daftlush said:
Nothing happens when i try to launch the app. Is that normal, or should there be a GUI? Also tried pro version.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Are you sure you have rooted device? As said in op it won't open without root access.
Sent from my SM-N920I using xda premium
dr.ketan said:
Are you sure you have rooted device? As said in op it won't open without root access.
Sent from my SM-N920I using xda premium
Click to expand...
Click to collapse
ohh yeah. root is 100%.
Sent from my SM-N920T using Tapatalk
daftlush said:
ohh yeah. root is 100%.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Which is your device model ?
Reinstall and click on app icon and wait till it ask for supersu. Once you grant permission then only app will show ui
Sent from my SM-N920I using xda premium
dr.ketan said:
Which is your device model ?
Reinstall and click on app icon and wait till it ask for supersu. Once you grant permission then only app will show ui
Sent from my SM-N920I using xda premium
Click to expand...
Click to collapse
t-mo. rooted. su set to auto allow.
Sent from my SM-N920T using Tapatalk
Check Super su log and see it has granted su permission to app.
i have no baseband and imei unknown after updating to latest tmo firmware and installing DarthStalker. Have backup from when i first rooted phone. will purchasing your app fix you think?
do i need to downgrade to old firmware and restore?
many thanks for all your hardwork for the community,!
Try Restoring directly if doesn't work then flash same firmware on which you made backup. If any issue or doesn't work pm me.
Before doing anything make copy of backup on multiple storage.
Sent from my SM-N920G using xda premium
Thank you so much for all the help. I am now back up and running. You are awesome ,sir.!
Got it to work. How do i find out what to type in promt to restore?
Sent from my SM-N920T using Tapatalk
nice tool, but how to restore a backup ?
nmx87 said:
nice tool, but how to restore a backup ?
Click to expand...
Click to collapse
the same question
Guys it's in the OP...use Terminal Emulator with the commands in the OP. .