I have a smt-210 with custom rom.
The rom has stupid security policies and does not allow you to navigate to settings. The whole settings section is blocked.
Wifi is disabled . GPS is disabled. Any connectivity is disabled even the usb debugging/connecting is disabled.
They have modded framework-res and if u try to access any of these u get a message saying settings blocked
My problem is while trying to boot in recovery mode there was a soft reset and the system time got reset to 2012.
Now some applications in the rom are set to work only for a limited period of time. Those are commercial apps and are built that way. I need to change the date back to the current date so that they work.
I can connect to adb shell in recovery mode.
I have tried
Code:
date -s "20140822.175400"
But i get
Code:
date: can't set date: Function not implemented
Sat Sep 22 17:54:00 CEST 2012
What is this error ? Have they changed the date binary ? Is it disabled at kernel level ?
Is there any other way to set the date using adb shell?
i cannot ask the developers of the rom for support because this will enable me to have a time reset on the apps and use them indefinitely. Which they wont like.
I have been looking at this
HTML:
http://thecodeartist.blogspot.in/2011/03/simulating-keyevents-on-android-device.html
but its very tedious and would not work as i have not seen the settings UI of the rom.
The options that i can think of is
1) back up the rom using trwp, install a new rom , change date in that rom and install back this rom.
But this process is quite risky and anything goes wrong. I will have to buy a new tab which i cannot afford right now.
2) back up the rom using twrp and install it on an emulator. But i cannot see a proper emulator for tab 3. The one available on samsung's website
HTML:
http://developer.samsung.com/android/tools-sdks/Samsung-GALAXY-Tab-Emulator
is not compatible with
HTML:
http://developer.android.com/sdk/index.html
. I tried to follow the instructions on Samsung's website but eclipse bundle has been updated and settings are not present as they describe.
I am choosing twrp because it has so many options. But it cannot change system time. Do you know a recovery that lets you change the date ?
hmm
hey,
so are you asking for help to rip-off a developer ?
m
i was asking for help in modifying a tab that i own. I guess thats what we do here ?
I was asking help on modifying system time, If u dont know how to do that its ok.
There are 20 different ways to rip developers off. You can just card there soft. You can find modded apks. etc
Please tell me you have never used a paid modded application.
hmmm
@the_bond
hi,
trying to and or fixing stuff in xda yes.
the fine print of your question? no.
your attempt at deflecting what is an honest question AND as subtle a hint that i could make, is far less productive
than simply amending your initial query to be more...friendly. savvy?
m
I'd like to help too but I'm in the same boat as moonbutt74. This sounds rather dodgy.
What exactly is this custom ROM and why is it locked down the way it is? Answer this question honestly without deflecting the question and I might help you.
Is there any way to switch this from enforced to permissive? I use a program called arliberator. It mirrors the phone acreen onto the head unit in the car, the only flaw is that it only works in permissive mode.... any help will be much appreciated.
There is an option for this inside wanam exposed but I don't know if it works and you must be rooted.
Im rooted of course, through the tmobile method, will try wanam in a sec but doesnt knox have to be disabled?
So wanam didnt work
Please inform us if it works. If mine comes in today i will post also
It didnt work, i tried the commands through terminal emulator as well and no dice. We'll probably have to wait until a custom kernel is released, on the other hand i have sound working in the car just can't mirror the screen.
Bump
Bump
The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a Qualcomm SoC at their core. This includes the S10 and S20 series, the N10 and N20 series, the A10 - A70 series, the Tab A and Tab S series, Z Flip and (Z) Fold devices, and many more.
When flashed onto a compatible device, the multi-disabler will semi-permanently disable a number of device protection features and services that become problematic on a rooted device. Some pose a threat to the rooted state of the device, while others become dysfunctional and generate a flood of log messages. Semi-permanently in this context means that the disablement will persist until re-enabled by the user, for example as a side-effect of flashing new firmware with Odin. You will therefore need to reflash the multi-disabler every time you perform a system-wide firmware update.
The methodology of the multi-disabler is the path of least intervention. This means that for any given device, only those services that must be disabled to ensure the smooth operation of the device will be tackled.
The following is a list of features disabled by the multi-disabler on Samsung devices launched in 2019:
FBE (file-based encryption): Until this is disabled, most versions of TWRP — all for Exynos devices and many for Qualcomm — cannot read files on /data (the userdata partition). You must format /data to actually remove FBE after disabling it. Back up your data first!
Vaultkeeper: Magisk now dynamically disables this during boot, but if you boot outside of Magisk, it will return with a vengeance on some devices.
Process authentication (a.k.a. proca): This service must be disabled on some devices in order to use a custom kernel without problems. Note that all 2019 devices with TWRP utilise a custom kernel for Android, because the same kernel is shared by Magisk to boot the system. This does not apply to devices lauched in 2020 and later.
Stock recovery auto-restoration: In certain circumstances, your device will automatically restore its stock recovery partition, overwriting your custom recovery (TWRP). Magisk now also provides dynamic protection against this, but again, this will not save you if you boot outside of Magisk.
wsm: On Android 10 and 11, this service prevents Samsung smartwatches from connecting to the Galaxy Wearable app.
Extra services are disabled as needed per device.
Furthermore, when the ZIP file is renamed to contain the string _btfix somewhere in the name and the file is then flashed on a supported Android 10 device, the system's libbluetooth.so library will be patched in situ to prevent the loss of Bluetooth pairings across reboots. This is a recurring issue with many rooted Samsung devices manufactured before 2020 and updated to Android 10. Devices launched in 2020 and later do not need this patch.
The multi-disabler's support for this solution is limited to a relatively small number of Samsung devices and is deprecated as of v3.0. It will be removed in a future release.
If you find that patching fails on your device, please refer to Arthur Trouillot's superior libbluetooth patcher, which supports a much wider variety of devices.
The multi-disabler is written in Bourne shell, so you can — and ideally should — audit the code yourself to ensure its safe operation. It's performing open-heart surgery on the software of your device, so you should not simply trust it. Apart from anything else, bugs can creep in from time to time, despite or sometimes even because of my refactoring of the code.
The multi-disabler is idempotent, which means you can safely flash it multiple times without incurring unintended side-effects.
The package is attached to this posting and the code is available on GitHub.
Change log
v3.1 (2020-12-30)
Fix failure to detect a Samsung device on some versions of TWRP.
Make deprecated libbluetooth patching also work on devices originally launched on Android 9 and later updated to Android 11.
v3.0 (2020-12-29)
Add support for Android 11.
All Samsung devices running Android 9 or later are now implicitly supported.
Fix bug that caused disablement of stock recovery auto-reflash to fail on Android 10 devices.
Improve progress and error reporting.
v2.6 (2020-10-05)
Add support for the North American Z Fold2 (F916U/U1).
Add support for the A71 (A715F).
Add support for the Note10 Lite (N770F).
v2.5 (2020-09-14)
Fix issue of 2019 devices upgraded to OneUI 2.5 (DTH firmware) not booting after flashing.
Add failsafe logic for robust mounting of System partition by devices using very recent TWRP builds from the Android 10 branch (e.g. S20, N20, Tab S7 and Z Fold2).
Disable cass service on S10 and N10 series devices (required for OneUI 2.5).
Added an extra path to files searched for Vaultkeeper service disabling.
Added an extra path to files searched for cass service disabling.
Added support for the Z Fold2 (F916B/N and F9160).
v2.4 (2020-09-10)
Added support for many new 2020 devices, such as the S20 and Note20 ranges, as well as the Tab S7 and Tab S7+ ranges.
Fixed mode of patched Bluetooth library to match original.
Other minor bug fixes.
v2.3 (2020-04-11)
Support Snapdragon-based devices that have been upgraded to Android 10, such as the F900[FN] (Fold), F907[BN] (Fold 5G), T860 (Tab S6) and T865 (Tab S6 LTE), as well as Asian S10 and Note10 models.
Improve robustness of libbluetooth patching.
v2.2 (2019-12-13)
Disable wsm service to allow Samsung smartwatches to connect to Galaxy Wearable app (thanks to Andrei Seitan).
Support optional patching of system libbluetooth.so for retention of Bluetooth pairings across reboots (thanks to Arthur Trouillot).
Remove undocumented interactive mode.
v2.1 (2019-12-04)
Fix disabling of Vaultkeeper and proca in the vendor interface manifest.
Add support for N971N (Korean N10 5G).
v2.0 (2019-11-30)
Add support for Exynos-based devices upgraded to Android 10.
Add support for T72[05].
v1.7 (2019-10-20)
Add generic support for Qualcomm devices.
Support the Qualcomm S10 (G9700, G9730 and G9750), Note10 (N9700, N9750 and N9760), Tab S6 (T860 and T865) and Fold (F900F and F907B) ranges.
Add support for more Korean (N type) variants.
v1.6 (2019-09-18)
Add support for more variants of A50: A505([YG]N|G).
Fix A205G detection.
v1.5 (2019-09-13)
Added support for A10 - A50 and Tab A 10.1.
v1.41 (2019-08-28)
Added support for N976B (Note 10+ 5G).
v1.4 (2019-08-28)
Changed regex that caused too much of $ANDROID_ROOT/init.rc to be commented out by some versions of sed(1).
v1.3 (2019-08-18)
Updated to work with TWRP 3.3.1-6_ianmacd and later for the S10 range.
Added support for Note 10 and Note 10+ F and N model devices.
v1.2 (2019-06-17)
Added support for G977B (S10 5G) model devices.
v1.1 (2019-04-22)
Fixed stock recovery auto-reflash prevention.
Added support for N (Korean) model S10 devices.
v1.0 (2019-04-09)
Initial version, supporting F model S10 devices.
Will this in some way remedy the problem that when powering off the S10, it wont listen to they keycombo to boot into TWRP anymore?
If one is in system, and do a reboot all is fine, it will heed the keycombo and let you into TWRP to do what you want and then reboot->recovery to start system with root.
But as soon as the device is turned completely off, it breaks.
Just a question: is this to be flashed after rooting with johnwu magisk root process or which rooting method would u advice?
cheers
Nextasy said:
Just a question: is this to be flashed after rooting with johnwu magisk root process or which rooting method would u advice?
Click to expand...
Click to collapse
If rooting with Magisk alone and in accordance with John Wu's instructions, this disabler isn't needed. If you're going to use a rooted TWRP image instead of stock recovery, however, then you're probably going to want to flash it.
So this basically would work for and with the "TWRP for Galaxy S10 Magisk Prepatched by geiti94" and not with John's!?...
After applying this patch and everytime l reboot my devoce it will reboot directly to rooted magisk environment without me going thru' the hassles associated with Johnwu magisk boot procedures?
Thanks for ur time to reply and the mod.
cheers
does the disabler in the twrp thread also need to be applied? or does this replace it?
Nextasy said:
So this basically would work for and with the "TWRP for Galaxy S10 Magisk Prepatched by geiti94" and not with John's!?...
After applying this patch and everytime l reboot my devoce it will reboot directly to rooted magisk environment without me going thru' the hassles associated with Johnwu magisk boot procedures?
Click to expand...
Click to collapse
No, this disabler has no effect on the need to hold down keys to boot the recovery partition.
tensux said:
does the disabler in the twrp thread also need to be applied? or does this replace it?
Click to expand...
Click to collapse
This one effectively supersedes the one in the TWRP thread, because that one disables only FBE encryption, while this disables several other things.
ianmacd said:
This one effectively supersedes the one in the TWRP thread, because that one disables only FBE encryption, while this disables several other things.
Click to expand...
Click to collapse
thanks, i am going to try it again. i have been able to get into twrp on the first try, but it always reboots after the Samsung logo comes up and it looks like its going to boot
tensux said:
thanks, i am going to try it again. i have been able to get into twrp on the first try, but it always reboots after the Samsung logo comes up and it looks like its going to boot
Click to expand...
Click to collapse
Same here... twrp+multi disabler+format data+wipe cache+soldier's zip (in that order). Everything was fine until I pressed power off. Needed to go all over again... and am wondering if it really pays off of having twrp......
ianmacd said:
No, this disabler has no effect on the need to hold down keys to boot the recovery partition.
Click to expand...
Click to collapse
Thanks. But l can flash it after rooting with "TWRP for Galaxy S10 Magisk Prepatched by geiti94"?
dr4go said:
Same here... twrp+multi disabler+format data+wipe cache+soldier's zip (in that order). Everything was fine until I pressed power off. Needed to go all over again... and am wondering if it really pays off of having twrp......
Click to expand...
Click to collapse
seems like only a very small amount of people have been able to get it to work. the procedures are more complicated than with past phones, but i wonder if there could be a very specific version of bootloader we need to have flashed, not just any of the ASCA's
dr4go said:
Same here... twrp+multi disabler+format data+wipe cache+soldier's zip (in that order). Everything was fine until I pressed power off. Needed to go all over again... and am wondering if it really pays off of having twrp......
Click to expand...
Click to collapse
And, really, I think at this point that ppl saying it working for them actuallly never tried a true power down.
I still think therefore that all have the same problem. If you shutdown your phone manually or run out of battery, you are screwed.
PiCkLeS said:
And, really, I think at this point that ppl saying it working for them actuallly never tried a true power down.
I still think therefore that all have the same problem. If you shutdown your phone manually or run out of battery, you are screwed.
Click to expand...
Click to collapse
What I didn't understand is what happens once you turn off the phone ?? Brick unrecoverable ??
Or it must be redone all starting from download mode and stock firmware, what interests me to know is only if the phone is easily recoverable or you risk big.
drago122 said:
What I didn't understand is what happens once you turn off the phone ?? Brick unrecoverable ??
Or it must be redone all starting from download mode and stock firmware, what interests me to know is only if the phone is easily recoverable or you risk big.
Click to expand...
Click to collapse
What I mean is that few ppl actually turn off their phones. But if they do they are stuck with no way to boot system at all or able to boot into twrp recovery .
Most just reboot and there the keycombo works fine.
So if you have the twrp solution done, and power down your phone (off, not reboot) yes you probably must start over from the beginning.
PiCkLeS said:
What I mean is that few ppl actually turn off their phones. But if they do they are stuck with no way to boot system at all or able to boot into twrp recovery .
Most just reboot and there the keycombo works fine.
So if you have the twrp solution done, and power down your phone (off, not reboot) yes you probably must start over from the beginning.
Click to expand...
Click to collapse
Ok but you don't risk a hard brick, you have to start again from the download mode and the stock firmware must be put back and then everything else, correct?
drago122 said:
Ok but you don't risk a hard brick, you have to start again from the download mode and the stock firmware must be put back and then everything else, correct?
Click to expand...
Click to collapse
Yes.
PiCkLeS said:
Yes.
Click to expand...
Click to collapse
Thank you for the clarifications
drago122 said:
Thsnk you for the clarifications
Click to expand...
Click to collapse
You are welcome
Hi everyone,
I really need device encryption in order to be able to use my tablet with a work profile.
Has anyone ever done this with this device?
I have tried with LOS 17.1 and 14.1 by @davidmueller13 but unfortunately it reboots, then tells me it is encrypting (with the pending time displayed) and after that reboots again. I am then prompted to put in my pin (which I set before of course) and after that it is just stuck at the bootscreen / LOS logo for hours.
Any help is greatly appreciated.
With the P605 and various other older devices w/o encryption by default and a custom rom, all my attempts ended with bricking the device...
There may also be a significant performance penalty, the older the device.
lecorbusier said:
With the P605 and various other older devices w/o encryption by default and a custom rom, all my attempts ended with bricking the device...
There may also be a significant performance penalty, the older the device.
Click to expand...
Click to collapse
with LOS 16 I got it to work
Thanks a lot!!! I am gonna give it a try.
Alright @Tronje , thanks to your advice I have a working encrypted device.
Unfortunately the system patch level it too old. I cannot set up the working profile due to that.
Any further advice?
I am no software expert, but I do not get why in LOS16 this feature works flawlessly while in the other builds it is not supported.
MaKel89 said:
Alright @Tronje , thanks to your advice I have a working encrypted device.
Unfortunately the system patch level it too old. I cannot set up the working profile due to that.
Any further advice?
I am no software expert, but I do not get why in LOS16 this feature works flawlessly while in the other builds it is not supported.
Click to expand...
Click to collapse
I am also only a user and cannot explain, sorry.
With maas360 In my company everxthing is good for the moment.
I think you have to ask the developer/ maintainer.
Alright, I am one step closer to what I am looking for.
I have managed to encrpyt LOS 14 by reducing my filesystem size via TWRP Terminal in order to gain some space for the crypto footer.
LOS14 has a security patch level sufficient for setting up with Microsoft Intune. Nevertheless, even though my tab is not rooted, Microsoft Intune somehow detects root. Any bright ideas on why that is happening?
Hello,
I have a problem with mac address on Oneplus 9 pro LE15BA OOS 11.2.10.10. Every time i reboot device i see slightly different mac address in settings even though i disabled mac randomization in wifi settings. Has anyone run into the same problem?
I just got a Oneplus 9 LE2115 and am seeing the same issue, my Unifi control panel is littered with mac addresses from the same phone (one for each reboot) even though i chose "Device MAC" for that SSID!
The problem is the Device MAC itself keeps changing.
So. Dumb.
.
You could log it as a fault on the OnePlus community forum, they'll ask you to supply logs.
Have anyone solve this problem？
dementate said:
I just got a Oneplus 9 LE2115 and am seeing the same issue, my Unifi control panel is littered with mac addresses from the same phone (one for each reboot) even though i chose "Device MAC" for that SSID!
The problem is the Device MAC itself keeps changing.
So. Dumb.
Click to expand...
Click to collapse
So glad I found this post! I have the same problem on my OP9 with Unifi, but it's infuriating me as I have MAC address filtration setup so it's breaking my wifi security situation. Has anyone else figured out how to solve this? If not, this phone is completely unusable on my home network. My 10 Pro does not have this issue.
centifanto said:
So glad I found this post! I have the same problem on my OP9 with Unifi, but it's infuriating me as I have MAC address filtration setup so it's breaking my wifi security situation. Has anyone else figured out how to solve this? If not, this phone is completely unusable on my home network. My 10 Pro does not have this issue.
Click to expand...
Click to collapse
It seems to be a bug specific to the op9 a12 update. One idea is to root your phone and force the MAC, at least until it's fixed properly
Appreciative said:
It seems to be a bug specific to the op9 a12 update. One idea is to root your phone and force the MAC, at least until it's fixed properly
Click to expand...
Click to collapse
Ah good to know, thanks for the reply. Did you read this in another post?
I am rooted, and have seen mention of using an Xposed module, but I'd rather not mess with that as I have had issues with it in the past and don't have a real need for any specific Xposed functionality.
Also have seen the following command
busybox config <net int> hw ether XX:XX:XX:YY:YY:YY, but unsure if this would be risky.
Any thoughts?
I'm wishing A13 would come out of beta....hopefully that'll fix it
centifanto said:
Ah good to know, thanks for the reply. Did you read this in another post?
I am rooted, and have seen mention of using an Xposed module, but I'd rather not mess with that as I have had issues with it in the past and don't have a real need for any specific Xposed functionality.
Also have seen the following command
busybox config <net int> hw ether XX:XX:XX:YY:YY:YY, but unsure if this would be risky.
Any thoughts?
I'm wishing A13 would come out of beta....hopefully that'll fix it
Click to expand...
Click to collapse
I haven't used macchanger in years but there used to be multiple versions in the play store. They all required root. They did all work at the time but this was pre-magisk. I haven't looked for a magisk module that may do the same. Or if termux (or termux+busybox) may support macchanger or setting device mac like you show in your example.
I read that this is a bug on OP9 a12 on reddit and also on xda. I also came across the following information in this thread:
[MOD][XPOSED][12-13] MACsposed - Restore support for setting custom MAC addresses on Android 12 and 13.
MACsposed Historically, setting a custom MAC address on Android was very easy for rooted users. Starting with Android 12, however, Google's implementation of MAC address randomization has made it impossible, as the MAC address is always changed...
forum.xda-developers.com
MACsposedHistorically, setting a custom MAC address on Android was very easy for rooted users. Starting with Android 12, however, Google's implementation of MAC address randomization has made it impossible, as the MAC address is always changed when the network state is altered. If you have encountered this problem, then you need MACsposed! MACsposed is an Xposed module that blocks the MAC address randomizer on Android 12 and 13 and allows you to once again make use of your favorite tools for setting your MAC address
Click to expand...
Click to collapse
I haven't tried it but I'm positive there is a way to achieve setting the Mac, whether xposed, magisk, or busybox/tools available, someone will have it available. Sorry I don't know more yet. Please report back what you find out, for others facing the same problem.
As for it being risky, write down your real MAC before you do anything for peace of mind. I hope there's a magisk module available, I don't particularly like using xposed for the same reason as you, had a few modules causing weird stuff to happen years ago and try to avoid it whenever possible
Goodluck.