So a Question,
Can the OEM unlock be toggled back to Disable by any other way, other than doing it manually in developer settings?
Like from a Factory Data Wipe, ODIN Rom Install, Smart Switch ROM Install or something?
I've just enabled it, and I used a Deodexed settings apk in my rom to use a few mods. Now after a ROM update, the SecSettings.apk is odexed again, and that part of the settings is no longer accessible. So wondering whether the Rom would surprise me with a "Custom Binary locked by FRP" someday...
Thanks!
Well by Installing Custom Rom That Would not Change OEM Unlock to Off.
But I am not sure about installing official firmware about Odin.
Download developer option Shortcut App on play store and check the setting by your self.
Related
Few questions
1. I have sprint and nexus 6. Ideally I'd like a stock rom, but with the clear recent tasks button in the bottom, and enabled tethering, and also rooted. What minimalist or close to stock rom would you suggest? I am tired of using stock and having a pain every time there is an OTA update whereby it won't flash and having to go through the steps of editing build.prop and the sql database file to enable tethering.
2. What is the easiest way to keep a custom rom up to date. I just want it to almost behave like stock with updates easy to obtain and near automatic. Is there an app or rom that has this feature?
3. what is the difference between factory build LMY48M and LMY47Z? They are both listed as 5.1.1
4. I use titanium backup. However, if i update a rom and just save user data (when i previously had it save system data I had a problem) and after i flash restoring user data, I notice many of the settings such as my bluetooth and smart lock etc. settings aren't saved. Any suggestion to streamline the flashing process further?
Thanks for your help and advice!
deadave said:
Few questions
1. I have sprint and nexus 6. Ideally I'd like a stock rom, but with the clear recent tasks button in the bottom, and enabled tethering, and also rooted. What minimalist or close to stock rom would you suggest? I am tired of using stock and having a pain every time there is an OTA update whereby it won't flash and having to go through the steps of editing build.prop and the sql database file to enable tethering.
2. What is the easiest way to keep a custom rom up to date. I just want it to almost behave like stock with updates easy to obtain and near automatic. Is there an app or rom that has this feature?
3. what is the difference between factory build LMY48M and LMY47Z? They are both listed as 5.1.1
4. I use titanium backup. However, if i update a rom and just save user data (when i previously had it save system data I had a problem) and after i flash restoring user data, I notice many of the settings such as my bluetooth and smart lock etc. settings aren't saved. Any suggestion to streamline the flashing process further?
Thanks for your help and advice!
Click to expand...
Click to collapse
you do realize that all you have to do to update a rooted stock rom is flash the system.img via fastboot, then quickly reroot(flash the supersu file)? yes, its that easy.
oh, and i backup my apps and settings through google. every time i wipe, google will restore all my apps, my wallpaper, and my system settings.
/data/data/com.android.providers.settings/databases/ doesn't have to get changed if you just flash system img?
deadave said:
/data/data/com.android.providers.settings/databases/ doesn't have to get changed if you just flash system img?
Click to expand...
Click to collapse
no. that is if you don't wipe data. you wont lose any data flashing just the system.img. you will lose SuperSU though. but all you have to do is reflash it.
Is there a TWRP for the Nexus 6? Can I go from stock rooted to CM12 & back without bricking?
RichTJ99 said:
Is there a TWRP for the Nexus 6? Can I go from stock rooted to CM12 & back without bricking?
Click to expand...
Click to collapse
Yes, TWRP is available for the Nexus 6.
And yes you can go from stock rooted, to a different ROM (CM12 if you want) and back without any problems.
Good Morning,
I have a carrier unlocked Australian N950F Exynos Note 8 running 7.1.1 with OEM Unlock showing in developer settings (took a week or so). My phone has downloaded but not yet installed this OTA:
N950FXXU3CRC7/N950FOLN3CRC7/N950FXXU3CRC7 (1021.03MB)
I think it'll be Oreo but I haven't checked which exact version.
I have not installed TWRP or rooted this phone yet but I'd like to do so. I'd also like to move to Oreo before I proceed as my battery life could be better.
What is the best way to proceed? I've read through some long threads and ended up confused about exactly what's the best procedure.
Is some kind or decryption required at some point? Will I lose the data currently on my phone?
I haven't installed the OTA update yet.
Thank you.
CRC7 is Oreo, 8.0 which is currently the latest for Note8 (8.1 may be a long while out if we even get it officially).
The process for rooting Oreo is basically the same as Nougat, for Oreo just be sure you are using the updated TWRP that fixes the data mount issue.
If you root Nougat first, you won't be able to update OTA so you'll then need to install a custom rom to get Oreo.
You can update to Oreo via OTA first & your data will be intact but regardless if Oreo or Nougat, after installing TWRP you'll need to wipe data to remove encryption. So yes, you will loose data. You won't loose internal or external storage unless you choose to format them but it's a good idea to make a backup of them just in case.
As for data, you'll need to use smart switch, helium, etc if you want to back it up. I have no experience with backing up data without root so I'm not sure what methods work best.
It seemed to work. I restored all my contacts, apps etc in Oreo. When I went to restart the phone and enter TWRP to flash magisk I get a message about only official binaries are allowed. Now the phone won't even boot. I'm guessing I now need to re-flash official firmware with odin just to get my phone working? Another week for OEM unlock? I waited this long because I thought the problem was resolved
Unfortunately if you have the OEM lock issue, that will never go away. So yes, you have to flash official firmware to boot again. If you were on Oreo, you can try flashing Nougat to see if you might get lucky & get OEM unlock back.
Since you have the OEM lock issue, remember to always flash the RMM state fix even if you flash a custom rom that has the fix built in. Always flash RMM fix right after flashing a custom rom. If not flashing a custom rom, flash RMM fix before booting to system after you install TWRP.
Thanks for the reply.
Was I supposed to install Samsung AntiRoot Removal and RMM State Bypass as per this guide? Is this guide the correct method?
galaxynote8root.com/galaxy-note-8-root/how-to-root-galaxy-note-8-on-android-8-0-oreo/
I'm currently downloading Oreo 8.0 XSA (unbranded Australian rom) to reload my phone and wait another week.
I would like to use the XSA Samsung rom rather than a custom rom. Is OEM Unlock available in Oreo after a week?
Thank you
I use the method listed in any of the TWRP threads. I've never heard of Samsung Anti Root Removal. By the sound of it on the page it sounds like dm no verity. You need to flash that & RMM state fix. Flash the XSA firmware you want to use. Log into your Samsung account, don't reboot for 168hrs & OEM unlock should appear. Then follow a guide for installing TWRP.
Hello Friends,
I just want to know that OEM toggle will be missing or not in developer option when i will be booting my phone first time after install custom rom? AS it is written in Ironman Rom install instructions that choose NO ROOT if you install rom first time due to dalvik-cache. So, if OEM toggle will be missing then how i gonna root my phone?
Thanks in advance
the toggle should be there showing it's already unlock.
I remember that in the first releases of Ironman Rom (nougat times) the toggle was hidden by the dev. To prevent users for disable it accidentally. But normally it should be available and enabled.
If you don't see it, don't reboot your device for the next 7 days (168h) and it should be visible again.
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts
Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.
Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.
I'm aware I can restore to stock via odin. But I have a couple of questions.
A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?
And
B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)
Thanks in advance for any help you can provide.
This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock
ZeroXO said:
This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock
Click to expand...
Click to collapse
Okay I was thinking I might of missed something. The patch for oem issue I thought covered that.
Is the unknown (bat) firmware the one I need to flash to stock?
Sent from my OnePlus6T using XDA Labs
TheLogicalGamer said:
Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.
Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.
I'm aware I can restore to stock via odin. But I have a couple of questions.
A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?
And
B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)
Thanks in advance for any help you can provide.
Click to expand...
Click to collapse
Using odin 13.1.3 is recommended.
As you have the N950F, it is part of the multi OXM CSC, so you can flash the filmware for you country and carrier if desired (N950F)
If you want to root, I suggest just flashing a custom rom or kernel, as they have been patched for the RMM KG state issue.
Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.
awambawamb said:
Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.
Click to expand...
Click to collapse
Google fastboot flash with PC or recovery flash via custom Recovery.
For both the bootloader has to be unlocked. In my opinion there's no other way to rollback .
I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A
awambawamb said:
....
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide......
Click to expand...
Click to collapse
I advise to search for the right information on XDA and the downloads from Xiaomi servers.
awambawamb said:
I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A
Click to expand...
Click to collapse
Downgrading using the rename trick is not possible now due to OTA validation. But still, downgrading is still possible as long as the bootloader is unlocked (you can re-lock bootloader afterwards btw so no worry about banking apps).
Procedure might be something similar to this:
1. Unlock bootloader
2. Flash any latest OSS ROM (this is just to remove MIUI)
3. Use MiFlash and fastboot method to install old versions (re-lock if you want)
Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.
PS: Just to add, Anti-Rollback is not yet enabled for sweet so no worries with getting bricked while downgrading. Just be careful and flash appropriately.
Thanks for the kind reply, @BigChungus321 . Glad to hear that I can still unlock and lock the bootloader! at least for those 6 months of warranty.
Just one thing, in the step you suggested you said:
1. Unlock bootloader2. Flash any latest OSS ROM (this is just to remove MIUI)3. Use MiFlash and fastboot method to install old versions (re-lock if you want)Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?
wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?
awambawamb said:
Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
Click to expand...
Click to collapse
It is the same but I do encounter people who face anti-rollback error rejecting the downgrade if flashing from MIUI to MIUI. But going from OSS to MIUI, this arb check does not seem to occur.
awambawamb said:
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?
Click to expand...
Click to collapse
No clue if that prevents the issue/bug you encounter. I usually just dirty flash the full rom update (not the incremental which is around ~200mb) in recovery and I don't seem to get issue this way, aside from recovery being replaced because dm-verity is getting activated again.
awambawamb said:
wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?
Click to expand...
Click to collapse
I've seen many people who have this issue too. Again, no clue how to fix this. Maybe reboot, and just enable mobile data. Try changing sim card or switching sim card slots. Use other Mi Account for unlocking. I did see discussions about how using the same sim card and same Mi account can on a different device can cause this. I still have no clue how to fix this though so sorry. Might be a good idea to use a fresh sim card and mi account if you still encounter it.