yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Note 8 Questions and Answers] nsfxpython:
Wrong device forum.
[Samsung Galaxy Note 8 Questions and Answers] Timmmmaaahh!:
Moved.

Welcome, @Dandisou! Make sure to post in the correct section to get better support :)

Your Note 8 isn't Sprint or Verizon or anything, is it? In that case I'll have to move it once more.
[Samsung Galaxy Note 8 Questions and Answers] Dandisou:
Never mind i fixed it (for those who are interested: hold volum up+bixby+power, then wait until android settings pop up, then factory reset)
[General Questions and Answers] HippoMan:
With Android 11, Google seems to have taken yet another step in the "making Android increasingly painful to use" direction by disabling the ability for device-only contacts to be available via the standard Contacts Provider. Because of this, I have to use Google-stored contacts on my Android 11 device in order for these contacts to be available to my apps. Otherwise, my apps don't see any contacts.

I have a rooted Android 11 device, and I'm hoping that there is some way that I could disable the standard Contacts Provider service and that I could then install an alternate, custom Contacts Provider service which knows how to access device-only contacts, and which knows how to make these contacts available to all apps that need contacts ... and which never will try to store my contacts on any of Google's servers nor anywhere else in the cloud.

Is it possible to disable Android's standard Contacts Provider service? And does such a 3rd-party Contacts Provider service exist?

Thank you in advance for any thoughts and suggestions.
[General Questions and Answers] HippoMan:
Well, I think I found a solution to the issue that I'm trying to solve. And it doesn't require any new Contacts Provider service to be installed, after all.

First of all, I made sure that contacts syncing is turned off.

Next, I installed the "True Phone" contacts and phone manager app from the play store and made it my default phone app.

Then, I used that program to make a local backup of my contacts, which is one of its capabilities.

Following that, I froze the Contacts app, but I kept the Contacts Storage app active. I checked the permissions for the Contacts Storage app, and I see now that it has no network-related permssions. So apparently, it just looks at the local contacts database, and some other piece of software is what actually syncs Google's cloud-based contacts data with the local database. And by turning off contacts sync-ing, it seems like I have indeed disabled that process.

Then, I went from my desktop computer to http://contacts.google.com with the same login credentials that are associated with my Android device. I then permanently deleted all of the contacts there.

(I rebooted my Android device between each of these steps and also after the final step.)

Now, my SMS and phone apps still see the contacts info in my local database. And I can manage the local contacts backup and restore via that True Phone app.

There are probably other phone/contacts apps which also could be used for this. But True Phone works well enough for me.

So ... it turns out that no OS surgery is needed to mess with the contacts nor to install an alternate Contacts Provider service.
[General Questions and Answers] HippoMan:
PS: And I now have learned something. I was asking about a "Contacts Provider service", but I now realize that the standard Contacts Storage app itself seems to be the "Contacts Provider".

And because I found out that this app does not even have network permissions, it seems clear that this app simply gets contacts from the locally stored sqlite contacts database, and therefore, I don't need to replace this app with anything else.

And so all I needed to do was disable contacts sync-ing, because that is what would sync contacts between Google's cloud and the local contacts database.
[General Questions and Answers] blackhawk:
How long were you playing with it to get to this point? Fun times...

Cloud apps can be little terrors, the only one I use is Gmail. It's never been breached by malware in over 15 years. Lol, Outlook not so much so.
[General Questions and Answers] HippoMan:
It took me around a day of on-and-off playing around sessions to figure this all out ... with some input from a few other helpful souls.

I agree about cloud-based services. I don't even use gmail. I run my own email server, so I use that to manage all my email accounts. I manage my own web servers and my own DNS servers, as well.

It's more work for me to manage those things, but I don't mind, and I actually enjoy that work, most of the time.
[General Questions and Answers] blackhawk:
Not too shabby. Always a learning curve.

Which manufacturer of phone?

Contact backup on Samsung's is relatively easy using Samsung Contacts. I have superceded most of my Google apps with Samsung's.

As long as I don't update things are stable and predictable. For over 3 years now, I like that!

However my needs are a lot more basic.
[General Questions and Answers] HippoMan:
Thank you!

I'm on a Pixel 5 using crDroid-7.28 (Android 11).

There are a few apps out there for performing contacts backup. My thing is that I also wanted my Phone app to not even *try* to go to Google in the cloud to search for or save contacts.

Once I realized how to shut down contacts sync-ing, some Phone apps I tried still attempted to access the Google-cloud-based contacts. But I found at least one Phone app which doesn't do that and can work fine when restricted to local contacts only: that app is True Phone.

I'm happily using it, but now for some reason it's no longer in the Play Store, and the developer is trying to get it back into the Play Store. So, I don't upgrade it, but the current version I have still works, luckily.
[General Questions and Answers] blackhawk:
I want hard backup for everything, Gmail is the only exception due to security. No cloud anything otherwise.

Samsung contacts is based in part on Apache source code. It dates back to 2004, revised 2011.

Unfortunately without Samsung Framework I don't think it will run on another brand of phone.

However there likely are other 3rd party apps using the same source code. A long shot but maybe helpful.

What a mess. I spent some time looking for a phone dialer app. Found this, but don't know if it allows for easy contact backup.

View attachment 6004937
[General Questions and Answers] HippoMan:
I vaguely remember looking at Simple-Dialer in the past, but I don't remember my findings.

As time permits over the next day or two, I'll check it again and report back here.
[General Questions and Answers] HippoMan:
In the mean time, here is a link to the message here which references the download link for latest available True Phone app, while the developer works to get it back into the Play Store ...

https://xdaforums.com/t/app-4-0-tru...act-manager-replacement.2934816/post-88945033

This app offers the option of totally local contacts, and it offers backup and restore in *.vcs files.

I'm actually rather happy with True Phone.
[General Questions and Answers] HippoMan:
I'm sorry for the delay. I finally got to investigate Simple Dialer.

On Android 13 (both on a Nothing 2 phone running stock A13 and on a Pixel 7 Pro running crDroid 9.8), it works well, and it definitely can handle local-only contacts with no problem. Also, it works well on a Pixel 5 running crDroid A11.

Actually, it seems to be that both Simple Dialer and Simple Contacts need to be downloaded, because they work together (they are put out by the same developer).

In order to get my contacts imported, they had to come from a valid *.vcf file. I created that file by temporarily saving my contacts locally via the standard Contacts app (that app now supports local export and import of contacts).

Then, I shut down the standard Contacts app and imported the vcf-file-based contacts into Simple Contacts. That worked with no problem, and I could re-save them in another *.vcf file from Simple Contacts, as well, so it's no longer necessary to get the standard Contacts app involved any more.

There are only a small number of features in Simple Contacts/Dialer compared to a full-blown contacts/dialer app like True Phone, but for my purposes, Simple Contacts/Dialer work just fine, and now I've switched to them from True Phone.
[Realme GT Neo 2] rtkpX:
So, I went back from custom ROMs to RealmeUI, now on version 4.0, but there's apparently a 4.75GB update, when I download it, it downloads fine, however, once I try to install it, it sends me straight to TWRP recovery, since I guess it's trying to access to its own recovery to update the device, but since TWRP is installed as the recovery, it will launch that.

Two questions:

· Can I install the update from TWRP?

If not

· How to install the default recovery?
[Realme GT Neo 2] SanOne+1:
Try this https://xdaforums.com/t/soft-unbric...-realme-gt-neo-2-bitra-fastboot-mode.4399223/
[Realme GT Neo 2] rtkpX:
Only the recovery, not the entire SO, also, Android 13, RUI 4.0.
[Google Pixel 4a Questions & Answers] LucidlyAwake:
I was trying to follow this guide: https://github.com/felikcat/unlimited-hotspot

I used this kernel: https://xdaforums.com/t/kernel-03-13-2022-fsociety-tribute-for-google-pixel-4a-a11-a12-l.4258269/

My device is now stuck in a loop where it will boot to fastboot, but no matter which option I select (aside from barcode and power off) brings me back to the fastboot. I'm unable to boot into recovery mode.

My computer is unable to find my device with adb and fastboot.

Any help would be greatly appreciated

I realized I did not have the USB drivers installed for my device. After installing, fastboot on my computer is able to detect my device, but I am unsure about how to proceed from here

Okay so I followed this guide: https://xdaforums.com/t/guide-unlocking-downgrading-to-a10-twrp-root.4233275/

and was able to complete is successfully. My phone is now rooted on android 10. I have a couple questions

My phone was rooted and on android 11 prior to this incident, but it was so long ago that I don't remember how I did it. Is it possible to get back to android 11?

My second question is that I'm wondering if it's still possible to follow that previous guide, preferably without breaking my phone this time
[POCO M3 Pro / Redmi Note 10 / 10T 5G] chopwell20:
Amazing guide.

Thanks. and missing screenshot where Authbypass gives you prompt.View attachment 5877405
[POCO M3 Pro / Redmi Note 10 / 10T 5G] fl0w:
SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.

Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
yes, it is bypassable.

you just go to the mapping, and disable the checks on those partitions. it will still boot normally, afterwards, if you want (which is not necessary), you can reflash your phone via fastboot and miflash for those partitions to be flashed correctly

View attachment 5895435
[POCO M3 Pro / Redmi Note 10 / 10T 5G] fl0w:
Thanks for your reply.

Unfortunately, my phone won't boot when i exclude those images. No vibration, no black screen and no fastboot/recovery.

The another bypass method which requires using readback also doesn't work. I think it's probably because mt6833 is a newer chipset compared to the ones used in tutorials.

Any other advices please? I really don't want to pay money just to use MIUI again.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
Could you give me more details about the another bypass? I dont understand what do you mean.

If that did not work, then I suppose your bootloader is locked

Please download the engineering ROM > https://mifirm.net/model/camellian.ttt#files;

and flash it via SP Tool like you did to MIUI, then boot to fastboot and flash an EEA image > https://mifirm.net/model/camellian.ttt#eea (if i am correct, EEA images are allowed to be flashed even with locked bootloader.)

If you do get the same verified boot error, disable those partitions to flash once again

If these methods didnt work, you need to install MTK Client to unlock your bootloader and try to reflash via fastboot or SP Tool
[POCO M3 Pro / Redmi Note 10 / 10T 5G] fl0w:
My father took my phone and paid to repair it. Well, i guess thats a way to fix things...

Anyway, the other method i was talking about was the one using PGPT image and using Hex editor blah blah blah.

By the way, now my phone works but it seems NVRAM was deleted. My IMEI doesn't show up. Can i recover it without using temporary methods?
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
I dont know how to recover IMEIs since I always back my NVRAM and write it via MTK Client.

You can try this guide:

Thread '[QUICK GUIDE][HOW TO] Unbrick Camellia/Camellian and restore IMEI' https://xdaforums.com/t/quick-guide-how-to-unbrick-camellia-camellian-and-restore-imei.4502077/

Alternatively, which I am not sure, try looking up a IMEI writer program somewhere in the web for MTK
[POCO M3 Pro / Redmi Note 10 / 10T 5G] TheZian:
---------- full quote removed ----------

Bro i need help

I followed the process as is, everything went well, I marked the blue box with the checkmark, when I turned on my device it was still the same, what do you recommend I do?

sorry for my bad english, i am using a translator because i am spanish speaking
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
That is weird, are you able to boot into recovery or fastboot?

Did you get any verified boot error?

Did you use the right firmware? If so, what version (MIUI version (Indonesia/EEA/MI, etc.), Android version and Codename)? If you used the latest one (MIUI 14 Android 13) please try MIUI 13 Android 12 or lower

Try this:

Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://xdaforums.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451

Esto no debería pasar.

¿Eres capaz de reiniciar en fastboot o recovery?

¿Obtuviste algún error de arranque verificado (verified boot)?

usaste el firmware correcto? si si, cual version (version de la MIUI (Indonesia/EEA/MI...) version de la Android y codename)?
[POCO M3 Pro / Redmi Note 10 / 10T 5G] TheZian:
I use MIUI 12 global version, and can't access fastboot or recovery mode, it didn't give me any error either, and I think I use the correct firmware version.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
Try this:

Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://xdaforums.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Addendum_expired:
I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Shilze:
I get the same error, anybody know how to fix?
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Addendum_expired:
And there is a "MediaTek Preloader USB VCOM" displayed in the Windows Device Manager.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] devixe:
I did have an issue but did not really go through all these stress...I also unbricked it using Brom and my original stock ROM files
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
Please try this:

Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://xdaforums.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Shilze:
It doesn't work, I think the problem is that the boot mode is bootloader instead of bootrom.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
if your phone is displaying the 3 boot modes in the edge, then yes you are in bootloader*

you should restart to any mode, then right as it reboots you shall boot into BROM immediately and redo the same process
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Addendum_expired:
I think that when I press the volume up (+), volume down (-), and power buttons on my phone simultaneously, it doesn't seem to recognize any device. However, when I only press the volume up (+) and volume down (-) buttons, it recognizes a MTK Preloader USB VCOM port, and during the process, it seems to attempt to connect twice when "Disable Auth" is enabled. In addition, the BootMode displays as BootLoader
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Addendum_expired:
I attempted to flash a GSI onto my device, but it failed. After restoring from a backup in OrangeFox Recovery, it seems to have not worked as well and gets stuck on the logo screen for a long time. As a result, my only option left is to try re-flashing the ROM using SP Flash since this method has worked for my device in the past. However, it appears that this is not working now.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] valbaldemar:
My phone screen is always black with no backlight. According to your instructions, the phone was flashed. Flashtool completed without errors
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
You can try different mtk preloader/bootrom drivers if you try searching up in the web

Have you tried filtering the usb connection with libusb?

Could you let the phone turn off by itself and then try to reboot into BROM by pressing all the buttons down and try?

Or unless you have a different model and codename. Do you have the camellia or lilac?
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
Ah, nevermind. I see your problem.

You have a phone with MTK 6765. The Camellia has a MTK 6833 chip.

Did you use the drivers offered in this thread? If you did, please install these ones that are for your device:

https://mega.nz/file/YfgSkILT#8ST9kN0hVLaEtviUg1AhrlFnzKzGEAYy63KI6MYDlNE
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Addendum_expired:
Yes, I can shut down normally, access fastboot and recovery, and show charging when connected to a charger in a shutdown state. I can also enter all other modes except that when trying to boot into the operating system, the phone keeps getting stuck on the logo screen. I've also tried using libusb to filter USB connections, but it didn't work.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
If you can access fastboot, then no need to follow this procedure. Your phone is soft bricked, not hard bricked since your phone still boots to fastboot and recovery (a hard brick is where your phone is completely dead that cant boot to nowhere, only to BROM)

Do you know how to peform a fastboot flash? If so, you will be able to boot into system by reflashing with MiFlashPro

Edit: just remembered you have a phone with MTK 6765. Would you mind telling what phone do you have by the way? It could be completely different from this device's forum and I could be mistaken to give you the wrong procedure.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Addendum_expired:
Yes, it's not a Xiaomi phone. My device is Vivo Y3 (PD1901A) with an MT6765 processor. It's not a very popular device.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Addendum_expired:
Yes, I tried to flash GSI using fastboot flash, but then the device kept rebooting. After restoring the system backup from OrangeFox Recovery, the device is now stuck at the boot logo. I've thought about re-flashing the system.img using fastboot, but the system in this ROM is made up of multiple system.new.dat files.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] valbaldemar:
Please help me. What am I doing wrong? What firmware to choose? I tried several options. So far no results. Once, when trying to start fastboot mode, there was a multi-colored screen. Flashed V13.0.6.0.SKSMIXM. unsuccessfully
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
Would you mind sending a photo of your issue?

Anyways, try an older firmware like MIUI 12.0 Android 11, Global (MI) firmware
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
I cant really help you. I understand that the VIVO Y3 is not popular, it doesnt even have a forum, but SP Tool should have worked since its a tool for every MTK device.

Anyways, please try reflashing again, and use these drivers that are for your phone socket:

Those in the thread are for MTK 6833
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Addendum_expired:
Yes, about a year ago, my device of this model was bricked, but I was able to successfully flash the ROM back onto my device using this tool and managed to get it working again. However, now, after more than a year, it seems that this tool is not working anymore. I'm not sure if it's because the manufacturer has updated the system and patched the vulnerability.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
What can I try to help you is the following

Try the thread's MTK Auth bypasser. It works for every MTK device, but worth to take a try

Restart your computer. For the drivers to take proper effect and work correctly, maybe restarting your machine might work (just as the setup utility informed in the video). This is also mandatory for the MTK 6833 drivers

You only need to apply the libusb filter once and not every time you boot your phone into BROM, so no need to waste time on it (incase you have been doing it)

Try to find older firmware for your device and flash it, since 1 year ago you affirm they have done major changes
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Addendum_expired:
I have some good news, I finally managed to start up my device🎉 🎉 🎉
[POCO M3 Pro / Redmi Note 10 / 10T 5G] TheZian:
I tried the procedure again and in this case it gave me an error about the verified boot, do you have any solution to this problem?

Intenté otra vez el procedimiento y en este caso si me dió un error sobre el verified boot, ¿Tienes alguna solución hacia este problema?

Mod. edit: post translated. alecxs
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
yes, in the error message, there will be specific partitions that are checking the verified boot. disable the checkboxes on those partitions in the mapping:

si, en la mensaje error, habrá particiones específicas que están comprobando el verified boot. deshabilita las casillas de verificación en esas particiones en el mapeo:

Mod. edit: post translated. alecxs
[POCO M3 Pro / Redmi Note 10 / 10T 5G] TheZian:
It has not worked for me, it is still in the bootloop and without giving me access to recovery or fastboot, I really do not know if it is important but the phone bricked after trying the following tutorial:

After putting the command "fastboot reboot fastboot" it entered the bootloop and did not give me access to recovery or fastboot, I don't know if that is important but I'll tell you anyway.

No me ha funcionado, sigue en el bootloop y sin darme acceso al recovery o al fastboot, realmente no se si sea de importancia pero el teléfono se brickeo después de probar el siguiente tutorial:

Después de poner el comando "fastboot reboot fastboot" se metió al bootloop y no me dió acceso ni a recovery o fastboot, no se si sea importante eso pero te lo comento de todos modos

Mod. edit: post translated. alecxs
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
First of all, forget about GSI. We already have custom roms for camellian. I will come back to that later.

Now, it looks like you are trying to boot into dynamic fastboot (fastbootd), correct?

it mentions that you can't boot into fastboot, but could you do it

before putting fastbootd?

If you currently can't start your phone, flash through this guide.

then if you can start Fastboot, you should use Mi Flash to flash the system on your phone the MIUI.

https://mifirm.net/download/7689

I recommend you try this version of miui (12.5.6)

if you don't know how to proceed with MiFlash tell me

and going back to GSI, just use these custom ROMs of your choice:

Spoiler content hidden.

Thread '[ROM][12.1][UNOFFICIAL][xdroidOSS][STABLE] for Camellia/Camellian' https://xdaforums.com/t/rom-12-1-unofficial-xdroidoss-stable-for-camellia-camellian.4584283/

Thread '[ROM][12][Camellia/Camellian] PixelExperience [AOSP] (Unofficial)' https://xdaforums.com/t/rom-12-camellia-camellian-pixelexperience-aosp-unofficial.4572103/

Post in thread '[ROM][12.1][UNOFFICIAL][Camellia/Camellian] crDroid v8.14 [14.04.2023]' https://xdaforums.com/t/rom-12-1-unofficial-camellia-camellian-crdroid-v8-14-14-04-2023.4573661/post-88425331

Mod. edit: post translated. alecxs