yashsingh1/xdaforums huggingface dataset:
[Realme 8i / Narzo 50] Zxalilh:
(I assume you already have the needed drivers and programs to root your device)

1. Find the boot image from the zip of the custom ROM and move it to your device.

2. Install Magisk.

3. Patch the boot image you moved to the device, you can patch it following this.

4. Move the patched boot image to your device.

5. Run "adb reboot bootloader".

6 - 1. Run "fastboot boot patchedboot.img".

• After if boots (automatically), go to Magisk and let it actually patch the boot image. Doing this can prevent you from potentially bricking and making your device unusable.

6 - 2. Or you can run "fastboot flash boot patchedboot.img" which will instantly root the device.

(This has a small chance of failing if you do something wrong.)

• Your device is now rooted :) •

(I found out that this might not work due to fastboot being inaccessible. Please refer to this guide.)
[Realme 8i / Narzo 50] Ripped_1:
Thnx for your help,

I rooted my phone

👍🏻
[Realme 8i / Narzo 50] Madhav Bihani:
Please tell me how did you install custom rom without root and twrp???????
[Honor Magic6] schmidt93:
Hello all.

Coming from a Xiaomi 12 to Honor Magic6 Pro, and to my disappointment I find out I cannot do selfie videos with bokeh effect on. I can only film with bokeh on the rear camera in the Movies camera mode, AND ONLY ÎN 24 FPS.

Do you know a workaround, a 3rd party app that can film front camera, at least 30 fps, WITH BOKEH?
[Touch Diamond, MDA Compact IV Themes and Apps] jmermel:
Compatible Maps for TomTom v815​
[Xiaomi 13] antwoine.westlee:
The Xiaomi 13 actually uses the A/B system partition scheme specified by Google

Custom ROMs are apparently only flashed on A for whatever reason.

Does it make any sense to flash the custom ROM on A and B or can you use 2 separate systems here?

If I let Magisk update the bootloader through the app, it boots to A once and then flashes to B the next time, even though there shouldn't be anything there to begin with.

Currently I boot A, then flash A via TWRP and also manually install Magisk on A. Does it make any sense to do the same for B?

I am familiar with the principle of A and B for the OTA updates.

However, I do not know whether this also gives me an additional advantage (emergency backup in case of a broken ROM, for example). What is the best way to proceed here?

I switched directly from an Android 9 device to 14. I don't have any practical experience and when I search the web, the masses here seem to be even more clueless. In another forum that deals with custom roms for Xiaomi 13, not even anyone knew anything about this B partition.
[Xiaomi 13] antwoine.westlee:
A/B (seamless) system updates | Android Open Source Project

source.android.com

So many ROM developers and would-be experts and nobody has an answer to such a basic question.

It's not as if this is something new. Google has made the A/B layout mandatory since Android 11 and it was already used occasionally before that.

So now we have great custom ROMs on the devices that don't make use of the extra partition, apparently no developer has a plan how to use them manually in a meaningful way.

If nobody seems to want to use the thing here, the partition could also be dissolved and repartitioned and the unused X GB given to the user.
[Xiaomi 13] flauros82:
I don't think I'm the best person to tell you but right now I have AOSP Uvite Extended and it was only set to B and I have no problems, when I connect the USB cable to the PC everything that should be in a single partition is free, I think directly When doing FORMAT data after flashing, it leaves the smallest free partition and takes advantage of it for the other one.
[OnePlus 12] omar302:
Since the last update (802) on the NA OnePlus 12 the setting for allow notification snoozing is missing from the notification settings.

Is this common for all? Any workaround to get it back?

Thanks.

Below is a screenshot of how it used to be:

View attachment 6114977
[Realme 7 Pro Questions & Answers] rafnov:
How you deal with automatic brightness setting always going to low when not in the full light?
[Xperia Z5 Premium Q&A, Help & Troubleshooting] James.Xperia:
Hello everyone,

Is here someone who has the access to Xperia blog? (The site doesn’t allow new registrations.)

I need from the site download these two firmwares:

1.

Xperia Z5 Premium_E6853_32.1.A.1.185_Central Europe 1_Generic

<Mod Edit> Off-site download link removed

2.

Xperia Z5 Premium_E6853_32.0.A.6.200_Italy_Generic

<Mod Edit> Off-site download link removed

Or if someone has the CE 1 this firmware:

Premium_E6853_32.0.A.6.200

or

Premium_E6853_32.0.A.6.170

Thank you very much
[Xperia Z5 Premium Q&A, Help & Troubleshooting] khusika:
Greetings @James.Xperia

For your information, I have removed the download link from your post above. This is because the link you embedded cannot be accessed by the public and forces users to request access first. As per XDA rule No. 11, providing off-site download links is prohibited.

If the firmware you are looking for cannot be found on that site, I suggest you look for other references.

Regards,

Khusika - Forum Moderator.
[Windows RT General] save_jeff:
Im looking into installing PostmarketOS on my Surface RT.

the first step is to jailbreak via this but Im getting "Not Authorized" and can't download the zip file.

i found this but it says there is a jailbreak killing update after Okt. 2016.

Is it still possible to disable secure boot on a completely updated surface RT?

Would love to have linux running on my old Surface RT after all this years
[Windows RT General] jwa4:
The new link you found replaces the dead one. You will still be able to jailbreak after a few extra steps, see the jailbreak killing updates section of the guide here.
[Upgrading, Modifying and Unlocking] james341:
good day to you

i searched for info about how to do sim unlock to mio a701 and i can't find nothing

can anybody help in this issue ?

thanks in advanced
[Redmi K20 / Xiaomi Mi 9T Guides, News, & Discussio] Angel Tech:
Lineage 17.1 with that idiot known from my tiktoks

the rom is the same as LIneageOS 17.1 but it has Adam as default wallpaper

and yes, it's Android 10 rom because i can't find Unpack and Repack tool for newer Android versions:(

this was made for fun if something;P

hope you enjoy it

link to the rom:

adamos_xiaomi_davinci_K20_MI9T_test_build_1.7.4_davinci_84_10

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com
[Redmi K20 / Xiaomi Mi 9T Guides, News, & Discussio] alecxs:
Hello Angel Tech,

welcome to XDA developers. I have closed your thread and moved into the General Forum because it didn't qualify for the ROMs, Kernels, Recoveries, & Other Development Sub-Forum.

Please refrain from posting other work without permission or credits in future.

XDA-Developers FORUM RULES #12

Furthermore, you haven't mentioned the kernel source link in your first post. GPL compliance mandates it to be present. Prior to your next posting, kindly read the developer notes.

XDA-Developers and the GPL

Regards,

alecxs

XDA moderator
[General Questions and Answers] FSimsek:
I own to devices the first one is: carlinkit t-box ambient with android 13 and the second one is; a Chinese unbranded car dvr display with 4 channel camera support (see attached pictures). Car dvd display has bluetooth that functions only for sound transfering and an usb-a port that supports only wired mirror link screen share with android devices. My questions are;

1) any solutions to modify or change the firmware or root the device to add more features like android auto or carplay support or other customizable features.

2) I had given an advice as in ''Will Post any Stock ROM Files That are Requested'' thread ( https://xdaforums.com/t/will-post-any-stock-rom-files-that-are-requested.4670670/post-89567443 ) to add a wireless carplay/android auto module to hardware on audio port. This is very technical advice so is there anyone can help me to simplify the instructions if this ithe only solution for my problem

.View attachment 6114984View attachment 6114985View attachment 6114986View attachment 6114987View attachment 6114988View attachment 6114989View attachment 6114990View attachment 6114991View attachment 6114992View attachment 6114994View attachment 6114995View attachment 6114996
[Fire TV Q&A, Help & Troubleshooting] ptstr:
Hello,

I have Fire TV Stick (3rd Gen) Fire OS 7.6.7.1 (PS7671/4097).

I noticed that free space went from 1.4GB to 400MB and saw that’s because there was a pending update under my Fire TV which offers the option to “Install Update”.

When I click on it, it then shows “Installing update... The system will reboot and the update will finish in few minutes.”

But it’s been already more than few minutes and it still stuck. I tried to restart the fire tv and try again but same issue. After few minutes it stops and offers the option to “Install Update” again.

Any idea how to resolve or get rid of the update/restore the storage?

I tried to run this command through ADB:

pm clear com.amazon.device.software.ota

But it says it’s a protected package now.

Neither it seems like I can run TDUK Update Wiper or Cm2019 as it seem to depend on local adb which is blocked in my current version.

Thanks.
[Fire TV Q&A, Help & Troubleshooting] IsHacker:
I have the same issue with my firestick 2nd gen (tank). It says it has an update available but when I click install it updates and reboots normally but when I go to updates again it says the update is still available and hasn't been installed. Any solutions for this, anyone?
[Fire TV Q&A, Help & Troubleshooting] ptstr:
Looks like it disappeared by itself, it didn’t actually update and the storage is restored, so all good, I already disabled updates so it doesn’t happen again.
[Sony Xperia 5 V] qubbnpete:
Hey there,

On the simtray / SD tray, there's a mention for SIM1, and in the back SD, but shouldnt the device also provide for SIM2, as in Dual sim?..

From what I read, it should fit insgead of the SD card, but a SIM doesnt fit there.... It's almost a mm too long.

Anyone have this issue?
[Sony Xperia 5 V] SXUsr:
The second sim is an eSIM, not a physical one.
[Sony Xperia 5 V] qubbnpete:
There are actually 2 models of this phone, I recently learnt => https://www.phonemore.com/compare/phones/sony-xperia-5-v-xq-de72-vs-sony-xperia-5-v-xq-de54/24006000

I had no idea when i bought it, that the only one abe to use a second physical sim had to buy it in east asia.
[Google Pixel 6a] monkbinho06:
My Pixel 6a is stuck in a bootloop, where it reaches the Google logo on a white background before rebooting, following a failed automatic OTA update. I've attempted to resolve this using Google's repair tool, ADB sideloading of factory and OTA ZIP files, but without success. Additionally, I've tried flashing the update via fastboot, but the locked bootloader limits my options. Any assistance would be greatly appreciated.
[Google Pixel 6a] V0latyle:
What happens when you try to sideload the OTA? The factory update cannot be sideloaded, ONLY the OTA.
[Google Pixel 6a] monkbinho06:
When I try sideloading the OTA image, the Command line dies off at 47 % and when I look at the phone logs, I get the message in the photo below. View attachment 6115061
[Google Pixel 6a] V0latyle:
Signature verification failed, the file you're trying to send to the device is the wrong file. Please share the name of that file.

The OTA zips for Pixel 6a "bluejay" are here:

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Here is the link for the June 2024 update:

https://dl.google.com/dl/android/aosp/bluejay-ota-ap2a.240605.024-f8a734a3.zip

Here's a tip when doing things from command line: after you type adb sideload and leave a space after "sideload", simply drag and drop the OTA file into the command window, which will automatically populate the path.

You also may want to consider using Pixel Flasher.
[Google Pixel 6a] monkbinho06:
Here is the file name bluejay-ota-ap1a.240405.002-6114363c.zip

I have tried using pixelflasher,but I am still not able to get past the signature verification step.

When I try to open the zip file by double clicking it, I get this weird error shown on the screenshot below. Might this indicate that theView attachment 6115077 OTA i am trying to sideload is corrupted?
[Google Pixel 6a] V0latyle:
You shouldn't be unzipping the OTA, just flash it as is.

The OTA downloads page lists the SHA-256 checksum for each file so that you can verify integrity. For the June update, the checksum is f8a734a35362604436aa42106343acf1c6441cb6ca60d85cf351f0ad79ddacd9

Reboot to recovery, select Install update from ADB. Command in ADB is adb sideload <path to file> but I don't use Mac so I have no idea how that works. I would assume you can simply place the OTA zip in the Platform Tools folder and type the filename:

adb sideload bluejay-ota-ap2a.240605.024-f8a734a3.zip
[Google Pixel 6a] monkbinho06:
I verified the June checksum, and it matches what's listed on the Google site. However, I still encounter the same whole-file verification error when attempting to sideload it.

Here are the details of my ADB installation.

Android Debug Bridge version 1.0.41
Version 35.0.1-11580240
Installed as /usr/local/bin/adb
Running on Darwin 23.5.0 (x86_64)
[Google Pixel 6a] V0latyle:
Odd. You're using ADB Platform Tools straight from Google, right? You aren't using a custom or minimal ADB toolbox? 35.0.1 is up to date so it doesn't seem like it but I just want to make sure.

So far it seems like you're doing everything right.

Since this started with a failed OTA, I'm concerned that something got corrupted somewhere to the point where it can't verify genuine update images. If your phone is still in warranty I'd recommend you seek RMA.
[Samsung Galaxy Nexus] Andrewmsi:
Hi

I recently found my old galaxy nexus but when I Power it on it just bootloops 2 times and then stucks in the "X" logo for infinite time I tried flashing it with fastboot but when I unlocked the bootloader it would look itself back I tried to wipe the data but it wouldn't do anything and when I deleted the partition cathe it would go to the google logo and then to recovery mode I have available download mode/odin mode, recovery mode and bootloader.

I appreciate any help
[Samsung Galaxy Nexus] parrots_:
Did you flash it in Odin too? Try that, it should fix it.

Firmware shouldn't be too hard to find, just search up the model number and put firmware.
[Samsung Galaxy Nexus] iceepyon:
If you can't reinstall the OS onto your device. Then the internal storage has probably failed. You will need to replace the motherboard
[Samsung Galaxy Nexus] Andrewmsi:
The eMMC is probably fried I tried flashing it with odin and it just bootloop I might try another rom because it completed it. If I fix it I will update
[Samsung Galaxy Nexus] parrots_:
When you wipe in recovery, does it have any other messages that aren't apart of the data wipe? Could show issues in the eMMC.
[Samsung Galaxy Nexus] Andrewmsi:
No it just completes it normallyView attachment 6116170
[Galaxy Tab 3 7.0 Android Development] soyeonswife63:
Status: ❌ Not booting

Download Link: Google Drive

Installation

Flash the custom TWRP image provided in the Google Drive link.

Boot into TWRP, and wipe 3 partitions: System, Data and Cache. (THIS WILL DELETE ALL DATA AND THE OPERATING SYSTEM! BEWARE)

Flash the ZIP file for the latest CM12 image.

If you can't boot into the OS, wait a bit on the boot logo, then force reboot into TWRP, and run adb shell cat /proc/last_kmsg > kernel_logs.txt on your PC after connecting to USB. Then upload the file here.

We're currently looking for testers, as lack of testers slows down development a lot. You can also join the Discord server.

Thanks to @adryyy's works, we were able to get a CyanogenMod build. However, it doesn't boot just yet.

I think this is caused by a bug in the implementation of the memset function in ARM, see the issue here

CyanogenMod's build system builds with GCC 4.8 so this bug's existence is expected

Building with GCC 4.7 seems to result in an unbootable kernel, as last_kmsg is no longer available after that.

Applying the commits 455bd4c and 418df63 to fix the issue makes the kernel presumably unbootable as well

A last_kmsg of the kernel without the memset patches has been attached, for those who want to help and have expertise in the area.

Device trees etc. is at samsung-goya on GitHub

Kernel source: android_kernel_samsung_goya
[Galaxy Tab 3 7.0 Android Development] soyeonswife63:
Reserved
[Galaxy Tab 3 7.0 Android Development] yogibaaeer:
I can contribute with testing, if you provide some instructions.
[Galaxy Tab 3 7.0 Android Development] JerryMaguire01:
me too!!
[Galaxy Tab 3 7.0 Android Development] soyeonswife63:
Instructions for flashing & getting logs updated, thank you everyone for the interest :)
[Galaxy Tab 3 7.0 Android Development] 16klaudi20:
Booting not working repair please
[Galaxy Tab 3 7.0 Android Development] notnoelchannel:
We are looking for testers! Are you willing to be one? :)
[Google Pixel 7] mschflbn:
Hey there,

I've had a lot of connectivity issues with my P7 and I was curious if there is a way to flash only the modem firmware from the, say, February 24 release which seemed to have everyone pretty content with the connectivity. Is this able to be done or am I stuck with waiting for a monthly update to fix the error. Thank you!
[Google Pixel 7] Lughnasadh:
Yes. Put the radio image in your Platform Tools folder, open up Command Prompt from that folder, go into fastboot mode (adb reboot bootloader) and enter the following command:

fastboot flash radio radio.img
[Google Pixel 7] mschflbn:
Awesome! That's what I was hoping for. Do you know how to extract the radio image file from the OTA zip? I'm assuming it can be done within platform tools?
[Google Pixel 7] Lughnasadh:
Extract it from the factory image. Download the factory image, extract the contents, then extract the inner zip and it will be in there.
[Google Pixel 7] mschflbn:
Thanks! Do I need to root to install this or will it work fine just like side loading an OTA zip. Sorry - my mind is slipping. I haven't done any of this since my Nexus days. 😀
[Google Pixel 7] Lughnasadh:
No you don't need root. Just flash the radio image in fastboot. I'm assuming your bootloader is unlocked so you can flash images.
[Google Pixel 7] mschflbn:
Yup - unlocked bootloader! So I unzipped the OTA zip file, but inside I can't an inner zip. I'm finding payload.bin inside which is the largest of the files. Is it inside the payload file and I need to unpack that?
[Google Pixel 7] Lughnasadh:
No, not the OTA file. The factory image. It's easier.
[Google Pixel 7] mschflbn:
Aha! That makes more sense. Thank you!
[Google Pixel 7] mschflbn:
I'm guessing it is the file "radio-panther-g5300q-230927-231106-b-11056121" img file is likely the correct one?
[Google Pixel 7] abhinavp649:
Yep, thats the file you are looking for. You can simply rename it to just "radio.img" for simplicity during fastboot. Good luck!

Edit: Make sure to have a backup of the existing radio image of your phone in case something goes wrong with the connectivity. better safe than sorry :)
[Google Pixel 7] mschflbn:
Awesome. Thank you again for the help!
[Google Pixel 7] swangjang:
You can also drag and drop the file into the cmd window instead of renaming.

E.g.

fastboot flash radio *drag and drop the radio.img into the cmd window*
[Google Pixel 7] 41rw4lk:
I'll throw out a warning when flashing modems and bootloaders. Since you're flashing an older modem this won't matter much, but something to keep in mind. Modems and bootloaders typically have a revision number, say rev 3 for example. You can typically flash within the same revision or higher, but rolling back you typically can't. Why does this matter? Say you flash a modem that is rev 4 and it doesn't work as intended, well you can't roll back to rev 3 now, you would have to wait for an update and hope that fixes your issue. The revision number doesn't change with every update either, but when it does, usually you can't roll back.

I've seen users end up with unusable phones for months, waiting for a update to come along. Even worse, an update never came.
[Touch Diamond, MDA Compact IV Themes and Apps] jmermel:
Compatible Maps versions for TomTom v815

​

Compiled by demonfatal
[Touch Diamond, MDA Compact IV Themes and Apps] KRiZ-R:
Now what is the difference between the maps?
[Touch Diamond, MDA Compact IV Themes and Apps] jmermel:
OK

Some of the maps have lane and voice guidance. These, at this time, can not run on a PDA

Some have more detail that others. [for instance, there are v815 maps of North America and USA and Canada that range from 878MB to 1600MB]

Hope this clarifies this:)
[Touch Diamond, MDA Compact IV Themes and Apps] KRiZ-R:
Ok, thanx :)

Do you have a list of which one has the most details?
[Google Pixel 7 Pro] accnetdev:
Hi, as usual I used the factory image, patched init_boot using Magisk 27, started my Pixel 7 Pro in fastboot mode and this is what happened :​

Répertoire de c:\_\android\platform-tools_r34.0.5_win

19/06/2024 14:57 <DIR> .

18/10/2023 16:54 <DIR> ..

04/10/2023 18:21 5 920 544 adb.exe

04/10/2023 18:21 108 320 AdbWinApi.dll

04/10/2023 18:21 73 504 AdbWinUsbApi.dll

04/10/2023 18:21 439 584 etc1tool.exe

04/10/2023 18:21 1 845 024 fastboot.exe

04/10/2023 18:21 54 560 hprof-conv.exe

04/10/2023 18:21 242 128 libwinpthread-1.dll

17/06/2024 16:18 8 388 608 magisk_patched-27000_v003V.img

04/10/2023 18:21 476 960 make_f2fs.exe

04/10/2023 18:21 476 960 make_f2fs_casefold.exe

04/10/2023 18:21 1 157 mke2fs.conf

04/10/2023 18:21 756 000 mke2fs.exe

04/10/2023 18:21 1 063 139 NOTICE.txt

04/10/2023 18:21 38 source.properties

04/10/2023 18:21 1 373 984 sqlite3.exe

15 fichier(s) 21 220 510 octets

2 Rép(s) 439 910 068 224 octets libres

c:\_\android\platform-tools_r34.0.5_win>fastboot flash init_boot magisk_patched-27000_v003V.img

Sending 'init_boot_a' (8192 KB) FAILED (Write to device failed in SendBuffer() (Too many links))

fastboot: error: Command failed

c:\_\android\platform-tools_r34.0.5_win>fastboot flash init_boot_a magisk_patched-27000_v003V.img

Warning: skip copying init_boot_a image avb footer (init_boot_a partition size: 0, init_boot_a image size: 8388608).

Sending 'init_boot_a' (8192 KB) FAILED (Write to device failed (no link))

fastboot: error: Command failed

c:\_\android\platform-tools_r34.0.5_win>fastboot flash init_boot_b magisk_patched-27000_v003V.img

Warning: skip copying init_boot_b image avb footer (init_boot_b partition size: 0, init_boot_b image size: 8388608).

Sending 'init_boot_b' (8192 KB) FAILED (Write to device failed (no link))

fastboot: error: Command failed

​

I am looking for some help to root my Pixel 7 Pro, any idea?​

Image used : cheetah-ap2a.240605.024-factory-c6156301.zip​
[Google Pixel 7 Pro] gamer765:
If you copied the errors you're getting and pasted it into Google, the top search result will lead you here: https://android.stackexchange.com/q...e-failed-no-link-unknown-error-too-many-links

Have you given that a try?
[Google Pixel 7 Pro] accnetdev:
Thanks for the link(s).

I am going to look for an old PC or USB2.0 hub and go back here to let everyone know.
[Google Pixel 7 Pro] BunnyPig1:
I highly recommend you take a look at PixelFlasher.

It's an incredible tool. It will probably tell you if it's something with fastboot, your device or the image you're trying to flash. It can also help you grab the latest Magisk and patch init_boot for you automatically.

Check out the FAQ as well, might find some information there.

Here are some other threads that might help you out.

Thread 1

Thread 2
[Google Pixel 7 Pro] accnetdev:
@BunnyPig1 OK thanks.

One time I tried to install it, but was afraid to use it, I gave up. It must be mastered/understood and it was not to me.

For this time, I have chosen to test the registry entries, if it does not work I will get another old PC or hub USB2.0.

If nothing works I will test the tool you mention, but I am not confident to my use of it.