Yeah from what I am reading as well, TWRP does NOT auto loki >_>
Edit: Newb hammer for me, seems like Adams version auto loki's independently.
Edit: Newb hammer for me, seems like Adams version auto loki's independently.
Last edited:
I assume you're looking for the OTA update APKs? Here they are:... Also, I need the name of the update APK so I can target and kill it with CASUAL. ...
A custom icon is a small price to pay for not having a brick upon firmware update.I assume you're looking for the OTA update APKs? Here they are:
AT&T Software update V42_1_1303_5_1 (com.wssyncmldm) - wssyncmldm.apk & odex
FWUpgrade 1.2.0 (com.sec.android.fwupgrade) - FWUpgrade.apk & odex
LocalFOTA v2_1303_2_1 (com.LocalFota) - LocalFOTA.apk
Also, if you are planning to delete/remove these, it will likely make the "Custom" icon permanent until the user restores them or returns to stock.
I have them froze through Titanium and it does not cause the custom icon. Freezing may have a different result than deleting, but it shouldn't.I assume you're looking for the OTA update APKs? Here they are:
AT&T Software update V42_1_1303_5_1 (com.wssyncmldm) - wssyncmldm.apk & odex
FWUpgrade 1.2.0 (com.sec.android.fwupgrade) - FWUpgrade.apk & odex
LocalFOTA v2_1303_2_1 (com.LocalFota) - LocalFOTA.apk
Also, if you are planning to delete/remove these, it will likely make the "Custom" icon permanent until the user restores them or returns to stock.
Freezing them the apks are still on the phone so system checks see them there, with them frozen they just don't runI have them froze through Titanium and it does not cause the custom icon. Freezing may have a different result than deleting, but it shouldn't.
This was addressed in maybe the third or fourth post. It isn't a bootloader unlock, but it circumvents security in a way that let's one flash things as if there was an unlocked bootloader.silly question i guess, this method (loki) completely unlock the bootloader?
i noticed that you said this wont work for Verizon version, but will you be making a cross platform version to work with all models?I haven't installed a custom ROM yet, I've been focused on deploying recovery thus far. I don't have that "custom" on my phone.
No, It will try to root, but it won't install the kernel. I've blocked that. I can whitelist that device if you can prove it works.
No it installs twrp for you. Just reboot into recovery. Isn't it vol down+power?Do i have to run Casual every time i need to go into twrp recovery? I dont see anything on my apps. Even pressing the vol up+Home+power does not work.
Email me a proper recovery and a VZW build.prop. I will add it to the nightlies.i noticed that you said this wont work for Verizon version, but will you be making a cross platform version to work with all models?
I just figured it out...its still the vol up+power. I just pressed the buttons too long, so it just reboot everytime.No it installs twrp for you. Just reboot into recovery. Isn't it vol down+power?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Great point. I'm wondering if your tool can move/rename the files, with a simple set of instructions/commands to put them back how they were (with of course a clear warning what the risks are)? I know it's extra coding/time, so I could completely understand skipping this.A custom icon is a small price to pay for not having a brick upon firmware update.
That's what I've done, and it works rather well.I have them froze through Titanium and it does not cause the custom icon. Freezing may have a different result than deleting, but it shouldn't.
This seems to be the case. When freezing them, it leaves them in-place, and so when it does scan (btw, if you are fast enough after a restart, you can go into "about device" and watch it scan for a bit before it determines "custom" or "official"), it sees the files intact and counts it as "official".Freezing them the apks are still on the phone so system checks see them there, with them frozen they just don't run
I think the scan does more than just determine "custom" status, so disabling it might be damaging to the phone functioning properly. However, at some point the scan has to determine if changes sufficient enough have occurred to warrant custom status or not. There has to be code that determines if the custom status (and unlock icon) appears upon the next boot or not.Great point. I'm wondering if your tool can move/rename the files, with a simple set of instructions/commands to put them back how they were (with of course a clear warning what the risks are)? I know it's extra coding/time, so I could completely understand skipping this.
Related: is there any way to freeze or disable an application apart from using TiBu? I know it's possible to freeze some apps through the stock Application Manager, just not these three (among some other 'critical' apps). It would be nice to just disable these and other bloatware with nothing but root access and a script. Not everyone has TiBu like we do.
That's what I've done, and it works rather well.
This seems to be the case. When freezing them, it leaves them in-place, and so when it does scan (btw, if you are fast enough after a restart, you can go into "about device" and watch it scan for a bit before it determines "custom" or "official"), it sees the files intact and counts it as "official".
Related but getting off-topic from the thread a tiny bit: this "scan" it does in About Device seems to be what triggers the bootloader to show the Custom icon. I'm curious if it would be possible to omit/disable this scan before it flags the system as custom? I would imagine that if the scan were disabled/removed while the status was still "official", it might not ever flag the boot as being custom ever again. *shrug*
Any devs here willing to take this one on and get it included in AdamOutler's tool?![]()
Not knowing much about the scan itself, this is also my understanding of the higher-level logic that the phone follows. Here's some more observations that might help:I think the scan does more than just determine "custom" status, so disabling it might be damaging to the phone functioning properly. However, at some point the scan has to determine if changes sufficient enough have occurred to warrant custom status or not. There has to be code that determines if the custom status (and unlock icon) appears upon the next boot or not.
I would think it would have to be similar to the scan returning a "1" if it detects custom or a "0" if it does not (official). If it detects "1", further instruction is given for it to place the unlock icon on the screen and show status as custom upon the next reboot.
I wonder if it would be feasible to locate where that code is, and then change it so it permanently acts as if the scan returns a "0" (official) every time no matter what it finds.
Of course, this is just speculation.
I just figured it out...its still the vol up+power. I just pressed the buttons too long, so it just reboot everytime.
So basically, as soon as i see the message "recovery bootin....", i let go the buttons right away.![]()