yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] umanatro:
My head unit is stuck on the Honda logo but I don't know how to fix it. I already tried all recommended types of reseting but nothing. I think it's a matter of downloading a firmware update but I don't know which one. I would look at firmware but sadly I can't even get to that menu. I tried reaching out to the company I bought it from but they said they couldn't send the update file cus it was too big so I should just return for a refund. I believe my unit is using a novada 8581 board. I haven't really seen much about this board so I'm hoping someone knows. If anyone out there could help I'd really appreciate it.

I was able to grab this system info from a video of a guy with the exact same device. I don't know if this will help but here it is:

APPVER: K4811_NWD_S217851.20220402 190135.H4EE 01D

PlatformVER:K48-2022/03/29/13:47-31-40.01_R_DSP

MCUVER:

V6.0-FF01-20211009-A02-CAN0017-17-FF-FF000000000-00

BTVER: Bluetooth_V5.0/2021-05-26

CANAPPVER: V.22.03.10A_3.0(10:58] (H.211116) emm:

0x4ec522a8

CARTYPE Current for general purpose engine type (00000)

CANBOXVER:

Screen: M_YTO_9707_6_090_01_Y011_5_20220111.bin
[Android Head-Units] kevinhm:
Me too. Dont have update.zip file to restore.
[Android Head-Units] engage4:
Try contacting uploader of the video
[iQOO 9] where_dafaq_iam:
So, I opted in for the close beta program in my iqoo 9 that vivo provides with its funtouchos and after some day I got an update which was funtouchos 13 based on Android 13 and I installed it real quick but boy it was buggy! First thing I noticed was the lagging then came the strangest thing, the lower portion of the screen was not responsive to some specific actions like the "clear all" tab in the notification shades was not responding and had to be tapped several times to trigger the func., Instagram suffered a lot for its tabs are at the bottom and it was annoying to tap 5-6 times just to get from one tab to the other.

Initially I thought my touch screen is at fault but then I figured out my dock apps were all good and the touch response was okay so I downgraded the device and now it's working fine.

But then even after downgrading I am getting the same update version: PD2136BF_EX_A_38.8.12 , i haven't even agreed to the beta program.

Now am confused whether I should update again and take the risk or shall I wait for further updates?
[iQOO 9] Ranji007:
Even I had the same issues.
[Android Q&A, Help & Troubleshooting] rregn:
I got an T510 which shows on switch on "could not do normal boot. Invalid kernel length.

i switched it into download mode,

loaded Odin v3.13 and wanted to flash T510XXU3BTK1 - because it shows

AP SWREV: B:3 K:3 S:3

first try, the flash didn't start:

extracting the PIN from the firmware and specify it in the PIT tab didn't help

later:

any hint, what can i do ? I never had this failure on flashing.

thanks and kind regards
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
Hello and good evening, @rregn

Prior to your next posting please read the guidances that are stuck on top of every forum like

[ATTN] : Read before posting - Any questions posted here will be MOVED or CLOSED

Please read the below before posting. Any questions not development related will be moved or closed. Forum Searching | Posting | The Basics: (Make sure you've read them before starting a new thread) Forum Rules Forum Search Google Forum...

xdaforums.com

and the others. I've moved your thread to Android Q&A.

Thanks for your cooperation!

Regards

Oswald Boelcke

Senior Moderator
[Android Q&A, Help & Troubleshooting] joke19:
Test this Odin version https://xdaforums.com/t/patched-odin-3-13-1.3762572/
[Android Q&A, Help & Troubleshooting] rregn:
But which one? there 6 versions of odin attached in this post .
[Xiaomi Mi 10T / 10T Pro Questions & Answers] queen15:
xiaomi mi 10t 5g suddenly shutdown not turning on
[Xiaomi Mi 10T / 10T Pro Questions & Answers] Onadimuz:
Same as mine after an update. Did you find any solution?
[Xiaomi Mi 10T / 10T Pro Questions & Answers] PhoneRepairHUB:
hey those your bootloader is already unlock if so you can ry edl flashing, try also test point , what does the pc get detected if you plug yor phone?
[Xiaomi Mi 10T / 10T Pro Questions & Answers] Onadimuz:
I did not manage to unlock the bootloader since. It's completely no response when pushing the power button and when charging, it's completely dead. And not even my PC can detect it. I'll try to send to Xiaomi shop and see what they can do.
[Xiaomi Mi 10T / 10T Pro Questions & Answers] PhoneRepairHUB:
possible for you its just a software but its a better option to bring it to service center
[Xiaomi Mi 10T / 10T Pro Questions & Answers] felixpaz1992:
I had the same problem, the only solution was "reballing CPU + Ram + UFS" in your case I would have to take it to a technical service specialized in micro-soldering
[General Questions and Answers] dkjh:
How do i set omnia blue tooth options to for example,

when someone sends me the file, i can choose to ACCEPT or REJECT?

currently, my omnia accepts all incoming file when i chose this option

settings > beam > select recieve all incoming beams.

appreciate any help! =D
[Galaxy S 4 Q&A, Help & Troubleshooting] agingmyact:
Rather than buy a Raspberry Pi, I was hoping to convert a Samsung S4 i337 (AT&T) to be a dedicated Linux/Python server.

My S4 is at OK2 via odin and kingroot, but it seems I'm stuck trying Linux Deploy (can't get it to recognize the SD card) and everything linux oriented wants to run on top of the existing system via apps, using the S4 screen, etc..

What options, if any, get me simplicity and reliability like a Raspberry Pi? I'd prefer to do everything via SSH access to the S4 with minimal need for a GUI on the phone itself. The intent is to run several Python scripts (using lots of libraries) every hour or so via cron. Even better if the system can recover itself after a reset/outage and start everything running again.

Or should I just toss the S4 and shell out $200 for a Raspberry Pi?
[LineageOS Questions & Answers] Doggie2040:
How do you uninstall user installed aps in Lineage OS?
[LineageOS Questions & Answers] Fytdyh:
check in settings >> apps
[Moto G5S Plus Questions & Answers] Princesskomz:
I am unable to locate magisk in internal storage in TWRP. Internal storage shows some size but cannot see the zip file anywhere. I also dont own a sd card so using that is out of the option. I have even tried adb sideload but it was showing as error 2. I am just 1 step away to root my phone and that is just to install magisk somehow on my phone. Any help would be greatly appreciated. Thanks
[Moto G5S Plus Questions & Answers] Fytdyh:
first, get a micro sd card. on some roms you might encounter a problem with data decryption of internal storage, thus making reading anything with twrp unusable. also you need one to make a nandroid backup to restore your phone. second, see where your browser downloaded the file. perhaps in android/data ? some of them do download there, since scoped storage
[Moto G5S Plus Questions & Answers] Princesskomz:
Thanks for the response. I thought we can root without sd card as nowadays phones come with internal storage. Anyways, I have not added customised rom its the original one that I use. The file I downloaded was in another zip folder, not in android/data as seen on pc. also in twrp I can see my storage is mounted like I can see the size number "Internal Storage (532276mb)" something like this but I am still unable to locate a single folder let alone any file in internal storage. I am so confused as how to proceed further.
[Moto G5S Plus Questions & Answers] Fytdyh:
try removing any security from your phone, like fingerprints or pin. maybe thats a reason
[Moto G5S Plus Questions & Answers] Princesskomz:
my phone is without any security. still I am unable to find any solution :(
[Moto G5S Plus Questions & Answers] Princesskomz:
do we need to install some custom rom ?
[Xiaomi Poco X3 NFC Questions & Answers] tuncerdemir:
The screen refresh rate drops when watching videos on YouTube. This creates a general feeling of slowdown on the phone. there is nothing like this in the previous version, but when you upgrade to the new version, this problem appears. you can see in the video.

My phone : POCO X3 NFC, MIUI 13, 13.0.4.0(sjgidxm)
[OnePlus 9 Pro] michael-brade:
Hi, is it possible to go back to the "old" partition scheme without the A/B slots? In other words, is the A/B slot thing part of the software (boot loader?) or is it hard-coded into the hardware? If the phone is rooted, I don't really care much for the A/B slots. And it is a waste of space IMHO.
[OnePlus 9 Pro] V0latyle:
No, it is not possible, and yes, it is hard coded.

This is the recommended layout prescribed by AOSP: Seamless system updates

This is actually superior to the "old" way in a few ways, primarily the means of updating the device. As is the case with Samsung, devices with only one "slot" and dedicated recovery must update via recovery mode, which prevents the user from using the device while updating.

The A/B system streamlines the system like this:

Let's say you're currently running Update 1 on Slot A. When Update 2 comes out, the system downloads the update package, extracts the payload, and writes the contents to Slot B, which is currently the "inactive" slot. Once the update has been completed, the system prompts a reboot, and tells the bootloader to boot into slot B. Once the system successfully boots from slot B, slot B is now marked "active", meaning the device will boot from that slot from now on, and slot A is marked inactive.

When Update 3 comes out, the process repeats again - while system is running on slot B, it downloads and installs the update to Slot A. The only interruption in user availability is the reboot.
[OnePlus 9 Pro] michael-brade:
Thanks! And yeah, I know the theory of the seamless update. I just don't need nor want it :D I have discovered the disks and partitions with sgdisk - so now I can see how they are hardcoded. Well... fair enough, I'll deal with it.
[OnePlus 9 Pro] michael-brade:
However, *idea* :) Could you use that system to install two different OSes on the phone? One on Slot A and one on Slot B?
[OnePlus 9 Pro] MrSteelX:
You are just asking for bad times. Is it possible, yes it is but slot a and b share the same data partition.
[Tilt, TyTN II, MDA Vario III Themes and Apps] bigcdatdude:
im running the regular WM 6.1

but when i try to pur some of the roms that are on here on my phone it gets stuck at the grey screen on my tilt and an error message comes up on my laptop.

somebody please help and let me know what to do so i can put some of these roms on my phone
[Tilt, TyTN II, MDA Vario III Themes and Apps] goodapollo:
well you may be using bad roms but dont expect anyone to give u the adress for better ones. Just a bit warez.

but if not im not sure.

Try to b more specific with ur question
[Tilt, TyTN II, MDA Vario III Themes and Apps] pazookie:
LOL!!!

First off wrong forum..post in rom development (http://xdaforums.com/forumdisplay.php?f=378) AND READ THE WIKI AND SEARCH BEFORE POSTING your lucky you didnt post this in that forum first or youd be flamed major

and he meant roms for the device (as in images of the operating system and software that is in a sense what you see when you boot up and how your device functions)...if your on the forum and dont know what a rom is and think it is an emulator rom you dont belong here..
[Tilt, TyTN II, MDA Vario III Themes and Apps] brynweb:
HAHAHAHAHAHAHAHAHAHAHAAAAA!

This thread is hilarious :D
[Tilt, TyTN II, MDA Vario III Themes and Apps] goodapollo:
hahaha

not sure what i was thinking

guess wen he said rom(s) i assumed emulator

I suppose that will teach me not to post while im playing halo

srry buddy
[Tilt, TyTN II, MDA Vario III Themes and Apps] kkonan:
use xp instead of sucking vista
[Tilt, TyTN II, MDA Vario III Themes and Apps] deuzeff:
You may want to stay polite and be helpful by posting :). This is a mutaul aid forum, not a flaming place ;).
[Redmi Note 9 Questions & Answers] noteugenio:
Hello! Just created an account in this forum to seek help because this is driving me nuts.

I have a Xiaomi Redmi Note 9 (Merlin) which has no system (Android), but I still can access fastboot and recovery menu, so I went ahead and unlocked the bootloader and flashed MIUI without any issue. To my surprise, when I booted the phone back up, it was like I didn't do anything as it still bootlooped, it didn't even show the MIUI logo, so I tried again; still nothing.

So, I tried the following:

- I followed the guide in this forum for hard-bricked Note 9 phones (https://xdaforums.com/t/guide-how-to-fix-a-hard-bricked-redmi-note-9-merlin-hard-brick.4347025/), and I can tell the firmware flashes because the starting menu and the fastboot logo changed from the rabbit to FASTBOOT in orange letters, but still no system.

- I flashed stock firmware, but still no system.

- I flashed the MIUI version that the phone came with through fastboot, but still no system

- I tried to flash the newest version of MIUI the phone came with through TWRP using the recovery version, but still no system (and when I try to reboot, TWRP says there is no system)

- I tried installing Pixel Experience to see if MIUI was the issue but, still no system. The phone just keeps bootlooping endlessly.

- I tried running https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt to see if the encryption was the problem, but no progress.

I would appreciate any help to at least have my phone working, even if it's not with MIUI but with a custom ROM. At this point I don't care anymore, just want a useable phone.

Thank you. :)
[Redmi Note 9 Questions & Answers] lebigmac:
Hi. Just flash the whole stock MIUI ROM of your choice and then

In TWRP you must format /data (you did first make a backup of your personal data right?)

Then phone should boot again.

I hope this helps. Good luck! (y)
[Redmi Note 9 Questions & Answers] noteugenio:
I've tried that a couple of times but it's like I didn't do anything, when I reboot I still get no system
[Redmi Note 9 Questions & Answers] noteugenio:
bump
[Redmi Note 9 Questions & Answers] noteugenio:
bump - really desperate about this matter
[Redmi Note 9 Questions & Answers] lebigmac:
I can't believe reflashing stock ROM + formatting the /data partition didn't fix your issue 😲

You are using the flash_all.sh script that comes with the stock MIUI firmware right?

well your only option it seems is to check the bootloop log and then try to find out the reason for bootloop that way. Maybe somewhere inside TWRP you can find some kind of bootloop log? Good luck! 🍀
[Redmi Note 9 Questions & Answers] noteugenio:
Yeah, I even tried with other PCs to see if that was the issue. Will try looking in the logs. Thank you! :)
[Amazfit] dsaft:
When I go out for running the GTR2 does not vibrate for 1km marks.

During the run the watch shows the always on screen (only time info) and when a new km is completed the normal run activity monitoring screen (duration + distance + pace + HR) pops up, but there is no vibration feedback.

If I move the wrist to show the activity monitoring screen right before the km mark and keep it on then the watch vibrates on the km mark and shows a big info screen with the pace of the last km.

I made a test enabling the 20 minutes on screen menu setting before I start the run to keep showing the activity screen. Then I got vibration + big pace info screen for every km until the 20min on period expired. After that, the watch turned back to only showing the run activity screen without vibration.

I was using Amazfit Pace before and there I always got vibration + summary info for every km.

This is an important feature for runners.

Does anyone know how to setup the GTR2 watch to get the vibration + pace info screen for every km during an entire run?

Thanks in advance!
[Amazfit] dsaft:
Here is an update.

I disabled the AOD (always on display) mode and went for a run and then I got the vibration alert + big pace info screen for every km mark.

It doesn't make sense to have to disable AOD every time before running to be able to get the expected km mark alert...
[Google Pixel 7 Pro] jac0b:
Has anyone found a charging switch for ACC that works with Battery Idle Mode?
[Google Pixel 7 Pro] RogerF81:
I'm just using the default one, works well.
[Google Pixel 7 Pro] jac0b:
Can you post the switch?
[Google Pixel 7 Pro] RogerF81:
View attachment 5740211

Do you mean this?
[Google Pixel 7 Pro] jac0b:
Yes thanks.
[Google Pixel 7 Pro] jac0b:
That is the switch I am using but it acts weird after reaching the pause capacity. Are you using stock kernel or a custom kernel?
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm using the same default switch on the stock (rooted) kernel.
[Google Pixel 7 Pro] jac0b:
What version of ACC do you have?
[Google Pixel 7 Pro] roirraW "edor" ehT:
v2022.6.4 of ACC.

View attachment 5740677
[Google Pixel 7 Pro] jac0b:
Thanks, that version works. I was using a newer version.
[Google Pixel 7 Pro] Tracker31:
Battery idle mode is not working for me. Any idea?
[Google Pixel 7 Pro] jac0b:
The switch worked sporadically. I started using the 4300 switch and idle has been working perfect now.
[Google Pixel 7 Pro] MArtyChubbs:
The app finally started to work consistently after installing the latest Android 13 QPR1 Beta
[Google Pixel 7 Pro] Gerr1:
What’s the benefit to using this?
[Google Pixel 7 Pro] Namelesswonder:
Restricting charging current to the battery, putting a limit on the battery voltage or capacity at where charging will be shut off, reducing or disabling charging when the battery temperature reaches a certain point, and if supported enable the ability to disconnect the battery from the charger while using the charger to power the phone. All for managing the health of the battery.
[Google Pixel 7 Pro] Gerr1:
OK, thank you for Clearing this. Dont need this, buying a new Phone every year
[Google Pixel 7 Pro] cesar_9046:
Can you send your config please?
[Google Pixel 7 Pro] jac0b:
Here is my config file. This is for version 2022.6.4 with a pause capacity of 90%

Sorry, it won't upload from my phone.

Here is a link.

config.txt

drive.google.com
[Google Pixel 7 Pro] cesar_9046:
Thanks, but the link is not open!
[Google Pixel 7 Pro] jac0b:
Should work now. I had to change the access to anyone with link can view.
[Google Pixel 6] tibl37:
I'm experimenting with a CalyxOS (13) fork, and suddenly broke booting (on a quite late stage — getting an NPE caused by my change in UserManagerService creation).

Other partitions, including boot should be fine, as I did no changes to their contents.

Device was stuck in a bootloop for ~3 reboots, then turned off and now does not react to any actions: any keys combination, holding power for about a minute or connecting a charger.

It was fully charged, and I've also tried to leave it connected to the charger for about 12 hours.

Is there some other way to enter the bootloader to flash a fixed fw?
[Google Pixel 6] ne0ns4l4m4nder:
Probably died and needs to be charged. Charge it and reflash factory firmware to both slots and wipe data using pixel flasher
[Google Pixel 6] tibl37:
That's strange, because before bootloop it was fully charged, I don't think it could fully discharge in 2-3 minutes.

And I've also already tried to charge it, it doesn't react to charger even after being connected for 12 hours.
[Google Pixel 6] Lughnasadh:
Did you have the A13 bootloader flashed to both slots? Symptoms are similar to when the new ARB bricks the Pixel 6 devices, whereby user only had the A13 bootloader on 1 slot, phone got into a bootloop, then reverted to the opposite slot which had the A12 bootloader on it, leading to a brick that so far has been unrecoverable except to RMA it.
[Google Pixel 6] tibl37:
Hmm, looks like slot b still contained the original Android 12 bootloader :(

Here is the last fastboot log:

Setting current slot to 'a' OKAY [ 0.072s]
Sending 'boot_a' (65536 KB) OKAY [ 1.749s]
Writing 'boot_a' OKAY [ 0.249s]
Sending 'dtbo_a' (16384 KB) OKAY [ 0.420s]
Writing 'dtbo_a' OKAY [ 0.063s]
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.026s]
Writing 'pvmfw_a' OKAY [ 0.007s]
Sending 'vbmeta_a' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.002s]
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.002s]
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.648s]
Writing 'vendor_boot_a' OKAY [ 0.244s]
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.024s]
Resizing 'product_a' OKAY [ 0.003s]
Resizing 'system_a' OKAY [ 0.003s]
Resizing 'system_ext_a' OKAY [ 0.002s]
Resizing 'system_b' OKAY [ 0.002s]
Resizing 'vendor_a' OKAY [ 0.002s]
Resizing 'vendor_dlkm_a' OKAY [ 0.002s]
Resizing 'vendor_b' OKAY [ 0.002s]
Invalid sparse file format at header magic
Resizing 'product_a' OKAY [ 0.005s]
Sending sparse 'product_a' 1/5 (262120 KB) OKAY [ 7.131s]
Writing 'product_a' OKAY [ 1.034s]
Sending sparse 'product_a' 2/5 (262120 KB) OKAY [ 7.232s]
Writing 'product_a' OKAY [ 1.023s]
Sending sparse 'product_a' 3/5 (262120 KB) OKAY [ 7.282s]
Writing 'product_a' OKAY [ 1.095s]
Sending sparse 'product_a' 4/5 (262128 KB) OKAY [ 7.214s]
Writing 'product_a' OKAY [ 1.017s]
Sending sparse 'product_a' 5/5 (207840 KB) OKAY [ 5.494s]
Writing 'product_a' OKAY [ 0.865s]
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.004s]
Sending sparse 'system_a' 1/4 (262112 KB) OKAY [ 7.134s]
Writing 'system_a' OKAY [ 1.031s]
Sending sparse 'system_a' 2/4 (262120 KB) OKAY [ 7.087s]
Writing 'system_a' OKAY [ 1.089s]
Sending sparse 'system_a' 3/4 (262140 KB) OKAY [ 7.302s]
Writing 'system_a' OKAY [ 1.002s]
Sending sparse 'system_a' 4/4 (104872 KB) OKAY [ 2.835s]
Writing 'system_a' OKAY [ 0.501s]
Invalid sparse file format at header magic
Resizing 'system_ext_a' OKAY [ 0.004s]
Sending sparse 'system_ext_a' 1/2 (262124 KB) OKAY [ 7.442s]
Writing 'system_ext_a' OKAY [ 1.075s]
Sending sparse 'system_ext_a' 2/2 (89968 KB) OKAY [ 2.581s]
Writing 'system_ext_a' OKAY [ 0.357s]
Resizing 'system_b' OKAY [ 0.003s]
Sending 'system_b' (340 KB) OKAY [ 0.010s]
Writing 'system_b' OKAY [ 0.038s]
Invalid sparse file format at header magic
Resizing 'vendor_a' OKAY [ 0.005s]
Sending sparse 'vendor_a' 1/2 (262116 KB) OKAY [ 7.207s]
Writing 'vendor_a' OKAY [ 1.103s]
Sending sparse 'vendor_a' 2/2 (254340 KB) OKAY [ 7.116s]
Writing 'vendor_a' OKAY [ 0.965s]
Resizing 'vendor_dlkm_a' OKAY [ 0.004s]
Sending 'vendor_dlkm_a' (39444 KB) OKAY [ 1.102s]
Writing 'vendor_dlkm_a' OKAY [ 0.196s]
Rebooting OKAY [ 0.001s]
Finished. Total time: 122.552s
[Google Pixel 6] Lughnasadh:
After initially flashing or updating to A13, whether it be a custom rom or stock firmware, did you ever flash an A13 build to the opposite (inactive) slot? Or flash the A13 bootloader to the opposite slot? Or did you ever take an OTA after updating to A13, resulting in A13 being put on the opposite slot? If not, then you likely still had the A12 bootloader on your opposite (inactive) slot.

Once updating to A13, the A13 bootloader needs to be flashed to both slots to avoid potentially bricking your device due to the new ARB. Your symptoms sound exactly the same as when users have bricked their devices because of this. They only had the A13 bootloader on one slot, got into a bootloop therefore causing the device to revert to the opposite slot which still had the A12 bootloader on it and thus bricking your device.

Android 13's anti-rollback protection has already bricked at least one Pixel 6

Some Pixel 6 users running Android 13 are stuck between a rock and a hard place with Google's anti-rollback protection.

www.androidpolice.com
[Google Pixel 6] tibl37:
I've probably upgraded to A13 OTA (not sure, because I had multiple Pixels and not sure if this one was updated OTA or by flashing with fastboot), but I'm sure that I didn't flash slot b manually.