Related
i have tried every twrp but phone stucks on galaxy s7edge screen when trying to access recovery ? plz anybody ?
i have done many posts related to my s7edge g935f , its just kept in the cupboard and cant use it from several months because of the dmverity error , i need to root it and use custom rom plz ?
Put the phone in download mode, use Samsung Smartswitch to reinstall stock rom
surfer3000 said:
Put the phone in download mode, use Samsung Smartswitch to reinstall stock rom
Click to expand...
Click to collapse
i have already done that , it stuck on modem part , secure check radio fail and when i flash without modem , it successfully flashed but root issue , when i flash twrp , it doesnt boot into into twrp and stuck on logo?
I do not believe that you see a "modem" part when using smart switch? Otherwise use Samsung Kies for S7 edge. And do the Firmware Upgrade and Initialization menu item
surfer3000 said:
I do not believe that you see a "modem" part when using smart switch? Otherwise use Samsung Kies for S7 edge. And do the Firmware Upgrade and Initialization menu item
Click to expand...
Click to collapse
i have done every try , it doesn't accept the modem part , i am teally confused about it , so much long time passed and just kept the phone useless, samsung switch is showing it g935f o2u model but not accepting o2u firmware too
suhaibahmad said:
i have done every try , it doesn't accept the modem part , i am teally confused about it , so much long time passed and just kept the phone useless, samsung switch is showing it g935f o2u model but not accepting o2u firmware too
Click to expand...
Click to collapse
Mmmm, before u flash TWRP, u should enable oem unlock on developer option
aditia581999 said:
Mmmm, before u flash TWRP, u should enable oem unlock on developer option
Click to expand...
Click to collapse
yes i have enabled that and also usb debugging
What to do : Reflash the stock firmware , after that is completed , turn off the phone , and install on your pc : the No verify Opt encrypt 5.0 from here:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip
And the SuperSu file from here :
https://download.chainfire.eu/supersu
Now go download the latest Odin, and connect your phone.
Flash the Twrp 3.1.0.0 ( be aware to choose the file for Hero2lte) and reboot to recovery.
DO NOT LET IT BOOT INTO THE SYSTEM.
IF IT DOES , IMEDIATLEY CLOSE THE PHONE AND BOOT INTO RECOVERY .
Once you are in recovery , firstly go to wipe and do a factory reset .
Then connect your s7E to the PC while you are in the TWRP , and copy the SuperSu file and the verity opt oncryption to the storage.
Note: if you have an SD card inserted , copy the files to the SD not the internal storage.
Now , pay attention , If you don't do the next steps in the right order , you may brick your beautiful 800$ phone.
So pay attention , you have to firstly run the No verity encrypt file.
After it's done, go back >reboot>reboot in recovery.
Now search the file and run it (the SuperSu file)
It will take a bit longer to flash the SuperSu.
After it's done , reboot
Note: your phone should reboot 2 times , If it doesn't or it reboots more than 3 times, CLOSE your phone , and repeat the whole process.
IF your phone reboots 2 times , your are good to go .
The first BOOT May take some time (usually around 6 minutes) and it may loop a couple times, DO NOT INTERRUPT THE PROCES !
IF your phone boots up successfully, configure it and run a root checker , it should say : congratulations your device is rooted.
IF IT doesn't, well you have had to mess something up during the process.
Hope that helped , let me know if it did
allahTch said:
What to do : Reflash the stock firmware , after that is completed , turn off the phone , and install on your pc : the No verify Opt encrypt 5.0 from here:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip
And the SuperSu file from here :
https://download.chainfire.eu/supersu
Now go download the latest Odin, and connect your phone.
Flash the Twrp 3.1.0.0 ( be aware to choose the file for Hero2lte) and reboot to recovery.
DO NOT LET IT BOOT INTO THE SYSTEM.
IF IT DOES , IMEDIATLEY CLOSE THE PHONE AND BOOT INTO RECOVERY .
Once you are in recovery , firstly go to wipe and do a factory reset .
Then connect your s7E to the PC while you are in the TWRP , and copy the SuperSu file and the verity opt oncryption to the storage.
Note: if you have an SD card inserted , copy the files to the SD not the internal storage.
Now , pay attention , If you don't do the next steps in the right order , you may brick your beautiful 800$ phone.
So pay attention , you have to firstly run the No verity encrypt file.
After it's done, go back >reboot>reboot in recovery.
Now search the file and run it (the SuperSu file)
It will take a bit longer to flash the SuperSu.
After it's done , reboot
Note: your phone should reboot 2 times , If it doesn't or it reboots more than 3 times, CLOSE your phone , and repeat the whole process.
IF your phone reboots 2 times , your are good to go .
The first BOOT May take some time (usually around 6 minutes) and it may loop a couple times, DO NOT INTERRUPT THE PROCES !
IF your phone boots up successfully, configure it and run a root checker , it should say : congratulations your device is rooted.
IF IT doesn't, well you have had to mess something up during the process.
Hope that helped , let me know if it did
Click to expand...
Click to collapse
thanks for such a nice tutorial , the problem is my phone is o2u and flashing issue in the modem part even i have tried with samsung switch , anyhow that is not a big issue now whenever i only flash ap , the phone boots successfully and i can enable oem unlocking and developer option and when i flash twrp and wants to boot into it , the phone stuck there
suhaibahmad said:
thanks for such a nice tutorial , the problem is my phone is o2u and flashing issue in the modem part even i have tried with samsung switch , anyhow that is not a big issue now whenever i only flash ap , the phone boots successfully and i can enable oem unlocking and developer option and when i flash twrp and wants to boot into it , the phone stuck there
Click to expand...
Click to collapse
I had the same issue to fix.
open smart switch and use the emergency initialization and recovery feature.
it will ask for your model and serial number which is on a sticker on the back of your phone.
Cosmic Blue said:
I had the same issue to fix.
open smart switch and use the emergency initialization and recovery feature.
it will ask for your model and serial number which is on a sticker on the back of your phone.
Click to expand...
Click to collapse
I have tried that , that also stucks in the modem part and give radio fail secure check error , i cant even flash it , i was thinking i will root it and install a custom rom but it cant boot to twrp , and if i just flash the AP part then the device boots successfully and the imei and baseband everything ok . Just the hidden codes not work , its really a weird issue , im really confused about it
suhaibahmad. When you refer to "whenever I only flash AP"you are referring to using ODIN, NOT SMARTSWITCH. There is a difference.
surfer3000 said:
suhaibahmad. When you refer to "whenever I only flash AP"you are referring to using ODIN, NOT SMARTSWITCH. There is a difference.
Click to expand...
Click to collapse
on smartswitch it stucks in the modem part and flash radio fail error on the screen . and now come to odin , if i just flash AP in odin then the phone boots successfully but not good performance and cant even root it
Plz anybody help , my phone is just a piece of .....
I successfully rooted my phone but it got stuck in a bootloop when I restarted it.
I can't enter recovery mode or turn it off, all I can do is enter odin mode.
I have tried:
1. The AGQ5 fix (https://forum.xda-developers.com/ga...g-aqg5-fix-t3636857/post73032395#post73032395) it doesn't work.
2. Smart switch, it says my device is unsupported
Please help!
1- flash twrp again
2- flash stock rom with odin ( download mode )
you can reboot just with vol - + shut down B
you maybe installed the wrong version of twrp the latest one is for the new bootloader if you have the older bootloader install the last version
It doesn't boot into TWRP even after I flash it again
djisgod said:
you maybe installed the wrong version of twrp the latest one is for the new bootloader if you have the older bootloader install the last version
Click to expand...
Click to collapse
Sorry if I'm asking a question but how do I check my bootloader version? I just used the latest version (twrp-3.1.1-0-herolte.img.tar) from a site but I can't link it.
popmpopm said:
1- flash twrp again
2- flash stock rom with odin ( download mode )
you can reboot just with vol - + shut down B
Click to expand...
Click to collapse
It doesn't boot into TWRP even after I flash it again
Flash full stock in odin. Then you can try twrp again if you wish.
It worked, thanks so much for all your help. Words cannot describe how grateful I am.
help
osidaksjdmw said:
It worked, thanks so much for all your help. Words cannot describe how grateful I am.
Click to expand...
Click to collapse
help me
how can did you get to download
HELP ! S8 Wont BOOT !!
I have the same problme! I can flash Combination file and then its booting and I can go to recovery mode ,but after when I flash again STOCK rom succesfully ,S8 wont boot Any Idea what is going on ? Im on U2CRED ....PLEASE HELP !!!!
zassamel said:
I have the same problme! I can flash Combination file and then its booting and I can go to recovery mode ,but after when I flash again STOCK rom succesfully ,S8 wont boot Any Idea what is going on ? Im on U2CRED ....PLEASE HELP !!!!
Click to expand...
Click to collapse
I can flash Combination file
Click to expand...
Click to collapse
What this supposed to me ?
samsung s8
StonebridgeGr said:
What this supposed to me ?
Click to expand...
Click to collapse
Combination File ,its AP witch allow you to bypass for example FRP lock
osidaksjdmw said:
I successfully rooted my phone but it got stuck in a bootloop when I restarted it.
I can't enter recovery mode or turn it off, all I can do is enter odin mode.
I have tried:
1. The AGQ5 fix (https://forum.xda-developers.com/ga...g-aqg5-fix-t3636857/post73032395#post73032395) it doesn't work.
2. Smart switch, it says my device is unsupported
Please help!
Click to expand...
Click to collapse
EXACT same problem. Put I cant flas anything via Odin. Not even TWRP. What do I do???
PLEASE help
benna said:
EXACT same problem. Put I cant flas anything via Odin. Not even TWRP. What do I do???
PLEASE help
Click to expand...
Click to collapse
why you cant? what error did it give you? might you dont have drivers installed on your pc?
StonebridgeGr said:
why you cant? what error did it give you? might you dont have drivers installed on your pc?
Click to expand...
Click to collapse
ODIN MODE
DOWNLOAD SPEED : FAST
NAME: SM-G950F
CURRENT BINARY: CUSTOM
SYSTEM STSTUS : CUSTOM
RMM STATE: PRENORMAL
FAP LOCK: OFF
OEM LOCK : OFF
SECURE DOWNLOAD: ENABLED
SW REV. CHECKFAIL(BOOTLOADER) DEVICE :2 BINARY :1
I can ONLY boot into download mode.
When switching on the phone , I get the Galaxy S8 logo by Samsung with the red writing on the top:
"Only officiall released binaries are allowed to be flashed"
Flashing original firmware via ODIN just fails.
"Complete (write) operation failed !!" is the error in Odin.
I tried different versions of Odin , original firmware and boot loaders suggested on XDA. All just fails.
So my phone is just dead.
I had the lasted firmware on ( OTA update about a week ago)
I installed TWRP now , roooted with Magisk , all was fine untill I rebooted the phone.
So drivers and all are fine , everything worked until I rebooted the phone.
Please help. What to do now. I need my phone !!!
PLEASE
Hi,
So I rooted this device successfully but with my dumb head I apparently disabled OEM unlock.
Now my device is not booting. It only shows the samsung logo. I can go to download mode and android recovery.
I already tried:
- Wipe data
- Install stock firmware using Odin
- Install TWRP using Odin
None of this worked. It gives errows like "Custom binary blocked by FRP"
How can I possibly turn on the OEM while Im unable to go into Android?
Michelium said:
Hi,
So I rooted this device successfully but with my dumb head I apparently disabled OEM unlock.
Now my device is not booting. It only shows the samsung logo. I can go to download mode and android recovery.
I already tried:
- Wipe data
- Install stock firmware using Odin
- Install TWRP using Odin
None of this worked. It gives errows like "Custom binary blocked by FRP"
How can I possibly turn on the OEM while Im unable to go into Android?
Click to expand...
Click to collapse
I've found the solution for this problem. Thanks anyways.
Michelium said:
I've found the solution for this problem. Thanks anyways.
Click to expand...
Click to collapse
What was the solution?
i have the exactly same problem.
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
Hi there,
I have a Samsung Galaxy Tab A6 (SM-T285) which I bought today. I followed this tutorial to install twrp, ultimately to root the device:
I can't even post links so sad. But the link was of **********.
Everything worked fine and I was able to boot and reboot fine. Until I signed in with my Google Account. After trying to reboot, I get a black screen with the Samsung logo and a text in red saying: Custom binary blocked by FRP Lock. I went back to the store and they advised me to install Samsung Smart Switch to try and restore. In the Smart Switch program I get an error saying that the device is not supported by Smart Switch.
I can get into download mode, not into any other mode. I can't get into recovery mode. The tablet doesn't start up at all. On the download mode it also says FRP Lock ON.
When I go back into ODIN and retry to install the from above TWRP image, it says operation failed.
Can anybody please advice? I am at a complete loss. Am I supposed to flash the original boot file? Where can I find that for my device? Will my tablet accept that, since ODIN didn't even want to flash my current TWRP image a second time?
P.S. I only read later that you are supposed to change the OEM setting. I didn't. Is that the cause of this issue, and if so, can I do something about it?
Thanks
Pro_Gamer368 said:
Hi there,
I have a Samsung Galaxy Tab A6 (SM-T285) which I bought today. I followed this tutorial to install twrp, ultimately to root the device:
I can't even post links so sad. But the link was of **********.
Everything worked fine and I was able to boot and reboot fine. Until I signed in with my Google Account. After trying to reboot, I get a black screen with the Samsung logo and a text in red saying: Custom binary blocked by FRP Lock. I went back to the store and they advised me to install Samsung Smart Switch to try and restore. In the Smart Switch program I get an error saying that the device is not supported by Smart Switch.
I can get into download mode, not into any other mode. I can't get into recovery mode. The tablet doesn't start up at all. On the download mode it also says FRP Lock ON.
When I go back into ODIN and retry to install the from above TWRP image, it says operation failed.
Can anybody please advice? I am at a complete loss. Am I supposed to flash the original boot file? Where can I find that for my device? Will my tablet accept that, since ODIN didn't even want to flash my current TWRP image a second time?
P.S. I only read later that you are supposed to change the OEM setting. I didn't. Is that the cause of this issue, and if so, can I do something about it?
Thanks
Click to expand...
Click to collapse
Reinstall stock rom
Change OEM setting in Developer Options
Then you install TWRP - Turn off auto reboot in TWRP
After ODIN install, manually reboot to recovery.
gcrutchr said:
Reinstall stock rom
Change OEM setting in Developer Options
Then you install TWRP - Turn off auto reboot in TWRP
After ODIN install, manually reboot to recovery.
Click to expand...
Click to collapse
wait......... do i off oem unlock or on it
Pro_Gamer368 said:
wait......... do i off oem unlock or on it
Click to expand...
Click to collapse
slide the button to the right
gcrutchr said:
slide the button to the right
Click to expand...
Click to collapse
thanks, you're a legend :good::good::good: