yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] consumimur:
completely bug free . thanks . less settings from sgc versions and night sight is a bit darker that sgc but everything is working with no crashes at all .for those having crashes or it is not installing , you have to enable 2api and add the commands for pie first guys . https://xdaforums.com/mi-a2/how-to/how-to-enabling-cam2-gcam-android-t3868766
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] k00r:
After few moments freeze while shot.

Logcat.

View attachment 4688255
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] boe323:
where photo booth? slow crashes
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] elzafir:
Only older Google Camera v3.xx works without root.
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] elzafir:
This works on Mi A2 on stock Android 9.0 Pie v10.0.2.0 (unlocked bootloader, rooted with Magisk, build.prop changes made systemlessly with MagiskHide Props Config v3.0.3 module) with a few crashes here and there when starting up and changing modes. But slow-mo works, 4K video works, front cam works. Just be sure to activated all four build.prop entries:

Code:

setprop persist.camera.HAL3.enabled 1

setprop persist.vendor.camera.HAL3.enabled 1

setprop persist.camera.stats.test 5

setprop persist.vendor.camera.stats.test 5
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] bariz143:
Anyone have a updated version for this one?
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] poyraz aydın:
sample photograph

Thank you. Working perfectly !

:cool:
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] Krishnasai2998:
Unable to install gcam in mia2

I tried unlocking bootloader with commands but it was unsuccessful , installed gcam but It won't work as my phone doesn't have camera2 API enabled. Can someone tell me how to use gcam on mia2

Thanks.
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] dieselman6969:
O have unlock bootloader and Root my mi A2 can i install the oficial updates?
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] mariosenta:
https://xdaforums.com/mi-a2/how-to/how-to-enabling-cam2-gcam-android-t3868766
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] Sivakumar$:
Bro there's a simple tutorial use that boot patchedimg method and u can have temp root to enable camera2api then after u can also receive and update ota without any issue
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] sampit76:
Greeting,

Did you enable Camera 2 api without UBL and without root? Only adb command?

Could you please share the method/step by step.

Thanks & best regard
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] mariosenta:
You have to unlock bootloader and you have to root, but when you finish enabling cam2api, you can unroot the device, but bootloader have to stay unlocked. Check this tread:

https://xdaforums.com/mi-a2/how-to/how-to-enabling-cam2-gcam-android-t3868766
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] pruiz96:
Hi, I wanna install it in my Xiaomi Mi A2, but I don´t know how to do it, can someone explain me?
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] cyrill2211:
How did you use adb to enable camera2api? What are the risks??
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] Kazeeto:
Not working ☹️

It can't be opened on my mi 6X although i have upgraded my phone to latest version MIUI and Android Pie.

Please help.
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] pratyush07:
Should I root?

Is the new/current version stable and is it worth rooting my device?
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] gdimak:
Thank you!
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] suraj4783:
Re Upload gcam for mi a2 in google drive
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] Habbolo:
please reupload in drive

Fallen link
[Mogul, XV6800 General] ca3sar:
I had taken the card out to plug into an adapter and attach a 3gp movie. Once i took card out and tried through my laptop, the card looked like all the files changed to boxes. Now when inserting card into phone it doesn't pick up anything and shortcuts failed. One problem is that i have my spb backups on the storage card and alot more. Any help would be awesome. Will a hard reset restore the card?

--Im currently running pocket mechanic for recovery, we will see.

http://forum.ppcgeeks.com/showthread.php?p=255562#post255562
[Mogul, XV6800 General] bedoig:
Sounds like the card may be corrupted. You can try to salvage what you can from the card by copying it to your PC, but you will most likely have to format it and start over.
[Xiaomi Redmi Note 5 Pro Themes, Apps, and Mods] elkhshap:
i need to change navbar icon by themes

how to do that?
[Xiaomi Redmi Note 5 Pro Themes, Apps, and Mods] RupeshRN:
You Can Change Navigation Bar Icon to Install Parallel Dark, Parallel Light, etc Themes if You on Miui Rom

:)
[Xiaomi Redmi Note 5 Pro Themes, Apps, and Mods] elkhshap:
i'm in miui rom 10.0.4.0 stock no root till now
[Xiaomi Redmi Note 5 Pro Themes, Apps, and Mods] RupeshRN:
Not Need To Root for Change Navigation Button From Theme.

Just Install Below Theme and Apply.

Android Oreo pro

Parallel Dark

Parallel Light

Dark NY

Android P, etc

:)
[Xiaomi Redmi Note 5 Pro Themes, Apps, and Mods] ronit0806:
Where is the download link
[Xiaomi Redmi Note 5 Pro Themes, Apps, and Mods] elkhshap:
NO CHANG navbar icon
[Xiaomi Redmi Note 5 Pro Themes, Apps, and Mods] bunbury:
Open Themes and search for them, it's easy.

The Nav Bar that I use is the one from "SUI10 v10" theme, and it's great also.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] Manniac:
I'm kinda a noob at this but I'm not completely clueless. .. I've tried a couple one click apps, watched a few videos, and read countless articles without any luck. .. can someone help me? If it's even possible....
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] GregJ7:
From all I've read, no, you can't. You can root NC2 (Android 4.4.2 KitKat) or OC1. You might check this post out.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] digitalcandy4me:
An old thread, but I just wanted to leave this for others.

There aren't any public tools to directly root the OC3, OC2, or OC1 Lollipop firmwares for the N900A.

However, it is possible to achieve root by wiping the phone, installing the NC2 (KitKat) firmware, and then upgrading the OCx, while preserving root access.

I had followed the threads (at the time back then) using SafeStrap methods, but I couldn't get SafeStrap to work with OC3, so I had to abandon SafeStrap and use FlashFire to install OC3 and maintain root.

After that, I deodexed OC3, install xposed, and was up and running happy.

I'm not sure exactly what Samsung fixed, but OC3 was released a full 18 months after OC2, so I think it's a more secure software release (only 2.5 years old, instead of 4+ years, heh). I recall that on OC2, some of the stagefright CVE's still showed as vulnerable, but I just ran the Zimperium app on OC3 and see it reports that it's not vulnerable to any of the CVEs.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] FluppingCrud:
[MENTION=7337047]digitalcandy4me[/MENTION] thanks for the helpful info. This is one of the few times I've read this solution. It's the only one I've seen that seems promising.

Like OP I'm newb. But I've never rooted a phone. I've done plenty of other tech but I hate coding. I just want to change the dumb stock rom on this phone. Bloatware haunts me simply on principal.

I have "unlocked" att 5.0 lollipop Samsung n900a 0c3 and info on this phone is crickets. I have no idea how to downgrade to 4.4, I'm not confident it will even work but I'll try it. I paid 70$ so no big deal + it seems like I couldn't even succeed in bricking this stupid vault.

ANYWAY could you possibly give some more detail on how to do this? I know people hate getting vague questions on this bo:rolleyes::confused:ard but it seems like there's no where to find answers. I really have looked.

:crying: :confused:
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] chrisnice906:
Flash nc1 firmware, towel root....install busybox and safe strap and flash away.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] chrisnice906:
Read my answer!
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] chrisnice906:
Maybe u should not be modifying phones.
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
I made this thread so all those trying to compile twrp for op6t can come together.

We can share ideas. What we have and have not got to work. What will work and what won't work.

Basically a thread where all information regarding twrp can be found in one location.

###########

#Please pm me #

##########

If using open source built roms and you have issues with twrp we may need to modify source in the rom or our twrp source.

Please report to rom maker as well.

Things to include.

What source 9.0 or 8.1

Compiling errors.

Post #2

Is where the download links are kept and updated.

Post #3 is where the other variations of twrp for source built roms or ports will be available to download if needed.
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
New test. twrp-op6t-test-0.3.img TEST ONLY!

[MENTION=1314742]Dameon87[/MENTION] & myself have been working on this recovery for a while. We think it will get better. There are still bugs and issues with twrp. We would like your feedback.

Thanks

I am not responsible for anything that can happen to your device.

Rebuilt and fully working mke2fs

Decryption works

Storage works.

Please test and let us know what works and what doesn't.

twrp-op6t-test-0.2.img

https://www.androidfilehost.com/?fid=11410963190603862182

Updated twrp

Added more functionality ability to flash all zips and Ota's

Backup and restore all partitions including data.

Twrp-op6t-test-0.3.img

https://www.androidfilehost.com/?fid=11410963190603871199

New test twrp-unified-0.4.img

Everything working as usual

Cleaned up source and added [MENTION=4712355]mauronofrio[/MENTION] notch theme

Twrp-0.4.img

https://www.androidfilehost.com/?fid=11410963190603875438

Twrp installer thanks to [MENTION=4712355]mauronofrio[/MENTION]

https://www.androidfilehost.com/?fid=11410963190603876589

Updated twrp to decrypt 9.0.10

Twrp-0.5.img

https://www.androidfilehost.com/?fid=11410963190603879261

Twrp installer

https://www.androidfilehost.com/?fid=11410963190603879262

New test

Fixed screenshot color when taking screen shots in recovery.

Fixed touch vibration.

Please test and report back.

Twrp-0.6.img

https://www.androidfilehost.com/?fid...63190603880512

Twrp installer

https://www.androidfilehost.com/?fid...63190603880513

Device source

https://github.com/TWINNFAMOUS/android_device_oneplus_fajita

Bootable recovery source

https://github.com/OP6T-TWRP/android_bootable_recovery

Hope you all enjoy
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
This is where I will keep other twrp variations if needed for all source built roms and ports for our device. When available these will only be meant for testing. Thanks
[OnePlus 6T  Guides, News, & Discussion] dpryor88:
You're from the HTC u11 life! You made that phone awesome while I had it. Good to see you here!
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
I'm trying to build with 8.1 source and I get errors so build doesn't finish.

Is there anyone that's building successfully with 8.1?
[OnePlus 6T  Guides, News, & Discussion] mauronofrio:
Me, can you explain what are you doing exactly? Which source are you using?
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
I'm trying with full omni source on 8.1. I've used the device source from both op6 & op6t without modifying just to see if it would be and it fails. I'll post output error soon as I can.

I don't have issues building with 9.0 source after I modify device source but it won't boot to twrp just stock recovery like it's not selecting the rite slot
[OnePlus 6T  Guides, News, & Discussion] Dameon87:
Make sure if you're using a newer version of Ubuntu with GCC 7+ you do: export LC_ALL=C

That should get you past the initial build errors.
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
Thanks for the info. I upgraded to linuxmint19 Recently. Guess I didn't pay attention to the changelog.
[OnePlus 6T  Guides, News, & Discussion] Dameon87:
You also need to change two lines in the build/tools/buildinfo.sh :

echo "ro.build.version.release=$PLATFORM_VERSION"

echo "ro.build.version.security_patch=$PLATFORM_SECURITY_PATCH"

to:

echo "ro.build.version.release_orig=$PLATFORM_VERSION"

echo "ro.build.version.security_patch_orig=$PLATFORM_SECURITY_PATCH"
[OnePlus 6T  Guides, News, & Discussion] mauronofrio:
And you need to increase the PLATFORM_VERSION to 16.1.0 ( in the new pixel 3 TWRPs is used 16 ) in build/core/version_defaults.mk to override Google's anti-rollback features
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
The only issue I found was my lack of awareness. Ive been fighting with the 8.1 source all because the newer os I installed. I'm testing things out.

One thing I know is if the security patch level and date doesn't match what's in the phone then decryption won't work.

So I'm starting there.
[OnePlus 6T  Guides, News, & Discussion] Dameon87:
Was this taken from the default/stock recovery or just a standard boot? I've been using the twrp-8.1 branch (Which uses android_bootable_recovery 9.0 branch by default now). I've tried a multitude of things, but I simply just get the e4crypt_initialize_global_de fail error as well. I think the way things are done for the Pixel 3/XL are the way to proceed, but aside the device tree we don't have much else to go on.
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
Maybe Fstab files need modifying

The recovery.fstab I pulled out of the boot.Img has a data partition labeled f2fs

And a Data partition labeled ext4
[OnePlus 6T  Guides, News, & Discussion] Dameon87:
Already tried that but I didn't really get anything different. There's a few issues that are happening I think.

Dmesg repeats this over and over and over:

<3>[19700123_15:34:23.729788]@4 FG: fg_psy_get_property: unsupported property 27

<14>[19700123_15:34:26.049860]@4 init: starting service 'boot-1-0'...

<11>[19700123_15:34:26.050060]@4 init: property_set("ro.boottime.boot-1-0", "798060609590") failed: property already set

<11>[19700123_15:34:26.050448]@0 init: cannot execve('/sbin/android.hardware.boot@1.0-service'): No such file or directory

<14>[19700123_15:34:26.051342]@4 init: Sending signal 9 to service 'boot-1-0' (pid 762) process group...

<14>[19700123_15:34:26.051372]@4 init: Successfully killed process cgroup uid 0 pid 762 in 0ms

Then just getting this according to the recovery.log:

I:File Based Encryption is present

e4crypt_initialize_global_de returned fail

e4crypt_initialize_global_de returned fail

e4crypt_initialize_global_de returned fail
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
This is probably why it won't even boot twrp built with 9.0
[OnePlus 6T  Guides, News, & Discussion] Dameon87:
Are you doing a minimal build env, or pulling in the entire Omni tree? There is only a twrp-8.1 branch for the minimal manifest, but that does pull in android_bootable_recovery 9.0 branch. I can get both to compile and boot fine.
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
Full sources on both 8.1 and 9.0
[OnePlus 6T  Guides, News, & Discussion] Dameon87:
Alright I'm doing a full sync of the omni repo and will give that a try next. I had been just using the minimal manifest.
[OnePlus 6T  Guides, News, & Discussion] Dameon87:
Yeah so far I can't boot with 9.0 branch. I'm going to try to do some debug and figure out what's going on. I can't even get into adb shell like normal to see what's going on, though.
[OnePlus 6T  Guides, News, & Discussion] Nsane457:
If I'm not mistaken, android-9.0 implies PLATFORM_SDK_VERSION is 28.

I don't have much experience building for Android but it should be noted that the build would enable -DUSE_KEYSTORAGE_4 which uses android.hardware.keymaster@4.0, so /vendor/bin/hw/android.hardware.keymaster@4.0-service-qti should probably be added to device/oneplus/fajita/recovery/root/sbin, a line should be added to prepdecrypt.sh, and a service entry should be added to device/oneplus/fajita/recovery/root/init.recovery.qcom.rc.

Strange thing is, in an ADB shell, something like ls -l /sbin/android.hardware.boot@1.0-service will list the file with root ownership but actually trying to execute it results in No such file or directory.
[OnePlus 6T  Guides, News, & Discussion] Dameon87:
Yep, I've already grabbed the android.hardware.keymaster@4.0-service-qti and added it to /sbin as you mentioned. I had already pulled apart the initramfs from the stock kernel for some hints. I also added the relevant entries to init.recovery.qcom.rc. I didn't, however, add a link to predecrypt.sh. I'll look into that now.
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
Sounds like we tried alot of the same things.

Im going to try and implement some things from pixel 3 source there is alot there that can be added with little editing.
[OnePlus 6T  Guides, News, & Discussion] xls654:
i compiled twrp on omni full 9.0 and twrp 9.0 branch,

do some dirty modify, and decrypt success,

oneplus 6t need keymaster 4.0 to decrypt
[OnePlus 6T  Guides, News, & Discussion] mauronofrio:
Explain the modify you made
[OnePlus 6T  Guides, News, & Discussion] xls654:
I clone your 9.0 fajita branch

to boot & decrypt normal, add this lines in system.prop

ro.product.board=sdm845

ro.board.platform=sdm845

ro.build.version.release=9

ro.build.version.security_patch=2018-11-01

I will upload & share twrp image and installer soon, thanks for you share.
[OnePlus 6T  Guides, News, & Discussion] mauronofrio:
I'm building a new twrp just now, when you made the changes please make a pull request in my repo
[OnePlus 6T  Guides, News, & Discussion] mingo_mgx:
dude thank you so so much for getting decryption working much love <33333333333333
[OnePlus 6T  Guides, News, & Discussion] mauronofrio:
There is a little problem now, setting a security_patch can be a problem for future updates, i think you should use always the securiy_patch_origin
[OnePlus 6T  Guides, News, & Discussion] mauronofrio:
Acutally all the twrps i made with your source are unable to boots, have you made some modifications to the omni 9 source before compiling?

I saw your twrp and your source and seems your source is not complete, you leave some files that in your twrp are not, i make a commit to remove them:

https://github.com/mauronofrio/andr...mmit/bdd0d9fcd2cdc380fdf72ad7cdd01de51819132c

But it still unable to decrypt, i'm using omni-9.0 and my source with that 3 files removed ( I also tried with yours).

Seems your init and some libs are different, so can you explain me which source are you using? Maybe you have imported some commits from gerrit? Or you made these changes?
[OnePlus 6T  Guides, News, & Discussion] Nsane457:
Maybe this means using

repo init -u git://github.com/omnirom/android.git -b android-9.0

instead of

repo init -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-8.1

and replacing aosp's bootable/recovery with https://github.com/omnirom/android_bootable_recovery (android-9.0 branch).

I built this before but it never booted right for me. Had to hack in a 8.1 branch busybox with all sorts of workarounds to compile. So all xls654's busybox inclusions to recovery/root/sbin would probably make sense as a workaround, I'm guessing.
[OnePlus 6T  Guides, News, & Discussion] mauronofrio:
No, there is something more, maybe i found it, can you test a twrp?
[OnePlus 6T  Guides, News, & Discussion] Nsane457:
Sure, I guess.
[OnePlus 6T  Guides, News, & Discussion] mauronofrio:
can you contact me on telegram? always mauronofrio
[OnePlus 6T  Guides, News, & Discussion] xls654:
hack omni 9.0 hardware keymaster source code, fix some recovery bug, upload the patch later
[OnePlus 6T  Guides, News, & Discussion] mauronofrio:
ok thanks, i losed a day to understand how you compile it
[OnePlus 6T  Guides, News, & Discussion] xls654:
some patches for twrp fajita build, the patch 0001-init-Add-install_keyring-command.patch not sure, other two patches is need.

View attachment twrp_fajita_patches.tar
[OnePlus 6T  Guides, News, & Discussion] Dameon87:
I still can't get a bootable recovery with the patches, and changes. Something has gotta be missing from the way this was done. Can you please verify what manifest branch you used?

On omni 9.0 full sync, I can't get the recovery to even boot.
[OnePlus 6T  Guides, News, & Discussion] xls654:
use this command repo init

repo init -u --depth=1 git://github.com/omnirom/android.git -b android-9.0

this is my manifest.xml real file

View attachment default.xml
[OnePlus 6T  Guides, News, & Discussion] Nsane457:
I was able to build it and it works. It's hackish, but maybe someone more experienced could refine it.

Run git-repo init --depth=1 -u https://github.com/omnirom/android.git -b android-9.0 to get the full omnirom.

Edit .repo/manifest.xml and add <project path="device/oneplus/fajita" name="xuelisong/twrp-fajita" remote="github" revision="android-9.0" />.

Edit .repo/manifests/remove.xml and add <remove-project name="platform/bootable/recovery" />.

Edit .repo/manifests/omni-default.xml and, below all the lines starting with <include , add the lines <project path="bootable/recovery" name="android_bootable_recovery" remote="omnirom" revision="android-9.0" /> and <project path="external/busybox" name="android_external_busybox" remote="omnirom" revision="android-8.1" />.

Run repo sync.

Edit build/tools/buildinfo.sh and build/core/version_defaults.mk as per the usual way.

Fdit build/soong/cc/config/clang.go, search for "-Wno-enum-compare-switch", and just below it append "-Wno-error",(with the comma and quotes).

Edit external/busybox/Android.mk, search for BUSYBOX_WARNING_HIDE :=, and remove everything after the := and add -Wno-error. The variable should look like BUSYBOX_WARNING_HIDE := -Wno-error.

These two edits are just to get busybox to build which likely isn't even used since the binaries are included in xuelisong's recovery/root/sbin but the build fails otherwise.

Apply the patch View attachment op6t-crypt.patch (combination of the 3 previous patches).

Build with

. build/envsetup.sh

ALLOW_MISSING_DEPENDENCIES=true LC_ALL=C lunch omni_fajita-eng

ALLOW_MISSING_DEPENDENCIES=true LC_ALL=C mka recoveryimage

You might run into a snag complaining about 2 different versions of JAVAC compiler. If so, open out/soong/make_vars-omni_fajita.mk and edit the line starting with SOONG_JAVAC := to reflect the original javac compiler, and redo ALLOW_MISSING_DEPENDENCIES=true LC_ALL=C mka recoveryimage.
[OnePlus 6T  Guides, News, & Discussion] Dameon87:
Thanks mate. I was on that path and had to replace the android_bootable_recovery. For whatever reason the current Omni tree imports the one directly from AOSP. After that, and adding busybox I just needed to iron out the busybox fails.
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
Add

TW_USE_TOOLBOX

to boardconfig for busybox error u don't even need any of it.

https://www.androidfilehost.com/?fid=11410963190603859172

Also on 9.0 omni tree I only use export ALLOW_MISSING_DEPENDENCIES=true
[OnePlus 6T  Guides, News, & Discussion] Nsane457:
Decryption fais when built with TW_USE_TOOLBOX := true for some reason.
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
Works for me I'm building on 9.0. Linuxmint 19 openjdk8. Patched files and I use mka bootimage now instead of make recoveryimage. I have f2fs for userdata I've made more changes since last night. Pm me I'll send u a link to source.
[OnePlus 6T  Guides, News, & Discussion] AnoopKumar:
f2fs ?

edit: why f2fs ?

---------- Post added at 08:59 PM ---------- Previous post was at 08:56 PM ----------

Guys, what's the current status ? pie ? booting ? decryption working ? backup & restore ? wipe ? adb & mtp ?
[OnePlus 6T  Guides, News, & Discussion] twinnfamous:
I'm playing with the source trying to see what breaks it so I don't break it on accident