Related
Hi guys,
Once again, thanks to MartinEve and the whole unrevoked team for the work they've made on Wildfire rooting.
I've just used unrevoked to root my wildfire. Seems alright cause :
> id cmd tells I'm root
> titanium backup tells root permission is given
Cool
But... I try to do a nandroid backup from the clockworkmod recovery and it says : "Error while dumping boot image!"
Do you have any idea ?
Thx a lot
Solved...
It was due to a problem on my sdcard (was not able to write in the /sdcard folder even from windows). I had to delete some files and then nandroid backup was available.
mmr41 said:
Solved...
It was due to a problem on my sdcard (was not able to write in the /sdcard folder even from windows). I had to delete some files and then nandroid backup was available.
Click to expand...
Click to collapse
Why dont you post your problem and its solution here for others to benefit from it
http://forum.xda-developers.com/showthread.php?t=742518
I just wanted to share a story of woe and redemption so that it doesn't happen to you.
As background, I had sim unlocked my phone using helroz's method a while back, and my phone has been working fine from team whiskey's early days till now. Recently, I was flashing my phone as most of us do. I noted that after flashing the dead horse kernel, my market was not working properly, so I decided to odin back to JFD. From there, I flashed Bionix, but afterward, noted that I wasn't getting any cell reception. After some investigation and several odins, I looked at my software info and found that my baseband was unknown. I flashed back to JFD however, and it worked fine. In fact, this was the only rom where the cell worked. The phone otherwise was functioning flawlessly, including wifi.
Further investigation showed that this has happened to others, and anecdotally, people have fixed it by odining over and over or doing some magic with their sim card. I did just that but to no avail. After some thinking, it occurred to me that maybe my /efs data was bad, so I took a look. Hitting *#06# showed the generic samsung IMEI while in JFD (it did not work in other versions as the baseband was not working), not my normal IMEI. That's odd. I still had the backup from trying to sim unlock it months ago. I tried to overwrite the /efs folder w/ my own, but I could not write it due to 'not enough space.'
Further investigation showed that indeed, my efs partition had been borked, and so I could not write data to it (I could copy however). The only way to fix this is by flashing/odin'ing a new partition. This only works if you have a backup, which I didn't. Basically, I had a fancy media player at this point.
I went ahead and looked on craigslist and found a vibrant w/ a broken screen, figuring I could swap out the guts. I immediately backed up the /efs folder and partition of the broken phone, just in case. On a whim, I tried to flash the efs partition from the broken phone to my phone. Lo and behold, the baseband came back. I was now able to write to that partition, so overwrote the /efs folder w/ my backup from before. My IMEI came back afterwards, and so now, I have 2 functioning vibrants. I'm not sure what data is stored in /dev/block/stl3, but I do know I was able to fix my phone using another phone's data. They both work w/ my sim, though I am unsure if they can connect simultaneously using different sims or if they are somehow cloned, but the IMEIs are different for sure.
The moral of the story is that this phone is nigh unbrickable and even when it doesn't boot, you can always try the jig. The only part of the phone you can't fix w/ a routine odin it seems, is the efs partition, so I would encourage everyone to make a backup and keep it safe. This is not done standard as an initiation into rooting and roms and such, but it should be. Normally, odin'ing a rom does not write to this area, but even w/o screwing with this, frequent flashing and odins can apparently corrupt it, leaving you high and dry. With this backup and odin, you could probably fix your phone from any jam.
Here are the relevant threads on how to do this:
http://forum.xda-developers.com/showthread.php?t=882039
http://forum.xda-developers.com/showthread.php?t=859914
Keep those backups safe!
Thank you for sharing ur experience, I recently noticed that my data speeds have gone down after unlocking my vibrant using the method you mentioned above.Damn, I get edge speeds when I am on a HSPA network. Dunno whats the problem,called up simple mobile,am not data throttled.Sigh..
Sent from my SGH-T959 using XDA App
man this is scary, but your phone still works at JFD right?
Sent from my SGH-T959 using XDA App
It didn't for a while. Now, both phones are fully functional. I had a copy of the /efs folder of my old phone, but not an image of the partition. The problem is, when the partition gets screwed, you can't write to it, making the /efs useless.
That's why I'm trying to get people to make the backup. It takes a few minutes, but can be a lifesaver. I do believe you can flash a foreign stl3 partition and overwrite the /efs like I did, but unless you had a friend, no one would share it w/ you as it contains their imei info. Better to just back up your own. And if you lose your /efs, game over.
How exactly do you back up a partition?
Very cool of you to post this up. Is there any reason to back up your efs partition if you have no reason to unlock?
<---backing it up anyway.
It's not the unlocking. It seems that over time, some people (such as myself) screwed up the efs partition by just flashing/odin'ing various roms. It shouldn't happen, but it does. Consider that no roms write to the stl3 layer, yet mine was working one day, then one odin later, it didn't. I'm sure the number of people this happens to is quite small, but when it happens, it happens. It's like a 6 mb backup which isn't that big of a deal.
It's better to be safe than sorry.
I did an experiment on my Galaxy Tab, that I move the /efs folder to memory card.
Soon I found the reception goes way worse (at least 10dBm less) and the serial number changed to 00000000, then I immediately copied (restore) the folder and everything was back to normal.
I tried to examine the files with hex editor but I found nothing spectular.
vnamee said:
It's not the unlocking. It seems that over time, some people (such as myself) screwed up the efs partition by just flashing/odin'ing various roms. It shouldn't happen, but it does. Consider that no roms write to the stl3 layer, yet mine was working one day, then one odin later, it didn't. I'm sure the number of people this happens to is quite small, but when it happens, it happens. It's like a 6 mb backup which isn't that big of a deal.
Click to expand...
Click to collapse
That's really weird. I've never really looked into the occurrence because I always assumed it was isolated only to those that did some weird hacking in an attempt to unlock, or to those that were developing and found themselves doing some nasty, nasty things.
I just created efs_dev-block-st13.img and efs-backup.tar.gz so hopefully I'm all safe and sound now.
Thanks again! Once I get beyond GPS stuff I find myself clueless.
draikz said:
How exactly do you back up a partition?
Click to expand...
Click to collapse
You need to read the two links in the OP and download adb. You also need root and busybox.
all you need is to root your phone, such as w/ superoneclick which will put busybox on there. Then all you need is adb.exe.
Open up a command prompt where adb.exe is located. You can adb su or just go adb shell and then su.
The only commands you need are:
cat /dev/block/stl3 > /sdcard/stl3.bin (backs up sector management layer of partition)
cat /dev/block/bml3 > /sdcard/bml3.bin (backs up block management layer of partition)
tar zcvf /sdcard/efs-backup.tar.gz /efs (tars /efs folder)
cp stl3.bin efs.rfs (just makes copy of stl3.bin to new name efs.rfs)
tar -cf efs.tar efs.rfs (makes an odin flashable tar of partition)
I kept a copy of stl3.bin, bml3.bin, efs-backup.tar, and efs.tar.
vnamee said:
all you need is to root your phone, such as w/ superoneclick which will put busybox on there. Then all you need is adb.exe.
Open up a command prompt where adb.exe is located. You can adb su or just go adb shell and then su.
The only commands you need are:
cat /dev/block/stl3 > /sdcard/stl3.bin (backs up sector management layer of partition)
cat /dev/block/bml3 > /sdcard/bml3.bin (backs up block management layer of partition)
tar zcvf /sdcard/efs-backup.tar.gz /efs (tars /efs folder)
cp stl3.bin efs.rfs (just makes copy of stl3.bin to new name efs.rfs)
tar -cf efs.tar efs.rfs (makes an odin flashable tar of partition)
I kept a copy of stl3.bin, bml3.bin, efs-backup.tar, and efs.tar.
Click to expand...
Click to collapse
I've got backups of stl3.bin, bml3.bin and efs-backup.tar.gz
When I try to make the partition an odin flashable tar it tells me: "No such file or directory".
You have to cd into the directory, or else it should be:
cp /sdcard/stl3.bin /sdcard/efs.rfs (just makes copy of stl3.bin to new name efs.rfs)
tar -cf /sdcard/efs.tar /sdcard/efs.rfs (makes an odin flashable tar of partition)
This is kind of old news, but nevertheless important.
Months ago in the Q&A section there were two threads about the importance of the EFS, and how a corrupted nv_data.bin and EFS can cause many problems including losing the ability to use a different carriers sim, yet nobody paid attention to those threads, but I thought the info was vital.
Would using ROM Manager and backing up your current rom, also backup the /efs?
vnamee said:
You have to cd into the directory, or else it should be:
cp /sdcard/stl3.bin /sdcard/efs.rfs (just makes copy of stl3.bin to new name efs.rfs)
tar -cf /sdcard/efs.tar /sdcard/efs.rfs (makes an odin flashable tar of partition)
Click to expand...
Click to collapse
Yeah, I did. I'll do it again and post up exactly what I type and put in. Maybe it's just operator error.
Here ya go.
It might have been operator error because that time I watched efs.tar get written to /sdcard
It should be efs.rfs, not efs/rfs. It's a file, not a directory.
SamsungVibrant said:
Would using ROM Manager and backing up your current rom, also backup the /efs?
Click to expand...
Click to collapse
Nandroid does not back up the /efs partition, at least not that I can tell. All those files in the backup folder are of the various partitions, and efs partition is not part of it.
The reason I made this thread to begin with is because when I had this problem, I looked high and low, and found scant info. In the future, if someone else has this problem, this will come up in a search and won't have some lame magical fix that may or may not work.
vnamee said:
It should be efs.rfs, not efs/rfs. It's a file, not a directory.
Click to expand...
Click to collapse
Pinky slip!!! For whatever reason, it took 3 tries but I finally got it to backup. Thanks for the help! I would never think to back this stuff up. Everyone does Nandroid's like crazy, which is good, but losing this stuff is losing your phone!
Excellent write-up vnamee thank you..........
<RESOLVED> [HELP]N7100_IMEI 0049xx_SN 0000.._Service State "out of service"
Hi Guys. I got this issue after upgrading my Note II to the latest OMEGA ROM v17. After doing the upgrade I was able to use it for a couple of hours and then I realized though there is a signal I am not receiving any internet data (internet icon was gone). I restarted the phone, switch to flight mode back and forth, switch on/off data, but still no luck. I soon realized also that I am not receiving any SMS or call. I thought it was just my carrier so I called them and made a complaint like hell. They said that my line should be fine. From there I started reading for all possible reasons why I am getting this issue. I then found out that my IMEI that is showing on the phone is different on the sticker attached on the battery compartment. Serial number on the phone is 000000000. Service state is "Out of service" though it detects from which network my SIM is. I have tried to flash different custom ROMs and several stock ROMs, but with no go. Tried also different methods on restoring EFS and still no luck. Stupid me, I don't have any backup EFS file or a copy of a nand backup. I was able to get out of the factory mode, wifi and everything else are working except for not receiving any call or SMS because of the bad IMEI, SN, and the Service state "Out of service". I have read some fixes on other threads from a different android phones, but with no avail in fixing mine. I know there's a lot of thread of the same issue, but I want to create my own so I can make sure that people who got ideas on how to fix this is just referring to my "own" issue which will be easier for me to monitor the thread.
So I have tried the following:
- flashed different custom ROMs - no good
- flashed several stock ROMs - no good
- tried EFS Professional.exe - no good
- tried N7100_EFS_Backup_Restore_WIN - no good
- tried ARIZAPatch.apk - no good
- tried SGS tools - no good
- tried com.helroz.GSII_Repair_102.apk - no good
- tried NV-items_reader_writer.exe - I don't know how to make it work
- restored old EFS Backup - no good
- able to find an old NANDroid backup (when it was still working before), flashed it - no good
They say helps the modem from the topic http://forum.xda-developers.com/showthread.php?t=2333216
### --- XXDME4 modem --- ### fix IMEI - -unknown modem
on the XXDME6 base - you can not install old modems,
because it will cause for unknown modem & imei status.
Solution flash - XXDME4 modem
XXDME4 modem
flash via TWRP / CWM
ATTACHED FILES
modem XXDME4 .zip - [Click for QR Code] (4.84 MB, 1209 views)
Click to expand...
Click to collapse
tried that still no go
red_hanks said:
...
Click to expand...
Click to collapse
Read this
victorator said:
Read this
Click to expand...
Click to collapse
Tried that mate but no luck.
in /efs folder contains files *.bak?
aaleo said:
in /efs folder contains files *.bak?
Click to expand...
Click to collapse
yup
move the following files in a backup folder somewhere to your internal SD card
.nv_core.bak,
.nv_core.bak.md5,
.nv_data.bak,
.nv_data.bak.md5,
nv_data.bin,
nv_data.bin.md5
moving them they will be deleted from the efs folder
Reboot.
Now you will have the generic IMEI.
aaleo said:
move the following files in a backup folder somewhere to your internal SD card
.nv_core.bak,
.nv_core.bak.md5,
.nv_data.bak,
.nv_data.bak.md5,
nv_data.bin,
nv_data.bin.md5
moving them they will be deleted from the efs folder
Reboot.
Now you will have the generic IMEI.
Click to expand...
Click to collapse
I have tried that method but it just made my note2 switch to factory mode. Sorry to ask but have you tried that method on your own or you just copy pasted that from somewhere showing that you're willing to help but no certainty if that really works or will just mess up something?
I did it. I did not have IMEI (0000000000) I think you can help it. The last thing that comes to mind to flash the original firmware from sammobile.com through odin.
---------- Post added at 04:39 PM ---------- Previous post was at 04:23 PM ----------
You can restore files via adb
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /efs
cp /mnt/sdcard/.nv_core.bak /efs/.nv_core.bak
cp /mnt/sdcard/.nv_core.bak.md5 /efs/.nv_core.bak.md5
cp /mnt/sdcard/.nv_data.bak /efs/.nv_data.bak
cp /mnt/sdcard/.nv_data.bak.md5 /efs/.nv_data.bak.md5
cp /mnt/sdcard/nv_data.bin /efs/nv_data.bin
cp /mnt/sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
aaleo said:
I did it. I did not have IMEI (0000000000) I think you can help it. The last thing that comes to mind to flash the original firmware from sammobile.com through odin.
---------- Post added at 04:39 PM ---------- Previous post was at 04:23 PM ----------
You can restore files via adb
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /efs
cp /mnt/sdcard/.nv_core.bak /efs/.nv_core.bak
cp /mnt/sdcard/.nv_core.bak.md5 /efs/.nv_core.bak.md5
cp /mnt/sdcard/.nv_data.bak /efs/.nv_data.bak
cp /mnt/sdcard/.nv_data.bak.md5 /efs/.nv_data.bak.md5
cp /mnt/sdcard/nv_data.bin /efs/nv_data.bin
cp /mnt/sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
Click to expand...
Click to collapse
Just tried original firmware but same thing. I am getting frustrated now..
Stupid idea. Maybe it's in the sim card is broken. There is another test for?
aaleo said:
Stupid idea. Maybe it's in the sim card is broken. There is another test for?
Click to expand...
Click to collapse
SIM card is ok. Read my explanation on post #1.
Was able to find an old EFS backup of mine dated January 2013. Tried to restore it but still same issues.
red_hanks said:
Was able to find an old EFS backup of mine dated January 2013. Tried to restore it but still same issues.
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2332913
The Stability update on which is based the rom has some changes in the kernel and the efs folder. Maybe that thread can help you out....hope it does....:good:
red_hanks said:
Tried that mate but no luck.
Click to expand...
Click to collapse
Just wondering, did you tried Kies Emergency restore???
Sent from my GT-N7100 using xda premium
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
hagba said:
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
Click to expand...
Click to collapse
Wow sounds complicated lol hope this don't happen to me!
Sent from my GT-N7100 using xda app-developers app
glevitan said:
Read this: http://forum.xda-developers.com/showthread.php?t=2332913
The Stability update on which is based the rom has some changes in the kernel and the efs folder. Maybe that thread can help you out....hope it does....:good:
Click to expand...
Click to collapse
Done with this with no luck.
aspot72 said:
Just wondering, did you tried Kies Emergency restore???
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Not sure how to do that, never use Kies before
hagba said:
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
Click to expand...
Click to collapse
Like what I have said, found an old backup of mine and it doesn't work. So it's pointless to try this.
I was sleepless (haha) trying to find solution for this. I came across this site and tried the app there. But as you can see on the image below, the button to change the IMEI is grayed out. There is not clear instructions on the site so it is kinda hard what to do in times like that. The app might be for a specific device but if it recognized the IMEI on my phone then it should be able to change it.
Hi Folks,
well i've just managed to recover a Galaxy S3 /EFS without JTAG and without ANY backup other than a dd of the damaged EFS partition which is /dev/block/mmcblk0p3
I am looking for other users with the following conditions
you must have a copy of you efs partition before any modifications , eg. as soon as you efs went wrong you dd'ed /dev/block/mmcblk0p3 and kept a copy before trying anything else. If you worked on the /efs before or select efs clear in oding then this wont work.
I am not going to post the solution yet, it requires more research but it's a possible solution, may even transfer to other devices with exynos and a /efs partition.
Possible ways to confirm efs damage
1. system stays on Galaxy s3 logo and does not show animated boot logo
2. cwm wont mount /efs
3. e3 recovery wont list csc files
if the above is the same as here then let me know.
No PM's please, i want to keep the work public.
darkspr1te
Sorry MODS, please move to Samsung Galaxy SIII , general, miss-post i was tired
darkspr1te said:
Hi Folks,
well i've just managed to recover a Galaxy S3 /EFS without JTAG and without ANY backup other than a dd of the damaged EFS partition which is /dev/block/mmcblk0p3
I am looking for other users with the following conditions
you must have a copy of you efs partition before any modifications , eg. as soon as you efs went wrong you dd'ed /dev/block/mmcblk0p3 and kept a copy before trying anything else. If you worked on the /efs before or select efs clear in oding then this wont work.
I am not going to post the solution yet, it requires more research but it's a possible solution, may even transfer to other devices with exynos and a /efs partition.
Possible ways to confirm efs damage
1. system stays on Galaxy s3 logo and does not show animated boot logo
2. cwm wont mount /efs
3. e3 recovery wont list csc files
if the above is the same as here then let me know.
No PM's please, i want to keep the work public.
darkspr1te
Sorry MODS, please move to Samsung Galaxy SIII , general, miss-post i was tired
Click to expand...
Click to collapse
hi this same problem has happened to me on my s4.
i have all your above listed problems.
However i do have a backup of my efs folder.
please help, thanks
I'm curious with the solution..
Cause many people had problem with efs and not having efs backup...
Sent from my GT-N7100 using xda app-developers app
starscream0 said:
hi this same problem has happened to me on my s4.
i have all your above listed problems.
However i do have a backup of my efs folder.
please help, thanks
Click to expand...
Click to collapse
I've only just got my first bricked S4 in yesterday and only completed it's screen replacement today. The screen is only damged due to owner giving up on it and litting it sit on his desk util something was dropped on it.
Anyway, my point of this is I am not ready to do S4 debrick as I 'am still working on S3.
The key behind my 'possible' recovery method is my solution involves searching for certain MAGIC's in the /EFS backup and also knowing exactly where in the efs image data would be.
For example, key areas of a EFS are in the same sector of the memory each time when looking at a mmcblk0p3 backup image,
i will use mac address as a example.
in the 5 so far efs backups i've examined the mac address is at offset 0x30000, so even if you cannot read the actual efs partition and using fsck on the mmcblk0p3 fail, my part one trick involves just going to 0x30000 and reading the data back. without the efs file system being involved. The same trick i used to recovery the blown boot sector and partition table of the SHV-E160L.
the second trick is to look for keywords within the backup img, example lets say the IMEI always had 0xAA 0xAA 0xAA before it, and the data required was 400 byte, we simply look for 0xAA 0xAA 0xAA in the file and copy it and the next 400 bytes.
the final trick I wont release yet, jumping the gun (as people do) will result in a JTAG brick, it's not perfect, its not a one click solution that we all want, but it's early days yet, but the method does work, i've 5 sammy's in front of me to prove it.
My rep in the Korean galaxy note section should prove I am not threading for likes too
Final note, Its a work in progress and I am using the forum to post my thoughts and look for Guinea pigs and attract other developers to documents the Samsung /efs system.
I am aware that parts are hashed and encrypted, the goal is not decrypting it but to recover the information to revive the device.
I am expecting users to share their /EFS backups with me, but I will not share those files with others to protect the users IMEI,
my issue is i don't have enough differing /efs files to build a bigger picture, what if the file locations was just luck ?
oh, if anyone has a copy of testdisk for arm, please share, i am fighting to get it to compile for arm-eabi-none- grrrrrr.
darkspr1te
Another note: I've not taken into account fragmentation of data in my above post, i was keeping that out of it for now, but i am aware of the EXT2/3 file table setup, how nodes can be split up.
Hi
I have a problem i get this error : E:failed to mount /efs (Invalid argument)
and the /efs file is empty there is nothing there what do i have to do please help
and the other message i get is ( Factory mode is on )
and sometimes it register the network after some hours it got no service and after flash i got back my network it hapend many times.
Please help.
Click to expand...
Click to collapse
The Phone is Dead now !! anyone can help please
habab said:
Hi
I have a problem i get this error : E:failed to mount /efs (Invalid argument)
and the /efs file is empty there is nothing there what do i have to do please help
and the other message i get is ( Factory mode is on )
and sometimes it register the network after some hours it got no service and after flash i got back my network it hapend many times.
Please help.
Click to expand...
Click to collapse
Read this thread.
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
i didn't understand this
2- Create a file with a name 'factorymode' on the sdcard, open it, input 'ON' and then save it. Navigate to the efs folder, create the folder with a name 'FactoryApp' (case sensitive). Finally move the file 'factorymode' you have created above to that folder. Reboot the phone to see if the problem still persists?
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
i have tried that thread still have same problem .
Any help !?!?
..
fffft said:
I'm sure that you find this frustrating. However we are not psychic. Unless you tell us what led up to this and in particular, a step by step, detailed description of what you have tried, how can we discern going on?
What led up to this situation? What exactly have you tried? Step by step, in detail. What exactly is in your /efs folder? Did you create the /efs/FactoryApp/factorymode file as was suggested earlier? Do you have a backup of your /efs partition? Is reactivation lock disabled?
If you actually created the file in the manner described and it didn't succeed and barring something novel in a description of your situation the next step is probably to mount the /efs partition from recovery mode, format it, recreate the /efs folder, remount and reboot so that the efs is rebuilt. But before you do any of that, give us a better description of your situation.
.
Click to expand...
Click to collapse
Hi , i Downloaded a efs backup app and i just pressed on restore before i press on backup , after that the /efs file is empty . i tried to make ( /efs/FactoryApp/factorymode ) with this app : root browser but that didn't work...
i have tried to Flash with many stock room from sammobile but the /efs file still empty .
after reboot i have to connect to Wifi every time i reboot the phone and some time i have Network and some time nott .
..
yes i have backup of the efs ,
the app that i am using just named Root browser with black android pirate icon
.
i maked the directory ( FactoryApp ) then ( file factorymode on the root ) then moved it on FactoryApp , after reboot i find the file emptey again !
and i used this app ( http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325 ) for backup
..
1. i am sorry, my English is so bad !!
2. day 1 , i Downloaded the app Samsung tool and then maked a backup of EFS on External SD-Card ,
3. I maked restore and i had removed the SD-card
4. after that i didn't know that the efs file was damaged , i just installed an room from sammobile ( G900FXXU1ANG9_G900FNEE1ANG5_NEE ) , after the installation was done the phone started but i got an warning massage that says , FactoryMode is on and the wifi was off and only emergency call , i rebooted the phone the wifi was till of but i got back my Network after that i tried many firmware from sammobile
5. o searched on xda and find that it can be the efs but when opened the /efs it was empty.
6. i have the efs-backup on my sd i tried to restore it but nothing happened .
7. i tested that ( Opened this app : https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree ) maked /efs/FactoryApp/ and then file factorymode , ON ) but it can't be moved to FactoryApp when i move or copy it to the folder it is nott there , After rebooting the phone even the FactoryApp directory is deleted .
in my sdcard i found only this ( samsung tool/efs.img )
i tried to make this again
directory ( FactoryApp ) then ( file factorymode on the root ) then moved it on FactoryApp
Click to expand...
Click to collapse
After reastart phone screen is just black !! but the pc is finding it !!! now the phone is dead
..
No i can't boot to anything !! it is just black screen .
No i can't boot to anything !! it is just black screen .
please help me with that.
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
fffft said:
I'm sure that you find this frustrating. However we are not psychic. Unless you tell us what led up to this and in particular, a step by step, detailed description of what you have tried, how can we discern going on?
What led up to this situation? What exactly have you tried? Step by step, in detail. What exactly is in your /efs folder? Did you create the /efs/FactoryApp/factorymode file as was suggested earlier? Do you have a backup of your /efs partition? Is reactivation lock disabled?
If you actually created the file in the manner described and it didn't succeed and barring something novel in a description of your situation the next step is probably to mount the /efs partition from recovery mode, format it, recreate the /efs folder, remount and reboot so that the efs is rebuilt. But before you do any of that, give us a better description of your situation.
.
Click to expand...
Click to collapse
fffft said:
No problem and your patience is appreciated.
Nothing anomalous is showing up in those details so I think we can safely assume that accidentally pressing the restore button rather than backup button simply corrupted your efs partition. All of those questions were aimed at confirming that with certainty, but I understand that this is a lot of work and frustrating for you too. So we'll proceed on that basis.
An efs.img file is an uncompressed efs backup. So try restoring that with your efs program. I have no idea if it is a valid (working) backup, but you aren't going to cause any further harm by trying to restore it. If that works, great and you're done. If not, then we'll go on to rebuild your efs instead.
To rebuild your efs partition we need a custom recovery. So a few last questions.
You are rooted, correct?
Did you use Towel root or CF-autoroot? (I am trying to discern if you have super su /busybox installed)
Are you able to boot to recovery mode (home + power up + power)?
Do you have a custom recovery installed e.g. TWRP or CWM?
If you can answer yes to all four questions, then go ahead and run the following efs repair script. If not, then you'll need to install a custom recovery first. If you're already rooted but don't have TWRP, then it's just a matter of flashing TWRP with Odin from download mode.
In any event, once you have a custom recovery in place you can run this recovery script.
Download the script here. Copy it to your external SD card. Then boot to recovery mode and install the flashable zip file "Brick_Loop_FIX_afterRestoringBackup.zip" that you copied to your Ext SD card.
Then reboot. If you still have any issues, reboot a second time, then let us know if your phone is working properly again.
Credit to Backachu, I believe for saving me the work of having to write a script for you or describe how to enter the commands manually.
The script comes from this thread. http://forum.xda-developers.com/showthread.php?p=47014662
As an aside, there is a minor mystery there. This comes from a Note 3 thread so when I went to modify it to work with your S5, I found that it was already set up for the S5 rather than the Note 3.. so why it is that way in a Note 3 thread is a mystery. Go figure. But I did check and you can use it the way it is.
.
---------- Post added at 07:43 AM ---------- Previous post was at 07:36 AM ----------
I'm not sure what you mean by "dead". If you can boot to recovery & download mode, don't worry about it for now. Otherwise please elaborate.
.
Click to expand...
Click to collapse
..
fffft said:
Don't panic. I'm sure that we can address the new issue, whatever it is.
I need a little information to determine how to fix it.
I understood that your screen is black after you rebooted. What do you mean by the PC can find it. What message do you see on the PC.. the normal USB message when you connect your phone or something else? If something else, what is the exact message from the PC?
Also please do the following
Disconnect the USB cable and remove your battery from your phone for ten seconds. Then replace the battery.
Now press and keep holding the home button. Then press and hold the volume down button as well, then lastly the power button. Keep holding all three until the phone starts (about ten seconds).
Let me know if you do or don't get to the download mode screen when you do that.
If you don't, try it a second time, just in case you weren't continously holding all three keys to get into download mode.
If you still don't, then we want to ensure that the Kies program is not running (if you have Kies on your computer). Then try going to download mode again in the same manner as above, then plug the phone into your computer with the USB cable and start the Odin 3.09 program and tell me what you see on the Odin screen.
.
Click to expand...
Click to collapse
When i plug it in i get a news USB device named : ZUES Flash Device .
i have tried to Hold Home + Volume - + Power nothing happen.
Odin don't find it , and kies program is not running.
..