Related
Trying to compile as many users who have faced the same issue and to get some data to find a work around.
SM-N950F - Australian (TEL/TEL/TEL) post paid Telstra Note 8.
Waited one week for 'Allow OEM to be unlocked' to appear in Dev Settings.
This is my experience and now have the official binaries issue.
I also got the OEM unlock after one week, this is what happened when trying to install TWRP and Magisk on Stock ROM.
I tried to flash TWRP lost night and that was okay. I decided to hold onto stock and just have TWRP and Magisk at this stage until other roms are a little less buggy. Flashed TWRP. flashed Verity / Magisk, setup phone again and then decided to do a backup in TWRP. When trying to go into TWRP got the message 'Only official released binaries are allowed to be flashed' and then went into a soft brick. Had to restore phone to stock and now OEM unlock has disappeared again, In download mode FRP and OEM lock are both OFF. Tried to reflash TWRP and get the same message - 'Only official released binaries are allowed to be flashed'.
So the plot thickens.
Andysmith71 said:
Trying to compile as many users who have faced the same issue and to get some data to find a work around.
SM-N950F - Australian (TEL/TEL/TEL) post paid Telstra Note 8.
Waited one week for 'Allow OEM to be unlocked' to appear in Dev Settings.
This is my experience and now have the official binaries issue.
I also got the OEM unlock after one week, this is what happened when trying to install TWRP and Magisk on Stock ROM.
I tried to flash TWRP lost night and that was okay. I decided to hold onto stock and just have TWRP and Magisk at this stage until other roms are a little less buggy. Flashed TWRP. flashed Verity / Magisk, setup phone again and then decided to do a backup in TWRP. When trying to go into TWRP got the message 'Only official released binaries are allowed to be flashed' and then went into a soft brick. Had to restore phone to stock and now OEM unlock has disappeared again, In download mode FRP and OEM lock are both OFF. Tried to reflash TWRP and get the same message - 'Only official released binaries are allowed to be flashed'.
So the plot thickens.
Click to expand...
Click to collapse
We are on the same boat bro,
Mine is SM-N950F/DS Singapore (XSP), got on Sep 9th via preorder from Singtel.
But I did not notice if oem unlock option was there when I got the device. Then I tried to flash TWRP last week(oem unlock was there), flashed SuperSU 2.82. When I was configuring an app to modify host(to disable ads), the phone rebooted itself before I was able to flash dm-verity, and went into the bootloop with the same msg 'Only official released binaries are allowed to be flashed' [emoji33]
Alright, here's where I'm at after some experimentation.
I received my phone on the 19th, and when I looked in "Developer options" for the "OEM Unlock" option it was not present. A week (7 days) goes by and I look in "Developer options" again and I see that "OEM Unlock" is there. I enabled the toggle that day, and then in the evening I successfully flashed TWRP and noverity. After this I rebooted according to the instructions and I encountered the "Only official released binaries are allowed to be flashed" message along with a soft brick. Reflashed stock firmware to get out of it and "OEM Unlock" has vanished from "Developer options"
Now, a week goes by after this (7days again) and I check for "OEM Unlock" on the 26th. Just like clockwork it's there. This time I flash TWRP, skip noverity, and flash Magisk. I'm able to successfully root and I boot into the system -- I check "Developer options" for "OEM Unlock" and the toggle isn't there. For whatever reason after a while I decided I would reboot and see what happens. I go into a soft brick with the same "Only official released binaries are allowed to be flashed" message. I'm kind of kicking myself, because now I need to wait another week for the toggle to show up so I can make another attempt.
Next week I am going to flash TWRP, flash Magisk, and then let the phone sit there for another week while I wait for the "OEM Unlock" toggle to show back up. Once that happens I am going to see if I can reboot freely or if I encounter another soft brick situation. If I soft brick again I'm fresh out of ideas as a phone that is rooted but can never be rebooted without flashing back to stock is a non-starter.
thegreenthief said:
Alright, here's where I'm at after some experimentation.
I received my phone on the 19th, and when I looked in "Developer options" for the "OEM Unlock" option it was not present. A week (7 days) goes by and I look in "Developer options" again and I see that "OEM Unlock" is there. I enabled the toggle that day, and then in the evening I successfully flashed TWRP and noverity. After this I rebooted according to the instructions and I encountered the "Only official released binaries are allowed to be flashed" message along with a soft brick. Reflashed stock firmware to get out of it and "OEM Unlock" has vanished from "Developer options"
Now, a week goes by after this (7days again) and I check for "OEM Unlock" on the 26th. Just like clockwork it's there. This time I flash TWRP, skip noverity, and flash Magisk. I'm able to successfully root and I boot into the system -- I check "Developer options" for "OEM Unlock" and the toggle isn't there. For whatever reason after a while I decided I would reboot and see what happens. I go into a soft brick with the same "Only official released binaries are allowed to be flashed" message. I'm kind of kicking myself, because now I need to wait another week for the toggle to show up so I can make another attempt.
Next week I am going to flash TWRP, flash Magisk, and then let the phone sit there for another week while I wait for the "OEM Unlock" toggle to show back up. Once that happens I am going to see if I can reboot freely or if I encounter another soft brick situation. If I soft brick again I'm fresh out of ideas as a phone that is rooted but can never be rebooted without flashing back to stock is a non-starter.
Click to expand...
Click to collapse
I'm doing the same as you, I'm still a few days away from week 2. So I'll do the same, flash TWRP and Magisk then try my hardest not to have the phone restarted for any reason for another week. No reports yet of this work around as it's still early in the peace but I know there are a number of users who will try this method. Good luck and I'll post how I go or if someone else posts sooner! BTW did you do a wipe/format before flashing Magisk out of interest? Cheers.
zhengsmall said:
We are on the same boat bro,
Mine is SM-N950F/DS Singapore (XSP), got on Sep 9th via preorder from Singtel.
But I did not notice if oem unlock option was there when I got the device. Then I tried to flash TWRP last week, flashed SuperSU 2.82. When I was configuring an app, the phone rebooted itself before I was able to flash dm-verity, and went into the bootloop with the same msg 'Only official released binaries are allowed to be flashed'
Click to expand...
Click to collapse
Hey mate, maybe you can try the method a few users are going to do now, after another week and when OEM re appears then redo the process but this time don't boot the device. However I see what happened in your case the phone restarted itself when configuring SuperSU.. I've not hear that happening before. Maybe try Magisk if your looking at trying again? Strange it rebooted by itself. Good luck and let us know how you go.
Andysmith71 said:
I'm doing the same as you, I'm still a few days away from week 2. So I'll do the same, flash TWRP and Magisk then try my hardest not to have the phone restarted for any reason for another week. No reports yet of this work around as it's still early in the peace but I know there are a number of users who will try this method. Good luck and I'll post how I go or if someone else posts sooner! BTW did you do a wipe/format before flashing Magisk out of interest? Cheers.
Click to expand...
Click to collapse
It's good we're getting to a point where we can collect data and try different approaches. It was a much darker time when we were all sitting around wondering if/when the OEM Unlock toggle would show up!
Yes, I did a wipe/format prior to flashing Magisk. One thing I haven't been doing is clearing the cache/dalvik following successful flash... is that important? I recall doing that back when I rooted my S7 Edge, but I've not seen or heard about anyone doing it since.
You might want to check the huge thread on this thats about three posts from here. Short story it seems if you stay in recovery and install a rom with knox disabled you are good to go. Read more there...
krabman said:
You might want to check the huge thread on this thats about three posts from here. Short story it seems if you stay in recovery and install a rom with knox disabled you are good to go. Read more there...
Click to expand...
Click to collapse
Thanks mate, been reading up there and seen the posts. Looks like Renovate has had most success so far with that method. Looks promising, fingers crossed. I've got another few more days in jail before I get the OEM unlock back.
I don't think anyone has reported a failure yet doing it that way. Still a ways to go on the testing though, It appears folks aren't all that anxious to screw up a good thing once they get up and running. The good news is if ordinary dumbassez like us can get in the smart guys should get something figured out sooner rather than later. Anyhow, good luck, if it's any consolation mine showed up in 5 days...
Andysmith71 said:
Hey mate, maybe you can try the method a few users are going to do now, after another week and when OEM re appears then redo the process but this time don't boot the device. However I see what happened in your case the phone restarted itself when configuring SuperSU.. I've not hear that happening before. Maybe try Magisk if your looking at trying again? Strange it rebooted by itself. Good luck and let us know how you go.
Click to expand...
Click to collapse
Thanks for the suggestion mentioned, but what do you mean by redo the process? Or just switch off and then on the oem unlock toggle when it reappears in 7 days after the first flash(twrp and supersu) followed by a reboot(as only via reboot can I judge if it works)?
In addition, in my case the phone restarted itself when I tried to modify host to disable the annoying ads, not during configuring SuperSU.
Just ended up in the same boat as OP. same version same carrier etc.
hopefully soon the smart ones can figure this out. off to find stock rom and try to get back a working device
AndiF85 said:
Just ended up in the same boat as OP. same version same carrier etc.
hopefully soon the smart ones can figure this out. off to find stock rom and try to get back a working device
Click to expand...
Click to collapse
Hey mate, try the below mentioned method and see if it works.
thegreenthief said:
Alright, here's where I'm at after some experimentation.
I received my phone on the 19th, and when I looked in "Developer options" for the "OEM Unlock" option it was not present. A week (7 days) goes by and I look in "Developer options" again and I see that "OEM Unlock" is there. I enabled the toggle that day, and then in the evening I successfully flashed TWRP and noverity. After this I rebooted according to the instructions and I encountered the "Only official released binaries are allowed to be flashed" message along with a soft brick. Reflashed stock firmware to get out of it and "OEM Unlock" has vanished from "Developer options"
Now, a week goes by after this (7days again) and I check for "OEM Unlock" on the 26th. Just like clockwork it's there. This time I flash TWRP, skip noverity, and flash Magisk. I'm able to successfully root and I boot into the system -- I check "Developer options" for "OEM Unlock" and the toggle isn't there. For whatever reason after a while I decided I would reboot and see what happens. I go into a soft brick with the same "Only official released binaries are allowed to be flashed" message. I'm kind of kicking myself, because now I need to wait another week for the toggle to show up so I can make another attempt.
Next week I am going to flash TWRP, flash Magisk, and then let the phone sit there for another week while I wait for the "OEM Unlock" toggle to show back up. Once that happens I am going to see if I can reboot freely or if I encounter another soft brick situation. If I soft brick again I'm fresh out of ideas as a phone that is rooted but can never be rebooted without flashing back to stock is a non-starter.
Click to expand...
Click to collapse
Andysmith71 said:
I'm doing the same as you, I'm still a few days away from week 2. So I'll do the same, flash TWRP and Magisk then try my hardest not to have the phone restarted for any reason for another week. No reports yet of this work around as it's still early in the peace but I know there are a number of users who will try this method. Good luck and I'll post how I go or if someone else posts sooner! BTW did you do a wipe/format before flashing Magisk out of interest? Cheers.
Click to expand...
Click to collapse
I will give it a try once oem unlock returns. Hopefully this can be resolved soon. Being in jail sucks. I've tripped Knox so lost Samsung features and no root still so dont have root advantages.
Sent from my SM-N950F using Tapatalk
krabman said:
You might want to check the huge thread on this thats about three posts from here. Short story it seems if you stay in recovery and install a rom with knox disabled you are good to go. Read more there...
Click to expand...
Click to collapse
Well I got out of Jail yesterday after getting back the OEM unlock for the 2nd time. This time I decided to 'play it safe' until the smart people figure out what the issues are. This method worked perfectly for me and I've now been flashing Viper, flashing extra fonts, doing backups in TWRP and generally using the phone as normal again. The current Renovate release (r95) has most of the issues fixed and is a good daily driver, also the facial recognition is all fixed and Magisk is working with no issues, I've been able to use my banking apps for over the counter purchases again, tested and all working. Here is the method that worked for me -
How to flash Renovate and not stuff up. Remove SIM card before starting (I got this from Krabman's posts so I was not going to tempt fate at this stage by leaving in my SIM card, this is just a playing safe method for now).
1. Install TWRP (I trust you all are okay with everything up to this part)
2. In TWRP, swipe right and go into menu.
3. Wipe / Format Data / Yes
4. Reboot into RECOVERY
5. Flash DM-Verity
6. Wipe / Factory reset (by swiping)
7. Flash Renovate - I chose to root with Magisk cause it works for my banking apps.
8. After flashing Renovate, allow it to boot into System.
9. Do your basic setup and then reboot.
10. Now insert SIM and continue to setup your phone, Ti and all that good stuff. Phone is now rooted and working, TWRP is all working and safe to use as normal. This is the part that I did Ti restore and flashed Viper4Android etc etc.
11. Happy days for now, until we work out exactly what the issues are.......
The only thing I did not do was to try and flash the XSA firmware (Australia Unbranded) with the S8 CSC firmware installer. Apparently another user used it and it worked for them on the Note 8, however I did not want to chance it for now. The only drawback is on Volte and WiFi calling is missing but that's not a deal breaker. I might research a bit more before I try to flash the CSCSelection_S7_S8 zip.
AndiF85 said:
I will give it a try once oem unlock returns. Hopefully this can be resolved soon. Being in jail sucks. I've tripped Knox so lost Samsung features and no root still so dont have root advantages.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
I was in the same boat as you - if Renovate floats your boat then check out my last post, I've installed Renovate and all working nicely again... Waiting for one week then in jail for another week sucked hard!
Great to hear it worked for you. I was thinking of using Renovate as well as it looks like the best option we have at the moment. Now you have confirmed it's all good I'll be doing it the day I'm released from OEM jail. When I flashed stock firmware I tried the note 8 xsa to see if it was any better than the Telstra version but instead just lost features and gained new things in settings which didn't even work so went back and flashed Telstra version.
I know it's wishful thinking but does Samsung pass work for you? I don't care for Samsung pay and health but Samsung pass was a nice feature.
Sent from my SM-N950F using Tapatalk
AndiF85 said:
Great to hear it worked for you. I was thinking of using Renovate as well as it looks like the best option we have at the moment. Now you have confirmed it's all good I'll be doing it the day I'm released from OEM jail. When I flashed stock firmware I tried the note 8 xsa to see if it was any better than the Telstra version but instead just lost features and gained new things in settings which didn't even work so went back and flashed Telstra version.
I know it's wishful thinking but does Samsung pass work for you? I don't care for Samsung pay and health but Samsung pass was a nice feature.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Just tested that out for you, unfortunately that is the only one that does not work (Well we know Samsung Pay won't work due to KNOX being tripped). It goes through all the setup okay, then on final authentication it says "Samsung Pass is temporarily unavailable, please try again later". So that's a bit of a bummer.. I've tested Android Pay, all good, and I also use NAB pay and works with no issues as well as long as you set it up correctly with Magisk (there is a bit of a method to follow but I found a way to make it work - in case your with NAB at all).
I might make a suggestion to mwilky to see if that could possibly be fixed in the ROM as I agree it's a great feature.
Edit - That question was already asked by another user, mwilky says that it does not work the moment TWRP is flashed and not likely able to be changed. Bummer.
Soft brick
How do you get out of the soft brick? I have the SM-N950F/DS but I do not know what REGION I need to download for the official firmware. Thanks for any help!
bwallis said:
How do you get out of the soft brick? I have the SM-N950F/DS but I do not know what REGION I need to download for the official firmware. Thanks for any help!
Click to expand...
Click to collapse
Use Samsung Smart Switch for that. it will tell you the region code for your phone. It could restore for you, or you could use http://fw.updato.com/, or SamFirm, to download appropriate ROM
Alright finally I'm out of jail.
About to download everything then going to attempt tonight.
Andsmith71 how have you found the rom over the past week?
Any issues?
still holding Root?
Does Bixby Voice still work?
Sent from my SM-N950F using Tapatalk
Hey.
I've got my Note8 few days ago, was thinking about rooting soon, mainly because I want ARISE and V4A badly.
I've been reading forums and I've encountered few issues people had with rooting, now I'm not sure if I want to risk and root. I don't want mess up my Note. I have quite a bit experience with modding android phones, but still, last Samsung phone I had was SGS3 and any of those problems weren't present then. No problems with rooting LG's, Huawei's or Xiaomi's.
First of all, thing named "jail", related to "only official binaries are allowed". How bad is that? Is it still a thing in custom ROMs? Or even just rooting stock firmware? And what does that exactly mean? Is jailed phone still usable?
Second thing, there was an problem with charging the phone, Snapdragon version. It's supposed to charge only till 80%. Only Snapdragon related or both?
I have european SM-N950F Duos, I guess it's factory unlocked one. Unlock OEM option in Developer Options was present from the day one.
I'd appreciate any explanation.
80% charging is only related to Samsung S8/S8+/Note 8 models utilizing Qualcomm's Snapdragon 835 chip. This doesn't apply to Exynos.
In regards to 'only official binaries are allowed', this should be, and someone correct me if I'm wrong, related to specific Exynos models where 'OEM Unlock' appears after 7 days upon activation BUT disappears later when root is achieved. I believe models purchased from Southeast Asia were/are most affected.
To counter 'only official binaries are allowed', a workaround was found where flashing a custom rom AFTER 'OEM Unlock' appeared would counter the issue.
Thus, based on the details relayed, you should be good to go IF 'OEM Unlock' was present from activation.
If you are concerned that you fall into the affected group, you can always perform a factory wipe and see if 'OEM Unlock' is still present. If it isn't available, you know the workaround. If it is available, you can go ahead and flash Recovery (TWRP) and go for root (SuperSU or Magisk).
Good luck!
A_H_E said:
80% charging is only related to Samsung S8/S8+/Note 8 models utilizing Qualcomm's Snapdragon 835 chip. This doesn't apply to Exynos.
In regards to 'only official binaries are allowed', this should be, and someone correct me if I'm wrong, related to specific Exynos models where 'OEM Unlock' appears after 7 days upon activation BUT disappears later when root is achieved. I believe models purchased from Southeast Asia were/are most affected.
To counter 'only official binaries are allowed', a workaround was found where flashing a custom rom AFTER 'OEM Unlock' appeared would counter the issue.
Thus, based on the details relayed, you should be good to go IF 'OEM Unlock' was present from activation.
If you are concerned that you fall into the affected group, you can always perform a factory wipe and see if 'OEM Unlock' is still present. If it isn't available, you know the workaround. If it is available, you can go ahead and flash Recovery (TWRP) and go for root (SuperSU or Magisk).
Good luck!
Click to expand...
Click to collapse
Thanks! That clarified a bit. I'll try stock wipe method first, that seems most adequate/safe method to be sure.
So what will we loose upon rooting apart from Sam pay and sec folder?
IS there anything other then the above that will stop working ?
I've read SHealth requires Knox too since one of the updates.
resutatto said:
I have european SM-N950F Duos, I guess it's factory unlocked one. Unlock OEM option in Developer Options was present from the day one.
I'd appreciate any explanation.
Click to expand...
Click to collapse
@resutatto : hey, where did you buy your note 8 from ? is it from an online store ? i am looking for one exacty like your model with OEM unlock option available from day one.
thank you !
mailistman said:
@resutatto : hey, where did you buy your note 8 from ? is it from an online store ? i am looking for one exacty like your model with OEM unlock option available from day one.
thank you !
Click to expand...
Click to collapse
I've got mine from one of the carriers. Non branded, clean.
Rooting always comes with a risk. Lol
Hey everyone!
First posting here, long time reader. So, I just f***** up big time. I tried to install the YT Vanced modules for my X4, realized I had to get rid of the stock YT app first, installed Terminal Debloater and at that point my device stuck during boot. To make things infinitely worse, I then proceeded to re-lock the bootloader cycling through the last commands issued. That was dumb, yeah.
Now I get the "device corrupt" message when I try to boot normally and fastboot won't let me flash again saying I need to enable USB debugging, which I can't because the system won't let me boot.
I have a severe feeling I'm screwed with nobody but myself to blame, but I'm also aware of the godlike knowledge in these boards so... can anyone point me in a direction here? Damn I like that phone and have zero funds for a new one right now :/
I can still get into the Power+Down menu, the stock recovery gets me nowhere though. Oh, and it's the Euro Model, Motorola Moto X4 XT1900-05, running the Oreo OTA update.
Cheers people,
grslbr
You need to flash the original official firmware that came loaded on your device but good luck trying to find a copy of that. With the bootloader locked, you're screwed.
Thanks for answering. Yeah, since I locked the bootloader in my infinite wisdom I think I am screwed for good.
Could Lenovo have some magic tools to re-flash the stock ROM? I mean I know I voided my warranty but I liked that phone and am all out of options at this point. :/
FI stock roms seem to be located at https://firmware.center/firmware/Motorola/Moto X4/Stock/ Have not tried them myself and not sure you can flash with a locked bootloader.
You should be able to flash a stock ROM pretty easily. From what I've seen, you should be able to install any retail stock rom without unlocking the bootloader.
grslbr said:
Thanks for answering. Yeah, since I locked the bootloader in my infinite wisdom I think I am screwed for good.
Could Lenovo have some magic tools to re-flash the stock ROM? I mean I know I voided my warranty but I liked that phone and am all out of options at this point. :/
Click to expand...
Click to collapse
Hold Vol+ and Power buttons. Phone will try to reboot several times and then boot normaly. Go to developer options and tick allow factory unlock and USB debugging. Then you just unlock bootloader as usual.
This procedure helped fix the same issue with my xt1900-7 reteu.
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting. I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging.
jwils1236 said:
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting and wouldn't have bought it if I would have known (or at least not updated to Pie). I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging/impossible. Any help would be appreciated and if a solution is brought to light, I am gladly offering $. This could easily be considered a device with best hardware and when rooted, access to best software -- I didn't see significant enough improvements in Note 9 and figured by now the support from XDA community would be abundant for the exynos processor. Turning out ridiculous waste of money if I can't root it (already purchased silver carbon fiber skin, 256 GB Samsung Evo Select SD card, attachable portable wireless charging pack, etc.). Please help!
Click to expand...
Click to collapse
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Its just easy step
Things u needed before proceed
* SD card
*Magisk latest version
*Odin
* Twrp zip file
1. Reflash ur device with proper firmware
2. After done go download mode and flash Twrp zip on odin. After done reboot ur device to Twrp again
3. After boot up to Twrp go to Wipe and do a factory restore . After this done u must install Magisk or u will get official binary only after reboot to system
4. After all the step are followed u are good to go. Cheers
stonedpsycho said:
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Click to expand...
Click to collapse
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
Also, for anyone reading this with the same issue, extracting the boot image from stock firmware (can be done through command prompt/terminal dump or by extracting from stock firmware -- AP Odin file) and patching with Magisk will not flash or work/give root access either unless this device is fully unlocked -- OEM unlock doesn't matter, if RMM still says "Prenormal" in download mode.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I am quite sure it is still rootable on bootloader 6, so updating would be fine.
The trick to get the OEM toggle is a bit hit and miss, the guide below is the method that has had a higher success rate for me, if followed exacty as written.
https://www.google.com/amp/s/www.xd...-samsung-galaxy-s8-samsung-galaxy-note-8/amp/
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I ended up using Chimera Tool to bypass RMM state. Worked instantly. This seems to be a common issue for many Samsung devices, at least on Pie. Not sure there is an alternative solution, currently. Only one I could find for my device.
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
tonyboy_23 said:
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
Click to expand...
Click to collapse
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
tonyboy_23 said:
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
Click to expand...
Click to collapse
there is only one method that is going to work for you, that method is linked above.
the problem with instructions can be when you don't know what they mean and the way they're written assumes you should.
there are many steps and they are all crucial (like unlocking the bootloader first).
if you don't understand what something means paste it here and ask, people will help you.
bininga59 said:
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
Click to expand...
Click to collapse
Thank you. I have followed the guide to the letter. My screen (in dl mode) is showing OEM bootloader thingy lock is OFF... but I am still getting the 'only official...' error message when trying to flash the boot tar file made in the guide
3mel said:
there is only one method that is going to work for you, that method is linked above.
the problem with instructions can be when you don't know what they mean and the way they're written assumes you should.
there are many steps and they are all crucial (like unlocking the bootloader first).
if you don't understand what something means paste it here and ask, people will help you.
Click to expand...
Click to collapse
Thank you. I feel i understood what I was supposed to do in each step, but i still get the only official... message. The lock is showing as 'OFF' on the DL screen, but it still blocks me.
tonyboy_23 said:
Thank you. I feel i understood what I was supposed to do in each step, but i still get the only official... message. The lock is showing as 'OFF' on the DL screen, but it still blocks me.
Click to expand...
Click to collapse
The switch in developer mode MUST be like this (picture), otherwise you cannot flash or root custom roms, custom kernels, etc.
I've read that sometimes you have to wait a few days for it to show up as unlocked finally. also you can't lock a brand new phone instantly, you've got use it a few days too.
bininga59 said:
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
Click to expand...
Click to collapse
this guide is for SM-G780F, the model is SM-G780G, the guide is for exynos version, i have the snapdragon version but without 5g(SM-G780G), since the chipset is different, i cant see how it works
leokratos17 said:
this guide is for SM-G780F, the model is SM-G780G, the guide is for exynos version, i have the snapdragon version but without 5g(SM-G780G), since the chipset is different, i cant see how it works
Click to expand...
Click to collapse
rooting is pretty universal at the moment barring a couple OEM specifics. pretty much all Samsung phones root the same way.
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
leokratos17 said:
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
Click to expand...
Click to collapse
I have the same version, sm g 780g without the 5g (Brazilian version) can you help me to root?
leokratos17 said:
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
Click to expand...
Click to collapse
I also have this s20fe G780G 4g model I'm from Brazil, make a Tutorial help and...
The "OEM unlock" option I missed first but suddenly, after updates of the pre-installed apps and reboots, I got it.
I haven't tried to root as far and directly on front of my vacation.
Hit a wall trying to unlock BL, enabled in dev options and adb into DL mode but LONG PRESS VOL UP is not working! So there is no way to actually unlock BL!??!!?
WTF?