[Q] This just puped up when i was restoring my EFS ! - Galaxy S III Q&A, Help & Troubleshooting

so last night I planned to come back and find a new ROM to install and I did found one ( PardusHDRom_412_final ). After installing the rom as it said how to do, the phone started up normally but I noticed there is something wrong with the network. it just show Emergency calls only!
so I started looking up for the cause of the problem and I got that it was the EFS. the recovery made a backup before the installation which I didn't knew that has been done. so I tried to just easily copy and past the folder with my backup and everything will be good to go. IT WORKED xD I got network and made calls and everything working very normally but it wasn't the ROM I wanted to have. I said if it happened once and worked then it will happen again after installing the rom I want. I installed the official ROM and Rooted it and tried doing what I did before but it didn't work and now im getting this msg all the time.
the rom it worked on was paranoid1.4
I tried doing factory reset and it showed me the same thing.
I installed another Official ROM but no luck and still this msg showing up..
Any help?

Its called factory mode and its documented in the imei / efs sticky thread from general > sticky roll-up
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

You mean it's a forum here or its director in my phone?
Sent from my GT-I9300 using xda app-developers app

Theres a link in my signature. General is a forum here in the s3 forum.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
Theres a link in my signature. General is a forum here in the s3 forum.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
ok I tried both steps it provided and no luck yet so now im trying restock and give it a try with the backup I have of efs. wish me luck xD thanks for the fast replay

I tryed this, and it worked very well:
Go into Root Explorer. Go to /efs/FactoryApps/ and open the file "factorymode" with a texteditor.
Then delete "OFF" and write "ON" there. Now reboot and it will work.
Next time if you have to copy your EFS, just change it on your computer before copying.

Mikey94 said:
I tryed this, and it worked very well:
Go into Root Explorer. Go to /efs/FactoryApps/ and open the file "factorymode" with a texteditor.
Then delete "OFF" and write "ON" there. Now reboot and it will work.
Next time if you have to copy your EFS, just change it on your computer before copying.
Click to expand...
Click to collapse
No, it didn't work. I tried with both ES file explorer and Root explorer ( blue icon ) it didn't do anything!

Maybe you screwed permissions up by copying your backup the way you did.
You should put your backup on pc and follow the adb guide in my thread to delete and restore efs again.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
Maybe you screwed permissions up by copying your backup the way you did.
You should put your backup on pc and follow the adb guide in my thread to delete and restore efs again.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
you mean this?
I'm stuck in factorymode, is this related?
Yes, factorymode is caused by corrupt efs. It is possible to fix it with root and a terminal emulator.
Firstly try these commands (case sensitive)
Code:
su
echo -n ON >> /efs/FactoryApp/factorymodeIf they fail, use the more detailed commands:
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
rebootThis should hopefully return you to user mode. If not, restoring to stock and / or restoring an efs backup may be the next things you try before sending for repair.
I followed every step you said and I even read it again. cant I just do fix permission from recovery?
I hope you not laughing at me right now! lol

mahmoudsalem91 said:
you mean this?
I'm stuck in factorymode, is this related?
Yes, factorymode is caused by corrupt efs. It is possible to fix it with root and a terminal emulator.
Firstly try these commands (case sensitive)
Code:
su
echo -n ON >> /efs/FactoryApp/factorymodeIf they fail, use the more detailed commands:
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
rebootThis should hopefully return you to user mode. If not, restoring to stock and / or restoring an efs backup may be the next things you try before sending for repair.
I followed every step you said and I even read it again. cant I just do fix permission from recovery?
I hope you not laughing at me right now! lol
Click to expand...
Click to collapse
wow I did it!!!!! I just flashed an earlier stock rom ( 4.0.4 ) and its just working fine!
any steps before I upgrade to 4.1.2?

Oh no it didn't work. It's still there but it's just not showen
Sent from my GT-I9300 using xda app-developers app

mahmoudsalem91 said:
Oh no it didn't work. It's still there but it's just not showen
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Sorry, could you elaborate?

rootSU said:
Sorry, could you elaborate?
Click to expand...
Click to collapse
ok here is what happened. I tried finding a way to fix this. I don't know if it possible to just wipe the efs folder out to just reset it to default as it was so then I can be able to get the F*** out from this factorymode ( its really annoying ).
I flashed official ROM 4.0.4 and that's the full name ( I9300XXALE8_I9300HTSALE2_I9300NELE4_HOME.tar.md5 ). Network worked fine, I could make and receive calls and sms but that was the weird this that I noticed which there was no setup steps in the beginning as every new setup roms. so I did an update and another one and then another one then I got to the 4.1.2 now and im having the msg right now again.
can I format the efs partition ? is there is any other way than the one provided in your sticky forum?
btw changing from OFF to ON didn't work because it was already ON.

You'd only have the set up wizard if you factory reset.....
You need to delete EFS contents and restore your efs backup.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
You'd only have the set up wizard if you factory reset.....
You need to delete EFS contents and restore your efs backup.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Ok all done. this time its DONE and working as normal again and here is what I did exactly.
after installing lots of Roms to find a way to get the hell out of the factorymode, the last rom I been using was Pardus HD. I tried changing from OFF to ON in factorymode file by text editor but it wasn't any luck by that because it was already ON. after I read what RootSU said in the last replay ( thanks a lot for your help ) deleting all efs partition files and restore the backup I hade. I deleted everything in this folder and just went into recovery ( philz touch ) did a factory reset and then chose installing new rom so it deleted everything. I went to mount and partition and did a format to cache and system again and then I installed a new rom ( Omega V48.1 ). the phone started but it was in factorymode still. opened ES file explorer and went to efs/factoryApp/ and then I opened the factorymode file with text editor and it was off so I changed it from OFF to ON and restarted the phone.
phone started in startup setup and after that everything back to normal. Im NOT gonna try flashing any roms for now, I will just enjoy my phone that back from factory f*** mode and maybe later I will see something new to flash or just back to stock.
im posting this because there is lots of people in factorymode and I know how they feel about being in this **** mode. it is really pain in the ass.
thank you so so so much RootSU and everyone helped me out.
Kevin out

mahmoudsalem91 said:
Ok all done. this time its DONE and working as normal again and here is what I did exactly.
after installing lots of Roms to find a way to get the hell out of the factorymode, the last rom I been using was Pardus HD. I tried changing from OFF to ON in factorymode file by text editor but it wasn't any luck by that because it was already ON. after I read what RootSU said in the last replay ( thanks a lot for your help ) deleting all efs partition files and restore the backup I hade. I deleted everything in this folder and just went into recovery ( philz touch ) did a factory reset and then chose installing new rom so it deleted everything. I went to mount and partition and did a format to cache and system again and then I installed a new rom ( Omega V48.1 ). the phone started but it was in factorymode still. opened ES file explorer and went to efs/factoryApp/ and then I opened the factorymode file with text editor and it was off so I changed it from OFF to ON and restarted the phone.
phone started in startup setup and after that everything back to normal. Im NOT gonna try flashing any roms for now, I will just enjoy my phone that back from factory f*** mode and maybe later I will see something new to flash or just back to stock.
im posting this because there is lots of people in factorymode and I know how they feel about being in this **** mode. it is really pain in the ass.
thank you so so so much RootSU and everyone helped me out.
Kevin out
Click to expand...
Click to collapse
Thanks for the update.
Hey, have a look at custom backup jobs in Philz. The EFS backup done by Philz is very good. Now you have a working one, it's easy to restore. Highly recommended.

rootSU said:
Thanks for the update.
Hey, have a look at custom backup jobs in Philz. The EFS backup done by Philz is very good. Now you have a working one, it's easy to restore. Highly recommended.
Click to expand...
Click to collapse
doing it now :good:

I am having this same issue. stuck in factory mode.
I ran a root browser and my EFS folder is EMPTY ??? what do I do?
I don't have a backup of the EFS folder as I just got the phone (used) and never touched it prior.

mahmoudsalem91 said:
doing it now :good:
Click to expand...
Click to collapse
So you have a backup of the efs folder?
Just read through everything we wrote here. Hope it helps
Sent from my GT-I9300 using xda app-developers app

factory mode reroot
i rooted my s3 i535 actidenally erased all data and my fone is in factory mode i have back up efs files and program to restall them but fone is not rooted no more i tryed using rootdegfs but it dont pick up my fone... so how do u root a fone that is in factorymode ty

Related

[Q]Galaxy SII "No Lockscreen" on ICS.

Hi Guys , sorry for my bad english i'm European.
I dont know why but on my SGS II i9100 on every ICS rom , Samsung or Unofficial i get no lock screen or power off menu. The only fix i attempted is Permissions Fix from CWM but lockscreen is still missing.
Any fixing methods?
Hi,
just want to make sure, you happened to choose "No scree lock" for Screen security?
Settings>Security>Screen lock
kkipsy said:
Hi Guys , sorry for my bad english i'm European.
Click to expand...
Click to collapse
That would be a terrible excuse if you were from the UK
Anyway, have you wiped data and caches?
re
hehe ^^
does not matter what i chose from settings , no lock , slide , pattern or pin. screen lock simply does not work.. and when i press the power button ( lock button ) for 2 seconds the phone shuts down , without the power off confirmation. pretty annoing.
Yes xethor , i did. Steps i did : permission fix from CWM , data / cache delete , factory reset.. still nothing
i dont think it's beacause of the custom ROM , i get no lockscreen in oficial sammy rom or any ICS rom.
Pretty sure this is the 3rd fail thread on this in as many days. Why you guys make new threads every time instead of using dedicated threads is beyond me.
Anyway, see posts in other threads.
Odia said:
# echo -n ON > /efs/imei/keystr
# reboot
Click to expand...
Click to collapse
oinkylicious said:
There's plenty of other information in the threads dealing with these ROMs too. If only people would ask/read there, rather than making new threads for every issue they encounter.
(potential original source in T989 forums http://forum.xda-developers.com/showthread.php?t=1438451)
Click to expand...
Click to collapse
re
# echo -n ON > /efs/imei/keystr
# reboot
i'm a noob in this kind of stuff... i dont know how to operate those commands.
ew
please , can someone redirect me to a thread where those commands are explained , how i run those commands on a rooted ICS sgs2?
hmmm , my first quess , is that i must use some app to navigate to efs/imei , and edit keystr file ... i will try that! also make a backup of EFS folder!!
kkipsy said:
please , can someone redirect me to a thread where those commands are explained , how i run those commands on a rooted ICS sgs2?
Click to expand...
Click to collapse
- Download "Terminal Emulator" app from market
- open it
- type into the command shell you just got:
Code:
su
echo -n ON > /efs/imei/keystr
sync
reboot
re
thank you HellcatDroid and oinkylicious ! problem solved !
my problem solved to!!!! thank you man !!!
thanks!!! it's help me also!
don't wanna be the scrub, but my lock screen is still gone. restored all of my efs backups and it's still not back any other thoughts?
EDIT: after a bit of derp on my part, I realized that the EFS folder wasn't keeping my changes despite all the attempts to restore the keystr file. In order to fix this, I had to set all permissions to 777, then reset the keystr file to ON. Once I had my lockscreen and boot menu back I just rebooted into CWM and proceeded to fix permissions.
in short, if the editing doesn't work:
1) Change permissions of the EFS and IMEI folder to 777
2) edit the keystr file
3) fix permissions in CWM
And how did I set efs and imei permission. Plz?
It fixed mine too!!! however the IMEI still starts with 00... I know thats not right since samsungs imei starts with 3 soemthing. please help how i can restore my original imei
thanks

[Q] Instructions on going from LinromV2 back to stock?

I got an EFS.tar backup
I got Odin
I got Heimdall
I got YP-G1 stock.tar.md5
I just don't know how put it all together.
Back on GB roms, I would just wipe everything via CWM, use Odin to flash stock, and then wipe once again.
But this is ICS. Surely it's different, right?
I wrote out instructions in either the LinICS or the Nebula thread (I can't remember it was several weeks ago), also the files are in the Restore to stock thread from Zaclimon. you gonna have some issues in that your efs backup is an efs.tar instead of an efs.rfs
Oh!
I also have a cwm recovery image of stock, if that matters at all
Doesn't seem like a quick restore job either though
theplasmastorm said:
Oh!
I also have a cwm recovery image of stock, if that matters at all
Doesn't seem like a quick restore job either though
Click to expand...
Click to collapse
IT DOESN'T, when you go to LinICS or any of the CM9 ROMs your player is converted from RFS partitions to MTD ones and you HAVE TO use HEIMDALL with a PIT file to reparttion the player back to RFS as you flash the stock ROM.
Totally lost on what to do. I don't know where to begin or anything. I need someone to hold my hand step by step like a baby.
I've read the recovery thread and did some searches around the place, but I don't really understand a thing. I have a US YP-G1
Alright after some fiddling around I got back to stock but the usual blank efs issues are there. I still don't understand how to restore my efs.tar. Could someone help me please?
I also can't mount efs and have no idea what to do with the blankefs.img in the recovery thread
Okay after some more fiddling around I was able to restore my EFS. The efs bugs are still there though so I'm suspecting that the automatic backup that CM9 did is utterly useless and I lost my efs forever. Well I guess I'm going back to linaro <_<
theplasmastorm said:
Okay after some more fiddling around I was able to restore my EFS. The efs bugs are still there though so I'm suspecting that the automatic backup that CM9 did is utterly useless and I lost my efs forever. Well I guess I'm going back to linaro <_<
Click to expand...
Click to collapse
Did you have content on your efs.tar?
Yes my efs.tar has stuff in it
What I did was...
wipe data
restore stock via heimdall. add in blankefs.img in the efs spot.
flashed terra via odin
went to cwm recovery. got on adb shell
cd /efs
ls -l. nothing was in it except what blankefs did
tar -x -f /sdcard/efs.tar
ls -l. tar successfully extracted
got off adb shell and restarted the player
the efs issues still presist
so then i got on adb shell again and checked the efs folder and everything was still there
So I don't know
theplasmastorm said:
Yes my efs.tar has stuff in it
What I did was...
wipe data
restore stock via heimdall. add in blankefs.img in the efs spot.
flashed terra via odin
went to cwm recovery. got on adb shell
cd /efs
ls -l. nothing was in it except what blankefs did
tar -x -f /sdcard/efs.tar
ls -l. tar successfully extracted
got off adb shell and restarted the player
the efs issues still presist
so then i got on adb shell again and checked the efs folder and everything was still there
So I don't know
Click to expand...
Click to collapse
one thing that works, atleast the method I used to solve it, once you've copied the contents back into the EFS folder on the player, then flash the Dream Ultra ROM from CWM, then after booting the ROM up shutdown and wipe data/factory reset, then use Odin to flash the stock GB.tar through odin.
Roms at these links.
http://forum.xda-developers.com/showthread.php?t=1719685&highlight=dream+ultra
http://forum.xda-developers.com/showthread.php?t=1512331&highlight=stock+rooted+4+0
Oh snap that worked. Aroma installer to the rescue.
theplasmastorm said:
Oh snap that worked. Aroma installer to the rescue.
Click to expand...
Click to collapse
Now make a a proper EFS.rfs backup using the method described here http://forum.xda-developers.com/showthread.php?t=1632376&highlight=efs+backup that way next time you need to revert back from an ICS ROM you can flash the efs.rfs to the efs section instead of the blankefs.img and not have to go through this again.
FYI the method listed can be done on the player using terminal emulator just go into it and type su to gain superuser then type the the part for making an efs backup and your done, then copy that file to your PC.
Well when I first flashed linaro there was no mention of efs backup or anything in the topic post and that is why I got in the predicament in the first place.
And then when I watched your vid on how to flash it there was no mention of efs backup either.
Well all that is in the past. I know better now.
I already made a backup as soon as I got back to stock
theplasmastorm said:
Well when I first flashed linaro there was no mention of efs backup or anything in the topic post and that is why I got in the predicament in the first place.
And then when I watched your vid on how to flash it there was no mention of efs backup either.
Well all that is in the past. I know better now.
I already made a backup as soon as I got back to stock
Click to expand...
Click to collapse
Sorry, it was in my older videos that I did, forgot to mention it in that one, guess I'm not the only one to goof up if it's not in the OP either.
theplasmastorm said:
Yes my efs.tar has stuff in it
What I did was...
wipe data
restore stock via heimdall. add in blankefs.img in the efs spot.
flashed terra via odin
went to cwm recovery. got on adb shell
cd /efs
ls -l. nothing was in it except what blankefs did
tar -x -f /sdcard/efs.tar
ls -l. tar successfully extracted
got off adb shell and restarted the player
the efs issues still presist
so then i got on adb shell again and checked the efs folder and everything was still there
So I don't know
Click to expand...
Click to collapse
Whenever I try to do these steps before flashing dream ultra rom it tells me "tar not found" I have a efs.tar on my sd card for certain.

[Q] Used the toolkit and i have a q and an A

So I used the S3 toolkit by mskip and it's cool it's so fast lovely. One problem now I can't delete anything. I went to look for the answer.
Quote: Originally Posted by pat357
Mark,
Maybe you missed my initial post concerning a possible bug in the Toolkit v7.0.
http://forum.xda-developers.com/show...postcount=1307
After making a backup from my internal SD using the "backup SD" option in the Toolkit, it pulled all my files to my PC and everything went well.
However after restoring my SD using the "restore internal SD", my permissions appeared to be screwed up.
I could not delete/modify any file anymore on my internal SD. I got a lot of FC from apps.
What are the correct permissions and owner from the internal SD (=/data/media) ??
Did the toolkit change any permissions/ownership ? I thought I saw a " chmod 775 or 755" flashing on the terminal when restoring my SD (about the last command at the end, IIRC).
To get it working again, I did a :
Code:
su
chmod -R 777 /data/media/*
The owner from each file is now "root" (0), but my permissions are complete open (777)
Somehow this doesn't seem correct.... but I don't know.
So, again : what are the correct permissions and owner from the internal SD (=/data/media) ??
Click to expand...
Click to collapse
adb shell chmod -R 775 /data/media
adb shell chown media_rw.media_rw /data/media
Mark.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
COOL! Now how do I do that?
I honestly don't know where the first place to look would be
google how to use adb
Nope
Also
Re: [SAMSUNG GALAXY S3 UNIFIED TOOLKIT V7.0] Drivers, Backup, Root, Recovery + MORE [
Quote: Originally Posted by mskip
If you have root then try installing a file manager such as Root Explorer from the Play Store which should let you delete any files you need to.
Mark.
Click to expand...
Click to collapse
Thanks I finally got it. But I an not sure how. I did try this but it was like my chip was blocked from formatting or erasing anything then after hours of trying to erase it and factory reset and wipe it magically fixed.
Domination V3 Powered!
Click to expand...
Click to collapse
I have root explorer and it's still not deleting. And mind didn't get fixed magically omg what do I do?!?!
I tried the adb thing also.
Someone anyone know how to fix this omg
okay there's a file permission part of thie toolkit but I'm probably gonna destroy my phone if I do something here
Mother of god i flashed the stock rom and it still did nothing why jesus
vapidteens said:
Mother of god i flashed the stock rom and it still did nothing why jesus
Click to expand...
Click to collapse
READ THE RULES stop bumping .
jje

factory mode and yellow text on screen

After the problem with imei ,Now there's the problem with yellow text on screen..not working lockscreen no extendend menu on power button,it's shutdonw when I hold,I tried to go back on stock...not working..I try many code in SU...not work..i try many things but nothing work..I can fix this or is "forever" ?
this apears on samsung based roms..
" su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
"
and not working..
From terminal emulator
su
echo -n ON > /efs/FactoryApp/factorymode
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
From terminal emulator
su
echo -n ON > /efs/FactoryApp/factorymode
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
I tried..not working...yellow text keep apears...sorry for my english
Run this
su
efs/FactoryApp/factorymode
...in terminal and show me screenshot
Sent from my GT-I9300 using Tapatalk 4
I'm also with this problem on mine. A help from a more experienced user would be appreciated. Still have the wrong IMEI issue. Can someone help?
Please don't hijack this thread with a different issue
If you have a problem with your imei and you cant find an answer in one of the many imei threads created each day, post a thread with specific details of your issue... how you got there, firmware involved, what you've tried
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Run this
su
efs/FactoryApp/factorymode
...in terminal and show me screenshot
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Network -> yes
IMEI -> yes
Serial number -> yes
lockscreen -> no
after rom flash no "tour" (setup google account,setup name etc)
extended power menu -> no
yellow text on screen -> yes
cosmy032 said:
Network -> yes
IMEI -> yes
Serial number -> yes
lockscreen -> no
after rom flash no "tour" (setup google account,setup name etc)
extended power menu -> no
yellow text on screen -> yes
Click to expand...
Click to collapse
Thanks. The screenshot you uploaded with the terminal shows what I would expect for a correct factorymode setting.
I take it you have no efs backup?
I think all you can do is wipe and return to stock to see if you can get it repaired. Maybe return to stock fixes it (although unlikely)
rootSU said:
Thanks. The screenshot you uploaded with the terminal shows what I would expect for a correct factorymode setting.
I take it you have no efs backup?
I think all you can do is wipe and return to stock to see if you can get it repaired. Maybe return to stock fixes it (although unlikely)
Click to expand...
Click to collapse
I have some efs backup,I tried to wipe..to flash stock with odin..but it's same..
I tried flash with odin ->
I9300XXUFME3_I9300OJKFME1_HOME.tar
I9300BVALE4_I9300OROALE4_I9300BVLE4_HOME.tar
I9300XXEMD3_I9300OJVEMC1_I9300XXEMA5_HOME.tar
KIES_HOME_I9300XXEMG4_I9300OXAEMG4_1314436_REV00_user_low_ship.tar
I9300XXEMC2_I9300OXFEMC1_I9300XXEMC2_HOME.tar
but none worked....I don't have any ideas...how to fix..
if restoring the backup also failed, all you can do is send it in I think. Or keep googling hoping someone else finds a fix. Sorry
rootSU said:
if restoring the backup also failed, all you can do is send it in I think. Or keep googling hoping someone else finds a fix. Sorry
Click to expand...
Click to collapse
I restored backup succesful but backup repair imei,serial number and network yellow text and lockscreen no..
cosmy032 said:
I restored backup succesful but backup repair imei,serial number and network yellow text and lockscreen no..
Click to expand...
Click to collapse
Service centre next .
jje
JJEgan said:
Service centre next .
jje
Click to expand...
Click to collapse
If after the command:
echo -n ON > /efs/FactoryApp/factorymode
you get this message:
can't create /efs/FactoryApp/factorymode No such file or directory
then your EFS is missing (got wiped out somehow), and it cannot be recreated by simply flashing a stock firmware or by factory reset.
I had the same problem, so I read the EFS partition from an identical working phone via
dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=/sdcard/efs.img.ext4
adb pull /sdcard/efs.img.ext4
TAR-ed it, then flashed it via Odin and now everything works fine.
@billa And how is life as someone other's clon?
@cosmy032 You could restore your IMEI, right? What's your modem now?
rp158 said:
@billa And how is life as someone other's clon?
@cosmy032 You could restore your IMEI, right? What's your modem now?
Click to expand...
Click to collapse
The EFS no longer contains the imei, so you can safely write someone else's. If yours is corrupted that's a whole different thread.
billa said:
The EFS no longer contains the imei, so you can safely write someone else's. If yours is corrupted that's a whole different thread.
Click to expand...
Click to collapse
No..I buy a Nexus 5 and now i'm tinking it was a good choice

[Q] HELP missing factoryapp folder cannot exit factory mode

So, like the title suggests, my factoryapp folder is missing, I've used Terminal Emulator to try and fix the factory mode problem but it tells me that it can't find efs/factoryapp, I've done a factory reset but my factoryapp folder's still missing, I didn't backup my efs folder, is there any other way, besides service center, that I can exit factory mode?
zachlag said:
So, like the title suggests, my factoryapp folder is missing, I've used Terminal Emulator to try and fix the factory mode problem but it tells me that it can't find efs/factoryapp, I've done a factory reset but my factoryapp folder's still missing, I didn't backup my efs folder, is there any other way, besides service center, that I can exit factory mode?
Click to expand...
Click to collapse
Are you doing it with root access?
Best way is to set up adb and list the folder contents of efs that way.
Have a look at the general > Sticky roll-up thread > IMEI ? EFS - Know this stuff thread. I have instructions.
If your list does indeed show the factoryapp folder is missing, I can supply you one.
my error you posted twice
Alright, so the lockscreen and power menu came back but there's yellow text covering a part of my screen, any solution to that?
zachlag said:
Alright, so the lockscreen and power menu came back but there's yellow text covering a part of my screen, any solution to that?
Click to expand...
Click to collapse
Need to exit factory mode. See my last post please.
rootSU said:
Need to exit factory mode. See my last post please.
Click to expand...
Click to collapse
Yeah, my factoryapp folder is indeed missing...
zachlag said:
Yeah, my factoryapp folder is indeed missing...
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/20471345/SUroot/Tools/efs.rar - Here is FactoryApp folder. Unrar to windows desktop
Connect to USB, boot recovery, mount EFS (as per my guide)
Run commands
Code:
adb push c:\users\rootsu\desktop\efs /efs/
adb shell
chmod 755 /efs/FactoryApp
where c:\users\rootsu\desktop\ is where you put the efs folder extract
Where's your efs guide?
zachlag said:
Where's your efs guide?
Click to expand...
Click to collapse
Please read my first post in this thread :/
rootSU said:
Please read my first post in this thread :/
Click to expand...
Click to collapse
OH, sorry didn't read it carefully! Alright, I'll try this, will keep ya updated, thanks in advance
zachlag said:
OH, sorry didn't read it carefully! Alright, I'll try this, will keep ya updated, thanks in advance
Click to expand...
Click to collapse
Cool. Cheers
rootSU said:
Cool. Cheers
Click to expand...
Click to collapse
I'm getting an "error: cannot connect to daemon", is this normal?
zachlag said:
I'm getting an "error: cannot connect to daemon", is this normal?
Click to expand...
Click to collapse
nope
is that running the adb shell command?
Try a reboot (of the computer)
Also, look at things liek AV etc, maybe they are blockign. Run CMD as Administrator... Things like that
rootSU said:
nope
is that running the adb shell command?
Try a reboot (of the computer)
Also, look at things liek AV etc, maybe they are blockign. Run CMD as Administrator... Things like that
Click to expand...
Click to collapse
Still, can't man.... :\ I'm really at my wits end here...I've followed the instructions but I always get that error
Have you Googled the error?
Dont have dell pc suite installed?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Have you Googled the error?
Dont have dell pc suite installed?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
If you have a terminal program installed on ya phone, you can always use that instead. Kust dont use the adb part of the commands.
True but it would be better to get adb working as this is something I'd prefer done when android isn't running.
Its clearly an issue on the pc, just finding out what it is. Im not sure I've even got the full error
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
True but it would be better to get adb working as this is something I'd prefer done when android isn't running.
Its clearly an issue on the pc, just finding out what it is. Im not sure I've even got the full error
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Thanks for the help anyway, I've removed all traces of root and sent it to the service center, got it back within 3 hours and all's working well so far (knock on wood). If I root and flash Omega v46.1 or any other ROM running on 4.2.2, and do a titanium restore, will it restore my old efs? Or will it just flash the ROM and work without problems?
Titanium doesn't touch EFS. Use philz recovery and backup efs before flashing anything
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Titanium doesn't touch EFS. Use philz recovery and backup efs before flashing anything
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Alright man, thanks so much for your help so far! One last question, will there be any problems if I flash a ROM running 4.2.2 (Omega v46.1) when I'm currently on 4.1.2 (Stock)?

Categories

Resources