Related
Hello guys,
I need extremely technical help as no longer know what to do.
I have a Galaxy S7 Edge device, which installed the rom BobCat and everything went well until then.
Later I decided to install another rom to test KingRom that left me unsatisfied, because I thought it had some bugs. Had the TWRP 3.0.0 recovery and decided to upgrade to 3.0.2, everything went well.
At one point I do not remember when or how if was when install back, downgrade to TWRP3.0.0, I do not remember if it was via Odin or TWRP, it happens that the installation stopped halfway. Then unplug the device, restarted in recovery mode and got the following message "E: falied to mount EFS (Invalid Argumen)", I could not restart the device (Boot Loop, and stucked at Samsung Logo) except in Recovery Mode, which also made to stay without IMEI number and Serial Number.
I googled until I came to this tutorial:
http://forum.xda-developers.com/s7-e...ssues-t3379516
I followed all the steps explained, I back up EFS_backup and RADIO_bakcup partitions.
Installed FACTORY BINARY G935, everything went well. After restarted, already had the correct IMEI number but still did not present the S / N.
After all that, i tried to install Stock Firmware via Odin, from here started the problems that could not solve.
In the first attempt Odin stucked in "System" (also used the PIT file with the same CSC ... .i do not know if I was right using PIT?). Restarted the device forcibly, entered the stock Recovery, did a complete wipe and always get this message "E: falied to mount System (Invalid argument), I returned to install Factory Binary, then reboot in Recovery and the same message no longer appeared.
Again I try to install the Stock Firmware and Odin always stucks in System, or NAND writing, or Partition, etc. I've tried various Stock Firmware, with and without PIT files, always without success.
Only Factory Binary that successfully installs. The TWRP via Odin also but when device restarts to enter Recovery Mode always get the message at the top of the display:
"Recovery image signature check Fail"
"Reboot to avoid Warranty bit set."
1. Does the partitions are in good shape? how can I check it?
2- I did good or bad using PIT file?
3- Does the problem is running Windows XP through a Virtual Machine?
4 What else can I do?
In all actions used and am using a Macbook 4.1, OsX Lion 10.7.5, Odin 3.11 Windows XP Professional 32bit through Oracle VM VirtualBox 3.4.38
Device:
Galaxy S7 Edge (SM-G935F) CSC = SWC SwissCom
1st Original Firmware: (I guess was 1?) G935FXXS1APG5_G935FVFG1APF3_SWC
Need help Please
Thank you so very much!
Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!
Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.
SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?
i have tried every twrp but phone stucks on galaxy s7edge screen when trying to access recovery ? plz anybody ?
i have done many posts related to my s7edge g935f , its just kept in the cupboard and cant use it from several months because of the dmverity error , i need to root it and use custom rom plz ?
Put the phone in download mode, use Samsung Smartswitch to reinstall stock rom
surfer3000 said:
Put the phone in download mode, use Samsung Smartswitch to reinstall stock rom
Click to expand...
Click to collapse
i have already done that , it stuck on modem part , secure check radio fail and when i flash without modem , it successfully flashed but root issue , when i flash twrp , it doesnt boot into into twrp and stuck on logo?
I do not believe that you see a "modem" part when using smart switch? Otherwise use Samsung Kies for S7 edge. And do the Firmware Upgrade and Initialization menu item
surfer3000 said:
I do not believe that you see a "modem" part when using smart switch? Otherwise use Samsung Kies for S7 edge. And do the Firmware Upgrade and Initialization menu item
Click to expand...
Click to collapse
i have done every try , it doesn't accept the modem part , i am teally confused about it , so much long time passed and just kept the phone useless, samsung switch is showing it g935f o2u model but not accepting o2u firmware too
suhaibahmad said:
i have done every try , it doesn't accept the modem part , i am teally confused about it , so much long time passed and just kept the phone useless, samsung switch is showing it g935f o2u model but not accepting o2u firmware too
Click to expand...
Click to collapse
Mmmm, before u flash TWRP, u should enable oem unlock on developer option
aditia581999 said:
Mmmm, before u flash TWRP, u should enable oem unlock on developer option
Click to expand...
Click to collapse
yes i have enabled that and also usb debugging
What to do : Reflash the stock firmware , after that is completed , turn off the phone , and install on your pc : the No verify Opt encrypt 5.0 from here:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip
And the SuperSu file from here :
https://download.chainfire.eu/supersu
Now go download the latest Odin, and connect your phone.
Flash the Twrp 3.1.0.0 ( be aware to choose the file for Hero2lte) and reboot to recovery.
DO NOT LET IT BOOT INTO THE SYSTEM.
IF IT DOES , IMEDIATLEY CLOSE THE PHONE AND BOOT INTO RECOVERY .
Once you are in recovery , firstly go to wipe and do a factory reset .
Then connect your s7E to the PC while you are in the TWRP , and copy the SuperSu file and the verity opt oncryption to the storage.
Note: if you have an SD card inserted , copy the files to the SD not the internal storage.
Now , pay attention , If you don't do the next steps in the right order , you may brick your beautiful 800$ phone.
So pay attention , you have to firstly run the No verity encrypt file.
After it's done, go back >reboot>reboot in recovery.
Now search the file and run it (the SuperSu file)
It will take a bit longer to flash the SuperSu.
After it's done , reboot
Note: your phone should reboot 2 times , If it doesn't or it reboots more than 3 times, CLOSE your phone , and repeat the whole process.
IF your phone reboots 2 times , your are good to go .
The first BOOT May take some time (usually around 6 minutes) and it may loop a couple times, DO NOT INTERRUPT THE PROCES !
IF your phone boots up successfully, configure it and run a root checker , it should say : congratulations your device is rooted.
IF IT doesn't, well you have had to mess something up during the process.
Hope that helped , let me know if it did
allahTch said:
What to do : Reflash the stock firmware , after that is completed , turn off the phone , and install on your pc : the No verify Opt encrypt 5.0 from here:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip
And the SuperSu file from here :
https://download.chainfire.eu/supersu
Now go download the latest Odin, and connect your phone.
Flash the Twrp 3.1.0.0 ( be aware to choose the file for Hero2lte) and reboot to recovery.
DO NOT LET IT BOOT INTO THE SYSTEM.
IF IT DOES , IMEDIATLEY CLOSE THE PHONE AND BOOT INTO RECOVERY .
Once you are in recovery , firstly go to wipe and do a factory reset .
Then connect your s7E to the PC while you are in the TWRP , and copy the SuperSu file and the verity opt oncryption to the storage.
Note: if you have an SD card inserted , copy the files to the SD not the internal storage.
Now , pay attention , If you don't do the next steps in the right order , you may brick your beautiful 800$ phone.
So pay attention , you have to firstly run the No verity encrypt file.
After it's done, go back >reboot>reboot in recovery.
Now search the file and run it (the SuperSu file)
It will take a bit longer to flash the SuperSu.
After it's done , reboot
Note: your phone should reboot 2 times , If it doesn't or it reboots more than 3 times, CLOSE your phone , and repeat the whole process.
IF your phone reboots 2 times , your are good to go .
The first BOOT May take some time (usually around 6 minutes) and it may loop a couple times, DO NOT INTERRUPT THE PROCES !
IF your phone boots up successfully, configure it and run a root checker , it should say : congratulations your device is rooted.
IF IT doesn't, well you have had to mess something up during the process.
Hope that helped , let me know if it did
Click to expand...
Click to collapse
thanks for such a nice tutorial , the problem is my phone is o2u and flashing issue in the modem part even i have tried with samsung switch , anyhow that is not a big issue now whenever i only flash ap , the phone boots successfully and i can enable oem unlocking and developer option and when i flash twrp and wants to boot into it , the phone stuck there
suhaibahmad said:
thanks for such a nice tutorial , the problem is my phone is o2u and flashing issue in the modem part even i have tried with samsung switch , anyhow that is not a big issue now whenever i only flash ap , the phone boots successfully and i can enable oem unlocking and developer option and when i flash twrp and wants to boot into it , the phone stuck there
Click to expand...
Click to collapse
I had the same issue to fix.
open smart switch and use the emergency initialization and recovery feature.
it will ask for your model and serial number which is on a sticker on the back of your phone.
Cosmic Blue said:
I had the same issue to fix.
open smart switch and use the emergency initialization and recovery feature.
it will ask for your model and serial number which is on a sticker on the back of your phone.
Click to expand...
Click to collapse
I have tried that , that also stucks in the modem part and give radio fail secure check error , i cant even flash it , i was thinking i will root it and install a custom rom but it cant boot to twrp , and if i just flash the AP part then the device boots successfully and the imei and baseband everything ok . Just the hidden codes not work , its really a weird issue , im really confused about it
suhaibahmad. When you refer to "whenever I only flash AP"you are referring to using ODIN, NOT SMARTSWITCH. There is a difference.
surfer3000 said:
suhaibahmad. When you refer to "whenever I only flash AP"you are referring to using ODIN, NOT SMARTSWITCH. There is a difference.
Click to expand...
Click to collapse
on smartswitch it stucks in the modem part and flash radio fail error on the screen . and now come to odin , if i just flash AP in odin then the phone boots successfully but not good performance and cant even root it
Plz anybody help , my phone is just a piece of .....
Hello,
I wanted to change the bootlogo, I've modify an logoboot file (zip).
I have with TWRP install this zip file but now my tel does not boot anymore, and I no longer have access to TWRP because there is a problem with the logo ...
I still have access to download mode and odin. I tried to install the official ROM but nothing changes. Do you have any ideas how to reset the boot by odin?
I cant factory reset because the recovery is not shown, i see just an black screen.
Slon4564556 said:
Hello,
I wanted to change the bootlogo, I've modify an logoboot file (zip).
I have with TWRP install this zip file but now my tel does not boot anymore, and I no longer have access to TWRP because there is a problem with the logo ...
I still have access to download mode and odin. I tried to install the official ROM but nothing changes. Do you have any ideas how to reset the boot by odin?
I cant factory reset because the recovery is not shown, i see just an black screen.
Click to expand...
Click to collapse
You need to restore param partition.
View attachment SM-A510F-PARAM.tar.zip
Unzip and flash the SM-A510F-PARAM.tar.md5
If you have any other model of A5 you'll have to find it yourself. It's in the BL package of the full firmware.
tys0n said:
You need to restore param partition.
View attachment 4706671
Unzip and flash the SM-A510F-PARAM.tar.md5
If you have any other model of A5 you'll have to find it yourself. It's in the BL package of the full firmware.
Click to expand...
Click to collapse
Thank you very much ! You are my savior ^^
Hello to everybody.
like the title of the thread suggests i have a Samsung S7 Edge (g935f) that isn't able to boot anymore. For what I remember I rooted this phone in 2017, using cf autoroot with Odin, but never installed some other custom rom.
Friday i needed to install upgrades and make a big mistake, I've disabled the unlock oem option. Now the device don't boot anymore, showing the Custom binary blocked by FRP lock when try to boot and even when is in charge, and in recovery mode you can see dm-variety verification failed... error.
I've tried to flash a new stock firmware, downloaded using the Samfirm tool, with odin but stuck in NAND Wright.
I've read that with this two errors, the phone is most likely in a hard brick situation.
Some other informations: in recovery mode I have the following informations:
MMB29K.G935FXXU1BPH6
samsung/hero2ltexx/hero2lte
6.0.1/MMB29K/G935FXXU1BPH6
and at the bottom the "dm-verity" error message
in download mode:
Current binary: Custom
System status: Custom
FRP LOCK: On (that's my fault)
Hope someone can help, and thanks.
Sorry didn't read your post correctly.. since you are still on v1 bootloader
Follow this link :
https://www.techzai.com/fix-drk-device-root-key-for-samsung-galaxy-phones/amp/
In short, extract AP and copy boot.img and system.img to new folder, then rename boot.img to recovery.img and repack AP using only these 2 files (system.img and renamed recovery.img) or maybe repack system+renamed recovery+boot which means we flash boot.img 2 times.. if using only system and renamed recovery doesn't work, and maybe add userdata.img too if adding boot.img doesn't work..and try flashing in official odin (if it doesnt get flashed in official odin.. use prince comsy modified odin)
(before doing this download this firmware and apply above procedure on it :
https://www.sammobile.com/samsung/galaxy-s7-edge/firmware/SM-G935F/EUR/download/G935FXXU1BPH6/89733/ )
(Auto tar 2.0 link use to repack files to tar :
https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file )
Don't tell me if you detect any viruses lol, i don't own any file, just helping to get your phone working again (delete all such files after using them)
Flash bl, csc, cp as usual alongwith this modified AP, use default odin options (don't tick nand erase or any other advanced option in odin)
And dont try to boot into recovery as there will be no recovery .. if lucky .. you will be able to boot phone to go in settings and enable oem unlock option.. if unlucky you will brick your phone even further like efs partition further damage/ nv data corruption (which could be fixed by a box)
So i told you the risks, i will not be responsible for anymore damage.
Note : don't update to newest/latest firmwares or higher bootloader (because it makes rooting and fixing device very difficult as firmware with a higher bootloader version cannot be downgraded to lower bootloader version) and also your dm verity is permanently destroyed so even if you are able to fix your phone by yourself you will always need to keep oem enabled and dm verity disabled to use it.. and upgrading to latest firmware will only create more problems
Good luck ..