I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?
pr10dr said:
I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?
Click to expand...
Click to collapse
You just need to flash the latest G930F for Germany. The firmware code is DBT, it's unbranded so no netweork provider bloatware.
I've attached Samfirm tool. It gets the latest firmware straight from samsung servers version 8.
1. Unzip
2. Run application as admin
3. Check auto box
4. SM-G930F in Model box
4. DBT in Region box
5. Check Update
6. Wait to finish
7. Flash files with Odin
8. New Phone.
I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6
Alright i think i resolved part of the issue as follows:
* i flashed the complete stock firmware as described above
* After flash was done i rebooted again into download mode and installed TWRP as recovery via odin
* I then booted into TWRP and copied the "no-verity-opt-encrypt" in the latest version to the phone
* The zip of "no-verity-opt-encrypt" i then installed with TWRP.
The phone booted up. Factory Samsung Android works but the imei is still shown as empty / unknown.
Some guides suggest to flash a factory combination image but i can not find one for bootloader version 8 which is on my phone.
pr10dr said:
I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6
Click to expand...
Click to collapse
Yes sometimes this happens, try a different firmware like United Kingdom BTU.
Does Odin say Pass?
The updating and erasing screen is normal after flash just leave it.
Once the phone boots on BTU you can either change language to German or flash DBT again.
It's worth checking / reinstalling Samsung drivers. Use different USB port. Odin should be version 13.
As long as you can boot into download mode the problem is fixable.
Thanks for your advice.
I will try the BTU firmware later. Just to check we are on the right track: If i understand you correctly you are saying the lost imei will be "fixed" by installing either the BTU or DBT stock firmware via odin?
Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.
pr10dr said:
Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.
Click to expand...
Click to collapse
OK it sounds like the BL info on the EFS is missing or corrupt.
Just try one more thing before trying to repair the EFS.
Flash firmware again with Odin but uncheck "auto reboot"
When passed in Odin disconnect phone.
Hold volume down+home+power. As soon as the screen goes back move your finger to volume up while still pressing home +power. You want to boot into system recovery. It may take a few attempts.
Once in system recovery, wipe data/factory reset and reboot phone.
Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated
pr10dr said:
Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated
Click to expand...
Click to collapse
Anyone offering money to fix or connect to a server is a scammer, stay clear.
To repair the EFS you have to get the stock firmware back on there or flash someone esle's EFS back up file. You can buy a damaged S7, install TWRP, back up the EFS to the SD card, put that sd card in your phone then restore the efs. Your phone will then take on the identity of the phone the EFS file came from. Effectively you will have a new IMEI number and mac address. As long as the donor phone is not registered on the network your phone will work fine. You cannot have two phones with the same IMEI registered on the network, both will be blocked and black listed. Obviously the donor phone must be exactly the same model as yours.
However the method below should be tried first.
The error with the text "failed to open recovery" means the phone cannot find the partition where the stock recovery file is located.
Now to solve this we can install TWRP with ODIN and that will provide a way to install the stock firmware in .zip format direct from the sd card using TWRP as the recovery method instead of the inbuilt stock recovery which cannot be found.
You should then be left with a phone which has a restored EFS with your original IMEI and other data with TWRP as the recovery tool.
Which ever method you choose TWRP must be installed first.
Related
I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0
I figured it out
planb234 said:
I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0
Click to expand...
Click to collapse
I fianlly figured out the deal with TWRP not flashing.
The change between file systems is what TWRP won't flash.
To flash into the new, the old, or back up property check the file type.
Ext 2, Ext 4, F2FS, etc ...
To get recovery to load install from odin with auto boot disabled, remove battery, than vol + - menu and power.
the steps below..
1. Power off (complete) boot to download.
2. Load Odin, uncheck auto reboot, PDA TWRP. after it installs pull battery to exit.
3. Boot to recovery - wipe- advanced wipe -Repairor Change File System - Check System (go thruough each)
4. Repair and change each to the file type you want to flash
5. repair and or change the files for the zip you are going to flash
6. you have done all the rest before ....
Issue resolved, thread closed, thanks.
Hi There, need some help if you can...any educated and experienced help would be appreciated thanks.
After downloading my stock firmware and extracting via Huawei update Extractor all the image files ( System, user data, Cache, etc) I backed up oeminfo and cust files via Rayglobe Knife and saving the extracted update.app file to my dload folder on SDCard and successfully resetting my phone to factory using the vol+/- and power method I was quietly confident to make the jump and flash a rom the Android 7.0 (N) Nougat beta on Huawei posted by Somboons
I followed the instructions and dirty flashed this thru TWRP as instructed which seemed to go ok until I tried to reboot, the phone booted to stock recovery so I wiped Dalvik, Cache and Factroy reset, this completed and it all went down hill from there, basically now just stuck at boot screen saying that its about to reboot but never moves unless I use button combos
(OK so yes I feel stupid now and I'll beat myself up so you don"t have to, but I reallyt thought that I could always get back to stock via my SDCard)
What I can do...
Phone can only boot to eRecovery ( with WIFI failed message )
I can go into fastboot ( shows Bootloader and FRP unlocked)
What i can't do...
Cant access my update file on SDCard....Trying to boot using vol+/- and power to access my dload/update.app file on my SDCard just freezes at initial boot screen and tells me to push vol up button for 3 second and this takes me to eRecovery where all i can do is reboot or shut down.
I can't adb sideload files " no SU Binary detected"
What I've tried...
I have tried Rayglobe knife UNBRICK option placing my extracted boot, cust, system, recovery .img files but his fails with my PC popping up and saying this operation can't be performed on this PC please contact developer so this fails.
I then tried to fastboot flash all the image files which seemed to work successfully but no changes to the situation.
I have tried to fastboot flash the update.app which went thru the sparse process of all seven files and then come up with error command can not complete ( something in those words)
I have tried to fastboot new stock recovery from my rom as well as TWRP recovery but nothing works even if it says seems to have completed in the adb command prompt.
I have a feeling this is to do with the encryption of the rom and now my system cannot recognise my partition and without recovery I have no way of mounting my sdcard.
Thank god I have my old and reliable Lumia 1520 to fall back on untill I get this sorted.
Any Help would be appreciated....thanks in advance
Are you able to boot into Huawei recovery?
Mickie.C said:
Hi There, need some help if you can...any educated and experienced help would be appreciated thanks.
After downloading my stock firmware and extracting via Huawei update Extractor all the image files ( System, user data, Cache, etc) I backed up oeminfo and cust files via Rayglobe Knife and saving the extracted update.app file to my dload folder on SDCard and successfully resetting my phone to factory using the vol+/- and power method I was quietly confident to make the jump and flash a rom the Android 7.0 (N) Nougat beta on Huawei posted by Somboons
I followed the instructions and dirty flashed this thru TWRP as instructed which seemed to go ok until I tried to reboot, the phone booted to stock recovery so I wiped Dalvik, Cache and Factroy reset, this completed and it all went down hill from there, basically now just stuck at boot screen saying that its about to reboot but never moves unless I use button combos
(OK so yes I feel stupid now and I'll beat myself up so you don"t have to, but I reallyt thought that I could always get back to stock via my SDCard)
What I can do...
Phone can only boot to eRecovery ( with WIFI failed message )
I can go into fastboot ( shows Bootloader and FRP unlocked)
What i can't do...
Cant access my update file on SDCard....Trying to boot using vol+/- and power to access my dload/update.app file on my SDCard just freezes at initial boot screen and tells me to push vol up button for 3 second and this takes me to eRecovery where all i can do is reboot or shut down.
I can't adb sideload files " no SU Binary detected"
What I've tried...
I have tried Rayglobe knife UNBRICK option placing my extracted boot, cust, system, recovery .img files but his fails with my PC popping up and saying this operation can't be performed on this PC please contact developer so this fails.
I then tried to fastboot flash all the image files which seemed to work successfully but no changes to the situation.
I have tried to fastboot flash the update.app which went thru the sparse process of all seven files and then come up with error command can not complete ( something in those words)
I have tried to fastboot new stock recovery from my rom as well as TWRP recovery but nothing works even if it says seems to have completed in the adb command prompt.
I have a feeling this is to do with the encryption of the rom and now my system cannot recognise my partition and without recovery I have no way of mounting my sdcard.
Thank god I have my old and reliable Lumia 1520 to fall back on untill I get this sorted.
Any Help would be appreciated....thanks in advance
Click to expand...
Click to collapse
I have solved so
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
warsangel said:
I have solved so
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Click to expand...
Click to collapse
A very big thanks ....this worked with no hitches except I now have no service now have to find unlock code for sim and get rid of the Ascend 7 splash screen that appears before the original Huawei Boot screen.?
After the above issues with thanks to warsangel's suggestion to use DC_Phoenix, I have managed to get my phone back up and running...got sim working so I now can detect my network and call and text using HCU client.
I now want to get rid of the annoying splash screen on bootup that shows Huawei Ascend spalsh screen before the mate 8 factory Huawei animated boot up screen. I still cannot access my dload folder on SDCard using vol-/+ and power button combo and if I dial in to manufacturers settings using*#*#2846579#*#* when i select upgrade from sd card i get a "PT failed do you still want to continue" if i click yes it re installs the firmware but makes no changes at all. Does any one have any other ideas. Of how to clear the splash screen and get the phone working back on Mate 8 button and bootup settings. Everything else works perfectly just a couple of things that will niggle at me...just want to get it back to out of the box as I have the Original Firmware zip file for this phone and region. cheers
bluheart said:
Are you able to boot into Huawei recovery?
Click to expand...
Click to collapse
Hi blueheart...no I can't, I think this is my problem, I can get to fast boot and I can't fastboot anything now because the boot loader is locked with a different code than the original one that I paid for with dc-unlocker. I have manged thru HCU cLIENT to get my original imei number and serial number but this serial number doesnt show up when I fastboot devices, lists one that come with the Phoenix firmware I flashed which is an Ascend as this was a NXT image closest to my NXT-L09.
My problem still is that I seem to go in to 2G and lose the signal all the time, I'm thinking I need to enter more details in CDMA repair in HCU Client or am I going about this the wrong way???
Oh bru, no idea!
HCU client is good enough. Keep trying dload if your bootloader is locked, it will flash for sure. Phone isn't easy to brick.
bluheart said:
Oh bru, no idea!
HCU client is good enough. Keep trying dload if your bootloader is locked, it will flash for sure. Phone isn't easy to brick.
Click to expand...
Click to collapse
Cheers Mate, managed to get to dload/update now but this doesnt seem to give a full reset, but modem is holding a signal but intermittently will drop into no service. I managed via HCU to re enter my imei and serial but a different serial number showsup in my settings still ??? getting back to where i need to but the signal dropping is a real problem. The next step is to try and get bootloader unlocked....any advice from any one.... if I fastboot flash modem will this be enough to bring my base band back or is there another file I should be looking at? cheers
You need to have cust and oem info of your own area for best signal
bluheart said:
You need to have cust and oem info of your own area for best signal
Click to expand...
Click to collapse
Thanks....I have my backup oeminfo it isnt a .img or .app file it just says oeminfo (type=file) can i fast boot this ? or do I have to use SRKtool as I don't want to unlock bootloader.
DC-Phoenix tool lets me fastboot .img files via backdoor and app files can I convert the oeminfo file to and .img file?
Cheers
How did you do the back up?
You can flash via fastboot
bluheart said:
How did you do the back up?
You can flash via fastboot
Click to expand...
Click to collapse
Backup was done through Rom Manager but the back up isn't an image it's a series of files like system.ext4, boot.emmc.win etc with MD5 info files. I've re-rooted device and tried to use rom manager to restore but when it boots to TWRP recovery nothing happens??? and I can't see any of the files if I go into the twrp folder on the SDcard because they aren't zip or img file.
My biggest problem even after doing full factory reset, wipe cache or install my original firmware update.app file, it doesn't seem to over write the image file that I used to recover my phone with the DC-Phoenix app, every thing indicates that it has been successful, but when I boot up,, It never goes to the stock setup mode where you would normally, choose your region, set your pin etc....it's like my install is only a shell or part of my install is not overwriting the dgtks firmware file I used which was a Huawei Ascend 7. The system re-defaults after rest to this firmware. Anyone help me to get rid of it and get back to my stock please?
I can use my stock update.app but it's not installing over the NXT AL10_M00A095_Factory_firmware_Android_6.0_EMUI_4.0.dgtks that I use ( this was the closest firmware that they had ) I think I need to format my whole system to ext4 ??? especially the partition that it storing this data that is preventing me to get my stock firmware back....any help or advice on this ...thanks
Yes format via Huawei recovery then flash
Or
Root and flash via TWRP after unzipping
bluheart said:
Yes format via Huawei recovery then flash
Or
Root and flash via TWRP after unzipping
Click to expand...
Click to collapse
just to update....I tried formatting and resetting all partitions to ext4 format most of the partitioning was successful with the exception of Systrem and Cust...TWRP would allow me to do these....I did numerous wipes via TWRP and Stock RECOVERY but unfortunately even with a full update.app via sdcard / dload folder and fastboot update.app (my firmware) via DC-Phoenix I couldn't seem to get a full factory stock install, same problems as discussed above and file system always goes to Encrypting screen and then I end up with the Ascend 7 screen and settings with obviously the wrong base band for my region. So I hate to admit defeat, but I've relocked bootloader, reset as much as I can and sent off to the Huawei Workshop to see if they can reset all the partitons back to normal.
Hahaha
Cool, let's see
bluheart said:
Hahaha
Cool, let's see
Click to expand...
Click to collapse
Update: well I dodged a bullet today....I sent my Mate 8 away 5 days ago to the Huawei tech support up the other end of the country and it arrived back today, back to stock and they replaced the main board with no cost to me at all. I was sure that they would call foul play and charge me but I obviously did such a number on the phone and then cleaned up all traces that they couldn't make that call lesson learn't and I see a few other people having similar problems with the Beta Nougat Rom....that you may need to post a big warning and send them to this posting so they are fair warned. I think this thread is done....I might just leave my phone alone and no tweaking for a while
Absolutely true!
XDA is not a playground for kids
You need courage to keep the Mate's balls on fire and get burnt with the nuclear reactions while keeping the blame on self
Hi,
I just "slightly" bricked my S7 (SM-G930F), and I hope someone can help me. My first S7 (which had Superman-Rom installed) had a burnt-out USB port, so I got a brand new replacement. I made a TWRP backup from the old one and installed that on the new one, but I think I made 1 (or even 2) critical mistakes here: I installed TWRP with ODIN on the phone directly out of the box without starting it once, so I never activated the OEM unlock. Furthermore I restored the backup including the EFS partition. The first start-up went fine, just I couldn't unlock the screen (password not valid). After restarting the phone I got the message "Custom binary locked by FRP lock". Using Smart Switch's device initialization, I could get the phone into download mode again and flashed the stock rom (G930FXXU1DQEI with VD2 carrier) via ODIN. But that got me nowhere, after showing "Installing system update" I just got a screen with "No command". Then the phone rebooted again and went directly to the recovery, showing "Successfully verify for dmverity hash tree". Any attempt to restart the phone just shows the Samsung boot logo two times and then I'm back in recovery, where it then shows "No Support SINGLE-SKU, Supported API: 3, dm-verity error, failed code: 0x02". Trying to install TWRP again just triggers FRP lock. I tried both Smart Switch and ODIN several times in different orders, but nothing works.
Here the timeline again:
1. TWRP-Backup old phone (Superman-Rom)
2. First start new phone directly to download mode, installing TWRP (no OEM unlock)
3. TWRP-Restore new phone, EFS included
4. Rom starts, lock screen password not valid
5. Restart
6. FRP lock
7. Smart Switch
8. Stock rom via ODIN
9. "No command"
10. Starting to recovery, dm-verity ok
11. Restart
12. Starting to recovery, dm-verity error
13. Restart
14. GOTO 12
15. ???
Another interesting thing is that at the first start into recovery after flashing the VD2 stock rom, I also get the message "# MANUAL MODE#, Appling Multi-CSC, Applied the CSC-code : DBT, Successfully applied multi-CSC". As I downloaded the VD2 rom, why is it setting the csc to DBT?
Anyone who can help me break the loop?
Yanai1701 said:
Hi,
I just "slightly" bricked my S7 (SM-G930F), and I hope someone can help me. My first S7 (which had Superman-Rom installed) had a burnt-out USB port, so I got a brand new replacement. I made a TWRP backup from the old one and installed that on the new one, but I think I made 1 (or even 2) critical mistakes here: I installed TWRP with ODIN on the phone directly out of the box without starting it once, so I never activated the OEM unlock. Furthermore I restored the backup including the EFS partition. The first start-up went fine, just I couldn't unlock the screen (password not valid). After restarting the phone I got the message "Custom binary locked by FRP lock". Using Smart Switch's device initialization, I could get the phone into download mode again and flashed the stock rom (G930FXXU1DQEI with VD2 carrier) via ODIN. But that got me nowhere, after showing "Installing system update" I just got a screen with "No command". Then the phone rebooted again and went directly to the recovery, showing "Successfully verify for dmverity hash tree". Any attempt to restart the phone just shows the Samsung boot logo two times and then I'm back in recovery, where it then shows "No Support SINGLE-SKU, Supported API: 3, dm-verity error, failed code: 0x02". Trying to install TWRP again just triggers FRP lock. I tried both Smart Switch and ODIN several times in different orders, but nothing works.
Here the timeline again:
1. TWRP-Backup old phone (Superman-Rom)
2. First start new phone directly to download mode, installing TWRP (no OEM unlock)
3. TWRP-Restore new phone, EFS included
4. Rom starts, lock screen password not valid
5. Restart
6. FRP lock
7. Smart Switch
8. Stock rom via ODIN
9. "No command"
10. Starting to recovery, dm-verity ok
11. Restart
12. Starting to recovery, dm-verity error
13. Restart
14. GOTO 12
15. ???
Another interesting thing is that at the first start into recovery after flashing the VD2 stock rom, I also get the message "# MANUAL MODE#, Appling Multi-CSC, Applied the CSC-code : DBT, Successfully applied multi-CSC". As I downloaded the VD2 rom, why is it setting the csc to DBT?
Anyone who can help me break the loop?
Click to expand...
Click to collapse
Hi
Main issue I see is:
Install EFS partition from one phone to the other.....lets hope you did not mess the IMEI , EFS are device specific.
OEM unlock maybe an issue but Odin flashing should solve it ( most of the times)
You said you flashed with ODin , what file you used CSC or home_csc? if you used CSC did you selected re partition?
MAX 404 said:
Install EFS partition from one phone to the other.....lets hope you did not mess the IMEI , EFS are device specific.
Click to expand...
Click to collapse
Is there a way to restore the original EFS partition? ODIN has the option to clear the EFS, but I could not find any information on what this does, only "stay away from it!!!!!".
MAX 404 said:
You said you flashed with ODin , what file you used CSC or home_csc? if you used CSC did you selected re partition?
Click to expand...
Click to collapse
I tried both, but mainly CSC to also do a factory reset, and I also tried to repartition. Only thing I still haven't tried is "Nand Erase All", because "stay away from it!!!!!"
Yanai1701 said:
Is there a way to restore the original EFS partition? ODIN has the option to clear the EFS, but I could not find any information on what this does, only "stay away from it!!!!!".
I tried both, but mainly CSC to also do a factory reset, and I also tried to repartition. Only thing I still haven't tried is "Nand Erase All", because "stay away from it!!!!!"
Click to expand...
Click to collapse
There are ways to restore the EFS , the question is do you have a copy of the original EFS??
Do not use option in Odin you do not know about.... re partition is known did you use it?
check this info regarding that
Yes, I already tried to repartition. And no, I don't have a backup of the original EFS, I accidentally restored it because I overlooked that is was checked in TWRP (or just checked everything that was there without really looking?).
Regarding Odin it's just sad that nobody seems to know what some of the options really do, maybe some combination could help me.
Yanai1701 said:
Yes, I already tried to repartition. And no, I don't have a backup of the original EFS, I accidentally restored it because I overlooked that is was checked in TWRP (or just checked everything that was there without really looking?).
Regarding Odin it's just sad that nobody seems to know what some of the options really do, maybe some combination could help me.
Click to expand...
Click to collapse
long shot but you could try this.
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
or may have to take it to a service shop ( a good one) they have special boxes with special options to fix this kind of problems
Thanks for your help Max, but it seems I have to pick your last option and search for a service shop. I downloaded the latest available combination firmware, but after installing it the phone gets stuck on the boot screen with displaying "ASV TBL VER = 10; ASV TBL VER2 = 0; NAD: PASSED; NAD ACAT: FAILED; RPMB PROVISIONED" on the top. Reverting to the normal firmware brings me back to the recovery loop. The problem is also that there seems to be no combination firmware for Nougat, all the files are for Marshmallow. Not sure if this is the reason that the phone gets stuck, but I think it likely.
Hey guys,
I tried to root my S6 yesterday - so I entered Download mode and flashed TWRP onto it. I ran into the known problem with android replacing the recovery app, so i disabled the auto restart in Odin, and voila - I had twrp access. Couldnt get SuperSU onto the device because Im using full disk encryption (havent solved that yet) - and I couldnt get past ADB sideloading the SuperSU thing. Anywho - I tried a few (compatible) TWRP images - and all of a sudden, I am unable to boot the phone, nor enter download/recovery mode
Its stuck on the Samsung Galaxy S6 boot screen, with a little red text saying "Recovery is not seandroid enforcing" Power+home+vol down boots it into the same state, and power+home+vol up doesnt do anything.
Edit: I got it into download mode by following guide on https://forum.xda-developers.com/s7-edge/help/recovery-seandroid-enforcing-t3416719/page2 .
Erh, not entirely solved - it still wont boot. Stuck in a boot loop. I can access TWRP now - but as the "SDCARD" is encrypted (and i cant see any option to decrypt it!) - i cant really fix anything.
Would it be an option to flash stock recovery? (And where do I find that? I see that other people are having problems finding that as well)
I found https://forums.oneplus.net/threads/encrypted-phone-and-now-cant-use-twrp.117119/page-2 - which suggests that TWRP should be able to handle an encrypted volume..so why isnt it prompting for decryption password?
ad9fe7uhasf said:
Erh, not entirely solved - it still wont boot. Stuck in a boot loop. I can access TWRP now - but as the "SDCARD" is encrypted (and i cant see any option to decrypt it!) - i cant really fix anything.
Would it be an option to flash stock recovery? (And where do I find that? I see that other people are having problems finding that as well)
I found https://forums.oneplus.net/threads/encrypted-phone-and-now-cant-use-twrp.117119/page-2 - which suggests that TWRP should be able to handle an encrypted volume..so why isnt it prompting for decryption password?
Click to expand...
Click to collapse
It won't boot it up even when you flash stock recovery. Because you messed up dm-verity.
If your device SM-G920F;
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920F
Region: XEF
Auto: Selected
Manual: Unselected
Binary Nature: Unselected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download full firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this; (even if you have another one)
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press AP and select file which starts with G920 from downloaded (from Samfirm) and extacted zip folder.
Connect your phone to your PC in download mode (the "Downloading..." screen) and click "Start" on Odin.
When you see "PASS" text on Odin, disconnect the cable.
This method will reflash and update the firmware of your device WITHOUT messing any personal data on your device.
forumber2 said:
It won't boot it up even when you flash stock recovery. Because you messed up dm-verity.
If your device SM-G920F;
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920F
Region: XEF
Auto: Selected
Manual: Unselected
Binary Nature: Unselected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download full firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this; (even if you have another one)
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press AP and select file which starts with G920 from downloaded (from Samfirm) and extacted zip folder.
Connect your phone to your PC in download mode (the "Downloading..." screen) and click "Start" on Odin.
When you see "PASS" text on Odin, disconnect the cable.
This method will reflash and update the firmware of your device WITHOUT messing any personal data on your device.
Click to expand...
Click to collapse
Amazing!! Thank you so much - no one else has mentioned that beautiful utility (Can I buy you a beer?) Ive managed to make it boot kinda normal again - but I think the image isnt quite right - there are constant popups with "IMS Service has stopped" and "com.sec.epdg has stopped" which renders it pretty much unusable. Ive tried clearing the cache partition.
ad9fe7uhasf said:
Amazing!! Thank you so much - no one else has mentioned that beautiful utility (Can I buy you a beer?) Ive managed to make it boot kinda normal again - but I think the image isnt quite right - there are constant popups with "IMS Service has stopped" and "com.sec.epdg has stopped" which renders it pretty much unusable. Ive tried clearing the cache partition.
Click to expand...
Click to collapse
I think you should backup everything you can and wipe data from stock recovery.
forumber2 said:
I think you should backup everything you can and wipe data from stock recovery.
Click to expand...
Click to collapse
Yes - definitely! But As the popups are appearing ALL the time (its practically impossible to use the device) - Its close to impossible to enter Private Mode to extract data. You seem to know a bunch
I have tried connecting a physical keyboard to enter private mode password - no luck. The popup ruins most input fields or cancels them. Tried working with adb, but I dont think theres a way into private mode?
As the device is not rooted, I dont think I can copy the private data folder away from the device via the shell. Safe Mode didnt help either - they keep appearing...stupid popups
I have managed to do a adb backup of the device - but that does not include Private Mode data, right?
Any last minute ideas?
(also - im serious about the beer )
ad9fe7uhasf said:
Yes - definitely! But As the popups are appearing ALL the time (its practically impossible to use the device) - Its close to impossible to enter Private Mode to extract data. You seem to know a bunch
I have tried connecting a physical keyboard to enter private mode password - no luck. The popup ruins most input fields or cancels them. Tried working with adb, but I dont think theres a way into private mode?
As the device is not rooted, I dont think I can copy the private data folder away from the device via the shell. Safe Mode didnt help either - they keep appearing...stupid popups
I have managed to do a adb backup of the device - but that does not include Private Mode data, right?
Any last minute ideas?
(also - im serious about the beer )
Click to expand...
Click to collapse
Yes, ADB backup won't include private folder.
Can you tell me which CSC code seems active when you boot into stock recovery?
Thanks for beer by the way, you keep it
forumber2 said:
Yes, ADB backup won't include private folder.
Can you tell me which CSC code seems active when you boot into stock recovery?
Thanks for beer by the way, you keep it
Click to expand...
Click to collapse
CSC code is NEE (Sweden?) (im danish though). It says - Appling Multi-CSC. XEF seems to be france. Could that be the reason?
ad9fe7uhasf said:
CSC code is NEE (Sweden?) (im danish though). It says - Appling Multi-CSC. XEF seems to be france. Could that be the reason?
Click to expand...
Click to collapse
I couldn't get it.
So, NEE was your original CSC code but now, it's XEF.
Am I right?
ad9fe7uhasf said:
CSC code is NEE (Sweden?) (im danish though). It says - Appling Multi-CSC. XEF seems to be france. Could that be the reason?
Click to expand...
Click to collapse
If this page is correct: http://www.all-things-android.com/content/using-private-mode-galaxy-s5 - if rooting the device is an option (that was all I wanted in the beginning, heh) - I could just copy the files out plain and easy.
ad9fe7uhasf said:
If this page is correct: http://www.all-things-android.com/content/using-private-mode-galaxy-s5 - if rooting the device is an option (that was all I wanted in the beginning, heh) - I could just copy the files out plain and easy.
Click to expand...
Click to collapse
You should root the device before encrypt the device
Ok, do the same procedure I've wrote above BUT in SamFirm, write NEE instead of XEF on Region Code section.
Let's see if this change will work.
forumber2 said:
You should root the device before encrypt the device
Ok, do the same procedure I've wrote above BUT in SamFirm, write NEE instead of XEF on Region Code section.
Let's see if this change will work.
Click to expand...
Click to collapse
Hi again.
The reflash didnt work. Im gonna see if I can find a rooting guide that actually works. When rooted, I should have access to all data. And after root, Ill reflash with LineageOS and start from scratch.
UPDATE: I followed the guide on https://www.tomsguide.com/us/samsung-galaxy-s6-guide,review-2856-3.html . It seemed to work until the first boot:
"Verification failed.
Unable to restart your device. The integrity verification has failed. You nede to reset your device to factory default settings. THis will erase all your data".
I then proceeded to follow your guide again - but it still did not boot. So I think I've hit the final brick wall :/
ad9fe7uhasf said:
Hi again.
The reflash didnt work. Im gonna see if I can find a rooting guide that actually works. When rooted, I should have access to all data. And after root, Ill reflash with LineageOS and start from scratch.
UPDATE: I followed the guide on https://www.tomsguide.com/us/samsung-galaxy-s6-guide,review-2856-3.html . It seemed to work until the first boot:
"Verification failed.
Unable to restart your device. The integrity verification has failed. You nede to reset your device to factory default settings. THis will erase all your data".
I then proceeded to follow your guide again - but it still did not boot. So I think I've hit the final brick wall :/
Click to expand...
Click to collapse
You CAN'T root it after you encrypt the device. I think you messed up the data partition now.
If reflashing the firmware didn't work too, you have no choice but wipe the data.
Yup, I think youre absolutely right. I wish I had found that information before I began
Thank you so much for the help. We need more people like you in the community
If you mean "The reflash didnt work" as in there was an error flashing hidden.img, and if you simply want to regain access to your encrypted data, you may be in luck.
I found myself in the same exact situation. What I did was use 7zip to extract the .tar.md5 file, and use 7zip again to create another .tar file that didn't include hidden.img. Then, I simply used Odin to flash the new file. I made sure that the firmware I was flashing was the exact, same firmware that was on my phone before this happened. Just search on Sammobile.
The key to regaining access to your encrypted data was to simply have your system marked as "Samsung Official", which you can check by going into download mode and looking at "current binary". If it says Custom, Verification fails as far as I can observe. This is true even if stock recovery says that dm-verity is okay. As long as you modified your system somehow (boot and recovery are the only ones I've tested), verification fails.
Since I regained access to my data, I may as well backup everything and start from a freshly reformatted /data, since everyone says that one should root before encrypting.
Verification Failed
Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data
Click to expand...
Click to collapse
ad9fe7uhasf said:
Hi again.
The reflash didnt work. Im gonna see if I can find a rooting guide that actually works. When rooted, I should have access to all data. And after root, Ill reflash with LineageOS and start from scratch.
UPDATE: I followed the guide on https://www.tomsguide.com/us/samsung-galaxy-s6-guide,review-2856-3.html . It seemed to work until the first boot:
"Verification failed.
Unable to restart your device. The integrity verification has failed. You nede to reset your device to factory default settings. THis will erase all your data".
I then proceeded to follow your guide again - but it still did not boot. So I think I've hit the final brick wall :/
Click to expand...
Click to collapse
Update: I found out that, if you do encounter the "Verification Failed" message, you don't need to flash everything with the fresh bootloader. Instead, flashing the stock version would work fine.
For example, if you flashed TWRP and encountered the verification failed message (read-only mode), then flashing the stock recovery solves the error message and you can boot.
I've tried flashing the Unknown (XAS) version of the N920PVPS3DRD1 firmware coming from the N920PVPS3DRD1 Sprint (cdma) Through odin. It got stuck on finding pit file, so I closed odin and now my device is stuck in a bootloop. It stays on samsung galaxy note 5 screen then restarts and goes to TWRP. When I go into download mode it doesn't display any information in the top left. I have a backup of the sprint version which I have tried restoring to (I haven't wiped any data in fear of losing the backup) However I have the backup on my PC too which I should be able to send to the device using ADB. This didn't work. And it is still stuck in a bootloop. Does anyone know how to solve the issue? Thanks.
Download the correct 4 file package(I like Android File Host) and reflash using Odin. Edit the Odin .ini file to unlock all of the options, and then make sure you check the boxes that say nand wipe, phone efs clear, and bootloader update. Also extract the .pit file and insert that into the pit section. If it doesn't flash fully the first time, uncheck all of the boxes, reboot Odin mode, and flash again. This almost always solves my flashing issues.