Dear fellows kindly help my problem here.
days ago due to "intune" app by microsoft office 365, my j530y need to unroot, and somehow the intune app reads my stock rom as custom rom.
so i download and flash this "SM-J530Y - J530YDXU3BRH6 XID" from Ymobile site.
everything working just fine (in my opinion), until i tried to flash twrp and try to root. NOTHING WORKED, i tried several twrp tar and cf autoroot also fail.
the notifications are :
1. "Only official released binaries are allowed to be flashed(RECOVERY)"
ID:0/010> Odin engine v(ID:3.1301)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 22 M
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> recovery.img
<ID:0/010> RQT_CLOSE !!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Code:
Click to expand...
Click to collapse
2. i tried to downgrade to marshmllow/nougat and this error appear: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2"
3. last resource was just trying to flash custom rom (breeze+) which packed in zip file. the problem is when i want to flash it in the stock recovery, the process failure "can't mount /sdcard"
so please guys help me, i already browse several threads and days for downgrading this, but nothing cant pass this error message "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2
please help,
im not a rich guy, but i will share a bit of my money to anybody give me the proper solution
Thank you in advance:crying:
hacker812c said:
[RMM] RMM State Fix Oreo 8.1 OEM Unlock Fix Dez 2018
This for users with RMM State or OEM Unlock Fix
And for users install custom ROM after Oreo 8.xx
[IMPORTANT]
With this tutorial you can reactivate de OEM unlock Option
TO install twrp or Downgrade to 7.0 nougat
Or install Custom ROM Oreo
[FILES]
#Samsung drivers
#Latest Stock firmware 8.x from Sammobile
#Odin any release after 3.x
#Miracle box 2.85
[NOTE:]
Back up your IMPORTANT files in your phone.
[STEPS]
1. install samsung drivers
2. Disable antivirus and Charge your Battery J7
3. Extract miracle all zip files
4. Run miracle box loader (run as admin)
5. Set your time to 2 years past.
6. Then close miracle box.
7. Open miracle box loader again (you will see miracle box is working now)
8. Connect the phone.
(Always check the phone. if there something pops up, tick "always allow" then "allow") i start Miracle Box_Cracked 2.58 and select Try to 3 options
9. Click "Connect" button on the top left side on miracle box
10. Click "Samsung tab" on the miracle box
11. Click Scan on the top right corner
12. Set the mode selection into : Download then hit "Go" button you will notice that your phone is on download mode and its blank. Just let it be on that state its on the process right now.
13. Click on "Reset Reactivation/EE Locks
14. Hit " Start button" and now its on the process.
15. Reboot the phone in download just hold synchronously press vol - , home button , and power then wait until you get again in the selection and then select "Continue". As you can see there's no more RMM State: prenormal in info. It means you're almost there..
16. Flash Stock 8.1 via Odin.
17. Enter in Stock Recovery and Factory Reset
18. Install TWRP and install Custom ROM
[CHECK ON STOCK]
After reboot Oreo
Steps on Check REMOVING RMM
Setup your phone
You're done.. Check Dev Options and you see "OEM Toggle".
[NOTICE]
After flash Fix is normal
You will see error on the miracle.
That's okay you're almost there to get rid of it.
[LINKS]
Miracle Box:
https://www.techeligible.com/2018/04/03/download-miracle-2-58-with-loader/
https://drive.google.com/file/d/1n_UGxEEmvJFGym0li05GH5tw087_7GjW/view
Hacker812c
The secret of my success is Jesus
Dedicated To Sabrina Mello (2015)
Click to expand...
Click to collapse
Hi all,
My J530Y oem unlock didnt show, rmm state prenormal, cant do anything to root or do more than stock users do basically.
ive been aimlessly crying for help and waiting if there's any update..ive been searching for this answer from July 2018.
So here's why i can work it out:
1. i read this thread just today, and realized there's some miracle called miracle box
2. i used miracle box to "RESURFACE" the OEM Unlock toggle in developer mode (3 times i fail, realized i have to use the newest stock rom of 8.1, indonesian region you can find it here) using odin until i make the oem unlock re-appear (this stock firmware is just temporary so at the end i replaced it with custom rom Breeze+)
3. im using twrp from here, countless time failure until i realized i should really read the guide to flash the twrp in odin, notice no7 that you have to untick auto reboot. read through and it should work!
4. last problem in twrp was it cant mount data partition, the solution is here, notice the faq part
5. so TWRP done, the next thing i do was installing these files in TWRP from OTG >RMM State Lock fix, and no-verity-opt-encrypt-6.0.zip
6. Last, im installing Breeze+ Also in TWRP and still using OTG. (i prefer using this because its prerooted with magisk, which is nice because i need the Intune Hider4magisk so i still can work freely with rooted device
7. I never "REBOOT SYSYEM" from step 4 to 6, since i tried and just realized need to install the custom rom at no6.
Might this help for my fellow J530Y users whose had the same problem as me.
Thank you all.
em. said:
Dear fellows kindly help my problem here.
days ago due to "intune" app by microsoft office 365, my j530y need to unroot, and somehow the intune app reads my stock rom as custom rom.
so i download and flash this "SM-J530Y - J530YDXU3BRH6 XID" from Ymobile site.
everything working just fine (in my opinion), until i tried to flash twrp and try to root. NOTHING WORKED, i tried several twrp tar and cf autoroot also fail.
the notifications are :
1. "Only official released binaries are allowed to be flashed(RECOVERY)"
2. i tried to downgrade to marshmllow/nougat and this error appear: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2"
3. last resource was just trying to flash custom rom (breeze+) which packed in zip file. the problem is when i want to flash it in the stock recovery, the process failure "can't mount /sdcard"
so please guys help me, i already browse several threads and days for downgrading this, but nothing cant pass this error message "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2
please help,
im not a rich guy, but i will share a bit of my money to anybody give me the proper solution
Thank you in advance:crying:
Click to expand...
Click to collapse
You have to wait for a week to flash twrp. Its a part of the Oreo update that the bootloader remains locked for 7 days
garylawwd said:
You have to wait for a week to flash twrp. Its a part of the Oreo update that the bootloader remains locked for 7 days
Click to expand...
Click to collapse
hi,
i kept my phone awake for 3 weeks and no UEM unlock on devlpr option, do u know why ?
i keep searching for some threads that actually got the uem unlock option in just one week, but not mine.
help.......
Same problem here on G570M.
Does anybody know if Oreo bootloader lock with olders Security patch can be bypassed changing date and making manual updates? I'm stucked right here.
em. said:
Dear fellows kindly help my problem here.
days ago due to "intune" app by microsoft office 365, my j530y need to unroot, and somehow the intune app reads my stock rom as custom rom.
so i download and flash this "SM-J530Y - J530YDXU3BRH6 XID" from Ymobile site.
everything working just fine (in my opinion), until i tried to flash twrp and try to root. NOTHING WORKED, i tried several twrp tar and cf autoroot also fail.
the notifications are :
1. "Only official released binaries are allowed to be flashed(RECOVERY)"
2. i tried to downgrade to marshmllow/nougat and this error appear: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2"
3. last resource was just trying to flash custom rom (breeze+) which packed in zip file. the problem is when i want to flash it in the stock recovery, the process failure "can't mount /sdcard"
so please guys help me, i already browse several threads and days for downgrading this, but nothing cant pass this error message "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2
please help,
im not a rich guy, but i will share a bit of my money to anybody give me the proper solution
Thank you in advance:crying:
Click to expand...
Click to collapse
same problem on SM-J530G
renguer0 said:
Same problem here on G570M.
Does anybody know if Oreo bootloader lock with olders Security patch can be bypassed changing date and making manual updates? I'm stucked right here.
Click to expand...
Click to collapse
WandresJersey said:
same problem on SM-J530G
Click to expand...
Click to collapse
Have you guys had any solution to this?
em. said:
Have you guys had any solution to this?
Click to expand...
Click to collapse
Just seven days waiting. There is a patch when unlocking bootloader that able to unlock without this trouble.
em. said:
Dear fellows kindly help my problem here.
days ago due to "intune" app by microsoft office 365, my j530y need to unroot, and somehow the intune app reads my stock rom as custom rom.
so i download and flash this "SM-J530Y - J530YDXU3BRH6 XID" from Ymobile site.
everything working just fine (in my opinion), until i tried to flash twrp and try to root. NOTHING WORKED, i tried several twrp tar and cf autoroot also fail.
the notifications are :
1. "Only official released binaries are allowed to be flashed(RECOVERY)"
2. i tried to downgrade to marshmllow/nougat and this error appear: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2"
3. last resource was just trying to flash custom rom (breeze+) which packed in zip file. the problem is when i want to flash it in the stock recovery, the process failure "can't mount /sdcard"
so please guys help me, i already browse several threads and days for downgrading this, but nothing cant pass this error message "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2
please help,
im not a rich guy, but i will share a bit of my money to anybody give me the proper solution
Thank you in advance:crying:
Hi all,
My J530Y oem unlock didnt show
Thank you all.
Click to expand...
Click to collapse
Thank for reply
If twrp correctly installed and internal memory not encrypt is possible flash any rom
Two problems
1 sd encrypt
2 OEM unlock and RMM state
I searching solution for You
Hacker friend
---------- Post added at 10:33 AM ---------- Previous post was at 10:22 AM ----------
renguer0 said:
Just seven days waiting. There is a patch when unlocking bootloader that able to unlock without this trouble.
Click to expand...
Click to collapse
So i will not go back to official rom
Samsung stupid software
Hacker
hacker812c said:
Thank for reply
If twrp correctly installed and internal memory not encrypt is possible flash any rom
Two problems
1 sd encrypt
2 OEM unlock and RMM state
I searching solution for You
Hacker friend
---------- Post added at 10:33 AM ---------- Previous post was at 10:22 AM ----------
So i will not go back to official rom
Samsung stupid software
Hacker
Click to expand...
Click to collapse
See last post mine on TWRP thread. I've posted a solution to this.
If you have your phone briked you can upload stock rom from odin. Take care about the version, you can't downgrade.
renguer0 said:
See last post mine on TWRP thread. I've posted a solution to this.
If you have your phone briked you can upload stock rom from odin. Take care about the version, you can't downgrade.
Click to expand...
Click to collapse
Very important this information
Thank You
Report below => text form post @Renquer0 (thanks)
About TWRP => Error on twrp installing any zip rom, magisk or kernel
When ENCRYPTION message is showed when booting DON'T CLICK IN RESET.
You need to enable data partition (guide quoted) and then install Magisk,
RMM State Bypass and no-verity-opt-encrypt-6.0 files in that order.
This is the entire quoted post:
renguer0 said:
For everyone that can't mount or format data (this f**k up the entire rooting process) you can follow this:
sharneil said:
While formatting device using TWRP re., device failed and showed me something like "unable to mount /data or system"
This happens because your recovery is unable to read internal storage. You need to do some small steps.
Steps
1) Reboot into TWRP recovery
2) go to " Wipe "
3) then " Advanced Wipe "
4) Choose " data " and tap on " Repair or Change File System "
5) Then tap " Change File System "
You will see text as ext4 infront of ' file system '
6) Change it to "EXT2" by tapping and swiping.
7) Once its done, change it to "EXT4" again.
(if some detail doesn't match after step 5, don't worry... Change file system path to something else then and to default again.)
DONE !
Then go back and try formatting ( or any other work ). It should succeed.
This method worked for me where I was using Redmi Note 4 with custom(Lineage) os and TWRP 3.2.3.0
If this doesn't work, then try once again or I will suggest you to install TWRP recovery again.
Thank you.
Click to expand...
Click to collapse
Maybe the OP can add it to the first post. This allowed to me to install TWRP and Magisk in my J5 Prime.
When ENCRYPTION message is showed when booting DON'T CLICK IN RESET. You need to enable data partition (guide quoted) and then install Magisk, RMM State Bypass and no-verity-opt-encrypt-6.0 files in that order.
Click to expand...
Click to collapse
Hope it helps. In my case I couldn't format data partition in TWRP until I changed filesystem to EXT2 and EXT4.
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:
Hello guys, I'm in dire need of your expertise, I'm stuck on a "custom binary blocked by frp" error... I can't flash stock roms, I can't boot into recovery, I can't turn on the phone... I can't do anything, all the time same error.... I never rooted or used custom roms, all I did was flash different stock firmwares cause my original was unstable and restarted and crashed apps constantly... flashed 2 or 3 stock firmwares which had the same problems until this happened as I was about to flash another firmware... PLEASE HELP ME ... or idk what i will do if i dont fix this... :crying:
theSperks said:
Hello guys, I'm in dire need of your expertise, I'm stuck on a "custom binary blocked by frp" error... I can't flash stock roms, I can't boot into recovery, I can't turn on the phone... I can't do anything, all the time same error.... I never rooted or used custom roms, all I did was flash different stock firmwares cause my original was unstable and restarted and crashed apps constantly... flashed 2 or 3 stock firmwares which had the same problems until this happened as I was about to flash another firmware... PLEASE HELP ME ... or idk what i will do if i dont fix this... :crying:
Click to expand...
Click to collapse
You probably have the oem lock enabled at the moment. Use smart switch and try to do an emergency recovery. This will flash stock rom.
When you have successfully restored your phone. Enable developer settings. And unlock the oem tick
Sent from my SM-G935F using Tapatalk
Michel habets said:
You probably have the oem lock enabled at the moment. Use smart switch and try to do an emergency recovery. This will flash stock rom.
When you have successfully restored your phone. Enable developer settings. And unlock the oem tick
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
I tried many times.... both emergency and initalization fail with and error and downloading mode shows "SECURE CHECK FAIL : (BOOTLOADER) ... I flashed a CP file an hour ago and got myself to recovery, but it fails to mount system with a lot of other mount fails... please help
I think it's cause I didn't set up secure start up and i think i disabled oem unlock and usb debugging, but usb works just fine... and didn't delete google account... but still I shouldnt be locked out so badly, I can't do anything... I can't flash via odin cause frp... mannaged to flash a BL and a CP file and nothing else. Still can't boot or flash AP or CSC cause of frp-fap or w/e it is... and recovery doesn't help since system is empty or non existant... not sure.. pls help
If you got yourself tor recovery. Do a full wipe there. It will disable the protection on it if I'm correctly. Try that step.
You said you could flash the bl. Doest it pass or fail when you try the same thing with a complete rom?
Sent from my SM-G935F using Tapatalk
---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------
theSperks said:
I tried many times.... both emergency and initalization fail with and error and downloading mode shows "SECURE CHECK FAIL : (BOOTLOADER) ... I flashed a CP file an hour ago and got myself to recovery, but it fails to mount system with a lot of other mount fails... please help
I think it's cause I didn't set up secure start up and i think i disabled oem unlock and usb debugging, but usb works just fine... and didn't delete google account... but still I shouldnt be locked out so badly, I can't do anything... I can't flash via odin cause frp... mannaged to flash a BL and a CP file and nothing else. Still can't boot or flash AP or CSC cause of frp-fap or w/e it is... and recovery doesn't help since system is empty or non existant... not sure.. pls help
Click to expand...
Click to collapse
Ow and BTW. You being like locked out so badly is just a sign that the initial purpose. Namely to apprehend someone getting to your data works perfectly
Sent from my SM-G935F using Tapatalk
Michel habets said:
If you got yourself tor recovery. Do a full wipe there. It will disable the protection on it if I'm correctly. Try that step.
You said you could flash the bl. Doest it pass or fail when you try the same thing with a complete rom?
Sent from my SM-G935F using Tapatalk
---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------
Ow and BTW. You being like locked out so badly is just a sign that the initial purpose. Namely to apprehend someone getting to your data works perfectly
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
When I do a wipe data/factory reset it cleans everything but has an error / E:failed to mount /system (invalid argument) can't mount '/system', rc = '-1' (Invalid argument) and then data wipe complete...
tried to mount the /system as well, and again e:failed to mount...
As for the flashing a rom all together doesn't work, almost all images files are denied by FRP - FAP w/e it is.... with a green msg in downloading mode "Custom Binary (your img here) Blocked by FRP/FAP Lock ... recovery.img,boot.img, system.img etc... , only can flash CP and BL, BUT the BL file that I can actually flash is from a SM-G935F_BTU_G935FXXU1APC8, my stock firmware which is german vodafone's latest ( G935FXXS1BPI8_G935FVFG1BPH1_VD2) BL, AP and CSC can't be flashed with odin ... BL fails with Secure Check Fail (bootloader) as does it fail in smart switch program.
My model number is SM-G935F ...and RF8H61YE4CP for S / N or what ever it was, too tired, I've been trying to fix the phone for 16 straight hours... pls help
My main problem is that Smart Switch can't restore, it stops at 0% installing phase, since the BL ie the bootloader can't be installed. the download screen says in red SECURE CHECK FAIL : (BOOTLOADER) i'm 99% if I manage to somehow make smart switch install the bootloader ie the first thing it wants to install, everything else would fly since smart switch ignores the FRP/FAP , or so I heard. pls help guys there must be a solution hiding somewhere...
theSperks said:
My main problem is that Smart Switch can't restore, it stops at 0% installing phase, since the BL ie the bootloader can't be installed. the download screen says in red SECURE CHECK FAIL : (BOOTLOADER) i'm 99% if I manage to somehow make smart switch install the bootloader ie the first thing it wants to install, everything else would fly since smart switch ignores the FRP/FAP , or so I heard. pls help guys there must be a solution hiding somewhere...
Click to expand...
Click to collapse
If smart switch can't restore it the I'm out of options. Smart switch basic forces permission to restore the system.
Flashing a different bootloader isnt going to do anything if I'm correct. If the system and data image is intact you could try to flash the bootloader that goes with that rom.
That way it might boot and you would need to enter your Google credentials.
I messaged you a link to rootjunky with a bypass in the front. You might want to try that.
Otherwise you could try to flash a different recovery ( Philz?) that might gain access to the image.
If the data and system image is wiped. Then the only thing you can work with is odin.
I have no knowledge of adb, don't know if there are some options with sideload
Sent from my SM-G935F using Tapatalk
After a good night sleep, today I tried to flash the same AP as y-day and it worked. I successfully unbricked my s7 edge. The FRP/FAP lock that didn't let me flash probably had a timer and today it let me. Thank you god, and thank u guys for trying to help me.
Good to hear that you got it up and running. The frp lock was 3 days first. Well at least the Google credentials section. But after many customer support has been rolled back to 24 hours
Sent from my SM-G935F using Tapatalk
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?
Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
Click to expand...
Click to collapse
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request
ngvhoang96 said:
Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request
Click to expand...
Click to collapse
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.
Stixas said:
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.
Click to expand...
Click to collapse
Last time I tried download fw by using samfirm was last week and it didnt work. Can you test yours again?
And whre can I found the pit file? I dont think there is one in the internet right now.
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