Hello Forum,
i'm not new to rooting, custom roms et cetera.
But with the A530F, i got my first phone with the RMM-feature an Android Pie.
As far as my question couldn't be solved by the existing threads and posts, i hope you can help me clarify these things:
As far as i think i've learned from your posts, the RMM-state prenormal is being set when:
- i'm on stock rom
- toggle "oem unlock" in dev options
- flash any custom-thing by odin (twrp/nom official binary etc)
- boot into stock before flashing this "rmm_disabling.zip" because in Stock rom, the vaultkeeper-system triggers rmm...
So far, so good..
But:
What happens if :
- After flashing TWRP, i directly boot into twrp and delete all partitions, flash the Treble_System and a GSI etc?
- In this case, there, so i think, shouldn't be a vaultkeeper in the rom ever, which can ever trigger the rmm again to prenormal? Or am i wrong.
I ask, because in the guides here, i should always flash the rmm-disabling zip... but why, when only the stock rom can trigger the rmm to "prenormal".
Please help me to clarify this problem...
My intention is simply to leave stock, go to treble and then flash a gsi... and never think about rmm again...
Thank you!
Gesendet von meinem SM-A530F mit Tapatalk
I've never flashed that rmm zip after installing a gsi on my phone. Never got locked with that. The only time I got locked was on stock rom, and that was an frp lock 'cause I turned off OEM unlock while being rooted.
Okay, that sounds good and makes sence for me... otherwise i'd misunderstood the whole rmm thing...
So it works like i thought:
1. After flashing any kind if custom binary (recovery/rom et cetera) and rebooting to the os...
2. ...The vaultkeeper integrated (only) in the stock-rom triggers the rmm-staterenormal flag and locks any further non-stock-binarys for the waiting time of 7? days...
3. So if flashing a custom-recovery and wiping all Data/Stock-rom immediately after that.. i should be protected from rmm and can flash whatever i want without being locked out by rmm...
That's sounds good
Thank you very much for your help!
Greetings, Tob!
Gesendet von meinem SM-A530F mit Tapatalk
Related
HI Guys, I have installed the G955FXXU1CRAP at my s8+ but when I try to flash twrp with odin it get status fail and the phone says that installation of custom binaries are not allow (OEM LOCK and RMM STATE: PRENORMAL).
Did you tryed to install Twrp and root G955FXXU1CRAP? How you solve this bootloader lock?.
thanks in advance.
Alex.
In order to root you have to flash TWRP and for that OEM must be unlocked. You have to wait 7 days with the phone on (without reseting) to get capable of unlock OEM in developer options, due to a new security issue with Samsung.
I'm in the same situation. 4 days and 10 hours left.
This has been said a bunch of times throughout the S8 Plus threads - but I will give it to you again.
your phone is locked - y ou will not be able to flash anything until you pass the 168 hour (7 day) period. When you do get to that point, you can flash twrp, root and or flash a custom rom. Whatver you do, before you reboot your phone, flash the file you find at this thread: https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 It will make it so you don't have to do that again. Your phone will not get locked again and the RMM State will be NORMAL - instead of Pre-normal.
That is the only thing you can do. And it is important to remmeber to flash the RMM Fix before you reboot (after flashing twrp, SuperSU/Magisk and or a Custom Rom. If you don't flash that file yoiu will be very likely locked again for another 7 days as soon as you reboot.
The link above has a much better explanation but I hope this helps you and anyone else reading this that has the same problem.
Good Luck. (I have been waiting for 4 days so far - I have three days to go -
Well, thank you so much for that information guys. I did not know it.
Geekser said:
This has been said a bunch of times throughout the S8 Plus threads - but I will give it to you again.
your phone is locked - y ou will not be able to flash anything until you pass the 168 hour (7 day) period. When you do get to that point, you can flash twrp, root and or flash a custom rom. Whatver you do, before you reboot your phone, flash the file you find at this thread: https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 It will make it so you don't have to do that again. Your phone will not get locked again and the RMM State will be NORMAL - instead of Pre-normal.
That is the only thing you can do. And it is important to remmeber to flash the RMM Fix before you reboot (after flashing twrp, SuperSU/Magisk and or a Custom Rom. If you don't flash that file yoiu will be very likely locked again for another 7 days as soon as you reboot.
The link above has a much better explanation but I hope this helps you and anyone else reading this that has the same problem.
Good Luck. (I have been waiting for 4 days so far - I have three days to go -
Click to expand...
Click to collapse
Could you please be more detailed on the steps I should take for not being locked again?
I'm about to flash Oreo and I want to flash TWRP and Magisk manager after those 7 days but I don't know in what order I should do it all, when I have to flash that RMM aswell.
cyborgium said:
Could you please be more detailed on the steps I should take for not being locked again?
I'm about to flash Oreo and I want to flash TWRP and Magisk manager after those 7 days but I don't know in what order I should do it all, when I have to flash that RMM aswell.
Click to expand...
Click to collapse
Go here and read what the say about the RMM State fix - should explain everytihng https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Geekser said:
Go here and read what the say about the RMM State fix - should explain everytihng https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
Take a look at this screenshot though. I installed the CRAP build less than a day ago and when I first went into developer options, OEM unlock was already enabled. I'm REALLY confused right now..
Geekser said:
Go here and read what the say about the RMM State fix - should explain everytihng https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
Not sure if you know the answer to this but do we have to flash this every time we reboot on a custom ROM or flash this every time we flash a custom ROM?
I have 8 hours left until the lock is lifted on mine lol
cyborgium said:
Take a look at this screenshot though. I installed the CRAP build less than a day ago and when I first went into developer options, OEM unlock was already enabled. I'm REALLY confused right now..
Click to expand...
Click to collapse
Go into download mode (Power, Bixby and Vol Down) when you are in download mode, you can see what the RMM State is - it will either say NORMAL or PRE-NORMAL.
If yours says NORMAL - then you go can go ahead and flash TWRP via ODIN. If you are having flash issues at this point, ask in the TWRP Thread and you should be able to get some help.
However, if you are PRE-NORMAL in download mode, then you are locked and won't be able to flash anything until you pass the 7 day period.I think the 7 days begins on the date you flashed your current firmware.
YOu can be in PRE-NORMAL and still see OEM UNLOCK. BUT if you are pre-normal and you see OEM UNLOCK you cannot flash until your RMM State changes to NORMAL.
I hope that helps.
xxxrichievxxx said:
Not sure if you know the answer to this but do we have to flash this every time we reboot on a custom ROM or flash this every time we flash a custom ROM?
I have 8 hours left until the lock is lifted on mine lol
Click to expand...
Click to collapse
Yes, the RMM Fix must be flashed after you flash TWRP or after you flash a custom rom, everytime. UNLESS the rom has the RMM Fix baked into the rom - some do - some may not. Won't hurt to fllash it just in case, everytime.
Thanks again for the rapid response but, I'm identifying an issue with the storage on this firmware g955fxxu1crap. My phone exynos g955f has 64 gb of internal storage, but after this upgrade it shows only 16 gb of internal storage.
Did get this same error , how you solve it?
thanks in advance.
Ale3385
josegon30 said:
In order to root you have to flash TWRP and for that OEM must be unlocked. You have to wait 7 days with the phone on (without reseting) to get capable of unlock OEM in developer options, due to a new security issue with Samsung.
I'm in the same situation. 4 days and 10 hours left.
Click to expand...
Click to collapse
What happened after your seven days were you able to flash twrp and stay rooted in Oreo with Oreo bootloader and modem? Have you tried flashing the new Oreo Bl & Modem? Curious if the seven days is going to be mandatory for people with new phones that want to root them on Oreo.
Psyscope said:
What happened after your seven days were you able to flash twrp and stay rooted in Oreo with Oreo bootloader and modem? Have you tried flashing the new Oreo Bl & Modem? Curious if the seven days is going to be mandatory for people with new phones that want to root them on Oreo.
Click to expand...
Click to collapse
After 7 days I could perfectly flash TWRP and root, no big deal. If you go into download mode and see RMM STATE: PRENORMAL then you can't flash. I guess all new phones with 8.0 since January are pre-normal, but I'm not sure.
Ive seen in the other thread that you could flash the entire nougat stock rom (nov 2017 perhaps) which will allow you to bypass the rmm and then flash TWRP and custom ROM? Could anyone confirm this workaround?
Hi! I'm really humbly sorry, I'm new to this stuff, so I have to ask you...
I have a Galaxy S8+ Duos (SM-GD955FD). I bricked it once or twice trying to root it. So I had to flash a sammobile.com ROM...
Now this is done, I have a successfully rooted phone with with the Baseband version G955FXU1AQH3 and the irritating "security notice" (since I was not able to install Magisk, and the NotifyClean app doesn't work either).
I would like to flash the latest Oreo and root it. I also heard good things about the Oreo ROM by alexega.
So: I'm on AQH3 rooted. What can I do?
Thank you for your patience.
If wou want to install stock ROM you must follow this instructions: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-flash-crap-using-odin-t3748555. Bear in mind that if you install stock due to security issues you can't unlock OEM for 7 days after flashing (you must not reboot your phone for 170 hours).
If wou want to flash a custom rom you must have TWRP installed, move the zip rom to your SD card and just flash it from recovery. Make sure to format data before flashing.
josegon30 said:
If wou want to install stock ROM you must follow this instructions: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-flash-crap-using-odin-t3748555. Bear in mind that if you install stock due to security issues you can't unlock OEM for 7 days after flashing (you must not reboot your phone for 170 hours).
If wou want to flash a custom rom you must have TWRP installed, move the zip rom to your SD card and just flash it from recovery. Make sure to format data before flashing.
Click to expand...
Click to collapse
Nice, thank you. So I have just flashed the thing with the sammobile.com ROM again (so, no root) and updated to the oroginal firmware Oreo following your link (I worked parallel).
I was just about to root Oreo and was googling for a way... But did I get you right? I should not reboot my phone for 170 hours now?!? So, no rooting until next week?!
Edit: I have developer options enabled and the "OEM unlock" switch is on (it says: "Bootloader is already unlocked.""). So... confusion...
andifla852 said:
Nice, thank you. So I have just flashed the thing with the sammobile.com ROM again (so, no root) and updated to the oroginal firmware Oreo following your link (I worked parallel).
I was just about to root Oreo and was googling for a way... But did I get you right? I should not reboot my phone for 170 hours now?!? So, no rooting until next week?!
Edit: I have developer options enabled and the "OEM unlock" switch is on (it says: "Bootloader is already unlocked.""). So... confusion...
Click to expand...
Click to collapse
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Just rooted the new Oreo ROM with TWRP. Works just fine, thank you.
So, what are the advantages of the Oreo ROM by alexega compared to XXU1CRAP?
josegon30 said:
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Click to expand...
Click to collapse
Hi Jose. I am with stock nogat. Not root. Any advice for flash stock oreo firmware?
Allrey know about odin. Im talking about unlock options, etc.
Thks
Juan from Argentina.
juange said:
Hi Jose. I am with stock nogat. Not root. Any advice for flash stock oreo firmware?
Allrey know about odin. Im talking about unlock options, etc.
Thks
Juan from Argentina.
Click to expand...
Click to collapse
Just follow the steps from the link in my previous repply. As it's an original software, it won't trip knox or void your warantee.
hi, does anybody knows how to install the oreo firmware using odin but without changing the csc I already have?
josegon30 said:
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Click to expand...
Click to collapse
Do you need a custom rom to not have the RMM lock anymore? A stock with BlackMesa's RMM START .zip is not right?
costafabiof said:
Do you need a custom rom to not have the RMM lock anymore? A stock with BlackMesa's RMM START .zip is not right?
Click to expand...
Click to collapse
There's no need to have a custom rom, if you flash the fix in stock RMM lock gets killed everytime.
josegon30 said:
There's no need to have a custom rom, if you flash the fix in stock RMM lock gets killed everytime.
Click to expand...
Click to collapse
Did not work.
I can not find out where I went wrong.
developer11 said:
Android.com.pl **** you
Little cocksucker
Click to expand...
Click to collapse
Translation?
costafabiof said:
Did not work.
I can not find out where I went wrong.
Click to expand...
Click to collapse
First you have to install OREO and wait 7 days without reseting your phone. After 170 hours, you get OEM unlock in developer options and you will be able to flasf TWRP. After flashing TWRP you flash RMM-State_Bypass_Mesa and that´s all.
josegon30 said:
First you have to install OREO and wait 7 days without reseting your phone. After 170 hours, you get OEM unlock in developer options and you will be able to flasf TWRP. After flashing TWRP you flash RMM-State_Bypass_Mesa and that´s all.
Click to expand...
Click to collapse
That did not work out. But thank you for your attention.
Hi all, thanks in advance for reading me.
I have this model:
S8+ (SM-G955FD) with the last firmware from sammobile G955FXXU4CRJ5
When I flashed that firmware with ODIN I wanted to root, so this is what I did:
1. Changed the date of the date of the phone and went to "update firmware" and then reset to get OEM unlocked
2. Went to download mode and flashed succesfully TWRP.
3. In TWRP I formated data (yes) and rebooted into recovery
4. Flashed the following files: a) Magisk, b) No verify 6.0, c) RMM state bypass Mesa, d)samsung anti-root removal 4.1
5. Rebooted into system
Click to expand...
Click to collapse
After doing that, everything seems to be OK... I can re-config my phone and Magisk Manager is installed. But when I went to Developer options I can't see "OEM unlock" activated. So, when I rebooted I got the "only official released binaries are allowed to be flashed" error.
I made the procedure several times. Is that related to the "October security patch update"? I think the error is due to a failure in RMM state bypass flashing, although the flashing procedure says "OK. Done".
Anyone have the same issue? do you guys know how to fix it?
josegon30 said:
Hi all, thanks in advance for reading me.
I have this model:
S8+ (SM-G955FD) with the last firmware from sammobile G955FXXU4CRJ5
When I flashed that firmware with ODIN I wanted to root, so this is what I did:
After doing that, everything seems to be OK... I can re-config my phone and Magisk Manager is installed. But when I went to Developer options I can't see "OEM unlock" activated. So, when I rebooted I got the "only official released binaries are allowed to be flashed" error.
I made the procedure several times. Is that related to the "October security patch update"? I think the error is due to a failure in RMM state bypass flashing, although the flashing procedure says "OK. Done".
Anyone have the same issue? do you guys know how to fix it?
Click to expand...
Click to collapse
More than likely RMM state zip didn't work are you using the version 2 zip and did you allow modifications in twrp before flashing zip files.
@spawnlives; thanks for your repply, I guess that was part of the solution. What I did was to flash a custom kernel plus RMM state bypass v2. I read a custom kernel could fix my problem.
Now I have my phone rooted and with OEM unlock enlabed.
josegon30 said:
@spawnlives; thanks for your repply, I guess that was part of the solution. What I did was to flash a custom kernel plus RMM state bypass v2. I read a custom kernel could fix my problem.
Now I have my phone rooted and with OEM unlock enlabed.
Click to expand...
Click to collapse
what kernel did you use? i have the same issue. i cant reboot on unlocking as i get the dreaded only official binary....
Johnny™ said:
what kernel did you use? i have the same issue. i cant reboot on unlocking as i get the dreaded only official binary....
Click to expand...
Click to collapse
I used Velocity Kernel.
Just follow the steps: 1. flash twrp; 2. factory reset and reboot recovery; 3. flask kernel; 4. flash magisk; 5. flash no verify; 6. flash rmm bypass (v2, not v1).
thanks im really struggling, im on the 11th try, every time is just gives me only official bineries.... , ive tried several methods, all root nicely but wont reboot.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
i cant find the v2 its coming up as 4k where v1 is 100k?
josegon30 said:
I used Velocity Kernel.
Just follow the steps: 1. flash twrp; 2. factory reset and reboot recovery; 3. flask kernel; 4. flash magisk; 5. flash no verify; 6. flash rmm bypass (v2, not v1).
Click to expand...
Click to collapse
let me buy you a beer! got it working thanks, the V2 did the trick. I used your kernel as well just in case. no more nasty red message!
Johnny™ said:
let me buy you a beer! got it working thanks, the V2 did the trick. I used your kernel as well just in case. no more nasty red message!
Click to expand...
Click to collapse
:good: I´m glad it worked.
josegon30 said:
I used Velocity Kernel.
Just follow the steps: 1. flash twrp; 2. factory reset and reboot recovery; 3. flask kernel; 4. flash magisk; 5. flash no verify; 6. flash rmm bypass (v2, not v1).
Click to expand...
Click to collapse
Okay, that's great and all but I can't even do the first step because every time I'm in Download mode and try to flash TWRP with Odin, it says "Only official released binaries are allowed to be flashed (RECOVERY). I have triggered Knox security but I can't undo it now, so I can fix the RMM state with the bypasser because I can't even flash TWRP. It was suggested to change the date to another one, prior to the security patches, but that didn't work. Sad times...
nasko7 said:
Okay, that's great and all but I can't even do the first step because every time I'm in Download mode and try to flash TWRP with Odin, it says "Only official released binaries are allowed to be flashed (RECOVERY). I have triggered Knox security but I can't undo it now, so I can fix the RMM state with the bypasser because I can't even flash TWRP. It was suggested to change the date to another one, prior to the security patches, but that didn't work. Sad times...
Click to expand...
Click to collapse
Depending on .android version, you will need to have the following coditions to be able to flash non signed samsung firmware eg: twrp,root, custom roms etc.
In system - OEM unlocked
Download mode -
RMM status - normal ( or disappeared )
KG status - checking
Otherwise you will get errors
Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?
OEM unlock toggle in Developer's Options
Hi ¡...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers
Hi guys and girls,
I bought a oneplus 7 pro recently and wanted to unlock the bootloader and root it to install the xXx Nolimits mod except I made some errors (I believe I removed too much bloatware with the .profile file, my WIFI and my mobile data were no longer working), so I re-lock the bootloader except that I got this error message: "Your Device is corrupt. It can't be trusted and will not boot", I was scared for a moment but I managed to access the fastboot and re-unlock the bootloader this time to remove everything that was not there in the stock phone and re-lock the bootloader.
I did all the checks after re-locking my bootloader (root check, safety net check, sensor check, Widevine check and stock recovery check).
My question is: is it possible that something has been changed in the low level of android? (I just install TWRP with fastboot, flash Magisk with TWRP and finally flash the xXx nolimits mod).
Thanks for your help !
oops I created another thread by editing my old one. Sorry.
isman77 said:
oops I created another thread by editing my old one. Sorry.
Click to expand...
Click to collapse
Hi
You are going to be flogged! [emoji6]
Envoyé de mon GM1913 en utilisant Tapatalk
isman77 said:
Hi guys and girls,
I bought a oneplus 7 pro recently and wanted to unlock the bootloader and root it to install the xXx Nolimits mod except I made some errors (I believe I removed too much bloatware with the .profile file, my WIFI and my mobile data were no longer working), so I re-lock the bootloader except that I got this error message: "Your Device is corrupt. It can't be trusted and will not boot", I was scared for a moment but I managed to access the fastboot and re-unlock the bootloader this time to remove everything that was not there in the stock phone and re-lock the bootloader.
I did all the checks after re-locking my bootloader (root check, safety net check, sensor check, Widevine check and stock recovery check).
My question is: is it possible that something has been changed in the low level of android? (I just install TWRP with fastboot, flash Magisk with TWRP and finally flash the xXx nolimits mod).
Thanks for your help !
Click to expand...
Click to collapse
Just use MSMtool to reflash your phone. The links are in the guides section
isman77 said:
Hi guys and girls,
I bought a oneplus 7 pro recently and wanted to unlock the bootloader and root it to install the xXx Nolimits mod except I made some errors (I believe I removed too much bloatware with the .profile file, my WIFI and my mobile data were no longer working), so I re-lock the bootloader except that I got this error message: "Your Device is corrupt. It can't be trusted and will not boot", I was scared for a moment but I managed to access the fastboot and re-unlock the bootloader this time to remove everything that was not there in the stock phone and re-lock the bootloader.
I did all the checks after re-locking my bootloader (root check, safety net check, sensor check, Widevine check and stock recovery check).
My question is: is it possible that something has been changed in the low level of android? (I just install TWRP with fastboot, flash Magisk with TWRP and finally flash the xXx nolimits mod).
Thanks for your help !
Click to expand...
Click to collapse
From what I've seen from a few people on here, nolimits doesn't really do anything useful. Debloat a few apps but everything else it doesn't isn't that good, apparently. I used it before and thought it was good. But I'm pretty sure I get better battery and performance on stock with a custom kernel and used something else to debloat.
Also, as some else suggested, MSM tool is great to get back to stock with everything proper.
Thank you for your answers @Jinsuke32 and @GeekMcLeod
I would like to know if you can use MSM Tool with a locked bootloader and does this tool erase all data during flash?
isman77 said:
Thank you for your answers @Jinsuke32 and @GeekMcLeod
I would like to know if you can use MSM Tool with a locked bootloader and does this tool erase all data during flash?
Click to expand...
Click to collapse
Not sure if it can be used with locked bootloader. But it erases everything.
GeekMcLeod said:
Not sure if it can be used with locked bootloader. But it erases everything.
Click to expand...
Click to collapse
Ok, thanks for your quick response.