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!
Related
If I'm getting a new note. Can I restore a Nandroid of the rom from my old note to the new one to keep everything in tact or us that gonna mess stuff up?
Sent from my SAMSUNG-SGH-I717 using xda premium
ctraywick1 said:
If I'm getting a new note. Can I restore a Nandroid of the rom from my old note to the new one to keep everything in tact or us that gonna mess stuff up?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I would say right off the bat...Yes...your gonna mess stuff up....
why not use titanium backup paid...which is great, you can save all your setting/data/apps....then if your going to run the same ROM, on your new Note...just copy the titanium backup folder from your old Note to your new Note... and put tibu on your new Note...hit restore...btw the paid is great due to you capabilities of run batch backup and restorations...among lots of other items ...Tibu is a very powerful tool for any android smartphone...
check it out...
I think his goal is to clone his phone. Not for samsung even if it is the same exact model.
Samsung phones have an encrypted file that generates the phone IEMI. If you nandroid, that folder and file go to the second phone and your phone ends with no (or a generic) IEMI.
There are better ways to restore a new phone.
Edit: I did this with an AOSP ROM without issue. Even though everything seemed fine, I wouldn't suggest doing it. I know setting up the phone is a PITA, but the extra time it takes is well worth it considering the problems that may arise from restoring a nandroid to the same model phone.
bigjoe2675 said:
I would say right off the bat...Yes...your gonna mess stuff up....
why not use titanium backup paid...which is great, you can save all your setting/data/apps....then if your going to run the same ROM, on your new Note...just copy the titanium backup folder from your old Note to your new Note... and put tibu on your new Note...hit restore...btw the paid is great due to you capabilities of run batch backup and restorations...among lots of other items ...Tibu is a very powerful tool for any android smartphone...
check it out...
Click to expand...
Click to collapse
Yea i have the paid version so i could just do it like that and treat it like a new rom. Just restore my apps from tibu, sms/ call logs with mybackup pro, and just use my launcher/messaging theme and setup . So all i have to manually restore are my system settings. Thanks
rangercaptain said:
I think his goal is to clone his phone. Not for samsung even if it is the same exact model.
Samsung phones have an encrypted file that generates the phone IEMI. If you nandroid, that folder and file go to the second phone and your phone ends with no (or a generic) IEMI.
There are better ways to restore a new phone.
Click to expand...
Click to collapse
Didnt know that about the encrypted files,thanks for the warning. You were right I just wanted to be lazy and "clone my phone"
froidroid said:
Edit: I did this with an AOSP ROM without issue. Even though everything seemed fine, I wouldn't suggest doing it. I know setting up the phone is a PITA, but the extra time it takes is well worth it considering the problems that may arise from restoring a nandroid to the same model phone.
Click to expand...
Click to collapse
Point well taken
Sent from my SAMSUNG-SGH-I717 using xda premium
rangercaptain said:
I think his goal is to clone his phone. Not for samsung even if it is the same exact model.
Samsung phones have an encrypted file that generates the phone IEMI. If you nandroid, that folder and file go to the second phone and your phone ends with no (or a generic) IEMI.
There are better ways to restore a new phone.
Click to expand...
Click to collapse
i am certain nandroids DO NOT contain the /efs folder... back in the captivate days you had to do a manual backup of that folder in case your IMEI (M comes before the E btw) got messed up you could restore it with that backup... if a nandroid contained that, then that backup step would have been superfluous.
On top of that... nandroids don't even contain the fuggin modem...why would they have the phone specific information that you should NEVER even touch in the first place?
studacris said:
i am certain nandroids DO NOT contain the /efs folder... back in the captivate days you had to do a manual backup of that folder in case your IMEI (M comes before the E btw) got messed up you could restore it with that backup... if a nandroid contained that, then that backup step would have been superfluous.
Click to expand...
Click to collapse
Are you certain enough to let what you say brick someone's phone? I don't think you or I are enough of an expert to make that assertion.
From Rootswiki forum:
This question comes up in a lot of forums because some people think we should be able to just copy the whole package from one phone to another like we can on computers. Unfortunately almost every piece of software on phones is installed in such a way that it is inextricably tied to that particular piece of hardware. Nandroid and other backups only work on the phone they were made.
At code.google.com the consensus was don't do it.
I got the /efs folder detail from Samsung support. Its within the /system folder -- why would you think it gets skipped during backup? And the messed up IEMI number is a very common outcome. Just look around in other galaxy s class phone forums.
From TiBU FAQ's:
{
"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"
}
And your concern about the frakkin modem -- that code isn't in the modem, its in the nvdata file (the encrypted one I mentioned) in the /efs folder.
@ctraywick1:
Don't follow advice that could ruin your phone when there are only opinions not facts available.
Just develop a good backup strategy so migrating to a new rom or phone is less painful.
My point about the modern was not that IT contained the IMEI, i know perfectly well where it is, in fact better than you (see below lol). it was the fact that you flash modems all the time and yet they are not contained in s nandroid, so...why would non volatile data like that be included...
And the efs folder is most certainly NOT IN the /system directory...that would be retarded as that directory gets COMPLETELY FORMATTED with every Rom flash.
IT'S IN THE ROOT DIRECTORY
studacris said:
My point about the modern was not that IT contained the IMEI, i know perfectly well where it is, in fact better than you (see below lol). it was the fact that you flash modems all the time and yet they are not contained in s nandroid, so...why would non volatile data like that be included...
And the efs folder is most certainly NOT IN the /system directory...that would be retarded as that directory gets COMPLETELY FORMATTED with every Rom flash.
Click to expand...
Click to collapse
Why are you making such a big deal about this? The OP just wanted advice and I can find 100 posts that say don't copy your nandroid to another phone. Because we are dealing with a $600 device the wisest thing to do is say "don't do it" and help him develop a usedul backup strategy. What are you doing to further that goal? I gave several experts and you only offer your opinion. Thats just not good enough even if you are the smartest guy in the room.
And your own picture says you're mistaken about the flashing and rewriting. Look at the date of your /efs folder. I'm sure your phone is more than two days old. My stock phone has May 6 2012 date created.
Yes, I was wrong about the location, but the advice is still his best course. Experiment on your own phone.
Lol you come back with false information...i correct it.. Not "making a big deal", but i will not be corrected with information that is not accurate.
A nandroid is not the "whole phone"
As i said, it does not contain a modem, also doesn't contain your bootloaders, your sdcards/emmc, or the /efs folder.
And since it doesn't contain bootloaders there is no chance of hard bricking anything.
I didn't condone nor endorse anything either...Just saying the IMEI is not in a nandroid, that 's all
Yeah, I'm no expert just an enthusiast. Thats why I got the TiBu screenshot that said "whole phone". I guess they are giving incorrect information.
Your screenshot contradicts you -- look at the /efs folder date.
Oh.. That's cause i was experimenting with some stuff inside there, just goofing around and looking through it really, and even though it was a copy i was messing with... i copied back a known untouched version just out of ocd.
Well anyway I don't think it matters to you but I enjoy your posts and repect your opinions.
You add a lot of value to xda.
studacris said:
Oh.. That's cause i was ... i copied back a known untouched version just out of ocd.
Click to expand...
Click to collapse
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
Hi guys,
I just installed the Cyanogenmod 11 (Kit Kat) in my YP-G1 (US) and now the home button doesn't work. I have read that this problem could be solved with a "wipe data". Is that true?
The installation was made from the stock rom (rooted), then TerraSilent, then the preflash and finally the cm-11.zip (and obviously the gapps).
Thank you so much!
SourCinnamon said:
Hi guys,
I just installed the Cyanogenmod 11 (Kit Kat) in my YP-G1 (US) and now the home button doesn't work. I have read that this problem could be solved with a "wipe data". Is that true?
The installation was made from the stock rom (rooted), then TerraSilent, then the preflash and finally the cm-11.zip (and obviously the gapps).
Thank you so much!
Click to expand...
Click to collapse
you are most likely missing parts of your efs. as the install instructions said, make sure you have a backup so you can restore it. just put the needed files in your efs folder and you should be set
goldflame09 said:
you are most likely missing parts of your efs. as the install instructions said, make sure you have a backup so you can restore it. just put the needed files in your efs folder and you should be set
Click to expand...
Click to collapse
I did not have this issue on CM 10.2, so flashing to CM 11 caused my EFS to disappear? At the moment, I am back at stock and trying to restore my EFS with zaclimon's dummy EFS, but I don't seem to be making too much progress, as I still am missing my lockscreen and power options.
kusanou said:
I did not have this issue on CM 10.2, so flashing to CM 11 caused my EFS to disappear? At the moment, I am back at stock and trying to restore my EFS with zaclimon's dummy EFS, but I don't seem to be making too much progress, as I still am missing my lockscreen and power options.
Click to expand...
Click to collapse
I doubt that your efs got erased with the flash of cm11, have you checked it to see if everything was in order? If so are you able to restore your efs from the backup made into /sdcard/backup/efs?
zaclimon said:
I doubt that your efs got erased with the flash of cm11, have you checked it to see if everything was in order? If so are you able to restore your efs from the backup made into /sdcard/backup/efs?
Click to expand...
Click to collapse
I actually was unable to find any backups by the time I was able to access data again. Admittedly, I had wiped data in order to get everything up and running onto kit Kat, and even after that, I was not able to find a backup, which led me to resort to the dummy efs.
Wiping system after replacing the EFS with the dummy, and flashing factoryfs worked wonders. I am now back up and running, home button works fine, however, i still cannot seem to charge my device on CM10.2, something that I forgot to check while I was on CM11, so I will check that out now.
^ Same problem, can you help me with replacing using the dummy EFS? I'm assuming you follow Zaclimon's recovery method (using Heimdall because mine is US) but I don't know how to incorporate the EFS dummy file in there. I've reformatted to stock before but can't figure out what to do with the EFS.
I have no EFS backup though I did notice there were a couple files in a folder called system/firmware/efs
Although I fixed the EFS issue, my battery doesn't seem to want to charge. When it is plugged in, the battery indicator in the status bar shows charging, but battery stats in settings says it is not charging.
For the dummy EFS, just edit the files that Zaclimon says to edit in his post. Check your MAC address in phone information in settings, and copy that into your bt.txt. The buyer_code.dat can be opened up in wordpad, and I changed it to XAA. Lastly, serial.info should be your serial number, which you can find in the battery compartment on a sticker. After all of that is done, copy everything in the dummy efs to your efs folder on your device, wipe system, and reboot. That's all I have done to get it working. Once everything is working just fine, save that edited dummy efs somewhere, in my case, I have it saved in a Google drive folder, as the reason why I lost my EFS in the first place was because my computer was wiped along with all of my backups.
I've gotten and changed the three files but now can't find how to paste the EFS folder over the one in the system. I can't do it with file manager and permission is denied when I try doing it in ES File Explorer (even though it's granted root acces).
Also, there are two EFS folders on the system, on in /efs and one which is /sys/firmware/efs.....not sure which one to copy over.
Sportfreunde said:
I've gotten and changed the three files but now can't find how to paste the EFS folder over the one in the system. I can't do it with file manager and permission is denied when I try doing it in ES File Explorer (even though it's granted root acces).
Also, there are two EFS folders on the system, on in /efs and one which is /sys/firmware/efs.....not sure which one to copy over.
Click to expand...
Click to collapse
Do you have supersu installed from the play store? I had a similar issue once before, just install super su and then reinstall es file explorer, then grant access through super su. Also, just copy over to /efs, make sure you transfer everything from the dummy efs, including the modified files.
I have re-rooted by re-flashing CM11 but the problem I'm having now is that ES File explorer says no space available on /device when I try and copy/paste the EFS folder there over the old one. The other file managers like Astro don't seem to work either when doing it.
Question...after you copy/paste the backup folder in /system, do you close and then format /system or wipe data/factory reset?
Ok, this is a very strange device. After copying/pasting another backup up efs withotu doing any factory or system reset stuff and just restarting....home button is working.
What I'm curious about is why some people can install CM11 without this issue and others have to restore the efs....there must be a way to install CM11 without having to worry about efs problems.
Home Button Not Working.
May I get instructions on how to fix the home button issue on the cm11? I am on Carbon. :laugh:
Found a partial fix
Home button fix (without messing with /efs) worked for my wifes phone.
Still, quick settings doesn't work (can't switch to panel by pressing button from drawer)
Tested, incoming calls/texts work fine.
Run terminal
su
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
“update global set value=1 where name=’device_provisioned’;”
Reboot your tablet/phone
You might want to "select * from global where name=’device_provisioned’;" before the update query, to be certain what you're changing from in case you need to change it back.
I have had it I have deleted all my photos AGAIN!!! I can't seem to see why KitKat made the Ext-SD Read Only : (ie photos in the internal memory) : WHY can't we access the internal memory from any of the recoveries and with all the other problems associated with the LB that we are all familiar with this is a really bad phone to root.
How did this happen ?
I downloaded a new ROM, made sure my phone had them both the ROM and the Dual Recovery flashable file on the SD and rebooted to TWRP. I then wiped out my everything but external and internal SD. After doing this I went to flash the ROM but couldn't find it (I know it was there but buried in one of the million sub directories.) Next I was interrupted at the door by my boss, we got to talking and I realized that my screen was off. When I returned the phone was in fact dead. #$#@ I screamed out loud because I knew what this meant. Despite my knowledge of how this operates I knew from experience loosing all my wedding photos that this wasn't going to go over well (read my previous thread of lost wedding photos).
Why even recommend rooting to anyone with a locked boot loader after all this is a phone people buy to use the camera. The photos are forced by default to internal memory and internal memory is extremely volatile on this phone
HAS ANYONE OUT THERE been able to get the data back I simply have no system/recovery partition now ?! Surely SOMEONE out there knows of a way to .ftf a system partition only so I can access my internal memory as the data partition is still fully intact..
If not I wont be surprised as this LB phone (camera) is a total disaster for me and I am regretting getting it in the first place... It's a real mess with these glitches ..
futiless said:
I have had it I have deleted all my photos AGAIN!!! I can't seem to see why KitKat made the Ext-SD Read Only : (ie photos in the internal memory) : WHY can't we access the internal memory from any of the recoveries and with all the other problems associated with the LB that we are all familiar with this is a really bad phone to root.
How did this happen ?
I downloaded a new ROM, made sure my phone had them both the ROM and the Dual Recovery flashable file on the SD and rebooted to TWRP. I then wiped out my everything but external and internal SD. After doing this I went to flash the ROM but couldn't find it (I know it was there but buried in one of the million sub directories.) Next I was interrupted at the door by my boss, we got to talking and I realized that my screen was off. When I returned the phone was in fact dead. #$#@ I screamed out loud because I knew what this meant. Despite my knowledge of how this operates I knew from experience loosing all my wedding photos that this wasn't going to go over well (read my previous thread of lost wedding photos).
Why even recommend rooting to anyone with a locked boot loader after all this is a phone people buy to use the camera. The photos are forced by default to internal memory and internal memory is extremely volatile on this phone
HAS ANYONE OUT THERE been able to get the data back I simply have no system/recovery partition now ?! Surely SOMEONE out there knows of a way to .ftf a system partition only so I can access my internal memory as the data partition is still fully intact..
If not I wont be surprised as this LB phone (camera) is a total disaster for me and I am regretting getting it in the first place... It's a real mess with these glitches ..
Click to expand...
Click to collapse
If you got proper root you're always able to backup. It's just your fault you lost your data.
If it's just system that's gone you haven't lost any actual data yet, get the ftf for the firmware you were using, flash it in flashtool with everything but system /kernel checked. That way it doesn't wipe data etc. I'm not at my computer so can't be exact but you get the picture just restoring system via flashtool should do the trick
Also if you use xposed there's a module to enable handling of external storage, that and setting pics to save to external memory card should avoid you ever having this issue again. There's also an app called folder mount that can be used to ghost internal directories to the external card too hth
Oh also, I may be wrong but if you were using philz if you let the screen go dark while your running something it stays dark till it's finished then a quick press of the power button wakes it back up, you should of waited a little longer if that was the issue
Mr.R™ said:
If it's just system that's gone you haven't lost any actual data yet, get the ftf for the firmware you were using, flash it in flashtool with everything but system /kernel checked. That way it doesn't wipe data etc. I'm not at my computer so can't be exact but you get the picture just restoring system via flashtool should do the trick
Also if you use xposed there's a module to enable handling of external storage, that and setting pics to save to external memory card should avoid you ever having this issue again. There's also an app called folder mount that can be used to ghost internal directories to the external card too hth
Oh also, I may be wrong but if you were using philz if you let the screen go dark while your running something it stays dark till it's finished then a quick press of the power button wakes it back up, you should of waited a little longer if that was the issue
Click to expand...
Click to collapse
Your a GENIUS this totally saved me thank you so much sir : THIS WORKED... it was something I considered but found daunting because I have a 6906, the 6903 FTF worked for anyone reading this !!!! Maybe I can fix my attitude on this one thanks again...
futiless said:
Your a GENIUS this totally saved me thank you so much sir : THIS WORKED... it was something I considered but found daunting because I have a 6906, the 6903 FTF worked for anyone reading this !!!! Maybe I can fix my attitude on this one thanks again...
Click to expand...
Click to collapse
Can I suggest you edit title to include [SOLVED] - might help other folks out
No worries pal, glad you got it sorted I'd be just the same if I thought I'd lost data that was important to me
Plus, why the hell are you not using google+ to backup your photos ?
Personally I use My PhoneExplorer to back my phone up and synchronise with my pc. It wil also back up all your photos to a folder in the My Pictures directory, sync your calendar and even make basic data backups. Been using it for years now, ever since I had a Sony Ericsson K700 phone
This is just a suggestion if you are also a bit paranoid in storing all your stuff on google.
http://www.fjsoft.at/en/
Sent from my D6503 using XDA Free mobile app
But you know that even without any rooting there is an option inside the camera app where to store pictures? You can choose ext. SD Card there. In my opinion it's not hard to find and due to your last disaster it's your fault not checking this. Since there are options to keep pictures on SD Card in fact you shouldn't blame the phone nor Sony.
furrypotato said:
Plus, why the hell are you not using google+ to backup your photos ?
Click to expand...
Click to collapse
Privacy reasons, not wanting a third party to be responsible for your data etc etc
gurningchimp said:
Can I suggest you edit title to include [SOLVED] - might help other folks out
Click to expand...
Click to collapse
Would like to do this but don't know how exactly ...
futiless said:
Would like to do this but don't know how exactly ...
Click to expand...
Click to collapse
click on edit/delete
click on go advanced
see the title box Below Reason for editing... change that one
Example Picture
{
"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"
}
furrypotato said:
Plus, why the hell are you not using google+ to backup your photos ?
Click to expand...
Click to collapse
Kind of short sighted and pretentious to think we would all see things exactly the same. Personally Google isn't the "answer" to all my problems. Secondly I have had numerous smart phones as most of us have and this Xperia although I love it I have to dance around the volatile situation it poses to have 4.4 limitations which requires root to be able to in order to write to SD (?!). Kinda weird if you ask me and this is just one more thing to setup and calibrate so between roms it is easily overlooked. As I don't actually use social networking all that much and I have such large photos among many other things. I am thinking of other ways to automate this in the future. I am looking for a more set it and forget it method and if I could persist this between roms so be it.
I would like to know who keeps everything they own online aswell today... I mean why do companies use a VPN for data archive ... when they can just sync EVERYTHING to the cloud ?
I ponder politics
Envious_Data said:
click on edit/delete
click on go advanced
see the title box Below Reason for editing... change that one
Example Picture
Click to expand...
Click to collapse
Where is the field to edit the Thread and not just the first post ?
You should not flash ROMs in locked BL even if you have a recovery and root that doesn't mean it will flash a ROM.
Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.
I think we now have Xposed - check the end of this discussion:
https://github.com/rovo89/Xposed/issues/310
I might give this a go when I'm feeling less lazy.
Well actually yes xposed is available. But I left this solution for a long time in favour of Magisk and it's modules to be honest
Sent from my HTC U11 using XDA Labs
thref23 said:
I think we now have Xposed - check the end of this discussion:
https://github.com/rovo89/Xposed/issues/310
I might give this a go when I'm feeling less lazy.
Click to expand...
Click to collapse
Thanks a lot for the link! Thanks a lot to rovo89 for the beta4!!!
xposed-v90-sdk26-arm64-beta4-test1.zip works fine on SHT-AL09 after flashing it via TWRP
What we need:
ROOT
TWRP
Flash with TWRP View attachment xposed-v90-sdk26-arm64-beta4-test1.zip
Install View attachment XposedInstaller_3.1.5.apk
PROFIT!
{
"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"
}
ZeuseZ said:
Thanks a lot for the link! Thanks a lot to rovo89 for the beta4!!!
xposed-v90-sdk26-arm64-beta4-test1.zip works fine on SHT-AL09 after flashing it via TWRP
What we need:
ROOT
TWRP
Flash with TWRP View attachment 4525802
Install View attachment 4525805
PROFIT!
View attachment 4525804
Click to expand...
Click to collapse
A lot of Xposed modules do not work. GravityBox, which is my favorite, completely f*ked up the rom - had to reflash. Tried a couple of others - didnt break things, but didnt work either. It's dangerous to try these modules, because TWRP restore doesn't really work.
If I'm not mistaken, in the event of a bad module, Xposed can be disabled at boot by pressing a hardware key over and over again. Not that I want to find out.
Anyways, Edge and Edge Pro work. They don't remap the fingerprint sensor functionality. But they have other useful features.
thref23 said:
If I'm not mistaken, in the event of a bad module, Xposed can be disabled at boot by pressing a hardware key over and over again. Not that I want to find out.
Click to expand...
Click to collapse
Which hardware key would that be? And what exactly does "over and over again" mean - how many times or for how long?
Apo11on said:
Which hardware key would that be? And what exactly does "over and over again" mean - how many times or for how long?
Click to expand...
Click to collapse
Any key. This must be where I read it:
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
Lukest85 said:
While the device boots you can activate the xposed safemode to disable the framework & modules, without flashing any files and without entering recovery or ROM.
Background:
People are posting when stuck at boot screens or bootloops with xposed installed and there have been lots of great solutions/advice from the community but I have not seen much info posted about the xposed safemode so thought I would share what I believe to be the easiest & first thing to try in order to boot & troubleshoot your setup.
To disable xposed:
1. Repeatedly press any single hardware button during early startup (as soon as device powers on)
2. Wait for device to finish booting into recovery/ROM
3. Fix your setup
Details:
1. The first recognised key press generates two vibrations
2. Then continue to press the same hardware button four more times within 5 seconds
*Each key press generates a short vibration*
3. Success is confirmed with a long vibration
NB
• Activating safemode adds the file 'disabled' (no quotes) to data/data/de.robv.android.xposed.installer/conf/
• The 'disabled' file can be created manually from recovery or rom to disable xposed & modules
• If problems with hardware buttons try pressing the touchscreen to activate safemode
To re-enable xposed:
1. Remove the file 'disabled' using file manager or terminal
2. Reboot
3. Enjoy
***common reasons for xposed related bootloops are due to xposed module/s conflicting with system or each other, and user installing the incorrect framework for the device/sdk. Please investigate these options first and read/search the xposed Q&A OP/thread if you're unsure before posting or contacting devs***
xposed Q&A thread:
http://forum.xda-developers.com/showthread.php?t=3030118
Disclaimer:
**I cannot guarantee safemode works with every version of xposed or every device but it has always worked for me on differing setups, roms & devices.**
I hope this is helpful and will be updating the post again so stay tuned for more detailed/technical info.
Give thanks to talented & amazing devs: @Tungstwenty - xposed safemode @romracer - xposed @rovo89 - official xposed
Fantastic work & great dedication !!!
Click to expand...
Click to collapse
thref23 said:
Any key. This must be where I read it:
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
Click to expand...
Click to collapse
That's not really helpful in our case. It says to keep pressing and then it will boot into recovery. Step 3 says "Fix your setup" . If TWRP is not working properly (and that's exactly point - it does not, so there is no fixing) there is no benefit in booting into the recovery. Doing stuff like clearing cache does nothing when Xposed module screws up the rom. Not to mention you dont really need this Xposed "feature" in order to boot into recovery or download mode. You can just shut down your device and then use the regular, designated hw key combination in order to boot into either.
Apo11on said:
A lot of Xposed modules do not work. GravityBox, which is my favorite, completely f*ked up the rom - had to reflash. Tried a couple of others - didnt break things, but didnt work either. It's dangerous to try these modules, because TWRP restore doesn't really work.
Click to expand...
Click to collapse
TWRP restore works fine for me.
magnumlove said:
TWRP restore works fine for me.
Click to expand...
Click to collapse
You have different M5 model than mine - the 10" if I recall correctly. Partition table and a bunch of other things are not the same. You have the same or very similar model as the OP from that twrp thread, so it's not surprising the recovery works for you. If someone with SHT-AL09 says the restore works for them - that's a different story, and I'd have to start troubleshooting my own device. As of this moment, I think this recovery build is not fully compatible with 8.4" LTE version. It's failing to mount /system and /vendor partitions, and after some troubleshooting I've done I can see there are 4 versions of mount binary on my device. For example, when I manually invoke the one in /sbin folder - I can do "mount -o remount,rw /system" just fine, but when I try the same with mount version from /system/bin folder - it fails. And there is 2 more of them. It's not clear which one twrp is using when it's trying to mount partitions for restore, but it's obviously the wrong one. The only way I see to fix this is to recompile twrp.
I have the SHT-AL09. When I was bootlooped (I was actually more bricked than bootlooped), I installed TWRP, and I could not mount anything (except my SD card) as read/writeable.
After the equivalent of a factory reset, I installed TWRP, and it seems to work perfectly.
I have not tried to restore a backup. But I wonder if doing so would work after the equivalent of a factory reset, if not while bootlooped.
thref23 said:
I have the SHT-AL09. When I was bootlooped (I was actually more bricked than bootlooped), I installed TWRP, and I could not mount anything (except my SD card) as read/writeable.
After the equivalent of a factory reset, I installed TWRP, and it seems to work perfectly.
I have not tried to restore a backup. But I wonder if doing so would work after the equivalent of a factory reset, if not while bootlooped.
Click to expand...
Click to collapse
"seems to work perfectly" and "I have not tried to restore a backup" are contradicting statements in this context. "seems" sounds like a guess. If you want to be about 95% sure it will work -boot into twrp, goto Advanced->Terminal and type "mount". Examine if your /system and /vendor partitions are mounted as "ro" or "rw" - if it's ro then your restore is likely to fail. Needless to say, to be 100% sure you have to actually attempt a restore. Make certain to decrypt your /Data using PIN/password when twrp prompts you, otherwise you will get screwed. TWRP doesn't need to decrypt in order to wipe, and it wipes the /Data partition before every restore. If you don't decrypt and attempt restore - /Data will get wiped, but then the /Data restore will fail, because it's encrypted. In that case, theoretically you should be able to boot into twrp again, and it should prompt you for PIN /password to restore /Data again. Once you provide it and successfully decrypt - you should be run the restore again and restore the missing /Data partition from nandroid backup.
Apo11on said:
"seems to work perfectly" and "I have not tried to restore a backup" are contradicting statements in this context. "seems" sounds like a guess. If you want to be about 95% sure it will work -boot into twrp, goto Advanced->Terminal and type "mount". Examine if your /system and /vendor partitions are mounted as "ro" or "rw" - if it's ro then your restore is likely to fail. Needless to say, to be 100% sure you have to actually attempt a restore. Make certain to decrypt your /Data using PIN/password when twrp prompts you, otherwise you will get screwed. TWRP doesn't need to decrypt in order to wipe, and it wipes the /Data partition before every restore. If you don't decrypt and attempt restore - /Data will get wiped, but then the /Data restore will fail, because it's encrypted. In that case, theoretically you should be able to boot into twrp again, and it should prompt you for PIN /password to restore /Data again. Once you provide it and successfully decrypt - you should be run the restore again and restore the missing /Data partition from nandroid backup.
Click to expand...
Click to collapse
Without rebooting back into TWRP, I think all partitions are mounted r/w. Previously, if I unchecked 'mount system partition read only,' it would stay checked - not anymore. And I was able to successfully flash Xposed. That's what I mean by "seems to work perfectly."
I have TWRP backups now, that I hope I never have to try and restore. For now I'd much rather leave well enough alone than to be 100% certain. Plus I kind of hate rebooting.
thref23 said:
I have the SHT-AL09. When I was bootlooped (I was actually more bricked than bootlooped), I installed TWRP, and I could not mount anything (except my SD card) as read/writeable.
After the equivalent of a factory reset, I installed TWRP, and it seems to work perfectly.
I have not tried to restore a backup. But I wonder if doing so would work after the equivalent of a factory reset, if not while bootlooped.
Click to expand...
Click to collapse
Restore works fine from EMUI to EMUI. I had issues when trying to restore back to EMUI from a GSI-TWRP hung on the splash screen. Managed to restore in the end after flashing stock system img. All my back ups were made with PIN screenlock removed.
Apo11on said:
A lot of Xposed modules do not work. didnt break things, but didnt work either
Click to expand...
Click to collapse
same here, most modules don't work, has anyone found a solution?
Si73 said:
Restore works fine from EMUI to EMUI. I had issues when trying to restore back to EMUI from a GSI-TWRP hung on the splash screen. Managed to restore in the end after flashing stock system img. All my back ups were made with PIN screenlock removed.
Click to expand...
Click to collapse
I don't have screenlock but I haven't managed to create any backup, because of the famous 255 error
I've got huawei mediapad m5 lite (bah2-w19)