Develop Bugs

[HOW TO] build an autosigner for OSX

Ok, so I'm kind of new to automator which is why I'm making this as a tutorial instead of a download.
1. First you need to download the AndroidMod.zip JesusFreke posted
http://android-dls.com/forum/index.php?f=24&t=191&rb_v=viewtopic
2. Copy the three highlighted objects from the SignApk folder to the folder of your choice, I chose one called signapk in my applications folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Open the info window for one of the files in there final destination, keep it open as we're going to use the Where field in the next step.
4. Open Automator and choose a custom workflow. First go to Files and Folders then choose Duplicate Finder Items. What this does is create a duplicate of the file we're going to sign and pass it to the shell script we're about to create.
Then scroll down to utilities and then choose Run Shell Script.
5. Change the drop down for pass inputs from to stdin to as arguments. This allows us to either create an application we can drop files we want to sign onto, or create a finder plugin so we can right click(or ctrl-click if you're on a single button trackpad or mouse) and sign it from there.
6. The basic usage for the signapk.jar included in the android mod file is as follows: java -jar signapk.jar testkey.x509.pem testkey.pk8 <update.zip> <update_signed.zip>
what we need to change is add the absolute path to signapk.jar, testkey.x509.pem, and testkey.pk8. Thats what is listed in the where field in the get info window comes into play, just type everything listed there right infront of each of those three files. In my case thats going to be /Applications/signapk/. We also need to change <update.zip> to "[email protected]" with the quotes. Thats what is actually going to be the input from either dragging and dropping or right clicking. Finally the last parameter we just need to remove because we made a duplicate of the file to be signed, and if theres no final parameter it overwrites the file sent to it. My final shell script is shown in the image below.
7. Save the file as an application if you want to drag and drop files onto it and Save it as a plugin and then select finder if you want to be able to right click and sign. When using a finder plugin you right click and go to more, then automator, then choose the plugin you just saved.
Thats It! whenever you use it it will automatically create a copy of the file you're signing (ex. Launcher.apk -> Launcher copy.apk or update.zip -> update copy.zip) and sign that. The copy is the signed version and the original is left untouched.
Feel free to modify this however you want, if someone wants to release a prebuilt version of this automator action, thats perfectly fine by me, you don't even need to ask for permission. Do whatever you want with it.

Thanks very much! I was getting tired of launching Parallels whenever I wanted to do something like this.

yes super useful, was sick of tossing files back and forth between my computers. definitely needs to be a sticky.

I couldn't get it to work for me with ADP1.1 When I try to boot up with update.zip I get the error that the files were not signed. For argument sake I redid everything a few times. And saved my files exactly where you saved them and still no luck. Any ideas?
::edit:: I think that my problem has something to do with certain files not changing to .apk when I change them back from .zip. Some of my .apks change to that black square that you know are some executable program while the rest remain little white ones. Any ideas on how to change them to normal executable files?

yeah, if you open the info (command + i) on the file you'll see that the file has the .zip hidden. In the info window you can delete the .zip extension and just leave the .apk. Theres a setting somewhere to enable file extensions always, and it's quite nice to have that enabled

I already have it enabled. That is why I can't figure out why some files do that and some don't.
Edit: Finder is reading some of them as Unix executable and others as documents. I guess the trick is trying to figure out how to fix that.

That would be as simple as running chmod on them in the console, however I've never had a problem with that, as long as they're named.apk and not .apk.zip I've never had a problem putting them back on the phone even if osx didn't see them as unix executables

That is the only thing I could think of and chmod did not work. But I am not 100% sure that it is even the files that is the problem.
::Edit:: After testing things a little more I think it has something to do with the signing itself. Even though it makes that copy I don't think it is actually signing the file. Would you be able to upload your program?

i have had the exact same problem as Broopa and its getting really anoying lol could someone please upload the file for us to use.

Anyone have any idea why the folders aren't getting signed. I even installed java from Apples developer site and no luck.

c'mon people...youve all done it can you please send some info our way??

sorry guys I don't know why it's not working now. I'll try to get it fixed and reposted.

Any updates on this? I still can't get it to work.

i created the workflow, saved it as a service for finder, and tried it out.
it creates the dupe file, but pops up with an error message:
The action "Run Shell Script" encountered an error.
there must be something wrong with the script itself, or the arguments being called by it.
is nobody still working on this? i know it's been over a year, but this would be very helpful to have available.

[GUIDE][ROOT][19/Nov] r14: VISIONary + one click root

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: This application is no longer being updated and is only recommended for use on Froyo builds.
What is VISIONary?
VISIONary (so named because it was originally an application designed for the T-Mobile G2 / HTC Vision) is an application you install on your device that allows you to Temproot or optionally Permroot your device, using the 'rageagainstthecage' exploit.
How do I use it?
It's pretty simple really. The options appear as follows:
Temproot on boot - use this to automatically Temproot on each boot (I suggest Temprooting manually first to confirm all is well before enabling this)
Run visionary.sh after root - this allows you to run a script (as root) after rooting. The script file is /data/local/visionary.sh
Set system r/w after root - this allows you to leave the /system partition read/write after root
Temproot now - root temporarily (the root wil be lost after reboot)
Attempt permroot now - attempt to apply a permanent root (please read the safety information below before doing this!)
Unroot now - this will unroot your device
Safety information!
You use VISIONary at your own risk! Although we test it as much as possible, we are unable to guarantee that weird things won't happen.
As a rule, the 'Temproot' option of VISIONary should be completely safe. It installs an application (Superuser) in the conventional way and then sets up a 'ramdisk' for the other parts, which is wiped on boot. As such, no changes are made to the system partition of your device, hence it is considered a 'safe options'.
Permroot on the other hand is inherently more risky. Permroot does make changes to the /system partition of your device. Technically speaking the only change that is made is the installation of a small file to /system/xbin, but any system partition change comes with risks. If you try to permroot, be aware that you might get into a situation where your device will not boot. For this reason, we recommend you have a 'safety net'.
In general, the best 'safety net' for going ahead and doing a Permroot is ensuring that you have a copy of the stock ROM to reinstall should things go wrong. This should be an original update EXE or zip from your device manufacturer / provider which matches the software version currently installed on your device. Bear in mind that flashing older versions is often not possible, so if your device has been updated over-the-air, an update may not yet be available in this form. Hence, you may not be able to find a 'safety net' and attempting to Permroot would be inherently risky. For HTC devices at least, one option would be to Temproot, edit the MISC partition to revert the 'mainver' to an older version, thereby allowing you to flash an update older than the currently installed version should things go wrong. That option is currently outside the scope of this post, although I will provide details on how to accomplish this in another post.
Got your safety net? Aware of the risks? The download is below.
Download
r14 - (see changelog below for details) - [url="http://android.modaco.com/content/software/320350/19-nov-r14-visionary-one-click-root/]DOWNLOAD[/url]
The download is in APK format (if it is downloaded with a 'zip' extension simply rename). Copy to your device and click to install (or run 'adb install -r com.modaco.visionaryplus.r14.apk' if you have the SDK installed).
NOTE: USB DEBUGGING MUST BE ENABLED FOR VISIONARY TO WORK!
And finally
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P

thanks for you guys work

works perfectly! thanks

Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App

Question Answered..
Thank you P, my reboot question has been answered... just click and proceed. (To Be Tested)
It feels so good to see you on the scene.. It's been a while.. Since the N1

v8pwrdz28 said:
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Same here

v8pwrdz28 said:
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Reboot and try again...
P

paulobrien said:
Reboot and try again...
P
Click to expand...
Click to collapse
How long should the program run?

I have no experience whatsoever in developing or rooting on Android, so excuse me if this is a stupid question. When you say that if we want something to happen every time we finish rooting at bootup, to put it in /data/local/visionary.sh, what exactly does that mean? How does one go about doing this?

when i run this it just keeps saying rooting device with spinning wheel at top then it reboots

Not Working
Just getting the spinning wheel and flashing with no progress. Even tried to reboot and start over with no results

Thank you for making my life easier.

Does this app require you to do the "one-time" first step of the temp root process before you can use it?

Like others have said, this doesnt work for me. Just flashes rooting please wait and nothing happens.

Hey thanks it worked .. At first it kept running and nothing happened, so i rebooted the phone and it worked in the first try.

LogicHell said:
Does this app require you to do the "one-time" first step of the temp root process before you can use it?
Click to expand...
Click to collapse
No...
P

What should happen...
Boot device
Click VISIONary icon
Phase 1 runs
Logo disappears briefly as app reloads
Phase 2 runs
App disappears and root is complete
If this doesn't happen, I suggest rebooting and trying again.
P

Does it use the old 'root' script (copy everything to /system/bin and /system/app) or the new method? The old one expires eventually when linux drops the cache, the new one stays forever (until reboot). (Also, putting superuser on /data/app means it remembers it's permissions and grants across reboot, instead of losing it every time.)
The updated script is here:
Disconn3ct said:
FYI I altered the script to survive cache flushes and such. If you use this instead of the old 'root' script (and put everything in /data/local/bin instead of tmp) it will make the bare mininum number of changes to /system and those changes will last until you reboot (instead of flushing out over time).
Click to expand...
Click to collapse

Auto Root
I downloaded Startup Manager from the Market and set VISIONary to auto load on each bootup and so as of right now it auto loads with each restart. Very handy until it auto loads on itself. Just a thought.

Disconn3ct said:
Does it use the old 'root' script (copy everything to /system/bin and /system/app) or the new method? The old one expires eventually when linux drops the cache, the new one stays forever (until reboot). (Also, putting superuser on /data/app means it remembers it's permissions and grants across reboot, instead of losing it every time.)
The updated script is here:
Click to expand...
Click to collapse
Good call on putting the Superuser APK on /system/app! re: the 'old' or 'new' way, i'm doing it the old fashioned way (didn't know there was another way, heh)!
If you can point me to it, i'll change it for r2.
P

[Added Instructions 9/2] Boot/Down Animations from gdi2290

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
gdi2290 said:
I'm going to update this Thread later, when I find time, with my custom animations.
Click to expand...
Click to collapse
Checkout more of my Work:
Splash Screens for Droid Incredible 2 by gdi2290
Stock Sense 3.0 Lock Screen from gdi2290
Forum Signatures for Droid Incredible 2 by gdi2290
Instructions for Boot Animations
Acquire a Droid Incredible 2
Obtain S-OFF
Download the bootanimation.zip
Install Optional: do a nandroid backup​File Explorer method:
1. If not already rename your boot animation to bootanimation.zip (VZW_bootanimation.zip for stock and Skyraider Zeus ROM)
2. Place file in the root of your SD card
3. Download either Root Explorer(recommended) or ES File Explorer
If your apps wont let you write in a read-only you may have to re-Superuser your apps​4. Open Root Explorer Press and Cut/Copy (or Move) bootanimation.zip
5. Go to
In CyanogenMod and other ASOP ROMs the directory for bootanimation are in
/system/media
For any Sense HTC ROMs (Skyraider and Virtuous Unity)
/system/customize/resource​6. In Root Explorer press [Mount R/W] to active [Mount R/O]
7. Rename your existing bootanimation.zip(or VZW_bootanimation.zip) to bootanimation.zip.bak
8. Paste (or Move) bootanimation.zip(or VZW_bootanimation.zip)
ADB method:
1. Download Android SDK
2. Place Android SDK in C:\
3. CD (change directory) in CMD (command prompt) to C:\android-sdk-windows\platform-tools.
4. Rename your boot animation to bootanimation and put it in C:\android-sdk-windows\platform-tools
5. Open CMD (command prompt)
6. Type in order:
-adb remount
-adb push bootanimation.zip /system/media/bootanimation.zip
In CyanogenMod and other ASOP ROMs the directory for bootanimation are in
/system/media
For any Sense HTC ROMs (Skyraider and Virtuous Unity)
/system/customize/resource​-adb reboot​
Reboot your phone
Press the Thanks button on my post.
Changelog
Forum Header, SkyRaider Zeus (boot and down animation)
9/5/2011 04:32 PM
Instructions
9/2/2011 12:15 PM
Edited OP
8/21/2011 10:24 AM
SkyraiderROM boot audio tutorial
8/30/2011 12:11 PM
Changed OP style; Added: Droid Bionic android_audio.mp3; Added: Stock HTC (boot animation );Stock HTC (down animation)
8/29/2011 11:43 AM
Initial Release
8/27/2011 02:09 AM
gdi2290 said:
Skyraider Zeus ROM - adding Audio to BootAnimation
He doesn't like boot audio, so you have to add it back in by editing the <BootConfiguration> in
Code:
/system/customize/CID/default.xml
Press and hold down the file to Select Open in Text Editor
Scroll down to the bottom and edit the <BootAnimation>
you may also want to remove "VZW_" from bootanimation just make sure you do the same in /system/customize/resource
Click to expand...
Click to collapse
Boot Animations
Stock HTC
VirtuousROM 2.33
SkyRaider Zeus
Droid Bionic bootanimation.zip / Bionic Sound (thanks franklin270h)
​Down Animations
install just like bootanimations (backup your old file) and change permissions
Virtuous ROM 2.33
SkyRaider Zeus
Stock HTC
​
If your apps wont let you write in a read-only
you may have to re-Superuser your apps and/or
in Root Explorer press Mount R/W so it can show Mount R/O
Support me by signing up for Dropbox, pressing the Thanks button, rating the thread, reTweet it, and requesting your own custom Splash Screen with the image you likeb

gdi2290 said:
bootanimation.zip
.ogg sound file
Click to expand...
Click to collapse
Can you please explain how to overwrite a current bootanimation? I've tried in several different ROMs to do it and I get an "overwrite failed" error message everytime.
To explain: using ES File Explorer, I copy (already set to R/W using Mount/System rw/ro app) the new bootanimation.zip from my sd card (renamed to match my current animation). I go to system/custom/resources folder and try to do a paste. I get a warning message asking if I am sure I want to "overwrite the current folder (contents will be merged)", I click yes, it looks like it is going work, and then I get the "overwrite failed" message. What am I doing wrong? I'm sure it is something simple I'm missing.
In any case, love your work. Keep it up!

HarleyChick said:
Can you please explain how to overwrite a current bootanimation? I've tried in several different ROMs to do it and I get an "overwrite failed" error message everytime.
To explain: using ES File Explorer, I copy (already set to R/W using Mount/System rw/ro app) the new bootanimation.zip from my sd card (renamed to match my current animation). I go to system/custom/resources folder and try to do a paste. I get a warning message asking if I am sure I want to "overwrite the current folder (contents will be merged)", I click yes, it looks like it is going work, and then I get the "overwrite failed" message. What am I doing wrong? I'm sure it is something simple I'm missing.
In any case, love your work. Keep it up!
Click to expand...
Click to collapse
have you tried to rename your bootanimation.zip.old then paste this new one there. if that doesn't work you may have to re-Superuser your apps

Boot animation looks nice

Looks sweet. Can't wait to try it out.

Just installed. Looks pretty cool. Thanks.

gdi2290 said:
have you tried to rename your bootanimation.zip.old then paste this new one there. if that doesn't work you may have to re-Superuser your apps
Click to expand...
Click to collapse
I finally got the animation to work, but where do you put the sound file?

HarleyChick said:
I finally got the animation to work, but where do you put the sound file?
Click to expand...
Click to collapse
Code:
/system/customize/resource/android_audio.mp3
the file is .ogg not mp3 :\

How do I install down animation?
Sent from my ADR6350 using XDA App

egren58 said:
How do I install down animation?
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
install just like bootanimations (backup your old file) and change permissions

gdi2290 said:
/system/customize/resource/android_audio.mp3
the file is .ogg not mp3 :\
Click to expand...
Click to collapse
I tried renaming it and copying it over, but it still doesn't make any sound on boot.

HarleyChick said:
I tried renaming it and copying it over, but it still doesn't make any sound on boot.
Click to expand...
Click to collapse
I uploaded the mp3 version. Which ROM are you using? I still have to make it delay a few seconds to play correctly
via rooted Droid Incredible 2

gdi2290 said:
I uploaded the mp3 version. Which ROM are you using? I still have to make it delay a few seconds to play correctly
via rooted Droid Incredible 2
Click to expand...
Click to collapse
When I click on your "link" for the mp3 version, it just opens a window and plays the sound - no download.
EDIT: Never mind - I figured it out. DOH!

HarleyChick said:
When I click on your "link" for the mp3 version, it just opens a window and plays the sound - no download.
EDIT: Never mind - I figured it out. DOH!
Click to expand...
Click to collapse
lol yeah in chrome you have to download it since everything is sandboxed

gdi2290 said:
lol yeah in chrome you have to download it since everything is sandboxed
Click to expand...
Click to collapse
I still can't get it to make any sound during boot. I must have something wrong. By the way, using Skyraider Zeus ROM.

HarleyChick said:
I still can't get it to make any sound during boot. I must have something wrong. By the way, using Skyraider Zeus ROM.
Click to expand...
Click to collapse
For SkyraiderROM, he doesn't like boot, you have to add it back in by editing default.xml in
Code:
/system/customize/CID/default.xml
scroll down to the bottom
and edit the <BootAnimation>
Alternatively you can download this edited default.xml file I recommend the above method. Just make sure you rename your old file default.xml.bak
there is also a 1.1 update for Skyraider ROM

gdi2290 said:
For SkyraiderROM, he doesn't like boot, you have to add it back in by editing default.xml in
Code:
/system/customize/CID/default.xml
scroll down to the bottom
and edit the <BootAnimation>
Alternatively you can download this edited default.xml file, BUT I can't say for sure it will work I recommend the above method. Just make sure you rename your old file default.xml.bak
there is also a 1.1 update for Skyraider ROM
Click to expand...
Click to collapse
Okay, well that is way too complicated for me. The animation works fine, its just the sound that is off and I can live with that.
Already have the 1.1 update. Love the ROM, but HATE the boot animation that comes with it.

HarleyChick said:
Okay, well that is way too complicated for me. The animation works fine, its just the sound that is off and I can live with that.
Already have the 1.1 update. Love the ROM, but HATE the boot animation that comes with it.
Click to expand...
Click to collapse
here is a DROID audio lol its still a little off
I know what you mean lol I posted the stock unlock ring and I have downanimation in OP

gdi2290 said:
For SkyraiderROM, he doesn't like boot, you have to add it back in by editing default.xml in
Code:
/system/customize/CID/default.xml
scroll down to the bottom
and edit the <BootAnimation>
Alternatively you can download this edited default.xml file, BUT I can't say for sure it will work I recommend the above method. Just make sure you rename your old file default.xml.bak
there is also a 1.1 update for Skyraider ROM
Click to expand...
Click to collapse
I can confirm that the default.xml you posted does in fact work, people just need to remember to give that file the correct permissions as well.
Droid bionic boot animation is awesome, let us know when you get the sound delayed by a few seconds so it can match up perfectly.

awesome! thank you"!

[How-To] Disable System Updates & Clear Notification

I have seen a lot of posts here asking about how to disable system updates and make that annoying notification go away... So I figured I would post a complete how-to here...
Please forgive my poor syntax for now...I'm typing this on an iPad, I will update this, make it look nice and pretty, and add photos and links when I get home.
REQUIREMENTS
-ROOTED PHONE
-A KERNEL WITH A NON-STOCK RECOVERY (CWM/ROGUE/ETC..)
Disclaimer!!!!
I AM NOT RESPONSIBLE FOR ANY BROKEN PHONES, I HAVE TESTED THIS ON MY PHONE, IT WORKED FINE, THIS HAS ALSO BEEN MY PROCEDURE FOR DISABLING UPDATES SINCE MY G1 AND ALL MY PHONES IN BETWEEN (freeze update package, clear cache)
Also, please read the post in full before doing anything!!!
---
First of all, how do we disable those pesky system updates?
I'll show you a way to do it without any paid apps, you can even do it from adb or quicksshd! (REQUIRES ROOT)
First of all, go and download "terminal emulator" from the market, or if you have adb it can be done via adb-shell or with quicksshd.
you have terminal emulator installed...now what do you do?
Fire it up and type the commands as follows (don't type in the "$" or "#", these simply mean next-command as user and root, also don't type anything in brackets as these are only explanations of what the command is doing)
$ su
[this grants terminal emulator root, accept the permissions]
# pm disable com.samsung
[this disables or "freezes" the package required for system updates]
So what does this mean?....ALL SYSTEM UPDATES WILL BE DISABLED, THIS INCLUDES PRL AND PROFILE UPDATES!! to make sure it worked, go to settings>about phone>system updates, it should shoot you back to the main settings menu.
If you need to reverse this procedure to update your PRL or Profile, type the following:
$ su
[again...grants terminal root]
# pm enable com.samsung
[this enables or "unfreezes" the package required for system updates]
---
But what about that stupid notification? The commands above wont make it go away!!!!
To make the notification go away, simply choose click on it and choose "install" and let it reboot and do its thing....it's not going to work!!!
Why does it lock up on the update, giving you that android and triangle? The default system updater requires a STOCK recovery, as long as you have a kernel with a CWM based recovery installed, it will be impossible for the update to complete
as soon as it locks up hold your power button down and reboot, it will kick you back into CWM recovery, now while here, clear your cache (as that's where OTA updates are stored), i also clear my Dalvik Cache but it may not be necessary, and reboot....now your back in your rom!!!
Finally, before your phone checks for updates again...freeze com.samsung....no more notification, and until you unfreeze com.samsung, it won't bother you about it again.

This may be a dumb question but have to ask or won't know. If I stay with my current rom and have already updated prl and profile I won't need to do that anymore unless I flash another rom.

Normally you won't need to do it when you flash another ROM either, but there can be situations where you need to.
PRL update isn't that useful (at least the ones Sprint gives you) as these days they are just getting rid of more 3g roaming.
Profile update can solve data login issues which arise either from messed up NVRAM or from activating another device, then re-activating your phone.

I usually only update PRL/Profile if I have data connectivity issues, otherwise you shouldn't have to update even if you flash new roms over, usually I need a profile update about once every month and a half or so...give or take.
Just keep in mind that com.samsung is part of the rom, and flashing a new rom will render com.samsung active again
Another nifty tip....the above commands to freeze com.samsung will work for any app as long as you know the com.whatever name.

Titanium "freeze" does the same thing if you like GUI interface.

sfhub said:
Titanium "freeze" does the same thing if you like GUI interface.
Click to expand...
Click to collapse
Do you need to freeze all four (at least on my phone there are four) com.samsung files?
This does seem like an easier way for those of us not familiar with emulator commands.

In titanium backup, the only thing you need to freeze is "System Updates"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Im gonna spruce this guide up as soon as the disaster known as "finals week" is over.....

I went ahead and pm disable com.samsung BEFORE the update push to my phone. Hopefully I will never get the notification since I am happy on Calk 2.0 and EG30 baseband/modem.

Edit:
Thanks starnostar, this works for me.
If you use Swype it may cause you a problem with adding uppercase I to "dIsable" causing command not recognized. Open any input such as google search (any input that open the keyboard will do). Touch and long hold on the input until the input method dialog pops up. Change to Samsung keyboard (ET4G). You can change back to Swype afterwards.
FYI Freeze is only available in the Pro version of Titanium (currently $6.58).

Use antek file manager its free and let u freeze.
Sent from my SPH-D710 using Tapatalk

Or.....you can just edit build.prop to say 2.3.6 & EL13.

12MaNy, where is that file located?

syco123 said:
12MaNy, where is that file located?
Click to expand...
Click to collapse
Its in system. Just open root explorer then go to system and long press build.prop and select "open in text editor". Then change build version to 2.3.6 & EL13 wherever you see it (as applicable). Then click menu key/save. Then back out of root explorer and power down phone then power back on (hot reboot won't work). Then update profile and prl. You might get it one more time after that but that should be it.
Here's a couple images to show you what it will look like.
http://db.tt/p2857Sqz
http://db.tt/bFOZhKni

12MaNy said:
Its in system/media. Just open root explorer then go to system/media and long press build.prop and select "open in text editor". Then change build version to 2.3.6 & EL13 wherever you see it (as applicable). Then click menu key/save. Then back out of root explorer and power down phone then power back on (hot reboot won't work). Then update profile and prl. You might get it one more time after that but that should be it.
Click to expand...
Click to collapse
It is actually in /system
Just backup the original because if you ever want to get a patch-style OTA update, you are going to need to original.
Personally if all you want to do is disable the notifications for updates the pm disable in the first post is pretty simple and won't have any negative effects on updates as you can enable it when you want them.
Alternatively you could try forcing the update to fail by installing it while having some files changed. It may ask later, but so far hasn't asked me.

sfhub said:
It is actually in /system
Just backup the original because if you ever want to get a patch-style OTA update, you are going to need to original.
Personally if all you want to do is disable the notifications for updates the pm disable in the first post is pretty simple and won't have any negative effects on updates as you can enable it when you want them.
Alternatively you could try forcing the update to fail by installing it while having some files changed. It may ask later, but so far hasn't asked me.
Click to expand...
Click to collapse
Yep! Sorry....damn word prediction. Post corrected
....and root explorer auto saves original as .bak file

Thanks guys,
My problem was Swype adding an uppercase I to "disable" causing the command "dIsable", which I didn't notice (doh!). I changed the input method to the basic keyboard temporarily, tried again and so far 12 hours later no message.
The original method was easy, quick and works.

starnostar said:
In titanium backup, the only thing you need to freeze is "System Updates"
Im gonna spruce this guide up as soon as the disaster known as "finals week" is over.....
Click to expand...
Click to collapse
Didn't work for me. I froze it a week ago and just started getting update notifications again today.

I think most of the ROMs in the dev section have been updated to EL13, so just update your ROM/modem and there's no need to fiddle with freezing system updates or modify build.prop.

_MetalHead_ said:
Didn't work for me. I froze it a week ago and just started getting update notifications again today.
Click to expand...
Click to collapse
Yep, they're back for me too.
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
12MaNy said:
I think most of the ROMs in the dev section have been updated to EL13, so just update your ROM/modem and there's no need to fiddle with freezing system updates or modify build.prop.
Click to expand...
Click to collapse
I like the stock ROM but with the bloat removed. Is there a ROM like Starburst with EL13?

Thank u sir...(Starnostar)
Just Froze mine (updates) with Titanium...

How to up date LeEco Le Pro3, no root, no TWRP, 100% Stock

I am a New Pro3 owner, and a old XDA flasher. These days I just want stability and battery life. So given no one is getting OTA updates because the LeEco US office are... well about to close doors? Or at a minimum they are not maintaining the OTA servers as of today (09/06/2017 MM/DD/YEAR). I took it on myself to figure out how to get the updates and how to do them.
What you need:
These three files, nothing else.
5.8.019_sta.zip
5.8.020_sta.zip
5.8.021_sta.zip
Found here.
https://drive.google.com/open?id=0B2EAg2WU3OwpSHRMdEZ0Tks0a3M
It is very simple, but also very finicky.
1. Download 5.8.019_sta.zip, rename to update.zip
2. Place the update.zip on the root directory of your phone storage
3. Go to Settings -> System update (about 3/4 the way down)
4. Top right corner will see three vertical dots, tap the dots and select "local update" (see image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. When you select "local update" if you did everything correct it should say "Update package found bla bla bla". Click continue.
That's it, it will load the file, reboot in to recovery and flash the file.
Then just follow this process for each file 19s->20s-21s. Make sure you remove the last update.zip before you put the new one in place.
Now, here is how it can be "finicky". For some reason using an android file manager to rename the files to "update.zip" corrupts the file in some way... and the update once you get in to the recovery section of the auto update fails. BEST PRACTICE IS TO DOWN LOAD THE FILES TO YOUR PC, THEN RENAME IT ON YOUR PC TO update.zip AND TRANSFER TO YOUR PHONES ROOT STORAGE.
Why? no clue, but you can try it either way... but if you find it failing try ^^

Hi, thanks for sharing the files, nuch appreciated.
For some reason I cannot acces the files today ?

bethe said:
Hi, thanks for sharing the files, nuch appreciated.
For some reason I cannot acces the files today ?
Click to expand...
Click to collapse
https://drive.google.com/drive/folders/0B2EAg2WU3OwpSHRMdEZ0Tks0a3M?usp=sharing
made a new sharable link

Hi and thanks for sharing. If you don't mind could you tell me
what's included in these updates?

dallorsj said:
Hi and thanks for sharing. If you don't mind could you tell me
what's included in these updates?
Click to expand...
Click to collapse
Just google "5.8.019_sta" (for each one)
You should be able to find the change-log somewhere.

Edward,
Works great! Just some notes for everyone else.
1) Make sure phone is set to MTP (Media Transfer Protocol).
2) If you are using Windows and are 'dragging and dropping' onto the device just copy to the phone icon in file explorer, that will put it at / which is where it needs to be.
3) When I did this and used the local update option, it didn't even prompt for 19S, it just moved forward and started the upgrade and rebooted the phone. All it asked me to confirm was right when I selected local update to 'make sure' I wanted to do it. No version check, etc. I was on 18S, btw.

Are you saying you went straight from 18s to 21s? Without the intermediary updates? Are you bootloader locked or unlocked?

Thanks for all of those OTAs. I was restoring my device to stock and every update kept failing when I tried to manually update it. Note: Update will fail if your OTA is not called update.zip.
IT IS CASE SENSITIVE; in other words, it will fail if you name is 'Update.zip'.
Thanks again and this post should be stickied tbh.

If my phone has twrp and on a custom rom could i use the same steps to go back to stock?
Sent from my LEX727 using XDA-Developers Legacy app

Ugh
I could not resist the $199 sale on Amazon despite knowing all the shortcomings. I am starting to regret this decision ... somewhat ... especially since Amazon no longer lets you return phones & can only exchange within 10 days.
Anyhow, I was excited when I got this phone the next day after I ordered it but my 1st frustration was that I could not do any system updates. I read about all the improvements like app drawer & really wanted them but no, it kept saying my system was up to date (still on 18 mind you). Which led me to this thread ... but now my computer will not recognize the Le Pro 3 when I connect it. I tried different USB ports & cords and no luck so far. I also cannot download the above links from my phone so I am kind of stuck @ the moment ...
I do, however, think that I got the work around for the notification issue as they seem to be coming in now, so that's good.
Overall, the phone mostly works so I am not totally mad at this purchase but getting the updates would be nice.
Quick Question: if I try to install Lineage OS, will the phone still have the T-Mobile wifi calling?
Thank you all for this super helpful forum for basic users like me.
UPDATE: Rebooting the phone got my computer to recognize the phone. However, I have followed all the instructions above (downloaded the file, renamed it update.zip, dragged & dropped it right on the phone in explorer, but it still will not find it with the local update.
I downloaded the Cheetah File Manger which shows you the Root Directory, which did not look like where I put mine. So I tried to move it over to the Root Directory but it would not let me paste it there. So close ...................................... calling it a night ...... sigh

i wanted to follow your guidelines but there is no system update in settings in my device. i ve bought it from banggood if that info is useful.

Could you please add check sums for these files.
Thanks in advance!

Try to update my X727 from 5.8.018s to 5.8.019s:
1. Renamed 5.8.019_sta.zip to update.zip and copied it to phone root.
2. From File Manager pressed on update.zip and choose "Upgrade", it has started updating "Upgrading, do not power off the phone".
3. The phone rebooted and entered to Recovery with an error message: "Failed to update! Cause: Installation failed"
4. Presses Back-button and tried again "Update system" and got an error message "Failed to update! Cause: APK not found"
What's wrong?