Related
Hi Evryone.
Because I didn't found CWM or TWRP Recovery or any root method for the galaxy J5 J5108 and the J7 J7108, I made a pre-rooted firmwares for those models.
This firmware base on the hong kong firmware which include the Google apps, this a full firmware exactly like the original, except the root.
After flash you will see the SuperSU app in the app drawer.
Also, this firmware contains the bootloader from the china firmware which doesn't have frp lock.
The root include the binary files in the system, and a pathed boot. (from Android 6.0 or samsung 5.1.1 pathing the boot is necessary for the root work properly)
Flashing this firmware will not wipe data automaticly. you should not lose anything.
This file will work on any firmware/baseband/csc. you can always flash it like a stock firmware.
J5 - base on - J5108ZHU1APD2.
Android version: 5.1.1
J7 - base on - J7108ZHU1APD1.
Android version: 5.1.1
Downloads
J5
http://www.mediafire.com/download/o8hfu81j3j4irjt/J5108ZHU1APD2_Rooted_by_avicohh.exe
J7
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Installation instructions
Before flashing check the CROM Service status in Download mode, if it locked you will need to unlock the bootloader first with the app attached.
Install samsung usb drivers from here.
Download the self extracting 7z file above and extract it (just double tap) to some folder, you should receive a tar.md5 file.
Open odin 3 (attached in the zip)
Put the tar.md5 file in AP.
Put the device in download mode. (vol down + home + power button, and then click on vol up)
Connect your phone to usb and wait for odin detect the device.
Click start.
After it finish choose reboot system now in recovery.
Enjoy.
If you want to thank me for this work, you can do this by donating.. :good:
Thanks a lot avicohh. This was simple and painless. I now have google services on my mainland China phone. And root too! And like you said - I did not loose anything.
well now i am stuck. I enabled my google account, installed and updated my apps through google play, shutdown and now I can't boot. The message in red on the top of the boot screen is:
"KERNEL IS NOT SEANDROID ENFORCING
Custom Binary blocked by FRP lock."
I also cannot reflash the same HK rooted firmware using Odin
apparently I should have enabled developer options then enabled OEM unlocking before rebooting. But I didn't know that so for now I am bricked
Also apparently, the fix for it is to reflash the original firmware using Odin. I am now downloading the firmware from http://updato.com/firmware-archive-select-model?record=1F170CA05E5611E6B055FA163EE8F90B but it is still another 2-3 hours to complete the download (yes, poor internet connection here.)... So I'll see how that goes...
OK, that didn't work. Now the message on the download mode screen says:
SW REV. Invalid type.
FRP is enabled, not allow download non FRP bootloader binary
Well..
I just recently had the same problem in another device.
I don't think the "Oem unlock" has nothing to do with this. the problem is that when you're adding Google account the frp (factroy reset protection) is automaticly enabled, and then it blocks the pathed boot.
The reason reflash the original firmware didn't work for you is because you tried to flash the china version, that doesn't have google service and also doesn't have frp in the bootloader. (apparently once frp is enabled this kind of operation is not allowed because you are actually trying to remove the frp lock by flashing bootloader..)
I think the solution will be to flash the original hong kong firmware with the frp bootloader and original boot. (or just the original boot)
http://updato.com/firmware-archive-select-model?record=5C13445B54D811E6B055FA163EE8F90B
Then, try to enable the "Oem unlock" option and finally flash the rooted firmware again.
maybe it will work, I'm not sure about it but I would like to know.
If this won't work, I'll try to combine the rooted hong kong firmware with the non-frp bootloader from the china firmware.
Thanks so much for replying avicohh
avicohh said:
Well..
The reason reflash the original firmware didn't work for you is because you tried to flash the china version, that doesn't have google service and also doesn't have frp in the bootloader. (apparently once frp is enabled this kind of operation is not allowed because you are actually trying to remove the frp lock by flashing bootloader..)
Click to expand...
Click to collapse
This makes sense. I was actually suspecting this and was considering trying the 6.01 HK version since that is the only one I could find: http://updato.com/firmware-archive-select-model?record=5C13445B54D811E6B055FA163EE8F90B
Now that you've posted a link to your original 5.1 HK firmware I'll try what you suggest. I'll wait to get home before I start the download.
But I still wonder if the 6.01 would work on my phone?
It's a mistake.
This link above is 5.1.1, not 6.0.1.
There is no 6.0.1 fro this model for now.
yes, I see, the website says its 6.01, but its actually 5.1.1. How do I know? BECAUSE IT WORKED!!! It took 7 hours to download but when I got up this morning it was done, I flashed and it worked!!!
I'm going to read up some more on this FRP business before flashing the rooted version again. My old phone (very old) had no such thing. I'd never heard of it till this unpleasant way of learning about it.
downloading
Same problem downloading the stock firmware from http://forum.xda-developers.com/gal...108-how-to-root-galaxy-j7-2016-model-t3426967
I hope this works....
---------- Post added at 12:27 AM ---------- Previous post was at 12:26 AM ----------
Tukuvai said:
Same problem downloading the stock firmware from http://forum.xda-developers.com/gal...108-how-to-root-galaxy-j7-2016-model-t3426967
I hope this works....
Click to expand...
Click to collapse
I meant http://updato.com/firmware-archive-s...55FA163EE8F90B
Hi guys.
Thanks for your replies.
I've just checked it now on another device.
As it turn out after a several tests, this "custom binary blocked by frp lock" problem occurs only if the oem unlock option is disabled.
Here is what I did, step by step:
First, I enabled the oem unlock option and then I added Google account - nothing happened. frp lock in Download mode is still off and everything working fine.
I removed the google account, turned off the oem unlock option and finally added the google account again - frp lock in download mode immediately switch to on, and when I tried to restart, the device has stuck on the boot. (custom binary..)
I flashed stock firmware (from the link above), the device now bootup normally but the frp lock in download mode is still on. (I didn't remove the google account yet)
Final check - I enabled the oem unlock again, and the frp lock in download mode switch to off.
So..
I can safely say that all you need to do is just enable oem unlock in developer options, and then flash the rooted firmware.
Anyway, to be even more sure, I made a new firmware with the china bootloader, frp now is not even exist in download mode.
You can download the new firmware from here
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Good luck!
avicohh said:
Hi guys.
Thanks for your replies.
I've just checked it now on another device.
As it turn out after a several tests, this "custom binary blocked by frp lock" problem occurs only if the oem unlock option is disabled.
Here is what I did, step by step:
First, I enabled the oem unlock option and then I added Google account - nothing happened. frp lock in Download mode is still off and everything working fine.
I removed the google account, turned off the oem unlock option and finally added the google account again - frp lock in download mode immediately switch to on, and when I tried to restart, the device has stuck on the boot. (custom binary..)
I flashed stock firmware (from the link above), the device now bootup normally but the frp lock in download mode is still on. (I didn't remove the google account yet)
Final check - I enabled the oem unlock again, and the frp lock in download mode switch to off.
So..
I can safely say that all you need to do is just enable oem unlock in developer options, and then flash the rooted firmware.
Anyway, to be even more sure, I made a new firmware with the china bootloader, frp now is not even exist in download mode.
You can download the new firmware from here
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Good luck!
Click to expand...
Click to collapse
Hey, How do I enable OEM unlock when I can't even boot my device. it simply refuses to boot.
Hi
First flash the original HK firmware from here. the device should boot up normally.
http://updato.com/firmware-archive-select-model?record=5C13445B54D811E6B055FA163EE8F90B
Then, enable oem unlock.
Thanks for making the root version of mainland firmware. I'm going to stick with the HK version as I want to have google services. and thanks for testing the oem unlock
I informed myself some more about FRP and OEM unlock and I am now feel safe to use the rooted HK firmware. Except, I came across one note for which I want further clarification before proceeding. The note is from http://www.androidcentral.com/factory-reset-protection-what-you-need-know and it says:
"A couple notes need added here. This doesn't undo Samsung's (or anyone else's) version of Reactivation Lock. If you've enabled data reset protection through your Samsung account, you'll need to turn that off in your Security settings. You can find the switch under the "Find My Mobile" section."
So, I want to be sure I don't have this samsung Reactivation Lock enabled. and that I am in no danger of it auto-enabling. I believe I am safe but I would like to know if anyone has more clear information.
What I do know is before I flashed to HK ROM, when I went into download mode, there displayed a setting:
"REACTIVATION LOCK: OFF"
now, using the HK ROM, it is gone, but in that exact same location is the setting:
"FRP LOCK: OFF"
I think, that means the mainland version of the FRP lock (Samsung Reactivation Lock), is now replaced with the google FRP lock and as I don't have to worry about the samsung reactivation lock anymore. Is that so?
even so, as the article says, I look in "Settings" >> "Lock screen and security" >> "Find my mobile" >> log into Samsung Account when prompted, then it does not display the "Reactivation Lock" option that is shown in at least one guide that I found. I really think this is further proof I don't have to worry about Samsung Reactivation Lock. Can anyone confirm?
Yes I can confirm.
But pay attention that because of the FRP, is not possible to make a pre-rooted firmware for Android 6.0 and above or 5.1.1 Samsung devices, from firmware contains FRP protection like the HK one.
From those android versions (and above), a pre-rooted firmware (or any root method) must include a patched kernel.
Due to the FRP protection, once it turn on, it detect the custom kernel (boot) and not allow the device to boot. (custom binary blocked by FRP lock)
That's the reason I had to replace the HK bootloader which contain FRP protection, with the China bootloader which contain the Samsung reactivation lock. (instead of FRP, because china firmwares doesn't include any google services)
I don't know what the policy of the Samsung reactivation lock, about custom kernels.
And also I don't know if the Samsung reactivation lock turns on automaticly if you are adding Samsung account. (Like the FRP lock)
And one more thing, I beleive most people don't use Samsung account at all.
So after all this,
If it come to decision what to use, the FRP lock or the Samsung one (depends only in the bootloader), I'm pretty sure that in this case (custom boot), the best is to use the Samsung lock, and just dont add Samsung account, or add Samsung account if needed but turn off the Reactivation lock in the Find my mobile settings.
I hope it help you a bit.
Good luck.
btw, If you can check the Samsung lock after root and report here, it would be great.
avicohh said:
Anyway, to be even more sure, I made a new firmware with the china bootloader, frp now is not even exist in download mode.
You can download the new firmware from here
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Good luck!
Click to expand...
Click to collapse
Oh, at first I thought you meant you rooted the mainland firmware. Now, based on your later post, I believe what you did was to put the mainland bootloader in the rooted HK firmware. Is this the case? If so, that means I can still have google services, and root, and no possibility of FRP issues because its a mainland bootloader. OK, I will try tonight. The Samsung reactivation lock is off by default. Even adding a Samsung account does not turn it on, you have to go into "find my phone" to turn it on. So it should be safe. I will confirm tonight after I download your new firmware.
Yes, this is exactly what i did.
Thanks for testing the samsung account. so it is pretty safe.
yes, this new version with mainland bootloader is good. It seems almost impossible to lock.
Now when I go to download mode, there is no more "FRP LOCK: OFF". in its place is "REACTIVATION LOCK: OFF".
Just for fun I tested by going inter developer options and turned off OEM unlock - then I tried to reboot = success. Enter download mode = still "REACTIVATION LOCK: OFF". Of course I turned it back on again after the test.
and in settings, find my mobile, there is still not a setting for "REACTIVATION LOCK". I have seen an example on the web that this reactivation lock setting should be at the bottom of the options under find my mobile. So, actually now I cannot find any way to turn on the reactivation lock - this is good, its what we want.
Of course to even enter the "find my mobile" section I can do nothing at all (in fact it does not even show me what the options are) untill I give my samsung account credentials. Once I give credentials I can see the options but there is no option to turn on reactivation lock. There is just one thing, maybe, is that in "find my mobile", there a place that says: for more information go to findmymobile.samsung.com. When I go there I have 2 options:
-1) FIND - Find, Lock, Wipe my device
-2) PREPARE - Ready device for Find my Mobile
this "prepare" option I am afraid to try, I am afraid it may be the one to enable reactivation lock. Clearly it is not required to actually find my mobile because I just click the "Find" button and it it finds it for me. So, what would be the use of "prepare"?
At any rate, we know that just creating a samsung account does not activate the lock. I never had a Samsung account before. When I set up this new phone I never did enter developer mode to turn on oem unlock but i did create the samsung account. It was after that I flashed version 1 of avicohh's rooted firmware and when I went into download mode, it said REACTIVATION LOCK: OFF, so creating the Samsung account does not turn it on.
avicohh said:
Hi Evryone.
Because I didn't found CWM or TWRP Recovery or any root method for the galaxy J5 J5108 and the J7 J7108, I made a pre-rooted firmwares for those models.
This firmware base on the hong kong firmware which include the Google apps, this a full firmware exactly like the original, except the root.
After flash you will see the SuperSU app in the app drawer.
Also, this firmware contains the bootloader from the china firmware which doesn't have frp lock.
The root include the binary files in the system, and a pathed boot. (from Android 6.0 or samsung 5.1.1 pathing the boot is necessary for the root work properly)
Flashing this firmware will not wipe data automaticly. you should not lose anything.
This file will work on any firmware/baseband/csc. you can always flash it like a stock firmware.
J5 - base on - J5108ZHU1APD2.
Android version: 5.1.1
J7 - base on - J7108ZHU1APD1.
Android version: 5.1.1
Downloads
J5
http://www.mediafire.com/download/o8hfu81j3j4irjt/J5108ZHU1APD2_Rooted_by_avicohh.exe
J7
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Installation instructions
Before flashing check the CROM Service status in Download mode, if it locked you will need to unlock the bootloader first with the app attached.
Install samsung usb drivers from here.
Download the self extracting 7z file above and extract it (just double tap) to some folder, you should receive a tar.md5 file.
Open odin 3 (attached in the zip)
Put the tar.md5 file in AP.
Put the device in download mode. (vol down + home + power button, and then click on vol up)
Connect your phone to usb and wait for odin detect the device.
Click start.
After it finish choose reboot system now in recovery.
Enjoy.
If you want to thank me for this work, you can do this by donating.. :good:
Click to expand...
Click to collapse
sir, you are awesome!!
I'll try to install in my J5108. I will give to my daughter. Is there a form to unroot the phone? Thanks!
Yes.
Just install stock rom.
http://updato.com/firmware-archive-select-model?record=A097D215549D11E6B055FA163EE8F90B
I have an unlocked SM-G965F/DS (Exynos) that has not shown the OEM unlock option yet. Tried:
Installing active SIM
Logging in to Google and Samsung accounts, then
Leaving the phone online for 170 hours (uptime reached ~175 hours)
I see a few other threads on the SM-G965F/DS, also indicating no OEM unlock appeared. Has anyone actually gotten the SM-G965F/DS to show an OEM unlock option?
Firmware and hardware versions:
Hardware: SM-G965FZBDXSP
CSC code: XSP
Botloader: G965FXXU1BRE6
CSC: G965FOXM1BRE6
Android Build Number: R16NW.G965FXXU1BRE6
EDIT:
Bootloader shows:
Model: G965F
RMM State: Prenormal
FRP Lock: ON
OEM Lock: ON
Is only the single-SIM 965F unlockable? Is there a recommended dual-SIM model in case I end up just sending this one back?
Appreciate any help you guys can provide!
whitepines said:
Is only the single-SIM 965F unlockable? Is there a recommended dual-SIM model in case I end up just sending this one back?
Appreciate any help you guys can provide!
Click to expand...
Click to collapse
Mines dual sim, had oem unlock after the 7 day wait.
sent from my Exynos S9 plus, Pixel 2 XL or Note FE
force70 said:
Mines dual sim, had oem unlock after the 7 day wait.
sent from my Exynos S9 plus, Pixel 2 XL or Note FE
Click to expand...
Click to collapse
Great, thank you for the data point. Do you happen to know the CSC and stock firmware version you had installed when the OEM unlock appeared? If I don't see the option after another 7 days I intend to ODIN over a known good CSC / firmware version.
whitepines said:
Great, thank you for the data point. Do you happen to know the CSC and stock firmware version you had installed when the OEM unlock appeared? If I don't see the option after another 7 days I intend to ODIN over a known good CSC / firmware version.
Click to expand...
Click to collapse
My CSC is EGY (egypt) but no idea what the original firmware was when i got it
Mine is a S9+ dual sim and has OEM unlock
Vadwiser said:
Mine is a S9+ dual sim and has OEM unlock
Click to expand...
Click to collapse
do i need to have an active sim card in my phone to oem unlock? feeling like i wasted the last 3 days by not having one inserted. thanks in advance
this.guy.lol said:
do i need to have an active sim card in my phone to oem unlock? feeling like i wasted the last 3 days by not having one inserted. thanks in advance
Click to expand...
Click to collapse
Lol, why wouldnt you have one inserted?
sent from my Exynos S9 plus, Pixel 2 XL or Note FE
force70 said:
Lol, why wouldnt you have one inserted?
sent from my Exynos S9 plus, Pixel 2 XL or Note FE
Click to expand...
Click to collapse
because i have a oneplus 6 i am using. and because i require root. i dont use devices that are not rooted.
Did finally get it working. My device originally came with RMM prenormal, FRP lock off, OEM lock on. Setting up the phone normally and inserting a SIM, then waiting 7 days, did NOT work. I suspect the phone was in an abnormal state due to a partial setup by the prior owner / reseller.
What did the trick for me was to force reset the phone (lose all data) via the settings menu, have a SIM inserted, go through the full setup process (Google and Samsung accounts), then leave the phone on for 7 days. The reset caused RMM prenormal, FRP lock on, OEM lock on. After 168 hours the OEM unlock option appeared in the developer settings menu.
A little guidance here. I've only dealt with Google Nexus devices and the OnePlus One, which were ridiculously easy to unlock and put on a custom ROM. I'm currently running (yes, still) a Nexus 6P because there hasn't been a phone that really interests me. I do like the S9+, and can get a good price on a BNIB SM-G965F/DS. I just want to run AOSP on it, no frills, no thrills, just vanilla. That's how I roll. So, I'll need to unlock the bootloader, install TWRP, and load up a new ROM.
With that said, all that I've read, I'm a little confused. I use t-mobile, so will I need to put in the t-mobile sim for 7 days to get OEM unlock, or will I need this done in an EU country (it is an EU version) due to the region locking Samsung has been doing since 2013? There just seems to be a lot of competing and incomplete information all over the damned place.
And don't tell me to search, please. I've been around on this forum long enough to know how to search, and long enough to know that search doesn't always yield the results you're looking for. So, if you have a link to a more descriptive explanation of what to do/expect, I'd be grateful.
Thanks.
EDIT: Found this: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Maybe that would work... but still don't understand if I need it activated on an EU SIM first.. Now I remember why I've avoided Samsung devices...
stewa2jm said:
A little guidance here. I've only dealt with Google Nexus devices and the OnePlus One, which were ridiculously easy to unlock and put on a custom ROM. I'm currently running (yes, still) a Nexus 6P because there hasn't been a phone that really interests me. I do like the S9+, and can get a good price on a BNIB SM-G965F/DS. I just want to run AOSP on it, no frills, no thrills, just vanilla. That's how I roll. So, I'll need to unlock the bootloader, install TWRP, and load up a new ROM.
With that said, all that I've read, I'm a little confused. I use t-mobile, so will I need to put in the t-mobile sim for 7 days to get OEM unlock, or will I need this done in an EU country (it is an EU version) due to the region locking Samsung has been doing since 2013? There just seems to be a lot of competing and incomplete information all over the damned place.
And don't tell me to search, please. I've been around on this forum long enough to know how to search, and long enough to know that search doesn't always yield the results you're looking for. So, if you have a link to a more descriptive explanation of what to do/expect, I'd be grateful.
Thanks.
EDIT: Found this: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Maybe that would work... but still don't understand if I need it activated on an EU SIM first.. Now I remember why I've avoided Samsung devices...
Click to expand...
Click to collapse
Been a month and no oem unlock for me... Tried all the time trick settings and factory reset plus more time changing... I am not using a sin on this phone because I have a work phone... Why so much bs just for oem unlock?
IparryU said:
Been a month and no oem unlock for me... Tried all the time trick settings and factory reset plus more time changing... I am not using a sin on this phone because I have a work phone... Why so much bs just for oem unlock?
Click to expand...
Click to collapse
Oem unlock isnt gonna do anything for the device. Its kind of pointless to do for now.
HELP! OEM Unlock came up after 7 days. I turned it on, and it said that doing so will erase data... yadda yadda, and then it restarted, wiped, and then rebooted. ... No OEM Unlock in the menu anymore and back to RMM STATE: Prenormal.
WTF??
stewa2jm said:
HELP! OEM Unlock came up after 7 days. I turned it on, and it said that doing so will erase data... yadda yadda, and then it restarted, wiped, and then rebooted. ... No OEM Unlock in the menu anymore and back to RMM STATE: Prenormal.
WTF??
Click to expand...
Click to collapse
Multiple guides to either TWRP/root or ROM s9+ involve manually restarting the phone BEFORE samsung auto restarts your phone.
In other words, don't let the force restart from samsung go through, and manually restart it the moment you press OK to factory wipe and restart
EDIT: also make sure you have signed out of google before going into DL mode to TWRP phone, as this does the "FRP lock" from what I personally understand and Odin won't let you TWRP with FRP lock on. This was my 2nd mistake (and second 7-day lockout). First mistake was what you did, by letting samsung beat you at restarting phone.
jujubeans said:
Multiple guides to either TWRP/root or ROM s9+ involve manually restarting the phone BEFORE samsung auto restarts your phone.
In other words, don't let the force restart from samsung go through, and manually restart it the moment you press OK to factory wipe and restart
EDIT: also make sure you have signed out of google before going into DL mode to TWRP phone, as this does the "FRP lock" from what I personally understand and Odin won't let you TWRP with FRP lock on. This was my 2nd mistake (and second 7-day lockout). First mistake was what you did, by letting samsung beat you at restarting phone.
Click to expand...
Click to collapse
Thanks. I got through it all a while back now. You have to be lightning quick. So dumb. This will most likely be my last Samsung device. There are other options that are much less hassle to do this work on.
I've got a G965F that I've just updated to 9.0 (CSA1).
After setting up my phone I went into developer options, switched on OEM unlock and reset my phone.
Even after doing this, I still have a prenormal RMM state, however my FRP and OEM lock are both "off".
Has anyone experienced this, or know a workaround?
Or do I have to still wait 7 days?
brodyamc said:
I've got a G965F that I've just updated to 9.0 (CSA1).
After setting up my phone I went into developer options, switched on OEM unlock and reset my phone.
Even after doing this, I still have a prenormal RMM state, however my FRP and OEM lock are both "off".
Has anyone experienced this, or know a workaround?
Or do I have to still wait 7 days?
Click to expand...
Click to collapse
No workaround, wait 7 days. If you're lucky, it will clear. Depending on where you bought the phone, this might never clear though.
brodyamc said:
I've got a G965F that I've just updated to 9.0 (CSA1).
After setting up my phone I went into developer options, switched on OEM unlock and reset my phone.
Even after doing this, I still have a prenormal RMM state, however my FRP and OEM lock are both "off".
Has anyone experienced this, or know a workaround?
Or do I have to still wait 7 days?
Click to expand...
Click to collapse
Downgrade to oreo then wait 7 days after that you get normal Rmm
Joad said:
Downgrade to oreo then wait 7 days after that you get normal Rmm
Click to expand...
Click to collapse
In my understanding, it's not necessary to downgrade to Oreo for it to clear after 7 days. If it won't clear on Pie, then it won't clear on Oreo either. If in Oreo, it was clearing for OP and OEM unlock was appearing after 7 days, then the RMM prenormal will also clear in Pie.
daviddema said:
In my understanding, it's not necessary to downgrade to Oreo for it to clear after 7 days. If it won't clear on Pie, then it won't clear on Oreo either. If in Oreo, it was clearing for OP and OEM unlock was appearing after 7 days, then the RMM prenormal will also clear in Pie.
Click to expand...
Click to collapse
Ok my bad then cause i heard you have to be on oreo to get normal RMM state .
daviddema said:
In my understanding, it's not necessary to downgrade to Oreo for it to clear after 7 days. If it won't clear on Pie, then it won't clear on Oreo either. If in Oreo, it was clearing for OP and OEM unlock was appearing after 7 days, then the RMM prenormal will also clear in Pie.
Click to expand...
Click to collapse
When I was on Oreo, the OEM unlock option wasn't even there no matter how much uptime I had etc.
But straight away on Pie the option was there.
brodyamc said:
When I was on Oreo, the OEM unlock option wasn't even there no matter how much uptime I had etc.
But straight away on Pie the option was there.
Click to expand...
Click to collapse
That's correct, but even though the option is there immediately on Pie, RMM state is still prenormal in download mode, and therefore still unable to flash non official binaries in Odin. In Pie there is also a "KG state : checking" line in download mode. I think KG stands for Knox Guard (guessing only). Anyone's guess what that is for... complete opacity on the Samsung side...
Where did you buy your phone? Please post your csc codes in settings -> about phone -> software information -> service provider SW version
daviddema said:
That's correct, but even though the option is there immediately on Pie, RMM state is still prenormal in download mode, and therefore still unable to flash non official binaries in Odin. In Pie there is also a "KG state : checking" line in download mode. I think KG stands for Knox Guard (guessing only). Anyone's guess what that is for... complete opacity on the Samsung side...
Where did you buy your phone? Please post your csc codes in settings -> about phone -> software information -> service provider SW version
Click to expand...
Click to collapse
Bought my phone in NZ, but I've since flashed the Australian pie update (TEL).
Not sure how much info you want from SW version, so here's all of it:
SAOMC_SM-G965F_OXM_TNZ_PP_0008
22b4d3d424027ece
TNZ/TNZ/TNZ
brodyamc said:
Bought my phone in NZ, but I've since flashed the Australian pie update (TEL).
Not sure how much info you want from SW version, so here's all of it:
SAOMC_SM-G965F_OXM_TNZ_PP_0008
22b4d3d424027ece
TNZ/TNZ/TNZ
Click to expand...
Click to collapse
I can only guess that NZ phones are locked also then... if you can, check the phones of some of your friends in download mode and see whether they have the RMM prenormal and/or KG checking lines.
daviddema said:
I can only guess that NZ phones are locked also then... if you can, check the phones of some of your friends in download mode and see whether they have the RMM prenormal and/or KG checking lines.
Click to expand...
Click to collapse
Hello and what about my phone plz ?
rafik25 said:
Hello and what about my phone plz ?
Click to expand...
Click to collapse
You bought your phone in Germany and use it with a UK SIM I think?
As far as I know, European phones don't have that problem. Your prenormal mode should clear in 7 days. Check it in download mode, if it says RMM state prenormal, then it's locked. If it doesn't say RMM prenormal, you're good to flash whatever you want.
daviddema said:
You bought your phone in Germany and use it with a UK SIM I think?
As far as I know, European phones don't have that problem. Your prenormal mode should clear in 7 days. Check it in download mode, if it says RMM state prenormal, then it's locked. If it doesn't say RMM prenormal, you're good to flash whatever you want.
Click to expand...
Click to collapse
Yes i bought it in eBay.de. this is the lastest firmware....
In fact im leaving in France i tried several Times with lastest XEF Oreo and pie firmware but Always the same issues with prenormal state still full 168h ?
daviddema said:
I can only guess that NZ phones are locked also then... if you can, check the phones of some of your friends in download mode and see whether they have the RMM prenormal and/or KG checking lines.
Click to expand...
Click to collapse
Well I checked my friend's S9+ (of same model etc.); the RMM status wasn't there and his device status was Custom.
He says he hasn't rooted etc., and I believe him as he wouldn't even know what to do.
Either way it doesn't change anything haha, I'll just wait the remaining 5 days and hope for the best :good:
Just waited my 168 hours and my RMM state is still prenormal.
Bit unfortunate.
Edit: I restarted a couple times and my RMM state had disappeared from download mode and I was able to flash TWRP!
daviddema said:
In my understanding, it's not necessary to downgrade to Oreo for it to clear after 7 days. If it won't clear on Pie, then it won't clear on Oreo either. If in Oreo, it was clearing for OP and OEM unlock was appearing after 7 days, then the RMM prenormal will also clear in Pie.
Click to expand...
Click to collapse
I had no issues with RMM or OEM Unlock on the 9650 8.0, since moving to Pie, RMM won't clear and OEM Unlock option disappeared.
Downgrade to the newest 8.0 firmware you can, switch OFF OEM Unlock, Update to Pie, then switch OEM Unlock back on and wait the 7 day waiting period for RMM - This in theory should solve the issue as long as your model is able to be unlocked and root compatible.
Hope this clears up your understanding!
I have a strange issue I have unlocked my bootloader g965f exynos variant but my kg state says checking what does this mean ?? But I still have oem unlock option available
RMM STATUS is always Prenormal. KG STATUS is Checking. Why?
Has anyone had any success clearing the RMM prenormal flag? I've waited 7 days but it didn't work. OEM unlock is enabled in developer options and KG state is checking.
I have bought a 2nd hand s9 plus and I discovered it might be a sample/test device (CSC is EGY/EGY/SMP) Everything is working (Samsung account, Knox, fingerprints, etc...) but I am afraid it can be locked or something remotely anytime.
Should I be worried? I have installed the latest Pie update from Odin but my RMM state stayed prenormal even after 7 days uptime.
Note:
My download mode has a strange line
Eng mode : Eng allowed (someone name...)
I didn't see anything like that in any download mode.
Any help will be greatly appreciated.
Hi i searching hours for hours but don't get the firmware on this phone I have Odin, switch... From Samsung the newest firmware 5 pieces, adb, pipfile, actually drivers different cables and so one the biggest brob is developing mode is not acktiv I got this handy from my download junky grandma I don't know what crashed the phone a fouled try of flashing, a virus no idea sorry my English isn't so good at writing it on my own x.x but I understand 95% last 5% goggle helps the 2 pictures the first one is all time there power+vol. Combo only restart Handy back to same error invalid magic if I try to go in the recovery mode it only get the second picture and stuck on it. Power off key press alone does nothing
1 picture bootload fail, invalid magic
2 picture Odin mode, download speed fast, current binary Samsung official,
KG State broken,
FAP lock off
OEM lock on
Secure download enabled
Sales code Cid Aid /DBT EUX
Warrenty Void 0(0x000)
AP SWREV B7 K7 S7
Did 200.........
CARRIER ID EUX
CHIP ID and CHIP ID SJtag same value
Hope someone can help me out thx for coop mode ^^
Try to download the original phone firmware from samfw
marcmax01 said:
Hi i searching hours for hours but don't get the firmware on this phone I have Odin, switch... From Samsung the newest firmware 5 pieces, adb, pipfile, actually drivers different cables and so one the biggest brob is developing mode is not acktiv I got this handy from my download junky grandma I don't know what crashed the phone a fouled try of flashing, a virus no idea sorry my English isn't so good at writing it on my own x.x but I understand 95% last 5% goggle helps the 2 pictures the first one is all time there power+vol. Combo only restart Handy back to same error invalid magic if I try to go in the recovery mode it only get the second picture and stuck on it. Power off key press alone does nothing
1 picture bootload fail, invalid magic
2 picture Odin mode, download speed fast, current binary Samsung official,
KG State broken,
FAP lock off
OEM lock on
Secure download enabled
Sales code Cid Aid /DBT EUX
Warrenty Void 0(0x000)
AP SWREV B7 K7 S7
Did 200.........
CARRIER ID EUX
CHIP ID and CHIP ID SJtag same value
Hope someone can help me out thx for coop mode ^^
Click to expand...
Click to collapse
having the same issue and i dont know what caused it, did you get it fixed ?
helo sir
plz help me
I think the phone is dead :/
I don't think you can revive it...