[Q] Bricked(?) European Galaxy Tab P1000 16Gb - General Questions and Answers

Hi every body,
To start with, in order to avoid asking stupid questions, I've been trying to fix the problem and searching posts for about a month now (ironically, this might have been my mistake, trying everything possible
The answer to the question "why the heck did you do such a stupid thing?!" can be found at the end of the post, for those who has the time for others who are willing to help, and I'd be thankful for any, here are the details:
Device:
European Galaxy Tab P1000 16Gb 3G
Serial Number: you wish! )
Device is rooted and HAD the latest official update provided with Kies
Current state:
- Device stuck at the Samsung Galaxy Tab screen
- No recovery mode (volume-up + power on)
- Download mode still works (volume-down + power on
How did it happen:
It all started as I replaced the framework.jar and a couple of other libraries using adb (why the $$$$ No. 1). this would have been no problem, if I have left usb-debugging switched on after that, but I switched the usb-debugging off(why the $$$$ No. 2). After that I couldn't restore them using adb, logically...
I tried flashing several frameworks with no success. at the beginning, my mistake was using wrong combination of pit-files and roms.
The cause of all evel:
at a certain point I decided flashing with the clear efs option selected (why the $$$$ No. 3). Now I know I shouldn't have done that. especially that I have no backup of the original efs.
What does NOT work
Flashing with Odin or Heimdall theoretically works (I get no errors, the process finishes successfully and the device restarts). Still, it's stuck at the same Samsung Galaxy Tab screen, and still no recovery mode (volume-up + power also shows the same screen).
I tried flashing different samfirmwares and Rotos (using the propper pit-files and stricktly following instructions) to no avail.
I also tried flashing both with the sim and sd-card in the device, and after removing them.
so please HEEEEEEEEEEEEEELP!
why the $$$$ did I have to do this :
1. replacing firmware.jar: I wanted to add native arabic language support and I found this post on the internet providing instructions and jars - of course, it was a mistake to do it, but it's too late for that now, isn't it
2. switching the usb-debugging off: I wanted to copy files to the external card. I have no idea what I was thinking! first of all, I should have first tested whether the stupidity in point 1 have worked, second of all I can still access the sd-card with the debugging switched on! but I didn't know that at the time.
3. clearing the efs: Now, you didn't expect a logical explanation here, did you? ) I was frustrated and said what the heck! Ok ok, have your laugh, call me stupid and all you want - I deseved it
So, once again, any help would be just great!
Thanks in advance,
Moh

If your EFS is gone then you'll need to take the device to Samsung for repair. Samsung may be able to regenerate the EFS data based on the hardware, or they'll have to replace the mainboard.

Benjamin Dobell said:
If your EFS is gone then you'll need to take the device to Samsung for repair. Samsung may be able to regenerate the EFS data based on the hardware, or they'll have to replace the mainboard.
Click to expand...
Click to collapse
I thought so But then again, hope dies last
Thanks anyway

Related

[Q] samsung galaxy player 50

My sister have a Galaxy Player 50 with eclair...this PMP seems to be the same as the galaxy 3 (same resolution...and some other things) so can I flash lestatious or other rom on it ?
This hardware is not a phone...but maybe ?
Maybe I can try to flash...but if the pmp become soft bricked...it's over since i can't found an galaxy's 50 firmware...
Darius, I'm stuck with a brick galaxy player. I can try to flash with a galaxy 3 firmware if you want
Do you know how to make a dump of your device so you can share with me the original firmware?
http://forum.xda-developers.com/showthread.php?p=14493414
I don't know...but I'll try to find
Thanks!
I tried the firmware of galaxy 3, but didn't work
I dont think that its possible, first of all, despite being an android device, it doesnt have radio features, gsm 3g etc, only wifi, there are features that our phone does not support
Anyone found a solution for this yet? Not being able to test this device to it's full potential is really frustrating. Games are laggy and apps just do not run smooth on this one.
Has anyone tried z4root on this? I did and it freezes at "acquiring root shell".
@fedeff: how did you brick it?
Darius_AWS said:
My sister have a Galaxy Player 50 with eclair...this PMP seems to be the same as the galaxy 3 (same resolution...and some other things) so can I flash lestatious or other rom on it ?
This hardware is not a phone...but maybe ?
Maybe I can try to flash...but if the pmp become soft bricked...it's over since i can't found an galaxy's 50 firmware...
Click to expand...
Click to collapse
First root using One click root.
Give these commands in Terminal emulator
su
mount
Check for system partition.Suppose it is stlx (x=6,7,8 etc depending on system partition)
give this command to dump system...
dd if=/dev/block/stlx of=/sdcard/factoryfs.rfs
Copy it from sdcard and upload. I need to check it then i can help u out.
arunmcops said:
First root using One click root.
Give these commands in Terminal emulator
su
mount
Check for system partition.Suppose it is stlx (x=6,7,8 etc depending on system partition)
give this command to dump system...
dd if=/dev/block/stlx of=/sdcard/factoryfs.rfs
Copy it from sdcard and upload. I need to check it then i can help u out.
Click to expand...
Click to collapse
I'd gladly try it as long as Samsung gives me firmware, don't want to end up with a nice looking little brick here.
Is there any way that that an installer/firmware file could be saved in the device for backup purposes or something?
anon3524 said:
I'd gladly try it as long as Samsung gives me firmware, don't want to end up with a nice looking little brick here.
Is there any way that that an installer/firmware file could be saved in the device for backup purposes or something?
Click to expand...
Click to collapse
factoryfs.rfs is ur firmware backup....
@arunmcops: Thanks for the instructions. If someone try this and upload it'd be great for me.
@anon3524: I accidentally reseted the device to factory, trying to fix a problem with wifi (it suddenly stopped working one day).
arunmcops said:
factoryfs.rfs is ur firmware backup....
Click to expand...
Click to collapse
Ok, I am down to do this process you just explained as long as you or anyone explains to me how to recover the device with this "factoryfs.rfs" in case it gets bricked. You'd have to explain with detail how to grab this file and what to do with it etc. Also, if you could give further details on the initial process, that'd be great since a few things are unclear (to a brave noob like me).
Other than that, I am willing to try it to see the results.
BRING IT OON! *warface*
@arunmcops - I've got one of these, so have uploaded the file you wanted here - sorry, not allowed to post links yet:
dl.dropbox.com/u/6491656/Samsung/factoryfs.tar.gz (please don't flash this, its not a full rom)
I haven't made any changes to the base firmware other than renaming a couple of the phone.apk's to .old (cell standby was eating battery, and this device doesn't have a sim).
For fun, i've also uploaded a dmesg log
dl.dropbox.com/u/6491656/Samsung/dmesg.log
One other thing, i think the partition layout might be slightly different on this (might be wrong, don't have the phone) in that the internal sd card is mounted as /sdcard and the external one is /sdcard/sd.
Hope this helps!
Chris
@ctaylr Thanks for uploading the file.
I tried to load it using Odin, but it get stuck while uploading the file. The device is detected, but I think it's not transfering anything.
Is it possible to restore it form sd card?
fedeff said:
@ctaylr Thanks for uploading the file.
I tried to load it using Odin, but it get stuck while uploading the file. The device is detected, but I think it's not transfering anything.
Is it possible to restore it form sd card?
Click to expand...
Click to collapse
Hi...thats probably because it isn't intended as a flashable rom. Its just a dump of the stock firmware so that arunmcops asked to see to see if it had any resemblance of the galaxy 3 f/w, to see what we'd have to do to get a working custom ROM on this device..
Please don't attack it with any kind of Norse God ...especially until there is a confirmed route back to stock. All thats contained in the files is what you have on your device already - so there is also absolutely no point (for now).
If your having trouble with your device now, you could try doing a factory reset or playing about in Kies - i've fixed my device once after I got curious and flashed a custom ROM on here (which fyi completely messed it up - something like E:multi_csc: error: open /efs/imei/mps_code.dat because we dont have an IMEI code on this device) and then got it back working again - unfortunately i can't remember exactly what I did. Otherwise if this doesn't work I'll see if i can make a working stock package for Odin.
@ctaylr, yes I'm having problems with my device. It got soft bricked. I couldn't make it work using Kies. The only thing I can do is to start it in Download mode. If you can make a working package for oding that'd be great
This might help
http://forum.xda-developers.com/showpost.php?p=9515709&postcount=14
Thanks!
@fedeff Ok. i'll have a look over the weekend and see if i can make something that flashes.
Quick questions
1) do you have the 8gb or 16gb version?
2) have you tried going into recovery utils and doing a "wipe data/factory reset?" - you can do this by holding down home, volume down and volume up while turning the unit on - i seem to remember this fixed it for me, but it probably depends on how far Odin got while flashing. If your unit is already bricked, i can't see it doing much further harm
Thks
ctaylr said:
@fedeff Ok. i'll have a look over the weekend and see if i can make something that flashes.
Quick questions
1) do you have the 8gb or 16gb version?
2) have you tried going into recovery utils and doing a "wipe data/factory reset?" - you can do this by holding down home, volume down and volume up while turning the unit on - i seem to remember this fixed it for me, but it probably depends on how far Odin got while flashing. If your unit is already bricked, i can't see it doing much further harm
Thks
Click to expand...
Click to collapse
1) I have the 8gb version
2) By doing "wipe data/factory reset" is how I got it soft bricked. (the device wifi suddenly stopped working, and I thought that would help) After that it kept entering in the recovery mode. Then I tried to flash it with odin, now the only thing I can do is enter the download mode
Thanks again for helping me!
News?
Hi! I also like the others I am interested because my Galaxy player has 50 brick and I need someone to do dump the firmware so I can flash through odin! Please would you be my salvation and many other who have this player and would like to fix without waiting for the assistance of a month
Waiting for an answer I greet and thank all users who want to help me
sorry if English is not correct, but I'm using google translator (I'm Italian)
EDIT:
listen to me: http://forum.xda-developers.com/showthread.php?t=726673 This is the guide on how to get the dump of your fimrware if someone kindly did this process with its galaxy player 50 and then upload the file . tar obtained would help all
I don't think it is as simple as that.
If you fully read that topic above, it tells you. That will ONLY tarball the files in the /system folder. It doesn't dump the the bootloaders, efs or produce the initrd, which is also part of the firmware.
In fact that backup is exactly what i linked to earlier here, and doesn't flash properly through Odin. I don't know Odin very well (i use a ZTE Blade and clockworkmod normally ) but i'm going to take an educated guess it needs all of this information to successfully flash the player, and trying to flash without all of that probably won't work so well.
If i'm wrong, please let me know and i'll do what i can to help.
ctaylr said:
I don't think it is as simple as that.
If you fully read that topic above, it tells you. That will ONLY tarball the files in the /system folder. It doesn't dump the the bootloaders, efs or produce the initrd, which is also part of the firmware.
In fact that backup is exactly what i linked to earlier here, and doesn't flash properly through Odin. I don't know Odin very well (i use a ZTE Blade and clockworkmod normally ) but i'm going to take an educated guess it needs all of this information to successfully flash the player, and trying to flash without all of that probably won't work so well.
If i'm wrong, please let me know and i'll do what i can to help.
Click to expand...
Click to collapse
ok then I'm sorry I read the topic in a hurry and did not realize that you can not do what I say but re-reading now I understand!
ctaylr what do you advise me to do then? wanted to try an get into recovery and restore but I think the 3 keys are disabled enters only download ..
Google traductor sorry

[Q] Tablet PC Duke root

Is there a way to root this tablet ?
http://www.ekoore.com/web/en/product/tablet-2/duke-2/overview-4.html
the same as
http://www.plaisio.gr/Laptop-and-Tablet/Notebook/Tablets-iPAD/Turbo-X-Tablet-Hive-DUKE.htm
Anyone ??!?!??!
You could just try some of the popular methods.
Yeap! I would like to know as well! I have the same tablet.
The OEM firmware name says DUKE_FW_07312
Which is the most common way to root an unknown android phone or tablet?
I know how to root my DHD or any other known mobile device (HTC Desire or Samsung Galaxy S).
But how about an unknown device?
Please some help?
Anyone please help! I don't know how to proceed...
Root method for Duke
NOTE please press the thanks button if you use this source as it is only fair to thank the people who put the effort into helping you. This is a new tablet and it took days not hours to collect and test this. Please press Thanks!
Hi I have had a Duke in Asia for about 6 months fully rooted running 3.2, so it is possible. I have attached all files and instructions in a word document to allow this to happen, but it is as always at your own risk.
Thanks to Krtonsrx8 who supplied the boot image from "Tablet PC Duke" from Europe I have updated the install files to make the installation simpler for the Europeans. I have also modded the boot file from Europe so now there are separate processes for the Asian "Prolink TA8 Tablet" (mine) and the Europe tablet mentioned in this discussion.
Original
http://www.mediafire.com/?rxv3xuadq89lv04
Modified to make the process simpler
http://www.mediafire.com/?9vz4vkk2514ec1z
Good Luck
The Hamster
Than you very much for your help!
I have followed your instructions but I have stuck sfter step "1 Enable ADB.bat"...
I press reset but the tablet does not go into Honeycomb. It just remains black.
And if I run step "3 reset original boot – non ADB” nothing happens as well...
The Tablet does not return to normal nor boots normal...
How do I do a full restore if I need to?
Hi, Have you copued part-7.img across as mentioned in the document to the root directory. If not then please do this and then run 3 reset original boot – non ADB.
Please note you cannot run 3 - .... unless your tablet is in recovery mode. You can check this by going into the Device Manager and note the device with APX. If it is not there then you are not in recovery mode. Hold the recovery button and on button for 3 seconds. Alternatively hold both the reset and recovery for around 10 seconds and it should do the same. Once the APX driver is showing, run the 3 reset ...bat again.
Would you send me a copy of the pert-7.img and I can mod it in Ubuntu and send back to you. This is how the mod works it is a simple flag to allow ADB to run in 1 file.
I ROOTed it! YES!!!
First of all I want to thank you very much for your help!!!
I found out what was going wrong to the step "1 Enable ADB.bat"!!!!
I had to copy 3 files from MY backup folder! “Backup.bct”, “bootloader.img” and “part-7.img”
When I copied these file step 3 worked like a charm and my tablet booted back to normal!
So I thought! Hey! Why not to follow the 1st and 2nd steps again??? And I did!
So now with your help I am a happier owner of the above tablet!!!
Thank you very much again!
Congratulation
No Proplem, It took me about 2 weeks to sort out exactly what to do. If you need to use ADB, you can now do it with Root explorer and edit default.prop in the root directory to enable it.
Would you mind pushing the "Thanks Meter" as I am new to this forum
Also do you have the GSM version of the tablet, if so would you mind uploading the part 2 to part 11 for me. I have the wifi but plan to strip down and install the gsm card, but I need the software.
I had ADB already!
But of course I did not have root access!
And with the latest version of ADB for windows from the Android SDK I can see my device without any problem from windows!!! With the older versions I had "No device found"...
Thax again for your help!
No Problem, Would you please press the "Thanks button" and also do you have the GSM version?
Yes I have the GSM version.
Now that I have rooted do you know where I can find custom roms, kernels, recovery menus for my tablet?
Which tablets are compatible with mine?
Hi That I cannot answer as I only did it to get rid of the advertisements.
Now you are rooted and you have the backup you have the ability to open and manipulate the backups with tools like the attached. But it has to be done in Linux
I have helped you a load, the instructions and information drivers etc took a long time to compile, and I was really hoping that you would return the favour. I have asked several times your version, is it GSM as I am really after a GSM version I can use on my tablet. Can you help?
Of course I will return the favour!
I already have answered to your question about the GSM version.
I have the GSM version.
Unfortunaly the GSM part of the tablet is disabled...
My tablet has the SIM socket but the company that imports this tablet to Greece has the mobile part disabled!
Can I enable it???
To be honest I dont know. my tablet also has the gsm card reader and if it is disabled I would suspect that the unit does not have the gsm module card installed inside, it sounds like you have a wifi unit only like mine. To date in Asia there has not been a working GSM version released, lets see if one is actually released in Europe.
Sorry about not reading the text properly, will have my eyes checked. I am pleased the steps work on the Euro version as well as your firmware is a slightly different number.
Hello! Help me please.
I dont have backup.
I did:
Step 1 -> Step 2 -> Reset.
Tablet does not go into Honeycomb.
Tablet does not return to normal.
How do I do a full restore?
I need the original files (”Backup.bct”, ”bootloader.img”, ”part-7.img”) and step 3 ?
If I need the original files then give me please ”Backup.bct”, ”bootloader.img”, ”part-7.img”.
P.s.
Sorry my lang
ZBEP said:
Hello! Help me please.
I dont have backup.
I did:
Step 1 -> Step 2 -> Reset.
Tablet does not go into Honeycomb.
Tablet does not return to normal.
How do I do a full restore?
I need the original files (”Backup.bct”, ”bootloader.img”, ”part-7.img”) and step 3 ?
If I need the original files then give me please ”Backup.bct”, ”bootloader.img”, ”part-7.img”.
P.s.
Sorry my lang
Click to expand...
Click to collapse
Which version was your firmware?
If it was DUKE_FW_07312 then I can send you the 3 files you need.
khronosrx8 said:
Which version was your firmware?
If it was DUKE_FW_07312 then I can send you the 3 files you need.
Click to expand...
Click to collapse
I do not remember my version firmware
Send me please
Here you are!

[Completed] How do I unbrick my phone?

First of all, I'd like to say that I know very little about how Android, electronics or mobile phones work in general, so everything I've done has been from internet tutorials. Please don't use any jargon as I probably won't know what you mean. ELI5.
A few days ago, I tried to root my phone and it didn't work. As a result the phone went into a boot loop and I didn't know how to fix it. The long and short of it was that I ended up flashing the stock firmware onto my phone and basically doing a complete factory reset. After some time trying this I managed to get the phone to start up and I was able to access the interface and all that. Unfortunately, my WiFi wasn't working (the button would simply turn off whenever I turned it on) so I had no way to download the most recent updates or apps or anything like that. After following several tutorials on how to fix this, such as flashing the modems and bootloader, I still wasn't having any luck. So I tried something that proved to cause even more problems - I tried to install a new kernel. Now my phone won't even boot past the logo. I probably didn't install the right one, but what can I say, it's not very clear which one I need.
Now I'd like to point out that as a layman who just wants his phone to work again, half of the time I don't understand what I'm doing or whether or not I'm doing it right. In other words, I realise that I've probably messed up my phone, but what can I do? I can't take it to a technician because I don't have the money for that, I can't buy a new phone for the same reason and I can't phone up and ask for a replacement because the warranty expired ages ago and I don't have the original documents here.
I've installed the Team Win Recovery Project on my phone and I have Odin installed on my PC as well.
TLDR; yes, I know I'm an idiot and I don't appreciate you telling me. I'd like to reset my phone to how it was before - the normal firmware, the normal kernel and all that, but I'd still like to have root access and keep the TWRP recovery mode too.
Model: Samsung Galaxy S4 GT-I9505
Model name: GALAXY S4 LTE
Country: UK
Version: Android 5.0.1
You'll probably need more information, so if you do just let me know and, if possible, where I can find it.
I have some good news. I managed to flash the firmware again and now I can access the phone again. However, the WiFi problem persists. I've tried looking on the internet for a solution, but I can't find one. I've tried flashing the modem and all that stuff, but it still doesn't work.
Oh, and by the way, I no longer have TWRP and I don't think I have root access anymore either (I had to do a data partition wipe as well).
I'd really appreciate a reply from someone. I've tried everything, but to no avail.
einwaliser said:
First of all, I'd like to say that I know very little about how Android, electronics or mobile phones work in general, so everything I've done has been from internet tutorials. Please don't use any jargon as I probably won't know what you mean. ELI5.
A few days ago, I tried to root my phone and it didn't work. As a result the phone went into a boot loop and I didn't know how to fix it. The long and short of it was that I ended up flashing the stock firmware onto my phone and basically doing a complete factory reset. After some time trying this I managed to get the phone to start up and I was able to access the interface and all that. Unfortunately, my WiFi wasn't working (the button would simply turn off whenever I turned it on) so I had no way to download the most recent updates or apps or anything like that. After following several tutorials on how to fix this, such as flashing the modems and bootloader, I still wasn't having any luck. So I tried something that proved to cause even more problems - I tried to install a new kernel. Now my phone won't even boot past the logo. I probably didn't install the right one, but what can I say, it's not very clear which one I need.
Now I'd like to point out that as a layman who just wants his phone to work again, half of the time I don't understand what I'm doing or whether or not I'm doing it right. In other words, I realise that I've probably messed up my phone, but what can I do? I can't take it to a technician because I don't have the money for that, I can't buy a new phone for the same reason and I can't phone up and ask for a replacement because the warranty expired ages ago and I don't have the original documents here.
I've installed the Team Win Recovery Project on my phone and I have Odin installed on my PC as well.
TLDR; yes, I know I'm an idiot and I don't appreciate you telling me. I'd like to reset my phone to how it was before - the normal firmware, the normal kernel and all that, but I'd still like to have root access and keep the TWRP recovery mode too.
Model: Samsung Galaxy S4 GT-I9505
Model name: GALAXY S4 LTE
Country: UK
Version: Android 5.0.1
You'll probably need more information, so if you do just let me know and, if possible, where I can find it.
Click to expand...
Click to collapse
Hi
We have a dedicated help section for the S4, you'll need to start a new thread and ask there, providing as much info as you can:
http://forum.xda-developers.com/galaxy-s4/help
A [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly thread is also available for you if you dont want to start a new thread.
Good luck.
engloa said:
Hi
We have a dedicated help section for the S4, you'll need to start a new thread and ask there, providing as much info as you can:
http://forum.xda-developers.com/galaxy-s4/help
A [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly thread is also available for you if you dont want to start a new thread.
Good luck.
Click to expand...
Click to collapse
Hi engloa,
It's OK, I've fixed the problem now; I installed a different ROM and now it works fine. Thanks anyway though.

Hard bricked

I just hard bricked my phone, and I'm hoping I can try to get it working again.
I have made backups using flashfire in the past. (I had a few different backups I made).
Prior to getting hard bricked, I was running the PIA firmware, but I was trying to restore from a backup that I had through flash fire, and due to a total rookie move I ended up restoring (or attempting to) restore to a PG1 unintentionally, and well now I can't do anything.
I think I may have a jig at home from a previous samsung phone (I believe an S3), would that work for my S7?
I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2476353
Would that work for me?
I have a macbook pro I can use terminal with, I have a microSD card and reader, and I already have the stock PIA rom on my hard drive.
Is there hope still?
Right now regardless of what key combination I hold down my phone has a black screen.
Any help would greatly be appreciated.
Thanks in advance!
If you can't get into download mode then you don't have much to lose by trying what the other thread suggested.
@sacnotsack, thanks for the response, and that is my intention, however I am missing 1 crucial part to that thread and that is the debrick.img
Can someone with the PIA (G930TUVU4APIA) rom please post a dump of a partial system img for me? If I'm not mistaken, you can dump it with these commands in ADB.
adb shell
dd if=/dev/block/sda20 of=/sdcard/debrick.img bs=4096 count=128
Just to clarify...
sda20 should be the system partition. Any way that's what it is for me.
You can check yourself by doing typing this in ADB:
ls -al /dev/block/bootdevice/by-name
You will get something like this:
lrwxrwxrwx root root 2016-01-08 10:35 system -> /dev/block/sda20
And to get the block size you would type this:
blockdev --getbsz /dev/block/sda20
So the command
"dd if=/dev/block/sda20 of=/sdcard/debrick.img bs=4096 count=128"
If I get this working, I'll compile a nice tut for S7 users and post all the results with files in case anyone else runs into this issue.
Thank you in advance
I don't mean to be an annoyance, but does anyone have any thoughts or could point me to some direction? I know there are a lot of you that are much more knowledgable in this than I am, and all I'm hoping I can get assistance for is if someone can just make a dump of the debrick.img file so I can try to load it on my SD card.
Thanks
Hi, the easiest way to restore back to stock is to download Odin. I think it's Windows exclusive so you'll need bootcamp and install windows. After that, download Odin and extract it. Download stock firmware from androidfilehost.com, then extract. Open Odin and you'll see the options BL, AP, CP, and CSC. The firmware will have 4 or 5 files and will include these labels. Put each respective files into each options in odin. (Sometimes Odin will freeze, but let it do it's thing) After that, go into download mode (hold Volume down, Power, and Home whole turning on). Wait for Odin to recognize your device, if it doesn't, then download Samsung drivers. After it recognizes, press start and wait for the process to finish. That's it! Hopefully I was able to help.
MetalPhoenix45 said:
Hi, the easiest way to restore back to stock is to download Odin. I think it's Windows exclusive so you'll need bootcamp and install windows. After that, download Odin and extract it. Download stock firmware from androidfilehost.com, then extract. Open Odin and you'll see the options BL, AP, CP, and CSC. The firmware will have 4 or 5 files and will include these labels. Put each respective files into each options in odin. (Sometimes Odin will freeze, but let it do it's thing) After that, go into download mode (hold Volume down, Power, and Home whole turning on). Wait for Odin to recognize your device, if it doesn't, then download Samsung drivers. After it recognizes, press start and wait for the process to finish. That's it! Hopefully I was able to help.
Click to expand...
Click to collapse
MetalPhoenix45, thanks for your response. I have a Windows computer as well and I am very familiar with ODIN. The issue is, that in your explanation my guess is you are thinking the phone is in a "soft bricked" mode. The difference between a hard brick phone and a soft brick phone is that in a hard brick phone nothing is recognized when plugged in, it doesn't power on and it also doesn't show any sign of charge when it's plugged into the power.
In a soft brick mode, your phone can be stuck in a boot loop, or at the very least it still shows signs of it getting power. In which case I can just force into download mode and do what you stated above. I don't think that the things you mentioned above would work for me because when I have my phone plugged in to my computer, in device manager it doesn't detect anything. It doesn't even say unknown device or unrecognized hardware. It doesn't see it at all, and I have loaded the Samsung drivers on my pc because ODIN recognized the device prior to my issue.
I do have the stock firmware and everything on my machine, but I just can't get my phone to power or on into download boot even with a JIG.
m0d hipp¥ said:
I just hard bricked my phone, and I'm hoping I can try to get it working again.
I have made backups using flashfire in the past. (I had a few different backups I made).
Prior to getting hard bricked, I was running the PIA firmware, but I was trying to restore from a backup that I had through flash fire, and due to a total rookie move I ended up restoring (or attempting to) restore to a PG1 unintentionally, and well now I can't do anything.
I think I may have a jig at home from a previous samsung phone (I believe an S3), would that work for my S7?
I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2476353
Would that work for me?
I have a macbook pro I can use terminal with, I have a microSD card and reader, and I already have the stock PIA rom on my hard drive.
Is there hope still?
Right now regardless of what key combination I hold down my phone has a black screen.
Any help would greatly be appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Have you had any luck on fixing s7 I've got same issue I've even got device broken down minus the charger port due to cost of screen replacement! Not sure exactly how to test battery itself but every combination of testing battery externally I've nothing any ideas? I'd rather replace the battery vs charger port or is it completely done? This is.the first root I've ever had go wrong and haven't found any solutions yet and been looking since November
Thanks in advance for any advice
On rooted 910v now have a 920t rooted but let's just say my temper got the best of me and we'll will be replacing screen? Oddly enough as many times as the note 4 has been dropped either by myself or son not even a single scratch s7 definitely a pot more brittle!!
crazynate121 said:
Have you had any luck on fixing s7 I've got same issue I've even got device broken down minus the charger port due to cost of screen replacement! Not sure exactly how to test battery itself but every combination of testing battery externally I've nothing any ideas? I'd rather replace the battery vs charger port or is it completely done? This is.the first root I've ever had go wrong and haven't found any solutions yet and been looking since November
Thanks in advance for any advice
On rooted 910v now have a 920t rooted but let's just say my temper got the best of me and we'll will be replacing screen? Oddly enough as many times as the note 4 has been dropped either by myself or son not even a single scratch s7 definitely a pot more brittle!!
Click to expand...
Click to collapse
Unfortunately, I had no luck. I ended up haing to replace the PCB to fix the issue. Basically I learned the hard way that samsung isn't very "dev friendly". I don't blame them, but for any phone enthusiasts that plan on tinkering with their phone if you get the snapdragon version of the S7 vs the exynos version, you WILL run into trouble.
This is because the bootloader can't be unlocked on the SD models. Furthermore, if you get flagged for custom roms your warranty gets void. Over the years I've noticed Samsung is getting more and more strict about this. Honestly if you want a phone that will play nice with modding it, you should look into the google variants, Nexus, or the OnePlus. I can tell you from personal experience, OnePlus plays well with dev users. In fact they don't void the warranty for using custom roms or anything like that; in fact they're very pro and open about supporting the user base and providing a phone that the user is happy with.
Any way, that was my experience. I don't want to go off topic here, so if you have any questions you can PM me if you like, but the short answer is, if you're hard bricked then you will need to replace the motherboard/pcb. I even contacted places to see if they can jtag or jig or anything and they're not able to do it with the snapdragon S7.
bah double post, sorry I can't delete this
Funny you said nexus just ordered 2 two days ago older 7 but 4g and and what not strictly for experimental and ethical purposes of course was actually shocked at the still high priced note 5 Screen tbh but we live and learn!! SOMETIMES? LOL
m0d hipp¥ said:
Unfortunately, I had no luck. I ended up haing to replace the PCB to fix the issue. Basically I learned the hard way that samsung isn't very "dev friendly". I don't blame them, but for any phone enthusiasts that plan on tinkering with their phone if you get the snapdragon version of the S7 vs the exynos version, you WILL run into trouble.
This is because the bootloader can't be unlocked on the SD models. Furthermore, if you get flagged for custom roms your warranty gets void. Over the years I've noticed Samsung is getting more and more strict about this. Honestly if you want a phone that will play nice with modding it, you should look into the google variants, Nexus, or the OnePlus. I can tell you from personal experience, OnePlus plays well with dev users. In fact they don't void the warranty for using custom roms or anything like that; in fact they're very pro and open about supporting the user base and providing a phone that the user is happy with.
Any way, that was my experience. I don't want to go off topic here, so if you have any questions you can PM me if you like, but the short answer is, if you're hard bricked then you will need to replace the motherboard/pcb. I even contacted places to see if they can jtag or jig or anything and they're not able to do it with the snapdragon S7.
Click to expand...
Click to collapse
I am in the same boat, and considering your experience after this sore event, maybe you can help a lot of us guys here in the same situation.
My case is even worst, because, here in my country, there are NO Snapdragons, just G930F Equinoxes.
You may help im providing us lames the debrick.img file, but you must be rooted to do so. This would ve much appreciated.
Another way is to insert a blank 16GB+ SD card on the phone and format it through Odin. You just insert the card on the slot, enter download mode in the phone and load all files in Odin including the .pit. In Odin options select "Re-format" and "T Flash" that will say to the phone to format the ExtSDCard and use the ExtSDCard as destination instead of the internal emmc!
Post the image of the SD, that you can extract it with the Win32DiskImage, and you and your family will be blessed for ten generations. Also save the file in case you mess things again.
There is one method using QFil,but i'm stil trying to asemble all required files and don't now if it will even work. Should work...!!!
Anyway, can you please help us?
Best regards..
PadsPCB said:
I am in the same boat, and considering your experience after this sore event, maybe you can help a lot of us guys here in the same situation.
My case is even worst, because, here in my country, there are NO Snapdragons, just G930F Equinoxes.
You may help im providing us lames the debrick.img file, but you must be rooted to do so. This would ve much appreciated.
Another way is to insert a blank 16GB+ SD card on the phone and format it through Odin. You just insert the card on the slot, enter download mode in the phone and load all files in Odin including the .pit. In Odin options select "Re-format" and "T Flash" that will say to the phone to format the ExtSDCard and use the ExtSDCard as destination instead of the internal emmc!
Post the image of the SD, that you can extract it with the Win32DiskImage, and you and your family will be blessed for ten generations. Also save the file in case you mess things again.
There is one method using QFil,but i'm stil trying to asemble all required files and don't now if it will even work. Should work...!!!
Anyway, can you please help us?
Best regards..
Click to expand...
Click to collapse
Unfortunately, I won't be of much help. If you have the exynos S7, you would need to ask someone else with the same version of your phone for the software because the SD versions would run on different software due to different hardware.
Is there a reason why you don't try sending it out to get serviced so they can replace your PCB ?
I tried to get the debrick.img file a while back as well, but had no luck in doing so and actually I don't have my S7 phone anymore. I bought the OnePlus 3T and it's been working much better for my needs. I'm sorry to say this, but If you have any intention of modding a phone you have 2 options. 1. Get a phone that supports modding and allows you to unlock the bootloader 2. Get the unlocked variant of the phone.
If I have learned anything from my experience, it's that it is incredibly important to do your research. Not only look at the specs of the phone, but look at reviews from other users with the phone. Also if you plan on modding it, go through some threads and see how easy/difficult it is to mod that version of phone you're interested in.
m0d hipp¥ said:
Unfortunately, I won't be of much help. If you have the exynos S7, you would need to ask someone else with the same version of your phone for the software because the SD versions would run on different software due to different hardware.
Is there a reason why you don't try sending it out to get serviced so they can replace your PCB ?
I tried to get the debrick.img file a while back as well, but had no luck in doing so and actually I don't have my S7 phone anymore. I bought the OnePlus 3T and it's been working much better for my needs. I'm sorry to say this, but If you have any intention of modding a phone you have 2 options. 1. Get a phone that supports modding and allows you to unlock the bootloader 2. Get the unlocked variant of the phone.
If I have learned anything from my experience, it's that it is incredibly important to do your research. Not only look at the specs of the phone, but look at reviews from other users with the phone. Also if you plan on modding it, go through some threads and see how easy/difficult it is to mod that version of phone you're interested in.
Click to expand...
Click to collapse
Then i think got stuck, beacause in these forums there is no one willing/able/interested in helping anyone.
I said i'm in the SAME boat == I got an SM-G930T (from T-Mobile) that has a SnapDragon cpu but HERE in my country THERE ARE NO Snapdragons only Equinoxes. If we had such phones here surely i would have done this already, but G930F's won't do, as i have already tried.
So, as you know how i feel about a brand new SM-G930T Bricked, you wold be my last hope. There is no way to send it back to Samsung beacause it was bought from a friend and surely no warranty.
Anyway, best regards and rest in peace
Oh sorry, I misunderstood you. I'd like to think that it's not so much people don't want to try to help out, it's just that there is nothing that can be done for users on the snapdragon device so no one bothers unfortunately. Sorry to hear about this, and it really is unfortunate that you had to go through the same thing I went through with no help. Trust me, if I was able to do anything to provide any guidance I would.
Good luck!

[GUIDE] how to fix EFS Damaged on samsung devices [EASY!]

Edited in 2022 to make it look a bit better!
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Hello people, first I want to say that this is my first guide so it doesn't really look professional but I am doing my best to be clear as possible.
In this guide I will be showing you how to repair your IMEI for free/without Z3X box
So lets get into it.
Its better to start fresh in stock rom
So flash the stock rom first
Now we are really starting,
Step 1) flash TWRP and flash Magisk (if you weren't rooted yet)
Step 2) now search for a custom rom for your phone download it before doing something or just download on pc and move it later
Step 3) now go to mount and select efs or else your efs will be empty at the next step
Step 4) now go to file manager and goto /EFS
Just delete everything in it OR YOU CAN LEAVE Privo data and factory app, you have a backup anyways. *WARNING: DO NOT DELETE THE EFS PARTITION IT SELF, IT WILL MAKE YOUR PHONE NOT BOOTING ANYMORE ONLY DELETE THE FILES INSIDE OF IT SO DELETE ALL FILES*
Step 5) now flash the custom rom for s7 edge i would recommend kingrom, do full wipe at the aroma. You may try to skip this step. There have been comments saying that this guide also works without this step.
Step 6) now reboot your phone, first reboot may take 5-10/15 minutes please be patient and make sure you put your phone in the charger if your battery is low now when your phone is in the welcome screen look or your signal is returned if not just setup your phone sometimes it may take a while for the signal to appear. If your signal is returned then go to phone app and dial *#06# and look or the IMEI matches the IMEI of the box of your phone (make sure you have the original box if you don't have this then open the back of your phone (if you can), there is a sticker label with your s/n and IMEI. If you cannot open the back of your phone, then you will have to trust that the IMEI is right. If everything is functional then you're done with this guide. The next steps are more ''checking'' if everything is alright.
Step 7) If your s/n is ok skip to step 8 if its not right then download a root explorer and go to /efs/factoryapp and edit the serial no file with a text editor and enter your s/n there now save it and IMEI and s/n should be alright
Step 8) Now, for IF the IMEI is correct and everything is fully functional, then delete the earlier made backup of EFS and baseband and make a new one with the working partition, then save it somewhere safe on an external drive, the cloud or on an USB, or just a pc that you will never reset or wipe its data.
Congratulations on getting past step 8. I hope this guide has helped you and that it worked for you. If not then I'm sorry for not being able to assist you. This guide is just me sharing what I did to solve this issue. Good luck on solving your problem if this guide did not work.
If the IMEI is not correct or this guide doesn't work then I can't help you any further except for if you have any questions, however I found a guide for the Samsung galaxy s7/Edge (if you have s8 then click same link because the thread has a link to s8) by Cubz (thanks to Cubz for his guide)
Link: https://www.google.com/amp/s/forum....ow-to-fix-check-drk-imei-issues-t3379516/amp/
S7/E/8 only and some other models as long its an s7 (edge) or s8/+
******* Some tips when you follow the guide*******
1) When you flash combination firmware and it gives you errors then dial *#1234# and look at the cp it should have UX in it (X could be 1,2 or 3 download the correct firmware with the correct bootloader version. You can upgrade from u1 to u2 and u2 to u3 but not downgrade from 3 to 2 or 2 to 1
2) If it didn't work then flash back to stock and fully delete everything in efs folder then retry (this is actually just guide B) its better to follow the guide above
3) If you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
The first method was tested and worked on SAMSUNG GALAXY S7 EDGE SM-935F it may work on other Samsung devices and maybe other android devices but I cannot guarantee that it works on your device
** I take no responsibility for any damaged device, make sure you take a back up so you can go back to the state before you started following this guide!**
If the device gets bricked then always flash back to stock, if you cant enter download mode then just wait until your battery drains and then when you put it in the charger it may start up automatically so enter download mode fast or if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Happy flashing and please confirm in the comments below if it worked for your device or not
Guys please comment or it works on your device or not!
It works for me. But I have to manually change CSC on my phone after original rom flash to fix Network. TGP rom have that option.
I followed your guide and my model name changed from G930F to G930FD and my IMEI is just bunch of zeroes wtv
SOLVED AT LAST - MISSING IMEI and EFS DAMAGED SOLUTION
Hi Guys,
First off, please take GOOD note - I am NOT a techy, just an old boring flashaholic who works in an office and likes pyjamas more than partying. This is my account of me fecking up my phone and finally reaching a solution after three days and most of two nights to a missing IMEI, messed up EFS and non-working phone - hoping that it might help anyone as desperate as I was. You do what you do with your phone and that's your business and I'm not responsible if you mess it up, but my hope is that you have have a brain (that's all I have) and you get some helpful piece of info here as I did from a whole ton of posts I read that finally led me to this.
Next - I am not sure what landed me in this mess. I've seen Superman Rom mentioned a couple of times..I didn't use that but I did use Batman Rom which is by the same Dev. It was great to use, too, so I'm not faulting the Dev by any means. What did happen, though, is that when I flashed other ROMS, maybe 3 or 4 of them following, the Batman splash screen was always there before the new ROM's boot sequence, so there were clearly some residual things of it in there ...so perhaps the same coding is in there and could have had something to do with it, I don't know. The breaking point came when I flashed Sac23 Rom hoping to get Pie on my phone. It was cool but I decided to revert to Resurrection Remix - always my favourite overall - and all of a sudden I get errors.
What should have been a routine "Restore" of my backed up RR ROM via TWRP gave "Error mounting EFS". Reboot, wipe, retry. No joy, same again. A couple of tries to restore the EFS from the backup in TWRP didn't work either.
Next go to is flash "original firmware" (more on this wording later). I had that on my PC (not a phone backup, just the firmware so it's clean copy with no data).
Get Odin out, download mode, correct files in correct boxes, all that standard stuff you can find guides on most places - no joy.
Error showing was "Fail at pm.bin" or something like that. Install aborted.
Try again. This time "Fail at cm.bin" Install aborted. Reboot from recovery also fails. Oh sh1t.
Several more attempts made. I have five different Odin vers. I have seven different firmware vers. I have two USB ports and about 8 Samsung cables. Not a single combination I tried worked.
The XDA heroes will know what to do, I thought. I read and read. And read. And CubZ (who is a hero even if he IS from Lancashire ), says MAKE SURE YOUR PHONE IS RUNNING ORIGINAL SOFTWARE. Well...I kinda did that mostly already...but maybe I need to go RIGHT back to the rubbishy 6.0.1 version that came actually ON my phone when I got it....almost 2 years ago? Who remembers that stuff?? I'm about 18 ROMS down the line now. I was desperate. I'm telling you...I even got out my bank statements to trace when my first payment to my current provider was...I read about firmware numbers and country codes, and I chose one from Sammobile with a build date, country code, unbranded code (which my phone always was) and correct phone model (of course!) as I needed. And it WAS .."the ORIGINAL" firmware.
This time I swear Odin failed me a second BEFORE I pressed the start button! No joy.
Have a flask of coffee and a few valium sandwiches and off I go back to XDA again. I read a loooong series of "Missing IMEI" stuff and there's CubZ again with an IMEI/EFS fix guide guide...brilliant! And it WAS brilliant, and clearly he helped tons of people (kudos, man). But I had messed up MY phone in the time-honoured "right royal" way - worse than his guide could help me. My IMEI was Unknown, my EFS was empty, My SIM wasn't being recognised, no network info or signal...nothing. But genius that he is, he CubZ DID post a Combination file that gave me a base to keep trying on when firmware after firmware had failed almost immediately with errors either of pm.bin/abort or cm.bin/abort.
I almost wore the print out on CubZ guide, I read it so much and tried so many times. Then...I see people saying things about U1, U2 and U3 firmwares. Turns out you shouldn't mix the two. I got that snippet from CubZ too. More research and the little coffee-fuelled connections in my brain are like.....ok....
My ORIGINAL firmware has in its name "U1" and there are similar ones with "U2". Might that be it? My phone has been screaming "DEVICE 2 FIRMWARE 1" (or something like that) at every aborted 'original firmware' installation via Odin and download mode that I've tried, including the EXACT firmware that was on my phone the day it was unwrapped and I danced happily round the room with it.
So if DEVICE 2....FIRMWARE should be 2 maybe? Back to Sammobile. There are firmwares with the same model number, country code, branding info as mine..but with a "U2" where mine said "U1". But...they were Oreo and Nougat where mine was "originally" Marshmallow.
It's now day three in the Big Mother House. My valium and coffee and running out and my communication with the outside world has ceased. I've had about five hours sleep, my food is running low and I cannot call for takeaway cos I ficked my phone up good and proper. I even....get this....start looking up PAID services to fix this. I KNOW, right!!??
I pick up a Nougat firmware from Sammobile...careful to match model, country, branding AND U2 - wondering if I can match it up with CubZ's Combi file as a base to appease Odin......and then maybe revert to my 'original' stock from that to start another attempt at the IMEI/EFS thing.
It loaded. Odin was pleased with my sacrifice. And lo and behold, it had restored the whole lot WITHOUT me having to go any further with stock ROM reversions. It frickin' worked. I got my signal back. My SIM card was detected. My phone number was showing. My IMEI was showing. My E-Frickin-S was mended. I feel like Judd Nelson at the end of Breakfast Club.
So here's the semantic bit that I hadn't known and that is unclear in many many posts. My phone is now working 100% on stock firmware....but is is NOT REALLY the ORIGINAL software - it's the MODEL......COUNTRY......BRANDING.....LANGUAGE - specific firmware but it is Nougat where my original was Marshmallow, and it is a U2 firmware where my original FW was U1. THAT was the killer difference, it seems. Thanks to all of you who posted anything - many many of you - who helped me get this. It's a compatibility issue detail I've never seen or had issues with before.
I now have G930FXXS2DRDI_G930FXEU2DRB5_XEU
Where G930F is the model number, XEU is the country code for UK and Ireland (even though UK is a nation and not a country - just sayin' ) and the U2 sits there hiding in the middle of the second section of the name.
Which gives unzipped files as follows: NOTE - THESE ARE NOT LINKS.
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar.md5
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar.md5
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar.md5
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar.md5
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar.md5
It's Nougat, but that's okay for now; I got my IMEI, EFS, SIM, BIN, probably ENT, RAC, SUV and BMX too, everything
And now, with my working phone, I am gonna phone the local Chinese Takeaway for food, answer all my emails that popped and binged and tinkled at me when it became resurrected, and leave CubZ with huge thanks and all of you guys with the hope that this helps somebody out there.
And maybe look at backing this sucker up and reverting to my Oreo RR ROM I love so much..... I HATE Touchwiz!!!!
Good luck!
:good::good::good:
I was also on similar problem and i lost my efc
Baseband unkwn
Imel null
No signal
I was on s9 port rom by teamexykings and when i update i did dirty flash and my phobe stuck on samsung logo somehow it was boot but it was keeps rebooting than i boot my phone in twrp
When i was trying to wipe system data and dalvic cache
In wipe menu i was shocked to see that it showed internal storage 0mb
I had this problem 1st time
And i have to format my phone to boot properly
U know my big mistake is that i haven't taken a back up of my all apps and my data
After 10-15 min latter it boots
But 2nd shocked was that
I lost my signal my imei my baseband vesrsion unknown
I was so scared to lost my imei
Than i searchon google and i have read lot of articals about restoring efc partition
And than i found similar thread like u have explained
It's really work for me
And this article will help most of device of samsung
And xda user
What i have done
In twrp i mount efc partition
Than in advance menu
File manager
Efc
And i have deleted all of file in efc
(Remember not efc partition it self)
Except privo
Privo data and factory app
Than reboot
After boot my phone i got signal back
I was so happy that it was very easy to do
Your guide will help for many device
shabbir143 said:
I was also on similar problem and i lost my efc
Baseband unkwn
Imel null
No signal
I was on s9 port rom by teamexykings and when i update i did dirty flash and my phobe stuck on samsung logo somehow it was boot but it was keeps rebooting than i boot my phone in twrp
When i was trying to wipe system data and dalvic cache
In wipe menu i was shocked to see that it showed internal storage 0mb
I had this problem 1st time
And i have to format my phone to boot properly
U know my big mistake is that i haven't taken a back up of my all apps and my data
After 10-15 min latter it boots
But 2nd shocked was that
I lost my signal my imei my baseband vesrsion unknown
I was so scared to lost my imei
Than i searchon google and i have read lot of articals about restoring efc partition
And than i found similar thread like u have explained
It's really work for me
And this article will help most of device of samsung
And xda user
What i have done
In twrp i mount efc partition
Than in advance menu
File manager
Efc
And i have deleted all of file in efc
(Remember not efc partition it self)
Except privo
Privo data and factory app
Than reboot
After boot my phone i got signal back
I was so happy that it was very easy to do
Your guide will help for many device
Click to expand...
Click to collapse
You deleted all files and folders from EFS Mounted partition? how is it possible working?
You are awesome man!
I just deleted the files in EFS, restarted without installing custom rom and my IMEI was fixed.
I'm definitely donating. How to donate to you?
Thanks for your great work!
cisekpro23 said:
You deleted all files and folders from EFS Mounted partition? how is it possible working?
Click to expand...
Click to collapse
I think samsung phones are capable of regnerating their efs. But its not working for me on samsung galaxy s6. Guess I am screwed.
Hey everyone, I'm sorry for not responding to anyone in this thread. I've been inactive for a long time. I want to thank everyone for trusting the guide and I hope it has worked for you if you tried following the steps. If you have any questions feel free to ask me.
Also I have edited my guide to improve the reading experience because I see my English was absolutely horrible at the time when I wrote the guide.
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
vigilante said:
Edited in 2022 to make it look a bit better!
Hello people, first I want to say that this is my first guide so it doesn't really look professional but I am doing my best to be clear as possible.
In this guide I will be showing you how to repair your IMEI for free/without Z3X box
So lets get into it.
Its better to start fresh in stock rom
So flash the stock rom first
Now we are really starting,
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Step 1) flash TWRP and flash Magisk (if you weren't rooted yet)
Step 2) now search for a custom rom for your phone download it before doing something or just download on pc and move it later
Step 3) now go to mount and select efs or else your efs will be empty at the next step
Step 4) now go to file manager and goto /EFS
Just delete everything in it, you have a backup anyway *WARNING: DO NOT DELETE THE EFS PARTITION IT SELF, IT WILL MAKE YOUR PHONE NOT BOOTING ANYMORE ONLY DELETE THE FILES INSIDE OF IT SO DELETE ALL FILES*
Step 5) now flash the custom rom for s7 edge i would recommend kingrom, do full wipe at the aroma
Step 6) now reboot your phone, first reboot may take 5-10/15 minutes please be patient and make sure you put your phone in the charger if your battery is low now when your phone is in the welcome screen look or your signal is returned if not just setup your phone sometimes it may take a while if your signal is returned then go to dialer and dial *#06# and look or the imei matches the imei of the box (make sure you have the origional box if you dont have this then open the back of your phone, there is a sticker label with your s/n and imei if imei is not good then skip to step 9
Step 7) now if your s/n is ok skip to step... if its not right then download a root explorer and go to /efs/factoryapp and edit the serial no file with a text editor and enter your s/n there now save it and imei and s/n should be alright
Step 8) Now, for IF the IMEI is correct and everything is fully functional, then delete the earlier made backup of EFS and baseband and make a new one with the working partition, then save it somewhere safe on an external drive, the cloud or on an USB, or just a pc that you will never reset or wipe its data.
Step 9) now for if the IMEI is not correct or this guide doesn't work then I can't help you any further except for if you have any questions, however I found a guide for the Samsung galaxy s7/Edge (if you have s8 then click same link because the thread has a link to s8) by Cubz (thanks to Cubz for his guide)
Link: https://www.google.com/amp/s/forum....ow-to-fix-check-drk-imei-issues-t3379516/amp/
S7/E/8 only and some other models as long its an s7 (edge) or s8/+
******* Some tips when you follow the guide*******
1) when you flash combination firmware and it gives you errors then dial *#1234# and look at the cp it should have UX in it (X could be 1,2 or 3 download the correct firmware with the correct bootloader version you can upgrade from u1 to u2 and u2 to u3 but not downgrade from 3 to 2 or 2 to 1
2) if it didn't work then flash back to stock and fully delete everything in efs folder then retry (this is actually just guide B) its better to follow the guide above
3) if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
The first method was tested and worked on SAMSUNG GALAXY S7 EDGE SM-935F it may work on other Samsung devices and maybe other android devices but I cannot guarantee that it works on your device
** I take no responsibility for any damaged device, make sure you take a back up so you can go back to the state before you started following this guide!**
If the device gets bricked then always flash back to stock, if you cant enter download mode then just wait until your battery drains and then when you put it in the charger it may start up automatically so enter download mode fast or if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Please donate and like this thread if you found this helpful, I have experienced this problem my self and it costed me €60! I said NO its too expansive so then I found this solution and now I am sharing it to the world, I could have let this guide cost €61 but my guides and solutions are free a support would be great for finding this out
Happy flashing and please confirm in the comments below if it worked for your device or not
Click to expand...
Click to collapse
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
bamcarpio123 said:
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
Click to expand...
Click to collapse
Have you created a back up of your efs partition? I have clearly written it in the guide with all caps. If you haven't made a back up, please do so to avoid getting into this situation in the future.
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Click to expand...
Click to collapse
Anyways, I'm sorry to hear you got your self in this situation. Even though it has been a long time since I did this kind of stuff, I still remember that it's possible to fix this issue. I am sure that I have been in this situation before my self and that I somehow managed to get it back. Try to back up all your data, then flash stock rom with CSC file and not Home CSC
vigilante said:
Have you created a back up of your efs partition? I have clearly written it in the guide with all caps. If you haven't made a back up, please do so to avoid getting into this situation in the future.
Anyways, I'm sorry to hear you got your self in this situation. Even though it has been a long time since I did this kind of stuff, I still remember that it's possible to fix this issue. I am sure that I have been in this situation before my self and that I somehow managed to get it back. Try to back up all your data, then flash stock rom with CSC file and not Home CSC
Click to expand...
Click to collapse
I'm sorry for being so stupid because I continued without performing a backup in TWRP, I forgot to back up the EFS, and when I panicked because I was already screwed up, I deleted the efs folder—which is incorrect. I deleted the efs partition before I saw this thread. And now it always says, "failed to mount /efs (invalid argument)" and I've done everything, and it seems like everything is done, I have no idea what to do. I haven't slept for four days and there is still no hope. but my phone is still okay with the stock firmware, but it always restarts. I did almost everything but still nothing
My phone's current csc code is THL (Thailand), but the original is XTC (Philippines), which is my nation, thus I'm curious why THL? of course I flash the right firmware which is the csc is XTC but if I check the CSC the CSC is still THL. I tried to change the csc using tools, but it cannot be change. There may be no hope. I'm worried about losing my phone, yet I'm to blame.
If I lose my IMEI, it won't matter. But the thing is my phone is always restarting every minute.
(can someone know how to disable auto-reboot so i can still use my phone even the EFS is damaged?)
ALSO THANKYOU FOR YOUR REPLY! I APPRECIATE IT!
EDIT: OH I FIX THE EFS PARTITION. NOW MY PROBLEM IS HOW TO GET OUT FROM THIS DARKNESS. HOW CAN I FIX THE IMEI AND BASEBAND WHAT EVER? HMM. BUT I WON'T GIVE UP
bamcarpio123 said:
My phone's current csc code is THL (Thailand), but the original is XTC (Philippines), which is my nation, thus I'm curious why THL? of course I flash the right firmware which is the csc is XTC but if I check the CSC the CSC is still THL. I tried to change the csc using tools, but it cannot be change. There may be no hope. I'm worried about losing my phone, yet I'm to blame.
Click to expand...
Click to collapse
Try to download this tool if you haven't already: https://samfirmtool.com/
I like to use this tool when flashing stock rom because I can download specific versions of stock ROMS and also enter the correct region in it. And to top it off the download is really quick (depending on your download speed of course)
Enter your device model number and at region enter the csc you need. It should download the correct files with the right csc. However, I did find this thread saying it is impossible to change your csc to XTC, but it is always worth a try.
If the CSC is XTC then try to follow this guide again to fix your EFS.
If it is not XTC then try to install a custom rom for your phone that has an aroma installer that allows you to pick a CSC, it might also help with the EFS problem but I am not sure.
EDIT: OH I FIX THE EFS PARTITION. NOW MY PROBLEM IS HOW TO GET OUT FROM THIS DARKNESS. HOW CAN I FIX THE IMEI AND BASEBAND WHAT EVER?
Click to expand...
Click to collapse
Since you have mentioned that your EFS partition is fixed, try to follow the guide again but correctly this time. Maybe it will work this time.
Can you tell me how you checked what your CSC is? And which phone do you have? In case this didn't work.
.
.
vigilante said:
Try to download this tool if you haven't already: https://samfirmtool.com/
I like to use this tool when flashing stock rom because I can download specific versions of stock ROMS and also enter the correct region in it. And to top it off the download is really quick (depending on your download speed of course)
Enter your device model number and at region enter the csc you need. It should download the correct files with the right csc. However, I did find this thread saying it is impossible to change your csc to XTC, but it is always worth a try.
If the CSC is XTC then try to follow this guide again to fix your EFS.
If it is not XTC then try to install a custom rom for your phone that has an aroma installer that allows you to pick a CSC, it might also help with the EFS problem but I am not sure.
Since you have mentioned that your EFS partition is fixed, try to follow the guide again but correctly this time. Maybe it will work this time.
Can you tell me how you checked what your CSC is? And which phone do you have? In case this didn't work.
Click to expand...
Click to collapse
My phone is Samsung Galaxy J8. Before i start to flash custom rom, I took a snapshot of the device's hardware information and discovered that the csc is really XTC. I have completed all the necessary steps. I did everything right, but nothing actually changed. I'm so exhausted that I might just give up. I appreciate your assistance.
If I can't retrieve the imei, it's fine, but unfortunately my phone is always restarting
EDIT: MY PHONE IS NOW FIXED. THE SIMS ARE NOW WORKING, THE SIGNAL IS BACK AND I FEEL SO HAPPY. HOW DO I FIX? WELL I USED THIS METHOD, I DELETE ALL THE FILES FROM EFS FOLDER (NOT THE PARTITION JUST THE FILE INSIDE OF IT) THEN I FLASH THE LATEST STOCK ROM WHICH IS ANDROID 10 BUT THE CSC FILE IS FROM ANDROID 9 AND AFTER THAT I USED TFT SAMSUNG MODULE WHICH IS VERY HELPFUL AND LEGIT TOOL AND ITS 100% FREE!. THEN I FIX THE IMEI AND BASEBAND USING THAT TOOL AND YES THAT SOFTWARE IS A BEAST. AND NOW ITS WORKING PROPERLY. IT TOOK ME 2 WEEKS TO SOLVE THE PROBLEM BUT IN REALITY ITS VERY SIMPLE HAHAHA! IT SAVES ME FROM SPENDING MONEY JUST TO SAVE MY PHONE BUT I DO NOT KNOW THAT I AM THE ONE WHO WILL FIX MY PHONE HAHA HOW COOL IS THAT. JUST DON'T GIVE UP NO MATTER WHAT HAPPENS!
#FVCKTHATZ3XBOX
THANKS TO THIS METHOD AND TO SIR VIGILANTE.
EVERYTHING IS POSSIBLE JUST DONT GIVE UP EVEN YOU'RE TIRED.

Categories

Resources