Hi there,
I have a Samsung Galaxy Tab A6 (SMT-580) which I bought today. I followed this tutorial to install twrp, ultimately to root the device:
dottech .org/200476/how-to-install-twrp-recovery-on-samsung-galaxy-tab-a-sm-t580/
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
its.the.christianator said:
Hi there,
I have a Samsung Galaxy Tab A6 (SMT-580) which I bought today. I followed this tutorial to install twrp, ultimately to root the device:
dottech .org/200476/how-to-install-twrp-recovery-on-samsung-galaxy-tab-a-sm-t580/
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
I recently did the same thing. I used the fix that you can find online by searching for RootJunky and it worked great. Just make sure you have the latest version of Odin - 3.10.6, otherwise it will not work. I can't post URLs yet as I have not posted enough times.
Good luck
Yes, the OEM reset is the problem. Thank you, Samsung, for allowing us, the people who buy your stuff, the ability to lock the device by looking at it crosseyed.
This is the guide you want to use for TWRP and root: Newbie-friendly: TWRP and Root for Tab A tablets (2016, 10.1")
I would not try that RootJunky business just yet until you see someone else get it to work on a 580. It looks from watching the video you need to able to boot, and you can't. And having someone say it "should work" is a surefire way to a brick.
You should be able to get your tab into the stock recovery mode. If you can, once there do a "factory reset" and reboot. It will hopefully reboot and take you to the wifi connections screen where you will have to sign in with the Google account on the tab and then let you finish the factory reset. If you get that far, then try the link.
I had the FRP after a failed installation of XPosed, and like you, nothing worked. The factory reset was just a shot in the dark before I took the tablet out and shot it.
It's just the same to me. Where can I see the RootJunky solution?
Forgive my English.
Thank you.
I've successfully bypass the Google FRP lock on the SM-T580 instructions are in this forum
I am in the exact same boat as you. I rooted my SM-T580 last night, then logged into my google account to install Root Check for Superuser. Everything seemed fine, I thought I was in the clear. Then when I tried to power back on this morning, I get the FRP lockout message.
I'm fairly certain it's only the TWRP installation tripping the FRP. Booting into Odin does not fail immediately, but only when you try to flash a new TWRP file. This tells me that FRP is checking whether the incoming recovery file is the official version or not.
In theory, if you try to flash the official recovery file to the tablet, it should pass the FRP check. FRP might let the tablet boot normally after that, since everything would check out as official.
I would try this myself, but I can't find any links to the official recovery firmware. I have hit a wall and am not sure where to go from here.
---------- Post added at 12:57 AM ---------- Previous post was at 12:40 AM ----------
kleptobismol said:
I've successfully bypass the Google FRP lock on the SM-T580 instructions are in this forum
Click to expand...
Click to collapse
You're addressing a slightly different flavor of FRP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(pretend this says 'Samsung Galaxy Tab A 10.1')
FRP stops me on this screen with small red text in the top left corner that says: Custom binary blocked by FRP Lock.
It also stops me from booting into TWRP to do a total wipe.
Assume your tablet is SM-T580, try to flash back official firmware which is on sammobile.com
This is the official bootloader (BL ), you can try it first
http://www.mediafire.com/file/nootyin3bghsof3/BL_T580.rar
Otherwise, you have to flash the BL and AP. Which one is your build number, APG1 or APL4 ? You can look up in Recovery Mode.
get me out of thy hell????!
I already installed CF-Auto-Root almost year ago, downloaded from autoroot.chainfire.eu, to get root access on my SM-T585 tablet. Last night, i suddenly suffered to get it connected to the OTG flash drive and then I tried to figure out the problem by disabling and enabling USB debugging, OEM, developer mode, and finally let it to restart. Thereafter, the tablet get looped in wired booting screen says "custom binary blocked by frp lock". I then tried to flash with the official firmware using odin, but I get unable to see the tablet in the odin's ID.COM box. please help me to get out of thy hell????!
Two Different FRP Locks!
kleptobismol said:
I've successfully bypass the Google FRP lock on the SM-T580 instructions are in this forum
Click to expand...
Click to collapse
This is not the same FRP lock that Kleptobismo was mentioning. The link he provided goes to a page that is about the frp lock that loosely blocks access to the phones settings unless you go through a maze starting with the Talkback mode and find your way to Google Chrome sometimes having to unlock the Instal apps from other sources switch. Then you can actually factory reset the device and take control of it. Dealing with that FRP lock is easy compared to this one. This one won't let you into the device past the logo screen. You can get to download mode but It won't let you use Odin3 to flash any types of Official Stock Firmware, not the OTA, the AP file, the 3 file or the 4 file. And there's absolutely no Recovery menu.
Does this sound familiar? Getting past the "Custom Binaries Blocked by FRP Lock" was relatively simple by flashing in a file called, "SM-T580 Binary 4 FRP Unlock. with Odin3 which I have in rar. But there's another difficulty that's pretty much just like it. On another SM-T580 I get the same difficulties with Odin3 stalling at initialization and not booting past the logo screen and instead of booting to recovery I get the other screen but this time it doesn't say custom bianaries blocked by frp in red letters. It says, ODIN MODE DOWNLOAD SPEED FAST in red letters. below that is,
PRODUCT NAME: SM-T580
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0500)
RP SWERV: B:4 K:1 S:2
This one I have yet to figure out or get past. Seeking advice.
Casper Young said:
This is not the same FRP lock, The link goes to a page that is about the frp lock that loosely blocks access to the phones settings unless you go through a maze starting with the Talkback mode and find your way to Google Chrome sometimes having to unlock the Instal apps from other sources switch. Then you can actually factory reset the device and take control of it. Dealing with that FRP lock is easy compared to this one. This one won't let you into the device past the logo screen. You can get to download mode but It won't let you use Odin3 to flash any types of Official Stock Firmware, not the OTA, the AP file, the 3 file or the 4 file. And there's absolutely no Recovery menu.
Click to expand...
Click to collapse
There are third party locks used by corps that don't want their devices resold. (Fearing loss of company data.) Sometimes they spoof being FRP but aren't. The FRP lock is a standard Google feature and will only block a "factory reset" by requiring you the enter the Google Account login and password used by the device at the time it was reset. They don't prevent installing a stock ROM via Odin but, unless you use the "combo" method, installing another ROM won't remove the FRP lock. It would appear to me that your tablet has a third party lock and NOT an FRP lock.
allo,
it's been a long time since i've post here,
anyway... always apply the "KISS" (keep it simple stupid) method with android.
so... for the "custom binary blocked by frp lock"
remove back cover of tablet,
start odin,
plug your tablet in download mode, odin will not see it
unplug battery, odin now see the tablet
plug battery back
flash your rom!
Sherlock Holmes quote "How often have I said that when you have excluded the impossible whatever remains, however improbable, must be the truth."
Strange Peer said:
allo,
it's been a long time since i've post here,
anyway... always apply the "KISS" (keep it simple stupid) method with android.
so... for the "custom binary blocked by frp lock"
remove back cover of tablet,
start odin,
plug your tablet in download mode, odin will not see it
unplug battery, odin now see the tablet
plug battery back
flash your rom!
Sherlock Holmes quote "How often have I said that when you have excluded the impossible whatever remains, however improbable, must be the truth."
Click to expand...
Click to collapse
I will try and write what will happen there, but first I should get someone able to open the back cover of the tablet.
There are two distinctly different types of FRP Locks
The FRP lock is a standard Google feature and will only block a "factory reset" by requiring you the enter the Google Account login and password.[/QUOTE said:
,
I'm talking about a different kind of FRP lock and this surely is not a standard Google Feature. You're thinking I have some access to the device in a way that let's me sign into wifi and then get stopped by a Google Sign in page where I don't have the user id and password from a previous owner. You apparently didn't read what I said where this is not the same FRP lock. There are two situations where a user will be stranded and unable to use the tablet. The general symptoms start with, when they turn the device on, it stops at the Logo screen and fails to boot. (I don't get to the Welcome screen and am not able to use talkback to do some puzzle so I can "Bypass and Remove a Google Account FRP lock"). Odin3 fails to get past initialization and therefore nothing gets flashed to the device. Recovery is inaccessable and you get redirected to a screen that tells you in red letters "Custom Binaries Blocked by FRP Lock." This FRP lock happens whenever the binaries are overloaded due to a bad Root, ROM or invalid file being flashed into the device. The second one has all the same symptoms except that when you try to boot to recovery it doesn't say custom binaries blocked. I've dealt with my Binaries blocked issue and now I'm trying to get another device out of a very similar situation.
Click to expand...
Click to collapse
allo again,
The general symptoms start with, when they turn the device on, it stops at the Logo screen and fails to boot. (I don't get to the Welcome screen and am not able to use talkback to do some puzzle so I can "Bypass and Remove a Google Account FRP lock"). Odin3 fails to get past initialization and therefore nothing gets flashed to the device. Recovery is inaccessable and you get redirected to a screen that tells you in red letters "Custom Binaries Blocked by FRP Lock.
that exactly it... took me 4 month to find how to bypass... the tablet would never boot...
odin would not see the tablet until i've unplug the battery... (custom binaries blocked by frp lock)
for the other google bypass account you just need to follow the step describe in this video (google account frp lock)
https://youtu.be/2MBdg9OIT7M
it's really easy to open the tab, just google or youtube a video to learn how to!
Strange Peer said:
allo again,
for the other google bypass account you just need to follow the step describe in this video (google account frp lock)
https://youtu.be/2MBdg9OIT7M
it's really easy to open the tab, just google or youtube a video to learn how to!
Click to expand...
Click to collapse
Am I on the wrong page? Which one is this one talking of? The FRP that relates to the Google Account Sign In? Or the FRP
relating to the Recovery being Blocked? There are 2 of those I've noticed, possibly a third issue with not being able to access the Recovery Menu. Instead you are redirected to a partial image of the Download Menu, specifically the upper left corner. One will say in red letters, "Custom Binaries Blocked by FRP Lock". And there's another one where it starts off saying Odin Mode and the line below that says Download Speed Fast. Both have the same symptoms: Bootloop at Logo Screen (some flickering or lines), Download Mode is accessable but Odin3 fails to initialize (it actually does). Trying to go to Recovery is redirected, no recovery menu available.
The custom binary block can be eliminated by flashing a binary 3 then a binary 4 file into the device or sometimes only a binary 4 (FRP Unlock) file.
The second one, I'm still working on and seems to be the bootloader is locked or OEM is turned off.
Custom binary blocked by frp lock
I was wondering if you could please give me a walk thriugh on this. I have a Galaxy Tab A6 tablet
kleptobismol said:
I've successfully bypass the Google FRP lock on the SM-T580 instructions are in this forum
Click to expand...
Click to collapse
Casper Young said:
This is not the same FRP lock that Kleptobismo was mentioning. The link he provided goes to a page that is about the frp lock that loosely blocks access to the phones settings unless you go through a maze starting with the Talkback mode and find your way to Google Chrome sometimes having to unlock the Instal apps from other sources switch. Then you can actually factory reset the device and take control of it. Dealing with that FRP lock is easy compared to this one. This one won't let you into the device past the logo screen. You can get to download mode but It won't let you use Odin3 to flash any types of Official Stock Firmware, not the OTA, the AP file, the 3 file or the 4 file. And there's absolutely no Recovery menu.
Does this sound familiar? Getting past the "Custom Binaries Blocked by FRP Lock" was relatively simple by flashing in a file called, "SM-T580 Binary 4 FRP Unlock. with Odin3 which I have in rar. But there's another difficulty that's pretty much just like it. On another SM-T580 I get the same difficulties with Odin3 stalling at initialization and not booting past the logo screen and instead of booting to recovery I get the other screen but this time it doesn't say custom bianaries blocked by frp in red letters. It says, ODIN MODE DOWNLOAD SPEED FAST in red letters. below that is,
PRODUCT NAME: SM-T580
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0500)
RP SWERV: B:4 K:1 S:2
This one I have yet to figure out or get past. Seeking advice.
Click to expand...
Click to collapse
Hi, Please how were you able to fix this problem.
my Samsung S6 edge plus is stuck on a boot loop (showing samsung Galaxy S6 edge + logo). I can boot up device in Download mode but has no recovery. The problem is I can only flush it with the firmware G928AUCS6ERH1 (official Rom) successfully, any other firmware will give me an error. After flashing it is still stuck on a boot loop.
It has a FRP lock too. in download mode I see:
Current Binary: Samsung Official
System Status: Custom
FRP Lock: ON
Secure Download: Enable
Knox Warranty void: 0 (0x0000)
RP SWREV: B:6 K:0 S:1
Don't really know what to do. Please help, I will appreciate any ideas on how to fix this.
kwesi2505 said:
Hi, Please how were you able to fix this problem.
my Samsung S6 edge plus is stuck on a boot loop (showing samsung Galaxy S6 edge + logo). I can boot up device in Download mode but has no recovery. The problem is I can only flush it with the firmware G928AUCS6ERH1 (official Rom) successfully, any other firmware will give me an error. After flashing it is still stuck on a boot loop.
It has a FRP lock too. in download mode I see:
Current Binary: Samsung Official { this indicates your device is using the official stock firmware)
System Status: Custom {Indicates Custom ROM (possibly Rooted and/or TWRP installed)
FRP Lock: ON (This may not mean what you think) It's working
Secure Download: Enable
Knox Warranty void: 0 (0x0000)
RP SWREV: B:6 K:0 S:1
Click to expand...
Click to collapse
I'd like to know if you tried to flash something into it before it gave you difficulties. Assisting with a device not in my hands can sometimes be more difficult. You are able to get to and use Download mode so you're not in Binary Locked status. If you were you would see the words "Custom Binary Blocked by FRP Lock" somewhere in red letters. And Odin would initialize then fail.
Sounds to me that an attempt to Root and install TWRP went bad. A lot of times if you don't install a custom ROM after installing TWRP (your custom Recovery) it will do things like that after it resets or is turned off and later back on again. It will toss out the TWRP leaving you with no recovery. What it's doing is failing to Boot. That's the Bootloader. Are you using a 4file? Too many people have learned to only use the AP file when flashing, you should use them all. The BL, AP, CP and the CSC. The Bl is your bootloader file.
You may want to try the full firmware. This is where I found it.
https://androidfilehost.com/?w=search&s=G928AUCS6ERH1
---------- Post added at 10:23 AM ---------- Previous post was at 10:14 AM ----------
Maxxbet20 said:
I was wondering if you could please give me a walk thriugh on this. I have a Galaxy Tab A6 tablet
Click to expand...
Click to collapse
What exactly would you like a walkthrough on? I come to this page about once a week, if you'd like a quicker response contact me directly here.
https://www.facebook.com/CaspurYoung/
Casper Young said:
What exactly would you like a walkthrough on? I come to this page about once a week, if you'd like a quicker response contact me directly here.
Click to expand...
Click to collapse
i could have used a walkthrough too that would have saved me a few hours...
when my stepdaughter came to me to fix her tablet, i didnt really know about frp...
so when her tab got locked, her not remembering the pin, i figured i just needed to reset the thing to stock.
and so i did, -how little did i know - enabling frp in the process.
the first solution i tried was for her to remember which google account she used to install it but she lost the password.
the linked phone nr was deactivated 2 years ago, rendering the lost password link useless. no luck there.
so now i needed to bypass the frp .. or throw the [email protected]# thing in the bin and buy her another one so she can netflix again.
the horror - telling a 16yo her data went to the dark depths of cyberspace .. and maybe i now ruined the tab all together
reading up on the issue i learned my last resort is to flash the combination rom, and when done, reset to original rom.
(the recovery screen tells me it's a binary u1 version t585xxU1APE3 )
i did manage to find a few combination roms, and various original roms that should do the trick
but just flashing back and forth did not do the trick.
all looks well, but when done .. still the same issue ..
but in the end i managed to fix it by finding the correct (older) stock rom and tricking it a bit.
persistence is the key.
Casper Young said:
I'd like to know if you tried to flash something into it before it gave you difficulties. Assisting with a device not in my hands can sometimes be more difficult. You are able to get to and use Download mode so you're not in Binary Locked status. If you were you would see the words "Custom Binary Blocked by FRP Lock" somewhere in red letters. And Odin would initialize then fail.
Sounds to me that an attempt to Root and install TWRP went bad. A lot of times if you don't install a custom ROM after installing TWRP (your custom Recovery) it will do things like that after it resets or is turned off and later back on again. It will toss out the TWRP leaving you with no recovery. What it's doing is failing to Boot. That's the Bootloader. Are you using a 4file? Too many people have learned to only use the AP file when flashing, you should use them all. The BL, AP, CP and the CSC. The Bl is your bootloader file.
You may want to try the full firmware. This is where I found it.
Click to expand...
Click to collapse
Sir (@Casper Young), thank you for responding. I really appreciate that.
I hope the following will throw more light on my situation:
The phone is my wifes and she does not remember exactly what caused it to boot cycle.
When I was made aware I attempted to fully flash the rom with the following firmware but all failed to flash with exception of G928AUCS6ERH1
G928AUCS4CQA1
G928AUCU3CPHA
G928AUCU1AOGG
I have not been able to access the recovery mode since the issue began.
I also flashed with a combination file I made from the G928AUCS6ERH1 using the SAMFRP even though I was successful with the flash the phone is still boot looping. I have again done a full firmware flashing with the firmware you provided (thank you for providing it) and the phone is still not booting.
Any more suggestions from you and anyone will help.
Once again I appreciate your help. Thanks
Hello all,
I'm in possession of a Huawei P8 Lite of which the owner lost the passphrase. The question is whether the photos on the device can still be recoved. The bootloader of the device is currently locked. Debug mode is not enabled (nor is my computer authorized).
I was hoping that it would be possible to unlock the bootloader (which supposedly does not trigger a factory reset on this model?) - and then install a custom recovery from where I could backup the pictures. In order to unlock the bootloader, I would need IMEI-1 + IMEI-2 and the S/N. I was able to obtain one of the IMEIs by typing *#06# on the emergency call screen. Is there a way to obtain the other codes somehow (perhaps via fastboot)? Once I obtain the necessary information, my assumption is that I would be able to get an unlock code from Huawei after which I can unlock from fastboot. (Or does OEM unlock still need to be enabled from the developer options in Android?)
Edit: seems like the S/N is shown when connecting in fastboot mode and listing "fastboot devices".
Edit2: seems like obtaining the IMEI through the emergency call functionaltiy combined with the S/N is enough: I modified the "Product ID Generator" tool to include the "ALE-L21" model, and now it generates valid Product IDs that can be used on the Huawei website to obtain an unlock code.
Alternatively, I've noticed that there's an "emergency data backup" mode on this model, which I accidentally entered. I was hoping anyone knows more about this mode (note that this is different from the fastboot & rescue mode). I got booted into this mode because somehow the ext4 partition failed to mount during one of the many times I rebooted the phone. This mode also allowed me ADB access - however, this was a rescue OS which did not actually contain the user data. I would like to attempt to boot into this mode again, gain root access via a kernel exploit, and either read out the unlock code from /dev/block/mmcblk0p** or directly copy the media onto an SD card. Does anyone know how to "trigger" booting into this mode? The kernel code for the p8 lite seems to have a flag "CONFIG_FEATURE_HUAWEI_EMERGENCY_DATA" which enables this feature.
Pointers welcome
Note, I'm not desperate to recover the data - but this has become more of a "challenge" I'd like to solve.
Edit: I was able to unlock the bootloader with details obtained from the device. Unlocking the device did not initiate a wipe. Now it comes down to installing a recovery image and pulling the data
ce3c said:
Hello all,
I'm in possession of a Huawei P8 Lite of which the owner lost the passphrase. The question is whether the photos on the device can still be recoved. The bootloader of the device is currently locked. Debug mode is not enabled (nor is my computer authorized).
I was hoping that it would be possible to unlock the bootloader (which supposedly does not trigger a factory reset on this model?) - and then install a custom recovery from where I could backup the pictures. In order to unlock the bootloader, I would need IMEI-1 + IMEI-2 and the S/N. I was able to obtain one of the IMEIs by typing *#06# on the emergency call screen. Is there a way to obtain the other codes somehow (perhaps via fastboot)? Once I obtain the necessary information, my assumption is that I would be able to get an unlock code from Huawei after which I can unlock from fastboot. (Or does OEM unlock still need to be enabled from the developer options in Android?)
Edit: seems like the S/N is shown when connecting in fastboot mode and listing "fastboot devices".
Edit2: seems like obtaining the IMEI through the emergency call functionaltiy combined with the S/N is enough: I modified the "Product ID Generator" tool to include the "ALE-L21" model, and now it generates valid Product IDs that can be used on the Huawei website to obtain an unlock code.
Alternatively, I've noticed that there's an "emergency data backup" mode on this model, which I accidentally entered. I was hoping anyone knows more about this mode (note that this is different from the fastboot & rescue mode). I got booted into this mode because somehow the ext4 partition failed to mount during one of the many times I rebooted the phone. This mode also allowed me ADB access - however, this was a rescue OS which did not actually contain the user data. I would like to attempt to boot into this mode again, gain root access via a kernel exploit, and either read out the unlock code from /dev/block/mmcblk0p** or directly copy the media onto an SD card. Does anyone know how to "trigger" booting into this mode? The kernel code for the p8 lite seems to have a flag "CONFIG_FEATURE_HUAWEI_EMERGENCY_DATA" which enables this feature.
Pointers welcome
Note, I'm not desperate to recover the data - but this has become more of a "challenge" I'd like to solve.
Edit: I was able to unlock the bootloader with details obtained from the device. Unlocking the device did not initiate a wipe. Now it comes down to installing a recovery image and pulling the data
Click to expand...
Click to collapse
Now simply install twrp, connect to PC and you will be able to see all the files in Explorer
faby GT said:
Now simply install twrp, connect to PC and you will be able to see all the files in Explorer
Click to expand...
Click to collapse
With twrp you can delete lockscreen specific files to remove lock
Audriuskins said:
With twrp you can delete lockscreen specific files to remove lock
Click to expand...
Click to collapse
If you think about this, you can see how easy it is to unlock a phone (also for bad purposes...)
Agreed, I'm surprised that Huawei didn't force a device wipe before allowing OEM unlock. Especially because you can obtain all the details you need from the phone to obtain an unlock code on the Huawei website.
I indeed ended up installing TWRP and remove the password.key file to remove the lock
Hello everyone,
This is a SM G975F exynos model
Please note that the bootloader is locked!
I tried to root the phone and it sort of succeeded but now its stuck on bootloop
And moreover Knox is tripped ... if that even matters at all?
I can access download mode, recovery and charges normally with no issues at all.
Problem is i cannot get into the home screen or the setup screen
I have used odin to flash 2 versions of android 10
Since i cannot downgrade because of bootloader being locked....
The odin flashes two versions of 8 bit roms one is G975FXXU8DTH7 and other is G975FXXU8CTG4
Both are android 10
If i do try to downgrade odin gets stuck at boot image flash stage and doesnt work again due to bootloader being locked
can any one help me on what the issue might be?
i can get into download mode , recovery mode, the flash results in a success and i get a pass on odin as well
all it does is get stuck on samsung (non animating) stock splash screen and it restarts again and again
Some relevant information i fetched from download mode screen
KG State : Prenormal
FRP Lock : Off
OEM Lock : On (U1)
please assist me on further on this issue if you can
I can even share the video of the phone behaviour if needed via discord
Thank you
Hi,
Did you fix this problem, I'm in the same situation. Trying to flash all versions of ANdroid 10 and 11 now with Odin, as I don't know which stock formware it was on when it went into bootloop.
Update: When in Recovery Mode, go to the Recovery Logs, then one off those log histories shows all the System build numbers and their installation dates. FRom there you can work out which system was installed when it went into boot loop.
I installed the last system it was working on, then left it in boot loop for 2 hours and it suddenly started to initiate. Leaving it overnight didn't work as I think it turns itself off when the prompts aren't responded to.
Can you please post a photo as I am wondering if we have the same problem as described in this link:
Samsung S10 + bootloop ERASE FAIL: READ ONLY
Samsung S10 + SM-F975F/DS IMEI stating Taiwan (Update: Very contradicting information if the phone is Snapdragon OR Exynos) if it even matters to solve the issue I dont know Owner of the above since 2019 without issues; USB debugging mode...
forum.xda-developers.com