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 ?
Related
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:
hi guys.
My problem started few days ago when my phone start to restarts many times in a day,so I start to do a factory reset and it failed,I mean the phone restart like normal after this attempt but have some errors with google play services and the phone starts to booting again and again..after this I managed to get in the recovery mode and try to do a factory reset there but failed again and the phone start to boot to Samsung logo..I put it in download mode and try to flash with odin the latest firmware noughat that was previously installed in the phone 2 weeks ago..the odin process starts normaly and it was a successful operation but I got a error about NO COMMAND and the phone is restarts to Samsung logo..What can I do to fix this issue???
try to flash back an 6.0.1 version, after make wipe data from recovery and let phone reboot and see if anything changed, if same result you might have a hardware issue
remosam said:
try to flash back an 6.0.1 version, after make wipe data from recovery and let phone reboot and see if anything changed, if same result you might have a hardware issue
Click to expand...
Click to collapse
to flash back to 6.01 version I have to download this?the problem is that now I don't have good internet ...If I didn't enabled the OEM unlock and usb debugging before the flash,could be the cause for this boot logo?
cristy7610 said:
hi guys.
My problem started few days ago when my phone start to restarts many times in a day,so I start to do a factory reset and it failed,I mean the phone restart like normal after this attempt but have some errors with google play services and the phone starts to booting again and again..after this I managed to get in the recovery mode and try to do a factory reset there but failed again and the phone start to boot to Samsung logo..I put it in download mode and try to flash with odin the latest firmware noughat that was previously installed in the phone 2 weeks ago..the odin process starts normaly and it was a successful operation but I got a error about NO COMMAND and the phone is restarts to Samsung logo..What can I do to fix this issue???
Click to expand...
Click to collapse
flash 6.1 firmware via odin
cristy7610 said:
to flash back to 6.01 version I have to download this?the problem is that now I don't have good internet ...If I didn't enabled the OEM unlock and usb debugging before the flash,could be the cause for this boot logo?
Click to expand...
Click to collapse
oem unlock and usb debugging is only related to custom firmware or rooted stock, isn't your cause. download stock 6.0.1 and check what happens after flash
riz157 said:
flash 6.1 firmware via odin
Click to expand...
Click to collapse
On first flash today via Odin I got a message "no command" and android screen,if it means something that...If I use smart switch and the option emergency software recovery ,it will download the original 6.1.0 firmware?
"no command" mesage usually appears before entering recovery mode, use smart switch and enter serial to restore firmware, will install 6.0.1 if your original csc don't have yet 7.0
---------- Post added at 11:38 PM ---------- Previous post was at 11:30 PM ----------
if you have international model, G935F you can download XEU 6.0.1 firmware from here: https://drive.google.com/file/d/0BzcqBQZhElPfNDJzMTd5NGh6ODQ/view?usp=drivesdk
Thanks guys..I managed to fix it with smart switch...and after this I flashed via Odin,noughat again and everything is ok now.
Hi!
My G-935F is bricked after I downloaded the latest update. Phone is all stock with no mods at all.
Tried to flash the whole phone with Odin, witch worked. But the phone is still stuck in start screen.
I also tried to flash different roms to it but since it is a uprooted phone, that never worked. Is said something like binary 4 device 2. Also tried to flash earlier BL but the phone won't downgrade. It also complains about FRP sometimes when trying to flash different roms.
Download mode is still avalible but I am unable to get in to recovery mode.
Is the phone hardbricked or is there a solution I haven't tried?
Very greatfull for any input.
Removed
ultimatepumperx1 said:
You are fine if you have access to Download mode, just download the Stock firmware from sammobile.com since you have international version just pick your country if you are unable to find exact same country firmware try like germany one but there might be firmware for example Nordic countries and it is just g935f firmware for nordic countries and take sammmobile site and if you are example from germany then get germany version if possible you can still use your phone but you might can't use samsung pay with different country firmware not sure but yea. I guess you are finnish because of the end of your name "lainen" im too
Click to expand...
Click to collapse
That is what I have done all ready. Several times. And there are no problems with the flashing process what so ever. But the phone won't continue to boot beyond the first start-up screen. It is stuck in the first logo that appears when I start the phone.
No I'm actually from Sweden. But neighbours then!
ultimatepumperx1 said:
Hmm, seems strange what we know that your phone isn't hard bricked. Try this
if you are unable to view it i can explain it here so flash whatever country' firmware i recommend your own which is this case sweden so put everything in the odin remember to put CSC instead of HOME_CSC then boot to recovery mode(VOLUME UP+HOME+POWER) hold until you see updating then you should see no command then just wait few seconds to let it think:highfive: think then go vol down to factory reset then power again vol down to the yes! then power again and then go boot to the system using power button and cross fingers!
Click to expand...
Click to collapse
Bro his frp lock is enabled so he can't factory reset it and flashing stock rom succeeds but no boot up. Also unable to flash twrp recovery or boot in normal recovery. We've been looking for a solution but so far no luck
ultimatepumperx1 said:
Okay, sir i know, that he can't flash twrp because of frp lock, but he actually can factory reset trough recovery system if he flashes latest stock rom he will get stock recovery whatever he does, also he has flashed many different firmwares already so i bet there must be recovery
---------- Post added at 07:08 AM ---------- Previous post was at 07:04 AM ----------
You need to factory reset your device, because you have old data of your system, sadly they are unrecoverable, but atleast you don't end up with brick
Click to expand...
Click to collapse
The problem is that I can't get in to recovery mode. If I Could, then I guess there wouldn't be a problem to get the phone up and running. But since I can't, there Is a bigger problem.
Yesterday, when trying different solutions. I tried to get in to recovery mode after a total flash. And then I booted in to a blue screen with the droid on it, and the text underneath it that was saying "erasing".
That was the only change I seen since the phone got bricked. Even if the system erased itself, and I did a total flash afterwards, the system won't boot, and I still can't get in to recovery mode.
Hi, I'm getting exactly the same issue here, almost tried everything, frp lock is enabled i can't acces to recovery menu and i'm unable to flash TWRP, frp lock blocked everything, i can just access to download mode
Please, I need some help with my SM-G9350 Hong-Kong Galaxy S7 edge on Binary 4
I got custom binary blocked by frp lock on SM-G9350 HK Hong-Kong Galaxy S7 edge, and then I flashed stock firmware via Odin and all was just fine and Odin succeed pass, but when installing system updates in recovery it was up to 32% then erasing and then it should boot up system, but it didn't it keeps rebooting to recovery with no options at all, just showing the android guy with no command below and then when I hard it to enter in recovery menu it shows a black screen with some lines that says couldn't open recovery cause unknown and no such file directory, and device is busy, and keep doing the same thing, I did same and flashed again with latest firmware but same thing happened, and then I tried to flash TWRP in order to flash a custom rom but Odin fails and says in download mode custom binary recovery blocked by frp lock, known that my device's bootloader is already unlocked and I flashed before this a whole of stuff, now, I can just access to download mode, otherwise I can't do anything else even no adb , there is no a combination file for the Hong-Kong variant G9350ZH, there is only for the Open-China variant G9350ZC which is not combatible with the device, even there are no adb enabled files, if someone has a solution for this, please kindly take care of this problem
THIS IS REALLY IMPORTANT: I watched too many videos on YouTube and in conclusion flashing stock firmware is enough to get rid of many issues including the frp lock, so, here there are two different S7 edge devices with two different processors and both got the same and exact problem with latest stock rom, what Samsung done with latest firmwares of the Galaxy S7 edge, they made a lot of new devices running pie, and S7 should be old according to them while a lot of S7 users are waiting for a Pie OneUI update, I got some problems earlier but flashing the Old CRH1 solved the issues and now with their latest firmwares all bricks up
Here's what it says in recovery .. attached below, with no usual selection menu at all
ultimatepumperx1 said:
okay so you can boot to recovery if you have stock recovery there, so go to download mode and type to adb "fastboot reboot recovery" and it will boot and you will see droid maybe saying "updating or smth" then no command and let it think for atleast minute and you should be inside recovery after that or just follow vol up and power and home button like i said then just wait minute again when you see the droid.
---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------
Click to expand...
Click to collapse
I am trying to get adb to work. I dont know how it works but as soon as i open the ADB.EXE file,
the cmd flashes up really quick, with a lot of text in it, just to dissapear again.
I cant get it to stay to type in any commands. The phone, when i am
opening ADB.EXE, is plugged in and in download mode. Is it anything i am doing wrong
or is the phones firmware so corrupt so it doesent recognise it?
And does really ADB work on a phone where debuggning mode is untouched?
ultimatepumperx1 said:
okay so you can boot to recovery if you have stock recovery there, so go to download mode and type to adb "fastboot reboot recovery" and it will boot and you will see droid maybe saying "updating or smth" then no command and let it think for atleast minute and you should be inside recovery after that or just follow vol up and power and home button like i said then just wait minute again when you see the droid.
---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------
then you have installed wrong firmware make sure to get latest firmware and install it with latest odin.
Latest odin: https://odindownload.com/
and Latest Firmware from https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G9350/
make sure to put your country if possible or what it came with,
Click to expand...
Click to collapse
I'm using the right firmware from sammobile and right latest odin, if it was not the right firmware Odin will never let me flash at all, and it is the country that it came with, unfortunately
So i found this file on the internet
Frp Lock disable flash with odin to ap
Maybe try this
https://www.mediafire.com/file/7du404j8hn8da9n/Exynos.tar/file
Reboot to download mode to check
I haven't tested it
gupt07ash said:
So i found this file on the internet
Frp Lock disable flash with odin to ap
Maybe try this
https://www.mediafire.com/file/7du404j8hn8da9n/Exynos.tar/file
Reboot to download mode to check
I haven't tested it
Click to expand...
Click to collapse
This did not do the trick! Odin fails ond i got a message in red
that said "custom binary (userdata) blocked by frp"
Im testing the other tip with ABD and fastboot. But no luck yet.
ultimatepumperx1 said:
No adb doesn't work but fastboot does which comes in the same folder so what you need to open cmd in the adb.exe file it is normal to flash if you do it like that but you have to navigate to the adb folder and then type fastboot reboot recovery what is basicly does is that it tells fastboot.exe to reboot recovery and this code won't work but you will understand what i mean so "fastboot.exe reboot recovery" don't put ".exe" and it will work like i said before.
Click to expand...
Click to collapse
Think i got he hang of it. But when i am trying to connect to my S7, it cant find y device.
Feels like i am not beeing able to connect to the phone while in download mode.
I have a S6 that i am experimenting with by the side, that is working. Abd are not able to connect
this device either when in download mode. Maybe there is another way around it with this program?
Dampalainen said:
This did not do the trick! Odin fails ond i got a message in red
that said "custom binary (userdata) blocked by frp"
Im testing the other tip with ABD and fastboot. But no luck yet.
Click to expand...
Click to collapse
I'm all out of ideas
Flashing stock rom always does the trick. Maybe try the one from sammobile for your country
gupt07ash said:
I'm all out of ideas
Flashing stock rom always does the trick. Maybe try the one from sammobile for your country
Click to expand...
Click to collapse
I can try. But it feels just like there is somtething wrong with the booting process. Is everything the phone needs to boot, in the BT file that you can flash in ODIN or is there anything else? I mean, if the boot file would work properly, then i would have gotten in to recovery menu.
Dampalainen said:
I can try. But it feels just like there is somtething wrong with the booting process. Is everything the phone needs to boot, in the BT file that you can flash in ODIN or is there anything else? I mean, if the boot file would work properly, then i would have gotten in to recovery menu.
Click to expand...
Click to collapse
Yes ofcourse
Is it the firmware you flashed?
gupt07ash said:
Is it the firmware you flashed?
Click to expand...
Click to collapse
Yes! Thats the one!
Have tried some different solutions this evening and got nothing.
Even used erase NAND option along with the correct PIT file.
Read alot about it before proceeding with NAND erase.
There is no change on the phone after NAND erase.
even though i have made a total flash of the phone afterwards.
Feels like it must be a hardware issue?
Dampalainen said:
Yes! Thats the one!
Have tried some different solutions this evening and got nothing.
Even used erase NAND option along with the correct PIT file.
Read alot about it before proceeding with NAND erase.
There is no change on the phone after NAND erase.
even though i have made a total flash of the phone afterwards.
Feels like it must be a hardware issue?
Click to expand...
Click to collapse
Can't be a hardware issue..
Maybe the old firmware was different than what you're trying to flash. Heck if I were you, I'd try all of them stock roms until it boots up
ultimatepumperx1 said:
Okay, sir i know, that he can't flash twrp because of frp lock, but he actually can factory reset trough recovery system if he flashes latest stock rom he will get stock recovery whatever he does, also he has flashed many different firmwares already so i bet there must be recovery
---------- Post added at 07:08 AM ---------- Previous post was at 07:04 AM ----------
You need to factory reset your device, because you have old data of your system, sadly they are unrecoverable, but atleast you don't end up with brick
Click to expand...
Click to collapse
gupt07ash said:
Can't be a hardware issue..
Maybe the old firmware was different than what you're trying to flash. Heck if I were you, I'd try all of them stock roms until it boots up
Click to expand...
Click to collapse
You mean all the others with different languages?
I was downloading a Norwegian version tonight. I am going to try that one tomorrow.
But since the recovery menu is still missing, it feels like the problem would be in the BL file?
Dampalainen said:
You mean all the others with different languages?
I was downloading a Norwegian version tonight. I am going to try that one tomorrow.
But since the recovery menu is still missing, it feels like the problem would be in the BL file?
Click to expand...
Click to collapse
Yes all the latest firmwares from different regions. Surely something should work
If you do fail, dm a developer. They might have a good solution.
http://forum.gsmhosting.com/vbb/f162/gsm-flasher-frp-reactivation-lock-remover-pro-2200193/
...
https://www.s7fanclub.com/gsm-flasher-pro-frp-tool-for-windows-pc-to-bypass-samsung-frp-lock.html
ultimatepumperx1 said:
I would try smart switch if it will get your recovery working but try everything
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
Trying to unlock frp via download mode is last thing you should do, myself i would just find a way to get recovery working.
---------- Post added at 06:33 PM ---------- Previous post was at 06:31 PM ----------
i think your partitions are ****ed up somehow. i think there is way to restore them.
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
have you tried flashing bl with pit file only or ap with pit file only,
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
because pit file stands Partition Information Table (PIT) it might work.
Click to expand...
Click to collapse
I'm having the same and exact problem, nothing worked it sucks up, tried pit fle and even with some cracked boxes to reset frp but nothing worked
Recently, I turned off developer options in my rooted S7 Edge (SM-G935FD). Idk if that is the cause, but after rebooting I got the error "Custom Binary Blocked by FRP Lock". I couldnt boot into my recovery (TWRP) either. I was running on Oreo btw. I watched some Youtube guides and apparently the solution was to flash stock rom. So... I flashed an Oreo Stock Rom on my phone via Odin. I thought that would solve my problem, but instead it made it worse. It didnt give me the Custom Binary Blocked by FRP lock error but my boot screen is stuck at the boot animation (not a bootloop). I could boot into the stock recovery tho. I tried a factory reset, that didnt make things better. I could also boot into download mode. I thought I made a mistake, so I flashed like 5-8 times with both CSC an Home_CSC. The result was the same, it would get stuck at the boot animation. I tried flashing TWRP via Odin too, but it said "Custom Binary (Recovery) blocked by FRP Lock". I tried sideloading that TWRP file to my device via ADB. It gave me an error too (I think "Cannot flash from external devices" or something like that) I thought flashing with Re-partition and Nand Erase On would solve my problem, so I tried that, but it didnt work. Im running on Binary 3 apparently. Is there anything I can do?
Rapidfayaround said:
Recently, I turned off developer options in my rooted S7 Edge (SM-G935FD). Idk if that is the cause, but after rebooting I got the error "Custom Binary Blocked by FRP Lock". I couldnt boot into my recovery (TWRP) either. I was running on Oreo btw. I watched some Youtube guides and apparently the solution was to flash stock rom. So... I flashed an Oreo Stock Rom on my phone via Odin. I thought that would solve my problem, but instead it made it worse. It didnt give me the Custom Binary Blocked by FRP lock error but my boot screen is stuck at the boot animation (not a bootloop). I could boot into the stock recovery tho. I tried a factory reset, that didnt make things better. I could also boot into download mode. I thought I made a mistake, so I flashed like 5-8 times with both CSC an Home_CSC. The result was the same, it would get stuck at the boot animation. I tried flashing TWRP via Odin too, but it said "Custom Binary (Recovery) blocked by FRP Lock". I tried sideloading that TWRP file to my device via ADB. It gave me an error too (I think "Cannot flash from external devices" or something like that) I thought flashing with Re-partition and Nand Erase On would solve my problem, so I tried that, but it didnt work. Im running on Binary 3 apparently. Is there anything I can do?
Click to expand...
Click to collapse
I still have the "FRP Lock: On" on download mode, so I tried bypassing FRP lock via binary 5 combination firmware and flashing a binary 7 stock firmware. This time, it doesnt get stuck at the boot animation, instead it redirects to a screen with an android face saying "Installing System updates". A few seconds later, it says "No command" with a dead android face. Then it reboots and the same thing happens. Basically a boot loop, but in a different way. I cant seem to boot to stock recovery either. The worst thing is that I cant even turn off the thing. I have to leave it loop for the entire day until its battery dies
Rapidfayaround said:
I still have the "FRP Lock: On" on download mode, so I tried bypassing FRP lock via binary 5 combination firmware and flashing a binary 7 stock firmware. This time, it doesnt get stuck at the boot animation, instead it redirects to a screen with an android face saying "Installing System updates". A few seconds later, it says "No command" with a dead android face. Then it reboots and the same thing happens. Basically a boot loop, but in a different way. I cant seem to boot to stock recovery either. The worst thing is that I cant even turn off the thing. I have to leave it loop for the entire day until its battery dies
Click to expand...
Click to collapse
after flashing the combination firmware, flash the stock firmware and go thru the boot process
Youdoofus said:
after flashing the combination firmware, flash the stock firmware and go thru the boot process
Click to expand...
Click to collapse
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Rapidfayaround said:
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Click to expand...
Click to collapse
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Rapidfayaround said:
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Click to expand...
Click to collapse
the "no such file or directory" error is due to either having had removed stock recovery in flashing the firmwares or the factory recovery corrupted due to likely the same reason. Just flash a revision 7 firmware for your phone and it will at least boot
Dark Stranger said:
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Click to expand...
Click to collapse
^^^ this ^^^
Dark Stranger said:
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Click to expand...
Click to collapse
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Rapidfayaround said:
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Click to expand...
Click to collapse
I am somehow relieved to know that someone else on this planet is on the same (EXACT) boat as me....this is what we get for messing around too much with our phone hum?
1 - After booting up my phone I get the blue background with a dead Android and "No Command" message
2 - I tried accessing recovery by pressing Power+Home+VolumeUp, but all I get is a black screen with a wall of code lines with "fail to open recovery_cause(No such file or directory)" at the beggining of the text.
3 - "No problem! I'll just flash TWRP with ODIN and install a custom ROM and be done with it!".
..NOPE! FRP(factory reset protection) is ON!!! I cannot install TWRP
4- I've tried to find a combination file with binary version 7...but looks like the internet doesn't seem to care about the good ol' number 7...All I can find is binary version 6.
What Im trying to do now is creating my own combination file binary version 7 (if that's even a thing...) from a stock firmware. But I'm not getting any luckier down this path.
Looks like we need a hero...:crying:
PseudoNoob said:
I am somehow relieved to know that someone else on this planet is on the same (EXACT) boat as me....this is what we get for messing around too much with our phone hum?
1 - After booting up my phone I get the blue background with a dead Android and "No Command" message
2 - I tried accessing recovery by pressing Power+Home+VolumeUp, but all I get is a black screen with a wall of code lines with "fail to open recovery_cause(No such file or directory)" at the beggining of the text.
3 - "No problem! I'll just flash TWRP with ODIN and install a custom ROM and be done with it!".
..NOPE! FRP(factory reset protection) is ON!!! I cannot install TWRP
4- I've tried to find a combination file with binary version 7...but looks like the internet doesn't seem to care about the good ol' number 7...All I can find is binary version 6.
What Im trying to do now is creating my own combination file binary version 7 (if that's even a thing...) from a stock firmware. But I'm not getting any luckier down this path.
Looks like we need a hero...:crying:
Click to expand...
Click to collapse
OMGGGGGGGG....Looks like I am not the only one. DAMN. Bro...tell me if you find a solution ok? Hopefully there is a way to solve this problem...there has to be one. And share your combination firmware after you finish it. Thank you very much
Rapidfayaround said:
OMGGGGGGGG....Looks like I am not the only one. DAMN. Bro...tell me if you find a solution ok? Hopefully there is a way to solve this problem...there has to be one. And share your combination firmware after you finish it. Thank you very much
Click to expand...
Click to collapse
No luck over here friend...
Desperate times require desperate measures. Have you ever tried flashing combination files from different S7 Edge versions?
I can find files for the G935A with a revision 7 of the binary...Im thinking flashing it into my G935F and see what happens. I've read the risks associated with installing firmwares from other phone versions, but I'll have a paperweight either way.
I'll keep this thread updated.
Rapidfayaround said:
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Click to expand...
Click to collapse
Doesn't really matter if you have a F or FD. I'd say you flash the latest stock rom for G935F or FD(which ever is latest) for any country regardless. By this you should be able to boot and won't get any odin errors.
UsmaniMustafa said:
Doesn't really matter if you have a F or FD. I'd say you flash the latest stock rom for G935F or FD(which ever is latest) for any country regardless. By this you should be able to boot and won't get any odin errors.
Click to expand...
Click to collapse
Can you provide me the link plz.
Turns out, its a hardware problem with the storage. Replacing the motherboard might be the solution I think. :/
I had solved my phone last day
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
hazratboss said:
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
Click to expand...
Click to collapse
Oh ok I will contact you
hazratboss said:
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
Click to expand...
Click to collapse
Does it matter if I use the cracked version without box. And no, I dont have the ufs cable. Is there anything else I can do?
Hi guys, I have the exact same problem with my S7 edge from T-mobile (g935t). Odin will only accept for flash the latest rom and after flash it reboots but I get BSOD. I tried a pit file also from an old g935T rom which was android 6.0 and I managed to get into recovery for a moment and I did a factory reset/wipe cache but after reboot entered again in a black screen and the blue led was lit. I finally removed the battery to turn the phone off. I can still enter download mode but is there anything else I can do to resurrect the phone?
Samsung s7 edge (g935f)
Hi everyone , please am having issue of NO COMMAND and i cant boot into recovery. My oem is on so i cant install twpr neither. Am on binary u8. Please any solution to recover my phone?
Very very good new guys...yep you guessed it right. I was able to fix this problem.
How you may ask? Follow these steps
Note: Make sure you have enough battery. Lack of battery charge in my case caused alot of problems.
1. Download a U7 Rom for your SM-G935F or SM-G935FD
2. Extract the Rom as well as the AP
3. After you extract the AP, you will be greeted with boot.lz4.img , recovery.lz4.img , system.lz4.img & meta-data
4. Make a backup of recovery.lz4.img and meta-data just in case. Also, make a copy of boot.lz4.img and rename the copied one to recovery.lz4.img. Don't forget to delete the original recovery and meta-data
5. Now, you should be left with boot.lz4.img , (modified) recovery.lz4.img and system.lz4.img.
6. Now, download this https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file
7. Now, make a .md5 file that contains (modified) recovery.lz4.img and system.lz4.img
8. After you are done making that .md5, flash it along with CSC, CP and BL.
9. You should directly boot into your device, (if you do), charge your phone for a while if the battery is lower than 20%.
10. Then, go to the settings and enable OEM Unlock before doing ANYTHING
11. Then, reboot to download mode and flash TWRP
12. Download the no-verity-encryption.zip
https://zackptg5.com/android.php#disverfe
13. Allow system modifications and format data (NOT WIPE)
14. If that doesn't work, go to TWRP, connect it to your PC and copy the no-verity-encryption.zip file and install it
15. If that still doesn't work then, follow this tutorial
https://www.google.com/amp/s/forum....niversal-dm-verity-forceencrypt-t3817389/amp/
16. Then, you should boot and yea...enjoy ?
If this method doesn't work then, you need to try different combinations.
Try packing these files in AP
1. Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
2. (Modified) Recovery.lz4.img & system.lz4.img
3. Meta-data, Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
If that doesn't work, I'm sorry this is how I fixed it. ?*
For anyone wondering how I fixed it well, firstly a HUGE THANKS TO @shah22 & @Tapas27sTapas2. This would have been LITERALLY IMPOSSIBLE WITHOUT THEM. So, basically I tried an AP with renamed recovery.lz4.img and system.lz4.img only along with CP, CSC and BL. Due to my phone having literally 0%, this journey was very difficult.
Feel free to ask any question
Very very good new guys...yep you guessed it right. I was able to fix this problem.
How you may ask? Follow these steps
Note: Make sure you have enough battery. Lack of battery charge in my case caused alot of problems.
1. Download a U7 Rom for your SM-G935F or SM-G935FD
2. Extract the Rom as well as the AP
3. After you extract the AP, you will be greeted with boot.lz4.img , recovery.lz4.img , system.lz4.img & meta-data
4. Make a backup of recovery.lz4.img and meta-data just in case. Also, make a copy of boot.lz4.img and rename the copied one to recovery.lz4.img. Don't forget to delete the original recovery and meta-data
5. Now, you should be left with boot.lz4.img , (modified) recovery.lz4.img and system.lz4.img.
6. Now, download this https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file
7. Now, make a .md5 file that contains (modified) recovery.lz4.img and system.lz4.img
8. After you are done making that .md5, flash it along with CSC, CP and BL.
9. You should directly boot into your device, (if you do), charge your phone for a while if the battery is lower than 20%.
10. Then, go to the settings and enable OEM Unlock before doing ANYTHING
11. Then, reboot to download mode and flash TWRP
12. Download the no-verity-encryption.zip
https://zackptg5.com/android.php#disverfe
13. Allow system modifications and format data (NOT WIPE)
14. If that doesn't work, go to TWRP, connect it to your PC and copy the no-verity-encryption.zip file and install it
15. If that still doesn't work then, follow this tutorial
https://www.google.com/amp/s/forum....niversal-dm-verity-forceencrypt-t3817389/amp/
16. Then, you should boot and yea...enjoy ?
If this method doesn't work then, you need to try different combinations.
Try packing these files in AP
1. Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
2. (Modified) Recovery.lz4.img & system.lz4.img
3. Meta-data, Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
If that doesn't work, I'm sorry this is how I fixed it. ?*
For anyone wondering how I fixed it well, firstly a HUGE THANKS TO @shah22 & @Tapas27s. This would have been LITERALLY IMPOSSIBLE WITHOUT THEM. So, basically I tried an AP with renamed recovery.lz4.img and system.lz4.img only along with CP, CSC and BL. Due to my phone having literally 0%, this journey was very difficult.
Feel free to ask any question
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.