yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] Tomatofudge:
I tried hal9k android 9 and got BT to connect, but hands-free is not working. I have to select WQ_BC8 from factory settings for BT and then it gives CAR-KIT device name in bluetooth. Does anyone have any knowledge about this BT module and can it work in more recent versions of android?
[MTCD Android Head Units General] Tomatofudge:
Didn't have much luck getting BT work well on Android 8 & 9 custom roms, didn't even try BT connectivity on stock roms. Don't know if it was just user error or custom roms I tried, but magically in Android 10 BT worked great, both stock and custom rom. Still need to make sure OBD connection works.

If people new to these things need help, please don't hesitate to ask a question! My idea for this thread is a collection of dumb questions so we don't litter official threads meant for other use than FAQ.
[MTCD Android Head Units General] AnthonyUK:
I have that head unit, in a MB right?

I have been using Hal9k android 8 for around 4 years and it has been very reliable including the BT.
[Xiaomi Poco X3 Pro] hirodz:
My phone When turned off, it never works no mode recovery no mode fastboot no qoualqom port in pc, But when it gets cold and I put in cable charge and press power on his boot and work, But the device is getting hotter than before, What can I do for him to me back like before, Knowing that I install custom ROM and custom recovery and root magisk and some module but i use it and it was working normally at first.

What can I do to solve the problem?
[Xiaomi Poco X3 Pro] Antonio7489:
You should flash MIUI again and see if phone heats again, if it dose its somthing releted to hardware, maybe the battery idk,you should go to an Xiaomi repair center to get it fixed.
[Xiaomi Poco X3 Pro] hirodz:
I can't go to Xiaomi repair center my phone rooted
[Xiaomi Poco X3 Pro] irmas5:
Then flash miui latest, automaticaly you loosing root. lock bootloader, and go to repair centre
[Xiaomi Poco X3 Pro] hirodz:
Ok
[General Questions and Answers] VoidRoamer:
Hello. I purchased a Nokia 5.3 over a year ago and it began registering phantom screen touches. Apps would open, options would be clicked, one finger would cause a pinch action, etc. It became so bad and frequent that the phone was unusable so I had the screen professionally replaced. The problem reoccurred shortly after the new screen was installed so they installed a second screen under warranty. All was fine after several months yet now the problem has begun to pop up again and seems to becoming more frequent.

I'm fairly careful about what apps I install, limit myself to Google Play and have ESET mobile security installed to scan new apps and periodically the rest of the phone.

Does anybody have any insight into this? I'm completely stumped.

Thanks.
[General Questions and Answers] Devgency:
Often, it is caused by the device itself. For example, the Ghost touch of the iPhone X was caused by a faulty component within the display module. However, a wrong fit in the device or the motherboard can also cause a ghost touch on your smartphone. This is often the case after a repair or a fall.
[General Questions and Answers] SOFO888:
I also had ghost touches and still have them, but found a way to get rid of them.

I cleared the cache partition in recovery mode. This helped a lot.

Moreover I noticed that the screen protectors are sometimes a mess.

I had a screen protector on my old phone for 5 years without issues. On my current phone I already have the second screen protector within 1 year.

The first screen protector had a lot of ghost touches. After dissassembling the screen protector, everything was fine again. I glued a new screen protector on the phone. Actually it was the same as the first one because the package I bought consisted of 2 screen protectors. Next time I will try another brand.

--> Do you have a screen protector?

Try the following steps:

1.Clear cache partition in recovery mode.

2.If it doesn't help and you have a screen protector take it off.
[Samsung Galaxy Tab S6 Lite Questions & Answers] andy01q:
Working with Odin. I accidentally flashed CSC to CP when CP should have been empty b/c Wifi model. Now stuck at Samsung screen when trying to start, but I can get to Download-mode. I can flash BL/CP/CSC to the correct positions, however how do I "unflash" CP? Actually I can't even reflash the correct parts anymore, Odin does get stuck at "initializing".

After Odin got stuck "initializing" for about 8 minutes I left download mode (Power Key + Volume Down) and restarted Odin and now Odin doesn't even recognize the device anymore. Patching drivers with Zadig does work (for some reason Heimdall requires me to reinstall the Drivers for "Gadget Serial" every single time I disconnect the device or leave Download mode also sometimes on Zadig 2 different Gadget Serial devices pop up when connecting in Download mode and sometimes only 1 does)

and heimdall print-pit results in:

"Initialising protocol...

Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.

Please be patient!

Session begun.

Downloading device's PIT file...

ERROR: Failed to receive PIT file size!

ERROR: Failed to download PIT file!

Ending session...

ERROR: Failed to send end session packet!

Releasing device interface..."

I have flashed Lineage Recovery (although the device is relatively quick at reinstalling the old recovery, so not 100% sure). I can not access either Recovery.
[Samsung Galaxy Tab S6 Lite Questions & Answers] andy01q:
I got a new Samsung cable. Odin recognized the device again. Then I extracted the PIT from the firmware zip and that and also added AP, CSP and CSC and NOT CP and checked "repartition" and clicked START and got:

"<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin engine v(ID:3.1401)..

<ID:0/004> File analysis..

<ID:0/004> Total Binary size: 7363 M

<ID:0/004> SetupConnection..

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)"

Which is kinda nothing, so I restartet and tried without the external PIT and without repartition and got something similar, but with "<ID:0/004> Can't open the serial(COM) port." at the end which Google says hints to driver issues, so I patched Gadget Serial with Zadig once again and then Odin log says Device removed and now refuses to recognize the device again. :(
[Samsung Galaxy Tab S6 Lite Questions & Answers] andy01q:
I tried Samsung Smart Switch and that program just tells me that my device is not supported.
[Samsung Galaxy Tab S6 Lite Questions & Answers] embryo1:
Start flashing the latest stock firmware .
[Samsung Galaxy Tab S6 Lite Questions & Answers] andy01q:
That's what I've been trying. The Log of that attempt is in #2.
[Samsung Galaxy Tab S6 Lite Questions & Answers] embryo1:
Trying this ? : Only .tar in BL option.

Update Firmware on Samsung Galaxy Tab S6 Lite (Wi-Fi)
[Samsung Galaxy Tab S6 Lite Questions & Answers] andy01q:
Thank you for that idea.

I just tried that. Odin hang on "Initializing..." for 4 minutes and then I accidentally touched the USB cable -> Disconnected. Now I can't enter Download mode (I get to the warning screen, but when I press Volume Up I only get a little bit of brightness flickering.) I tried 5 different cables, so I don't think they are at fault. I don't have a good way to tell how much battery the device has right now, so I'll charge it for a few hours and then try again. There's no good way to tell if the device is actually charging either right now. (The boot screen shows up if I connect it to the power source and that's all.)
[Samsung Galaxy Tab S6 Lite Questions & Answers] andy01q:
Okay, after letting the device charge for 3 hours I actually could get back into Download mode. This time I made sure to find a safer place before starting the Odin process. I left Odin alone for 40 minutes and when I came back the log said:

"<ID:0/003> Added!!

<ID:0/003> Odin engine v(ID:3.1401)..

<ID:0/003> File analysis..

<ID:0/003> Total Binary size: 12 M

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> There is no PIT partition.

<OSM> All threads completed. (succeed 0 / failed 1)"

Then I tried Heimdall which also failed with the following Log:

"D:\heimdall\Heimdall Suite>heimdall flash --CM cm.bin --KEYSTORAGE keystorage.bin --BOOTLOADER sboot.bin --UH uh.bin --UP_PARAM up_param.bin

Heimdall v1.4.0

([Copyright and licence stuff])

Initialising connection...

Detecting device...

libusbx: error [init_device] device '\\.\USB#VID_04B8&PID_1138&MI_01#6&37E97C82&0&0001' is no longer connected!

libusbx: error [init_device] device '\\.\USB#VID_0B05&PID_1837&MI_02#6&A74EF7C&0&0002' is no longer connected!

ERROR: Failed to access device. libusb error: -12"

Second attempt after repatching with Zadig:

"Initialising connection...

Detecting device...

libusbx: error [init_device] device '\\.\USB#VID_04B8&PID_1138&MI_01#6&37E97C82&0&0001' is no longer connected!

libusbx: error [init_device] program assertion failed: device address collision with root hub

libusbx: error [init_device] device '\\.\USB#VID_0B05&PID_1837&MI_02#6&A74EF7C&0&0002' is no longer connected!

ERROR: Failed to detect compatible download-mode device."

Okay, that's probably because conflicting with Odin. So properly disconnect the device (close all related programs, then Power+Vol Down) and -> no more entering download mode again. So I'll reconnect to power for a while and will update later.

edit:

3rd attempt with Heimdall:

"D:\heimdall\Heimdall Suite>heimdall flash --CM cm.bin --KEYSTORAGE keystorage.bin --BOOTLOADER sboot.bin --UH uh.bin --UP_PARAM up_param.bin

Heimdall v1.4.0

(...)

Initialising connection...

Detecting device...

libusbx: error [init_device] device '\\.\USB#VID_04B8&PID_1138&MI_01#6&37E97C82&0&0001' is no longer connected!

libusbx: error [init_device] device '\\.\USB#VID_0B05&PID_1837&MI_02#6&A74EF7C&0&0002' is no longer connected!

Claiming interface...

Setting up interface...

Initialising protocol..."

and I'm waiting since 5 minutes and will wait another 35 minutes, but I highly expet a fail.

Edit: An hour later the cmd-log still remains the same with Heimdall unable to Initialize a protocol.
[Samsung Galaxy Tab S6 Lite Questions & Answers] embryo1:
Download the latest firmware :

https://sfirmware.com/samsung-sm-p610/

and try a second USB port

Unpack the zip to use the recent ODIN 3.14.4 ( https://devsjournal.com/download-odin-tool-for-samsung.html )

Good luck
[General Questions and Answers] VoidRoamer:
I bought a Nokia 5.3 because of the combination of cost, features and Nokia's commitment to the Android One program. At the moment I'm lucky to get an outdated security update every few months let alone the promised OS upgrades. According to the program I believe they were supposed to give monthly security updates and two major OS updates which never happened. I'm still stuck on 11.

Given that there seems to be no action by Google or any other entity to enforce these requirements, can I assume the program is dead?
[General Questions and Answers] xXx yYy:
You should ask NOKIA this question: they joined the Android ONE program.
[General Questions and Answers] VoidRoamer:
Fair point. My experiences with corporate support have always been so bad that the part of my brain that would suggest that has shut down. That being said, the Android One page hasn't been updated in years and according to the Wikipedia page no new phones have registered with the program since 2021.
[General Questions and Answers] VoidRoamer:
So I sent a support request to Nokia and ended up receiving a response within an hour! I was pleasantly surprised at how quickly they told me to go f**k myself.

I'm pretty sure Android One is dead. IMO of course.
[General Questions and Answers] Guan Yu:
thats why custom rom is always the best
[Realme 8] Reqie:
(this is not my work, I'll leave the author below)

View attachment 5633751

Changelog:

• Initial beta build

Notes:

• Based on Android 12.1

• Only use RealmeUI 3 firmware (C.08 recommended)

• SELinux Permissive

• DT2W not working

• HDR video works

• If anything else is broken, report it.

• This is a BETA build, stability and security cannot be guaranteed, and you should expect issues!

Spoiler content hidden.

Spoiler content hidden.

Download (author is bengris32 on github)
[Realme 8] meesam3379:
based
[Realme 8] Reqie:
added to thread
[Realme 8] AE_Fahim:
looks like 4pda is more active in realme 8 development than xda
[Realme 8] Reqie:
agreed
[POCO M4 Pro 5G, Redmi Note 11S (Opal), 11T (India)] jammer3d:
Miui 12.5.5 update broke the gyroscope and has reduced performance by a bit hence I want to downgrade, please reply with a method to downgrade without unlocking bootloader or rooting. Thank you
[iPAQ rw6828, XDA Atom ROM Development] kutenkind:
I am having problems with my exec when using video programs and my tomtom mobile7. The problem is after 3 minutes into a video the display turns off and shuts off the video, if i press power button on top it resumes the video. I use the youtubeplay with downloaded video.

With tt7 it does similliar thing its in middle of guiding me and then it switches off the display and then when i press power button the tt7 is switched off.

This is very annoying as i would like to use the gps without any problems.

Any suggestions?

Using the [FINAL-23/Oct/2008] ROM FOR ATOM EXEC WM6.1 WITH HTC MANILA "TouchFLO 2D" BUILT-IN rom.

Thanks in advance :)
[iPAQ rw6828, XDA Atom ROM Development] kutenkind:
Well i loaded another rom the CE OS 5.2.20758 Build 20758.1.4.1 PV for the atom exec and now the problems are gone! :)

I guess the WM6.1 CE OS 5.2.20755(Build 20275.1.0.2) rom is buggy. Hope this helps anyone else with same issues.
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] aparnasyal:
which rom has miui dialer?
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] Eef:
MIUI.
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] Maxx9:
Xiaomi EU Rom i was using before and it comes with Miui Dialer And Message App.
[Android Q&A, Help & Troubleshooting] alino74@gmail.com:
Hey guys!

New cell OPPO A16 (CPH2269 - CPH2269EEA - MEDIATEK HELIO P35 MT6765)

A guide for the root?

But Above all ---- >>>>> is there a guide for the root, to unlock the bootloader without losing the data you have in that moment on your mobile?

Ciao raga!

Nuovo cell OPPO A16 (CPH2269 - CPH2269EEA - MEDIATEK HELIO P35 MT6765)

Una guida per il root?

Ma Soprattutto ---->>>>> esiste una guida per il root, per sbloccare il bootloader senza perdere i dati che si hanno in quel momneto sul cellulare?
[Android Q&A, Help & Troubleshooting] alino74@gmail.com:
Anyone, have any suggestions?
[Android Q&A, Help & Troubleshooting] mateo12293pl:
You need to unlock the bootloader through BROM mode. "MediaTekBootloaderUnlock.zip" for Windows. 1.Press both the volume up and down buttons. 2. Flash "boot.img" with Magisk. 3. flash "boot.img" from / fastboot flash boot.img. (not sure if there can be errors). install Magisk. and ready.

https://xdaforums.com/attachments/mediatekbootloaderunlock-zip.5621181/
[Android Q&A, Help & Troubleshooting] conducked:
where to find how to the boot.img to flash?
[Android Q&A, Help & Troubleshooting] mateo12293pl:
Where: https://oppostockrom.com/oppo-a16-cph2269

And flash it with Magisk and flash from ADB.
[Android Q&A, Help & Troubleshooting] verday:
This may be necroposting but can you me give a more detailed tutorial? I've never rooted a device before and I've been searching for a tutorial on how to root the oppo a16 but never found a detailed one in English.
[Android Q&A, Help & Troubleshooting] dornz:
Will this work with A16s ?
[Android Q&A, Help & Troubleshooting] wenyendev:
I thought that unlocking bootloader of Oppo phones was impossible.

https://xdaforums.com/t/decision-by...access-for-oppo-phones-starting-2016.3348114/

@mateo12293pl

Were you still be able to unlock the bootloader of Oppo and root it? @alino74@gmail.com
[Samsung Galaxy J5 Questions & Answers] Mihaicelmare YT:
Hello Everybody

Can someone make a bootloader flashable ZIP for my J530F?

It is very important for me, that phone is my YouTube camera

If someone can, then let me know how can I make it!
[General Questions and Answers] kraken-gz:
this is not troll, i just forgot command, but i understand where is problem, i just need help in issuing command, and also keeping TWRP after booting in system

okay, this is not usuall getting stuck in twrp after flashing it via fastboot.

i just need help how to boot , system

because way i installed it, is via fastboot:

' fastboot flash recovery twrp.img '

done good

but i mistakenly followed tutorial , and executed what they said should be okay (i mean it is okay, to boot it into recovery, but my phone manufacturer is stupid and don't include proper fastboot)

so i typed command

' fastboot boot recovery '

which it booted into recovery, and when i reboot into 'system' from twrp it boots into system. i had same issue, but i forgot command how to do this (and link to that solution also)

i just know that, last command, my phone misinterpret it , to boot recovery as boot way. instead of kernel, boot.img

------------------------------------------

because we have beautifull documentation on fastbood issued by google, i don't know how to make it boot system, i mean, boot.img

and, i want it to keep twrp installed, suprisingly, when i go power + volume up , sometimes it brings stock recovery and sometimes twrp.

for now, help me how to issue command, to boot kernel and not recovery

- and phone is: Allview Viva H801 , android 5.0

yea, some no name, that's why i'm asking for help

---------------

EDIT:

i think i managed to permamently flash TWRP, which was purpose, because now I can, use power on + volume up , and it always brings up TWRP (yay)

but now, i don't know how i can access bootloader (fastboot) , if i need to issue commands you instruct me to issue. i can use only twrp
[General Questions and Answers] Droidriven:
Connect to adb while booted into TWRP and type the command:

adb reboot bootloader

That "should" boot into fastboot

For future reference, when flashing TWRP via fastboot, immediately after you flash the TWRP.img, enter the command:

adb reboot recovery

That should boot straight into TWRP and keep TWRP. If you let the device boot into any other mode than recovery, it will revert back to stock recovery, you have to boot directly into TWRP immediately after flashing it in order to keep TWRP.
[G1 Android Development] blues:
I was on RC19 with root. And I have the certs renamed to avoid the RC30 update.

In order to download a few apps from market, I renamed the certs back, and I renamed the updater.apk.

But it still goes to download the RC30 and reboot the phone. While it is booting, I took the battery out.

Now every time I power on, it still goes to the boot screen with a progress bar showing the update progress. So I keep the phone off now.

Is there still chance for me to go back to RC19 or update to a modified RC30 with root?
[G1 Android Development] JesusFreke:
Hey blues, give me an IM. I'll be darned if I let another phone be updated to RC30 when it can still be prevented :D
[G1 Android Development] Darkrift:
First, you didnt read about renaming the certs. You could have renamed the OTA certs and left the others which would have let you use the market fine. People need to be more careful with this crap and read better. Not to be a jerk, but these are expensive phones to be messing with like this and not paying attention. I would hate to see a bunch of new G1 users bricking their devices because they tried removing a battery during an update.
[G1 Android Development] Gary13579:
(registered just to post this, LONG time lurker)

Also, root is locked off for this reason. So people DON'T **** up their phones, and HTC/T-Mobile ends up paying out the ass because of something YOU screwed up.

At the OP, try this: Take the sdcard out, put the RC28 or 29 on the card (as update.zip), then throw it back in. Even without changing the keys to test keys, or being able to rename the certs, this would allow you to update and keep root access. Then you could install the modded RC30.
[G1 Android Development] JesusFreke:
Wow. I can feel the love tonight guys :p. Take it easy, geez. lol. So he made a mistake and almost ended up with RC30 installed. That's a far cry from bricking your phone.

Heck, even I screwed up and accidentally installed RC30 on my first phone :p
[G1 Android Development] Gary13579:
No, but not reading correctly/renaming the wrong files could very very easily brick your phone. I'm not bashing him for almost upgrading, as that isn't really his fault (the updater is annoying as ****).

If T-Mobile has to replace thousands of bricked phones, do you really think Google would think twice about unlocking root?
[G1 Android Development] blues:
I am back to RC19 now.

Here is what happened:

1. While the phone is booting, I removed the battery to stop the rc30 update.

2. I put rc29 as update.zip on the sdcard, and boot the phone.

3. While the rc30 update progress bar was moving on, I press alt+L

4. I saw the rc30 update is failed. It said some file under /cache is not correct.

5. And I saw the menu. then I press alt+S. It said unable to mount the sdcard. So the sdcard update failed either.

6. then I pressed the home+return, the phone boots. then I am back to rc19!

Not sure what happened!
[G1 Android Development] JesusFreke:
I challenge you to actually brick a G1 just be deleting or renaming files.

They're more resilient than you think. Granted, it's fairly easy to make it so your phone won't boot up into normal mode. But as long as you have a viable recovery partition, you can just reflash and be good to go.

The only way to brick a phone I can think of offhand, just by simple file manipulation, would be to overwrite /system/recovery.img with some random file, and then make some other change so that it wouldn't boot in normal mode.
[G1 Android Development] Gary13579:
I'm not actually going to try it, but if the phone doesn't boot, it is essentially a brick.

How would you go about recovering a phone that won't boot? With the official keys. Would the recovery screen allow you to reflash an official update, say bricked modded RC30 to official RC30, since the build versions are the same? I'd assume no.

The only way I could see recovering a bricked phone is if the updater allowed you to install versions <= the current version. Or if there is some kind of "is everything okay" check on important files to insure that the phone would boot, and if there isn't, allow an install that's = the current build.

Even so, the phones would still be bricked and would probably require customer service/return, which would cost T-Mobile quite a bit. Even if all they have to do is reflash it, time is money.
[G1 Android Development] neoobs:
He means it won't boot into the normal screen but you could still boot into the recovery partition and wipe the phone clean.

And I believe you can install updates from the same version... I installed the RC29 update twice with no errors.