Since only the 20c tot is available, you need to follow special steps to get it all the way up to 20y.
You need to be rooted with no system mods or custom recovery images
Be careful to download from the ACTUAL web host, not the phishing site! You are supposed to end up with zip files. Malware is also being hosted on devhost, as people have been reporting
Sorry, not really in the mood to write down newbie friendly steps, maybe someone can consolidate them. I don't check my PMs...
From now it would be great if someone generously backs up their fota folder every time until we get a new tot leak.
How to Force OTA dlpkgfile install
http://forum.xda-developers.com/showthread.php?t=2699123
Some details of how to follow the force OTA procedure for D800. You MUST be on a stock LG G2 D800 firmware:
Copy dlpkgfile into /cache/fota/, chmod dlpkgfile to 666. Again this file gets deleted after the update.
If /cache/recovery folder does not exist, create it. This folder is automatically removed after the update. chmod it to 777 because it doesn't matter.
Write the cache command to recovery. With adb under root user, run:
Code:
echo "--update_package=/cache/fota/dlpkgfile" > /cache/recovery/command
Running the am start command. With adb under root user, run:
Code:
am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart
All the steps starting from 20c fresh install:
1) 20c fresh
Guide to go to 20c (D80020c): http://forum.xda-developers.com/showthread.php?t=2663369. If you are coming from a custom ROM, chance are that you need the special DLL to force the flash.
2) root 20c
Towelroot get root on 20c: https://towelroot.com/
You could set SuperSU to OTA survival mode, not sure if this is actually needed
Choose one of the two from below:
3a) 20c -> 20y (force OTA, see above)
https://mega.co.nz/#!5h9nTRzL!444IEUUENYyfUUSovecNRF31JWVbg_WoERFxUUe0r8o
(Mirror) http://d-h.st/VJzP
AD0CFBA03A8E82240D6EB48BB285ED78
3b) 20c -> 20k (force OTA, see above)
http://d-h.st/dBhB
20k -> 20u (force OTA, see above)
http://d-h.st/BT3
20u -> 20y (force OTA, see above)
http://d-h.st/auPE
Result = 100% stock rooted 20y without waiting for AT&T. Process to do each incremental update shouldn't take more than 20 minutes total.
* * *
Other fixes if you don't have the AT&T SIM available
AT&T address book contacts hijacking:
*#*#2666#*#* and setting "registration" to "completed"
Enable wifi tether:
http://forum.xda-developers.com/showthread.php?t=2668453
Acknowledgements
20k from 20c
http://forum.xda-developers.com/showthread.php?t=2711503
20u from 20k
http://forum.xda-developers.com/showthread.php?p=53335676
20y from 20u or 20c
Thanks to oddhours (http://forum.xda-developers.com/member.php?u=815149) for sharing the 20u to 20y update
30f from 20y
http://forum.xda-developers.com/lg-g2/general/dlpkgfile-lg-g2-att-lollipop-file-t3082867
It works like a charm. Thank you so much. I waited for a long time.
every body give me images how to update 20k to 20u? I don't live in US. thanks!
what if I only have the camera mod. would that affect anything? and how do you do the command push really not trying to mess anything up.
Works fine for me... thanks
real2015 said:
what if I only have the camera mod. would that affect anything? and how do you do the command push really not trying to mess anything up.
Click to expand...
Click to collapse
When it comes to OTAs, you are usually okay with additions to the firmware, but not modifications.
Does a custom recovery qualify as a system mod?
lesterp said:
Does a custom recovery qualify as a system mod?
Click to expand...
Click to collapse
This will not work with a custom recovery.
Sent from my LG-D800
xaueious said:
When it comes to OTAs, you are usually okay with additions to the firmware, but not modifications.
Click to expand...
Click to collapse
could anyone share the ota dump of 20k from 20c, the link above is not working... I am not living in US... Many Thanks! :crying:
bigheadlyf said:
could anyone share the ota dump of 20k from 20c, the link above is not working... I am not living in US... Many Thanks! :crying:
Click to expand...
Click to collapse
https://www.dropbox.com/s/gqjc9utwc2x5rcf/fota_4-10-14_ 20c to 20k.zip?dl=0
works fine, great job.
Mirror for both ota
Please pull the update zip (dlpkgfile: D80020u → D80020y = 89.5 MB).
Thanks! :good:
MrNgocHoang said:
Please pull the update zip (dlpkgfile: D80020u → D80020y = 89.5 MB).
Thanks! :good:
Click to expand...
Click to collapse
same same, need this ota anyone..
Is the new NAG I Have, "Software update is available"? (October 8, 2014) How do I get the Nag to go away? It tried to autoupdate, don't want my phone jacked up, waiting for an update here.
fail
Copy dlpkgfile into /cache/fota/
open terminal emulator for android
su
allow permission
close terminal emulator for android
open terminal emulator for android
su
echo "--update_package=/cache/fota/dlpkgfile" > /cache/recovery/command
am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart
reset and upgrade fails
is wrong
atifsh said:
same same, need this ota anyone..
Click to expand...
Click to collapse
I also need the D80020y dlpkgfile so I can do a manual update to D80020y. Can someone please upload this file. Thanks in advance.
I had sucessfully apply d80020u update over 20k manually by google over the net
above Ota tutorial is not complete.initial steps Are Missing
shalabh2009 said:
I had sucessfully apply d80020u update over 20k manually by google over the net
Because this tutorial is not complete.initial steps. Are. Missing
Click to expand...
Click to collapse
nothing is left here, linked to external address is provided
all we were asking was the 20(new) ota, if you have it, share it.
I had d80020k Ota and 20u Ota only,can anyone provide d80020y Ota.thanks
*delete this post*
---------- Post added at 03:44 PM ---------- Previous post was at 03:03 PM ----------
xaueious said:
Since only the 20c tot is available, you need to follow special steps to get it all the way up to 20u.
You need to be rooted with no system mods. Sorry, not really in the mood to write down newbie friendly steps, maybe someone can consolidate them. I don't check my PMs...
From now it would be great if someone generously backs up their fota folder every time until we get a new tot leak.
Guide to go to 20c:
http://forum.xda-developers.com/showthread.php?t=2432476
If you are coming from a custom ROM, chance are that you need the special DLL
Towelroot get root on 20c:
https://towelroot.com/
20k from 20c, download the ota dump and ONLY get dlpkgfile
http://forum.xda-developers.com/showthread.php?t=2711503
20u from 20k, download the ota dump and ONLY get dlpkgfile
http://forum.xda-developers.com/showthread.php?p=53335676
Force OTA install
http://forum.xda-developers.com/showthread.php?t=2699123
Based on force OTA install steps,
Copy dlpkgfile into /cache/fota/
If /cache/recovery folder does not exist, create it. This folder is automatically removed after the update. chmod it to 777 because it doesn't matter.
chmod dlpkgfile to 666 before running the am start command. Again this file gets deleted after the update so it doesn't matter
Steps:
1) 20c fresh
2) root 20c
3) 20c -> 20k
4) 20k -> 20u
Result = 100% stock rooted 20u without waiting for AT&T. Since 20k and 20u updates are <50MB, process to go from 20c to 20u shouldn't take more than 20 minutes total.
* * *
Other fixes if you don't have the AT&T SIM available
AT&T address book contacts hijacking:
*#*#2666#*#* and setting "registration" to "completed"
Enable wifi tether:
http://forum.xda-developers.com/showthread.php?t=2668453
Click to expand...
Click to collapse
full instructions with adb are:
1)Copy dlpkgfile into /cache/fota/
2)create /cache/recovery if it does not exists
3)on adb run:
adb shell su
chmod 777 /cache/recovery/
chmod 666 /cache/fota/dlpkgfile
echo "--update_package=/cache/fota/dlpkgfile" > /cache/recovery/command
am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart
worked for me
I'm working on creating an unbrick script so I have downloaded the latest update from OnePlus and used an payload.bin extractor to extract its contents.
However, the images that I got did not include the bootloader or the radio.
So I was curious if there was a way for me to extract the current bootloader and radio image files stored on my OnePlus 6.
Or maybe there is another way I can go about extracting those two images from the downloaded file I grabbed on the OnePlus 6 download page?
I just finished an update to my flashing script, now it will work with payload.bin and unpacked payload files.
Currently, only gsi_sdm660_64 models are available for this option.
And Windows only, too.
PLEASE ENSURE YOUR PHONE HAS UNLOCKED BOOTLOADER, OTHERWISE THIS GUIDE IS USELESS.
Let me introduce you how to use the new script:
DL: https://github.com/HikariCalyx/OSTRemote/releases
source: https://github.com/HikariCalyx/OSTR...Script/generic_flash_script_gsi_sdm660_64.bat
If you use unpacked nb0 extension stock firmware as before, please follow this guide:
https://forum.xda-developers.com/nokia-7-plus/how-to/guide-workaround-flashing-sparse-t3906070
Click to expand...
Click to collapse
1. You must have Python 3 installed. It can be downloaded from https://www.python.org/downloads/
2. Extract the payload.bin from full OTA package (e.g. March 2019 update known as B2N-351F-0-00WW-B04)
3. Put the script file (and required files if you prefer original script source) and the payload.bin altogether
4. Download payload_dumper.py and update_metadata_pb2.py from the URL given by the script, and place them to the same directory of the script.
5. Type lowercase "yes" (without quotes) and press Enter, wait for the procedure complete.
6. The script will dump the payload.bin and process both system and vendor image to flashable sparse image.
7. After that, you should know what to do next.
If you already have dumped payload and converted system.img / vendor.img, the script will tell you if you want to flash the unpacked OTA packages, you can simply type "yes" and proceed.
You needn't to waste the time of processing payload.bin again, once you don't delete them.
I'm considering port this script to universal for almost every A/B Android devices, if it works great.
Nice job dude, this will be very useful to many people.
Very well Hikari, nice script
Very very much appreciated work!
Can't wait to try it out!
Thanks !
Mod edit - Translated by Google Translate:
Very supportive! !! !!
*********************
非常支持！！！
does this work for other Nokia models? Such as 3.2?
I've read all the how to's and most of them I dont understand.
I'm on the june update, rooted and have magisk.
I do not have a backed up stock image on majisk
Would like to apply the july update and re-root.
I was wondering if I should get the stock image from july - patch it with magisk now but is that even possible? (then transfer it to pc) - then apply the july ota - then flash the patched magisk for root.
You might try reading the thread "[Guide] How to root the Pixel 3a and take OTA updates once rooted"
zonedgold said:
I was wondering if I should get the stock image from july - patch it with magisk now but is that even possible? (then transfer it to pc) - then apply the july ota - then flash the patched magisk for root.
Click to expand...
Click to collapse
Here's how I did it, since I like to flash the factory image...
[stuff] is different depending upon the file itself (which month release it is) and if it's for pixel 3a or pixel 3a xl.
Grab the factory image: https://developers.google.com/android/images
Extract the downloaded file
Extract the image-[stuff].zip
Get the boot.img file from the image.zip extraction and put it on your phone
Patch with Magisk (the top Install option of the two... Install>Install>Select and Patch a File)
Copy the magisk_patched.img file to your computer (located in the Download folder)
Edit flash-all.bat from the extracted downloaded file and remove the -w flag
If you don't remove that -w flag, it will wipe your phone!
Run flash-all.bat
Follow the adb instructions done before, to flash the magisk-patched file
In flash-all.bat, change
Code:
fastboot -w update image-[stuff].zip
to
Code:
fastboot update image-[stuff].zip
If you don't remove that -w flag, it will wipe your phone!
Jon8RFC said:
Here's how I did it, since I like to flash the factory image...
[stuff] is different depending upon the file itself (which month release it is) and if it's for pixel 3a or pixel 3a xl.
Grab the factory image: https://developers.google.com/android/images
Extract the downloaded file
Extract the image-[stuff].zip
Get the boot.img file from the image.zip extraction and put it on your phone
Patch with Magisk (the top Install option of the two... Install>Install>Select and Patch a File)
Copy the magisk_patched.img file to your computer (located in the Download folder)
Edit flash-all.bat from the extracted downloaded file and remove the -w flag
If you don't remove that -w flag, it will wipe your phone!
Run flash-all.bat
Follow the adb instructions done before, to flash the magisk-patched file
In flash-all.bat, change
Code:
fastboot -w update image-[stuff].zip
to
Code:
fastboot update image-[stuff].zip
If you don't remove that -w flag, it will wipe your phone!
Click to expand...
Click to collapse
Thank you but , got it all done
Hi all,
My bootloader is unlocked and phone rooted since November. I was able to do the OTA updates up to January with the stock boot.img technique but since February I couldn't find the update.
The update system tells me there is no update. I have obviously restarted several times, the root is inactive, I do not understand at all where the problem comes from. If anyone has an idea, I take it.
(magisk app (22.1) installed but Magisk root off)
I see a similar probleme here : https://forum.xda-developers.com/t/may-update-not-available.4272659/
If anyone had a how-to dirty flash, without loose app&data...
So, I find this from other thread from Pixel 1 (old) :
TENN3R
Download the entire factory image, unzip, open the folder and you'll see a "flash-all.bat" (supposed you're on windows, otherwise the other 2 script files are for mac and linux)
Edit it with notepad (or what you prefer) and remove the "-w" from the latest line, then save it.
Go in fastboot mode, then launch your edited flash-all script file. This will flash the new factory image but without wiping your device, like an ota, but without all the troubles ota has, then it will auto reboot.
Copy on phone magisk and/or kernel
Now disable lockscreen security, then go in fastboot again. Type in cmd "fastboot boot <twrp.img>" (or what it is called)
When terminal gives you "OKAY" unplug device and you should be in twrp. Flash the zips you've choosen and then reboot and re-enable lockscreen pin, password etc..
Magisk and kernel should now work, I did it just now without any problem.
Click to expand...
Click to collapse
I had to download entire factory image or just the OTA update from google website ?
EDIT : ok, full factory image
The full OTA can be applied without unlocking the bootloader.
The factory image has to have the -w removed or it wipes your data.
Both remove root so you have to re-patch your boot.img and then flash it.
Thx, I find the good way, with -w removed. Everything works.