Related
After around 5-6 hours this morning/afternoon, I've officially given up on fixing this on my own, and I've all but accepted my device to be a $600 paperweight.
I decided to make one last attempt at saving it by posting for help.
Problem: My phone has a feature called "FRP" (Factory Restore Protection), which is tied to one's Google account. Basically, if you have a Google Account on the phone, it locks the phone to any custom binary/custom OS/whatever.
Once I realized this, in order to root my phone, I went in and removed my Google accounts. Sure enough, this disabled the FRP Lock, and I was able to root my device.
After rooting my device, I re-added my Google accounts and went about my business for the next couple of weeks or so.
Just this morning, my phone was having issues charging, so I decided it'd be a good idea to give my phone a reboot. Big problem. It turns out I simply haven't ever turned off my phone since I rooted it. On top of that, I didn't think the FRP Lock would apply to booting the phone, I thought it only affected flashing new firmware. I was wrong.
After my phone turned off, red text appears at the top of the screen: "Custom binary blocked by FRP Lock".
This is the problem. It simply cannot boot. Because it cannot boot, I cannot remove the Google accounts to disable the lock and resolve the problem. Because the lock can't be disabled, I can't flash the phone's original firmware, because FRP Lock will stop anything and everything I try to do.
---
Goodbye 1k+ photos on phone... And, well, goodbye *phone*.
Unless someone has any helpful thoughts! And that's why I'm here.
tl;dr: Soft bricked phone due to FRP Lock. Not able to restore original firmware, factory restore, or boot into phone's operating system.
Important: The phone turns on, and I have access to the recovery menu as well as "Download Mode"
---
What I have tried:
Factory restoring through the recovery menu, doesn't have any effect
Flashing stock firmware through Odin (Nand write failure)
Flashing a custom recovery environment (TWRP) through Odin (FRP Lock blocked this flash)
ADB and Fastboot cannot recognize the device
Tried to use Kies 3 and Smart Switch to "re-initialize" my OS or something. Both failed, saying that my phone wasn't compatible, and that my serial number was invalid (it was, in fact, correct)
---
And I probably did more things that I simply don't remember. The point here is that I've done everything, and literally everything has failed for one reason or another.
I feel like it is a possibility that if I attempted another stock ROM, then I might be able to avoid the Nand Write Failure. But again, I don't know, and I've almost accepted that I need to start looking for cheap alternative phones.
Thanks in advance, I really hope that this can be fixed one way or another. I'd be sad to see my photos disappear, but if it was the only way for my phone to work again, I could live with it.
have you tried delete the operating system and then flashing a stock rom using odin
by deleting the OS you have a blank phone with google deleted, thus disabling FRP lock.
Cosmic Blue said:
have you tried delete the operating system and then flashing a stock rom using odin
by deleting the OS you have a blank phone with google deleted, thus disabling FRP lock.
Click to expand...
Click to collapse
I thought about doing that, but I have no way of wiping the phone. What do you suggest?
you can wipe the phone through recovery. it is under the advance section. you will need to delete each section manually.
1. Go to download mode
2.Untick auto reboot,
3.Flash twrp
4.do not reboot to system, reboot to recovery.
5. Install super su and reboot system
Done.
Cosmic Blue said:
you can wipe the phone through recovery. it is under the advance section. you will need to delete each section manually.
Click to expand...
Click to collapse
I am not running a custom recovery OS, there is no Advanced section. :s
Yarraque said:
1. Go to download mode
2.Untick auto reboot,
3.Flash twrp
4.do not reboot to system, reboot to recovery.
5. Install super su and reboot system
Done.
Click to expand...
Click to collapse
When I try to flash TWRP (or anything for that matter), FRP Lock blocks the flash.
Purlek said:
When I try to flash TWRP (or anything for that matter), FRP Lock blocks the flash.
Click to expand...
Click to collapse
Go to the developer settings and unlock "oem unlock" thing. Try again.
Yarraque said:
Go to the developer settings and unlock "oem unlock" thing. Try again.
Click to expand...
Click to collapse
I was unable to boot into the phone.
However, I've more or less resolved the issue.
The issue was that when I was first trying to flash stock firmware, I was using an old version. I've read since then that that doesn't work. So I spent 15 hours+ downloading the latest firmware of 6.0.1, and sure enough, it flashed successfully.
Purlek said:
I was unable to boot into the phone.
However, I've more or less resolved the issue.
The issue was that when I was first trying to flash stock firmware, I was using an old version. I've read since then that that doesn't work. So I spent 15 hours+ downloading the latest firmware of 6.0.1, and sure enough, it flashed successfully.
Click to expand...
Click to collapse
Oh nice to hear ^^
Samsung FRP
Cosmic Blue said:
have you tried delete the operating system and then flashing a stock rom using odin
by deleting the OS you have a blank phone with google deleted, thus disabling FRP lock.
Click to expand...
Click to collapse
Would this work with the Samsung Account Factory Reset Protection?
.
Hi - I really am in need of help. My phone which is a T-Mobile Samsung Galaxy Note 5 (was) running latest 6.x firmware,
but custom and rooted via DarkStalker's awesome ROM. All was running fine for months. I did do one thing before my phone died,
I turned OFF developer option and forgot to turn it back ON before I i rebooted. Now the phone is bricked ( I pray it is SOFT not
hard bricked ). When I turn ON the phone it just says "FRP Lock is ON" and then shuts off.
I can enter download mode but NOT recovery. This phone is my work phone and has so much important stuff on it, I just have to fix this.
Plus my wife will shot me for paying $700 and breaking it.
Anyway ... I assume I must go back to stock some how. I can boot to download mode and connect to Odin. But I tried to flash:
1) SM-N920T_1_20160702132553_r0dr7864oe.zip
Also I tried this file ( again via Odin )
2) Noble_Kernel_Auto-Root_N920T_v0.1_Rebuid3.tar.md5
But BOTH files resulted in a FAIL on the Odin screen. ( SEE PIC BELLOW )
Now when I boot it boots to a screen that says this:
Odin Mode
Download Speed: Fast
Product name: SM-N920T
Current Binary: Custom
System Status: Custom
FRP LOCK: ON
Secure Download: Enabled
Knox Warrenty Void: 1
AP Swrev: B:2 K:0 S:0
=========
Custom Binary (Recovery) BLOCKED by FAP Lock
.
Click to expand...
Click to collapse
Sooooo basically I can NOT boot to the OS because the FRP lock is ON and I guess should be OFF, but when I try to Odin Flash I get a FAIL at the end of the flash. ( again see picture bellow )
PLEASE HELP I will try anything. .. My job and my wife are going to kill me soon.....
Cheers to all
Thanks
.
Thibor69 said:
.
Hi - I really am in need of help. My phone which is a T-Mobile Samsung Galaxy Note 5 (was) running latest 6.x firmware,
but custom and rooted via DarkStalker's awesome ROM. All was running fine for months. I did do one thing before my phone died,
I turned OFF developer option and forgot to turn it back ON before I i rebooted. Now the phone is bricked ( I pray it is SOFT not
hard bricked ). When I turn ON the phone it just says "FRP Lock is ON" and then shuts off.
I can enter download mode but NOT recovery. This phone is my work phone and has so much important stuff on it, I just have to fix this.
Plus my wife will shot me for paying $700 and breaking it.
Anyway ... I assume I must go back to stock some how. I can boot to download mode and connect to Odin. But I tried to flash:
1) SM-N920T_1_20160702132553_r0dr7864oe.zip
Also I tried this file ( again via Odin )
2) Noble_Kernel_Auto-Root_N920T_v0.1_Rebuid3.tar.md5
But BOTH files resulted in a FAIL on the Odin screen. ( SEE PIC BELLOW )
Now when I boot it boots to a screen that says this:
Sooooo basically I can NOT boot to the OS because the FRP lock is ON and I guess should be OFF, but when I try to Odin Flash I get a FAIL at the end of the flash. ( again see picture bellow )
PLEASE HELP I will try anything. .. My job and my wife are going to kill me soon.....
Cheers to all
Thanks
.
Click to expand...
Click to collapse
If you are in the latest firmware (PH2) you have to flash the same firmware (PH2)
.
Thank you sir. But ... im not sure how to tell if I am PH2 or not. Either way, could you point me to a download link for the firmware and I will try it .. please
Cheers
josezr said:
If you are in the latest firmware (PH2) you have to flash the same firmware (PH2)
Click to expand...
Click to collapse
Thibor69 said:
.
Thank you sir. But ... im not sure how to tell if I am PH2 or not. Either way, could you point me to a download link for the firmware and I will try it .. please
Cheers
Click to expand...
Click to collapse
I don't know if I can put links here, but here's
https://mega.nz/#!IJ5VlSRC!HPWdi1sjAhsDm1PoCsp_UK2jkSigsjUXsUxo2egcytE
josezr said:
I don't know if I can put links here, but here's
https://mega.nz/#!IJ5VlSRC!HPWdi1sjAhsDm1PoCsp_UK2jkSigsjUXsUxo2egcytE
Click to expand...
Click to collapse
Thank you so much my friend. I will try it and report back.
Cheers
Unfortunately I did the exact same thing as you one time. And unfortunately Odin wouldn't allow me to flash anything. But there was this tool we use to use all of the time for the s4 and it's called Samsung Kies. As in "keys". Basically as long as you can get in download mode it doesn't matter how you brick it.
You just soft bricked it but the bad thing is we can't flash unadulterated version of firmware with Odin. So if frp lock is on Odin is a no go. And when I say unadulterated I mean one that's not directly from Samsung not touched or changed in anyway.... which are hard to come by in many cases in my experience. When the recovery is changed it won't pass an Odin check usually if frp lock is on. Matter of a fact I don't think you can flash anything with fap lock on with Odin. Due to the fact that frp lock is basically saying bootloader locked.
When you turn off oem mode you unlock the checks put in place by the firmware and hardware during boot. Odin uses these checks also so when you try and flash it'll be a no go. Good news for you is this already happened to me and I figured why couldn't I just restore with heimdall. Well that's a no go to. So final solution was to try out kies that I had remembered using heavily with the s4.
1. Download Samsung Kies3. Link: http://www.samsung.com/pk/support/usefulsoftware/KIES/#none
2: Install and open kies.
3. Go to the the tools tab and select firmware upgrade and initialization.
4. It will ask for your model name. Type SM-N900T.
5. Now it will ask for the Serial Number of your device. It is located on the back of your phone toward the bottom. Type that in and hit enter.
6. Now a message pops up and says the device can be restored etc...... Hit OK.
7. Now a message says Now initializing latest version. Hit OK.
8. Now it will Prepare software for initialization.
9. A screen will come up that says "Please follow the steps below to proceed with emergency recovery.
A. Make sure that the device is turned off.
B. Switch the device to recovery mode and reconnect the cable.
- To switch to recovery mode, turn on the device by pressing the Power button while holding down the Volume control "▼" Button and the Home button, and then press Continue (the Volume control "▲") button.
10. When it detects you are in download mode it will take care of the rest.
Try not to make the same mistake again.
I just rebooted with the developer options turned off on Friday. I was on ph1 firmware. Saw joeyv (spelling?) Deodexed stock rom with an option for an Odin installation. Did the installation through Odin and was back to stock. Odin flashed the kernel and tarp combo and was back up and running with root. No information was lost. For anyone else having this problem.
Sent from my SM-G935T using Tapatalk
Thank you JohnMonsour for taking the time to write all that. I will save it for future use if needed. BUT ... thanks to Josezr I got it fixed.
I was able to boot into download mode like I stated, but I just needed the correct firm to flash. They all failed until I tried
N920TUVS4DPH2_N920TTMB4DPH2_TMB.zip ( Thank you Josezr ).
I just flashed that file and Odin completed and phone rebooted to OS. So ALL IS GOOD. My only question now is ... inside the developer
options section ( in settings ) I have turned Developer options back ON but ... all the options that can be set ON or OFF are in the OFF
position and I am not sure which should be turned on. Can anyone please give me a quick run down on how they should be set .. like this:
stay awake on
next ones set to,
on
off
off
off
on
off
ect............
=======================
Debugging
=======================
on
on
off
ect........
=======================
Networking
=======================
on
off
off
ect........
It would sure help me. Thanks again to all 3 of you guys for helping.
Cheers
This is crazy I just ran into my phone becoming locked yesterday. T mobile sent me a update and my phone of course was set to auto update and my phone would do nothing it was a FRP LOCK. All I did was download odin and used this site to walk me through it all files are provided thanks to [ROM] [STOCK] N920TUVU3DPG1 | 6.0.1 | Deodexed | KNOX Free | 7.22.2016 by jovy23. At the bottum of the page is the download and also instruction to use odin. This was a life saver. LINK/ http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270. Copy and past everything you need to do to get out of a FRP Lock situation is in this tutorial. Thanks again Jovy23.
JohnMonsour said:
Unfortunately I did the exact same thing as you one time. And unfortunately Odin wouldn't allow me to flash anything. But there was this tool we use to use all of the time for the s4 and it's called Samsung Kies. As in "keys". Basically as long as you can get in download mode it doesn't matter how you brick it.
You just soft bricked it but the bad thing is we can't flash unadulterated version of firmware with Odin. So if frp lock is on Odin is a no go. And when I say unadulterated I mean one that's not directly from Samsung not touched or changed in anyway.... which are hard to come by in many cases in my experience. When the recovery is changed it won't pass an Odin check usually if frp lock is on. Matter of a fact I don't think you can flash anything with fap lock on with Odin. Due to the fact that frp lock is basically saying bootloader locked.
When you turn off oem mode you unlock the checks put in place by the firmware and hardware during boot. Odin uses these checks also so when you try and flash it'll be a no go. Good news for you is this already happened to me and I figured why couldn't I just restore with heimdall. Well that's a no go to. So final solution was to try out kies that I had remembered using heavily with the s4.
1. Download Samsung Kies3. Link: http://www.samsung.com/pk/support/usefulsoftware/KIES/#none
2: Install and open kies.
3. Go to the the tools tab and select firmware upgrade and initialization.
4. It will ask for your model name. Type SM-N900T.
5. Now it will ask for the Serial Number of your device. It is located on the back of your phone toward the bottom. Type that in and hit enter.
6. Now a message pops up and says the device can be restored etc...... Hit OK.
7. Now a message says Now initializing latest version. Hit OK.
8. Now it will Prepare software for initialization.
9. A screen will come up that says "Please follow the steps below to proceed with emergency recovery.
A. Make sure that the device is turned off.
B. Switch the device to recovery mode and reconnect the cable.
- To switch to recovery mode, turn on the device by pressing the Power button while holding down the Volume control "▼" Button and the Home button, and then press Continue (the Volume control "▲") button.
10. When it detects you are in download mode it will take care of the rest.
Try not to make the same mistake again.
Click to expand...
Click to collapse
its so much wrong with this write up its not funny...for one his model number is sm-n920t second if he is in frp lock then he cant turn his phone off, i tried this method it doesnt work period
you can't turn your phone off?
Yeah actually you can hard reset it and then enter download mode....
Hold volume down the home button and power for like 10 seconds then when the screen turns black you quickly hold volume down, home, and power......
You might not be able to turn it off but you can still enter recovery and download mode.
You might not be able to get into recovery depending on how screwed up your phone is.
And kies3 version was the only one that would work with the above method, now kies has checks in place that checks your knox status and if you've tripped knox it won't work. I can rewrite the guide and link the proper kies if it's really necessary. But this is from 2016 so I am sure that I don't need a proper rewrite.
And at this point I'm pretty sure it might not even matter what version of kies is used it probably does all checks server-side. So this method is obsolete for an almost obsolete phone.
Sorry I didn't help you.
Hi all my g955f has oem lock. Can't enable it. Can't boot into system. Tried to flash twrp but says oem blocked custom binary. It was turned on but friend (who is quite cluey) turned it on by accident.
I have combination file for g955f
Can see ish debbing turned on. No oem unlock in combination file. So really stuck any help please
Just flash stock, then fix it. Your friend (Or you, if you're lying) probably has no idea what they're doing.
Lol I did delete efs folder a whole ago my friend did get it back. I did get my imei back. I showed him then he turned off OEM lock. The egg! So I have flashed stock. Can't flash dm verity file because won't flash custom binary because of lock
Harrrd said:
Hi all my g955f has oem lock. Can't enable it. Can't boot into system. Tried to flash twrp but says oem blocked custom binary. It was turned on but friend (who is quite cluey) turned it on by accident.
I have combination file for g955f
Can see ish debbing turned on. No oem unlock in combination file. So really stuck any help please
Click to expand...
Click to collapse
I had exact same problem...took it to Samsung...cost me £290 for a new board.
Had to pay coz warranty void coz i rooted it.
Matt
this is how I fix the problem.
if you have FRP Lock as well then remove FRP by combination file.
after remove FR, P the phone will still ask for WIFI during reboot
downgrade the phone firmware to G955FXXU1AQCA_OXM1AQCA.zip if possible
flash the lower version firmware
if you got boot error then do hard reset
after finish reboot
go to settings to reset the phone again (not hard reset)
you will remove the Knox problem.
I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.
Thanks a lot for all your help!
The problem was I entered the download mode by the adb command "adb reboot-bootloader" and this mode seems to be different to the one which can be accessed by pressing the keys.
Now everything worked fine
I have exactly the same problem here:
SM-A205G with OEM Unlock enabled
There is no unlock bootloader in the bootloader no option anymore
at least in the bootloder of this edition
And I suppose that if it is the bootloader that flashes everything, it is COMPLETELLY LOCKED, could be jailbroken by some new method, but until them... no option :sad:
V0latyle said:
You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.
Click to expand...
Click to collapse
It seems that this <confirm> option in the bootloader is being removed by samsung, so... even if unlock oem is enabled... it will not work...
I can only reach the bootloader by going to recovery mode them selecting reboot bootloader, or by adb reboot bootloader, but it boots directly in download mode without the option to long-press volume up key
A flasher that doesn't flashes doesn't makes sense. Maybe samsung have hidden something new in there?...
Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com
wavedevice said:
Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, you don't unlock the bootloader VIA the bootloader in Samsung phones.
so you know what happened? I accidentaly reset my phone! I have gone into download mode and there was additional choices: to unlock bootloader holt volup, so I did, then again to confirm unlocking press volup. I did so and then there was for a brief moment android logo and "erasing" and then after about 2 minutes of just Samsung logo phone restarted and asked me to perform setup as it was new! WTH? There was nothing mentioned about deletion
DaHansi said:
I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
Click to expand...
Click to collapse
I had the same problem on my samsung tab a10.1. That's why I had to flash the stock firmware 3 times. Every time I flashed twrp with odin, I got the error (custom binary blocked by oem lock).
I write what they should do in order.
1. Turn on the phone.
2. Open Developer mode
3. USB debugging mode - on
4. oem unlocking - on
5. then turn off the phone and disconnect from usb
6. Connect the phone to the PC with USB by holding down the volume up and volume down buttons at the same time. WITHOUT PRESSING THE POWER BUTTON
7. Press and hold the volume up button according to the instructions in the pop-up window.
oem unlocked
Sorry that, I had another problem. May I know how to unlock the OEM if my S10e phone can't turn on.
My device always on "samsung" display page, can't open to index. Do you know this issue? Expecting your reply.
Hi! I have the same issue on my Xiaomi Mi 11 Pro (It was Chinese) but it came unlocked with xiaomi.eu rom.
After i installed a global rom, and google wallet nfc pay did not work, so i thought okay i will lock it then so maybe wallet would accept it, (with the eu rom it worked before) so i put the device in fastboot and used fastboot oem lock on cmd...
And from then it stucks on miui recovery 5.0 screen, and says, this miui version can't be installed on this device...
I might not enabled oem unlocking before i shut if off, but i added it to my mi account so i dont know if after a week i can maybe unlock it. But i think the other possible solution would be to sideload the original chinese stock rom, which is for M2102K1AC, Mi 11 pro, codename mars, but i couldn't find it anywhere... If someone can upload a link to it, that would be a huge help! Or any idea! thx!
geraldmany said:
HI! i got a mi 11 pro 1 year ago, and it was offically chinese, but it came unlocked with Xiaomi.eu firmware, but i could't update it via the updater app, so i searched and found the global star version and just flashed it, everything worked, only now google pay nfc didnt work, it said that its probably because of the unlocked bootloader, so i got to fastboot and in cmd i sent fastboot oem lock, and since then my phone is stuck in miui recovery 5.0 screen and says that i cannot run this firmware on the device, i tried to unlock it but failed, maybe after a week, but i think that i didnt turn on oem unlocking on the phone itself before this... So im just hoping that after a week unlocking could be done... Or my other idea is, that i could install the original chinese rom with sideload, because i managed to install another global version on it since, but the result is still the same, the only problem is that i cannot find literally anywhere a mars codenamed firmware...
Click to expand...
Click to collapse
Anyone who might have the same situation, i found a simple, but effective solution, not sure if it works on every xiaomi device, but i will write down the steps here:
You need to use XiaomiADB, here is the download link and the description for how to use it -> https://xiaomiui.net/how-to-use-xiaomiadb-8044/ (if the page is not available, then feel free to msg me!)
For xiaomi adb, you need to go to 3rd option on the miui recovery screen, NOT THE FASTBOOT
So basically i went through the steps to “xiaomiadb sideload_miui <filename>”
And I tried to install a rom, BUT IT DIDNT ACCEPT IT!
The message was:
ERROR: This rom cannot be installed, server code -> 2001, server message -> Can't install unofficial rom
after trying 4 times all the same and: Installation of this rom via stock recovery is not allowed by Xiaomi
Says Installation failed, and then i just decided to download another rom so i PLUGGED OUT THE PHONE right after this, and went to another room to connect to wired network, to download and try a different rom... when i came back, to all my surprise, the phone was turned on, so i went to the setting dev ops and enabled bootloader unlocking, linked it to my account enabled adb and everything that is needed to flash another rom later, so then i rebooted and again, miui recovery 5.0 screen, but now i enabled unlocking, so i put the phone in fastboot, and tried MI UNLOCKER TOOL again, now it says: Please unlock 168 hours later. And do not add your account in MIUI again, otherwise you will wait from scratch.
So that means, after 7 days i wll be able to unlock it, until then, i can turn it on with the above method, in short try to sideload (copy and install) a rom to it, and then after it failed, plug it out and just wait like 10-20 maybe 30 seconds and bam your device is normally booted... I hope it helps to some of you, (i have been searching for the solution for almost a week, my other option was to pay someone who can MAYBE do it or send the phone back to china and pay the repairs, so im really happy with this method! If it helps to you, please reply so i and the others will know that it worked! Have a nice day!
Goodnight all,
I unlocked the OEM bootloader and Rooted my Samsung Galaxy Z Flip 4 using Magisk. It is a European model.
Now each time I start it I get warning messages that the security has changed as a result.
I reset my phone completely and I still have these warning messages on startup.
Is it possible to remove these warning messages because I will most certainly resell the phone???Is there a solution to lock the OEM bootloader again or is it irreversible???
Thank you in advance for your help and good evening to all.
This is by design. An unlocked bootloader should display the ORANGE state on boot to notify the user. This is normal, and no action is needed.
It is not possible to remove these warning messages as this is a result of the bootloader functioning as intended.
You can re-lock your bootloader if you want but make sure you have performed a clean flash with the factory firmware first. You would then follow the same process you used to unlock the bootloader (device off, hold both Volume buttons, plug in USB cable).
It's just a minor inconvenience though and does not affect device operation.
Good evening,
@V0latyle
if I understood your explanation , I download the latest firmware which is installed on my phone with the help of SamFirm or other software.
Then I use Odin in administrator mode and I select the file in the BL box, the file in the AP box, the file in the CP box and especially in the CSC box I put the CSC file (and not Home_CSC) in order to a hard reset of my Samsung Galaxy Z Flip 4 phone. Once the flash is done, the phone reboots to factory state, I click the build number 7 times then I go to developer options and there I could finally lock my OEM development loader again??? Once I've done all of this
,will the bootloader security warning message go away???
Please tell me if I understood correctly please and above all thank you again for your help.
nicoco19 said:
Good evening,
@V0latyle
if I understood your explanation , I download the latest firmware which is installed on my phone with the help of SamFirm or other software.
Then I use Odin in administrator mode and I select the file in the BL box, the file in the AP box, the file in the CP box and especially in the CSC box I put the CSC file (and not Home_CSC) in order to a hard reset of my Samsung Galaxy Z Flip 4 phone. Once the flash is done, the phone reboots to factory state, I click the build number 7 times then I go to developer options and there I could finally lock my OEM development loader again??? Once I've done all of this
,will the bootloader security warning message go away???
Please tell me if I understood correctly please and above all thank you again for your help.
Click to expand...
Click to collapse
You don't have to do anything with Developer Options or the OEM Unlock toggle. OEM Unlocking only functions as a "safety" to permit you to unlock your bootloader.
If it is already unlocked, simply follow the instructions you used to unlock it after you enabled OEM Unlocking the first time - with the device powered off, use the key combo to boot into Download Mode, then hold Volume Up until you see the device lock warning. When you relock the bootloader, it will wipe data. Once done, no further steps are needed.
If you want to tinker with your device and enjoy the benefits of root, why not leave it unlocked? Sure the bootloader warnning is slightly annoying but again that's by design.
@V0latyle
ah ok, I understand better, I'm doing the reverse step of what I did the very first time I unlocked the OEM bootloader.
I put my phone in download mode by connecting it to my computer and then I hold the volume up key for a long time to lock the OEM bootloader. And if I understood correctly, once this is done, my phone will be factory reset and no more warning message on startup. That's right ???
In fact, I'm asking you all this because I want to sell my phone to switch to the S23 Ultra.
thank you for your help and your feedback
nicoco19 said:
@V0latyle
ah ok, I understand better, I'm doing the reverse step of what I did the very first time I unlocked the OEM bootloader.
I put my phone in download mode by connecting it to my computer and then I hold the volume up key for a long time to lock the OEM bootloader. And if I understood correctly, once this is done, my phone will be factory reset and no more warning message on startup. That's right ???
Click to expand...
Click to collapse
Yes, if the bootloader is locked and the firmware is original OEM, there should be no warning.
@V0latyle I'm testing all this to the letter tomorrow evening and in the process I'll come back for other people that it could help.
thank you for your help and keep you posted
Hello,
I did what you said and problem solved, the warning messages at startup disappeared.
Thank you again for your help @V0latyle
But u know that KNOX is triggered and u loose some of functions anyway even if you relock bootloader ?