Database Users

[TOUCH RECOVERY] TWRP Recovery v2.7.1.0 (with SELinux)

Team Win Recovery Project , or twrp for short, is a custom recovery built with ease of use and customization in mind. It’s 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.
BUGS:
(nothing)
CHANGELOG:
v2.5.0.0> v2.6.3.4
-Add SELinux support for install kitkat correctly
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
v2.4.4.0 > v2.5.0.0
Special Note: If you are running a custom theme, the changes in 2.5.0.0 will likely not be compatible with your theme.
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
Download:
http://www.mediafire.com/download/xea7kjz7xvfozuc/recovery_TWRPv2.7.1.0_u8800pro.img

what about offmode charging? and i saw battery charge in recovery only after 1-2 min, in previous versions it didn't have this delay..

gatoringu said:
what about offmode charging? and i saw battery charge in recovery only after 1-2 min, in previous versions it didn't have this delay..
Click to expand...
Click to collapse
Its when the device is not powered on in any way and it charges when connected.

Re: [TOUCH RECOVERY] TWRP Recovery v2.4.4.0
Seems the same as the regular u8000. However, there is no getprop errors. Real nice work!
Sent from my U8800-51

Re: [TOUCH RECOVERY] TWRP Recovery v2.4.4.0
Gotta give it a try then as SomCom reviewed it as nice
-Rik[Rittik]

thanks for all the work)))

Best recovery for this phone.
Sent from my Nexus 4 using xda app-developers app

TWRP 2.5.0.0 Is almost done!!!

Somcom3X said:
TWRP 2.5.0.0 Is almost done!!!
Click to expand...
Click to collapse
Sorry for my ignorance... I've always used CWM recovery... Any little instroction for beginners on how to install it and stating to get a little knowladge with this on? //TWRP

Somcom3X said:
TWRP 2.5.0.0 Is almost done!!!
Click to expand...
Click to collapse
For u8800pro? By who?

objr said:
Sorry for my ignorance... I've always used CWM recovery... Any little instroction for beginners on how to install it and stating to get a little knowladge with this on? //TWRP
Click to expand...
Click to collapse
I will make a zip later.
SvTeam said:
For u8800pro? By who?
Click to expand...
Click to collapse
he'll release it when hes done. I do not want his Pm box becoming his gmail spam box.

Okie dokie. So we can expect a new developer for u8800pro?
Sent from my Nexus 4 using xda-developers app

SvTeam said:
Okie dokie. So we can expect a new developer for u8800pro?
Sent from my Nexus 4 using xda-developers app
Click to expand...
Click to collapse
Up to him.

Recovery updated to newest version, Enjoy

forumber2 said:
Recovery updated to newest version, Enjoy
Click to expand...
Click to collapse
Forumber2 you rock!
Edit: are the backups of the 2.4.4.0 compatible with the 2.5.0.0?

SvTeam said:
Forumber2 you rock!
Edit: are the backups of the 2.4.4.0 compatible with the 2.5.0.0?
Click to expand...
Click to collapse
Sure

Forumber, I changed I have just changed 2.4.40 with new one and is till the same version...
Sent from my U8800pro using xda premium

Well forumber2 thanks again
Sent from my SGH-T999 using xda premium

Great recovery...i never looked back on cwm after using twrp!!you may use this too its a great theme!!
{
"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"
}
http://forum.xda-developers.com/showthread.php?t=2236052
@ATMOSF3AR

/sdcard not mounted
Am i doing something wrong or is there something wrong with this recovery.
I try to install a mod that resides on sd card, but i cant seem to get to it. When i try to choose Mount/Mount SD Card nothing happenes, and in terminal it says:
E:Unable to mount 'sdcard'
The card is normally visible in ICS stock (that i am trying to change into some mod)
Help?

[AROMA] Universal PA GApps Customizer

{
"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"
}
What does 'Universal PA GApps Customizer' do?
It will generate a gapps-config based on your preferences, and save it on sdcard to can be loaded by a PA GApps package. So you can fully customize the installation!
The key words used are from TK GApps! So, older PA GApps based packages may have less key words(e.g. stock PA GApps script), or other packages which improved the stock PA GApps scripts may have more key words(e.g. Open GApps)! UPGC is an universal package, for now I just follow TK GApps key words, but soon I may start adding kind of "profiles" with key words for more packages.
Supported PA GApps based packages:
TK GApps - UPGC covers all keywords offered by this package
Open GApps - UPGC doesn't cover all key words offered by this package
Any other PA GApps based package (stock PA GApps scripts) - UPGC includes more keywords than this package offers
*Presets key words are not included (yet)
Latest version: R3
Download: https://www.androidfilehost.com/?w=files&flid=32578
Please offer feedback!
Thanks to:
@amarullz - for his AROMA Installer
@TKruzze - for his PA GApps scripts (especially update-binary)
@MastahF, @osm0sis, @TKruzze - for their PA GApps based packages

Reserved.

Not working for me.
It latest twrp it is just mentioning ... Starting Aroma ... But nothing happens and I need to force the reboot by pressing >8 Sec. Power button

Excellent. Works exactly as expected on my mako.
One minor error to be fixed: in the stock apps removal page, Browser is incorrectly labelled as CalendarGoogle.
Thanks & keep up the good work

solar666 said:
Not working for me.
It latest twrp it is just mentioning ... Starting Aroma ... But nothing happens and I need to force the reboot by pressing >8 Sec. Power button
Click to expand...
Click to collapse
Use a older version.. OnePlus One owners face this issue mostly..use TWRP 2.7.0.0 or 2.8.4.0
ahaider7 said:
Excellent. Works exactly as expected on my mako.
One minor error to be fixed: in the stock apps removal page, Browser is incorrectly labelled as CalendarGoogle.
Thanks & keep up the good work
Click to expand...
Click to collapse
Oh..thanks for report! I will fix it soon..also I will improve it a little bit

raulx222 said:
Use a older version.. OnePlus One owners face this issue mostly..use TWRP 2.7.0.0 or 2.8.4.0
Oh..thanks for report! I will fix it soon..also I will improve it a little bit
Click to expand...
Click to collapse
TK just released a new version with a new Photos keyword for the new Google Photos app!

so i flash this customizer and then flash whatever pa gapps package i have?

Update! Added "Photos" Keyword, fixed some strings, and new color theme!
Midnight_Rider said:
so i flash this customizer and then flash whatever pa gapps package i have?
Click to expand...
Click to collapse
Yes. If you save the .gapps-config in the same folder as the zip package, then be sure that PA GApps package is also in the same folder with the .gapps-config file when you flash it.

raulx222 said:
Update! Added "Photos" Keyword, fixed some strings, and new color theme!
Yes. If you save the .gapps-config in the same folder as the zip package, then be sure that PA GApps package is also in the same folder with the .gapps-config file when you flash it.
Click to expand...
Click to collapse
Finally got the chance to try this out on my old GN yesterday! Great job! It's beautiful!
Two things I was wondering about:
1) Is it possible for it to detect if there is already a .gapps-config/gapps-config.txt and load the "current saved config" from it as a starting point?
2) Can the UPGC zip directly flash the GApps package after it writes the config file? I think @hlxanthus was close to figuring this out (if he didn't actually have it working). :good:

osm0sis said:
Finally got the chance to try this out on my old GN yesterday! Great job! It's beautiful!
Two things I was wondering about:
1) Is it possible for it to detect if there is already a .gapps-config/gapps-config.txt and load the "current saved config" from it as a starting point?
2) Can the UPGC zip directly flash the GApps package after it writes the config file? I think @hlxanthus was close to figuring this out (if he didn't actually have it working). :good:
Click to expand...
Click to collapse
1) Of course. But to read the .gapps-config and then to set the settings from AROMA based on .gapps-config it's some work and I can't implement this feature right now. Another simple way to do the same thing, is to save the .prop files (where the settings from AROMA are stored) on sdcard and load them in the coming installations.
2) Uhm, I don't know if that is possible. If @hlxanthus knows, I'm open to listen

osm0sis said:
Finally got the chance to try this out on my old GN yesterday! Great job! It's beautiful!
Two things I was wondering about:
1) Is it possible for it to detect if there is already a .gapps-config/gapps-config.txt and load the "current saved config" from it as a starting point?
2) Can the UPGC zip directly flash the GApps package after it writes the config file? I think @hlxanthus was close to figuring this out (if he didn't actually have it working). :good:
Click to expand...
Click to collapse
raulx222 said:
1) Of course. But to read the .gapps-config and then to set the settings from AROMA based on .gapps-config it's some work and I can't implement this feature right now. Another simple way to do the same thing, is to save the .prop files (where the settings from AROMA are stored) on sdcard and load them in the coming installations.
2) Uhm, I don't know if that is possible. If @hlxanthus knows, I'm open to listen
Click to expand...
Click to collapse
1) @raulx222 a working method is included in the package I sent you a while ago. But it is quite convoluted getting it working, but worth it on the end. But, as I assume, if free time is a factor we understand why you don't implement it.
2) To actually call another script/zip to flash from within this aroma package? Well in theory you can call it to unzip to /tmp then set permissions on tkruzzes update-binary (which is just a bash script in the end) and run it. But I was never able to get this to work. If there is a more direct way to do this, I have no idea..

Looks like google clock is missing on the include/exclude keyword in R2

raulx222 said:
Use a older version.. OnePlus One owners face this issue mostly..use TWRP 2.7.0.0 or 2.8.4.0
Click to expand...
Click to collapse
Is this going to be fixed, or will it stay like this?

scorpionhd2 said:
Is this going to be fixed, or will it stay like this?
Click to expand...
Click to collapse
I can't fix that. We must wait for amarullz to release an update for AROMA Installer.

raulx222 said:
I can't fix that. We must wait for amarullz to release an update for AROMA Installer.
Click to expand...
Click to collapse
Got it, thanks!

[GUIDE] Dualboot CM13 and TouchWiz on Samsung Galaxy S6

/* INFO */
Hey guys, yesterday I've been able to dualboot CM13 and TW on my Galaxy S6. I didn't try all possible combination and will update this thread with your experience.
/* DISCLAIMER */
Your warranty is now void.
I am not responsible for bricked devices.
/* WHAT YOU NEED */
1. A Custom Recovery (TWRP or PhilZ Touch)
2. a TouchWiz ROM
3. The Dualboot Patcher : http://forum.xda-developers.com/showthread.php?t=2447534 (Download the APK)
4. CM13 : http://forum.xda-developers.com/galaxy-s6/orig-development/cyanogenmod-13-galaxy-s6-t3269984
/* INSTALLATION STEPS */
1. Make a nandroid backup in case anything fails. (optional if you like playing with fire like me)
2. Install the Dualboot patcher.
3. In the patcher, go to the ROMs section, and a popup will ask you to set the kernel. Do it.
4. In the patcher, go to the Patch ZIP file section, open your CM13 zip file and patch it (and GAPPS) to install in data and select zerolte in the device section. Patch the zip. (See known issues)
5. Restart in recovery, flash the patched zip files (ROM and GAPPS). Restart your phone.
6. It will now boot onto CM13, once you've completed your first boot setup, install the dualboot patcher.
You are now able to select which rom to boot from the ROMs section. Once you've selected which rom is the default, restart your phone. Voilà!
/* KNOWN ISSUES */
- If you are getting a bootloop booting your secondary rom, reflash the kernel of your primary slot and reset your kernels. You can then reset your kernels and wipe data/cache of your secondary rom from the app.
- Patch your CM13 ROM to install in the data slot. (Some TW roms take too much space in system). (See 2nd screenshot)
- You need to flash CM13 on an EXT4 partition. F2FS isn't supported.
/* SPECIAL THANKS */
@sktjdgns1189, @tdcfpp and @arter97 for their hard work on CM13.
@chenxiaolong for the dualboot patcher.
@dovah Testing CM13 as secondary ROM and discovering the system partition issue.
@ktetreault14 For giving me the information about the data partition not being wiped on factory reset.
/* SCREENSHOTS */

Definitely going to try this later today, but with TW as my first ROM.
Don't forget to make a nandroid backup, just in case anything fails

Termynat0r said:
Definitely going to try this later today, but with TW as my first ROM.
Don't forget to make a nandroid backup, just in case anything fails
Click to expand...
Click to collapse
Please let me know if it works, i will update the OP. Since CM13 is subject to a lot more updates than TW, i think it would be a lot better to install it as secondary but i don't know if patching the zip works, since arter97's kernel and back-to-n0t3 rom didn't work
I will add a section for nandroid backup aswell

Gonna try this too on 925F and WETA ROM as primary (with Hacker kernel). Will update this if it works.

I have been in contact with chenxiaolong regarding this device for awhile. Arters kernel doesn't work because of his own dualboot implementation interfering with the patcher.

ktetreault14 said:
I have been in contact with chenxiaolong regarding this device for awhile. Arters kernel doesn't work because of his own dualboot implementation interfering with the patcher.
Click to expand...
Click to collapse
Yes i remember being in contact with you on that old cm12 whatsapp group from mythos. I'm wondering why arter's cm kernel works, he still has his own dualboot implementation. Maybe setting the first kernel without patching the zip file works. We'll have to investigate.

Which rom(s) is/are working as TW base?
Thanks for the guide!

FaserF said:
Which rom(s) is/are working as TW base?
Thanks for the guide!
Click to expand...
Click to collapse
I patched Xtrestrolite myself, but i know that others would work.

Works with XtreStoLite 2.4, thanks for clear instructions

Working like a charm on my 925F! Thank you so much!
{
"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"
}

virulentt said:
I patched Xtrestrolite myself, but i know that others would work.
Click to expand...
Click to collapse
Thanks, another question.
Has anybody tested to dual boot it with stock rom rooted + CM13 as secondary? Would find that combination interesting
If nobody has tested it, could it work?

gdr_01 said:
Working like a charm on my 925F! Thank you so much!
Click to expand...
Click to collapse
Thank you for the screenshot

Anybody tried this with back-to-n0t3 as base rom? How'd it go?
Sent from my SM-G920I using Tapatalk

FaserF said:
Thanks, another question.
Has anybody tested to dual boot it with stock rom rooted + CM13 as secondary? Would find that combination interesting
If nobody has tested it, could it work?
Click to expand...
Click to collapse
We're still unsure since Arter has his own dualboot method implemented in his kernels. It could work, it could not work.... still waiting for feedback to update the thread!

sapnesh said:
Anybody tried this with back-to-n0t3 as base rom? How'd it go?
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
We know for a fact that back-to-n0t3 can't be patched. It could work as primary rom and set the kernel like i did with CM13, but we're still not sure if patching cm13 works lol.

I tried using TW as primary and CM13 as a secondary ROM, no dice sadly... It fails flashing CM, I'll have a look at the log to see if I can work out why, but it seems that running CM as primary will be the easiest option for most users.

dovah said:
I tried using TW as primary and CM13 as a secondary ROM, no dice sadly... It fails flashing CM, I'll have a look at the log to see if I can work out why, but it seems that running CM as primary will be the easiest option for most users.
Click to expand...
Click to collapse
Thank you for the clarification. So CM13 can only be a primary rom as we speak. I'm wondering if we flash an update over it, if it will override our secondary rom since it is stored in the system partition. I think there is an option to store the secondary rom in the data partition, we'll need to do some testing here again. Thank you for your information dovah

virulentt said:
Thank you for the clarification. So CM13 can only be a primary rom as we speak. I'm wondering if we flash an update over it, if it will override our secondary rom since it is stored in the system partition. I think there is an option to store the secondary rom in the data partition, we'll need to do some testing here again. Thank you for your information dovah
Click to expand...
Click to collapse
No problem ! Yeah some testing will be needed as new versions of CM come out, but it shouldn't be too complicated, I believe that in the dualboot app, there is a way to modify the primary ROM so that it doesn't erase the secondary one !

dovah said:
No problem ! Yeah some testing will be needed as new versions of CM come out, but it shouldn't be too complicated, I believe that in the dualboot app, there is a way to modify the primary ROM so that it doesn't erase the secondary one !
Click to expand...
Click to collapse
I don't think it would work since it is the same way of patching a zip file...
I would love if arter could remove his own dualboot implementation to use this app instead. I know he's more into fancy and complicated ways, but this application will help the community to provide feedback.

Yeah I tried it with rooted Stock TW as primary but it fails flashing the CM13 zip.
I had a look at the logfile
Some errors occurs on unmounting, so I tried unmounting everything first and flash via sideload, no luck.
I think this is the first error (I checked via adb shell and the path /tmp/install doesn't even exist during flash)
Code:
[D] update-binary-tool: Mounted /mb/system.img at /system
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
/tmp/install/bin/backuptool.sh: cd: line 112: can't cd to /tmp/addon.d/
md5sum: can't open '*sh': No such file or directory
Then it has a chain of these
Code:
[W] /system/multiboot/dual/system/bin: Failed to create directory: No space left on device
Trying to find the error...

[SHARE][5.1.1][CM-based] FlymeOS for Alcatel Idol 3 5.5

{
"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"
}
Hello,everyone.
I am simply sharing this with others! All the credit goes to the person who made this build!
The original thread is HERE(if you cant enter the page,turn on VPN as US,and it will work)
I reuploaded the build because one had to make several chinese accounts in order to download the rom at only 200 kb/s,which was extremely bothersome and time-consuming.
INSTRUCTIONS:
1.Wipe Dalvik,System,Data and Cache
2.Flash the rom(it will most likely fail)
3.Reboot the recovery
4.Flash the rom again,without previously wiping anything(wiping directly before flashing it will cause errors while installing,for unknown reasons)
5.Flash this boot.img(the stock one boots only on 1806 variant):https://www.androidfilehost.com/?fid=24438995911971047
6.Reboot,and let the system fully boot
7.Boot into recovery
8.Flash Gapps
9.Reboot​
DOWNLOAD​
XDA:DevDB Information
FlymeOS, ROM for the Alcatel Onetouch Idol 3
Contributors
The Marionette
Source Code: http://bbs.tclmobile.com.cn/forum.php?mod=viewthread&tid=37841&extra=page%3D1&mobile=2
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-03-05
Last Updated 2016-03-09

Nice!! Going to flash now!
EDIT: ROM works flawlessly, very snappy. I didn't flash the boot.img because my phone would go into a bootloop. ROM works fine without it at least for my device(6045O)

Thanks @The Marionette.
Where is an issue with popup dialog box: background is dark and text too, it's difficult to read.
Whe have to debloat chinese apps and install Playstore.
Installation of open-gapps 5.1.1 work but can't connect to google account.

murigny64 said:
Thanks @The Marionette.
Where is an issue with popup dialog box: background is dark and text too, it's difficult to read.
Whe have to debloat chinese apps and install Playstore.
Installation of open-gapps 5.1.1 work but can't connect to google account.
Click to expand...
Click to collapse
I used Kingroot it comes pre-installed to remove the bloatware apps try that and google login worked for me.

murigny64 said:
Thanks @The Marionette.
Where is an issue with popup dialog box: background is dark and text too, it's difficult to read.
Whe have to debloat chinese apps and install Playstore.
Installation of open-gapps 5.1.1 work but can't connect to google account.
Click to expand...
Click to collapse
gazasalim said:
I used Kingroot it comes pre-installed to remove the bloatware apps try that and google login worked for me.
Click to expand...
Click to collapse
Yeah,I do not know why Google Play Services wont work with Flyme...
As for the black dialog boxes:It is a bug in the framework,and the maker of the Flyme build for the Idol 3 said that he will fix it asap.

i have problem with installing gapps when i install it's black screen
edit:i tried many times but i get black screen,i tried with gapps 64 5.1 nano and pico and same?

Thanks for sharing and feedback
Wont flash if you are coming from stoc,flashed cm sys image and then flashed rom,didnt have to flash aditional boot.img
very diferent from other roms,really snapy,no bugs beside black popup dialog window,it has some usefull apps pre instaled but in chinese (for me thats another bug lol)
nice tnx @The Marionette keep up the good work with other roms

I also tried it few days earlier but found heating problem in my 45i. So moved away from it.

The Marionette said:
Yeah,I do not know why Google Play Services wont work with Flyme...
As for the black dialog boxes:It is a bug in the framework,and the maker of the Flyme build for the Idol 3 said that he will fix it asap.
Click to expand...
Click to collapse
to serve the boot file. img that aid is a kernel

Can anyone help me the problem with insta.lling gapps because i get black screen or welcome and setting was stopped

aleksandar.d123 said:
Can anyone help me the problem with insta.lling gapps because i get black screen or welcome and setting was stopped
Click to expand...
Click to collapse
im also gettig seetings stoped at welcome screen right after i install gapps,im gonna try few more times and let you know is there a way
Sent from my V8 Idol3 running pure octans
Managed to get past the black screen by swiping down sttusbar and somehowe got in settings cleared data for google playstore and services but cant log in to google acc (error comunicatig with google srevers)

nero curin said:
im also gettig seetings stoped at welcome screen right after i install gapps,im gonna try few more times and let you know is there a way
Sent from my V8 Idol3 running pure octans
Click to expand...
Click to collapse
OK i will wait

Tried to flash the rom from external sdcard with TWRP but encountered a mount error. Any advice?
Note: appears the error doesn't affect the installation. Nevermind.

gbs97 said:
Tried to flash the rom from external sdcard with TWRP but encountered a mount error. Any advice?
Note: appears the error doesn't affect the installation. Nevermind.
Click to expand...
Click to collapse
i have the same error here's solution
1.flash *you will get fail and mount error
2.then reboot to recovery
3.flash without wipping
4.automaticly reboots when it's installed,turn off and go to recovery and mount the system
5.Reboot System
This the full procedure it's works for me

aleksandar.d123 said:
i have the same error here's solution
1.flash *you will get fail and mount error
2.then reboot to recovery
3.flash without wipping
4.automaticly reboots when it's installed,turn off and go to recovery and mount the system
5.Reboot System
This the full procedure it's works for me
Click to expand...
Click to collapse
Thanks for the quick reply. For step 4, which partitions to mount?

gbs97 said:
Thanks for the quick reply. For step 4, which partitions to mount?
Click to expand...
Click to collapse
click on system and then reboot system and wait to system boot

Thanks for sharing
Thanks for sharing .
There are some bugs like can't connect to my google account or use data over the mobile network.
I hope it will be fixed.
PS : someone knows how to make a theme for this os? Thanks in advance

luigi024 said:
Thanks for sharing .
There are some bugs like can't connect to my google account or use data over the mobile network.
I hope it will be fixed.
PS : someone knows how to make a theme for this os? Thanks in advance
Click to expand...
Click to collapse
Mobile data works.

The Marionette said:
Mobile data works.
Click to expand...
Click to collapse
To fix google account and apps install under playstore, you have to comment line in build.prop BEFORE install gapps.
Code:
ro.build.fingerprint= blablabla
just add # at the begin like this:
Code:
#ro.build.fingerprint= blablabla
and then, install open-gapps 5.1.
it work fine for all regions
For better battery lifetime, you can take ramdisk from Flyme and Arde Dev CM zImage.

murigny64 said:
To fix google account and apps install under playstore, you have to comment line in build.prop BEFORE install gapps.
Code:
ro.build.fingerprint= blablabla
just add # at the begin like this:
Code:
#ro.build.fingerprint= blablabla
and then, install open-gapps 5.1.
it work fine for all regions
For better battery lifetime, you can take ramdisk from Flyme and Arde Dev CM zImage.
Click to expand...
Click to collapse
any links for ramdisk.and thanks for this gonna try it now
Sent from my V8 Idol3 running pure octans

[GUIDE] Android 9 Pie AOSP phh-treble ROM

The purpose of this thread is to describe treble ROM installation process for Mi Max 3 with specific detail for AOSP phh-treble, for a user to be able to get all required instructions in one place.
What does not work (everything else is supposed to be working):
VoLTE (did not have a chance to verify, reported for other GSI ROMs)
Stock camera does not auto-rotate photos (use third party camera)
Equalizer (MusicFX)
Disclaimer: Everything you do is your own risk. GSI is ARB-agnostic, since it does not contain firmware.
Prerequisites:
Bootloader unlocked
Data backed up (factory reset is required in the process). NB: if you had screen locked while backing up with recovery, this guide to reset the lock may be helpful some day in the future
TWRP 3.2.3 (other recoveries may work as well) installed
Xiaomi.eu Android Pie ROM installed
Note:Xiaomi.eu with Android Pie is required.
Skills required:
TWRP - flash zip files
Archive tool (like ZArchiver, to unpack XZ system image)
Steps:
Choose and download the "arm64-aonly" system image - with or without root and gapps. I used system-arm64-aonly-vanilla-nosu.img.xz from phh-treble releases page
Decompress system image using archiver tool, we need .img to flash
Download opengapps x64 nano or pico for Android Pie (this step is for vanilla system)
Download phh-treble-pie-fixes-minimal.zip for Bluetooth, camera2 and vendor fingerprint (the file is attached to FP)
Make sure your data is backed up
Make sure Xiaomi.eu ROM is already installed, or reinstall using respective instructions
Reboot to recovery
Install - select image type - select phh-treble .img file - select system partition - install
Install - select zip type - select opengapps archive - install (for vanilla image, this is not needed for image with pre-baked gapps)
Install - (make sure /vendor is mounted) select zip type - select phh-treble-pie-fixes-minimal.zip from this post below (to fix brightness, camera2 api and bluetooth)
Factory reset, note: google setup needs gapps-su build or you can dirty flash (restore /data from backup)
Reboot system, fingers crossed for several minutes. If the system does not boot for 2 minutes, you probably did not perform some step correctly
bonus material: one can re-arrange soft buttons following instructions from this post https://www.xda-developers.com/how-...icons-or-re-arrange-the-buttons-without-root/
bonus material: one can adjust auto brightness by issuing "settings put system screen_auto_brightness_adj 0.4" via ADB shell, where 0.4 is any value between -1 and 1
Note: to completely unroot, execute /system/bin/phh-securize.sh via adb root shell
Thank you!

So if I have Xiaomi.eu stable and go back to beta 8.10.25 (with ARB activated) I will be able to install this AOSP ROM ?
Before MI MAX 3 I got a OP3 so ARB is my nightmare.
I am dreaming of AOSP ROM installed. Is much better than that MIUI.

mvha said:
So if I have Xiaomi.eu stable and go back to beta 8.10.25 (with ARB activated) I will be able to install this AOSP ROM ?
Before MI MAX 3 I got a OP3 so ARB is my nightmare.
I am dreaming of AOSP ROM installed. Is much better than that MIUI.
Click to expand...
Click to collapse
Yes, you can. Treble roms can be installed on ARB and NON-ARB roms.

Battery life looks decent so far
{
"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"
}

Great guide. Thanks so much .
So is it safe to install 8.1 ROM on 9.0 too?

mvha said:
Great guide. Thanks so much .
So is it safe to install 8.1 ROM on 9.0 too?
Click to expand...
Click to collapse
Tried both phh-treble 8.1 and 9.0. GSI roms can be flashed one over another (factory reset may still be required for downgrade 9->8.1)

New Pie release with November security patch and some fixes
https://github.com/phhusson/treble_experimentations/releases/tag/v107

Hello guys.I own mi max 3 with unlocked bootloader, and installed xiaomi.eu stable.I would like to transform it to stock android device.Is this roms are stable for daily use, without fail, or battery drain?
Is it possible to make more detailed steps for newbies like me.. thank

galev_90 said:
Hello guys.I own mi max 3 with unlocked bootloader, and installed xiaomi.eu stable.I would like to transform it to stock android device.Is this roms are stable for daily use, without fail, or battery drain?
Is it possible to make more detailed steps for newbies like me.. thank
Click to expand...
Click to collapse
Hi @galev_90, it's stable with known issues - bluetooth and brightness need a fix described in the first post. MTP (usb file transfer) does not work (the patch may exist, did not try any), volte - probably does not work.
To get more specific instructions, one needs to explain what is not clear from what is already described. It may be helpful to read phh-treble thread by phhusson as well.

Allready instaled pixel experience rom on my mi max3 via another guide.evrythings work fine, and i test it

galev_90 said:
Allready instaled pixel experience rom on my mi max3 via another guide.evrythings work fine, and i test it
Click to expand...
Click to collapse
Link pleased.

It is not in this forum.Maybe link will be problem..

Instruction updated for latest Xiaomiu.eu baseline. MTP is fixed in 8.11.29 vendor.
Patch prepared for direct flashing via TWRP.

What does the patch do?
Edit: nevermind - found it in the OP: phh-treble-pie-fixes.zip - fixes auto brightness and bluetooth

New build v108 is up : https://github.com/phhusson/treble_experimentations/releases/tag/v108
Changelog: https://forum.xda-developers.com/showpost.php?p=77392674&postcount=1

Lecterr said:
New build v108 is up : https://github.com/phhusson/treble_experimentations/releases/tag/v108
Changelog: https://forum.xda-developers.com/showpost.php?p=77392674&postcount=1
Click to expand...
Click to collapse
I'm downloaded aonly gapp su version. Nothing failed in the new build 108. And I'm no flash anything else. Only aonly file.

chetchuakaka said:
I'm downloaded aonly gapp su version. Nothing failed in the new build 108. And I'm no flash anything else. Only aonly file.
Click to expand...
Click to collapse
Test Bluetooth media and phone calls.

My screen flickers when adjust brightnes...anyone else? Build 108...

Lecterr said:
My screen flickers when adjust brightnes...anyone else? Build 108...
Click to expand...
Click to collapse
Then brightness isn't fixed by default yet after all?

Hello everyone, installed the V108 and I also flash the screen with the brightness in automatic, otherwise everything works perfect, I do not use the calls by bluetooth, thanks for the ROM. a greeting