Hi all,
I have a big problem right now with my SIII....
I lost my gsm signal twice by using cleaning kernel script by mistake belongs to Galaxy note N7000, I have backup ESF folder and I'm restoring it in each time I lost my signal, for my surprise I lost my lock screen and it's not activating (not showing) and when I left the power button pushed to get the menu of power, airplane mode and reboot the phone power off, then I went back to Recovery Mode, wipe the dalvik, the cache reboot it and nothing... I formated everything and followed some steps how to recover the lock screen back with nothing happened like these commands throw ADB shell:
- type into the command:
su
echo -n ON > /efs/imei/keystr
sync
and I made the file keystr manually with command ON with no result.
And I checked setupwizard.apk in my system folder and still there, I have flashed stock rom since I'm on Omega v12.
Also, when I boot up my device with wifi On I'm facing Factory mode ON and disables the wifi but I can activate it back with no issue.
I have followed this thread for Factory mode ON with no result:
[Q]How exit FACTORY MODE ???
I have tried everything I could and found on google search and still I have the issue.
I flashed [Rom]GT-I9300 Resurrection Remix JB v3.0.3[10/08][AOKP JB PRE](AROMA+OTA)
and the issue disappeared, lockscreen activated and power button functioning as it should be, with jelly bean
rom my problem no more there but with ISC roms failed again. Also, I made double check on hidden feature
which called shutdown.app by typing in dialer *#7594# code and it's unchecked.
So, any suggestions ?
Edit: Btw, sorry for my bad English.
Have you try format system partition before flashing stock rom?
Sent from my GT-I9300 using xda app-developers app
Formatting system will most probably solve the issue. I would recommend doing that whenever you are switching between different android systems as it is always cleaner
Formatting system or anything else will not solve your issue. It is causes by a problem in your efs folder. This happened to alot of people on the S2 when upgrading to ICS, including myself. Took me months to finally figure it out.
Anyway, first step. Using root explorer or similar, navigate to your efs folder, then the factoryapp folder. In there check if you have these 2 files - factorymode & keystr.
If they are there click on them and open in text viewer. In both you should see the words 'ON'. If not, reopen in text editor and key those word in, in capital letters then save.
Try this and report back.
Sent from my GT-I9300 using xda premium
Arsaw said:
Have you try format system partition before flashing stock rom?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
ivanlmh said:
Formatting system will most probably solve the issue. I would recommend doing that whenever you are switching between different android systems as it is always cleaner
Click to expand...
Click to collapse
Yea I have formatted all partitions but I think I installed kitchen rom after that.
I have installed stock rom once only.
sxi200 said:
Formatting system or anything else will not solve your issue. It is causes by a problem in your efs folder. This happened to alot of people on the S2 when upgrading to ICS, including myself. Took me months to finally figure it out.
Anyway, first step. Using root explorer or similar, navigate to your efs folder, then the factoryapp folder. In there check if you have these 2 files - factorymode & keystr.
If they are there click on them and open in text viewer. In both you should see the words 'ON'. If not, reopen in text editor and key those word in, in capital letters then save.
Try this and report back.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I have them both with word ON in each one and keystr file in efs/imei with word ON as well but neither the lock screen activated
nor power button functioning as it should be!!
ierrors said:
I have them both with word ON in each one and keystr file in efs/imei with word ON as well but neither the lock screen activated
nor power button functioning as it should be!!
Click to expand...
Click to collapse
This is the exact same issue with the S2. When you lock the screen it goes straight to the home screen and holding the power button for a little powers the phone off.
Anyway, below is what my factory app and imei folders look like. Maybe move the keystr file from the imei folder to the factory app folder and test. Might need to reboot.
{
"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"
}
On the S2 some people had ON in those files but had to change something with hex editor. Can't remember what exactly.
Sent from my GT-I9300 using xda premium
sxi200 said:
This is the exact same issue with the S2. When you lock the screen it goes straight to the home screen and holding the power button for a little powers the phone off.
Anyway, below is what my factory app and imei folders look like. Maybe move the keystr file from the imei folder to the factory app folder and test. Might need to reboot.
On the S2 some people had ON in those files but had to change something with hex editor. Can't remember what exactly.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I have efs backup before the problem came up. imei folder doesn't have keystr but still not working.
What I 'll do now, I would restore jelly bean rom which lock screen nd power button are working normally then I'm gonna back up
EFS folder to my external SD then I 'll replace it with the one on the ISC rom. I hope this works.
Edit: I checked with Hex as well and made it as instruction but no luck.
Edit2: I replaced EFS folder w/ the one on jelly bean rom but also no luck!!.
ierrors said:
I have efs backup before the problem came up. imei folder doesn't have keystr but still not working.
What I 'll do now, I would restore jelly bean rom which lock screen nd power button are working normally then I'm gonna back up
EFS folder to my external SD then I 'll replace it with the one on the ISC rom. I hope this works.
Edit: I checked with Hex as well and made it as instruction but no luck.
Edit2: I replaced EFS folder w/ the one on jelly bean rom but also no luck!!.
Click to expand...
Click to collapse
What apps are you using to backup/restore EFS?
Sent from my GT-I9300 using xda app-developers app
Arsaw said:
What apps are you using to backup/restore EFS?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
kTool
here is explanation on youtube:
https://www.youtube.com/watch?v=iY9cDkj4CCw
and usually I backup/restore manually by using Solid Explorer
I solved the issue, put EFS folder from jelly bean rom and across check both factorymode and keystr in efs/FactoryApp, they were OFF
I wrote ON on both and problem solved and no more keystr in efs/imei . Thanks for all of you guys for your help.
ierrors said:
I solved the issue, put EFS folder from jelly bean rom and across check both factorymode and keystr in efs/FactoryApp, they were OFF
I wrote ON on both and problem solved and no more keystr in efs/imei . Thanks for all of you guys for your help.
Click to expand...
Click to collapse
Good stuff. Glad you got it sorted. Did my head in for months when I had the S2.
Sent from my GT-P7500 using xda premium
sxi200 said:
Good stuff. Glad you got it sorted. Did my head in for months when I had the S2.
Sent from my GT-P7500 using xda premium
Click to expand...
Click to collapse
Yea I about to get crazy of this one cuz I had it for a week and all posts talked about efs/imei/ folder which no more keystr file inside it in S3 since the whole issue was in efs/FactoryApp.
Thank you sxi200 very much for your help, appreciate it.
ierrors said:
Yea I about to get crazy of this one cuz I had it for a week and all posts talked about efs/imei/ folder which no more keystr file inside it in S3 since the whole issue was in efs/FactoryApp.
Thank you sxi200 very much for your help, appreciate it.
Click to expand...
Click to collapse
Very welcome. :thumbup:
Sent from my GT-I9300 using xda premium
Related
So my SGSII International (yes I'm on ATT) has been working fine for the last two weeks. But last night, after flashing from CM7 to Sensation, my phone lost all service. As in no reception nor internet. I have already flash an old backup, flashed back to stock, and delete my efs folder through ODIN, yet the problem persist. Any help on this?
Have you checked your SIM card?
Yes. I placed my SIM card in my old Captivate and I had full service.
First time I read something like this!
Did you wipe your phone before flashing again?
Deleted efs folder? Why?
Sent from my GT-I9100 using xda premium
I just had the same problem. I flashed several roms without success until I reinstalled a CM7 backup. I guess I'm sticking to CM for awhile.
What about your IMEI or efs folder? Are they still how they should be?
Type *#06# to check your IMEI number.
MisterAnthonyxD said:
and delete my efs folder through ODIN,
Click to expand...
Click to collapse
Please explain why you deleted it
Deleted and then restored with an old backup of the efs folder. Was following an XDA member's guide.
Sent from my SGH-I897 using XDA App
MisterAnthonyxD said:
Deleted and then restored with an old backup of the efs folder. Was following an XDA member's guide.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
So is everything back to normal or are you still having issues?
Issues still remain. Using my Captivate at the moment.
Sent from my SGH-I897 using XDA App
Ok. So what is your IMEI and baseband? Is your IMEI correct and the the baseband is shown?
You can check this under settings - status or dial *#06#.
What files are in your /efs folder?
What files are in your backed up /efs folder?
What are the dates of these files?
Did you restore efs folder with the correct permissions? A simple drag and drop wont work. Does your imei number display when *#06# is entered
Sent from my GT-I9100 using XDA App
My IMEI and Baseband both says unknown. And if I recall correctly, the date is 10/03, the day I got the phone. I don't have my SGSII on me so I don't remember the content.
Sent from my SGH-I897 using XDA App
Ok. So copy the old .nv_data.bak and .nv_data.bak.md5 in your efs folder. Delete everything else in there an change the .bak to nv_data.bin or .bin.md5
then open in your backup folder the file mps_code.dat open it and see whether the code in it is the same as you csc. If not change out to match your csc. Then copy the mps file in your almost empty efs folder and reboot.
I hope that works.
Sent from my GT-I9100 using XDA App
Thanks for the advice. However, Root Explorer doesn't allow me the change the setting to R/W so I can't do it on my phone. Is there anyway to do it using ADB?
I have the same problem, but I haven't changed anything on my phone.
The battery emptied last evening, and I managed to use a power connection on the trainstation to load up my phone, as I had to make some calls.
But suddenly it just says No Service, and I tried to look for my IMEI number with *#06# but I only get a blank box with IMEI:
Dont really know what to do next.
Also, the battery usage have gone crazy. My battery lasts about 4 hour - with no usage at all.
Edit: Nevermind, I just flashed CM7 and it all went back to normal.
MisterAnthonyxD said:
Thanks for the advice. However, Root Explorer doesn't allow me the change the setting to R/W so I can't do it on my phone. Is there anyway to do it using ADB?
Click to expand...
Click to collapse
You can easily do the copying of the files in an adb shell.
Try to unmount and remount your efs folder.
Have a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1261948&highlight=imei
And if this does not work reflash your original stock rom with correct csc and try the steps again.
Thank you SO much. The link you gave me helped save my phone. Although I did lose all of my files in my internal SD, it was worth it.
MisterAnthonyxD said:
Thank you SO much. The link you gave me helped save my phone. Although I did lose all of my files in my internal SD, it was worth it.
Click to expand...
Click to collapse
I am glad to help. Don't forget to backud your sdcard files from time to time. You can just copy them to your pc.
Hi I have one question for you
How to get out of factory mode in the galaxy's three
I do not have a screen lock wifi and GSM
Pleas help
Did you find a way to get out of factory mode?
For some reason i also get a red warning saying:
"Factory Mode is ON!!!"
In this mode some functions are not working properly. Wi-Fi is turning off now. Please change to user mode before verification"
any help?
Warmax88 said:
Did you find a way to get out of factory mode?
For some reason i also get a red warning saying:
"Factory Mode is ON!!!"
In this mode some functions are not working properly. Wi-Fi is turning off now. Please change to user mode before verification"
any help?
Click to expand...
Click to collapse
+1
this frustated me.
I think I remember seeing a setting in the stock recovery or odin screen, but I can't verify that since I've already flashed CWM.
devonck said:
I think I remember seeing a setting in the stock recovery or odin screen, but I can't verify that since I've already flashed CWM.
Click to expand...
Click to collapse
i revert back to stock recovery, nothing mentions factory or user mode or whatever. i think im gonna send it back to the service center. would they take it for warranty?
Have you considered flashing a stock rom from your region?
Alternatively CM9.
But yeah, take it back. Thats no good.
Are you saying the phone is booted and usuable (launcher, apps...)
and not looking like this: http://www.jayceooi.com/wp-content/uploads/2012/06/Samsung-Galaxy-S3-Odin-Download-Mode_01.jpg
That is the only 'factory mode' I know off, and it's triggered by plugging in a Jig (301kOhm resistor between Pin 3 and 5 of the USB plug) into the phone.
It might happen if the phone is powered off and plugged in since it seems some chargers come with a Jig included in their plug.
If not, please take a screenshot or photograph the screen so others know what you are talking about since I for instance got no clue.
d4fseeker said:
Are you saying the phone is booted and usuable (launcher, apps...)
and not looking like this: http://www.jayceooi.com/wp-content/uploads/2012/06/Samsung-Galaxy-S3-Odin-Download-Mode_01.jpg
That is the only 'factory mode' I know off, and it's triggered by plugging in a Jig (301kOhm resistor between Pin 3 and 5 of the USB plug) into the phone.
It might happen if the phone is powered off and plugged in since it seems some chargers come with a Jig included in their plug.
If not, please take a screenshot or photograph the screen so others know what you are talking about since I for instance got no clue.
Click to expand...
Click to collapse
yes it was booted and apps working etc.
Well i got it fixed but dont really know how. I was checking logcat and it looked like something was wrong in my EFS folder (files not found, permission denied...). Luckily i had a backup so i just restored the folder with Root Explorer and it worked!! Everything is fine now.
For the people having the same problem check logcat and look for FACTORY_ON= 1 and try to find out where it gets enabled.
Warmax88 said:
yes it was booted and apps working etc.
Well i got it fixed but dont really know how. I was checking logcat and it looked like something was wrong in my EFS folder (files not found, permission denied...). Luckily i had a backup so i just restored the folder with Root Explorer and it worked!! Everything is fine now.
For the people having the same problem check logcat and look for FACTORY_ON= 1 and try to find out where it gets enabled.
Click to expand...
Click to collapse
but what if i have only CWM backup? do the EFS folder is contained there?
i do have EFS backup, but i backed it up when i realized bad things happened. so it was a little too late.
anjarys said:
but what if i have only CWM backup? do the EFS folder is contained there?
i do have EFS backup, but i backed it up when i realized bad things happened. so it was a little too late.
Click to expand...
Click to collapse
I'm not sure but if CWM backup does make a backup of the EFS folder just restoring the image from when ur phone was working well should fix it??
Maybe I'd check logcat first and see if something relevant is there( there's an app in the market called aLogCat to see it).
Remember that modifying EFS folder is very dangerous!!
edit: looks like CWM backup doesnt backup EFS folder (http://forum.xda-developers.com/showpost.php?p=23436154&postcount=84)
Warmax88 said:
I'm not sure but if CWM backup does make a backup of the EFS folder just restoring the image from when ur phone was working well should fix it??
Maybe I'd check logcat first and see if something relevant is there( there's an app in the market called aLogCat to see it).
Remember that modifying EFS folder is very dangerous!!
edit: looks like CWM backup doesnt backup EFS folder (http://forum.xda-developers.com/showpost.php?p=23436154&postcount=84)
Click to expand...
Click to collapse
yes, i already restored CWM backup and brings me no glory
time to back all stock and send it back to service center. do you think they would take it as a warranty or not? i mean what would cause corrupted EFS other than flashing?
A hardware fault in the MMC chip _could_ cause it, however it's very improbable.
It depends on whether they bother searching for the cause or not.
You could try backing up /efs/ (make sure you copy the hidden files starting with '.' too), then delete it's content and flash anew stock firmware. Some people reportet it rebuilt a working efs however I somehow doubt it.
Please post the output of the following commands in Terminal Emulator or adb:
lsattr -aR /efs
ls -al /efs
Also check if your IMEI is still displayed correctly (*#06#) and not the default one.
It should be written below the battery.
d4fseeker said:
A hardware fault in the MMC chip _could_ cause it, however it's very improbable.
It depends on whether they bother searching for the cause or not.
You could try backing up /efs/ (make sure you copy the hidden files starting with '.' too), then delete it's content and flash anew stock firmware. Some people reportet it rebuilt a working efs however I somehow doubt it.
Please post the output of the following commands in Terminal Emulator or adb:
lsattr -aR /efs
ls -al /efs
Also check if your IMEI is still displayed correctly (*#06#) and not the default one.
It should be written below the battery.
Click to expand...
Click to collapse
yes, imei is correct. but im not with my device right now. will report back soon as i have it in my hands.
GPKrzychuXxX said:
How to get out of factory mode in the galaxy's three
Click to expand...
Click to collapse
# echo -n ON > /efs/FactoryApp/factorymode
(and yes ON is the correct setting to turn it off)
thanks
Odia said:
# echo -n ON > /efs/FactoryApp/factorymode
(and yes ON is the correct setting to turn it off)
Click to expand...
Click to collapse
thank you - you´re the best --> works for me
Guys to fix this you can also do it in root explorer. See below. Go to efs / factoryapp / factorymode. Click on it and in text viewer check that it says 'on'. If not open in text editor and change 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-I9300 using xda premium
And how can i fix it?
If i reboot the phone --> efs folder is clear and Factory modus.
When i open the efs with root explorer android begins to write the efs, but only with IMEI 0049**** and further i make a hot reboot,
then the folder AppFactory comes from android itself (or i copy it into) - then it asks me for pin and i´m in normal mode. My Simcard is knowing from the handy but there is no net because of imei. The APN´s are to see then.
I seems that android check at boot (logcat) if efs is korrect or not (and delete itself) --> if not boot to Factory mode
I needed to know which files are inside efs and how could i fix this problem to make normal reboot without Factorymode again?
(In the AppFactory is a file called serial_no , is this the serial of phone? Can i change it? S/N --> 0000000000 )
Now i´m waiting for the octopus box to write my imei back to original and then i hope it will change this way to boot.
I hope this will fix it - does anybody know more?
thx for help
apollo
Same problem I have.
The phone when boot up, by itself shut wifi off and Factory Mode is ON
I have Factorymode file and ON command is written out there, but still I have the issue.
Also my lock screen not activating and power menu not appearing when I hold power button it shuts down the phone immediately. .
I have a Verizon Samsung GSIII but I am experiencing this Factory Mode issue after messing with EFS in an attempt to restore IMEI. Does anyone have a good backup EFS folder that they could share? Thanks!
sxi200 said:
Guys to fix this you can also do it in root explorer. See below. Go to efs / factoryapp / factorymode. Click on it and in text viewer check that it says 'on'. If not open in text editor and change it.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hi.
Thank you, your Solution work perfektly.
I have a i9308(China Mobile) from my Customer for IMEI Repair,the Device had brocken IMEI:0000000000,after flash with CyanogenMOD for i9300,back to original Firmware was Factory Mode on Screen and had no Network,because IMEI broken
I have successfull repair IMEI with SPT Box,the Device work now perfektly and have Network,only S/N:000000000 and Rev.0.0.
Best regards!
So even though I have been s-off since the Panda hit the scene, I think those that have yet to unlock/root might REALLY like to know this.
Basically you can create a back up using ADB on your NON-ROOTED device. Unlock/Root (which we all know will require a factory reset when using HTCDev Unlock) and then with your freshly rooted device, you can restore from the ADB backup you create.
I haven't tried this out yet (just got the update and attached change log) but might try it out just to see. Lucky for me all the devices I support have been Panda *certified but this will be real handy if I have to deal with a un-s-off-able device.
{
"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 EVO using xda premium
I was gonna post this, beat me to it haha. It's a nice feature for those s-on
Sent from my EVO using Tapatalk 2
That's one of the very first apps I ever bought, almost 3 years ago. The dev is great. He always responds to emails quickly. I'm glad this was added. I don't need it (yet), but this is definitely a nice feature.
Cool - I wish this had been in the program a few months ago when I did the unlock.
I did the ADB backup/restore manually but this would be a lot easier.
metalfan78 said:
That's one of the very first apps I ever bought, almost 3 years ago. The dev is great. He always responds to emails quickly. I'm glad this was added. I don't need it (yet), but this is definitely a nice feature.
Click to expand...
Click to collapse
Yeah man, the FIRST and only app I "require" someone purchase if I'm working on a phone is TB. If you never buy another app, TB is the single best investment you can make if you are rooting your phone and this just add more "goodness" to the pile. :good::good:
metalfan78 said:
That's one of the very first apps I ever bought, almost 3 years ago. The dev is great. He always responds to emails quickly. I'm glad this was added. I don't need it (yet), but this is definitely a nice feature.
Click to expand...
Click to collapse
I was gonna say the same. I noticed one day that TiBu wasn't being granted SU just out of nowhere. I emailed Joel, he emailed me back in less than an hour with exactly the fix. (I think it was 'force system busybox' from TI settings). Guy is awesome.
I'm not sure how you perform adb backup. Would be curious to know.
from my flying AOKP'd Evo LTE and xda premium
scottspa74 said:
I was gonna say the same. I noticed one day that TiBu wasn't being granted SU just out of nowhere. I emailed Joel, he emailed me back in less than an hour with exactly the fix. (I think it was 'force system busybox' from TI settings). Guy is awesome.
I'm not sure how you perform adb backup. Would be curious to know.
from my flying AOKP'd Evo LTE and xda premium
Click to expand...
Click to collapse
Good and Evo did a write up on how to do it. I haven't tried it BUT you can find the instructions here >>>>> http://goo.gl/9rr8N
Sent from my EVO using xda premium
I recently bought the pro version of this app strictly for this feature. Thus far, I have been unable to get it to work. I've tried two different .ab files both of which have been successfully restored from using UBT. Any suggestions or ideas why TB pro would say the .ab files are invalid?
Thanks!
Ryan
Hi Ryan,
Is your backup file password protected (encrypted) or not?
Also please do (on the device or in a unix shell):
busybox head -n4 MyBackupFile.ab
and please post the result...
hmm. didnt see that. I'll have to give it a try
joel.bourquard said:
Hi Ryan,
Is your backup file password protected (encrypted) or not?
Also please do (on the device or in a unix shell):
busybox head -n4 MyBackupFile.ab
and please post the result...
Click to expand...
Click to collapse
Another reason this app is the $hit! The dev of this essential app checking boards and popping in to help directly.
I'm about to try this out on a new white EVO LTE so we'll see how easy this goes.
Great news. Would be even greater if we could do it direct to a computer?
Maybe possible by mounting a network share? Would need to find a way to check the backup has worked though.
Or maybe this can be done with adb pull?
My phone went into boot-loop a week or so ago and this feature of TiB saved the day. I could not boot the normal OS to make a backup and had no recent backup. Reflashing my rom and wiping cache & dalvik made no difference. But I made a nandroid from TWRP, factory reset, then was able to restore my txt's from the nandroid using TiB (dialer storage) all right on the device while out to dinner. Damned nice.
Sent from my EVO using xda premium
Ironically, I'd been using the free version of TB for quite a while... but recently bought Pro because I found it to be so useful...
Did anyone fix the AB issue in titanium backup?
When trying to use this feature, tianium backup is not letting me select the .ab file. The file appears greyed out.
The backup file is encrypted.
I ran "busybox head -n4" on my .ab file and got the following -
ANDROID BACKUP
4
1
AES-256
Any ideas?
Edit: I managed to force select the file using another file manager only to be greeted by a message from titanium backup stating the backup file is either invalid or unsupported.
@joel.bourquard
ms.goofy said:
When trying to use this feature, tianium backup is not letting me select the .ab file. The file appears greyed out.
The backup file is encrypted.
I ran "busybox head -n4" on my .ab file and got the following -
ANDROID BACKUP
4
1
AES-256
Any ideas?
Edit: I managed to force select the file using another file manager only to be greeted by a message from titanium backup stating the backup file is either invalid or unsupported.
@joel.bourquard
Click to expand...
Click to collapse
Hi,
Feel free to try with TB 7.6.1, it should work
joel.bourquard said:
Hi,
Feel free to try with TB 7.6.1, it should work
Click to expand...
Click to collapse
Thanks for fixing it. It works now. Though I need to use a third party file manager app to select the .ab file.
Does this mean it's somehow possible to backup directly to a PC via USB, instead of backing up to an SD? I have destroyed 2-3 SD so far by heating them up to much while doing long backup/restore
Hi guys I'm having a strange problem with my sister's galaxy s2. For the second time she lost her IMEI without any reason (no flash ecc just turned off the phone and no IMEI when turned on). The last time I've been able to restore it and I made all the backups using efs pro, But this time when I try to restore it the procedure goes well but the imei is still missing. I tried to restore it manually and I discovered that for some reason the EFS folder is blocked on READ ONLY and I can't switch it in R/W. This problem is preventing me to restore the IMEI and I can't find any similar case on google. Can someone helps me with it?
Thank you a lot
EDIT: Android version 2.3.6 Gigerbread.XILA3 with chainfire kernel
artos01 said:
Hi guys I'm having a strange problem with my sister's galaxy s2. For the second time she lost her IMEI without any reason (no flash ecc just turned off the phone and no IMEI when turned on). The last time I've been able to restore it and I made all the backups using efs pro, But this time when I try to restore it the procedure goes well but the imei is still missing. I tried to restore it manually and I discovered that for some reason the EFS folder is blocked on READ ONLY and I can't switch it in R/W. This problem is preventing me to restore the IMEI and I can't find any similar case on google. Can someone helps me with it?
Thank you a lot
EDIT: Android version 2.3.6 Gigerbread.XILA3 with chainfire kernel
Click to expand...
Click to collapse
Have you root your phone?
akumasihdisini said:
Have you root your phone?
Click to expand...
Click to collapse
Sure the phone is rooted. My situation is very strage. If I enter the EFS folder with root explorer and I click on "Convert to R/W" the folder remains R/O. Also if I try to cancel any file (or rename or move) in EFS folder nothing happes (that probabbly is what prevents EFS PRO from working). Is there any way to force that folder to be read/write or to cancel it? Maybe using adb shell from the pc?
try tool, play with it for a while.
GS2 repair app is your other choice.
Sent from...this is not even my S2
gastonw said:
try tool, play with it for a while.
GS2 repair app is your other choice.
Sent from...this is not even my S2
Click to expand...
Click to collapse
Thx for the info. Gs2 repari looks like the fix that i need but unfortunatelly it doesn't work. Can you specify what app is the Tool one that you suggested me?
hc ktool I think it's called.
Sent from the little guy
gastonw said:
hc ktool I think it's called.
Sent from the little guy
Click to expand...
Click to collapse
Thank you a lot gastonw that worked. If someone is interested I had to cancel the efs folder with hc ktool, reboot, restore and reebot again to have i work. Now I think that I will upgrade the phone to the last firmware available hoping to avoid other imei loss
Back up & save to a safe location that EFS folder like there's no tomorrow!
Sent from the little guy
gastonw said:
Back up & save to a safe location that EFS folder like there's no tomorrow!
Sent from the little guy
Click to expand...
Click to collapse
Eheh of course I already done it about one year ago! The problem was my blocked EFS folder but now I know how to fix it if it happens again :good:
People seem to have problems whenever they use EFS Pro. People should use kTool; seems to almost always restore without any problems.
This is the new ROM Manager?
Sent from the little guy
HI im accidentally delete bluid.prop file from system folder
Im on stock jelly beam lg AT&T rom oficial and rooted.
Thats all i have done
This is how it happend
Well I was trying to edit something there with root explorer and then I have two files with that name but one says .bak and I delete the one that doesn't says .bak and only have one know.
After I do it I try to open the one I left and it doesn't open. Them I realize I did a really stupid thing. I search and nobody is talking about it on this forum. The ones who talk about it was an old phones.
My phone is working cuz I didn't shut it down but I know that when I reboot it I will be **** up.
Pliz anybody knows what to do?
The only idea that I have is to do a factory reset may be it reinstall it or something. But I prefer to ask first here to see if one of you (the prooos) know something not like me an idiot who make a big mistake.
I'm sorry
Thanks in advance
radhames3048 said:
HI im accidentally delete bluid.prop file from system folder
Im on stock jelly beam lg AT&T rom oficial and rooted.
Thats all i have done
This is how it happend
Well I was trying to edit something there with root explorer and then I have two files with that name but one says .bak and I delete the one that doesn't says .bak and only have one know.
After I do it I try to open the one I left and it doesn't open. Them I realize I did a really stupid thing. I search and nobody is talking about it on this forum. The ones who talk about it was an old phones.
My phone is working cuz I didn't shut it down but I know that when I reboot it I will be **** up.
Pliz anybody knows what to do?
The only idea that I have is to do a factory reset may be it reinstall it or something. But I prefer to ask first here to see if one of you (the prooos) know something not like me an idiot who make a big mistake.
I'm sorry
Thanks in advance
Click to expand...
Click to collapse
I still have the file build.prop.bak
It wasn't opening but I select the option open with and select text viewer and it open and it was like the build.prop file
So I rename the file build.prop.bak to build.prop and I think now its ok I guess but I'm still worried
Did I solve my problem or not?
I'm scared to reboot it
radhames3048 said:
I still have the file build.prop.bak
It wasn't opening but I select the option open with and select text viewer and it open and it was like the build.prop file
So I rename the file build.prop.bak to build.prop and I think now its ok I guess but I'm still worried
Did I solve my problem or not?
I'm scared to reboot it
Click to expand...
Click to collapse
You should be fine. Worst case scenario just reflash the ROM without wiping data and it will restore the whole system partition including the build.prop. just make sure you always have a copy of the ROM you are currently running on your SD card.
Sent from my LG-E970 using Tapatalk 4
Joecascio2000 said:
You should be fine. Worst case scenario just reflash the ROM without wiping data and it will restore the whole system partition including the build.prop. just make sure you always have a copy of the ROM you are currently running on your SD card.
Sent from my LG-E970 using Tapatalk 4
Click to expand...
Click to collapse
Thanks to answer
But I don't have a copy of my Rom cuz I'm stock I'm only rooted nothing more (I'm not unlocked bootloader and anything just root)
What should I do? Factory reset going to setting--> general--> backup and restore --> factory reset.
Or what I did of rename the file solve the problem?
radhames3048 said:
Thanks to answer
But I don't have a copy of my Rom cuz I'm stock I'm only rooted nothing more (I'm not unlocked bootloader and anything just root)
What should I do? Factory reset going to setting--> general--> backup and restore --> factory reset.
Or what I did of rename the file solve the problem?
Click to expand...
Click to collapse
Renaming the backup file to build.prop should be fine. Check the permissions it should be rw-r--r. If all is good you should be fine to reboot/shutdown. LGNPST can always recover your phone as long as it can at least be turned on. Like I said you should be fine but there is always options.
Sent from my LG-E970 using Tapatalk 4
Joecascio2000 said:
Renaming the backup file to build.prop should be fine. Check the permissions it should be rw-r--r. If all is good you should be fine to reboot/shutdown. LGNPST can always recover your phone as long as it can at least be turned on. Like I said you should be fine but there is always options.
Sent from my LG-E970 using Tapatalk 4
Click to expand...
Click to collapse
Ok thank you
The permissions are like this= rw-r--r--. How I change it to the way you said.
Rw-r--r-- is the same as rw-r--r?
radhames3048 said:
Ok thank you
The permissions are like this= rw-r--r--. How I change it to the way you said.
Rw-r--r-- is the same as rw-r--r?
Click to expand...
Click to collapse
Yes that is the same. Should be good to go.
Sent from my LG Optimus G using xda app-developers app
cyberbandit1998 said:
Yes that is the same. Should be good to go.
Sent from my LG Optimus G using xda app-developers app
Click to expand...
Click to collapse
Ok thanks
Do you know how i can swicth between 2g 3g 4g
I tried *#*#4636#*#* and there's not option
I tried editing build.prop ro.radio.networkmode=enable and reboot and nothing
I tried download an app called LTE settings and it just a shortcut to the menu I see when I type *#*#4636#*#*
Any idea?
radhames3048 said:
HI im accidentally delete bluid.prop file from system folder
Im on stock jelly beam lg AT&T rom oficial and rooted.
Thats all i have done
This is how it happend
Well I was trying to edit something there with root explorer and then I have two files with that name but one says .bak and I delete the one that doesn't says .bak and only have one know.
After I do it I try to open the one I left and it doesn't open. Them I realize I did a really stupid thing. I search and nobody is talking about it on this forum. The ones who talk about it was an old phones.
My phone is working cuz I didn't shut it down but I know that when I reboot it I will be **** up.
Pliz anybody knows what to do?
The only idea that I have is to do a factory reset may be it reinstall it or something. But I prefer to ask first here to see if one of you (the prooos) know something not like me an idiot who make a big mistake.
I'm sorry
Thanks in advance
Click to expand...
Click to collapse
The remaining 1 is build.prop.bak? If yes then just remove the .bak, and you can open it now with texteditor, check permission make sure it is RW-R--R--, owner is root, then you should be good.