Everything was running fine, I flashed a ROM, rooted etc. Got everything installed, all was working perfectly. I turned the phone off, came back to it a few days later, now I get the above error when turning the device on.
I have read that I now need to flash the full stock firmware via Odin to unbrick it. I have the latest G960FXXSEFUA1 firmware downloaded and ready to go. How can i make it so I dont get in this situation again?
I was using a GSuite account, and had a screen lock PIN. I wonder if that caused it?
Yesterday, I flashed stock ROM, then set OEM Unlock, and then trioed to flash TWRP. I saw 'Only official released binaries are allowed to be flashed', somewhow i got round it, and got everything set up, custom ROM, the lot. Obviously we know how that ended, i saw the 'custom binary blocked by frp lock'
I've now flashed Stock via Odin, done the OEM unlock bit, it got me to wipe the device. I now turn it on and the OEM Unlock bit has gone.
Download Mode says 'OEM Unlock OFF', and 'KG State Prenormal'.
Do I now have to wait the seven days? Even though ive already done the OEM Unlock and reset the phone?
Related
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
You should try Fastboot EDL. search Google. Good luck
scottwitha5 said:
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
Click to expand...
Click to collapse
Give this thread a read.
http://forum.xda-developers.com/showthread.php?t=3405700
Several people have had success reviving their OP3. Also, there is an option to contact OnePlus support and have a remote session with their tech support. They will send you an email with files to download and will walk you thru what you need to do for them to unbrick your device.
Sent from my Nexus 6 using XDA-Developers mobile app
Try reflashing stock firmware with fastboot.
fast69mopar said:
Give this thread a read.
http://forum.xda-developers.com/showthread.php?t=3405700
Several people have had success reviving their OP3. Also, there is an option to contact OnePlus support and have a remote session with their tech support. They will send you an email with files to download and will walk you thru what you need to do for them to unbrick your device.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Windows wont install the drivers on the thread so i cant proceed and the next available date for Oneplus tech is July 24th this is so urgent....any other options?
Nv1dia said:
Try reflashing stock firmware with fastboot.
Click to expand...
Click to collapse
I cant because says flashing isnt allowed
scottwitha5 said:
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
Click to expand...
Click to collapse
Anybody?? Please help
scottwitha5 said:
Anybody?? Please help
Click to expand...
Click to collapse
Update: I followed the Mega Unbrick Guide for a hard bricked Oneplus 3, and now instead of even starting android, this appears, and I cant get into recovery or flash anything because it isnt allowed....please help me
I think your error was to relock the bootloader because if it was still unlocked, you could still reflash the boot.img (but your relocked your bootloader)
Solving it.
Don't worry I shall help you.
This happened to me too.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
To get the drivers and adb along with twrp and root use this toolkit.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Get the Oneplus drivers through this too.
It's not very complicated but ask me for any help.
Use the Method 2 in the Mega UnBrick Guide and download the stock image on to it.
You will lose data all of it.!
Make it boot.
Then tick OEM unlocking
Unlock bootloader through the toolkit.
flash twrp and root done..!!.
You messed up when you ticked off OEM unlocking and fastbooting it.
My girlfriend has a OnePlus 3T and is stuck on Oxygen OS 5.0.4, and it doesn't matter if I download the update via the update settings or install it locally or via adb, or use twrp to flash it, I tried all those ways.
Regardless, the update fails every time. I also tried deleting the ota folder, and rebooting her phone to recovery and deleting cache... that doesn't work either. I also tried using adb and typing in - adb reboot "dm-verity enforcing" - still nothing.
I also used the toolkit from here:
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
and I tried to lock the bootloader. It took me hours to figure out how to get the bootloader unlocked again, cause I had to enter a password to get in, and at the time my girlfriend had no password on her phone at all.
After I figured out about unlocking the bootloader again, I made a password in the security setting, re locked bootloader, still nothing. The password works while phone's bootloader is unlocked, but not while it's locked.
I made a video to further explain and show the situation.
https://www.youtube.com/watch?v=YBtQW00JsNU
Still nothing?
DranzerX13 said:
My girlfriend has a OnePlus 3T and is stuck on Oxygen OS 5.0.4, and it doesn't matter if I download the update via the update settings or install it locally or via adb, or use twrp to flash it, I tried all those ways.
Regardless, the update fails every time. I also tried deleting the ota folder, and rebooting her phone to recovery and deleting cache... that doesn't work either. I also tried using adb and typing in - adb reboot "dm-verity enforcing" - still nothing.
I also used the toolkit from here:
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
and I tried to lock the bootloader. It took me hours to figure out how to get the bootloader unlocked again, cause I had to enter a password to get in, and at the time my girlfriend had no password on her phone at all.
After I figured out about unlocking the bootloader again, I made a password in the security setting, re locked bootloader, still nothing. The password works while phone's bootloader is unlocked, but not while it's locked.
I made a video to further explain and show the situation.
https://www.youtube.com/watch?v=YBtQW00JsNU
Click to expand...
Click to collapse
I watched your video,
Before you relock the bootloader you must install the stock recovery for your device, you can't relock while TWRP is installed, use this guide, (read the guide once completely before you start).
https://forums.oneplus.com/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Also make shure you use the latest ADB drivers Inside (SDK Platform-Tools) from google:
https://developer.android.com/studio/releases/platform-tools
Good Luck!
It worked like a charm. Thank you!
Hi,
I'm stuck on 'samsung' logo screen after flashing stock rom. Please see details below if you can assist.
1. I have sm-505fn from carphone warehouse uk with jan/feb 2020 update..
2. I did oem unlock and flashed twrp
3. this gave bootloader warnings, but eventually went into twrp.
4. I didn't do the dm verify installation and after couldn't get into twrp again. (not sure how to sideload this at this stage)
because i didn't do above step and rebooted, i think i tripped the knox and SG/RMM state became 'prenormal'.
kept getting error: "Only official released binaries are allowed to be flashed" if i tried installing twrp again.
5. tried installing stock rom btu for march 2019, but odin gave errors as couldn't install older stock.
6. then installed feb 2020 stock from sammobile rom A505FNXXS4ATB1 which is the btu version.
7. above worked fine with odin and everything succeeded.
8. On reboot the first warning vanished, and I only got the 2nd bootloader warning. phone went through a 5 second update screen, then rebooted.
9. then got samsung a50 logo and system started booting with plain samsung logo.
10. been stuck at plain samsung logo for 40 min. tried restarting but same problem.
Can you please advise what i should do?
Can't believe its such a headache to install twrp this device (and then later remove the bl warnings
Thanks
ok, I got stock reinstalled and it worked in the end.
the bootloader was unlocked, and developer option to unlock was greyed out.
as it still gave the bootlocker warning, i turned oem lock on again via long press up on download mode. this fixed all warnings and i can boot now without warnings.
when i go into developer mode now, there is no option to oem unlock again.
if i go into download mode, there is no option to long press up and unlock again
on download mode it says:
KG State: prenormal
OEM Lock: ON (U1)
how can I turn oem lock off again, so I can try to install twrp?
Please assist.
thanks
SOLVED -
managed to turn oem unlock option again by turning off auto time update and setting clock back 10 days.
then on restart, the option appeared again and was set to oem unlock ticked.
went into download mode and i could see option again to unlock booloader.
long pressed up and it unlocked bootloader, erased data and restarted to system....
now... lets try to install twrp again and hope it doesn't give me 'unofficial binary' error due to SG prenormal state.
lol.. its KG STATE not SG fyi
Typo
lawmanukdc said:
Typo
Click to expand...
Click to collapse
lol id believe that in 1 comment but everywhere? oh well no biggie lol.. hope ur enjoyin ur phone now
How did you succeed to get the stock reinstalled ? Was it different version ?
lawmanukdc said:
ok, I got stock reinstalled and it worked in the end.
the bootloader was unlocked, and developer option to unlock was greyed out.
Click to expand...
Click to collapse
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
stefan1301 said:
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
Click to expand...
Click to collapse
Sounds to me like the hardware itself is bricked or damaged. If that is the case, the only option is to replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Try to flash latest rom
Here is the solution
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
alaanhaliko said:
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
Click to expand...
Click to collapse
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
alaanhaliko said:
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
Click to expand...
Click to collapse
No, I'm talking specifically of FRP lock.
The point you make about binaries has nothing to do with FRP. Binaries can be blocked on both FRP locked and FRP unlocked devices. The binaries only prevent flashing firmware with a lower binary than the current binary installed on the device. Binary version is related to RMM or KG state, not FRP. FRP is directly related to MDM and only "partially" related to the things you mention and only because there are other "tamper-proof" elements that "can" trigger FRP. Have you ever noticed that a device that does not have a Google account signed in does not encounter FRP issues when the device is factory reset, but if there is a Google account signed in the device, factory reset triggers FRP? If it were as you you seem to be suggesting, FRP would be triggered on devices that have no Google account associated to them when attempting to flash/modify the device, but this is not what happens.
OEM unlock really only applies to unlocking bootloader in order to flash unapproved software or make modifications to the system partition without being blocked.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
Hey,
I unlocked bootloader, then went to flash/root my phone, and it said "only official released binaries are allowed to be flashed (recovery)*".
I then flashed stock firmware and it still said the same thing, now i have flashed stock once more, booted the phone and went through the start questions/settings for my phone, i inserted a sim, took it off, connected to wifi, do i need to let it sit for 168hours now and then go and try to root my phone again via Odin? Freshly flashed firmware phone says "OEM unocking = Bootloader alreay unlocked" and is grey, so i just need to wait now?
You can get around the RMM KG knoxguard prenormal BS by using heimdall to flash just 3 partitions:
"heimdall flash --CM cm.bin --RADIO modem.bin --BOOTLOADER sboot.bin"
I just experienced this myself, unlocked bootloader on the stock ROM Android9 BIT1, but then flashed a more recent stock ROM Android 10 BIT5. Ended up having to ensure OEM was checked and showing in dev options on the new ROM despite it already saying 'Unlocked' in Download mode after enabling it on Android 9 BIT1 ROM.
Even on Wi-fi it didn't show up, but disabling auto date/time, turning off wi-fi, turning on wi-fi, reenabling auto data/time made it appear again