I've had a situation where RMM state has always been prenormal and OEM unlock been absent for months on Oreo. After updating to Pie, OEM unlock appeared immediately on first boot, but RMM state prenormal was still there and flashing twrp give me the " only official binaries are allowed to be flashed". Waiting again for 7 days didn't help. The same happens when flashing Samsung combination ROM ( OEM appears, but in download mode RMM lock is still there). After posting about my situation, I've found many users with the same problem wether here or on other Samsung devices forums.
I was hoping for such users to gather here and offer what they can to find any possible solution
Things I've tried untill now:
1- waiting for 7 days with Samsung and Google accounts logged in and SIM from my country put in place; didn't work.
2- flashing complete full stock oreo and waiting again ; didn't work.
3- changing date backwards and forwards trick; didn't work
4- Using miracle box to reset EE reactivation lock; didn't work.
5- factory resetting; didn't work.
6- I used ADB to uninstall rlc and kgclient apps; didn't work.
7- flashing combination file sometimes made OEM toggle appear, but RMM state still is prenormal.
8- I tried two different carriers both from my country and it didn't work. @dames0701 reports that he did the same with all the carriers in his country and got same result.
9- I've contacted Samsung customer service and they are either ignorant of the problem or don't have a fix.
I'll start this bounty with 10 $ which is very little, but hopefully with donations from different users across Samsung devices forums it becomes a significant sum
Edit : I withdraw my donation as I sold my phone, but I'll leave the thread for someone to find a solution one day.
I'm willing to beta test whatever solution anybody thinks it might work, My device is SM-G965F dual SIM.
Cheers...
Sent from my SM-G965F using Tapatalk
My experience
Solution of prenormal RMM security mode
Insert SIM compatible with a country of a device
Format the device
or
Install software
Did you wait for 7 days or did you use the time changing trick?
Sent from my SM-G965F using Tapatalk
I'm on prenormal too considering selling it and getting sony xz2. I regret selling xz premium. Plus really bad ram management samsung has
I'm coming from Sony too, xz1 to be specific, and I still believe that it felt snappier than S9. I was considering trading it with xz2, but the beautiful Amoled display on S9 is the reason why I reconsidered.
amakuramio said:
I'm on prenornal too considering selling it and getting sony xz2. I regret selling xz premium.
Click to expand...
Click to collapse
Sent from my SM-G965F using Tapatalk
ASMstudent said:
I'm coming from Sony too, xz1 to be specific, and I still believe that it felt snappier than S9. I was considering trading it with xz2, but the beautiful Amoled display on S9 is the reason why I reconsidered.
Sent from my SM-G965F using Tapatalk
Click to expand...
Click to collapse
I got it because of the low 1.7 aperture selfie which portrays faces beautifully
Thats all . Lol
https://www.google.com/amp/s/www.ubreakifix.com/blog/best-front-facing-camera-best-selfie/amp
any news plz ?
rafik25 said:
any news plz ?
Click to expand...
Click to collapse
Read the thread, that's the news
Flash combination rom, then newest stock firmware, then custom recovery. That's simply it. Works like a charm.. already did that two times..
fattymcdirty said:
Flash combination rom, then newest stock firmware, then custom recovery. That's simply it. Works like a charm.. already did that two times..
Click to expand...
Click to collapse
can u explain with ore details plz thx for advance :fingers-crossed:
Samsung apps won't work and shows this error as if my device has been rooted. Maybe it has something to do with rmm being always prenormal View attachment 4695986
Sent from my SM-G965F using Tapatalk
ASMstudent said:
I've had a situation where RMM state has always been prenormal and OEM unlock been absent for months on Oreo. After updating to Pie, OEM unlock appeared immediately on first boot, but RMM state prenormal was still there and flashing twrp give me the " only official binaries are allowed to be flashed". Waiting again for 7 days didn't help. The same happens when flashing Samsung combination ROM ( OEM appears, but in download mode RMM lock is still there). After posting about my situation, I've found many users with the same problem wether here or on other Samsung devices forums.
I was hoping for such users to gather here and offer what they can to find any possible solution
Things I've tried untill now:
1- waiting for 7 days with Samsung and Google accounts logged in and SIM from my country put in place; didn't work
2- flashing complete full stock oreo and waiting again ; didn't work
3- changing date backwards and forwards trick; didn't work
4- Using miracle box to reset EE reactivation lock; didn't work
5- factory resetting; didn't work
6- I've contacted Samsung customer service and they are either ignorant of the problem or don't have a fix
I'll start this bounty with 10 $ which is very little, but hopefully with donations from different users across Samsung devices forums it becomes a significant sum
I'm willing to beta test whatever solution anybody thinks it might work, My device is SM-G965F dual SIM.
Cheers...
Sent from my SM-G965F using Tapatalk
Click to expand...
Click to collapse
Hi Op. I thought I was the only one conducting the various tests as you did. Just to add a few extra things I have tried. As my country has various carriers, I bought a simcard from each. Flashed my phone with the manufacturer suggested firmware, signed in on all my accounts and left the phone on in the cupboard for 7days. This was done with oreo and Pie respectively. I went the combination file root to with no luck. My friend bought a brand new s9+ on the same day I asked if I can check it out. I discovered the following: out the box he had android oreo: Apon activating developer options his oem toggle was there. When I restarted his phone into download mode is RMM state was normal. He didn't even have to wait 7days. I took a screen shot of all his firmware and downloaded it and inserted the same carrier simcard as he had. I proceeded to flash the firmware oreo (I was on pie). I booted up just to have my oem toggle gone again. Although my BL was unlocked (done like you, when in installed pie). I booted into download mode and RMM stated was prenormal. I got a feeling our phones just don't check all the boxes for the RMM people at Samsung to send the RMM state change request.
Sent from my SM-G965F using Tapatalk
dames0701 said:
Hi Op. I thought I was the only one conducting the various tests as you did. Just to add a few extra things I have tried. As my country has various carriers, I bought a simcard from each. Flashed my phone with the manufacturer suggested firmware, signed in on all my accounts and left the phone on in the cupboard for 7days. This was done with oreo and Pie respectively. I went the combination file root to with no luck. My friend bought a brand new s9+ on the same day I asked if I can check it out. I discovered the following: out the box he had android oreo: Apon activating developer options his oem toggle was there. When I restarted his phone into download mode is RMM state was normal. He didn't even have to wait 7days. I took a screen shot of all his firmware and downloaded it and inserted the same carrier simcard as he had. I proceeded to flash the firmware oreo (I was on pie). I booted up just to have my oem toggle gone again. Although my BL was unlocked (done like you, when in installed pie). I booted into download mode and RMM stated was prenormal. I got a feeling our phones just don't check all the boxes for the RMM people at Samsung to send the RMM state change request.
Sent from my SM-G965F using Tapatalk
Click to expand...
Click to collapse
Waiting 7 days never changed a thing for me; not OEM toggle, RMM state or KG state.
Sent from my SM-G965F using Tapatalk
ASMstudent said:
Waiting 7 days never changed a thing for me; not OEM toggle, RMM state or KG state.
Sent from my SM-G965F using Tapatalk
Click to expand...
Click to collapse
Same here. I was hoping that mericlebox would work. I tried it on pie and oreo no luck. I even checked to see if my imei number was blacklisted and it's not. Ahh I want root
Sent from my SM-G965F using Tapatalk
Miracle Box is only works for Galaxy J7 Pro with Android 8.1.0, I have tested it on J7 Pro SM-J730G
redymedan said:
Miracle Box is only works for Galaxy J7 Pro with Android 8.1.0, I have tested it on J7 Pro SM-J730G
Click to expand...
Click to collapse
Thank you for the info, it is a pity.
Any other ideas anyone?
Sent from my SM-G965F using Tapatalk
ASMstudent said:
Waiting 7 days never changed a thing for me; not OEM toggle, RMM state or KG state.
Click to expand...
Click to collapse
Not sure if your aware of it but have you tried flashing the RMM State bypass zip
The rmm state effects a few models not just the s9.
This is from the S8 forums
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
This is a bit more info about how the bypass zip works and the zip file which has to be flashed via twrp.
https://forum.xda-developers.com/sa...nuary-security-patch-sm-t3739225/post75360965
As for the OEM unlock in developer menu the date method works for me although I had to come up with a different variation to the date method.
With things like Shealth and secure folder not working is more due to you tripping your Knox and not root.
Hope this is of some help
Hehe, I just had a situation like yours - waiting week, two, no OEM. I've seen all those 'back 7 days' methods and NEVER got them to work for me, but this time I was pretty desperate.
Well.... it worked. Here is what I did, which is basically a mix of stuff from various threads.
Finish FULL setup (with all the apks downloaded and updated)
Enable Dev Settings
Disable Automatic Updates in dev menu
Disable time and date update
Go to date and set it back 7 days
Go to update, disable automatic updates and check for new updates
Restart your device into stock recovery and clear cache
Restart back to system and set the date again 7 days backwards
Restart your device once again
Restore automatic time settings (which will set up the actual date), check for updates
Check if OEM toggle is showing, if not restart once again
Check if OEM toggle is showing, if not - wait 5min, check again
Repeat until you get this to work. Good luck mate!
spawnlives said:
Not sure if your aware of it but have you tried flashing the RMM State bypass zip
The rmm state effects a few models not just the s9.
This is from the S8 forums
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
This is a bit more info about how the bypass zip works and the zip file which has to be flashed via twrp.
https://forum.xda-developers.com/sa...nuary-security-patch-sm-t3739225/post75360965
As for the OEM unlock in developer menu the date method works for me although I had to come up with a different variation to the date method.
With things like Shealth and secure folder not working is more due to you tripping your Knox and not root.
Hope this is of some help
Click to expand...
Click to collapse
I can't install twrp because the device blocks any unofficial binaries from being flashed ,and no I haven't tripped Knox.
Sent from my SM-G965F using Tapatalk
NekoOtoko said:
Hehe, I just had a situation like yours - waiting week, two, no OEM. I've seen all those 'back 7 days' methods and NEVER got them to work for me, but this time I was pretty desperate.
Well.... it worked. Here is what I did, which is basically a mix of stuff from various threads.
Finish FULL setup (with all the apks downloaded and updated)
Enable Dev Settings
Disable Automatic Updates in dev menu
Disable time and date update
Go to date and set it back 7 days
Go to update, disable automatic updates and check for new updates
Restart your device into stock recovery and clear cache
Restart back to system and set the date again 7 days backwards
Restart your device once again
Restore automatic time settings (which will set up the actual date), check for updates
Check if OEM toggle is showing, if not restart once again
Check if OEM toggle is showing, if not - wait 5min, check again
Repeat until you get this to work. Good luck mate!
Click to expand...
Click to collapse
Since updating to pie OEM toggle appears by itself from first boot and I have it already enabled. The problem is RMM state not OEM toggle.
Sent from my SM-G965F using Tapatalk
Related
I have a brand new sealed Samsung S9 SM-G960F/DS which is most probably Exynos variant however I couldn't find OEM Unlock after activating the developer tools. I've googled that and was surprised that this is a recent Samsung policy and as mentioned by most users they've waited more than 7 days to see OEM Unlock so they can root the device. Any one was able to find an alternative or workaround solution instead of waiting 7 days since I don't have that much time to wait I need to root urgently before a birthday.
Your help much appreciated.
Nope, wait the 7 days
My G960F had OEM unlock available on day 1, check in download mode it is the model you think
Flashing Firmware
*Detection* said:
Nope, wait the 7 days
My G960F had OEM unlock available on day 1, check in download mode it is the model you think
Click to expand...
Click to collapse
Do you think flashing a new firmware will show the OEM lock?
c05338 said:
Do you think flashing a new firmware will show the OEM lock?
Click to expand...
Click to collapse
Factory resetting resets the 7 day timer, switching CSCs requires a reset, you'll have to wait it out
*Detection* said:
Factory resetting resets the 7 day timer, switching CSCs requires a reset, you'll have to wait it out
Click to expand...
Click to collapse
I'll wait but actually I don't have much time I should finish it before Monday and today is Saturday so far it's 25 hours up so I'm yet searching for a solution. Anyway to root the device without OEM unlock?
c05338 said:
I'll wait but actually I don't have much time I should finish it before Monday and today is Saturday so far it's 25 hours up so I'm yet searching for a solution. Anyway to root the device without OEM unlock?
Click to expand...
Click to collapse
No solution, read the forums, you cannot root without it, you have to wait no matter how many times you ask
c05338 said:
I have a brand new sealed Samsung S9 SM-G960F/DS which is most probably Exynos variant however I couldn't find OEM Unlock after activating the developer tools. I've googled that and was surprised that this is a recent Samsung policy and as mentioned by most users they've waited more than 7 days to see OEM Unlock so they can root the device. Any one was able to find an alternative or workaround solution instead of waiting 7 days since I don't have that much time to wait I need to root urgently before a birthday.
Your help much appreciated.
Click to expand...
Click to collapse
flash a combination ROM and oem unlock shows since first moment, unlock and flash the normal firmware that you want.
acabreram said:
flash a combination ROM and oem unlock shows since first moment, unlock and flash the normal firmware that you want.
Click to expand...
Click to collapse
Are you sure man? Any wrong stop will cause me issues to reset the time and wait another 7 days and I'm in an urgent time.
c05338 said:
Are you sure man? Any wrong stop will cause me issues to reset the time and wait another 7 days and I'm in an urgent time.
Click to expand...
Click to collapse
http://www.techzai.com/combination-rom-galaxy-devices/
I found this link to download Combination ROM does it fit?
c05338 said:
http://www.techzai.com/combination-rom-galaxy-devices/
I found this link to download Combination ROM does it fit?
Click to expand...
Click to collapse
A member tested the combination ROM theory yesterday for the same purpose and it bootlooped their phone
The combination ROM will allow you to "OEM unlock" your device, but the RMM prenormal state will prevent you from flashing anything custom. I tried this when I first got my S9.
You need to wait the 7 days on stock in order to be able to actually bootloader unlock your device. Make sure to keep a SIM card in, connect a Samsung and Google account, and don't power it off. There is no workaround for this.
*Detection* said:
A member tested the combination ROM theory yesterday for the same purpose and it bootlooped their phone
Click to expand...
Click to collapse
that's me LOL
if we can get it to boot up on s9/ plus
then the oem lock thing wouldn't be an issue
TheUndertaker21 said:
that's me LOL
if we can get it to boot up on s9/ plus
then the oem lock thing wouldn't be an issue
Click to expand...
Click to collapse
Wonder if it was because the combination ROM firmware is older than the current on the device
Did it factory reset after the flash? If not that might be causing the bootloop, or if the bootloader version is older on combination
*Detection* said:
Wonder if it was because the combination ROM firmware is older than the current on the device
Did it factory reset after the flash? If not that might be causing the bootloop, or if the bootloader version is older on combination
Click to expand...
Click to collapse
i mean i'm on ARD6 and i don't think there's any combination for this firmware
i flashed the latest combination i found on many times
TheUndertaker21 said:
i mean i'm on ARD6 and i don't think there's any combination for this firmware
i flashed the latest combination i found on many times
Click to expand...
Click to collapse
The way to check the bootloader is here
G960FXXU1BRE5
Version 1
If you boot into Download mode it should say at the bottom BL:1 or whatever version you are currently running, downgrading the BL is usually not possible from what I see lately
*Detection* said:
The way to check the bootloader is here
G960FXXU1BRE5
Version 1
If you boot into Download mode it should say at the bottom BL:1 or whatever version you are currently running, downgrading the BL is usually not possible from what I see lately
Click to expand...
Click to collapse
this is my version
but i flashed this one
COMBINATION_OXM_FA80_G965FXXU1ARB4_OXMFAC
and
COMBINATION_OXM_FA80_G965FXXU1ARB7_OXMFAC_CL13084894_QB17151834
COMBINATION_OXM_FA80_G965FXXU1ARC3
Bootloader version 1 for both yours and the comb'n firmware so doesn't seem to be that
Did you factory reset after flashing combination? That's the only thing I can think of that would cause the loop if you didn't
*Detection* said:
Bootloader version 1 for both yours and the comb'n firmware so doesn't seem to be that
Did you factory reset after flashing combination? That's the only thing I can think of that would cause the loop if you didn't
Click to expand...
Click to collapse
yeah i factory reset it after still nada
weird though
i can wait since i have youtube vanced, everything i always used besides titanium
TheUndertaker21 said:
yeah i factory reset it after still nada
weird though
i can wait since i have youtube vanced, everything i always used besides titanium
Click to expand...
Click to collapse
Yea I used Vanced too, much better than the original YT app
I always did full TWRP nandroid backups rather than TiBu, but it's a good app
Not really impressed with the lengths Samsung are going to to prevent us (the phone OWNERS) from doing what we want with OUR own phones tbh
There was a workaround to update system apps with Nougat, literally no harm done to Samsung with us doing that but they still patched it in Oreo
Starting to feel more like an iPhone than an Android, wasn't the whole point of Android that it was basically open and unlocked for us to play with?
Thing is though, Samsung make one of the best android devices available and they know locking it down isn't going to hurt their sales
*Detection* said:
A member tested the combination ROM theory yesterday for the same purpose and it bootlooped their phone
Click to expand...
Click to collapse
I appreciate if you can share his thread maybe he got the wrong ROM that bricked the phone.
Hey guys, last week i wanna flash a custom rom on my SM-a520f/DS but my OEM unlock was missing,I thought i just had to wait for 7 days but it won't show even after 7 days
Now i flashed official stock rom and will try to wait again for 7 days, but if this doesn't work then imma bout to lose my mind.
What can i do if it doesnt oem unlock doesnt p
Appear even if you reflashed stock romm
MitchiePitchie said:
Hey guys, last week i wanna flash a custom rom on my SM-a520f/DS but my OEM unlock was missing,I thought i just had to wait for 7 days but it won't show even after 7 days
Now i flashed official stock rom and will try to wait again for 7 days, but if this doesn't work then imma bout to lose my mind.
What can i do if it doesnt oem unlock doesnt p
Appear even if you reflashed stock romm
Click to expand...
Click to collapse
Maybe a factory reset would help, I dunno...
TechGuyOnTechIT said:
Maybe a factory reset would help, I dunno...
Click to expand...
Click to collapse
Just reflashed stock rom and waiting 7 days. I'll update if it works:fingers-crossed:
MitchiePitchie said:
Just reflashed stock rom and waiting 7 days. I'll update if it works:fingers-crossed:
Click to expand...
Click to collapse
Well this SHOULD fix the issue. If not, then I suspect the phone's internal clock is messed and needs complicated repair, but this a very very very VERY rare occasion, and I doubt you don't have this issue.
My phone just flashed a ok TWRP, but after I accidentally restarted, the phone didn't put me in OEM jail. Talk about lucky!
Just wait 7 days, activate developer options, click unlock oem, flash twrp via odin and after that is done IMMEDIATELY hold power and plus so it doesn't get you back to oem jail. After you are in TWRP, try not to turn it off to keep the recovery, and either install a zip that removes the 7 day jail or a cudtom rom. If you don't have a microsd to transfer from your pc to your phone, just use adb sideload. If you have any questions, just reply!
TechGuyOnTechIT said:
Well this SHOULD fix the issue. If not, then I suspect the phone's internal clock is messed and needs complicated repair, but this a very very very VERY rare occasion, and I doubt you don't have this issue.
My phone just flashed a ok TWRP, but after I accidentally restarted, the phone didn't put me in OEM jail. Talk about lucky!
Just wait 7 days, activate developer options, click unlock oem, flash twrp via odin and after that is done IMMEDIATELY hold power and plus so it doesn't get you back to oem jail. After you are in TWRP, try not to turn it off to keep the recovery, and either install a zip that removes the 7 day jail or a cudtom rom. If you don't have a microsd to transfer from your pc to your phone, just use adb sideload. If you have any questions, just reply!
Click to expand...
Click to collapse
WAIT, so you need to wait 7 days before activating developer's option? Does that put you in prenormal rmm state? Because i already activated my developer's option, If thats the case then i already messed up
MitchiePitchie said:
WAIT, so you need to wait 7 days before activating developer's option? Does that put you in prenormal rmm state? Because i already activated my developer's option, If thats the case then i already messed up
Click to expand...
Click to collapse
No, you haven't messed up! The 7 day jail doens't block you access to developer options, but doesn't let you enable OEM unlock. I was suggesting you should do this just to make sure you are not in the 7 day jail. Again, if you can check that option, then there is not a problem. Just try to have your jail patcher zip handy so you won't have to deal with this problem. Again, if you have any questions, just reply!
TechGuyOnTechIT said:
No, you haven't messed up! The 7 day jail doens't block you access to developer options, but doesn't let you enable OEM unlock. I was suggesting you should do this just to make sure you are not in the 7 day jail. Again, if you can check that option, then there is not a problem. Just try to have your jail patcher zip handy so you won't have to deal with this problem. Again, if you have any questions, just reply!
Click to expand...
Click to collapse
Okay, the OEM unlock didn't showed up and my rmm state is still prenormal after 7 days even in flashing stock. I might retry this again in another rom carrier. I'm really at the end of my rope here
MitchiePitchie said:
Okay, the OEM unlock didn't showed up and my rmm state is still prenormal after 7 days even in flashing stock. I might retry this again in another rom carrier. I'm really at the end of my rope here
Click to expand...
Click to collapse
Don't give up! Try to go to download mode, flash a complete Samsung rom (with bootloader, modem, recovery and rom). I guess you can find a stock samsung rom on google or via smart switch. Download mode only blocks installing THIRD PARTY ROMS, not the stock ones. Try that and give a reply.
TechGuyOnTechIT said:
Don't give up! Try to go to download mode, flash a complete Samsung rom (with bootloader, modem, recovery and rom). I guess you can find a stock samsung rom on google or via smart switch. Download mode only blocks installing THIRD PARTY ROMS, not the stock ones. Try that and give a reply.
Click to expand...
Click to collapse
I'll try to flash the rom again and wait 7 days, I'll boot ip without sim and sd card first
TechGuyOnTechIT said:
Don't give up! Try to go to download mode, flash a complete Samsung rom (with bootloader, modem, recovery and rom). I guess you can find a stock samsung rom on google or via smart switch. Download mode only blocks installing THIRD PARTY ROMS, not the stock ones. Try that and give a reply.
Click to expand...
Click to collapse
Man I already flashed stock rom and waited 7 days, I ain't doing that stuff again I'll just sell this phone if I don't find any other way.
MitchiePitchie said:
Man I already flashed stock rom and waited 7 days, I ain't doing that stuff again I'll just sell this phone if I don't find any other way.
Click to expand...
Click to collapse
Seriously? Are you SURE you don't see OEM unlock in developer options, because any Samsung device SHOULD have the 7 day lift period. If you confirm that you don't see it, the only thing left to do is to contact a samsung expert. Don't feel embarrassed that you ask samsung for a third party thing, they must help you even though that may result in voiding your warranty.
Honestly, this is a pretty uncommon issue :/
TechGuyOnTechIT said:
Seriously? Are you SURE you don't see OEM unlock in developer options, because any Samsung device SHOULD have the 7 day lift period. If you confirm that you don't see it, the only thing left to do is to contact a samsung expert. Don't feel embarrassed that you ask samsung for a third party thing, they must help you even though that may result in voiding your warranty.
Honestly, this is a pretty uncommon issue :/
Click to expand...
Click to collapse
I'll try reflashing a carrier rom (Globe) not a XTC (openline) rom and if this doesn't work then i dont know what will:fingers-crossed:
MitchiePitchie said:
I'll try reflashing a carrier rom (Globe) not a XTC (openline) rom and if this doesn't work then i dont know what will:fingers-crossed:
Click to expand...
Click to collapse
Samsung support centre could also help.
TechGuyOnTechIT said:
Seriously? Are you SURE you don't see OEM unlock in developer options...Honestly, this is a pretty uncommon issue :/
Click to expand...
Click to collapse
I have the same issue. Started with Android 7, rooted phone, flashed Hades ROM v6 ( Android 8) which is fine, but I no longer see OEM Unlock in Developer options (presumably I did before installing Hades). Have tried the date fudge:
https://forum.xda-developers.com/samsung-a-series-2017/help/guide-oem-unlock-oreo-t3791774
more than once. No joy. Hades is fine, but I'd like to try the OneUI Android 9 ROM...
Corbynista said:
I have the same issue. Started with Android 7, rooted phone, flashed Hades ROM v6 ( Android 8) which is fine, but I no longer see OEM Unlock in Developer options (presumably I did before installing Hades). Have tried the date fudge:
https://forum.xda-developers.com/samsung-a-series-2017/help/guide-oem-unlock-oreo-t3791774
more than once. No joy. Hades is fine, but I'd like to try the OneUI Android 9 ROM...
Click to expand...
Click to collapse
If you are still on hades, the dev removed the OEM unlock toggle to prevent noobs from disabling it which would bootloop your phone and twrp would also not boot. Most if not all custom roms remove it. So you can flash Oneui
Corbynista said:
I have the same issue. Started with Android 7, rooted phone, flashed Hades ROM v6 ( Android 8) which is fine, but I no longer see OEM Unlock in Developer options (presumably I did before installing Hades). Have tried the date fudge:
https://forum.xda-developers.com/samsung-a-series-2017/help/guide-oem-unlock-oreo-t3791774
more than once. No joy. Hades is fine, but I'd like to try the OneUI Android 9 ROM...
Click to expand...
Click to collapse
When you are on cfw, as the guy said, there is no need. The rom is third party, meaning it's not official, thus it remains unlocked. But if you are on stock rom, then the oem unlock will be shown.
iloveoreos said:
If you are still on hades, the dev removed the OEM unlock toggle to prevent noobs from disabling it which would bootloop your phone and twrp would also not boot. Most if not all custom roms remove it. So you can flash Oneui
Click to expand...
Click to collapse
TechGuyOnTechIT said:
When you are on cfw, as the guy said, there is no need. The rom is third party, meaning it's not official, thus it remains unlocked. But if you are on stock rom, then the oem unlock will be shown.
Click to expand...
Click to collapse
I wondered if this was the case. Thanks to you both.
TechGuyOnTechIT said:
Samsung support centre could also help.
Click to expand...
Click to collapse
that ain't an option for me since they dont really respond. You know any other option if it doesn't even show this week too?
i reflashed stock rom like 5 times now
MitchiePitchie said:
that ain't an option for me since they dont really respond. You know any other option if it doesn't even show this week too?
i reflashed stock rom like 5 times now
Click to expand...
Click to collapse
Punch your phone, return it, and get another one.
SnowFuhrer said:
Punch your phone, return it, and get another one.
Click to expand...
Click to collapse
Nooooo! Don't do that! That would be a waste! Maybe its a bug. Try to flash twrp even though it doesn't show you kem unlock, and if that still doesn't work, give up trying systemless rooting and go full supersu by doing a one-click root (kingroot, etc). Maybe that helps. If it still not working, then I will finally recommend bailing and just getting another one . Sorry...
hi,
A70 is now widely sold, i try to buy one soonest but just waiting for root and twrp. it is still empty here on xda...
i found a link show how to root and install
https://myphoneupdate.com/samsung-galaxy-a70-twrp-recovery/
can i ask if some one already tried as above? looks like a copy method for all kind of phones ...
tks.
Most likely fake, the article was published a month ago. A70 only got released on 26th March.
I would definitely wait until someone posts a technique here; I tend to trust the experts here, but not so much everywhere else on the internet. I would prefer to wait a few weeks and put with an unrooted device, rather than possibly end up with a bricked (or hijacked) device.
Andre
ok i will wait...
it was like this, waited for s10+, came twrp but didnot like camera hole and waiting for A70, then waiting for twrp, then oneplus7pro release, then wait a bit for its twrp, till then note 10 pro comes soon, then wait for twrp of it....
and after 2+ year still using note8 LOL
amk said:
hi,
A70 is now widely sold, i try to buy one soonest but just waiting for root and twrp. it is still empty here on xda...
i found a link show how to root and install
https://myphoneupdate.com/samsung-galaxy-a70-twrp-recovery/
can i ask if some one already tried as above? looks like a copy method for all kind of phones ...
tks.
Click to expand...
Click to collapse
First thing I tried ofcourse, rooting the A70, but... follow the steps in the manual yourself, and you'll see that you get stuck on step 3:
3.) After That Download TWRP Recovery https://twrp.me File On Your PC And Renamed The Downloaded Recovery File Name To twrp.img.
But there is no TWRP Recovery available for the A70
I also tried the A50 manual, but that also fails (stuck on OEM lock). I can install CROM Service, but it crashes.
Captain Beretta said:
First thing I tried ofcourse, rooting the A70, but... follow the steps in the manual yourself, and you'll see that you get stuck on step 3:
3.) After That Download TWRP Recovery https://twrp.me File On Your PC And Renamed The Downloaded Recovery File Name To twrp.img.
But there is no TWRP Recovery available for the A70
I also tried the A50 manual, but that also fails (stuck on OEM lock). I can install CROM Service, but it crashes.
Click to expand...
Click to collapse
don't follow some clickbait website's...
wait for a proper and trusted dev to release twrp. the phones has barely hit the market it will take a few weeks (if not months) at least till someone builds an twrp. one think you could provide us with would be some information. is the bootloader unlockable?
In devsettings is a possible to unlock oem. Try this before flashing twrp. If twrp flashed ok, I think need to wipe all data, include internal storage, then flash DM-VERITY, FORCE ENCRYPTION, AND DISC QUOTA DISABLER
zackptg5.com/android.php
I don't try it by myself. But you can try it, if you just buy the phone, and have not important data on it
What about this guide is it worth trying or not really possible? https://topjohnwu.github.io/Magisk/install.html
Avicohen21 said:
What about this guide is it worth trying or not really possible? https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
Need to try
hello everyone I find a good deal on galaxy a70 is anyone succeed in rooting?
celoxocis said:
... is the bootloader unlockable?
Click to expand...
Click to collapse
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode. then got another with tick to choose. baterry is so good but look like i have touch panel issue. waiting for update and then root, twrp...
amk said:
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode.
Click to expand...
Click to collapse
Mine (bought direct from Samsung UK) has the OEM Unlock option in the Developer Options menu. Not tried it yet, not really much point until there is a reliable and tested root out there.
Andre
Hey guys manegd to root with this guide https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Seems to work good I'll notify if I'll notice any bugs. If you have twrp porting guide send me and I'll try to Port. If you want I can open a new thread with more details and upload the AP file I used. BTW I have the Israeli version SM-705FN
Avicohen21 said:
Hey guys manegd to root with this guide https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Seems to work good I'll notify if I'll notice any bugs. If you have twrp porting guide send me and I'll try to Port. If you want I can open a new thread with more details and upload the AP file I used. BTW I have the Israeli version SM-705FN
Click to expand...
Click to collapse
make a topic please
sanakess said:
make a topic please
Click to expand...
Click to collapse
Ok when I get home I'll open a thread with detailed explanation of what I did
Samsung account
Hello. My dumbass bought used A70 with samsung account. I can't make a factory reset, because it needs password from old owner account which i don't know. But I have my Google account on that phone and Google find my device enabled. Will I need to enter samsung account information when I make a reset via Google find my device? So when reset is made, phone will be locked only by FRP? And then when I login in my old Google account can i create a new Samsung account or do I need to login in existing that was on that phone first? Sorry for offtopic.
Any news about TWRP? SuperSu or Magisk?
Hello All, still can't find TWRP for sm-a705fn
Can I flash TWRP for another Exynos phone, like Galaxy 9, to my A70 ?
Also, can I still use SuperSu with Pie/A70 ? I failed to root my previous Galaxy Tab8 with custom Pie using SuperSU, had to root with Magisk instead,
it worked just fine, but the link to topjohnwu mentioned in previous posts, tells scary things about Samsung/Pie/Magisk -
like, I have to switch between two recoveries... Is that really the case?
I haven't noticed any issue with Tab8/Pie/Magisk, but SuperSu would be still more familiar to me.
used2brick said:
Hello All, still can't find TWRP for sm-a705fn
Can I flash TWRP for another Exynos phone, like Galaxy 9, to my A70 ?
Also, can I still use SuperSu with Pie/A70 ? I failed to root my previous Galaxy Tab8 with custom Pie using SuperSU, had to root with Magisk instead,
it worked just fine, but the link to topjohnwu mentioned in previous posts, tells scary things about Samsung/Pie/Magisk -
like, I have to switch between two recoveries... Is that really the case?
I haven't noticed any issue with Tab8/Pie/Magisk, but SuperSu would be still more familiar to me.
Click to expand...
Click to collapse
No, you can't use twrp for a different device, and don't use SuperSU neither. It was sold by chainfire to a Chinese company years ago and have been basically abandoned since 2017. I'm pretty sure Magisk is the better choice on any device running android 5 - 9.
Sent from my motorola one vision
Hello,
The problem with the post you mentioned is that there is no valid twrp attached. And I noticed that only Odin detects the fastboot mode of this device. If you enable USB debugging let's say, the command "adb devices" will detect the device and list it; whereas, if you reboot it to bootloader mode(fastboot), the command fastboot devices doesn't detect the phone. So in fastboot mode, only Odin will detect the device. Meaning, that the post of fake and not tested.
Regards,
Wael
amk said:
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode. then got another with tick to choose. baterry is so good but look like i have touch panel issue. waiting for update and then root, twrp...
Click to expand...
Click to collapse
That's weird. I do have the Bootloader unlock option in the developer settings and can do/undo it just fine. Looks like Samsung is using different Firmware versions on the A70?
I can't seem to find a consistent guide on this. Any help to to get me rooted and using an unlocked bootloader is greatly appreciated. If anyone knows a great, recent guide or knows how to do this, please link it.
Blaze Uchiha said:
I can't seem to find a consistent guide on this. Any help to to get me rooted and using an unlocked bootloader is greatly appreciated. If anyone knows a great, recent guide or knows how to do this, please link it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-j2/help/j2-core-sm-j260g-help-t3921806
2nd comment which is my comment. It should work.
Unlocking bootloader for Samsung device seems to be only turn on OEM unlocking
Prove N. said:
https://forum.xda-developers.com/galaxy-j2/help/j2-core-sm-j260g-help-t3921806
2nd comment which is my comment. It should work.
Unlocking bootloader for Samsung device seems to be only turn on OEM unlocking
Click to expand...
Click to collapse
There's no OEM unlocking option in my developer's options. I thought it was weird but this phone is brand new as I just got it today
Blaze Uchiha said:
There's no OEM unlocking option in my developer's options. I thought it was weird but this phone is brand new as I just got it today
Click to expand...
Click to collapse
So its your carrier's problem then. TMobile to be exact. Are you on a contract or anything? Can you issue an unlock request if no contract?
(I dont know much how US-locked phone works~)
So I've got mine unlocked, almost absolutely 0 information on the product. Researched about 3 hrs now and still only got the info obtained from devcheck. Will provide anything required. Looking to root magisk, wanna try out lineage. I'll be a tester, i am a noob.
Model- sm-j260t1
Device- j2corepltemtr
2019
Build-M1ajq.j260t1uvu1asa3
Made 1-10-2019
8.1.0 os
build-13.18.14-15262773
If instructed how to back up I'd be happy to share kernel/firmware.
Tia
Snip
Snippititgood said:
So I've got mine unlocked, almost absolutely 0 information on the product. Researched about 3 hrs now and still only got the info obtained from devcheck. Will provide anything required. Looking to root magisk, wanna try out lineage. I'll be a tester, i am a noob.
Model- sm-j260t1
Device- j2corepltemtr
2019
Build-M1ajq.j260t1uvu1asa3
Made 1-10-2019
8.1.0 os
build-13.18.14-15262773
If instructed how to back up I'd be happy to share kernel/firmware.
Tia
Snip
Click to expand...
Click to collapse
Help me man lol
Sent from my SM-J260T1 using XDA Labs
Snippititgood said:
So I've got mine unlocked, almost absolutely 0 information on the product. Researched about 3 hrs now and still only got the info obtained from devcheck. Will provide anything required. Looking to root magisk, wanna try out lineage. I'll be a tester, i am a noob.
Model- sm-j260t1
Device- j2corepltemtr
2019
Build-M1ajq.j260t1uvu1asa3
Made 1-10-2019
8.1.0 os
build-13.18.14-15262773
If instructed how to back up I'd be happy to share kernel/firmware.
Tia
Snip
Click to expand...
Click to collapse
Yes did anything ever come of this? Also when you unlock it, does it you to root it?
So is there a way to get the OEM option to appear in the dev options or a way to install a bootloader without OEM?
I'm having the same exact problem with my phone. Same model and everything and I also do not have the unlocking option In my dev options. I've tried every exploit known to me and have no luck. I tried flashing TWRP theough Odin without the OEM unlocking and I get a fail because of a secure check fail which I'm not sure is related to the bootloader not being unlocked or something else. I'd love to get an answer to this so I can get lineageos on here
Has anyone found anything yet on how to unlock or enable OEM unlocking
As I understand it the OEM unlock setting is only available after owning the device for 160 days.
Samsung Galaxy J2 (Metro PCS) [SM-J260T1]
Sircrysalotz said:
Has anyone found anything yet on how to unlock or enable OEM unlocking
Click to expand...
Click to collapse
Firmware info of Samsung Galaxy J2 (Metro PCS) [SM-J260T1]
Android version - 8.1.0 (Oreo)
Build # M1AJQ.J260T1UVS6ATG2
There is no OEM unlock option in the dev options for this phone.
The most I could do is to get in to go into download mode, no bootloader came up.
I Used ADB Command: adb reboot bootloader
Another PC app I seen on xda forums is called "ADBAppControl".
There is an option reboot your phone with adb built in to do it too.
---------- Post added at 05:45 AM ---------- Previous post was at 05:17 AM ----------
Blaze Uchiha said:
So is there a way to get the OEM option to appear in the dev options or a way to install a bootloader without OEM?
Click to expand...
Click to collapse
My J2 is new and No at this Point, One Reply in here said after 160 days of owning it the option opens up, so I will have wait for the 160 days are up to check again.
Update, it been Over 160 Days and still do not see anything in the dev options. I bought the phone 4-12-2020. So i guess it lockout code that releases the option i suppose. or it just not available with this phone.
Was thinking of flashing my old stock 4.1 on it. cause 4.1 i had no trouble rooting it.
Yes,I'm new to the forum. I also have the same model phone unlocked from the carrier(Metro PCS). I've tried several ways to root this device but I don't have access to a PC I also get the security error code to pop up when I tried to install custom OS. I can't seem to get the recovery backup or to actually Flash the proper image to the bootloader I've also tried kingroot, kingoroot, l root, and some other one click root options. My understanding of using team Win Recovery Project without PC is limited I'm also trying to use magisk with it.In A novice in understanding...Does anyone have any advice..
Better find a friend with a computer to help you . Apps are crappier than Microsoft.
Since the inception of Android getting stuck in a bootloop after updating is a common problem. The Red Magic 6 Pro is no exception. For the purposes of this guide I'm referring to the global, or as known in the USA, the US version of the Red Magic 6 Pro. After receiving my device directly from Red Magic's website, I of course wanted to toy with it and see what I could and couldn't do with it. I downloaded the official global Rom from Red Magic's website for future possible fixes if anything went wrong unlocking the bootloader and rooting. I unlocked my bootloader and rooted via patching stock boot with Magisk as outlined in @chocolote4444 thread. After screwing around with Magisk modules and doing all I wanted to do, I decided to unroot and relock the bootloader. This is where the fun began.
After unrooting and relocking the bootloader, I placed the full update zip in root directory of internal storage and ran the local update. It wasn't necessary, but just to make myself feel better i did it anyway. After the update was complete and I rebooted it was stuck in boot animation bootloop. Factory resetting via recovery did nothing to alleviate the bootloop. Here's what I did to fix the bootloop:
1: Hold down power and volume down to reboot in to fastboot.
2:
Code:
fastboot getvar all
This will tell you what your current active slot is. Just look through the lines returned and you'll see it.
3: Once you see what your active slot is you're going to change the active slot to the opposite slot. If you're slot a you're going to change it to b and vice versa.
4: In order to change active slots you have to be bootloader unlocked if you aren't already. I won't detail here how to unlock because if you don't already know how to do it you shouldn't be doing this anyway.
5:Now to set your active slot,
Code:
fastboot --set-active=a
if you're on slot b or
Code:
fastboot --set-active=b
if you're on a.
6: At this point you can reboot. If all goes well you should reboot and the bootloop is gone. After rebooting and assuming everything has been done correctly, you should boot into system. After rebooting and you boot into system, you can reboot again into fastboot and relock the bootloader if you so wish.
The reason you're getting stuck in bootloop after update is it's not switching slots correctly after update. This is purely speculation on my part but it seems to fit. Thats it! You should now be up and running. I hope this helps someone whos stuck and as aggravated as I was.
Dang thank you for the guide, but rippers to people who still have their bootloader locked
CyberWolf92 said:
Dang thank you for the guide, but rippers to people who still have their bootloader locked
Click to expand...
Click to collapse
it makes me cry that we cant get solution for this locked bootloader
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
bob24260 said:
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
Click to expand...
Click to collapse
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Nocturne Seigneur said:
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
Click to expand...
Click to collapse
bob24260 said:
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Click to expand...
Click to collapse
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
CyberWolf92 said:
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
Click to expand...
Click to collapse
Do you have the 6 or 6 Pro?
bob24260 said:
Do you have the 6 or 6 Pro?
Click to expand...
Click to collapse
It's the 6 Pro
CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Mines the 6 Pro as well. Screenshot your about section in settings and we can compare. Make sure you block out any personal information. I don’t understand why yours is different.
CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Sorry I feel like an idiot. Yours is soft bricked?
bob24260 said:
Sorry I feel like an idiot. Yours is soft bricked?
Click to expand...
Click to collapse
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
CyberWolf92 said:
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
Click to expand...
Click to collapse
Their recovery is totally different. Most stock recoveries have a way to flash stock zips. Just for sh*ts and giggles have you tried adb sideload? Probably won’t work with locked bootloader but you never know. Try it in stock recovery.
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
CyberWolf92 said:
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
Click to expand...
Click to collapse
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
bob24260 said:
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
Click to expand...
Click to collapse
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
CyberWolf92 said:
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
Click to expand...
Click to collapse
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
bob24260 said:
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
Click to expand...
Click to collapse
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Edit: Mod please remove.
CyberWolf92 said:
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Click to expand...
Click to collapse
Verizon can be a huge pia. I used them for quite a few years but got tired of 400-500$ bills. I highly recommend Xiaomi. I've had several of their devices and for the money you can't beat them. A good entry level device of theirs is the Mi 10T. On paper they look sort of meh but having had one I can attest to their overall decency.