[REF] YU Yutopia Stock OTA URLs - Android General

Below are a list of all known YU Yutopia OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file, in case CyanogenMod pulls it down in the future.
OTA Updates - sambar
Current firmware: Android 5.1.1, Build LMY48B, Cyanogen OS version 12.1-YOG4PAS5W0
YOG4PAS5W0 from YOG4PAS570 - http://builds.cyngn.com/incremental/sambar/cm-sambar-e4b0cf4380-to-7da8d6c516-signed.zip
Mirrors
http://forum.xda-developers.com/android/general/yu-yutopia-mirrors-official-cyanogen-t3297695
SPECIAL THANKS
@oldblue910 for maintaining similar threads for various Nexus & GPE devices.

HASH (MD5)
Every AndroidFileHost mirror link consists of corresponding MD5 hash; please compare them after download.

INSTALLATION GUIDE
As long as your system is stock, flash (using ADB sideload or from SD card) in stock or custom recovery. Always re-flash the SuperSU zip immediately following to re-gain root access. Bootloader status isn't checked while updating.

Related

[REF] YU Yuphoria Stock OTA URLs

Below are a list of all known YU Yuphoria OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file, in case CyanogenMod pulls it down in the future.
OTA Updates - lettuce
Current firmware: Android 5.1.1, Build LMY49J, Cyanogen OS version 12.1-YOG4PAS8A8
YOG4PAS8A8 from YOG4PAS47N - http://builds.cyngn.com/incremental/lettuce/cm-lettuce-bafcc5769e-to-7490f96009-signed.zip
YOG4PAS47N from YNG1TBS2P2 - http://builds.cyngn.com/incremental/lettuce/cm-lettuce-79f9ccdc85-to-bafcc5769e-signed.zip
YNG1TBS2P2 from YNG1TBS1O3 - http://builds.cyngn.com/fota/incremental/lettuce/cm-lettuce-405aaf9dc6-to-79f9ccdc85-signed.zip
Mirrors
http://forum.xda-developers.com/yu-...u-yuphoria-mirrors-official-cyanogen-t3140830
SPECIAL THANKS
@oldblue910 for maintaining similar threads for various Nexus & GPE devices.
HASH (MD5)
Every AndroidFileHost mirror link consists of corresponding MD5 hash; please compare them after download.
INSTALLATION GUIDE
As long as your system is stock, flash (using ADB sideload or from SD card) in stock or custom recovery. Always re-flash the SuperSU zip immediately following to re-gain root access. Bootloader status isn't checked while updating.
Which version update to apply if current version is YNG1TAS1K0 ?
Hey, can anyone give me the update history for Yu Yureka so that I can know which version to upgrade to from YNG1TAS1K0 ?
I tried installing the whole 832 MB update from YNG1TAS1K0 to YNG1TBS2P2 and it failed.
Great share bro. It is very much needed. Kudos to you for making this for yuphoria
Removed signed zips.
Added COS 12.1 OTA (YOG4PAS47N from YNG1TBS2P2).
Credit goes to [email protected] Forums.
Titokhan said:
Added COS 12.1 OTA (YOG4PAS47N from YNG1TBS2P2).
Credit goes to [email protected] Forums.
Click to expand...
Click to collapse
I'm here too
And no need to thank me so much, but I appreciate it:good:
First post updated, added YOG4PAS8A8 from YOG4PAS47N incremental OTA URL.

[Help] Looking for CM 13 mirrors and recovery images

I'm looking for the following CM 13.0 snapshots for hammerhead (no-caf), as the official CM mirrors are dead:
- https://download.cyanogenmod.org/ge...0-20161222-SNAPSHOT-ZNH5YAO3Z2-hammerhead.zip (sha1 daa4fbc693e0daf580b1d05660408f331611c6f5)
- https://download.cyanogenmod.org/ge...2-SNAPSHOT-ZNH5YAO3Z2-hammerhead-recovery.img (sha1 dd189d0274f99b5d82b3523777c065e5443c931f)
I already noticed the CM image is available on android file host: https://androidfilehost.com/?fid=673368273298919550 - I also checked the sha1 sum matches, however, I wasn't able to find the matching recovery image. I want to use this for security reasons. Any idea where I can get this exact image from?
Thanks
I have the same problem
ROM (latest cm13 snapshot, same version that you posted just link is from a different user) : https://www.androidfilehost.com/?fid=529152257862709748
Corresponding recovery image: https://www.androidfilehost.com/?fid=529152257862709745
This is the folder that contains the CM zips and also the recovery folder is there where I found the corresponding recovery image: https://www.androidfilehost.com/?w=files&flid=160839

[Discussion & Feedback] OxygenOS 10.3.7 OTA for the OnePlus 6

{
"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"
}
Hey everyone,
We are starting to push the incremental rollout of OxygenOS 10.3.7 for OnePlus 6.
Changelog
Code:
[B]System:[/B]
• Newly added "Hide silent notifications in status bar" feature to filter unimportant notifications, making the app notification management easier( Route: Settings>Apps & Notifications> Notifications> Advanced> Hide silent notifications in status bar )
• Fixed the small probability issue that Screenshot may fail
• Updated Android Security Patch to 2020.11
• Improved system stability and fixed general bugs
[B]Game Space:[/B]
• Newly added gaming tools box for convenient switches of Fnatic mode. You can now choose three ways of notifications: text-only, heads up and block, just for your immersive gaming experience
• Newly added quick reply feature in a small window for WhatsApp and INS (Enable it by swiping down from upper right/left corners of the screen in gaming mode)
• Newly added mis-touch prevention feature. Enable it, swipe down from the top of the screen, click and the notification bar will pop out
Explore what's new on Android 10 here.
This OTA will have a staged rollout. The OTA will be received by a limited number of users today and will have a broader rollout in a few days after making sure there are no critical bugs. Using VPN to download this build might not work as the rollout Is not based on regions and is randomly pushed out to a limited number of devices.
For those who were on previous versions for OnePlus 6 and OnePlus 6T, we appreciate your active feedback and for reaching out to us. With your help, we have been able to better optimize and improve several key areas. Thank you for your patience and as always, we look forward to getting your continued feedback via the Community app.
If you don't have the Community app installed on your device, feel free to download it HERE. You can check here for more information on the integrated Feedback tool. Make sure to let us know how you feel about the build here in the thread too, we look forward to reading your feedback.
Downloads​
Full Update
OxygenOS 10.3.7: Official Link | Android File Host
MD5 Hash: 74e8f5a4439516aac04ce8c94fb9427a
Stock Boot Image
10.3.7 boot.img: Unofficial Link
MD5 Hash: b0c15983c4872b3ae622dc93693c4484
Magisk Patched Boot Image
10.3.7 boot.img: Unofficial Link
MD5 Hash: 4774a4a9eed732a837605ea9f5af4391
Previous Updates along with boot images:
Link: Unofficial Link
Custom Recoveries
Official/Unofficial TWRP by mauronofrio: Official Link
blu_spark TWRP by eng.stk: Official Link
Black Out TWRP by acuicultor/Morphine1: Official Link
Root
Magisk: Official Link
Warning: Do not flash partial update OTAs (under 1 GB) on a modified/rooted device! If you want to use partial OTAs, you must first flash the full OxygenOS zip that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full zips in recovery.
Installation Instructions​
Download the necessary files from the section above and follow the steps below:
Note: Dirty flashing is fine if you are running an old OxygenOS version or a ROM based on OxygenOS. If you are, however, coming from a Custom ROM, you must clean flash.
Caution: Please remove your existing screen lock/pin/pattern/password and set it to swipe before starting the update process.
For Non-Rooted Users with a Locked Bootloader and Stock Recovery
Download the full ROM zip from the downloads section above and place it in the root of your internal memory
Reboot to Stock Recovery > Shutdown device > Press Volume Down + Power buttons together
Select Language > Install menu > Install from internal > Select the full zip > Flash
Reboot to System
Note: First boot may take some time, so please be patient and wait for it to boot.
[Dirty Flash] For Users with an Unlocked Bootloader and TWRP Recovery coming from Stable OxygenOS, OxygenOS Open Beta
Download the full ROM zip and TWRP recovery from the downloads section above
Transfer the full ROM zip and TWRP recovery to the root of your device's internal storage
Reboot to TWRP recovery and take a nandroid backup of your existing ROM
From the TWRP menu, Install > Select full ROM zip > Swipe to flash
From the TWRP menu, Install > Select TWRP recovery zip > Swipe to flash
Reboot to TWRP recovery
Flash the latest stable Magisk in case you want to root
Reboot to System
Note: First boot may take some time, so please be patient and wait for it to boot.
Warning: Dirty flashing (update) can be risky! Remember that if you face issues after dirty flashing, you will have to clean flash.
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery
Download the full ROM zip and TWRP recovery from the downloads section above
Transfer the full ROM zip and TWRP recovery to the root of your device's internal storage
Reboot to TWRP recovery and take a nandroid backup of your existing ROM
From the TWRP menu, Install > Select full ROM zip > Swipe to flash
From the TWRP menu, Install > Select TWRP recovery zip > Swipe to flash
Reboot to TWRP recovery
From the TWRP menu, Wipe > Swipe to wipe
Flash the latest stable Magisk in case you want to root
Reboot to System
Note: First boot may take some time, so please be patient and wait for it to boot.
Never Settle.
XDA:DevDB Information
[Discussion & Feedback] OxygenOS 10.3.7 OTA for the OnePlus 6, ROM for the OnePlus 6
Contributors
Funk Wizard, Akhil701
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 10.3.7
Stable Release Date: 2020-11-29
Created 2019-02-11
Last Updated 2020-11-28
Downloads moved to post 1
Thread Maintainer: @jslawler & @Akhil701
Flashing instructions moved to post 1
Thread Maintainer: @jslawler & @Akhil701
Can we get more details on the 5.1.5? What bugs were fixed? What improvements were made?
GizmoFreak said:
Can we get more details on the 5.1.5? What bugs were fixed? What improvements were made?
Click to expand...
Click to collapse
There are no details on the list of bugs fixed or the details on stability at this time.
If i get any details on it from the rom team i shall get back to you.
I believe the team is still working on a bigger update and is focused on getting some more software additions to the OnePlus 6.
Hopefully the future updates will get you better features and optimisation for a smoother experience.
Downloading it now. It seems to be getting the full ROM, probably because I have unlocked the bootloader.
I cannot wait to get my device!! Ordered at launch Direct from OnePlus via priority ship so hopefully Friday arrival!!
Ghashul said:
Downloading it now. It seems to be getting the full ROM, probably because I have unlocked the bootloader.
Click to expand...
Click to collapse
Yes the system would prompt a full zip download for unlocked bootloaders / rooted devices. Download via system updates or from the direct link in the download section :good:
i got the Notch options with this Update, but this update removed the Always On Display function. I hope it will come back
louisitou said:
i got the Notch options with this Update, but this update removed the Always On Display function. I hope it will come back
Click to expand...
Click to collapse
Always on display? I didn't see that I my settings ?
louisitou said:
i got the Notch options with this Update, but this update removed the Always On Display function. I hope it will come back
Click to expand...
Click to collapse
You talking about screensaver?
stian230 said:
Always on display? I didn't see that I my settings ?
Click to expand...
Click to collapse
It was available in OOS 5.1.0 that came pre-installed from factory. It's been removed in later OOS versions.
eroigaps said:
You talking about screensaver?
Click to expand...
Click to collapse
nope, Always on Display is showing you the Battery %, the Notifications and the Clock on your locked screen. Exactly the same feature like Samsung Galaxys and LG Phones have, and it was looking exactly the same too. But well they removed it now..
louisitou said:
nope, Always on Display is showing you the Battery %, the Notifications and the Clock on your locked screen. Exactly the same feature like Samsung Galaxys and LG Phones have, and it was looking exactly the same too. But well they removed it now..
Click to expand...
Click to collapse
oneplus isnt know for removing settings in stable release... maybe its been moved elsewhere.
It has been removed in the latest update. It's discussed all over the internet.
We hope to see AOD back in the next updates or beta.
If you wish to unroot/go back to stock recovery: Please take a look here
Ok guys we have not forgotten you and the update should be available soon. It brings some welcome additions and hopefully the global rollout will start soon :fingers-crossed:
Stay tuned :highfive:
Looking forward to it!!
SirTAVARES said:
where can i make some suggestions to oxygenOS ?
or is it wasted time?
Click to expand...
Click to collapse
Feedback is always welcome and request for features can be done on https://forums.oneplus.com/feedback/
Thank you for your continued support :good:
I just bloody flashed the test 5.1.6 build. I regretted it so much. Everything is working the same or probably faster except for the failed safety net test.
How to I revert back to 5.1.5? I tried to local update official 5.1.5 zip file but it won't let me - downgrading is not allowed apparently.
Or is it better for me to wait for full official 5.1.6 OOS zip and local update it? Will it work?

Unoficial PitchBlack Recovery For Alcatel Tetra 5041c "u50a_att"

Here is PitchBlack recovery For the Alcatel Tetra.
I am not responsible for anything you choose to do with it,
Thanks go to my Test group over on telegram.
@clcombs262
@PizzaG
This is an Unofficial Port
so any bug reports need be listed here.
credit for orig. source go's to the PBRP team
For more info on sources Google is your friend.
I am open to donations, we are trying to buy a new pc.
Recovery Image and Flashable zip with the extra's
AIO toolkit
ROMS all RECOVERIES Everything is now found here:
https://t.me/Android_General_Chat
ChangeLog:
current time is =3:38PM CDT
date is=July 10 2019
This is now the Final-Release candidate
Fixed Bug in adb
fixed a bug that wouldn't allow flashing of the GSI system images
Now everything is reported as working
Enjoy
Note: interestingly I had the same bugs in two different recoveries
Deleted
Read the pm
Deleted
Will this work on the latest phone update? Still on 8.1, but as soon as it hit WiFi it updated to 8MA6UA60. Phone is cheap enough now to maybe break trying.. lol. And these GSI images currently work or is this trial and error? I was shocked by this phones performance on stock for it's price.. I just want to see it's full potential.
Edit: have not gotten this to be able to flash and stick. However you need the fastboot fix on the twrp forum (p23) to even attempt it on ua60.
You'll have to edit the command in the readme to match the updated kernel file as it got updated, but the script rundown did not.

[WIP][EXYNOS][ROM][UNOFFICIAL][12]LineageOS 19.1 for Galaxy S20 FE

LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Unlock bootloader
Boot into download mode
Flash recovery using heimdall or odin
Boot into recovery right as it finishes flashing
Flash ROM using adb sideload path_to_ROM.zip command
Optionally flash GAPPS the same way you flashed ROM
Format data in recovery
Reboot to system.
Downloads:
RECOVERY
ROM
GAPPS
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Credits
Doomer231
A2L5E0X1
DeHuMaNiZeD
Linux4
Device tree and kernel source code:
R8S-OSS
Issues:
voLTE[wont fix, unless any samsung gets voLTE fixed]
fingerprint scanner might not work
overlays might need some tweaking
no encryption
permissive SELinux
Steps I followed from @Gully.Moy that worked perfectly:
Unlocked bootloader as per guides no problem
Downloaded latest stock firmware from Frija and extract
Copy the AP_xxxxxxxxxxx.tar.md5 file to phone storage
Copy Magisk manager on your phone https://github.com/topjohnwu/Magisk/releases/tag/v25.2
Open Magisk manager, select 'install' next to Magisk, select the .tar.md5 file and patch it
Copy newly created magisk.tar file from phone download folder to computer
Flash via Odin 3.13.3 with standard BL CP and CSC from Frija download, but the magisk .tar file in AP slot.
Boot into android and reenable USB debugging (not sure if necessary).
(Recovery mode combination is volume up + side button with USB plugged in)
I am now in the first boot of the ROM that I copied to the internal storage and flashed with TWRP (as my device is not recogised in fastboot and doesn´t let me sideload via adb it closes) but seems to be in an endless startup loop and it failed to install the gapps also when I tried to, the provided recovery cannot be flashed with Odin @Doomvrr thank you.
BraskOviedo said:
Steps I followed from @Gully.Moy that worked perfectly:
Unlocked bootloader as per guides no problem
Downloaded latest stock firmware from Frija and extract
Copy the AP_xxxxxxxxxxx.tar.md5 file to phone storage
Copy Magisk manager on your phone https://github.com/topjohnwu/Magisk/releases/tag/v25.2
Open Magisk manager, select 'install' next to Magisk, select the .tar.md5 file and patch it
Copy newly created magisk.tar file from phone download folder to computer
Flash via Odin 3.13.3 with standard BL CP and CSC from Frija download, but the magisk .tar file in AP slot.
Boot into android and reenable USB debugging (not sure if necessary).
(Recovery mode combination is volume up + side button with USB plugged in)
I am now in the first boot of the ROM that I copied to the internal storage and flashed with TWRP (as my device is not recogised in fastboot and doesn´t let me sideload via adb it closes) but seems to be in an endless startup loop and it failed to install the gapps also when I tried to, the provided recovery cannot be flashed with Odin @Doomvrr thank you.
Click to expand...
Click to collapse
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Doomvrr said:
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Click to expand...
Click to collapse
Thank you for the ROM and the quick answer, if I can help out with something please let me know, thank you.
Doomvrr said:
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Click to expand...
Click to collapse
Forgot to ask, is there an ETA? Is it LineageOS 20? Thank you
Doomvrr said:
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Click to expand...
Click to collapse
It´s the October 2022 patch
Doomvrr said:
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
Click to expand...
Click to collapse
What is the context of the above statments, I ask because -
One of the primary reason for running a custom ROM is for rooting, and the primary reason for rooting for a LOT of users is the ability to run Magisk and EdXposed/Riru.
This one is exspecially confusing, the vast majority of users flash custom ROMs with TWRP. Does the recovery that needs to be flashed with this ROM as comprehensive as TWRP..?
b1k3rdude said:
What is the context of the above statments, I ask because -
One of the primary reason for running a custom ROM is for rooting, and the primary reason for rooting for a LOT of users is the ability to run Magisk and EdXposed/Riru.
This one is exspecially confusing, the vast majority of users flash custom ROMs with TWRP. Does the recovery that needs to be flashed with this ROM as comprehensive as TWRP..?
Click to expand...
Click to collapse
Agreed.
b1k3rdude said:
What is the context of the above statments, I ask because -
One of the primary reason for running a custom ROM is for rooting, and the primary reason for rooting for a LOT of users is the ability to run Magisk and EdXposed/Riru.
This one is exspecially confusing, the vast majority of users flash custom ROMs with TWRP. Does the recovery that needs to be flashed with this ROM as comprehensive as TWRP..?
Click to expand...
Click to collapse
Xposed modules may cause stability issues on the system due to their nature. Debugging the issue becomes a hard task because there can be a ton of reasons as to why it happens, and you'll be most certainly reaching out to the ROM maintainer to help you fix something not even related to his work.
I can't say for sure but I guess it's because TWRP has had some problems to keep up with the changes made to Android on recent years due to the maintainers' private life and the fact that some changes were groundbreaking, like moving the recovery to the boot partition instead of having its dedicated partition, as it used to be until a couple of Android versions.
TL;DR: maintainers post these statements so users can discard possible known causes of issues beforehand, and to avoid complaints about pieces of work that aren't their responsibility at all.
All-In-One said:
Xposed modules may cause stability issues on the system due to their nature. Debugging the issue becomes a hard task because there can be a ton of reasons as to why it happens, and you'll be most certainly reaching out to the ROM maintainer to help you fix something not even related to his work.
I can't say for sure but I guess it's because TWRP has had some problems to keep up with the changes made to Android on recent years due to the maintainers' private life and the fact that some changes were groundbreaking, like moving the recovery to the boot partition instead of having its dedicated partition, as it used to be until a couple of Android versions.
TL;DR: maintainers post these statements so users can discard possible known causes of issues beforehand, and to avoid complaints about pieces of work that aren't their responsibility at all.
Click to expand...
Click to collapse
Imho and experience this nearly always down to the Xposed modules not xposed itself. I have been using xposed since my Galaxy S and its been reliable and solid enough that after 10 Samsung devices later (S, S2, S4, S5, Note5, S6, S7, S7edge, Note9, S20FE) I will always install it. And the Xposed modules I run ar XpirvacyLua, Firefds kit [Q], GravityBox [Q] which are then Managed by EdXposed. I tend not to update the modules unless there is a specific issue that an update will fix.
Nope, check the twrp thread i the section we are upto 3.7.x which supports Android 12 (and should support 13 due to it being an incrmental update on 12).
Thats a fair comment.
Hello, is there a possibility to release this also for snapdragon?

Categories

Resources