Related
Presenting the latest development version of the TeamWin Recovery Project's touch recovery for the HTC Wildfire S. TeamWin Touch Recovery now has official builds available through TeamWin and GooManager for the Marvel. With any luck MarvelC support will soon follow. Please visit the TWRP and TeamWin pages for more information.
Compiled for and tested on the original GSM Marvel. Always awaiting more testing from CDMA Marvel users. This software is provided without support or warranty: use it at your own risk.
Known Issues:
Fails on a handful of new GSM Marvel devices with updated/incompatible hardware, locking at the initial HTC splash screen.
Change Log:
XX:XX XX/8/2012 - Initial release of TWRP v2.2.2.0: Upstream code changes resolve the issues with formatting SD-EXT and partitioning the SD-Card. Includes the initial release of a revised 320x480 default theme with cleaner action pages, slightly larger buttons and more spacious checklists. First stable, full-featured and issue free release of TWRP for the HTC Wildfire S. Previous buggy versions have been removed from the revision history and can no longer be downloaded.
17:35 19/08/2012 PDT - Second release of TWRP v2.2.1.5: Issues with offmode charging resolved thanks to kalaker.
23:32 17/08/2012 PDT - Initial release of TWRP v2.2.1.5: Upstream code includes changes that resolve issues with the system rebooting during backup operations.
03:00 06/08/2012 PDT - Initial release of TWRP v2.2.1.4: Upstream code includes a handful of nice little bug fixes including a resolution for the mount issues.
23:05 05/08/2012 PDT - Minor aesthetic tweaks to the new theme.
02:29 05/08/2012 PDT - Third release of TWRP v2.2.1: Includes a carefully scaled v2.2 theme enabling the latest release's advanced features.
22:59 28/07/2012 PDT - Second release of TWRP v2.2.1: Corrected a glitch in my build environment that could have lead to issues and then forked it for dedicated platform builds. First dedicated MarvelC build.
23:58 27/07/2012 PDT - Initial release of TWRP v2.2.1: Compiled from the most recent code provided by: TWRP, Cryptomilk and the CyanogenMod ICS-Release branch.
22:55 09/07/2012 PDT - Maintenance release of TWRP v2.1.8: Reconfigured and shrank the kernel in order to utilize a less aggressive form of compression than LZMA. Switched from the CyanogenMod ICS branch to ICS-Release.
12:35 09/07/2012 PDT - Initial release of TWRP v2.1.8: Built using the ICS branchs of the CyanogenMod and Cryptomilk Marvel sources. Oversized image required LZMA compression.
To Do:
Build flashable .ZIP
Download Links:
TWRP for GSM HTC Wildfire S (Marvel) v2.2.2.0 (Preview Release) - Image - Mirror
MD5: 34f201ec8c8b0f0d2eae64c88ac3d888
TWRP for CDMA HTC Wildfire S (MarvelC) v2.2.2.0 (Preview Release) - Image - Mirror
MD5: 7c4d137a37098900ff3b2a9412ee8994
This is not the place for support.
I apologize in advance for what may seem abusive but, as it has been laid down here in the RULES it stands to reason that I'm decently covered.
THIS IS NOT THE PLACE FOR YOUR QUESTIONS! THIS IS!
In my infinite generosity I've created a place where users can get answers to frequently asked questions and seek support from one another. As an added bonus it will save you from my wrath. Please limit all discussion in this thread to development issues. I've started you off with some installation instructions as that was the first issue. I will update and check in as necessary. Enjoy!
You need to have the HTC drivers installed.
Then in cmd type:
fastboot flash recovery recovery.img.
Place the img file in the same folder as the adb files, so you won't have to specify a path.
Good luck,
Awesome work btw. :laugh:
WoefulDerelict said:
I apologize in advance for what may seem abusive but, as it has been laid down here in the RULES and I CLEARLY stated there would be ABSOLUTELY NO SUPPORT in my original post, it stands to reason that I'm decently covered.
THIS IS NOT THE PLACE FOR YOUR QUESTIONS! Ignorance and stupidity will not be tolerated.
In my infinite generosity I've created a place where users can get answers to frequently asked questions and seek support from one another. As an added bonus it will save you from my wrath. I've started you off with some installation instructions as that was the first issue. Enjoy!
Click to expand...
Click to collapse
If you're not going to support this, then this dosent belong in the Dev section... it can go in the General section or Apps section. Only Supported work belongs in the Dev section.
He means he wont be answering any questions in this thread.............he created another thread for discussion in the general section
Semantics...
Red5 said:
If you're not going to support this, then this dosent belong in the Dev section... it can go in the General section or Apps section. Only Supported work belongs in the Dev section.
Click to expand...
Click to collapse
I believe the issue here is entirely one of semantics. In my lexicon support encompasses the magical realm of end-user hand holding. In no way do I feel it is necessary or reasonable to expect a user manual with warm and fuzzy walk-troughs of every possible thing you could want to do and some friendly advice with a hug every time the user has a problem with their FREE software. I certainly don't plan to offer any of the above.
I do; however, plan on maintaining my work. I'm quite interested in information that would allow me to improve the image or resolve a reproducible issue. I also have no qualms discussing the work with other developers, providing updates as the code base evolves, accepting proper issue reports or feature suggestions. I'd simply prefer to avoid getting bogged down by questions that could easily be answered by visiting the project's home page or querying Google. I find it quite counter productive to wade through user prattle when I'm trying to fix an issue or collaborate with another developer.
Hello.
Is this recovery version work on Marvel with black CWM Recovery effect (new graphics hardware) ??
I'm not sure what you're asking.
marchelius said:
Hello.
Is this recovery version work on Marvel with black CWM Recovery effect (new graphics hardware) ??
Click to expand...
Click to collapse
This should be compatible with any HTC Marvel based Wildfire S. I believe they are all based on the same SOC. The kernel should have support for all MSM7227 based graphics hardware.
WoefulDerelict said:
This should be compatible with any HTC Marvel based Wildfire S...
Click to expand...
Click to collapse
Should be, but it isn't. After flash, my phone stuck on white screen with green HTC logo after attempt to enter in recovery...
Works perfectly on my phone. Mine is the A510e.
The joys of platform fragmentation.
marchelius said:
Should be, but it isn't. After flash, my phone stuck on white screen with green HTC logo after attempt to enter in recovery...
Click to expand...
Click to collapse
SomeDudeOnTheNet said:
Works perfectly on my phone. Mine is the A510e.
Click to expand...
Click to collapse
I suppose the plus side is that I have some confirmation that the software works on other A501e devices. If you're going to report something as not working could you at least go to the trouble of including your device's identifying information? A510b/e, SPL and Radio versions would be a great start.
WoefulDerelict said:
I suppose the plus side is that I have some confirmation that the software works on other A501e devices. If you're going to report something as not working could you at least go to the trouble of including your device's identifying information? A510b/e, SPL and Radio versions would be a great start.
Click to expand...
Click to collapse
OK.
HTC A510e
Android 2.3.5
EQDKP v4.7
Kernel 2.6.35.10-ga66971c
47.23e.35.3038H_7.57.39.10M
S-ON, unlocked via HTCDev
Main branch broken with CM9 on Marvel since updating to 2.2 code.
TWRP updated their main branch to v2.2 today. While I was hoping for the resolution of current issues their changes break my build with CM9. I'm stepping through the changes presently to see if I reason out what changed between 2.2 and 2.1.8 to cause the issue and correct the it. Stay tuned for more updates.
More please...
marchelius said:
OK.
HTC A510e
Android 2.3.5
EQDKP v4.7
Kernel 2.6.35.10-ga66971c
47.23e.35.3038H_7.57.39.10M
S-ON, unlocked via HTCDev
Click to expand...
Click to collapse
Could I get the HBOOT, MICROP and Radio version from your SPL? Hold the volume rocker and power button down while turning on the device to access the bootloader for that information.
IF these Frankenstein devices exist I'm going to need a profile of the revised hardware in order to correct the issue along with some proud owners to test fixes as I don't have access to one. The Marvel I was given is based off the original hardware profile and TWRP2.1.8 works fine when built with CM9 and the cryptomilk.org MSM7227 kernel. I'll do what I can to fix it but, I'm currently trying to resolve build issues with the new 2.2 release. I'm hoping this new code base along with a revised kernel will resolve many of the current issues.
It's ALIVE!
The problem is it's behaving like I brought it to life with a couple bolts of lightning. To say that it has issues would be overly kind but, it boots and I can navigate around. I'm currently trying to track down all the shorts making 2.2 twitch. Stay tuned.
Fresh revision.
Finally managed a clean build from the latest source. I'd love for some brave MarvelC users to give it a test before building a flashable .ZIP for the general public.
WoefulDerelict said:
Finally managed a clean build from the latest source. I'd love for some brave MarvelC users to give it a test before building a flashable .ZIP for the general public.
Click to expand...
Click to collapse
Thanks but theres a few issues
1. Theme isn't updated
2. On-screen keyboard wont work due to current theme
3 l. Swipe to start backups/restoring wont work due the theme.
More or less this is just like the previous twrp until themes are resized etc
Sent from my Wildfire S A510e using Tapatalk 2
Yea, I knew that.
eoghan2t7 said:
Thanks but theres a few issues
1. Theme isn't updated
2. On-screen keyboard wont work due to current theme
3 l. Swipe to start backups/restoring wont work due the theme.
More or less this is just like the previous twrp until themes are resized etc
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
This was already noted in the original post as the last entry under the known issues header. I maintain this for a reason. Thankfully the themes are XML based and updating it shouldn't be ridiculously difficult. Once I've gotten the issue list stable and nailed down where they are all rooted I'll see what I can do to tackle this and the formatting errors as they seem to be the largest TWRP specific issues I could correct. I wager the XML theme business will be relatively quick and painless.
WoefulDerelict said:
This was already noted in the original post as the last entry under the known issues header. I maintain this for a reason. Thankfully the themes are XML based and updating it shouldn't be ridiculously difficult. Once I've gotten the issue list stable and nailed down where they are all rooted I'll see what I can do to tackle this and the formatting errors as they seem to be the largest TWRP specific issues I could correct. I wager the XML theme business will be relatively quick and painless.
Click to expand...
Click to collapse
Yeah the themes are XML based but the image editing will be the worst part
Sent from my Wildfire S A510e using Tapatalk 2
eoghan2t7 said:
Yeah the themes are XML based but the image editing will be the worst part
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
I'm trying to imagine that being easy. I'm not totally inept in Adobe or AutoCad products so I'm sure I can toss together something in a week or so. Depends on how much the real job needs my time and brain meats.
Grab it here: https://dl.twrp.me/zerofltespr/
Just installed with Flashify all good...
Sent from my SM-G920P using Tapatalk
Anyone got a flashable zip?
JoeFCaputo113 said:
Anyone got a flashable zip?
Click to expand...
Click to collapse
You mean for people who are too lazy to type "fastboot flash recovery twrp-3.0.0-0-zerofltespr.img" if they have a PC or to install Flashify if they don't?
Not me, I hate those guys.
(Just kidding with you Joe, but no, haven't seen one.)
koop1955 said:
You mean for people who are too lazy to type "fastboot flash recovery twrp-3.0.0-0-zerofltespr.img" if they have a PC or to install Flashify if they don't?
Not me, I hate those guys.
(Just kidding with you Joe, but no, haven't seen one.)
Click to expand...
Click to collapse
That's exactly why hahaa. Also I just hate using Odin TBH lol.
JoeFCaputo113 said:
That's exactly why hahaa. Also I just hate using Odin TBH lol.
Click to expand...
Click to collapse
Flashify will work just fine. Just place the .IMG file on your phone and point Flashify to it.
Also, what I posted is the ADB command. Universal for all devices. No need for Odin, my brother.
Link for anyone that needs instructions: http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
Deleted.
You can flash it through TWRP if you already have the old version installed.
Install>images>"your devicename.img location">tap "devicename.img">slide to flash>done.
rafyvitto said:
Install>images>"your devicename.img location">tap "devicename.img">slide to flash>done.
Click to expand...
Click to collapse
To help the thread, this is not for our specific device but a changelog for 3.0, and the appropriate cautionary tales.
Our device is here:
https://twrp.me/devices/samsunggalaxys6sprint.html
TWRP 3.0.0-0 Released
Feb 5, 2016
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
Thanks, @socos25!
JoeFCaputo113 said:
Anyone got a flashable zip?
Click to expand...
Click to collapse
just in case you're not comfortable with flashify still.
https://www.dropbox.com/s/1ujr6i1pr9oudhy/twrp3.0.0s6spr.zip?dl=0
Sent from my SM-G920P using Tapatalk
asafegous said:
just in case you're not comfortable with flashify still.
https://www.dropbox.com/s/1ujr6i1pr9oudhy/twrp3.0.0s6spr.zip?dl=0
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
You the man!! :good:
Just a shot in the dark but does anyone know if this'll work on my Sprint S6 Edge variant?
Much obliged,
This worked for me OK Sprint Samsung s6 oj7 rooted and debloated
########## #############
Official TWRP with prebuild Kernel is available here:
https://forum.xda-developers.com/mi-mix-2/development/recovery-twrp-3-2-1-0-xiaomi-mi-mix-2-t3780525
########################
Greetings flashaholics!
As usual before flashing this TWRP make an complete backup of your system!!!
Why another TWRP?
you'll get the latest TWRP release with most recent features & bugfixes
build live from sources - no prebuild kernels/files
more partitions to backup/restore supported
made project treble compatible by adding vendor & vendor_image partitions (leaving cust partition available for legacy purposes)
double tap to wake display
survives installation of official MIUI Global/CN ROMs (read INFO section to know how to achive that result exactly)
DOWNLOAD TWRP 3.2.3-0
... please see also supplemental infos & tool downloads below in INFO section
Please leave feedback for the beta. Does it work well? Did you encounter any problems? THX
Important changes in latest 3.2.3-0 build: 20180815-2003
based on fresh MIX 2 OmniRom base files and new msm8998 common sources - speed seems to be upgraded a little
previous changelog:
TWRP 3.2.3-0 based - build on Nextgen-Networks build environment with latest kernel 4.4.78
"FrankenTab" - mixed fstab v1 & v2 layout to achive de-/encryption and also keep as much partitions available as possible
treble compatible (by adding vendor & vendor_image partitions)
backup write speed restored (80 MB/s for file systems / 110 MB/s for imaged drives) and stayed compatible with OmniRom power/storage/kernel settings
Build completely live from latest build tree files - prebuild kernel fragments not needed anymore *yay*
en-/decryption support
ADB/MTP support
display brightness fixed - it's bright again! (see detailed notes in download section if it did not work for you)
additional partitions backup & restoreable (20 overall)
doupble tap to wake display is supported
display works when booting from LOS/OmniRom/RR to recovery via menu
survives installation of official MIUI Global/CN ROMs (OTA not tested yet)
Tested and perfectly working with ROMs as follows
MIUI 8.8.9 xiaomi.eu
MIUI 8.7.x xiaomi.eu
MIUI 8.6.x xiaomi.eu
MIUI 8.6.21 CN / xiaomi.eu
MIUI 8.6.14 Global
MIUI 8.6.8 CN
MIUI 8.5.11 Global
MIUI 8.5.8 Global / CN / xiaomi.eu
MIUI 8.5.2 Global
MIUI 8.4.26 by xiaomi.eu
LineageOS 15.1 build 20180501
OmniRom 8.1.0-20180430 HOMEMADE
INFO:
official MIUI Global/CN ROMs installation survival: dont reboot after ROM installation/update - just start a new flash session and flash latest magisk beta in a separate process - thats all! (OTA survival has not been tested by now)
If your TWRP gets constantly overwritten then flash the no-verity-opt-encrypt-1.6.zip right after your flashed TWRP to your device and right after each install/update of an original XIAOMI ROM from (en.)miui.com.
Procedure not needed for xiaomi.eu based ROMs.
Download no-verity-opt-encrypt 1.6 here
To make the flashing a little more convenient I've written a little windows script that utilizes adb/fastboot and presents all recovery images in its folder for your flashing happiness
This package also contains a script to remove/bypass the pin/passcode/pattern you've set - this could help then restoring an backup and the definitely correct pin/passcode/pattern is not accepted afterwards
Download recovery-flash.cmd 1.29 here
need an matching firmware for your device?
Download here from the Xiaomi Firmware Updater project on XDA (downloads in post 2)
Some very clarifying official information about en-/decryption types and how it works: https://source.android.com/security/encryption/
take a look here to have a full backup with internal storage covered also: [URL="https://forum.xda-developers.com/android/apps-games/app-twrp-tipatch-backup-internal-t3831217]Info & Download TiPatch[/URL]
For more detailed changelogs visit the download page.
Updated versions will be announced in this thread.
Instructions how to setup & build your own TWRP:
https://github.com/nextgen-networks/android_device_xiaomi_chiron-OMNI/blob/android-8.1_v10/README.md
Sourcecode (updated 2018-08-15 / v13):
Modified TWRP: https://github.com/nextgen-networks/android_bootable_recovery
Device-Tree (Device): https://github.com/nextgen-networks/android_device_xiaomi_chiron-OMNI
Device-Tree (SOC): https://github.com/nextgen-networks/android_device_xiaomi_msm8998-common
Kernel: https://github.com/omnirom/android_kernel_xiaomi_msm8998
Vendor-Tree (Device/SOC): https://github.com/DonkeyCoyote/proprietary_vendor_xiaomi
Thanks, works great so far.
As mentioned in the Lineage thread I intend to you encryption, neither the MIUI nor the iceman TWRP recoveries manage to mount my encrypted LineageOS storage, they just fail after the prompt.
Under this recovery I don't get a prompt.
Just wanted to mention, I will use it and test it anyway if encryption is not working yet, I will manage somehow.
Iam on Lineage. But after flashing TWRP not starting, only the fastboot mode
---------- Post added at 06:43 PM ---------- Previous post was at 06:36 PM ----------
https://www.nextgen-networks.de/de/...17-twrp-recovery-3-2-1-0-universal-build.html
It this the right Recovery?
Feenfleisch said:
Iam on Lineage. But after flashing TWRP not starting, only the fastboot mode
---------- Post added at 06:43 PM ---------- Previous post was at 06:36 PM ----------
https://www.nextgen-networks.de/de/...17-twrp-recovery-3-2-1-0-universal-build.html
It this the right Revolver?
Click to expand...
Click to collapse
Hey @Feenfleisch,
yes it is the correct link.
What exact commands did you use to flash TWRP?
Did the device does not boot at all or only when booting to recovery?
Only then ist booting recovery. Ich flash with Flashify
---------- Post added at 07:02 PM ---------- Previous post was at 06:57 PM ----------
The TWRP fromm the last link work (twrp-3.2.1-0-chiron_raupe-20180104-1520.img), the TWRP from your first Link not work. Maybay the wrong link?
Feenfleisch said:
Only then ist booting recovery. Ich flash with Flashify
---------- Post added at 07:02 PM ---------- Previous post was at 06:57 PM ----------
The TWRP fromm the last link work (twrp-3.2.1-0-chiron_raupe-20180104-1520.img), the TWRP from your first Link not work. Maybay the wrong link?
Click to expand...
Click to collapse
Uuuuuuups
Link leaded to Mi MIX instead of Mi MIX 2 download.
I fixed that ...
Thanks for the hint.
I've heard about several issues with flashify - better use fastboot.
USB MTP/ADB Sideload does not seem to work for me. IceMan's TWRP does.
Uploading to Google drive latest release
https://drive.google.com/file/d/1egaT1P66oEc1M0_S-tNXjG43nTLCDr3z/view?usp=drivesdk
DaCoolX said:
USB MTP/ADB Sideload does not seem to work for me. IceMan's TWRP does.
Click to expand...
Click to collapse
I'll investigate that (expect an update for this issue next week).
Thanks for reporting!
allrockedout said:
Downloads taking like 20 minutes I'll upload it to Google drive when done....
https://drive.google.com/file/d/1szvkblRyxxcVqVSqu7ejxhIkd07SUIqD/view?usp=drivesdk
Click to expand...
Click to collapse
... hmm this is very unusual - tested the speed to server and it took me a couple of seconds.
If you host the file as mirror please keep an eye for updated versions in future.
raupe said:
... hmm this is very unusual - tested the speed to server and it took me a couple of seconds.
If you host the file as mirror please keep an eye for updated versions in future.
Click to expand...
Click to collapse
Yeah I'll keep it updated of course. Plan on keeping this phone for a while. So I flashed twrp 3.2.1-0 image in twrp rebooted back into twrp..now my file storage is encrypted again. So I'll have to wipe data again... Ugh ok I'll test it out.
Cheers - downloading now.
This is vanilla TWRP right? Tired of seeing different themes, Chinese or other "customizations" in other TWRPs.
Sent from Xiaomi Mi Mix 2 @ LineageOS 14.1
I had to flash back to epic twrp. Couldn't remove encyption. After wiping data and rebooting to system than back to twrp. Everything was encrypted.
AndyYan said:
Cheers - downloading now.
This is vanilla TWRP right? Tired of seeing different themes, Chinese or other "customizations" in other TWRPs.
Sent from Xiaomi Mi Mix 2 @ LineageOS 14.1
Click to expand...
Click to collapse
Jepp this is stock/vanilla TWRP.
The only change i've made was to activate NTFS support some Qualcom specific stuff and disable the annoying "mouse" cursor that is present on default builds.
As you can read in comments (here and in Mi MIX forum) there are some hick-hacks with encryption.
This take a more deep dive because of the huge amount of variants the encryption has made from (a.k.a.: every OS build of MIUI/LOS/RR/Epic/mi-globe may use an different approach/driver for encryption).
There seems to be an problem with software and hardware encryption that conflicts with each other (see LineageOS change id 199842)
allrockedout said:
I had to flash back to epic twrp. Couldn't remove encyption. After wiping data and rebooting to system than back to twrp. Everything was encrypted.
Click to expand...
Click to collapse
Greetings @allrockedout!
Thanks for your report!
Just to figure out what leads to this behavior - could you give some information about your current firmware version, build date of the epic rom you used and what kernel the device info states?
Thanks in advance!
raupe said:
Greetings @allrockedout!
Thanks for your report!
Just to figure out what leads to this behavior - could you give some information about your current firmware version, build date of the epic rom you used and what kernel the device info states?
Thanks in advance!
Click to expand...
Click to collapse
I'm on Global Developer beta
Greetings readers!
I've build a new version today that contains some different en-/decryption libraries.
Please give it a shot and as always: Feedback is very welcome
Download: https://www.nextgen-networks.de/de/downloads/category/15-xiaomi-mi-mix-2.html
For those with touchscreen issues:
There have been made no kernel changes so dont expect any changes here.
is it suit for oreo cause my mix2 already update to 8.0, developer edition
ShawnLukeLee said:
is it suit for oreo cause my mix2 already update to 8.0, developer edition
Click to expand...
Click to collapse
Will be fine
ShawnLukeLee said:
is it suit for oreo cause my mix2 already update to 8.0, developer edition
Click to expand...
Click to collapse
Jipp, should work with 8.0/8.1 - sources used for building are 8.1 based.
I can give more detailed feedback if I'm selected for XIAOMI Android 8 global dev ROM next week.
On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app, included in our builds.
Our builds are based on the Code Aurora Forum Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Device-specific issues
Permissive.
You tell.
Note: Custom kernels are NOT supported unless the kernel says it supports PA and GMS is included!
Oh, this works on the Non-Pro variant for the most part (they are unified).
If you want to use Google Camera, i would recommend you to try Wichaya's Port.
Download
Instructions
Download the latest zip (link above)
Reboot to bootloader.
Flash the fastboot zip with "fastboot update pa_oneplus9-img-eng.vishal.zip"
Reboot into recovery after it is done flashing & wipe userdata.
Changelog for Alpha 2
Fixed up issue with Touchscreen on Pro variants.
Improvements to FOD
Overall performance changes
Automated DC Dimming
VoLTE/VoWIFI Fixed for Indian Carriers
Things to be noted :- This is still a userdebug build and is permissive.
Kernel Sources :- AOSPA/OnePlus9
ROM Source :- AOSPA
Contributors :- ZVNexus
Excellent as expected!
Will this work for TMobile variant converted to EU with the msm tool?
lendawg said:
Will this work for TMobile variant converted to EU with the msm tool?
Click to expand...
Click to collapse
Sure!
If you face any issues, ping me
Nice to see your OnePlus 9 Pro rom here! Kudos
I have le2123 model (op9pro) and there are problems with touch.
oguzxw said:
I have le2123 model (op9pro) and there are problems with touch.
Click to expand...
Click to collapse
If you want to make a bug report that's nowhere near specific enough, you should be capturing logs to supply and advising EXACTLY what "problems" you are having with touch.
le2123 logs of touch issue
logcat.txt
drive.google.com
There was a problem that I can't understand. My comment is not being edited.
le2123 logs of touch issue. https://drive.google.com/file/d/1dcFt0dTaFXa-YLPeq4MLrA2t74ykCuEm/view
avid_droid said:
Did you guys get the FOD sorted?
Click to expand...
Click to collapse
Yep!
oguzxw said:
I have le2123 model (op9pro) and there are problems with touch.
Click to expand...
Click to collapse
can you please explain the behaviour
And i would really prefer dmesg.
my english is not good enough to explain it but it is something that is very easy to understand in use
https://drive.google.com/file/d/1TvD6It45bluDncJS5vWwEYadHYcHFf2y/view?usp=sharing dmesg log
oguzxw said:
my english is not good enough to explain it but it is something that is very easy to understand in use
https://drive.google.com/file/d/1TvD6It45bluDncJS5vWwEYadHYcHFf2y/view?usp=sharing dmesg log
Click to expand...
Click to collapse
Thank, ill look into it.
malvigagan said:
Excellent as expected!
Click to expand...
Click to collapse
You bought 9 pru?
Nope xd
shubham8 said:
You bought 9 pru?
Click to expand...
Click to collapse
Thanks dev, good to see PA here..I am curious, is it mainly build for op9 or op9 pro ? thx
marko94 said:
Thanks dev, good to see PA here..I am curious, is it mainly build for op9 or op9 pro ? thx
Click to expand...
Click to collapse
It can be used on pro and non pro variants.
flashed... touch is a little off. otherwise really nice
ryantf420 said:
flashed... touch is a little off. otherwise really nice
Click to expand...
Click to collapse
What you mean, is a little off ? Share logs , maybe that can help dev
marko94 said:
What you mean, is a little off ? Share logs , maybe that can help dev
Click to expand...
Click to collapse
how would I get a log for something like that? the accuracy of touch is issue. have to hit slightly above where I normally touch....
Hi folks
Since some of you asked me to make another thread for my TWRP build, here you go, the kernel is based on EWB5 (A13) but is compatible with all currenlty released Android versions.
WARNING/DISCLAIMER: Since the outer display isn't shut down this build can cause irreversible screen burns if used extensively. As such I take no responsabilities if you damage your device while using my TWRP build (and/or) other projects that may suffer from the same issues.
Edit: after some time the "screen burn" disappeared, so it seems that it's just a remanent image. In doubt stick to the warning.
TWRP Image
Sources:
Kernel
Device Tree (Forked from @shadow-of-leaf Z Flip 3 DT)
So just push it as the recovery to the active slot via adb?
Breaks dex? If Not its kompatible with latest one ui?
It doesn't break dex, you can backup your recovery partition, it should be compatible with latest Android, since recovery is contained
Mikowitsch said:
So just push it as the recovery to the active slot via adb?
Click to expand...
Click to collapse
Yes, the usual way works fine
is the link down.. i cant download it
miman04 said:
is the link down.. i cant download it
Click to expand...
Click to collapse
Fixed !
Azkali said:
Fixed !
Click to expand...
Click to collapse
Tq sir .. can i get a simple guide on how to get the TWRP works on my fold 3. im currently on a rooted fold 3 Android 13.
Should i use odin and put in AP then flash rite away or i use fastboot?
miman04 said:
Tq sir .. can i get a simple guide on how to get the TWRP works on my fold 3. im currently on a rooted fold 3 Android 13.
Should i use odin and put in AP then flash rite away or i use fastboot?
Click to expand...
Click to collapse
Yes in Odin putting recovery.tar in AP will work fine ^^
i cant download recovery and vbmeta
Azkali said:
Hi folks
Since some of you asked me to make another thread for my TWRP build, here you go, the kernel is based on EWB5 (A13) but is compatible with all currenlty released Android versions.
WARNING/DISCLAIMER: Since the outer display isn't shut down this build can cause irreversible screen burns if used extensively. As such I take no responsabilities if you damage your device while using my TWRP build (and/or) other projects that may suffer from the same issues.
Edit: after some time the "screen burn" disappeared, so it seems that it's just a remanent image. In doubt stick to the warning.
TWRP Image
Sources:
Kernel
Device Tree (Forked from @shadow-of-leaf Z Flip 3 DT)
Click to expand...
Click to collapse
404 page on TWRP and VBMETA
Using the DT from Azkali to build a new Release of TWRP, i'll make a new Thread for that
Thanks so much @Azkali for your Device Tree, i hope to help you soon
ROM-PacMe said:
Using the DT from Azkali to build a new Release of TWRP, i'll make a new Thread for that
Thanks so much @Azkali for your Device Tree, i hope to help you soon
Click to expand...
Click to collapse
I have a newer TWRP, maybe instead of a new build we could figure something out together
Join the discord and ping me there, I'll be available later
Release q2q-5337227142 · bm0x/twrp-actions-compiler
Recovery for q2q
github.com
based on minimal-twrp branch 12.1
and uses the DT from @Azkali
enjoy!
ROM-PacMe said:
Release q2q-5337227142 · bm0x/twrp-actions-compiler
Recovery for q2q
github.com
based on minimal-twrp branch 12.1
and uses the DT from @Azkali
enjoy!
Click to expand...
Click to collapse
is it compatible with SM-926B?
q2q is SM-926B?
google didnt know anything about "q2q samsung"
Can you try, If not working, only re install the recovery stock and vbmeta too
The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?
thewayofwright said:
The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?
Click to expand...
Click to collapse
the revision is a random number gived from Github Actions, nothing more my friend
thewayofwright said:
The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?
Click to expand...
Click to collapse
only use the vbmeta and recovery tar of my own github releases, let me any update, ok?
i see soon any bug to help to fix