Related
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP Recovery, Tool/Utility for the Sony Xperia Z3 Compact
Contributors
someone755
Version Information
Status: Stable
Stable Release Date: 2015-08-18
Created 2015-08-18
Last Updated 2016-02-17
Device page on the TWRP website:
Mirror 1
There is no Mirror 2.
Due to the way Sony devices function, you will need to have an unlocked bootloader.
Your options, as far as ROMs go, are the following:
Any ROM with this commit
OR just use the new bootloader (with a proper recovery partition)
All credit goes to the TWRP team. I just annoyed the fools until they built the recovery.
Awesome! Very glad to see this.
After flashing through fastboot, its impossible for me to boot into recovery, my phone stays stuck on the Sony screen with the pink/orange led.
Running resurrection remix and m5 kernel, theme has been updated for 2.8.7, previously was on 2.6.0
Can this be install on LB?
rich2007 said:
Can this be install on LB?
Click to expand...
Click to collapse
it should work with andropluskernel, not with stock
omnomnomkimiiee said:
After flashing through fastboot, its impossible for me to boot into recovery, my phone stays stuck on the Sony screen with the pink/orange led.
Running resurrection remix and m5 kernel, theme has been updated for 2.8.7, previously was on 2.6.0
Click to expand...
Click to collapse
Works fine here. Did you check the md5 before installing? Does it work without the theme?
rich2007 said:
Can this be install on LB?
Click to expand...
Click to collapse
You need a custom boot image to boot into it (since our bootloaders don't really support a separate recovery partition, and we rely on a boot.img script to boot into one), which means you'd have to unlock the bootloader.
funiewski said:
it should work with andropluskernel, not with stock
Click to expand...
Click to collapse
On this note, if anyone can provide me with stock boot images, I'll try and keep them up-to-date with the extract_elf_ramdisk utility, so that users on stock may still boot into TWRP if they don't opt for the AndroPlus kernel.
Hello everyone,
Flashed this with "fastboot flash recovery", still getting the cm12.1 recovery.
BL unlocked, USB debugging enabled, CM 12.1 installed.
Anyone have a solution?
Thanks
Edit:
tried the twrp manager, no Z3C here, aswell the dd method, nothing changed.
pityu100 said:
Hello everyone,
Flashed this with "fastboot flash recovery", still getting the cm12.1 recovery.
BL unlocked, USB debugging enabled, CM 12.1 installed.
Anyone have a solution?
Thanks
Edit:
tried the twrp manager, no Z3C here, aswell the dd method, nothing changed.
Click to expand...
Click to collapse
Same here, there is no Z3C in the list on TWRP Manager, and the 'dd' method leaves an unusable recovery (stuck on orange led). I'm happy with official TWRP support, but do you guys even test your stuff before releasing it.....? The steps with TWRP manager app don't even exist (there is no 'advanced' to tap).
Flashed twrp.img as boot: fastboot flash boot twrp.img. -> TWRP starts every time i power on the phone. Flashed CM12.1 from this state, and TWRP got overwrited again with CM12.1 recovery. /sigh
Is the CM kernel counts as "Any custom kernel" ?
pityu100 said:
text
Click to expand...
Click to collapse
Menubalk said:
Same here, there is no Z3C in the list on TWRP Manager, and the 'dd' method leaves an unusable recovery (stuck on orange led). I'm happy with official TWRP support, but do you guys even test your stuff before releasing it.....? The steps with TWRP manager app don't even exist (there is no 'advanced' to tap).
Click to expand...
Click to collapse
Thanks both of you for reporting your issues. Your reports sparked an investigation, and we were able to identify several issues that have thus far been overlooked (for whatever reason).
The "stuff" was tested before it was released, yes, but we're now facing limitations in the form of unmerged patches to the CM device trees. The issues should have been resolved several years ago, but instead they are now wreaking havoc on Sony msm8974 recovery setups. I've gotten some of the elite TWRP and CM people on this, as well as smaller fellow rhine and shinano developers (though Myself5 and oshomun could hardly be classified as small nowadays).
I personally have already uploaded four changes to the CM gerrit (that should have been applied years ago); One of them got denied (though is now being discussed for the near future (possibly as soon as cm-13.0); the result of that discussion is, among others, that the Cyanogen Recovery is now available for download alongside the ROM zip over at https://download.cyanogenmod.org/?device=z3c ), two are still pending any input whatsoever, and the last one was promised a merge, but the device maintainers have gone quiet, at least on the outside.
(If you wish, you can view the patches and their progress at their links: patch1, patch2, patch3, patch4, patch5.)
However, both teams are also having issues with other matters (such as Z3 not building, or adding new features to TWRP), and there is also the fact that school starts around this time of year (which impacts both the younger developers as well as those who already have children).
To conclude, there really isn't a unified guide I can give you to get to TWRP. It works, and you can use it if you have the correct setup. However achieving that setup is not a simple walkthrough away, and it would differ ever so slightly for every person's preferences, not to mention it would be overwritten with each new ROM update.
Such is the state of affairs at this point in time. This may or may not change, but be assured that everything we can do about this, we will do.
EDIT: A quick note that some ROMs may already include fixes for these issues. I don't know which those ROMs could be, so I won't go into listing them, but the possibility exists.
someone755,
thanks for your quick reply and your investigation.
Hope for the best, but time will tell.
Thanks again
Someone, here is a build that actually works, maybe you guys can base on that?: http://forum.xda-developers.com/z3-compact/development/recovery-twrp-2-8-6-0-fota-recovery-t3093537
I'm on Cyanogen 12.1 nightlies with M5 (=Cyanogen-based) kernel btw.
Menubalk said:
Someone, here is a build that actually works, maybe you guys can base on that?: http://forum.xda-developers.com/z3-compact/development/recovery-twrp-2-8-6-0-fota-recovery-t3093537
I'm on Cyanogen 12.1 nightlies with M5 (=Cyanogen-based) kernel btw.
Click to expand...
Click to collapse
The thing is that if you flash a cm-12.1 boot image (completely stock, without kernel or ramdisk modifications that M5 or Kernel12 perform), it won't work. It works with some setups, but not with others, and is, for some reason, very specific -- to get rid of these errors, CyanogenMod would have to (at the very least) accept my changes.
If you feel like you have to try this for yourself, here's a link to the boot image: https://www.androidfilehost.com/?fid=24052804347797955 Getting out of the mess created once you flash this can be a pickle though, so unless you have a boot image on hand with which you know TWRP works, do not flash the file I linked.
I've had somebody say it started working for him after flashing r_02 of Kernel12, though sadly I'm not very sure that's a permanent solution (it is, however, a working temporary one).
Unfortunately the man who was supposed to review the changes is on leave from development, so waiting is the only option available right now (unless we come up with a zip file to flash after each nightly install, but that would only increase the chaos of this already-confusing situation).
someone755 said:
The thing is that if you flash a cm-12.1 boot image (completely stock, without kernel or ramdisk modifications that M5 or Kernel12 perform), it won't work. It works with some setups, but not with others, and is, for some reason, very specific -- to get rid of these errors, CyanogenMod would have to (at the very least) accept my changes.
If you feel like you have to try this for yourself, here's a link to the boot image: https://www.androidfilehost.com/?fid=24052804347797955 Getting out of the mess created once you flash this can be a pickle though, so unless you have a boot image on hand with which you know TWRP works, do not flash the file I linked.
I've had somebody say it started working for him after flashing r_02 of Kernel12, though sadly I'm not very sure that's a permanent solution (it is, however, a working temporary one).
Unfortunately the man who was supposed to review the changes is on leave from development, so waiting is the only option available right now (unless we come up with a zip file to flash after each nightly install, but that would only increase the chaos of this already-confusing situation).
Click to expand...
Click to collapse
Had no issues with my 2.8.7.0 twrp built into my ROMs boot.img been working with no issues so far
Sent from my Z3 Compact using Tapatalk
jenkins-84 said:
Had no issues with my 2.8.7.0 twrp built into my ROMs boot.img been working with no issues so far
Sent from my Z3 Compact using Tapatalk
Click to expand...
Click to collapse
The goal of FOTA recoveries was to let the user boot into a recovery regardless of what recovery is in the boot image. If you flash a CM nightly over your setup, you won't be able to get to TWRP again unless you perform various modifications to the CM boot image.
Packing recovery inside boot is what's causing all these issues in the first place, so doing what you suggest would be a step forward, but two steps back as well.
someone755 said:
The goal of FOTA recoveries was to let the user boot into a recovery regardless of what recovery is in the boot image. If you flash a CM nightly over your setup, you won't be able to get to TWRP again unless you perform various modifications to the CM boot image.
Packing recovery inside boot is what's causing all these issues in the first place, so doing what you suggest would be a step forward, but two steps back as well.
Click to expand...
Click to collapse
Yeah maybe but I don't care to much for CM based ROMs was for people using slimlp based mainly
Sent from my Z3 Compact using Tapatalk
jenkins-84 said:
Yeah maybe but I don't care to much for CM based ROMs was for people using slimlp based mainly
Sent from my Z3 Compact using Tapatalk
Click to expand...
Click to collapse
That's all fine and dandy until you realize most people are sticking with CM (for some unexplainable reason). Other ROM gerrits are much more likely to have already merged the needed changes (and are much more lenient and open when it comes to accepting new changes in general, and all this is the only reason this waiting game is now on).
someone755 said:
That's all fine and dandy until you realize most people are sticking with CM (for some unexplainable reason). Other ROM gerrits are much more likely to have already merged the needed changes (and are much more lenient and open when it comes to accepting new changes in general, and all this is the only reason this waiting game is now on).
Click to expand...
Click to collapse
Yeah but I don't wait on slim or use its device trees etc I build for my own and use commits I want, I don't really care what people use or do. I build ROMs for myself and a friend. I just happened to share a ROM that I don't care if people use or not. If I'm happy with what I build and use then that's all I care about
Sent from my Z3 Compact using Tapatalk
jenkins-84 said:
Yeah but I don't wait on slim or use its device trees etc I build for my own and use commits I want, I don't really care what people use or do. I build ROMs for myself and a friend. I just happened to share a ROM that I don't care if people use or not. If I'm happy with what I build and use then that's all I care about
Sent from my Z3 Compact using Tapatalk
Click to expand...
Click to collapse
You do realize TWRP is meant to work for everyone, not just for 'me and my bros'?
On topic:
Someone, that FOTA TWRP I linked does (or at the very least did, I've been on M5 Kernel for a few weeks now) work with a stock Cyanogenmod boot image. Before M5 kernel I could already reach TWRP. I really think it worth a closer look to see what that guy did because it works/worked for some reason..
My full sequence (the first time anyway):
Unlock Bootloader
Unpack boot.img from Cyanogenmod nightly zip
Flash boot.img in fastboot
Boot to Cyanogenrecovery
Wipe
Flash Cyanogenmod in recovery
Boot Cyanogenmod, Setup Wizard yadda yadda
Shut down and go to fastboot
Flash FOTA TWRP from said link
Test FOTA TWRP, Be happy
----Few days later----
Flash M5 through FOTA TWRP
Android 8.0 Oreo - Now in Development
Lineage for Oppo F1 (f1f)
LineageOS is a free and open-source operating system for smartphones and tablet computers, based on the Android mobile platform. It is the successor to the highly popular custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
Instructions
For Installing
1. Unlock root.
2. Download the latest TWRP, build, and GApps.
3. Install/unlock TWRP.
4. Reboot to TWRP recovery.
5. Wipe System, Data, Cache, and Dalvik.
6. Flash the build, and GApps respectively.
7. Flash patches if available.
8. Wipe cache and dalvik.
9. Reboot to system, and enjoy.
Note: If you have 'already installed' Lineage, and want to update your build, use the instructions below.
For Updating Build (Clean Flash)
1. Download the latest build and GApps.
2. Reboot to TWRP recovery.
3. Wipe System, Data, Cache, and Dalvik.
4. Flash the build, and GApps respectively.
5. Flash patches if available.
6. Wipe cache and dalvik.
7. Reboot to system, and enjoy.
For Updating Build (Dirty Flash)
1. Download the latest build.
2. Reboot to TWRP recovery.
3. Flash the build.
4. Flash patches if available.
5. Wipe cache and dalvik.
6. Reboot to system, and enjoy.
For Updating TWRP
1. Download the latest TWRP.
2. Reboot to TWRP recovery.
3. Flash the TWRP update.
4. Wipe cache and dalvik.
5. Reboot to system, and enjoy.
For Unlocking
1. Download magictricks.zip.
2. Go to stock recovery, then install/flash magictricks.zip
3. Reboot to fastboot, then connect phone to pc.
4. Setup adb shell in Windows.
5. Lunch CMD.
6. Install adb drivers for oppo f1f.
7. Type "cd c:\adb" then enter.
8. Type "adb devices" then enter.
9. You should see your device in the list, if not, go back to step six.
10. Put TWRP flashable zip to c:\adb (rename as twrp.img).
11. Type "fastboot oem unlock" then enter.
12. Type "fastboot flash recovery twrp.img" then press enter.
13. After, disconnect phone then reboot to TWRP.
14. Flash img/zips what you want.
Downloads
TWRP: download link
OpenGApps: download link
Unlocker: download link
ADB Installer: download link
ADB Extract: download link
For the builds, see below.
Version Information
Latest Stable Version
Build: 14.1-2017XXXX-UNOFFICIAL-f1f
Android Version: 7.1.1 Nougat
Latest Beta Version
Build: 15.0-2017XXXX-UNOFFICIAL-f1f
Android Version: Android 8.0 Oreo
OpenGApps Version
Platform: ARM64
Android: 7.1 (stable) or 8.0 (beta)
Variant: Stock (recommended)
Android 8.0 Oreo (In Development)
Downloads
Lineage 15 based on Android Oreo Source Code: Link
Notes for Android Oreo Development
Lineage 15 based on Android Oreo Source Code is the one we will need to port.
Android 7.1 Nougat (Old)
Downloads
Build: download link
Patch (Auto Rotation and Navigation Bar): download link
Patch (Kernel): download link
Add-ons
Temporary Camera: download link
Temporary Torch: download link
Known Bugs
The bugs listed here are bugs from the latest nougat build.
1. Camera crashes.
2. Torch toggle don't work.
3. Battery non-accuracy.
4. Hotspot Issue.
FAQ
Q1: What's the difference between updating build "Cleaand "Dirty Flash"?
Clean flash - removes all your files then install the update. Dirty flash - updates your build without removing your files.
Q2: When will you release the next stable build?
See "Version Information" in this thread.
Q3: Can I try the latest beta version?
Yes, if granted by developers of this thread. No, if not.
Q4: Did you already fix the bugs present in the latest stable build?
See "Known Bugs" in this thread.
Q5: What's better for updating build? Clean flash or Dirty flash?
I recommend dirty flash. Only use clean flash when you can't update build properly.
Q6: What's the difference between this thread and other threads.
This thread is for "DEVELOPMENT and FULL GUIDE for 'UNLOCKING, RECOVERIES, KERNELS, ROMS, and OPENGAPPS' for Oppo F1 (f1f)".
Credits, Sources
Developers and contributors:
@kdd998
Android 7.1 Build
@MiniBlu
Android 7.1 Kernel Patch
@khannz7
Android 7.1 Auto Rotation and Navigation Bar Patch
@Earthy
Instructions/Guides
Android 7.1 Add-ons
@ TWRP
TWRP
@ OpenGApps
OpenGApps
@ Lineage Github Repo
LineageOS 14.1
LineageOS 15.0
@ AOSP
Android Nougat Source Code
Android Oreo Source Code
and the community.
For those who want to help building builds for this rom, and for those have knowledge about building builds, just reply to this thread. We will cooperate and share knowledge with each other, so we can build a build faster, better, and more stable. Just teamwork.
Notes
Bug report:
For bug report, just reply to this thread.
Keep up-to-date here, this first thread post change info over from time to time. This thread is last updated: 00:00 PM, Mon-Sun, Jan-Dec 00 2017 (GMT+8).
Reserved 1 out of 9.
Reserved 2 out of 9.
Reserved 3 out of 9.
Reserved 4 out of 9.
Reserved 5 out of 9.
Reserved 6 out of 9.
Reserved 7 out of 9.
Reserved 8 out of 9.
Reserved 9 out of 9.
https://github.com/LineageOS/android_device_oppo_f1f
You can't do anything until there's a cm15 branch anyway.
You can try and port to our device from another device if you want.
There's still actually no new links in this thread. Its all other peoples work. U say u have a beta but havent posted anything. Try and help the other dev fix the sound in the nougat kernel. Instead of just posting other peoples work here.
Jamie_oppo said:
https://github.com/LineageOS/android_device_oppo_f1f
You can't do anything until there's a cm15 branch anyway.
You can try and port to our device from another device if you want.
There's still actually no new links in this thread. Its all other peoples work. U say u have a beta but havent posted anything. Try and help the other dev fix the sound in the nougat kernel. Instead of just posting other peoples work here.
Click to expand...
Click to collapse
Here's the Lineage 15 Source Code.
https://github.com/LineageOS/android_vendor_lineage
Earthy said:
Here's the Lineage 15 Source Code.
https://github.com/LineageOS/android_vendor_lineage
Click to expand...
Click to collapse
Yeah but you still need a los15.0 branch for the f1f device tree. Which isn't available and won't be for a long time
Jamie_oppo said:
https://github.com/LineageOS/android_device_oppo_f1f
You can't do anything until there's a cm15 branch anyway.
You can try and port to our device from another device if you want.
There's still actually no new links in this thread. Its all other peoples work. U say u have a beta but havent posted anything. Try and help the other dev fix the sound in the nougat kernel. Instead of just posting other peoples work here.
Click to expand...
Click to collapse
Jamie_oppo said:
Yeah but you still need a los15.0 branch for the f1f device tree. Which isn't available and won't be for a long time
Click to expand...
Click to collapse
We don't need to wait if we will build our own branch for the f1f device tree. And actually, we are the one should make it because we are the only who develops ROM for this. And also common sense to know that "the one who develop the ROMs should make everything needed here like kernel, branch that you're saying, etc.".
?
Earthy said:
We don't need to wait if we will build our own branch for the f1f device tree. And actually, we are the one should make it because we are the only who develops ROM for this. And also common sense to know that "the one who develop the ROMs should make everything needed here like kernel, branch that you're saying, etc.".
Click to expand...
Click to collapse
Well I have my doubt's. Prove me wrong. I would have no idea how to do this.
Also I think a group collaboration would be better. One person would just be too much work.
Good luck anyway
@MiniBlu, there's your credit. :angel:
@Earthy it is obvious none of this is your work. I personally don't see a camera fix as reason enough for you to repackage someone else's work and release it yourself. Under XDA rule:
12-3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
Click to expand...
Click to collapse
Thread closed
{
"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"
}
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Big thanks goes to @Steel01 for all the hard work and the Sources.
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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.
Hi Everyone
After some months of learning how to build my own Roms and how to edit the proprietary files of this Device i was able to build my first edited version of LineageOS 15.1 with HW Acceleration and the Camera working.
Its a slim an snappy Rom for everyone that´s looking for a monthly updated Android 8.1 Rom to keep this unique Device alive.
This first release is really basic because i deleted everything that doesn't work right.
My plans for this Rom are to keep it updated in case of Security Patches and add some Features here and there as i still learn how this Device and Android is working in general.
Also the official release of LineageOS 16 will end the development of this Rom for the reason i don't want to rival the official contributors of this Device.
Little FAQ to this Rom:
Do i need to Wipe my existing Rom even its LineageOS 15.1 based ?
Yes because i use my own Release Keys for this Rom you need to Wipe your existing one.
Is this Rom compatible with every Shield Tablet ?
Yes this Rom is working with every Shield Tablet
I have a Shield LTE Version and after flashing this Rom i cant connect my device for Data Transfer with my computer anymore.
For some Reason i still didnt found out on LineageOS 15.1 there is no Drop Down Menu for this Device to change the type of connection.
To change it go to Settings > Connected Devices > USB
I found a Bug with this Rom i didnt had on any Rom before what should i do before i post it here ?
Before you post any Bugs and Errors here make sure you installed this Rom correct as i told with a full wipe in your recovery first and if there are modifications installed like Magisk
Moduls or Xposed or you changed this Rom in any way, you should reinstall it fresh first to take a look if the issue still occurs.
If yes post a detailed report of the Error with a Logcat.txt File
Can i install and use Apps like Netflix, Amazon Prime,.. and watch content in HD again with this ROM ?
As this is a Problem with the Widevine Services and this Device itself this Rom doesn´t change anything on that. If you want to use the Netflix App for example you still have to use the liboemdecrypt modul on Magisk and its SD only
Thanks goes to:
@Steel01 and the whole LOS Team for doing all the hard work to keep this Device alive
@Artemka2008 for figuring out the OMX fix
@Triodexe for uploading his work on his Github so i could figure out how to edit the vendor files
@john_matrix for teaching me how to set up my build enviroment and being really helpful when i´m stuck with errors
Requirements:
Bootloader Unlock
Bootloader Version 4.00.2016.04
Custom Recovery installed (use Version 9.5.0_9-0 of TWRP or Lineage Recovery)
Instructions:
Download the latest build and gapps if needed (8.1 / arm / pico)
Reboot to recovery and wipe your existing Rom
Flash the latest build and gapps
Reboot
Downloads:
Builds : https://www.androidfilehost.com/?w=files&flid=325335
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/
Firmware Update : N/Stock 5.0
Whats working now:
HW Acceleration
Snap Camera
Whats still not working:
Nvidia Games App (Deleted)
Console Mode UI (Deleted but HDMI still working fine)
Encryption (will lead to a Bootloop if tried)
Screen Mirroring ( In App Cast like on the Youtube App still working fine)
Contributors:
@Steel01
Source Code: https://github.com/LineageOS
@Scavenger87
Device: https://github.com/Scavenger-87/android_nvidia_device_shield-common
https://github.com/Scavenger-87/android_device_nvidia_shieldtablet
Vendor: https://github.com/Scavenger-87/android_vendor_nvidia_shield
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.10.96+
Version Information:
Status: userdebug
SELinux: Enforcing
Security Patch: 5.10.2021
Build Signature: Own Release Key
Created 14.05.2021
Last Updated 18.10.2021
Scavenger87 said:
View attachment 5308899
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Big thanks goes to @Steel01 for all the hard work and the Sources.
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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.
Hi Everyone
After some months of learning how to build my own Roms and how to edit the proprietary files of this Device i was able to build my first edited version of LineageOS 15.1 with HW Acceleration and the Camera working.
Its a slim an snappy Rom for everyone that´s looking for a monthly updated Android 8.1 Rom to keep this unique Device alive.
This first release is really basic because i deleted everything that doesn't work right.
My plans for this Rom are to keep it updated in case of Security Patches and add some Features here and there as i still learn how this Device and Android is working in general.
Also the official release of LineageOS 16 will end the development of this Rom for the reason i don't want to rival the official contributors of this Device.
Little FAQ to this Rom:
Do i need to Wipe my existing Rom even its LineageOS 15.1 based ?
Yes because i use my own Release Keys for this Rom you need to Wipe your existing one.
Is this Rom compatible with every Shield Tablet ?
Yes this Rom is working with every Shield Tablet
I have a Shield LTE Version and after flashing this Rom i cant connect my device for Data Transfer with my computer anymore.
For some Reason i still didnt found out on LineageOS 15.1 there is no Drop Down Menu for this Device to change the type of connection.
To change it go to Settings > Connected Devices > USB
I found a Bug with this Rom i didnt had on any Rom before what should i do before i post it here ?
Before you post any Bugs and Errors here make sure you installed this Rom correct as i told with a full wipe in your recovery first and if there are modifications installed like Magisk
Moduls or Xposed or you changed this Rom in any way, you should reinstall it fresh first to take a look if the issue still occurs.
If yes post a detailed report of the Error with a Logcat.txt File
Can i install and use Apps like Netflix, Amazon Prime,.. and watch content in HD again with this ROM ?
As this is a Problem with the Widevine Services and this Device itself this Rom doesn´t change anything on that. If you want to use the Netflix App for example you still have to use the liboemdecrypt modul on Magisk and its SD only
Thanks goes to:
@Steel01 and the whole LOS Team for doing all the hard work to keep this Device alive
@Artemka2008 for figuring out the OMX fix
@Triodexe for uploading his work on his Github so i could figure out how to edit the vendor files
@john_matrix for teaching me how to set up my build enviroment and being really helpful when i´m stuck with errors
Requirements:
Bootloader Unlock
Bootloader Version 4.00.2016.04
Custom Recovery installed (use Version 9.5.0_9-0 of TWRP or Lineage Recovery)
Instructions:
Download the latest build and gapps if needed (8.1 / arm / pico)
Reboot to recovery and wipe your existing Rom
Flash the latest build and gapps
Reboot
Downloads:
Builds : https://www.androidfilehost.com/?w=files&flid=325335
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/
Firmware Update : N/Stock 5.0
Whats working now:
HW Acceleration
Snap Camera
Whats still not working:
Nvidia Games App (Deleted)
Console Mode UI (Deleted but HDMI still working fine)
Encryption (will lead to a Bootloop if tried)
Screen Mirroring ( In App Cast like on the Youtube App still working fine)
Contributors:
@Steel01
Source Code: https://github.com/LineageOS
@Scavenger87
Device: https://github.com/Scavenger-87/android_device_nvidia
Vendor: https://github.com/Scavenger-87/android_vendor_nvidia_shield
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.10.96+
Version Information:
Status: userdebug
SELinux: Enforcing
Security Patch: 5.5.2021
Build Signature: Own Release Key
Created 14.05.2021
Last Updated 14.05.2021
Click to expand...
Click to collapse
Thank You for breathing new life into this great little tablet!
Thanks for keep this device alive!
Any ideas why clash of clans will not work on this ROM? Installed COC from Amazon App Store right after flashing this ROM and the game closes with no error right after it fully loads at the loading screen. Tried Lineage OS 16.0 and had the same exact issue using the google play store version with pico opengapps. I just want to use a smooth running ROM and play clash also QQ. Clash ran like trash on the stock 7.0 rom even after doing everything possible to make the tablet smoother.
Thank you very much and nice job Scavenger for keeping our tablet up and running!
Tried this ROM and was very happy to finally see one above Nougat on my shield tablet k1 that has 1080p 60 FPS videos playing smooth with no artifacts and doesn't crash. Also super smooth. Very nice, congratulations and many thanks.
However after I rebooted to recovery and flashes magisk it got stuck forever on Nvidia logo
Wiped everything again, reinstalled (ROM and gapps) and it booted without magisk. Tried flashing magisk again, same problem
I never had this issue with magisk before on this tablet (and I've tried several ROMs).
Anyone else faced this issue? Any advice?
@ogremalfeitor How do you tried to install Magisk? Refer https://topjohnwu.github.io/Magisk/install.html
What would be the right way to install it?
@Scavenger87 Besides your LOS build we find also a recovery.img at androidfilehost.com - do we have to patch this one with the Magisk app? I never tried the LOS recovery before.
marrol said:
@ogremalfeitor How do you tried to install Magisk? Refer https://topjohnwu.github.io/Magisk/install.html
What would be the right way to install it?
@Scavenger87 Besides your LOS build we find also a recovery.img at androidfilehost.com - do we have to patch this one with the Magisk app? I never tried the LOS recovery before.
Click to expand...
Click to collapse
I tried many ways.
Usually with the latest magisk versions I rename the APK to ZIP and install it via TWRP (you can't do that with normal APKs but magisk one is special). This method has worked for me with other ROMs. From then on, when there are Magisk updates, I use the magisk manager app.
Meanwhile I tried dumping the boot partition from TWRP and use the manager to patch it, then flash it via fastboot. Same problem. If I then flash the unmodified boot image back, the system boots fine.
I'm now trying everything again, with the 3.5.0_9-0 version of TWRP (I had 3.4.0 installed). Also I was using aroma opengapps (costumizing what I want), I'm now going to try with pico as said in the first post. Will post back results.
ogremalfeitor said:
I tried many ways.
Usually with the latest magisk versions I rename the APK to ZIP and install it via TWRP (you can't do that with normal APKs but magisk one is special). This method has worked for me with other ROMs. From then on, when there are Magisk updates, I use the magisk manager app.
Meanwhile I tried dumping the boot partition from TWRP and use the manager to patch it, then flash it via fastboot. Same problem. If I then flash the unmodified boot image back, the system boots fine.
I'm now trying everything again, with the 3.5.0_9-0 version of TWRP (I had 3.4.0 installed). Also I was using aroma opengapps (costumizing what I want), I'm now going to try with pico as said in the first post. Will post back results.
Click to expand...
Click to collapse
No luck, same problem
Root addon from lineage os works, but fails safety net check pretty badly and does not support modules like Magisk...
@Scavenger87 do you have any advice to get Magisk working with this ROM? Are there any place logs are generated when the tablet is booting on the nvidia logo where mine is getting stuck? Thanks in advance.
Hello,
I have a question.
What should i Do with
Firmware Update : N/Stock 5.0
I have installed the Rom and the Gapps. And IT runs, on My K1
summerstyle said:
Hello,
I have a question.
What should i Do with
Firmware Update : N/Stock 5.0
I have installed the Rom and the Gapps. And IT runs, on My K1
Click to expand...
Click to collapse
It's just there for people that might have an outdated stock firmware. If it worked for you without it, you don't need it. Someone correct me if I'm wrong
ogremalfeitor said:
No luck, same problem
Root addon from lineage os works, but fails safety net check pretty badly and does not support modules like Magisk...
@Scavenger87 do you have any advice to get Magisk working with this ROM? Are there any place logs are generated when the tablet is booting on the nvidia logo where mine is getting stuck? Thanks in advance.
Click to expand...
Click to collapse
Maybe we have to patch boot.img from NVidia Stock Recovery 5.2 and flash this one?
ogremalfeitor said:
It's just there for people that might have an outdated stock firmware. If it worked for you without it, you don't need it. Someone correct me if I'm wrong
Click to expand...
Click to collapse
This is a separate blob update. What for do we need this?
marrol said:
Maybe we have to patch boot.img from NVidia Stock Firmware 5.2 and flash this one?
Click to expand...
Click to collapse
That's not it. The boot.img is unique to every ROM. It contains the kernel and the initial ramdisk (initrd, if you're interested in details search for that and there are a lot of interesting articles explaining the boot process of Linux and derivates like Android).
I know magisk modifies the initrd to sort of "inject" itself during that early boot process, but it doesn't make the system hang with other ROMs, hence before assuming it's a bug in magisk I'd like to know if anyone has any idea or if the ROM is missing anything that could cause this?
marrol said:
This is a separate blob update. What for do we need this?
Click to expand...
Click to collapse
I believe it has to do with outdated bootloaders, which will be the case for people who never used recent stock firmwares, and it's there should you have problems (but don't confuse bootloader with boot partition or boot.img that I mentioned in another post). I think the script in the Zip detects it when you flash in twrp and gives an error if necessary but please correct me if I'm wrong.
I have try to installed the Firmware Update : N/Stock 5.0 in TRWP. It doesnt work. A Error Shows and it cant installed.
Well meanwhile I went on and started using this ROM without magisk. Started to have crashes here and there not long after, like most (if not all) ROMs for my tablet above android 7... until the video started to get corrupted in YouTube Vanced too which is a deal breaker for me.
Guess this is not the one ROM to solve my problems with this tablet after all, but still it's a great effort. Hope others enjoy it and thanks to the dev for sharing.
Hi everyone after a little vacation and some testing out of your reported issues this is what i found out so far:
Hworangg said:
Any ideas why clash of clans will not work on this ROM? Installed COC from Amazon App Store right after flashing this ROM and the game closes with no error right after it fully loads at the loading screen. Tried Lineage OS 16.0 and had the same exact issue using the google play store version with pico opengapps. I just want to use a smooth running ROM and play clash also QQ. Clash ran like trash on the stock 7.0 rom even after doing everything possible to make the tablet smoother.
Click to expand...
Click to collapse
I installed that game on a Tablet with LOS 14.1 and LOS 15.1 and in both cases the Game crashes because it run out of memory. I did a quick test on my Rom with adding ro.config.low_ram=true to the build.prop which activate the Go Version of Android and decreased the usage of Ram this way .
The Game runs but it started to get really sluggish after around 30 seconds.
It seems this Game just needs more than the 2GB Ram this device can offer.
ogremalfeitor said:
Tried this ROM and was very happy to finally see one above Nougat on my shield tablet k1 that has 1080p 60 FPS videos playing smooth with no artifacts and doesn't crash. Also super smooth. Very nice, congratulations and many thanks.
However after I rebooted to recovery and flashes magisk it got stuck forever on Nvidia logo
Wiped everything again, reinstalled (ROM and gapps) and it booted without magisk. Tried flashing magisk again, same problem
I never had this issue with magisk before on this tablet (and I've tried several ROMs).
Anyone else faced this issue? Any advice?
Click to expand...
Click to collapse
After trying to flash many Versions of Magisk starting by 21.4 over 22.0 and the actual 23.0 via the TWRP Recovery Version (9.5.0_9-0) i mentioned in the Start Thread and trying to flash it with the Magisk App i also wasnt able to install Sucessfully Magisk without running into a Bootlop which is really a Bummer.
I dont know why this happends and i check my Kernel Logs i pulled with TWRP but for the moment we have to use the SU Addon by LOS.
Maybe it has something to do with that my build is signed with a personal key i will check that out.
summerstyle said:
I have try to installed the Firmware Update : N/Stock 5.0 in TRWP. It doesnt work. A Error Shows and it cant installed.
Click to expand...
Click to collapse
Thats just the Blob File that needs to be flashed when the Bootloader isnt updated to the latest Version (4.00.2016.04)
ogremalfeitor said:
Well meanwhile I went on and started using this ROM without magisk. Started to have crashes here and there not long after, like most (if not all) ROMs for my tablet above android 7... until the video started to get corrupted in YouTube Vanced too which is a deal breaker for me.
Guess this is not the one ROM to solve my problems with this tablet after all, but still it's a great effort. Hope others enjoy it and thanks to the dev for sharing.
Click to expand...
Click to collapse
On some rare ocassions you get those same green artefacts on videos like you get with the LOS 16.0 Rom but at least in my case it happends once a week or so and it seems it have something to do with memory managment again.
My guess is that the tegra drivers arent working really well with Android Versions above Nougat (7.0) and this leads to a memory leak but like i said its just a guess by me maybe @Steel01 can say more about that.
I try to optimize the memory management in the future builds if possible.
Hi Everybody
I think its time to give you a little update of my work on this build
After i got a good example of the problems with the ram management of this device i was looking for a solution last few days and i began testing with the Android Go Settings as i mentioned in the last Thread.
With that settings i was able to start that Game mentioned by @Hworangg and i even was able to play it a bit as you can see on one of the added Screenshots below. But you could also see this Game is a real RAM Hog with needing up to 484MB at the last session i played but it is kinda playable you just have to stay in that Game and turn off every notification as it might crashes otherwise. Speaking of crashes while the GO Settings really helping on reduce the usage of Ram by the System itself and let the device take more Memory Pressure it also leads to freezes where you often have to Hard Reset the Tablet because it seems to not close the Main App when its in a Out of Memory Situation. This is something i have to invest more time and research even after i played a lot with the Dalvik VM Settings.
I also found out that my Personal Key Signature is the reason that the install of Magisk is leading to a Bootloop. Here i also have to figure out why this is happen and if its even possible to install Magisk on a Signed Custom Rom as you change out the BOOT.img on this Device to achieve that and it seems the Magisk installer isnt able to resign the File with my Key.
TLDR:
I was able to set up my Build to use the optimized Android GO Settings to withstand more Memory Pressure so that Games like COC and heavy Browsing Sessions with lots of Tabs and Sites with a lot of Pictures doesn't crash that soon but it lead in both cases to a freeze of the whole Device.
The Magisk installer does not work when i sign my build with my own key.
For this Reason i decided to release a another Build for you to test with this Settings as a Nightly Release before i release my next Regular Build when the next Security Patch is out
You find it here : Nightly Build and i´m curious about your opinion.
Flashed the nightly onto a freshly wiped K1 along with opengapps and Magisk 23 using patched boot, no problems there. Video playback - Netflix played about as well as it could with level 3 widevine, with Jellyfin no obvious visual problems streaming 1080p over lan. Got hard freezes when running memory heavy apps (firefox, manga reader, 3d unity games) but it was expected.
Ended up downgrading back to factory stock Lollipop as the memory management is best there, even better than stock Nougat. But will keep an eye on your builds because the K1 could still be a great little tablet if the memory issues in newer versions of Android was fixed. Thank you for your hard work
{
"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"
}
Proudly Presents
Another Exclusive Release
Supported Model
UMX U693CL
Recoveries
OrangeFox_10 Recovery
Roms
AssuranceRom Custom Stock- Android 9
OmniRom Custom GSI- Android 9
CrDroid Custom GSI- Android 11
-AIO ToolKit Prerequisites-
1- Linux: Linux Mint Cinnamon Suggested
2- Python 3
3- Pip install Command: sudo apt install python3-pip
Rom Notes/Disclaimer/Warning
**Don't Deviate From The Install instructions Or The Rom Won't Install Correctly**
**The AIO ToolKit Unbrick Option Is Not Meant To Be Used As A Daily Rom**
** Flashing AssuranceRom Will Bypass FRP Locked Devices **
**Battery Stats Are Broken On GSI Roms**
**Only Use OrangeFox Until Further Notice: 11-15-2021**
-AssuranceRom Clean Flash Installation-
1- Move AssuranceRom To Device(External SD)
2- Boot Recovery
3- Wipe Cache, Dalvik Cache, Data
4- Install AssuranceRom
5- Enjoy!!
-Custom GSI Roms Flash Installation-
1- Move GSI Rom zip To Device(External SD)
2- Boot Recovery
3- Wipe Dalvik, Cache, Data
4- Install Custom GSI Rom zip
5- Boot Custom GSI Rom & Wait Until A-Team Notification
6- Boot Recovery With Normal Reboot and Hold Vol+
7- Enjoy!!
Contributors
Thanks To @deadman96385 for the Firehose Programmer
Thanks To Brenton Miller For The Substantial Donation For Continued Dev Work On This Device
Also Big Thanks To Brenton Miller for September 2021 Device Firmware Files
Big Thanks To The Folks Who Have Come To A-Team Telegram Group To Help Test
Device Downloads
UMX U693CL Downloads
Recovery Device Trees
Device Source
A-Team Website
A-Team Supported Devices
TeleGram Live Support
A-Team Digital Solutions
-Updates-
6-17-2021: Setup for Official Release
6-19-2021: Initial Package Release, Bugs Expected, Recovery Tree still needs some work
6-27-2021: AIO ToolKit Release, removing Initial old release. ToolKit is unfinished and missing some recoveries but is working. I'll add the remaining recoveries and such as time permits
6-28-2021: ToolKit Update v0.06. Dumping options added to Dev Menu, Custom Stock/unbrick Images further tweaked, bugfixes, menu tweaks, etc...
7-3-2021: Added option to remove device encryption, custom stock/unbrick option now a menu, DarkStar Recovery added to recovery menu, disabled first boot setup screen, removed a couple more bloat apps
7-9-2021: AssuranceRom v0.07 recovery flashable zip released, AIO ToolKit v0.09 released, changelog and installation now included in toolkit, removed DarkStar and Batik Recovery(Too Old and Missing Needed Features), Added OrangeFox Recovery, Added PitchBlack Recovery, Android 9 GSI roms tested booting, Android 11 GSI roms tested booting
7-24-2021: AssuranceRom v0.08 Recovery Flashable zip Released, AIO ToolKit v0.10 Released, Changelog now included in the ToolKit Package
8-31-2021: Rude people associated with this device and I'm bailing, go find some other sucker willing to give up their free time, for free, only to be bashed.
9-16-2021: Re-Added Link for The Files, enjoy.
10-21-21: Fixed Main Thread Post, Planned updates are 2 more recovery builds, posting device tree source for all recoveries, update AssuranceRom based off newest OTA release, several planned updates for AIO ToolKit, investigate fixing Lockscreen bug when encryption is disabled, investigate fixing dialer not being set as default dialer on first boot(Magisk Script Not Kicking in Like it should)
10-22-2021: Added TWRP_10 Device Tree to Github & Updated Post Link, TWRP_10 Added to Device Downloads but not yet added into the ToolKit.
11-11-2021: Fixed MTP in Recovery, Fixed Decryption in Recovery, New version of AssuranceRom based off September 2021 Update, AssuranceRom Lockscreen bug fixed, AssuranceRom Dialer bug fixed, Device is now using default encryption since recovery has working decryption AIO ToolKit Updated to reflect new recovery builds, AIO ToolKit Updated to reflect updated unbrick files, several small tweaks to AIO ToolKit, TWRP_10 Updated in ToolKit, OrangeFox_10 Updated in ToolKit
11-12-2021: AIO ToolKit v0.14 Release- Broke Unbrick Option into 2 parts, ReadMe explains this more. Unbrick options will now auto reboot device after flashing, Added Option 9 for testing ADB Connectivity, AssuranceRom v0.10 Release, Re-Added Google Dialer into AssuranceRom(Now set to default dialer), Added AssuranceRom Installation Instructions to Main Thread Post
11-13-2021: AssuranceRom v0.11 Release, Post Boot Setup Script properly adds preset settings now for X-Plore, Preset settings for NovaLauncher, Added Custom Lockscreen wallpaper and wallpaper, Added a bunch more preset device settings to Post Boot Setup Script. Device will now auto reboot when Post Boot Setup Script is complete so that the changes and settings can be applied, Updated NovaLauncher, AIO ToolKit v0.15 Release, NovaLauncher Updated in unbrick System Image, Added Installation Warning on Main Thread Post
11-14-2021: Prep Main Thread for Custom GSI Releases, OmniRom_A9_Custom_GSI-UMX_U693CL-v0.01.zip Release, AIO ToolKit v0.16 Release(Unbrick Option 1 BugFix)
11-15-2021: AssuranceRom v0.12 Release(Consult ChangeLog), OmniRom v0.02 Release(Consult Changelog), AIO ToolKit v0.17 Release(Remove TWRP For Now)
12-5-2021: CrDroid Custom GSI v0.02 Release, Working Assurance Service and Volte OOTB, All GSI Roms will only require 1 install now , I will eventually spread that out to AssuranceRom as well in the future.
1-4-2022: AssuranceRom v0.13 Release, AIO ToolKit v0.19 Release, consult ChangeLogs for changes
I would love to beta test this if possible, and assume all risk that may come with it as my own problem.
Fcking suuuper excited to make this garbage phone just a little less stinky. Thanks for putting this all together!
lol I just noticed I am considered a new member... after 11 years on the site. Must be cause I lurk.
I am interested in an orange fox recovery. But at this point any will do. So, how does one get past the fastboot issue this phone has?
Striking gold once again I see, much thanks and kudos to you,can't wait for release
Thanks alot
I ****ed up and forgot to make a backup of data first. Anyone have the Assurance Wireless APK for activation backed up?
tesell said:
I ****ed up and forgot to make a backup of data first. Anyone have the Assurance Wireless APK for activation backed up?
Click to expand...
Click to collapse
Unless you're still on a Sprint sim,it shouldn't be needed. I'm on the new T-Mobile tower sim and did initial activation on a GSI just fine
timjames474 said:
Unless you're still on a Sprint sim,it shouldn't be needed. I'm on the new T-Mobile tower sim and did initial activation on a GSI just fine
Click to expand...
Click to collapse
sweet, yeah, i think i am on t-mobile, pretty stoked with it so far. unlimited tether data, and now that its rooted, my vpn works. thinking about cancelling my xfinity.
There a step by step guide?
OK got it worked out what rom you recommend for this device there along on the page lol
I'd like a step-by-step guide too. It would save people a lot of trouble if they don't know this particular method of unlocking. Also, is there a way to unlock the assurance sim card for use on other devices?
Minalia said:
I'd like a step-by-step guide too. It would save people a lot of trouble if they don't know this particular method of unlocking. Also, is there a way to unlock the assurance sim card for use on other devices?
Click to expand...
Click to collapse
Assurance locks the SIM to the IMEI network side,so short of commiting felonies no you can't. Good news is the UMX is sim unlocked out of the box,so you can go to any T-Mobile,AT&T or Sprint MNVO(May need to call ASW and tell them to cancel your service for Sprint ). SafeLink is a good choice for lifeline
An AIO ToolKit is about to be released for this device, I wrote it to handle everything from fresh untouched device to fixing a soft-bricked device. The initial release will be removed shortly and this new ToolKit is for Linux...
Thanks for all your work, assurance sent my grandfather a wiko phone, He received a call and from the phone call. the phone was bricked aswell as some chinese ransomware looking malware. Called assurance and their sending this malware infested UMX again, thanks to you though I can get off that malware infested os and onto stock android! Keep up the great work!
tx for this toolbox coming out!
i got this phone via assurance, and indeed, it not only installs many apps/websites with zero user control, but also apps with all chinese characters, and that was right out of the box. a month later i called assurance to stop my service with them, though i've kept this phone. they asked why i was stopping their service, and i just told her it was enough that i had daily apps/games/sites installed without my permission or control, but that some of them were in a chinese character set; this from a phone given to u.s. citizens applying for federal help during covid.
i now use safelink instead, which just gave me a sim for my pixel 3a, much simpler/safer than assurance.
This is an awesome feat. I thank you so much! BUT I do need to explain a couple points from my experience doing this, just in the event that it maybe helps someone out.
I followed the guide step by step but as I have attempted other root options in the past, I think it caused my phone to soft-brick due to those past attempts that I tried with only my own limited knowledge.
So this is my personal experience, only posting for others in the event that someone else has a similar or identical issue. The issue(s) I had were almost certainly not at the fault of the person who wrote this guide, just FYI. For many, their process has proved successful first-try, as you'll see within the comments.
Again, MY experience:
FIrstly, I had to do things differently. So I DID NOT flash anything to the boot partition. I SKIPPED THAT STEP. (Of course this is after my first try when I followed the post's instructions. After my first attempt I found myself in a soft-brick situation. Luckily, I have two of these devices so I was able to rescue the device using the working device's firmware and I only flashed recovery to begin with, and then booted into TWRP, pushed Magisk and installed it...error. Sideloaded Magisk, SUCCESS!
(Always use software from the creator's site/forum, even when you know you can get it here...just to ensure you're getting a safe and up to date version). Once you've got you some Magisk, you can choose to flash any of the recoveries...(I used OrangeFox and TWRP. OrangeFox is prettty cool, but I don't see backup/restore options like in TWRP. PitchBlack wouldn't show my files AT ALL so options were very limited with that recovery.
And other than that, this guide is awesome! I'm now rooted, and I've got LSposed and even changed my font with a magisk module, as well as the boot up screen haha.
Thank you so much to @PizzaG , for not only putting this together but for taking the time to share and help others.
(TAKEN FROM ORIGINAL POST-UNCHANGED): We really appreciate your effort and your sharing with us!!! You ARE AWESOME!
clintongsan said:
This is an awesome feat. I thank you so much! BUT I do need to explain a couple points from my experience doing this, just in the event that it maybe helps someone out.
FIrstly, DO NOT flash anything to the boot partition. SKIP THAT STEP. I did this and it bricked my phone. Luckily, I have two of these devices so I'm currently trying to use the other to pull the firmware off, partition by partition, in hopes I can restore the first one with it, without copying over device info....we'll see lol. But yeah, all you need to do if you want this awesome guide, created by these wonderful devs, to work, is just flash the recovery image...reboot into recovery. (You can hold power and volume up until you see the screen flicker/flash, then let go of power or both power and vol up (I don't think it matters) and wala! You've got into TWRP.
Now, either install Magisk off a microSD card OR just sideload it using adb sideload (path to magisk). I used the latest Magisk from their website. (Always use software from the creator's site/forum, even when you know you can get it here...just to ensure you're getting a safe and up to date version). Once you've sideloaded Magisk, you can choose to flash any of the recoveries...(I used OrangeFox and TWRP. OrangeFox is prettty cool, but I don't see backup/restore options like in TWRP. I'm sure it's there somewhere I probably just didn't look well enough.
And other than that, this guide is awesome! I'm now rooted, unlimited data (xposed framework modules) and completely dark-mode across the device (again, xposed modules). I even changed my font with a magisk module and the boot up screen haha.
Thank you so much to the guys/girls/team that put this together. We really appreciate your effort and your sharing with us!!! You ARE AWESOME!
Click to expand...
Click to collapse
you are false in giving people that "advice" if you were in the test Telegram group for this device, you would surely know that 3+ people have been testing the ToolKit without issue. I post the Telegram link for a reason. So if people have an issue with something, instead of badmouthing an option or feature, you come get live help to fix the real issue at hand, which is not flashing the boot image.
So I pushed root for this device and installed a batick recovery and bootloops, trying the unbrick restore.
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?