bricked S6 until further updates? - Galaxy S6 Q&A, Help & Troubleshooting

I did something very stupid, I rooted my S6 today and turned off that OEM unlock mode and rebooted my s6 and now it gets stuck in the boot up screen and says custom binary blocked by FRP Lock, I was able to get to the download update page and the recovery page but I cant do anything with it, odin will not let me flash because of the FRP Lock, now I am downloading the latest stock rom for my S6, the same as the rooted one that I had, would I be able to flash it using odin? I heard that you can flash official stock rom even with the FRP Lock, you just cant downgrade it, but what about the same version, can I flash it successfully, or would I have to wait till the next version roll out? thanks for any info

I had this same issue, i could flash the same but sometimes the boot loader becomes corrupt and if that is the case you have to wait for a new update. As a side note, next time back up your EFS partition as this can save you from issues like this. you can make it into a tar to flash via Odin. Wanam makes a awesome app for this.

Related

Galaxy S6 Unable to boot into TWRP recovery

..
you asked the same question I was going to ask....hopefully someone replies to you, I'll keep asking around the interwebs for a solution I already asked Max Lee and still no reply. I'm rooted too (cf auto root) but i want twrp just in case.
I'm trying for 2 days for my 920i and I ha e twrp now I flashed 920f and boot fine!
https://www.fshare.vn/file/B38M8WL1ZQDE
merrykid said:
I'm using G920I Australia version.
I can successfully root using CF-Auto-Root.
But I can not get into TWRP recovery after I flashed that (tried both versions of the recovery) using odin. It stops at the first screen (samsung logo). I tried using adb commond reboot recovery and the hardware key (volum up+power+home), both of them do not let me in to the custom recovery.
I had tried enabled knox before flash TWRP, which made it into boot loop. And then recoveried using the official firmware. Now I can only get into the official recovery.
Any suggestions for how to get into the TWRP?
BTW, how to backup the pit file using adb? On previous models it was mmcblk0, but Galaxy S6 seems to have changed the memory map to sda1, sda2, etc.
Click to expand...
Click to collapse
I got the 920i Aus version too. I was told two different things.
Update firmware to AOD1 and flash TWRP and it should work.
-or-
Use the 920t as jah2110 says. I would find the file from somewhere more 'reputable'.
Downloading a AOD1 firmware now from sammobile which is awful slow. First one I tried to flash gave me fail in odin so im trying a different one.
Stuck at the Samsung logo after trying to flash the recovery via twrp app, now it doesn't even boot normally. so if you want to install twrp don't use the app, G920I telstra version
Just flash an AOD1 firmware or more. The new zealand firmware for instance and then twrp is gonna work.
If you are stuck after flashing twrp on the australian firmware just flash root using odin and you will be able to start your device again
massacreur75010 said:
Just flash an AOD1 firmware or more. The new zealand firmware for instance and then twrp is gonna work.
If you are stuck after flashing twrp on the australian firmware just flash root using odin and you will be able to start your device again
Click to expand...
Click to collapse
really? i didn't know that, anyway, if you want to update/reinstall the stock firmware, sammobile is so bloody slow, i deem it unusable, so i found this gem, much faster than sammobile, i downloaded at 1.3MB/s so it takes just over 20 minutes for the whole firmware. http://galaxys6root.highonandroid.com/galaxy-s6-stock-firmware/ give it a try if sammobile just pisses you off.
Yes it took me a few days to figure it out and everyone kept saying that twrp should work ...but thats just a matter of firmware version.
So is there a fix? I can get root but TWRP just sites and the boot screen.
I've been in the same situation using a Aussie Voda 920i, I was able to root using CF auto root but then had deep sleep issue & couldn't install TWRP. Now i've installed the singapore firmware & also got TWRP running but cant root.
If I use ODIN to root its gets stuck on logo screen & If I use TWRP it appears to go OK but just doesn't work. Also although CPU Spy says I am getting deep sleep battery life seems awfull
Twrp gave me the boot screen for infinite as well. I live in Alaska. I had to reflash root file to boot. Never got twrp to work. I tried to flash via app. I don't even want more possible headache flashing it with Odin.
Surely if you've got root you can install twrp from the app store and let it replace the recovery.
Same issue
I had exactly the same issue, flashed TWRP from a reliable source and my phone bricked at start up logo screen, could only get into download mode, once i did that i reflashed with ODIN and autoroot file and phone came back alive. Thank god.
---------- Post added at 10:47 PM ---------- Previous post was at 10:43 PM ----------
Tried to install TWRP from official APP, said it installed recovery successfully would you like to attempt reboot and get into recovery, got stuck again at boot screen LOLLLL awesome...... piece of ****ware.
Same for me G920F. I tried twice both failed.
First time use this thread The phone was successfully rooteded. I installed "TWRP Manager.apk". It cause phone infinitely reboot.
Then I restore the stock ROM (you won't know how painful to download the 1.5G+ ROM).
Second time, I rooted again. And tried use freshily (?) to manually install an img in sdcard. It said success and reboot. But it stayed in boot logo.
I restore the stock ROM again (but the kies3 needs to download ROM again!).
I will not try a third time unless there is an right answer.
__________________
btw, the first one say 'oem unlock' must be checked. But I do not have this option, maybe because my phone is unlocked already (not binded to any one).
GrandMstrBud said:
So is there a fix? I can get root but TWRP just sites and the boot screen.
Click to expand...
Click to collapse
im a Noob but i was told that my TWRP was being overwritten during the reboot and that i Must flash a custom kernal after rooting so that the TWRP wouldn't be overwritten
SillyTAO said:
im a Noob but i was told that my TWRP was being overwritten during the reboot
Click to expand...
Click to collapse
This only happens when you fail to force the reboot into recovery yourself.
If you let the phone reboot automatically after flashing, it will be stuck @ bootloop; so you have to be faster & hold the vol up+home+power buttons *immediately* when Odin finishes the process.
Don't bother removing the cable or waiting for the screen to change, that will be too slow.
Cant boot in twrp after flashing thru odin
knox counter trips

Soft-Bricked S6

So i recently switched to a new rom from my previous rooted one. Unfortunatly, i forgot to enable developer debugging or oem unlock in developer options before i restarted, so now my phone is in a boot loop. It wont go into recovery mode, or boot into the system. I can only go into download mode. My knox is tripped, and it shows frp lock. So far i tried flashing the stock 5.1.1 firmware using odin, and it fails on nand write. Tried flashing a new bl and cp, but frp blocks it. What can i do to fix this!?
Right, model of my phone is SM-G920T
EDIT: Seems to be when i was trying to flash the original firmware, i got an old one, F6, when the correct one is F8. Went through with odin and seems like everything is back on track!
Flash this updated stock 5.1.1 ROM via odin to overcome your woes:
http://www.sammobile.com/firmwares/download/51233/G920TUVU2COF8_G920TTMB2COF8_TMB/

FRP Lock - unable to boot and flash

I recently bought an S7 and wanted to root. It's my first Samsung phone so the software is new to me so apologies if there is an easy answer. I (extremely stupidly) re-enabled FRP lock within Android after rooting (hoping that it was stop the unauthorised actions warning). This now means when i start the phone it states "Custom Binary Blocked by FRP lock" and would not boot in to Android. I've read some threads but the current situation is:
1) When i tried to boot it would not boot to Android and stuck at the first splash screen and warning. Whilst i had rooted i did not flash twrp so only have the stock recovery.
2) I went in to the stock recovery and did a factory reset and cache clear. No change.
3) I tried Smart switch and kies - no luck - both said un-supported device or hung on connecting
4) I went to the thread with the most recent stock download (Netherlands) and downloaded that. I tried to install that and it hung for about an hour. I disconnected and it now says "An error has occurred whilst updating the device software" and does not boot.
So i cannot boot in to Android, have no custom recovery and KIES/SmartSwap do not work.
Any ideas????!?!?
Download the latest MM stock rom and try to bypass the frp lock.
lord_melchett said:
I recently bought an S7 and wanted to root. It's my first Samsung phone so the software is new to me so apologies if there is an easy answer. I (extremely stupidly) re-enabled FRP lock within Android after rooting (hoping that it was stop the unauthorised actions warning). This now means when i start the phone it states "Custom Binary Blocked by FRP lock" and would not boot in to Android. I've read some threads but the current situation is:
1) When i tried to boot it would not boot to Android and stuck at the first splash screen and warning. Whilst i had rooted i did not flash twrp so only have the stock recovery.
2) I went in to the stock recovery and did a factory reset and cache clear. No change.
3) I tried Smart switch and kies - no luck - both said un-supported device or hung on connecting
4) I went to the thread with the most recent stock download (Netherlands) and downloaded that. I tried to install that and it hung for about an hour. I disconnected and it now says "An error has occurred whilst updating the device software" and does not boot.
So i cannot boot in to Android, have no custom recovery and KIES/SmartSwap do not work.
Any ideas????!?!?
Click to expand...
Click to collapse
Flash latest nougat Stock rom from sammobile using The latest ODIN software. You shouldnt disable OEM unlock next time you root/install custom recovery to your phone or else this will happen again, and you'll have to flash stock firmware again.

Oem locked, frp block, and drk help

Hey guys. I'm in a hell of a bind and could use some help.
My Galaxy Note 5 (N920T, rooted) was running fine on this ROM: https://forum.xda-developers.com/tm...m-qc6-lite-rom-bloated-knoxed-odexed-t3598686 ; however, I had disabled OEM unlock at one point to try and fix a random app I was playing with. The battery died not long after, causing the phone to reboot. On power, it failed to boot due to custom binary block from FRP, so I decided to try and run the usual troubleshooting of flashing a stock ROM via Odin. Stock images will flash (tried 5.1.1, 6.1, and 7); however, when they try to install I get the error for no DRK. Sometimes I'll also get a dm-verity error as well... So I then tried to flash TWRP or any recovery via Odin to let me fix this issue; however, any custom recoveries I try to flash are being blocked by FRP.
So, I'm in a loop. I can't use my initial ROM because FRP, however I also can't install a stock ROM because of missing DRK, AND I can't fix the DRK or verity errors because I can't install a recovery capable of doing so because of FRP.
IMEI is intact when I look into Download mode, but I can't seem to get anything to work. I've tried the FRP Tool and crack, but that gives me FRP blocks as well (USERDATA).
Am I boned?
B U M P
Anyone?
same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*
You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.
Metabolic12 said:
You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.
Click to expand...
Click to collapse
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.
x24veggie said:
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.
Click to expand...
Click to collapse
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.
craig198 said:
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.
Click to expand...
Click to collapse
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP
craig198 said:
same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*
Click to expand...
Click to collapse
No. It started because you didn't back up your phone properly with twrp before going flash crazy
---------- Post added at 08:52 AM ---------- Previous post was at 08:47 AM ----------
x24veggie said:
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP
Click to expand...
Click to collapse
https://www.google.ca/amp/s/forum.x...to-solve-dm-verity-verification-t3293306/amp/ have you tried this? If we can figure this out please don't ever play with oem or have a stock recovery ? that's your security blanket

GalaxyS8+ SM-G955F: BRICK (Only official released binaries are allowed to be flashed)

My device has been bricked after attempting to root the device using Odin. (Samsung Galaxy S8+)
The device is stuck in a bootloop with the following accompanying error message in red on the boot screen:
"Only official released binaries are allowed to be flashed"
Here is what happened:
I flashed TWRP using Prince Comsy Odin. (The only Odin that actually works on the s8+)
I then booted into the TWRP recovery.
I followed a set of instructions, clearing the Cash and wiping
I restarted once then booted back into TWRP using Vol-Up + Power + Bixby
I was preparing to install Magisk & "no-verity-opt-encrypt-5.1" according to instructions to complete the root.
After installing "no-verity-opt-encrypt-5.1" with TWRP, the system rebooted and i was stuck in a boot loop.
I then got the error message in the bootloop "Only official released binaries are allowed to be flashed"
Since then i have not been able to successfully re-flash TWRP.
I now cant enter TWRP recovery boot using Vol-Up + Power + Bixby anymore
The bootloop is about 2 seconds long and too short to enter TWRP recovery
I can enter download mode and thats all
I have gotten the EXACT official stock ROM for the galaxy s8+ in South Africa with the carrier, Vodacom. (XFV-G955FXXU4CRL4-20181228165540)
If i flash with any official Odin version, it either fails or doesnt do anything for hours...
If i flash any Official stock Rom using Prince Comsy Odin then i do get the whole process of flashing with stock firmware being successful with the result saying "PASS".
The phone then reboots and i am still stuck in the same loop saying "Only official released binaries are allowed to be flashed"
This is after countless times and hours and hours of reflashing successfully with Official stock rom
I still cant get back into TWRP to do any partitioning or formatting or anything
I really don't mind if i lose all of my data and format the phone but PLEASE can you help me get my phone to work again..."?
Do i need to wait 7 days for the official flash to work?
Is there a way to completely wipe my phone without requiring going into Recovery mode with TWRP? Since i cant get into that state anymore either because of the Error Knox block or because of the Loop being too fast.
Please, please, PLEASE....please help me get my phone to work again...
Sincerely,
I know that Odin 3.13.1 works on the s8+ G955F as I flashed the latest BTU stock yesterday so try that version. I had a similar problem with the G950F and after flashing the files I booted into recovery mode and did a data and cache wipe and the phone rebooted. Flashing a stock rom should have wiped TWRP from the phone.
Reflash your rom or a later one, don't forget to take the tick out of the auto reboot box in Odin, boot to recovery and wipe everything and hopefully you will be good to go. Rebooting on mine took around 35 mins or so when going back to stock.
GalaxyS8+ SM-G955F: BRICK (Only official released binaries are allowed to be flashed
I have the same problem with the model G955F binaries 4 I can not always rooted
le_pentium said:
I have the same problem with the model G955F binaries 4 I can not always rooted
Click to expand...
Click to collapse
same for me !someone asked me to delete the RMM to resolve the problem
le_pentium said:
I have the same problem with the model G955F binaries 4 I can not always rooted
Click to expand...
Click to collapse
My problem is fix

Categories

Resources