Develop Bugs

Flashing Gio from ODIN with .tar.md5

I dowloaded my stock firmware from samfirmware.com and now i would like to flash it. It is a single tar.md5 package. I would like to known how to flash it. I searched, but it was not much help to me. Do i use the single package option in ODIN?
- i have never used odin, but i have flashed alot of roms so im not completely stupid when it comes to this stuff.

Yes, one package

Once you have Odin
To do so
The file "GIO_v0.1.ops"
You will find in the package of Odin
{
"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"
}
You put the file you downloaded md5
How do you see "PASS!" disconnect and if appears
"Close serial port and wait until rebooting" a disconnect, and wait until the phone turns on, of course, disconnect the cable.
It says Samsung on the phone remove the battery and enter the Recovery Menu
select "wipe"
select reboot
READY
I already have the new rom

Is it possible to unzip the rom with 7zip and remove the recovery image so i can still have my custom recovery?

AlwaysDroid said:
Is it possible to unzip the rom with 7zip and remove the recovery image so i can still have my custom recovery?
Click to expand...
Click to collapse
Ypu can but must be able to do a md5sum or flash as .tar without md5 check
Sent from my GT-S5660 using xda premium

Cant find?
voetbalremco said:
Ypu can but must be able to do a md5sum or flash as .tar without md5 check
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
Im trying to flash a file called S5660MUGKG3_S5660MBMCKG3_BMC. When ever i try to one package i cant seem to find it? Can anyone help me with this?

Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.

Darkshado said:
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Click to expand...
Click to collapse
How do I unzip it? Can I use winrar and extract?

Darkshado said:
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Click to expand...
Click to collapse
Yay I got it!
Thanks for your help!
Is it fine if it says 1 (COM10) ? and also its keeps on showing the boot animations over over... wont go further and on odin it says pass. should i keep on waiting or is somthing wrong? is it bricked?

1 (COM10) is simply to indicate the serial port number assigned to your phone by Windows and the Samsung USB driver in Odin.
Your phone is boot looping, some might consider this a soft brick. My best guess is that you previously installed a ROM that formatted your /data and /cache partitions from the stock RFS format to ext4 instead. The stock 5660M ROM doesn't support ext4.
Reboot in the stock recovery, either with "adb reboot recovery" or by using the home and power keys simultaneously.
From there, wipe user data and cache, or something similar I don't recall the exact wording, but I do remember they were two separate commands.
Reboot, should work now. Use ddms (part of the Android SDK) to see what's going on under the hood if you feel like it.
I take it computers are a relatively new thing for you to ask how to unzip files. My best advice: make very regular backups and read instructions carefully. Losing data is not cool. Losing someone else's data is worse. (I'm guessing you're on the family computer here...)

Bootloader update testing

http://www.mediafire.com/?n9vq4v9bcudgvvn
Note that it isn't a recovery update zip, you have to unzip it and flash the bin with fastboot.
I've updated it with a new menu system, text based, not image based like the old one.
A few updated to the graphics handling as well, nothing really special otherwise... It's just a boot loader, it doesn't have to be special.
Another note, I don't recall how the boot process works when it tries to boot linux, with out linux actually installed... It'll either hang the boot loader (force it off with long power button press), or it will just default boot Android.
Test it, abuse it, post results!
It's safe to flash to all OG Kindle Fire, but there's always a risk when flashing...
Edit:
Oh, and yea... Power button is still sluggish, actually it's probably worse now for some reason, I'm looking into that.
If I can't figure out why, I may look into alternatives.

seishuku said:
http://www.mediafire.com/?n9vq4v9bcudgvvn
Note that it isn't a recovery update zip, you have to unzip it and flash the bin with fastboot.
I've updated it with a new menu system, text based, not image based like the old one.
A few updated to the graphics handling as well, nothing really special otherwise... It's just a boot loader, it doesn't have to be special.
Another note, I don't recall how the boot process works when it tries to boot linux, with out linux actually installed... It'll either hang the boot loader (force it off with long power button press), or it will just default boot Android.
Test it, abuse it, post results!
It's safe to flash to all OG Kindle Fire, but there's always a risk when flashing...
Edit:
Oh, and yea... Power button is still sluggish, actually it's probably worse now for some reason, I'm looking into that.
If I can't figure out why, I may look into alternatives.
Click to expand...
Click to collapse
Is this just a modification to FireFireFire 1.4a?
Sent from my Amazon Kindle Fire

More or less... I may update the core u-boot code later too, but there really isn't a need.
Here's a crappy screen shot:
{
"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"
}

seishuku said:
More or less... I may update the core u-boot code later too, but there really isn't a need.
Here's a crappy screen shot:
Click to expand...
Click to collapse
Ah I see.....how did you setup partitioning for Android and Linux? I'm quite interested I'm how this works.....
Sent from my Amazon Kindle Fire

http://forum.xda-developers.com/showthread.php?t=1677085
Basically, you shrink the SD partition, and add a kernel and root fs partition.

seishuku said:
http://forum.xda-developers.com/showthread.php?t=1677085
Basically, you shrink the SD partition, and add a kernel and root fs partition.
Click to expand...
Click to collapse
I guess you could say, in theory, you could dual boot Android and Ubuntu Touch, but you would have almost no usable space
Sent from my Amazon Kindle Fire

Pretty much, I use Debian 7... Xwindows is a bit of a pain with th virtual keyboard, but its very usable.
Though I do have 4gb dedicated to Linux too.

Wow, pretty cool.
Sent from my Amazon Kindle Fire

seishuku said:
Pretty much, I use Debian 7... Xwindows is a bit of a pain with th virtual keyboard, but its very usable.
Though I do have 4gb dedicated to Linux too.
Click to expand...
Click to collapse
In a perfect world we'd combine /userdata and /media into 1 6gb partition which would make the tablet much more usable in almost any OS.
But obviously this creates quite the overlay nightmare for KFire users who could be on either configuration.

Yeah, it may create some problems, but I think in the long run it would be for the better.
Though it would create a headache for those dual booters that run two android os, but I think they are a little nuts anyway. :lol:
In other android worlds, repatitioning has been done with out much trouble... like on my old galaxy s, /data was moved from emmc to nand for better access speed.
Plus it would give a chance to clean up the partition table, get rid of those that aren't used, like backup efs and others, which also frees up some space (unless the user has done so already, like I have)

A thing for those that don't like messing up.
There should be a zip that executes in TWRP that partitions your kindle fire and install linux and you'd still have your android custom rom there

When I get more time to really sit down and work on it, that would be the plan... The problem is though, is that zip has to be on the SD partition and Linux is somewhat large.
That's a problem when you have to install from a zip and repartition, which is going to destroy the partition that you're installing from.
The way to do a linux install on the kindle is to have a host script running on your PC, you boot the kindle to recovery and the script will execute the needed commands via ADB and fastboot.

seishuku said:
When I get more time to really sit down and work on it, that would be the plan... The problem is though, is that zip has to be on the SD partition and Linux is somewhat large.
That's a problem when you have to install from a zip and repartition, which is going to destroy the partition that you're installing from.
The way to do a linux install on the kindle is to have a host script running on your PC, you boot the kindle to recovery and the script will execute the needed commands via ADB and fastboot.
Click to expand...
Click to collapse
Seems like ADB sideload could also work; as this doesn't actually place the zip on the sdcard (rather uses space in /dev/tmp if I recall).

That's true, I forget about sideloading.

[Q] Bloatware that is safe to remove?

Which packages did you guys remove?
I am happy that I could remove Firefly with Titanium Backup.
The app started randomly, in my pocket (I presume the camera button got pressed against My pocket), and I never really used it anyway.
I would like to know what does Whisperlink and if it is safe to remove.

arth_ur said:
Which packages did you guys remove?
I am happy that I could remove Firefly with Titanium Backup.
The app started randomly, in my pocket (I presume the camera button got pressed against My pocket), and I never really used it anyway.
I would like to know what does Whisperlink and if it is safe to remove.
Click to expand...
Click to collapse
Personally, I believe Firefly is a nifty little app that doesn't affect the phone in any way to actually consider removing it. But, well, to each his choice, right?!
Anyway, Whisperlink is an app that syncs your Kindle books info - purchases, reading progress, highlights 'n notes - across other amazon devices.

Amazon Appstore

The single issue is that it often starts up in my pocket and drains my battery.

[deleted]
NEW version here - http://forum.xda-developers.com/fire-phone/general/complete-app-list-replace-remove-t3132008

Bingo Bronson said:
FireOS 4.6.1 (KK 4.4.4)
Things I have removed so far: ........
to free up system space.
Used 'SD Maid' to scan for leftover "Libs" and other obsolete files.
Click to expand...
Click to collapse
And so after all these have been removed, how much free system space do you have, and do you think it is making an observable difference in terms of performance?

Bingo Bronson said:
FireOS 4.6.1 (KK 4.4.4)
Things I have removed so far:
REMOVED
Apps used (for now):
F-Droid Repo: AdAway, AFWall+, Amaze File Manager, ApkTrack, Autostarts, Calculator, Camera, Kernel Adiutor, Kitchen Timer, MuPDF, Sound Recorder, Swiftnotes,
VA: BusyBox, Buzz Launcher, Dolphin, KingUser, Multiling O Keyboard, MX Player, RAR, SD Maid, Titanium Backup, WhatsApp, Wifi Analyzer, WiFi File Transfer Pro
I removed all the lockscreen scenes (including \system\etc\com.amazon.lock\files\lockscenes\ls_moon.vbl) and used a black 1x1 px jpg instead, Amazon stock lockscreen.
I deleted \system\euclid , \system\media\fremedia (bootanimation.zip & boot.wav as well) and \system\tts to free up system space.
Used 'SD Maid' to scan for leftover "Libs" and other obsolete files.
Click to expand...
Click to collapse
Very radical list but thanks for trying each app. I just wonder if you remove com.amazon.device.settings then how can you change any setting in your system ever?

@ O.a.T. The perfomance hasn't changed that much, feels just as fast as running it with disabled "dynamic perspective". I am just trying to get the system as lean as possible. I will encounter problems with the current configuration, no doubt, so I will update the list in the future. System partition: 733 MB used, ~ 1,38 GB free.
edit: Battery life benefits the most from these changes, of course, using apps like 'Kernel Adiutor' or 'Kernel Toolkit' have the biggest influence compared to disabling / removing apps and services. Installed 'Greenify' for a couple of minutes, tells me "no apps need to hibernate" (big surprise ^^).
@ najoor The system settings is called 'Settings' / 'Settings Storage' (AmazonSettings.apk, 99% sure it's the main settings app ^^). 'com.amazon.device.settings' is a different component, so even with this one being removed, access to the settings menu works as usual.

Anyone know to reinstall fresh firephone OS ?
I messed up something and want to reinstall it. But, the "factory reset" just reset setings and won't recover, or reinstall fresh FireOS.

stunvn said:
Anyone know to reinstall fresh firephone OS ?
I messed up something and want to reinstall it. But, the "factory reset" just reset setings and won't recover, or reinstall fresh FireOS.
Click to expand...
Click to collapse
You can find the latest FireOS ROM in one of the Topics here on XDA and then if you are rooted, I believe, you can use Flashify from the google play store to install.
Personally, I rooted, and created a nandroid and a titanium backup of my current setup and all the apps before I started tinkering with the OS.
Or maybe this ...
http://forum.xda-developers.com/fire-phone/general/how-to-update-fire-phone-to-fireos-4-6-t3085745
is even easier.

What O.a.T. said, or try this as an alternative gah, ninja'd and edit by O.a.T. nevermind
1. Download the *.bin file (FireOS 4.6.1)
UK - http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-33.4.6.1_user_461013320.bin
GER - http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-34.4.6.1_user_461013320.bin
US - http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-35.4.6.1_user_461013820.bin
I strongly recommend using a download manager to speed up the download. Regular download with a browser is tedious.
2. Boot phone in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)
From the list, choose "Apply update from ADB"
3. adb sideload 'name_of_your_bin_file'
I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin

Bingo Bronson said:
What O.a.T. said, or try this as an alternative gah, ninja'd and edit by O.a.T. nevermind
1. Download the *.bin file (FireOS 4.6.1)
UK - "fire-phone-updates.s3.amazonaws.com/update-fire-phone-33.4.6.1_user_461013320.bin"
GER - "fire-phone-updates.s3.amazonaws.com/update-fire-phone-34.4.6.1_user_461013320.bin"
US - "fire-phone-updates.s3.amazonaws.com/update-fire-phone-35.4.6.1_user_461013820.bin"
I can't post links yet, just copy the above mentioned file name of your choice, your browser will be able to download it.
2. Boot phone in recovery: PWR + VOL. UP
Choose "install update from ADB" (something like that...)
3. adb sideload "name_of_your_chosen bin_file"
I recommend renaming the the downloaded file to "update.bin" so can just type in cmd: adb sideload update.bin
Click to expand...
Click to collapse
I followed those steps and have trouble at step 3. Device not found. Do you know how to fix this?
I tried to run adb devices but nothing show up. It's weird. because, before that I still can see my device on the device list.

stunvn said:
Do you know how to fix this?
Click to expand...
Click to collapse
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method. That's why your phone "disappears" as soon as you (re)boot into ADB.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"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"
}
Try this tool (& driver) http://forum.xda-developers.com/showthread.php?t=2588979
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload"

Thank you very much :fingers-crossed: :good::good::good::good::good:

Busybox fails to install

Accidentally installed the wrong busy box apk but cleared data and uninstalled then i tried installing the correct version of stericson busybox free and I'm greeted by this message
"There was a problem opening a shell with root access. this is either cause by supersu or by a device that is improperly rooted..."
It then goes on to say i should change permissions in supersu then reinstall. Of course I can't do this because our supersu does not have a settings menu.
I'm looking for help. Is there a way to resolve this over adb and change the su settings? Or can i reinstall supersu?--would that give me the popup i need to grant permissions (if that is in fact the issue...)
I'm not certain i can just run towel root again and reinstall supersu. I have the latest prerooted firmware installed.
BTW--I'm curious as to what happened. thinking the wrong busy box app is still causing issues because i did the same thing on my other fire tv and could easily install busy box again. Thanks.

You should be able to open the settingsmenu (or the apps list) of SuperSU in the FireTV system settings menu -> installed apps tab. Just start the SuperSU app for that.

Calibaan said:
You should be able to open the settingsmenu (or the apps list) of SuperSU in the FireTV system settings menu -> installed apps tab. Just start the SuperSU app for that.
Click to expand...
Click to collapse
Unless I'm misunderstanding, you can't do that with our supersu (think its just the way rbox designed it that supersu can't be opened). Go to applications and try it. I assume your setup is the same as mine--cwm & and prerooted firmware.
I'm thinking I'll just uninstall/reinstall supersu, but not even sure that will resolve the busybox issue.

No, I have not a rooted aTV (those for the german market were never deliverered with a rootable firmware, hope this changes with stagefright vulnaribilty). I assumed you´re running the regular SuperSU from Chainfire which does acts as a Superuser access management tool:
{
"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"
}
It should be possible to call this superuser app from the apps tab within the system menu like every other sideloaded app. Of course when you´re running another supersu app this probably won´t work.

Calibaan said:
No, I have not a rooted aTV (those for the german market were never deliverered with a rootable firmware, hope this changes with stagefright vulnaribilty). I assumed you´re running the regular SuperSU from Chainfire which does acts as a Superuser access management tool:
It should be possible to call this superuser app from the apps tab within the system menu like every other sideloaded app. Of course when you´re running another supersu app this probably won´t work.
Click to expand...
Click to collapse
Thanks. I have read in other thread people talking about using superuser app to access those settings we can't get with supersu on AFTV. That was a long time ago and don't think there was much feedback on how it worked.
I messed things up more than I thought. None of my root apps are working (ROM manager, titanium backup, samba file sharing, etc.
Wondering if just reinstalling the ROM.zip will fix everything? Only thing about that is it doesn't ask to regrant su for my installed apps normally. Not sure if it'll be different because root isn't functioning properly...

So maybe someone can confirm this? If I wipe factory reset in cwm will supersu reinstall and reset su settings? (Actually pretty sure it will) But really rather not do that because I'm forward thinking enough to install titanium backup but not smart enough to backup apps and data (always put it off then forgot) Now of course I can't use titanium.
So if that's my only option I'll do it but hoping there's a simpler way like flashing supersu zip in recovery. AND if that's an option should I first remove supersu apk in system/app?

I've had issues with the Busybox installer, too. It claims you can begin installing right away, but it's a good idea to wait until it finishes its scan to do the install.

Sizzlechest said:
I've had issues with the Busybox installer, too. It claims you can begin installing right away, but it's a good idea to wait until it finishes its scan to do the install.
Click to expand...
Click to collapse
Well I didn't actually want busybox installer. I wanted busybox free by stericson. I'm not even sure if the installer is by stericson. So did you try to run that installer program again and let it complete? Or were you actually talking about busybox free which is what I've always used on AFTV (its the recomended version we all are probably using). But not paying attention I installed the wrong apk. Now none of my root apps work which I don't understand. Busybox having trouble makes sense but pretty sure I've run other root apps without busybox in the past.
Its looking like I need to wipe it but not in a huge hurry. The AFTV functions OK without root so I'll hang around for a better solution.

KLit75 said:
Well I didn't actually want busybox installer. I wanted busybox free by stericson. I'm not even sure if the installer is by stericson. So did you try to run that installer program again and let it complete? Or were you actually talking about busybox free which is what I've always used on AFTV (its the recomended version we all are probably using). But not paying attention I installed the wrong apk. Now none of my root apps work which I don't understand. Busybox having trouble makes sense but pretty sure I've run other root apps without busybox in the past.
Its looking like I need to wipe it but not in a huge hurry. The AFTV functions OK without root so I'll hang around for a better solution.
Click to expand...
Click to collapse
This is what I was referring to: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Can you connect to your Fire TV using adb and do a "su" command to see if you get root? Did you fully unlock your bootloader?

Sizzlechest said:
This is what I was referring to: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Can you connect to your Fire TV using adb and do a "su" command to see if you get root? Did you fully unlock your bootloader?
Click to expand...
Click to collapse
That's the one that won't install. Yes. I can connect adb, reboot recovery and bootloader fully unlocked. I can't access everything in es file explorer because the root explorer option won't work without su permissions. But adb shell will get the # sign.

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?