s7 edge - Samsung Galaxy S7 Edge Questions and Answers

hey guys . i have a samsung s7 edge today i restarted my phone then i saw on the top of display ( custom binary blocked by frp lock ) then i opened youtube and i saw many videos they says flash the original firmeware of your device then i opened odin and i flashed the file . when i opened my device . on the display i saw no command on screen then when i opened recovery mode device says fail to open recovery cause(no such file or directory) i tried to install twrp ( custom recovery ) . in odin says fail and on device says ( custom binary blocked by frp lock ) i cant open the device when i opening device says error then it restart .. please help me i dont know what i should do .................................................

When you flashed from Odin did it go through all the process from boot, system to bin? Did it say Pass? If install worked, it automatically reboots phone, install firmware and prompts you to select language and continue with installation. Doesn't sound as this happened with you. Were you in download mode? Odin either passes, or fails.
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------
elv1503 said:
When you flashed from Odin did it go through all the process from boot, system to bin? Did it say Pass? If install worked, it automatically reboots phone, install firmware and prompts you to select language and continue with installation. Doesn't sound as this happened with you. Were you in download mode? Odin either passes, or fails.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
FPR lock would not stop Odin download.
Sent from my [device_name] using XDA-Developers Legacy app

when i flashing the twrp every thing going good then in the last of instaltion
when i flashing the twrp every thing going good then in the last of instaltion in odin saying fail ana on device says custom binary blocked by frp lock @elv1503

leonardo8877 said:
when i flashing the twrp every thing going good then in the last of instaltion in odin saying fail ana on device says custom binary blocked by frp lock @elv1503
Click to expand...
Click to collapse
You just need to flash stock from via Odin to get your phone up and running. Firmware comes as a zip file. Extract it. It has four elements. Import these 4 elements into Odin. The 4th element in Odin is CSC.. The firmware has CSC and Home CSC. Select Home CSC to save your data. Put phone into download mode, connect to PC, and flash firmware. You don't need TWRP or Recovery Mode.

@elv1503 . i tried all the ways to fix it but finally i found the method . i installed on my pc the crack virsion of miracle box then i choesed samsung then i open frp unlock . after then i flashed the twrp because its saying fail to open recovery such no files to open .... then i installed no verity opt encrypt file and the phone camed to life again .. thanks to your help @elv1503v.

leonardo8877 said:
@elv1503 . i tried all the ways to fix it but finally i found the method . i installed on my pc the crack virsion of miracle box then i choesed samsung then i open frp unlock . after then i flashed the twrp because its saying fail to open recovery such no files to open .... then i installed no verity opt encrypt file and the phone camed to life again .. thanks to your help @elv1503v.
Click to expand...
Click to collapse
Glad you got it fixed.

Related

Samsung Galaxy A9 Software Update Faliure

I own a Samsung Galaxy A9
I tried to update the firmware from the original lollypop to (maybe) marshmallow
I failed to update using the software, so i updated using smart switch
It went wrong, the update failed.
Now the blue screen with "An error has occured while updating the device software. Use the emergency recvery function in the Smart Switch PC software" appears..
I tried the emergency recovery but it also failed
The only button combination that worked is the power button + volume down --> It restarted, but the same screen appears
I even tried refresing the software with Odin, but it failed.
The phone says "FRP is enabled, not allow download non-FRP aboot binary"
Odin doesn't work
The samsung customer service in singapore (my country) is not able to help. Would really appreciate it if somebody could help me with this.
-Michael
Are you able to get into bootloader ? If so, you can try using ADB to remove OEM Unlock.. There should be bootloader unlock instructions for Samsung in these forums..
Sent from my SM-A9000 using XDA-Developers mobile app
I take it you tried to update via odin originally.
If you give more details if what part of the flashing process failed we may be able to help.
Was it a particular partition that failed to flash.
A screenshot of the failed flashing process with odin would be helpful.
Also you may be able to remove the blue error screen by flashing the stock recovery with odin.
Extract it from the stock firmware, convert it to a tar archive then flash it with Odin.
Boot to recovery and wipe cache.
That itself may get you booting.
There is also Twrp available for your device which could do the same thing.
I had the same issue.. i fixed it yesterday.. what i did was.. go to developer options.. enable OEM unlock.. download CROM from galaxy apps store.. it gives a warning msg regarding unlocking the device.. that isnt an issue..just press ok.. and it will say ur device is unlocked.. and then try reflashing firmware from ODIN.. and then i did root my A9 and its working pretty nice since yesterday..
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
and also.. if u try to update to marshmallow.. u may get errors.. i assume thats because that is an update from CHINA..NOT from HONGKONG.. i suggest everyone to wait untill hongkong version of Marshmallow is released.. even i flashed marshmallow..had some error and my device was not booting and just booting into recovery with some error like drm something like that.. and then i flashed a hongkong lollipop 5.1.1 version and then my device booted..
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
regarding the FRP locking system. do one thing.. first back up everything.. go to backup and reset option.. do a factory reset.. it will wipe everything so do make sure u backup everything.. it will reboot the device into recovery.. do full factory reset.. reboot again.. finish.. i did this.. FRP LOCK is gone.. am happy
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------
do all the steps as i said.. Insha Allah all your problems and errors will be solved..
Sent from my SM-A9000 using XDA-Developers mobile app
Mikekaipas said:
I own a Samsung Galaxy A9
I tried to update the firmware from the original lollypop to (maybe) marshmallow
I failed to update using the software, so i updated using smart switch
It went wrong, the update failed.
Now the blue screen with "An error has occured while updating the device software. Use the emergency recvery function in the Smart Switch PC software" appears..
I tried the emergency recovery but it also failed
The only button combination that worked is the power button + volume down --> It restarted, but the same screen appears
I even tried refresing the software with Odin, but it failed.
The phone says "FRP is enabled, not allow download non-FRP aboot binary"
Odin doesn't work
The samsung customer service in singapore (my country) is not able to help. Would really appreciate it if somebody could help me with this.
-Michael
Click to expand...
Click to collapse
Pls help me, i bought samsung galaxy A9 SM-A9000 Hong Kong version in singapore. My phone got firmware update error, i try to flash all A9 firmware with odin but still got problem and showing volume size is too big 7372800 < 7979008 , odin: invalid ext4 image. I try to flash with china firmware also. But frp not allowed. Pls help me what should i do. my phone can do downloading mode only. i can't do recovery mode and i don't have back up. Any idea to help me, pls.
mriyaan said:
I had the same issue.. i fixed it yesterday.. what i did was.. go to developer options.. enable OEM unlock.. download CROM from galaxy apps store.. it gives a warning msg regarding unlocking the device.. that isnt an issue..just press ok.. and it will say ur device is unlocked.. and then try reflashing firmware from ODIN.. and then i did root my A9 and its working pretty nice since yesterday..
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
and also.. if u try to update to marshmallow.. u may get errors.. i assume thats because that is an update from CHINA..NOT from HONGKONG.. i suggest everyone to wait untill hongkong version of Marshmallow is released.. even i flashed marshmallow..had some error and my device was not booting and just booting into recovery with some error like drm something like that.. and then i flashed a hongkong lollipop 5.1.1 version and then my device booted..
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
regarding the FRP locking system. do one thing.. first back up everything.. go to backup and reset option.. do a factory reset.. it will wipe everything so do make sure u backup everything.. it will reboot the device into recovery.. do full factory reset.. reboot again.. finish.. i did this.. FRP LOCK is gone.. am happy
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------
do all the steps as i said.. Insha Allah all your problems and errors will be solved..
Sent from my SM-A9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have the exact same problem as michael's... The problem is that we cannot enter the ROM at all... It only stuck at either the blue screen, or the odin mode screen. So we cannot disable neither FRP or Oem unlock...
Well in my chase i think the Crom service is already unlocked, but still... When trying to flash with :
China marshmallow : odin process failed even from the beginning (aboot.mbn <-- bootloader)
Hongkong lolipop : odin process failed during system ext4, saying it's too large
---------- Post added at 05:31 AM ---------- Previous post was at 05:30 AM ----------
ashyx said:
I take it you tried to update via odin originally.
If you give more details if what part of the flashing process failed we may be able to help.
Was it a particular partition that failed to flash.
A screenshot of the failed flashing process with odin would be helpful.
Also you may be able to remove the blue error screen by flashing the stock recovery with odin.
Extract it from the stock firmware, convert it to a tar archive then flash it with Odin.
Boot to recovery and wipe cache.
That itself may get you booting.
There is also Twrp available for your device which could do the same thing.
Click to expand...
Click to collapse
When trying to flash with :
China marshmallow : odin process failed even from the beginning (aboot.mbn <-- bootloader)
Hongkong lolipop : odin process failed during system ext4, saying it's too large
Is the TWRP for A9 available? I cant find any.
and remember this.. DO NOT FLASH CHINA MARSHMALLOW AS OF NOW.. it creates a problem.. FLASH ONLY HONGKONG FIRMWARE using the latest odin..
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
y do u need twrp? just flash via odin and its done..
Sent from my SM-A9000 using XDA-Developers mobile app
If odin won't flash and the bootloader is complaining about frp lock.
Then the firmware isn't meant for that device.
If it fails at aboot then it's likely nothing got flashed.
To remove the firmware error warning it's usually enough to flash the stock recovery or twrp with odin.
The stock recovery image can be pulled from the stock firmware and converted to tar with 7-zip then flashed with odin.
Note: twrp wont flash while frp lock is active.
ashyx said:
If odin won't flash and the bootloader is complaining about frp lock.
Then the firmware isn't meant for that device.
If it fails at aboot then it's likely nothing got flashed.
To remove the firmware error warning it's usually enough to flash the stock recovery or twrp with odin.
The stock recovery image can be pulled from the stock firmware and converted to tar with 7-zip then flashed with odin.
Note: twrp wont flash while frp lock is active.
Click to expand...
Click to collapse
"The stock recovery image can be pulled from the stock firmware and converted to tar with 7-zip then flashed with odin."
Which file do you mean by stock recovery image, and how to flash it with odin. I mean like which file should be converted to tar and should i put it into AP slot and then start odin like usual? thanks
jmarcus.w said:
"The stock recovery image can be pulled from the stock firmware and converted to tar with 7-zip then flashed with odin."
Which file do you mean by stock recovery image, and how to flash it with odin. I mean like which file should be converted to tar and should i put it into AP slot and then start odin like usual? thanks
Click to expand...
Click to collapse
Open the md5 firmware archive with 7zip and pull out recovery.img.
Use 7-zip to create a tar archive then flash with odin in AP slot.
ashyx said:
Open the md5 firmware archive with 7zip and pull out recovery.img.
Use 7-zip to create a tar archive then flash with odin in AP slot.
Click to expand...
Click to collapse
First of all thanks for this..
I tried this and able to access the recovery screen..
But still flashing the stock ROM after wipe/factory reset fail.
I found several problems in the recovery screen:
There is "dm-verity verification failed" error
and there is problem about mounting to /system and formating /sbfs thing..
When I tried flashing.. the problem is also always on the same point.. On the system.img.ext4 it failed, saying volume is too large, ODIN : invalid ext4... <-- Always this failure
I dont understand any of this.
jmarcus.w said:
First of all thanks for this..
I tried this and able to access the recovery screen..
But still flashing the stock ROM after wipe/factory reset fail.
I found several problems in the recovery screen:
There is "dm-verity verification failed" error
and there is problem about mounting to /system and formating /sbfs thing..
When I tried flashing.. the problem is also always on the same point.. On the system.img.ext4 it failed, saying volume is too large, ODIN : invalid ext4... <-- Always this failure
I dont understand any of this.
Click to expand...
Click to collapse
As previously stated the firmware is not intended for your device this is why you are seeing these issues.
Hi,
I have removed the blue screen, i tried flashing the stockrom after wipe/factory reset failed. I found several problems in the recovery screen. There is "dm-verity verification failed" error and error during wiping, there is a problem about mounting to / system and formatting/ sbfsthing. i don't understand any of this jargon.
Hope i can get some help for this, please.
Thanks
Mikekaipas said:
I own a Samsung Galaxy A9
I tried to update the firmware from the original lollypop to (maybe) marshmallow
I failed to update using the software, so i updated using smart switch
It went wrong, the update failed.
Now the blue screen with "An error has occured while updating the device software. Use the emergency recvery function in the Smart Switch PC software" appears..
I tried the emergency recovery but it also failed
The only button combination that worked is the power button + volume down --> It restarted, but the same screen appears
I even tried refresing the software with Odin, but it failed.
The phone says "FRP is enabled, not allow download non-FRP aboot binary"
Odin doesn't work
The samsung customer service in singapore (my country) is not able to help. Would really appreciate it if somebody could help me with this.
-Michael
Click to expand...
Click to collapse
Mikekaipas said:
Hi,
I have removed the blue screen, i tried flashing the stockrom after wipe/factory reset failed. I found several problems in the recovery screen. There is "dm-verity verification failed" error and error during wiping, there is a problem about mounting to / system and formatting/ sbfsthing. i don't understand any of this jargon.
Hope i can get some help for this, please.
Thanks
Click to expand...
Click to collapse
Don't worry about /sbfs other Samsung devices get the same warning.
Dm-verity is usually due to a modified system partition or just the wrong firmware.
Wipe issue is likely because of frp lock.
Thanks Ashyx.
Right now when i try turning on my phone, my phone just keeps restarting and the typical welcome screen appears. Nothing further happens.
ashyx said:
Don't worry about /sbfs other Samsung devices get the same warning.
Dm-verity is usually due to a modified system partition or just the wrong firmware.
Wipe issue is likely because of frp lock.
Click to expand...
Click to collapse
Mikekaipas said:
Thanks Ashyx.
Right now when i try turning on my phone, my phone just keeps restarting and the typical welcome screen appears. Nothing further happens.
Click to expand...
Click to collapse
Thanks and my phone also got same issue with mikekaipas
Hi, so anyone out there with any suggestions to remedy the situation? Or will i just have to give up on my phone?
Mikekaipas said:
Hi, so anyone out there with any suggestions to remedy the situation? Or will i just have to give up on my phone?
Click to expand...
Click to collapse
i also already tired to try on my phone; should i buy new A9?
Hi all
I want to flash odin a9000 hong kong version, and I am afraid of this looking this thread
I am on latest hong kong rom 5.1.1., unlocked bootloade by crom , rooted, twrp installed...
So, do I need to afraid of this @steberg @ashyx and other advanced users
thanks
Man... Oh maaaan.....
I have also got this problem with SM-A9000.
via smart switch my firmware detected as china built (BPE2). but the emergency recovery always failed at 100%
then i try ODIN, with china firmware ( i try with the newest & even the oldest & i have tried with both full AP instalation & the single instalation BL, AP, CP, CSC) the result:
"FRP is enabled, not allow download non-FRP aboot binary"
with PIT & Re-partition also fail. only add result:
"FRP is enabled, ignore PIT download"
when i try with HK firmware (either newest & all other) it's better while the full instalation fail.
the single instalation made it for BL, CP & CSC and i got into the boot loop which show black screen
and SAMSUNG GALAXY A9(6) logo and i can access recovery.
But AP instalation always fail ( i have tried PIT also), the screen said
"FRP is enabled, ignore PIT download"
"Volume Size is too big 7372800 < 7979008"
"ODIN : Invalid id ext4 image"
my question? is it really wrong firmware? because the BL, CP & CSC can be installed except the AP because of the system.img.ext4.
because with the China Firmware,none can be installed.
also in my recovery there log:
"dm-verity verification failed
E: failed to mount / system (Invalid argument)"
i tried to install TWRP, but still fail,its said:
"FRP is enabled, not allow download non-FRP aboot binary"
and as last resort i even try to tick "NAND erase all" but i just got the same result as above either with China and HK with PIT, with singular or full installation...
i've been working on this phone for several days and now kinda got confused.
1. i dunno how to disable this FRP (my phone no longer able to boot, so the developer option is out of question) is it possible with odin?
2. or is it because E: failed to mount? but i even try Nand erase all yet still no result.
3. or wrong firmware? i tried it all China and HK with PIT & re-partition, still no result.
4. is there a way to wipe everything and erase this FRP thingi ? ( i have tried to wipe all from recovery too) :crying:

S7 Edge G935F // Faulty ODIN flash // Stuck in Bootloader [SOLVED]

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?

G935f nougat root problem

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 .....

S7 edge bootloop

Hi,
I realy need your help,
I have a S7 edge who is stuck at the samsung logo.
I have flashed some stock rom (all in 7.0) via odin 3.12 after a wipe factory but nothing. So i decided to try it with Kies and smartSwitch but still nothing.
I have access to recovery and download mode.
FRP lock: On
The phone is not rooted, and the usb debugging not enabled.
The phone print this in the download mode:
ODIN MODE
Download speed: FAST
Product-Name: SM-G935F
Current Binary: Samsung Official
System Status: Custom
FRP lock: ON
Secure Downlaod: Enabled
Warranty Void: 0(0x000)
RP SWREV: B:1 K:0 S:0
After the installation of the flashed rom in the download mode, the phone reboot with a blue screen, a progress bar but it stop to 32%, and then it is printed "erasing.." and the phone reboot and is still stuck.
I have re-tryed with Kies, now the phone is with a green screen with 2 white Gears : "android is starting" but it is still stuck (i let him all the night but nothing)
i don't know what to do
nonechap said:
Hi,
I realy need your help,
I have a S7 edge who is stuck at the samsung logo.
I have flashed some stock rom (all in 7.0) via odin 3.12 after a wipe factory but nothing. So i decided to try it with Kies and smartSwitch but still nothing.
I have access to recovery and download mode.
FRP lock: On
The phone is not rooted, and the usb debugging not enabled.
The phone print this in the download mode:
ODIN MODE
Download speed: FAST
Product-Name: SM-G935F
Current Binary: Samsung Official
System Status: Custom
FRP lock: ON
Secure Downlaod: Enabled
Warranty Void: 0(0x000)
RP SWREV: B:1 K:0 S:0
After the installation of the flashed rom in the download mode, the phone reboot with a blue screen, a progress bar but it stop to 32%, and then it is printed "erasing.." and the phone reboot and is still stuck.
I have re-tryed with Kies, now the phone is with a green screen with 2 white Gears : "android is starting" but it is still stuck (i let him all the night but nothing)
i don't know what to do
Click to expand...
Click to collapse
You have to use smart switch emergency recovery function to restore your phone. It is a stand alone function within smart switch.
All you need is your phone model and serial number.
Apparently you missed a step when preparing your phone for flashing.
Or you can continue to use Odin which when you plug the USB in will show that a connection is made even though the phone says it's not in download mode.
Cosmic Blue said:
You have to use smart switch emergency recovery function to restore your phone. It is a stand alone function within smart switch.
All you need is your phone model and serial number.
Apparently you missed a step when preparing your phone for flashing.
Click to expand...
Click to collapse
I did an emergency recovery with my phone model and serial, same with kies.
nonechap said:
I did an emergency recovery with my phone model and serial, same with kies.
Click to expand...
Click to collapse
If that did not work, it looks like the memory chip on the mother board is damaged. Take it in if it is still under warranty.
Cosmic Blue said:
If that did not work, it looks like the memory chip on the mother board is damaged. Take it in if it is still under warranty.
Click to expand...
Click to collapse
it is not under warranty anymore, should i replace the motherboard ?
@nonechap bro
upgrade you bootloader before flash nougat rom
bootloader is here
https://www.androidfilehost.com/?fid=529152257862714907
modem is here
https://www.androidfilehost.com/?fid=529152257862714909
open odin and boot your phone into download mode
[1]Connect phone and wait until you get a blue sign in Odin
[2]Place the desired BL file in the [BL] slot.
[3]Place the desired CP file in the [CP] slot.
[4] Go to the Options section and make sure Auto Reboot, Re-Partition and F. reset time are unmarked.
[5]Push [Start]
Once odin reports "Success..." message in the Message box, boot your phone into download mode again
then flash again 7.0 roms via odin
then boot in recovery and wipe data and cache
and reboot device
be patience first boot takes 15 minutes or more
if fail you cant boot your device untill system status changed to official due to knox restrictions or bootloader changed to latest
if not boot that means your bootloader not update by odin due to frp lock is on
if you are on marshmellow before flash 6.0.1 firmware to boot device
firmwares are here
https://www.sammobile.com/firmwares/database/SM-G935F/
i suggest if device boots unlock bootloader first to disable knox
hit thumbs up if i helped you
rony raj said:
@nonechap bro
upgrade you bootloader before flash nougat rom
bootloader is here
https://www.androidfilehost.com/?fid=529152257862714907
modem is here
https://www.androidfilehost.com/?fid=529152257862714909
open odin and boot your phone into download mode
[1]Connect phone and wait until you get a blue sign in Odin
[2]Place the desired BL file in the [BL] slot.
[3]Place the desired CP file in the [CP] slot.
[4] Go to the Options section and make sure Auto Reboot, Re-Partition and F. reset time are unmarked.
[5]Push [Start]
Once odin reports "Success..." message in the Message box, boot your phone into download mode again
then flash again 7.0 roms via odin
then boot in recovery and wipe data and cache
and reboot device
be patience first boot takes 15 minutes or more
if fail you cant boot your device untill system status changed to official due to knox restrictions or bootloader changed to latest
if not boot that means your bootloader not update by odin due to frp lock is on
if you are on marshmellow before flash 6.0.1 firmware to boot device
firmwares are here
https://www.sammobile.com/firmwares/database/SM-G935F/
i suggest if device boots unlock bootloader first to disable knox
hit thumbs up if i helped you
Click to expand...
Click to collapse
In this case, when i flash the rom, should i use the 4 files or only the AP file ?
nonechap said:
In this case, when i flash the rom, should i use the 4 files or only the AP file ?
Click to expand...
Click to collapse
use old odin
rony raj said:
use old odin
Click to expand...
Click to collapse
What version of odin should i use ?
And i have to use only the AP file or the 4 files of the 7.0 rom after the bootloader update? (AP BL CP CSC)
nonechap said:
What version of odin should i use ?
And i have to use only the AP file or the 4 files of the 7.0 rom after the bootloader update? (AP BL CP CSC)
Click to expand...
Click to collapse
odin v3.09 or 3.12
update bootloader and modem from given first post by me
rony raj said:
odin v3.09 or 3.12
update bootloader and modem from given first post by me
Click to expand...
Click to collapse
Yes i know but when i have updated the bootload with the 2 files you gave me, i have to reboot in download mod and flash the 7.0 rom, but i have download the rom and i have 4 files, so should i flash only the AP or the four files ?
nonechap said:
Yes i know but when i have updated the bootload with the 2 files you gave me, i have to reboot in download mod and flash the 7.0 rom, but i have download the rom and i have 4 files, so should i flash only the AP or the four files ?
Click to expand...
Click to collapse
tell me rom on your device before bootloop
6.0 or 7.0
rony raj said:
tell me rom on your device before bootloop
6.0 or 7.0
Click to expand...
Click to collapse
6.0.1
nonechap said:
6.0.1
Click to expand...
Click to collapse
then flash 6.0 firmware
download from here
https://www.sammobile.com/firmwares/database/SM-G935F/
rony raj said:
then flash 6.0 firmware
download from here
https://www.sammobile.com/firmwares/database/SM-G935F/
Click to expand...
Click to collapse
I tried but still nothing, i think i have to replace the motherboard ?
nonechap said:
I tried but still nothing, i think i have to replace the motherboard ?
Click to expand...
Click to collapse
try another chance
To do the S7 FRP OFF - Put phone in download mode
Once phone is in download mode.
Flash the files which i will provide.
You Only need to flash boot.tar via odin for respective models (example for s7 use G930 Qualcomm folder) for (s7 edge use G935 Qualcomm folder)
Once you flash the boot tar file. The phone will reboot and it will enable ADB. Run the Bat file which i will provide and it will remove the FRP lock
Once done put the phone in Downlaod mode and flash stock ROM.
The whole process takes less than 10 mins.
Same Idea for S7 Exynos phones... put phone in downlaod mode and then flash the file (G930F(ENGroot) for s7 models & (G935F_Root for s7 edge models). Once done phone will reboot. Then use this bat file (g935f.bat). Once this is executed locks will be removed and phone will go in download mode. Flash stock Boot.img and ALL DONE.
download
https://mega.nz/#!Tw0TAI6I!jCGuxGrwqCGEy3flcRqF9EpzbaTkby7SJ_slKRaXqRs
rony raj said:
try another chance
To do the S7 FRP OFF - Put phone in download mode
Once phone is in download mode.
Flash the files which i will provide.
You Only need to flash boot.tar via odin for respective models (example for s7 use G930 Qualcomm folder) for (s7 edge use G935 Qualcomm folder)
Once you flash the boot tar file. The phone will reboot and it will enable ADB. Run the Bat file which i will provide and it will remove the FRP lock
Once done put the phone in Downlaod mode and flash stock ROM.
The whole process takes less than 10 mins.
Same Idea for S7 Exynos phones... put phone in downlaod mode and then flash the file (G930F(ENGroot) for s7 models & (G935F_Root for s7 edge models). Once done phone will reboot. Then use this bat file (g935f.bat). Once this is executed locks will be removed and phone will go in download mode. Flash stock Boot.img and ALL DONE.
download
https://mega.nz/#!Tw0TAI6I!jCGuxGrwqCGEy3flcRqF9EpzbaTkby7SJ_slKRaXqRs
Click to expand...
Click to collapse
After flashing boot.tar, when i run the .bat, it says error: closed
EDIT: i have to enter into the recovery mod and select "adb update" in order to make my phone detected by my computer
Those files are for the S7. Do they work for the S7 Edge also?
Edit - I tried it and it fails in odin. My phone is bricked.
rony raj said:
@nonechap bro
upgrade you bootloader before flash nougat rom
bootloader is here
https://www.androidfilehost.com/?fid=529152257862714907
modem is here
https://www.androidfilehost.com/?fid=529152257862714909
open odin and boot your phone into download mode
[1]Connect phone and wait until you get a blue sign in Odin
[2]Place the desired BL file in the [BL] slot.
[3]Place the desired CP file in the [CP] slot.
[4] Go to the Options section and make sure Auto Reboot, Re-Partition and F. reset time are unmarked.
[5]Push [Start]
Once odin reports "Success..." message in the Message box, boot your phone into download mode again
then flash again 7.0 roms via odin
then boot in recovery and wipe data and cache
and reboot device
be patience first boot takes 15 minutes or more
if fail you cant boot your device untill system status changed to official due to knox restrictions or bootloader changed to latest
if not boot that means your bootloader not update by odin due to frp lock is on
if you are on marshmellow before flash 6.0.1 firmware to boot device
firmwares are here
https://www.sammobile.com/firmwares/database/SM-G935F/
i suggest if device boots unlock bootloader first to disable knox
hit thumbs up if i helped you
Click to expand...
Click to collapse
Works !!!
Sorry to revive an old thread but I think it might help people recover from a bootloop with a bit of addtional explanation than initially provided.
So I have an S7 Edge as a backup phone and hadn't used it for a while. Google FRP was activated. I tried to update to a newer firmware through Odin (can't OTA since it's from Tmo and i'm in Canada). Anyways for whatever reason it failed in the middle and I was stuck in a bootloop that wouldn't stop. I tried downgrading, I tried factory, I tried new versions, nothing would do, I'm assuming because of FRP.
So I followed Rony Raj's post https://forum.xda-developers.com/showpost.php?p=71906126&postcount=17 but kept getting stuck. The thing is once you flash the proper Boot.tar file, the phone will appear to still be in a bootloop. You will have to go with the screen (the phone) and the sound of the connection and disconnection from your computer. So basically just sync with the sounds and time it so you open the ''S7 & S7 Edge QUALCOMM.bat'' file at the exact time your phone reconnects and it'll work. I had to do it about 6-7 times before i got it right.
When that is done your phone will restart in download mode. When you do just flash the latest version of the firmware you get from AndroidFileHos*.com or Sammobil*.com. Make sure you select all 4 files in Odin (BL, AP, CP and SELECT CSC HOME for CSC - NOT CSC).
Once all that is done your phone will restart and everything should be fine, well that worked for me
Thanks a lot to @rony raj for putting together the files and the steps to save my G935

After passed Odin flash "error" when trying to update system

Got a s7edge, g935F that got stuck in loop. ( stock, no root)
After a factory reset it didn't do nothing.
Now I did a Flash using Odin 3.1.3 and with the latest stock for my device from sammobile . The flash indicates pass but when the system reboots I get a short message that Systemupdate is in progress, then a 'error!' screen with a dead android and a bar that freezes @ 25 %
-Stuck.
-I only can get into Download mode. Recovery mode not working.
-Flashed with BL and without
-Tried other ports and cables.
- tried other stocks.
-tried TWRP for alterative recovery but get a protection error (FRP)
- tried Kies and SmartSwitch but they "don't support" this device ….
Any sugestions or fixes .
xxnedxx said:
Got a s7edge, g935F that got stuck in loop. ( stock, no root)
After a factory reset it didn't do nothing.
Now I did a Flash using Odin 3.1.3 and with the latest stock for my device from sammobile . The flash indicates pass but when the system reboots I get a short message that Systemupdate is in progress, then a 'error!' screen with a dead android and a bar that freezes @ 25 %
-Stuck.
-I only can get into Download mode. Recovery mode not working.
-Flashed with BL and without
-Tried other ports and cables.
- tried other stocks.
-tried TWRP for alterative recovery but get a protection error (FRP)
- tried Kies and SmartSwitch but they "don't support" this device ….
Any sugestions or fixes .
Click to expand...
Click to collapse
I had a similar issue where my FRP became locked and wasn't able to boot into System or flash TWRP. What I did was flash a clean build with Nougat instead of Oreo. Once I was able to boot into System and initialize my phone, I enabled developer settings and enabled OEM unlock which unlocked the FRP. I used the BTU firmware of Nougat by the way. Not sure if this will fix the issue for you but it's worth a shot.
heii70 said:
I had a similar issue where my FRP became locked and wasn't able to boot into System or flash TWRP. What I did was flash a clean build with Nougat instead of Oreo. Once I was able to boot into System and initialize my phone, I enabled developer settings and enabled OEM unlock which unlocked the FRP. I used the BTU firmware of Nougat by the way. Not sure if this will fix the issue for you but it's worth a shot.
Click to expand...
Click to collapse
Well it did something Other then just the "error!" message I got before.
Bootloop to "No command:" screen after Passed flash (Nougat) but still o access into Recovery mode
Now lets search from there …..
xxnedxx said:
Well it did something Other then just the "error!" message I got before.
Bootloop to "No command:" screen after Passed flash (Nougat) but still o access into Recovery mode
Now lets search from there …..
Click to expand...
Click to collapse
...
xxnedxx said:
Well it did something Other then just the "error!" message I got before.
Bootloop to "No command:" screen after Passed flash (Nougat) but still o access into Recovery mode
Now lets search from there …..
Click to expand...
Click to collapse
Are you getting the "no command" error when trying to boot into System or Recovery? Also which did you use the "CSC" or "Home_CSC" file when flashing?
heii70 said:
Are you getting the "no command" error when trying to boot into System or Recovery? Also which did you use the "CSC" or "Home_CSC" file when flashing?
Click to expand...
Click to collapse
I still can't get into recovery mode. ( I wish ) so this is happening when Flashing with CSC latest Nougat . (G935FXXU1BPLB_G935FPHN1BPK1_PHN)
I pass Odin but when the system boots It hangs on No command screen also there I cant enter recovery. (same when trying Home_CSC) ( no need for data recovery )
The first post is when I installed the latest Oreo.
xxnedxx said:
I still can't get into recovery mode. ( I wish ) so this is happening when Flashing with CSC latest Nougat . (G935FXXU1BPLB_G935FPHN1BPK1_PHN)
I pass Odin but when the system boots It hangs on No command screen also there I cant enter recovery. (same when trying Home_CSC) ( no need for data recovery )
The first post is when I installed the latest Oreo.
Click to expand...
Click to collapse
Try different firmware from another region and see if you get different results. The last option is to let your battery completely drain over a course of a few days, that will release the FRP lock. Or you can open your phone and reset the battery connection.
heii70 said:
Try different firmware from another region and see if you get different results. The last option is to let your battery completely drain over a course of a few days, that will release the FRP lock. Or you can open your phone and reset the battery connection.
Click to expand...
Click to collapse
Can i do a frp un lock using CF-autoRoot?
xxnedxx said:
Can i do a frp un lock using CF-autoRoot?
Click to expand...
Click to collapse
No cuz the very fact that FRP is locked means you can't flash anything that's not stock.
---------- Post added at 09:42 PM ---------- Previous post was at 09:35 PM ----------
heii70 said:
Try different firmware from another region and see if you get different results. The last option is to let your battery completely drain over a course of a few days, that will release the FRP lock. Or you can open your phone and reset the battery connection.
Click to expand...
Click to collapse
Also when I said "drain", I really meant it. You have to let the battery die to a point where your phone doesn't respond to anything, not to just to when the phone turns off at 0%. If you are even able to turn on the phone for a brief moment, then the battery still isn't drained enough.
---------- Post added at 10:03 PM ---------- Previous post was at 09:42 PM ----------
xxnedxx said:
I still can't get into recovery mode. ( I wish ) so this is happening when Flashing with CSC latest Nougat . (G935FXXU1BPLB_G935FPHN1BPK1_PHN)
I pass Odin but when the system boots It hangs on No command screen also there I cant enter recovery. (same when trying Home_CSC) ( no need for data recovery )
The first post is when I installed the latest Oreo.
Click to expand...
Click to collapse
G935FXXU1BPLB_G935FPHN1BPK1_PHN is Marshmallow, not Nougat. Here are all the firmware versions for PHN that are Nougat and Oreo, try them all and see if one of them works: https://updato.com/firmware-archive...ugat(Android+7.0),Oreo(Android+8.0.0)&rpp=100 . If not, you are going to have to go with draining the battery.
heii70 said:
No cuz the very fact that FRP is locked means you can't flash anything that's not stock.
---------- Post added at 09:42 PM ---------- Previous post was at 09:35 PM ----------
Also when I said "drain", I really meant it. You have to let the battery die to a point where your phone doesn't respond to anything, not to just to when the phone turns off at 0%. If you are even able to turn on the phone for a brief moment, then the battery still isn't drained enough.
---------- Post added at 10:03 PM ---------- Previous post was at 09:42 PM ----------
G935FXXU1BPLB_G935FPHN1BPK1_PHN is Marshmallow, not Nougat. Here are all the firmware versions for PHN that are Nougat and Oreo, try them all and see if one of them works: https://updato.com/firmware-archive...ugat(Android+7.0),Oreo(Android+8.0.0)&rpp=100 . If not, you are going to have to go with draining the battery.
Click to expand...
Click to collapse
Txs for feedback. Lets try some more flashing form that url . Already did a bunch from sammobile
Still no luck with the firmware's provided by that link.
Some of them Pass Odin Flash without error but when System reboots its ( using AP,BL,CP,CSC)
Blue screen (after short initialize 25 or 32% >> erase >> reboot>>)
- error!
or
- No command
Some of them Fail Odin with message In download mode screen:
- SW REV. CHECK FAIL (BOOTLOADER) DEVICE 2 BINARY 1
So I got a non rooted phone never opened development mode that just crashed into a BootLoop
After Wipe data en Catch attempt>>> "brick"
No recovery mode possible . Only download mode.
In download mode SmartSwitch and Kies see device connected but are not "supporting it" so emergency recovery = no option
"zucht"
heii70 said:
Try different firmware from another region and see if you get different results. The last option is to let your battery completely drain over a course of a few days, that will release the FRP lock. Or you can open your phone and reset the battery connection.
Click to expand...
Click to collapse
Unplugged the battery. Didnt do nuttin on FRP lock.
Still no luck even with some guyz online service.
Loads off error passed by. Stil no luck getting into recovery or getting a firmware installed.
xxnedxx said:
Unplugged the battery. Didnt do nuttin on FRP lock.
Still no luck even with some guyz online service.
Loads off error passed by. Stil no luck getting into recovery or getting a firmware installed.
Click to expand...
Click to collapse
Did you make sure to press and hold the power button for a minute or two to drain any residual electricity after unplugging the battery? Try that and see if that helps.
heii70 said:
Did you make sure to press and hold the power button for a minute or two to drain any residual electricity after unplugging the battery? Try that and see if that helps.
Click to expand...
Click to collapse
Yup Still locked
Screenshot
@xxnedxx Any progress? I have the exact same problem on my G930F. Even dis- and reconnected the battery.
I have the same problem, S7 Edge (G935F) Never ending loop, restarts on 25~32% and goes to no command. Tried different firmwares for 8.0 and I even located the PDA correct firmware, still no luck with it. Recovery doesnt work when I try to enter it I get the error code lines on the black screen. This problem occurred when I tried upgrading from nougat to oreo 8.0 and it went to neverending loop.
xxnedxx said:
Got a s7edge, g935F that got stuck in loop. ( stock, no root)
After a factory reset it didn't do nothing.
Now I did a Flash using Odin 3.1.3 and with the latest stock for my device from sammobile . The flash indicates pass but when the system reboots I get a short message that Systemupdate is in progress, then a 'error!' screen with a dead android and a bar that freezes @ 25 %
-Stuck.
-I only can get into Download mode. Recovery mode not working.
-Flashed with BL and without
-Tried other ports and cables.
- tried other stocks.
-tried TWRP for alterative recovery but get a protection error (FRP)
- tried Kies and SmartSwitch but they "don't support" this device ….
Any sugestions or fixes .
Click to expand...
Click to collapse
hello i had this problem while i was trying to root and unlock the phone
this is what i did hopefully it works for you too
1* download the latest firmware according to your android version
use odin3 v3.13 patched version
2* boot into boot loader
chose Bl on odin and the pit file , uncheck re-partition
and press start , that will get your phone unbrick then flash the ap file and then cp and csc that shoud do the job :good:
Efrencalvario said:
hello i had this problem while i was trying to root and unlock the phone
this is what i did hopefully it works for you too
1* download the latest firmware according to your android version
use odin3 v3.13 patched version
2* boot into boot loader
chose Bl on odin and the pit file , uncheck re-partition
and press start , that will get your phone unbrick then flash the ap file and then cp and csc that shoud do the job :good:
Click to expand...
Click to collapse
sorry my english.
the same for me
all o.k. but i flashed AP,phone say erasing 25%,off,and on,No command
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKOWN]#
No support SINGLE-SKU
File-Based OTA
Supported API:3
# MANUAL MODE V1.0.0#
E:[libfs_mgr]Blob verification failed:255
E:failed setting up dirty target
failed to mont '/system'(Bad file descriptor)
......
any idea?
I have exactly the same problem with G930FD S7, I dont even have FRP on still whenever I flash stock rom through odin
phone say erasing 25%,off,and on,No command
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKOWN]#
No support SINGLE-SKU
File-Based OTA
Supported API:3
# MANUAL MODE V1.0.0#
E:[libfs_mgr]Blob verification failed:255
E:failed setting up dirty target
failed to mont '/system'(Bad file descriptor)
I was able to flash TWRP and custom ROMS are working fine but no official ODIN,
---------- Post added at 11:53 PM ---------- Previous post was at 11:44 PM ----------
Efrencalvario said:
hello i had this problem while i was trying to root and unlock the phone
this is what i did hopefully it works for you too
1* download the latest firmware according to your android version
use odin3 v3.13 patched version
2* boot into boot loader
chose Bl on odin and the pit file , uncheck re-partition
and press start , that will get your phone unbrick then flash the ap file and then cp and csc that shoud do the job :good:
Click to expand...
Click to collapse
Can you elaborate further where to find the pit file ?

Categories

Resources