Dear members, i don't see the way how to skip 7 days of waiting on oreo on xda (OEM LOCK and RMM STATE: PRENORMAL).
But i found one.
Note: THIS DOES TRIP KNOX.
Download any ROM before December(Nougat) for your device.
Then, using ODIN and download mode flash that ROM. After setting UP device will not have RMM state in Download mode and you will se OEM unlock in Dev settings.
Now you can flash twrp and get custom ROM (Nougat or Oreo)
DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FOLLOW TUTORIAL AT YOUR OWN RISK.
INTERNAL STORAGE WILL BE COMPLETELY WIPED CLEAN (IF YOU USE CSC_OXM), MAKE SURE YOU BACKUP BEFORE FLASHING.
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
you can press thank's button for them
SmailkO said:
Dear members, i don't see the way how to skip 7 days of waiting on oreo on xda (OEM LOCK and RMM STATE: PRENORMAL).
But i found one.
Note: THIS DOES TRIP KNOX.
Download any ROM before December(Nougat) for your device.
Then, using ODIN and download mode flash that ROM. After setting UP device will not have RMM state in Download mode and you will se OEM unlock in Dev settings.
Now you can flash twrp and get custom ROM (Nougat or Oreo)
DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FOLLOW TUTORIAL AT YOUR OWN RISK.
INTERNAL STORAGE WILL BE COMPLETELY WIPED CLEAN (IF YOU USE CSC_OXM), MAKE SURE YOU BACKUP BEFORE FLASHING.
Click to expand...
Click to collapse
ODIN Does not allow Bootloader downgrade.
JazonX said:
ODIN Does not allow Bootloader downgrade.
Click to expand...
Click to collapse
yes it does. At least this time it does - I have flashed back to Nougat and then back to Oreo several times. If you don't want to be locked out once you have flashed OREO - you can use ODIN to flash a NOUGAT ROM and it will work. I know you can, I have done it.
Work! Thanks ?
JazonX said:
ODIN Does not allow Bootloader downgrade.
Click to expand...
Click to collapse
Who told U that, downgraded BL so many times in Odin.
rajkabul said:
Who told U that, downgraded BL so many times in Odin.
Click to expand...
Click to collapse
Can you explain how you did, So I can try again?
In my Note 7 - It didn't happen. Got a Fail error in ODIN.
JazonX said:
Can you explain how you did, So I can try again?
In my Note 7 - It didn't happen. Got a Fail error in ODIN.
Click to expand...
Click to collapse
Nougat and Oreo firmwares for the S8 are same binary. So you can downgrade.
For The Note Fan Edition, you can't downgrade from binary 2 to binary 1
New way
BlackMesa123 said:
Hello everybody. I got interested about this problem since my friends @Yahia Angelo and @corsicanu got the "Only official released binaries are allowed to be flashed" problem, so we decided to search deeply about this. We found out that this problem isn't related to FRP/OEM Unlock (even if enabled same problem comes), but to a new prop that you can see in Download Mode (RMM State: Prenormal). By searching in system, seems this prop is related to a new "thief" protection Samsung added in latest firmwares. Let's make an example: you get the device, setup Google Account, all good... then someone steals the device and wipes it... ok. After wipe he boots, but he can't pass the setup without internet, and when he connects to internet it asks for your Google account, since your account is saved in FRP partition, so he can't setup. This RMM State is more than that simple FRP, as it doesn't allow him to flash custom binaries to remove FRP. So now let's cut to the chase: who still doesn't have this RMM lock can avoid to get the device locked by following these two simple steps:
1. In build.prop, make sure "ro.security.vaultkeeper.feature" property is set to 0, like this:
Code:
sys.use_fifo_ui=0
ro.wsmd.enable=true
ro.security.vaultkeeper.feature=[COLOR="Blue"]0[/COLOR]
keyguard.no_require_sim=true
ro.carrier=unknown
2. Remove Rlc app. To do this go in "/system/priv-app" folder with a root file manager or with twrp file manager and remove "Rlc" folder.
For those who unfortunately has RMM State set to "Prenormal", as this user reports, seems that by keeping your phone running without shut it off/reboot, at a certain device running time value RMM State prop will set again to "Normal", so you can flash custom binaries again, if it works to you make sure to follow the above steps to not get locked again, I'll keep you guys updated about this when there will be news.
EDIT:
In attachments now you can find a zip that does the job for you. So when RMM State is set back to "Normal", flash a custom recovery and then flash this zip file to avoid lock again
Click to expand...
Click to collapse
UPDATE
rady96 said:
...................Odin flash fails fixed 100% solutions..................Explanation to why odin fails
When your s8/ s8+ is forced rebooted by holding the power and volume down buttons or crash reboots. And when booting into download mode for some reason download mode is locked or corrupted and Odin will fail even if you use official device specific firmware. So follow the steps below to fix
How to fix!
1. Boot into download mode by pressing ( power + volume down + Bixby button) and stop at the screen of continue and reboot.
2. Press volume down to restart phone
3. Quickly boot back into download mode by pressing (power + volume down + Bixby button)
4. Press continue
5. Congratulations fully working now
Click to expand...
Click to collapse
T0nyCr said:
New way
Click to expand...
Click to collapse
of course you have to be Rooted to do it manually and you have to have TWRP installed to flash the fix - so either way - if you can't flash because fo the Official Binaries Only warning - you will have to wait 7 days, 168 hours before you can flash again - or flash the NOUGAT BL as suggested by the OP.
FYI - there is an OREO ROM called Minotaurus (Find it on Telegram) that you can use while on the NOUGAT BL - so you can enjoy the benefits of OREO by first going to back to the last NOUGAT Firmware in ODIN - then flashing MINOTAURUS ROM (V19) - OREO Rom. (It is an excellent rom!)
Obviously this isnt for G955U??
Geekser said:
yes it does. At least this time it does - I have flashed back to Nougat and then back to Oreo several times. If you don't want to be locked out once you have flashed OREO - you can use ODIN to flash a NOUGAT ROM and it will work. I know you can, I have done it.
Click to expand...
Click to collapse
Thats because both nougat(Nov and DEC builds) and oreo are on V2 bootloader at the moment. ODIN DOES NOT allow bootloader downgrade. infact its the phone and not even ODIN controlling that.
It's binary 1, not 2
Envoyé de mon SM-N935F en utilisant Tapatalk
Doesn't work
T0nyCr said:
New way
UPDATE
Click to expand...
Click to collapse
New way (updated) doesn't work, still prenormal rmm state, still can't flash
gastondh91 said:
New way (updated) doesn't work, still prenormal rmm state, still can't flash
Click to expand...
Click to collapse
Just downgrade if you got the S8 or S8+
Envoyé de mon SM-N935F en utilisant Tapatalk
benyou54 said:
Just downgrade if you got the S8 or S8+
Envoyé de mon SM-N935F en utilisant Tapatalk
Click to expand...
Click to collapse
Yeah sure, i have nougat working with no prenormal rmm state but i want to have oreo with no prenormal and when i flash with odin it gets to prenormal again even if do that power+ vol- + bixbie trick, it doesn't work
gastondh91 said:
Yeah sure, i have nougat working with no prenormal rmm state but i want to have oreo with no prenormal and when i flash with odin it gets to prenormal again even if do that power+ vol- + bixbie trick, it doesn't work
Click to expand...
Click to collapse
The prenormal state goes away after 7 days. You have to wait 7 days with the phone turned on. There is no trick to make the rmm state disappeared from the download. Just wait 7 days then flash twrp, magisk and rmm fix [emoji106]
Envoyé de mon SM-N935F en utilisant Tapatalk
Do I have to flash to pure stock or can I stay on a nougat backup for 7 days?
Smartphones13 said:
Do I have to flash to pure stock or can I stay on a nougat backup for 7 days?
Click to expand...
Click to collapse
I don't know what you mean by nougat backup ? You just have to wait 7 days with your FE turned on, that's all.
Envoyé de mon SM-N935F en utilisant Tapatalk
so once I go back to stock rom I just need to wait 7 days with no reboots right?
Related
A brief Intro.
Starting from the 7.1.2 ROMs most of the developers decided to follow the process of checking modem version at the time of flashing the rom. Many peoples ended up in
"Error 7- assert(xiaomi.verify_modem("MSM8976.LA.1.0.c3-30041-STD.PROD-1.77504.1.83742.1") == "1")"
The main reason for this is the outdated firmware or it is happened to those who had unofficially unlocked the bootloader.
Some more info..
1. You must be on MM build bootloader. If you are unofficially unlocked bootloader it will give you ERROR7.
@TheStrix have alreday given a short information about it in his Official LineageOS thread. If you are unaware of it read it here
2.Outdated Firmware.
Your firmware must be from from MIUI Global DEV v7.5.4 or above.
Get MIUI Global DEV v7.5.4 from here
or the latest firmware from here
NB:-
- Iam using the MIUI Global DEV v7.5.4 firmware. All working fine including Volte. I dont know about the second one,you can give it a try.
-If you are unofficially unlocked ,MIUI Global DEV v7.5.4 will re lock your bootloader you will end up in bootloop.
- I will not be reponsible for any damages.
Solution 1 [Permanent Solution] ..
1. So if you are unofficially unlocked, i will suggest to clean flash the latest MIUI Fatboot Rom. Kenzo users get it from here.
2.Flash it using MIFlashTool ,and officially unlock it.
HOW TO UNLOCK THE BOOTLOADER OF REDMI NOTE 3?
PART 1 : REQUESTING FOR UNLOCK PERMISSION
Step 1 – Open up your favorite web browser in your computer (Chrome is recommended) then go to this link
Step 2 – You’ll see the official page of “Unlock Your Mi Device”. Now simply click on the blue “Unlock Now” Button in the middle of the page.
Step 3 – You’ll see a login page in the next page which is in Chinese. If you use Google Chrome to open the page, then you can simply use its built-in Google Translate feature.
Step 4 – Once logged in, you’ll see the Unlock Application Permissions page.Now simply fill in all required fields then click on that green Apply Immediately button.
Step 5 – In the next page, you’ll need to enter a verification code sent to you via SMS. Check your phone for any SMS verification sent by Xiaomi server. The code is usually valid for only 5 minutes so you need to enter it immediately.
Step 6– Once you have submitted the 6 digits code, you’ll then be redirected to another page saying that from the point toward all you need to do is just waiting for Xiaomi Developers to review and approve your application. Once approved, you’ll get another SMS which normally arrives in 15 min(Atleast for me. For some it may take time). The approval process is manual so just be patient on this.
PART 2 : BOOTLOADER UNLOCKING PROCESS
Requirements for Bootloader Unlocking :
-An active Mi account linked to your device, your phone number and it has permission to proceed with bootloader unlock (follow previous steps above)
-Please backup your data for just in case scenario.
-Again, if you are not fully aware of flashing custom ROM, then you better stay away of unlocking your phone’s bootloader.
Download Mi Flash Unlock tool for Windows here, and install it on your computer / PC.
Step 1 – On your device, please login to your Mi account.
Step 2 – Put / reboot your device into bootloader mode. To do that, simply turn off your device, press the Power button and Volume down ( – ) button at the same time.
Step 3 – On your computer, open MiFlash Unlock tool you’ve just installed. Click on the Agree button when asked.
Step 4 – Login to MiFlash Unlock tool with the same Mi Account.
Step 5 – Now connect your phone to computer using its USB cable.
Step 6 – Once your phone is connected, the Unlock button will become active. Next, simply click on the Unlock button to start the process. The unlock process will take about 10 – 15 seconds to complete. That’s all.
After unlocking your phone’s bootloader, you’ll be able to flash TWRP and other custom ROM. Enjoy..
Please take these as your concern upon unlocking bootloader :
One Mi account could only unlock one device within 30 days.
If you see a notice saying that “current user is not logged in connected device” then please reboot your device normally then login with your account in the device (see Step 1).
Unlocking bootloader will wipe all user data especially if your device is encrypted. That’s why you’ll need to create backup before going to proceed.
Neither Xiaomi or I will guaranteed if anything goes wrong during and as the result of unlocking. Proceed with your own risks.
Also, unlocked Xiaomi devices will be marked in the official service end.
PART 3 : Installing TWRP and Custom Rom.
Step 1 –. Get latest TWRP from here. Flash it via fastboot { I will not be explaining that in details}
Step 2 –. Take back up of EFS using Twrp. Wipe Everything including internal storage.
Step 3 –. Install Firmware-Rom-Gapps in order. Error 7 will be solved
Solution 2[Temporary Solution] ..
Only try this method if you are not able to officially unlock your device . Dont use the Firmware by Strix.It will relock your bootloader.
Step1 - Downalod the rom to your pc.
Step2 - Use any notepad. Suggestd one Notepad++. Get it from here
Step3 - Open the Rom.zip{dont extarct}. Navigate to META-INF/com/google/android/updater-script.
Double click on updater-script and open it with notepad++. Edit and remove this line from the file
Code:
assert(xiaomi.verify_modem("MSM8976.LA.1.0.c3-30041-STD.PROD-1.77504.1.83742.1") == "1")
Allow the file to save and close the zip.{Rom will recompress by itself}.
Step4 - Flash in order. Firmware -Rom-Gapps.
Some FAQ's ..
1. Iam not getting volte
Ans:- Restore the EFS. Try rebooting your phone 2 or 3 times. After Clean flash ,I had to reboot 3 times to get volte working. :fingers-crossed:
2.Iam not able to see FingerPrint Option?
Ans:- Your are defenitely on an old Firmware.Update to Latest Firmware It will work.
3.Iam getting Some other Errors. :crying:
Ans:- Post your Screen Shot Below.Will Check.
4.Iam getting some other problems in ROM.
Ans:- Report it with proper logs to the developer.Iam helpless.
5.I bricked my device
Ans:- I will Laugh at you. Always do everything at your own risk. :silly:
Some Advices ..
* At least use search once in your life time. From my observation its clear that no one ever uses search in the Rom Section. Even is there is a solution in every page you keep on asking same questions.
*Dont flood the thread.
*Dont qoute the whole op.
*Respect other members
If this was of help to anyone hit the like :fingers-crossed:
First
There's a problem with not updating the bootloader (aboot) and staying with a LP bootloader, you will most likely encounter bootloops. Say you edit that code line for the modem check, it will flash but it won't boot/work properly. You must update the bootloader in order to boot newer ROMs. And you need to update the modem and other stuff so you won't face issues. You need to offcially unlock no matter what you do, it's very easy.
Asphyxiate666 said:
There's a problem with not updating the bootloader (aboot) and stay with a LP bootloader, you will most likely encounter bootloops. Say you edit that code line for the modem check, it will flash but it won't boot. You must update the bootloader in order to boot newer ROMs. And you need to update the modem and other stuff so you won't face issues. You need to offcially unlock no matter what you do, it's very easy.
Click to expand...
Click to collapse
that's why I wrote temporary method..only for those who are lazy and not willing to start from root by flashing fastboot rom
adithyan25 said:
that's why I wrote temporary method..only for those who are lazy and not willing to start from root by flashing fastboot rom
Click to expand...
Click to collapse
I understand but with their laziness they will ruin their devices then come here and say "omg sir it doesn't boot wtf is this useless rom crap developers".
Asphyxiate666 said:
I understand but with their laziness they will ruin their devices then come here and say "omg sir it doesn't boot wtf is this useless rom crap developers".
Click to expand...
Click to collapse
I know that...most people don't even bother to use search..even if there is a solution just above their question they won't give a damn to look it..
guys help..i had officially unlocked the bootloader..and i don't remember the firmware i had installed...n i am still getting the error code 7..do i need to flash the kenzo global or dev firmware from the link..??
PrathaM X said:
guys help..i had officially unlocked the bootloader..and i don't remember the firmware i had installed...n i am still getting the error code 7..do i need to flash the kenzo global or dev firmware from the link..??
Click to expand...
Click to collapse
you must format your phone (not wipe) using twrp then install fw-rom-gapps...use fw by strix from above method(permanent)
I flashed v8.5.1.0 using MiFlash and it said flash completed successfully. However now it is stuck on the Mi splash screen with "powered by android" logo at the bottom. The dots are moving so I assume it is loading but it's been on that same screen for the past 10 minutes now.
Previously, the bootloader was officially unlocked but some stuff broke as I tried to upgrade to a new ROM and that's why I decided to flash v8.5.1.0 in order to go back to stock and start from scratch.
Edit: It works!
adithyan25 said:
you must format your phone (not wipe) using twrp then install fw-rom-gapps...use fw by strix from above method(permanent)
Click to expand...
Click to collapse
I'm on Marshmallow boot loader (flashed faatboot ROM) and officially unlocked & formated data.
Yesterday I did a update RR ROM (9th july) then I got error 7.
at the time of flashing I was on latest firmware 7.7.6.
So reflashed 7.5.4 firmware and it's worked.
So we should always stick to 7.5.4 firmware ? For avoiding error 7?
baku2313 said:
I'm on Marshmallow boot loader (flashed faatboot ROM) and officially unlocked & formated data.
Yesterday I did a update RR ROM (10th july) then I got error 7.
at the time of flashing I was on latest firmware 7.7.6.
So reflashed 7.5.4 firmware and it's worked.
So we should always stick to 7.5.4 firmware ? For avoiding error 7?
Click to expand...
Click to collapse
yep..in my knowledge the latest firmware has a change in modem version(updated version) so it wont match with one in updater script... so i will say to stick with some older firmware unless the developers chabge it in the roms update-script file...
iam using strix fw 7.6.15
adithyan25 said:
yep..in my knowledge the latest firmware has a change in modem version(updated version) so it wont match with one in updater script... so i will say to stick with some older firmware unless the developers chabge it in the roms update-script file...
iam using strix fw 7.6.15
Click to expand...
Click to collapse
Can you provide me the link please.
baku2313 said:
Can you provide me the link please.
Click to expand...
Click to collapse
its in the aosp extended 4.4 update op...
im quite busy now...i will share it later if you havent found it .... you will find the link in aosp extended thread
adithyan25 said:
its in the aosp extended 4.4 update op...
im quite busy now...i will share it later if you havent found it .... you will find the link in aosp extended thread
Click to expand...
Click to collapse
Strix updated his thread with 7.7.6 firmware (Kenzo).
I am on MM on Redmi note 3 Snapdragon version! I tried firmware (7.7.0 I guess) and then ROM Zip but still got the Problem ! Any thing else I can do?
What if i have locked bootloader and flashed twrp through miflash?
coolguy22 said:
What if i have locked bootloader and flashed twrp through miflash?
Click to expand...
Click to collapse
In theory it should work I guess? Assuming you used the guide from @khajiit here you should have a MarshMellow bootloader, as the MIUI version linked there is based on MM (kate_global_images_6.11.3_20161103.0000.00_6.0_global_16db0fc5fa), so it shouldn't relock. Can't try myself since I unlocked mine recently.
Amon_Re said:
In theory it should work I guess? Assuming you used the guide from @khajiithere you should have a MarshMellow bootloader, as the MIUI version linked there is based on MM (kate_global_images_6.11.3_20161103.0000.00_6.0_global_16db0fc5fa), so it shouldn't relock. Can't try myself since I unlocked mine recently.
Click to expand...
Click to collapse
Ok so if i get the latest firmware and install some 7.1.2 rom it shouldn't bootloop?
coolguy22 said:
Ok so if i get the latest firmware and install some 7.1.2 rom it shouldn't bootloop?
Click to expand...
Click to collapse
In theory, it should work.
..
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
not work
says: SECURE CHECK FAIL : (BOOTLOADER)
also for me....not work....
Gracias !
arcanemyth said:
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
Click to expand...
Click to collapse
Hi Sir,
Also just went through with that dreaded 'Only official released binaries are allowed to be flashed' while trying to install TWRP 3.2.1-0 and root via magisk v16. My G950FD was just a few days old though bought this in used condition. Its currently on v8 Oreo. After flashing this with the stock rom https://forum.xda-developers.com/galaxy-s8/development/rom-galaxy-s8-t3749171 the phone sprang back to life its the 2nd day and still OEM unlock option has not showed up and am quite impatient already wanting to have TWRP and root. After flashing your Nougat bootloader, will I follow this same procedure again? https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
Thanks
So what to do, i wait seven days on my S8. OEM unlock appears, but the phone stays in prenormal mode?
Worked perfectly for me and I also have a G950FD. Thanks a lot man !!!
Wow thanks a lot! This worked great, I was about 3 days into the wait after I made a mistake when flashing..
Really wanted Notorious kernel so I can use Dex, all solved now.
THanks!
arcanemyth said:
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
Click to expand...
Click to collapse
Thank you! I have been fighting with this for what seems like forever and thought I was screwed but this helped! :good:
se puede usar ese metodo para s8+ con oreo ?
I got same problem 'Only official released binaries are allowed to be flashed' and i tried to flash stock rom but it gives fail. Also it says sw rev check fail 2 binary 1 on download mod. how ca i solve this?
The10y said:
I got same problem 'Only official released binaries are allowed to be flashed' and i tried to flash stock rom but it gives fail. Also it says sw rev check fail 2 binary 1 on download mod. how ca i solve this?
Click to expand...
Click to collapse
Just odwnload one firmware bit 2
maurote said:
Just odwnload one firmware bit 2
Click to expand...
Click to collapse
Could you please elaborate? I don't understand. I'm having the same issue.
Try this:
1)- change phone date manually back 8 days
2) go to software update and check for update. You should receive errors messages sometime. Don't worry. Just ignore it.
3)- restart phone immediately after checking software update and go to Developer Options and you should see OEM Unlock appear back. You may need to try checking software update few times to get it work.
Additional information:
https://forum.xda-developers.com/showpost.php?p=76746640&postcount=12
help please I had the same problem, try flashing the attached boot manager but I get error in odin
please twrp for CRGB not work
doesn't work, fail in both normal odin n the special odin.
arcanemyth said:
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
Click to expand...
Click to collapse
Hello,
Could you please tell us if that gonna work for S8 G950FD Oreo 8.0.0 AUG 2018 G950FXXU3CRGH?
I used RMM-State_Bypass_Mesa which is set vaultkeeper.feature parameter to 0 and remove /system/priv-app/Rlc" and maybe more!!
Because it's song good until the test reboot where the system is still stucked with this message.
Many thanks
arcanemyth said:
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
Click to expand...
Click to collapse
I just get "SECURE CHECK FAIL : (BOOTLOADER)"
milaniov said:
I just get "SECURE CHECK FAIL : (BOOTLOADER)"
Click to expand...
Click to collapse
At a guess without more info I would say you are trying to downgrade your firmware
Okay, so I flashed TWRP onto my Galaxy S8 using Odin and then it said my workspace has been locked due to unauthorised software being installed on the device, so I then went and found my firmware online to flash it onto my device, hoping to bypass my workspace restriction but then found flashing the software factory reset my device, so I lost TWRP recovery. How on Earth do I flash TWRP onto my Samsung Galaxy S8 without being blocked from using my device? I’m a noob at this stuff but have some know how to get this far... Any help would be greatly appreciated! Thanks.. My end goal is to root my phone with Magisk and bypass SecurityNet restrictions on my phone from unlocking my bootloader.
Kriranda said:
Okay, so I flashed TWRP onto my Galaxy S8 using Odin and then it said my workspace has been locked due to unauthorised software being installed on the device, so I then went and found my firmware online to flash it onto my device, hoping to bypass my workspace restriction but then found flashing the software factory reset my device, so I lost TWRP recovery. How on Earth do I flash TWRP onto my Samsung Galaxy S8 without being blocked from using my device? I’m a noob at this stuff but have some know how to get this far... Any help would be greatly appreciated! Thanks.. My end goal is to root my phone with Magisk and bypass SecurityNet restrictions on my phone from unlocking my bootloader.
Click to expand...
Click to collapse
Follow this to the letter and you'll have twrp running. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
PS...go to page one first post
xlucian said:
Follow this to the letter and you'll have twrp running. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
PS...go to page one first post
Click to expand...
Click to collapse
hi.
i have an g950fd on 8.0
with this new firmware... 8.0 G950FXXU4CRKB
when i install "twrp", "RMM-State_Bypass_Mesa" and "magisk 18"
then it boot ok. BUT, when reboot.. BAM!
soft brick with the message "only official released binaries are allowed", even twrp i cant access...
ive gotten on download and flashed the firmware again and its on; but i really want my root....
so my rmm didnt worked.. how can i bypass this?!?!
anyone has a new rmm? please!!
b4 k3 s3
what i think is that i get oem unlock --> twrp-3.2.3-2-dreamlte --> rmm + magisk + samsung-antiroot-removal-2.4
and at some point the firmware reblock oem
what can i do? thanks!
Are you using the dm-verity thing?
rodrigodornas said:
hi.
i have an g950fd on 8.0
with this new firmware... 8.0 G950FXXU4CRKB
when i install "twrp", "RMM-State_Bypass_Mesa" and "magisk 18"
then it boot ok. BUT, when reboot.. BAM!
soft brick with the message "only official released binaries are allowed", even twrp i cant access...
ive gotten on download and flashed the firmware again and its on; but i really want my root....
so my rmm didnt worked.. how can i bypass this?!?!
anyone has a new rmm? please!!
b4 k3 s3
what i think is that i get oem unlock --> twrp-3.2.3-2-dreamlte --> rmm + magisk + samsung-antiroot-removal-2.4
and at some point the firmware reblock oem
what can i do? thanks!
Click to expand...
Click to collapse
at step 7 from install twrp...
when you are in twrp chose format and format the data to remove encryption.
I also got the message "only official released binaries are allowed" and twrp was gone and replaced by factory recovery
xlucian said:
at step 7 from install twrp...
when you are in twrp chose format and format the data to remove encryption.
I also got the message "only official released binaries are allowed" and twrp was gone and replaced by factory recovery
Click to expand...
Click to collapse
dude same here!
i dont even can enter on recovery even twrp or samsung..
and i formated too...
so..... its a new block? im using the worng rmm?
im on b4 k3 s3
i can downgrade to any b4 is that correct?
any b4 with root related?
thanks!
rodrigodornas said:
dude same here!
i dont even can enter on recovery even twrp or samsung..
and i formated too...
so..... its a new block? im using the worng rmm?
im on b4 k3 s3
i can downgrade to any b4 is that correct?
any b4 with root related?
thanks!
Click to expand...
Click to collapse
try and start from scratch
find the latest oreo firmware for you
flash it with odin and make sure OEM unlock is enabled
then follow again the guide...make sure you format data after step 7
xlucian said:
try and start from scratch
find the latest oreo firmware for you
flash it with odin and make sure OEM unlock is enabled
then follow again the guide...make sure you format data after step 7
Click to expand...
Click to collapse
i did...
today i enter on "oneclickroot" to check if its another way so i can root my device and the site says:
"SORRY
There Is No Root At This Time
Brand: samsung
Model: sm-g950f
Android Version: 8.0.0 (r16nw.g950fxxs4crlb)"
i found that the first firmware from b4 "G950FXXU4CRI5" on onclickroot appear rootable!
the same bootloader permit me to downgrade? or have other issues?
if oem unlock i just flash with odin?
thaks
rodrigodornas said:
i did...
today i enter on "oneclickroot" to check if its another way so i can root my device and the site says:
"SORRY
There Is No Root At This Time
Brand: samsung
Model: sm-g950f
Android Version: 8.0.0 (r16nw.g950fxxs4crlb)"
i found that the first firmware from b4 "G950FXXU4CRI5" on onclickroot appear rootable!
the same bootloader permit me to downgrade? or have other issues?
if oem unlock i just flash with odin?
thaks
Click to expand...
Click to collapse
You can flash with odin original firmware even if you don't have oem unlock.
But, to install twrp and root you NEED to have the oem unlock enabled in the developer settings
xlucian said:
You can flash with odin original firmware even if you don't have oem unlock.
But, to install twrp and root you NEED to have the oem unlock enabled in the developer settings
Click to expand...
Click to collapse
but about downgrade.. what is my barrieir?
can just downgrade to same bootloader or i can downgrade to others versions?
thanks!!
i flashed stock room on my s8, do i need to wait 7 days again to flash twrp? oem lock is off
trexander said:
i flashed stock room on my s8, do i need to wait 7 days again to flash twrp? oem lock is off
Click to expand...
Click to collapse
Depends, will have to check in download mode, if kg state and/or rmm state is prenormal then you will have to wait.
Om my s8 if i flash firmware i can modify my phone as soon as i connect to the imternet.
Hy their,
I heared that Since Bootloader Level 2 + are some Problems to Flash Roms,Kernel and other Things!
Is it true that if i have Bootloader Level 4 i can Only Flash BL 4 Roms ?
Or is their now a fix out how Stock Rom Oreo Rom with Bootloader Level 4 or others ....
Any Methode to Flash TWRP,Root and Flash any Rom with any Bootloader i would like ?
Or must The Bootloader Level always be The same?
Thanks for helping me!
I only Flashed Twrp,Magisk & Custom Roms on my Samsung S5 before !
MY Software Info is Attached
Overload87 said:
Hy their,
I heared that Since Bootloader Level 2 + are some Problems to Flash Roms,Kernel and other Things!
Is it true that if i have Bootloader Level 4 i can Only Flash BL 4 Roms ?
Or is their now a fix out how Stock Rom Oreo Rom with Bootloader Level 4 or others ....
Any Methode to Flash TWRP,Root and Flash any Rom with any Bootloader i would like ?
Or must The Bootloader Level always be The same?
Thanks for helping me!
I only Flashed Twrp,Magisk & Custom Roms on my Samsung S5 before !
MY Software Info is Attached
Click to expand...
Click to collapse
1. With bootloader version number's you can only flash the same or higher versions only. You can not downgrade bootloader versions numbers. eg: from Pie/Oreo to nougat or lower ( bl4 to bl3 or lower ).
2. With Oreo/pie brings a new lock In to the system called RMM state and kg state. You can check in download mode.
3. It's basically still the same method for installing twrp, root, custom rom etc.
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
RMM State Flash with TWRP
Hy again,
I have an Question.... I think that if i would Flash TWRP and RMM State. Format Device after it ...! Than their would be FRP and old Google Account Erased too ....right ?
Overload87 said:
Hy again,
I have an Question.... I think that if i would Flash TWRP and RMM State. Format Device after it ...! Than their would be FRP and old Google Account Erased too ....right ?
Click to expand...
Click to collapse
1. After installing twrp you will need to format data first then reboot back into twrp then flash/install everything else.
2. Deleting accounts from phone does not delete the account from the server side of things. ie: google account.
3. If frp locked in on ( check in download mode ) it maybe worth while turning it off.
4. Before doing anything always backup your phone first.
I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.
xperia ray said:
I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.
Click to expand...
Click to collapse
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.
Anlle said:
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.
Click to expand...
Click to collapse
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.
xperia ray said:
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.
Click to expand...
Click to collapse
Thank you, I will try until my phone is rooted. best of luck of me hehehe.
Anlle said:
Thank you, I will try until my phone is rooted. best of luck of me hehehe.
Click to expand...
Click to collapse
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/gal...j7nxt-t3974337
xperia ray said:
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
Click to expand...
Click to collapse
Thanks
According to the photos shown, you need to use MiracleBox, as it is prenormal
Try using this tutorial