yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A8 (2021)] Donatas155:
Tablet has 32GB of internal storage. I want to install a diagnostic program that takes up about 60GB. Android 13
[Samsung Galaxy Tab A8 (2021)] MetaP:
Root permissions can indeed enable the use of a microSD card as internal storage on Android devices, a process known as "adoptable storage." However, this feature has been removed from the user interface on some devices, including many Samsung models.

To enable adoptable storage on devices where it is not user-accessible, you would need to use ADB commands or a root-enabled file explorer that can edit system files. You should proceed with caution, as this process can lead to data loss if not done correctly, and not all apps will work well on external storage due to slower read/write speeds.

If you're considering this, make sure to back up all important data before proceeding.
[Samsung Galaxy Tab A8 (2021)] lewmur:
That would require a tablet with at least 128gb of internal storage. Why would someone write a diagnostic app that wouldn't work on over 90% of the devices on the market? Are you sure it needs 60gb of internal storage and not external SD card?
[Samsung Galaxy Tab A8 (2021)] Donatas155:
Yes,

I will describe the situation in detail: I am writing a program that takes about 300mb of internal memory. I transfer the program to the microsd card, it allows me to do this. Then the program needs to be updated, which takes about 60 GB to update (this includes diagnostics for the car). When I update, the updates are downloaded and stored in the internal memory. It takes up all the memory and does not fit. I tried to look in the program and in the android 13 system settings for options to change the location of the update to the microSD card, but I couldn't find it :( That's why I think that maybe rooting the device can solve it and I could direct the updates to the microSD card? :)

Or maybe it would be possible to connect the internal memory with a microSD card? This could be done in old android devices.

Thank you for your feedback
[Samsung Galaxy Tab A8 (2021)] lewmur:
Connecting the SD card as internal memory is a BADDD idea. The SD card is MUCH, MUCH slower that internal memory. At the very least it will cause the device to be laggy and with some apps it will even cause crashes. That is why Android no longer allows it. As to rooting allowing you to use the SD card to store the upgrade info, it might. I don't know why it won't do it without root.
[Samsung Galaxy Tab A8 (2021)] Maxim-Root:
It seems to me that such a program should be executed on a computer, so this tablet is weak for such programs. in general, mobile devices are not designed for such programs
[Samsung Galaxy Tab A8 (2021)] kevinco1:
Very true, the only Android apps that occupy this much space aren't even apps, they're games and most of it is additional data and resources
[Samsung Galaxy Tab A8 (2021)] kevinco1:
What is the name of this diagnostic app?
[Samsung Galaxy Tab A8 (2021)] Donatas155:
Name: ProDiag
[Huawei P8 Questions & Answers] liamdiazok:
Hello, I am trying to install TWRP on my P8 (GRA-L09), but when running "fastboot flash recovery twrp.img" I get this output:

liamdiazok@fbi-surveillance-van:~/Downloads$ fastboot flash recovery twrp-3.1.1-0-grace.img
Sending 'recovery' (26226 KB) OKAY [ 0.819s]
Writing 'recovery' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed

I assumed i needed root as it told me "Command not allowed"

So i ran "sudo fastboot flash recovery twrp.img"

liamdiazok@fbi-surveillance-van:~/Downloads$ sudo fastboot flash recovery twrp-3.1.1-0-grace.img
[sudo] password for liamdiazok: *i enter password*
Sending 'recovery' (26226 KB) OKAY [ 0.776s]
Writing 'recovery' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed

I said "okay so i'll try just booting twrp and not flashing it"

So I ran "sudo fastboot boot twrp-3.1.1-0-grace.img"

liamdiazok@fbi-surveillance-van:~/Downloads$ sudo fastboot boot twrp-3.1.1-0-grace.img
Sending 'boot.img' (26226 KB) OKAY [ 0.704s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed

Phone has bootloader unlocked, but OEM Unlocking is not available, the option doesn't appear in the developer options.

Why can't I flash TWRP?

Phone is running Android 5.0 w/ EMUI 3.1

Running Ubuntu 22.04 with KDE Plasma
[Huawei P8 Questions & Answers] MetaP:
If you're encountering the "Command not allowed" error when trying to flash TWRP, it's typically indicative of a few possible scenarios:

Bootloader Status

Double-check that the bootloader is indeed unlocked. Even though you mentioned it's unlocked, it's worth re-verifying. The absence of the OEM Unlocking option in developer settings is unusual if the bootloader is unlocked.

FRP Lock

Ensure that the Factory Reset Protection (FRP) is not triggering a lock. This can sometimes interfere with flashing processes.

Fastboot Version

Ensure that you are using the latest version of fastboot that is compatible with your device.

Firmware Restrictions

Some devices have firmware that prevents flashing of non-official recoveries even if the bootloader is unlocked. You might need to use a specific version of TWRP designed to circumvent this or additional unlock commands specific to your device.

Manufacturer's Tools

In some cases, you may need to use manufacturer-specific tools or methods to unlock the bootloader or flash recoveries.
[Huawei P8 Questions & Answers] liamdiazok:
Turns out phone was NOT unlocked, although it said "phone unlock" in red letters
[Google Pixel 7] Horrorfiend666:
Ditched My S20FE for the Pixel 7 I used to be on the original pixel a few years back. Anyway, to disguise root from apps such as Microsoft Authenticator? Im also looking at LineageOS
[Google Pixel 7] MetaP:
To disguise root access from apps like Microsoft Authenticator on your Pixel 7, you can use Magisk, a popular rooting tool that includes a feature called Magisk Hide. This feature allows you to hide root from specific apps. Here's a general approach:

1. Ensure your device is rooted with Magisk.

2. Open the Magisk Manager app.

3. Look for the "Magisk Hide" option in the menu.

4. In the Magisk Hide list, select the apps from which you want to hide root access, such as Microsoft Authenticator.

Regarding LineageOS, it is a custom ROM that provides a stock Android experience with additional privacy and customization features. Before flashing a custom ROM, make sure to back up your data and follow a reliable guide specific to your device model. LineageOS installation typically requires an unlocked bootloader and a custom recovery like TWRP.

Keep in mind that using Magisk Hide or other methods to disguise root access may not work with all apps, as some have advanced detection methods. Always stay updated with the latest Magisk versions for the best results in hiding root.
[Google Pixel 7] Horrorfiend666:
Thanks for the advice Im going to use the pixelflasher tool as well , Also How is support for the camera do we still need to implement a patch to get full quality ?
[Google Pixel 7] MetaP:
I'm glad you found what you were looking for and have plans for using the PixelFlasher tool :). Keep in mind that when using tools like PixelFlasher for flashing firmware or custom ROMs, camera performance and quality can sometimes be affected, especially if you're moving from the stock ROM to a custom one. For specific devices, patches or camera mods may be available to enhance camera functionality or restore it to its full capacity. It's a common practice within the custom ROM community to address such issues. For the most accurate and current information, checking dedicated forums like XDA Developers for your device model is recommended, as developers often release patches or updates to improve camera performance on custom ROMs.
[Samsung Galaxy S23] chetszot:
Hello

As S24 is virtually the same hardware as S23 in terms of camera, storage and memory, although different chipset (Exynos vs Snapdragon), I'm wondering is it possible to flash official S24 ROM to S23?

I would like to do so as S24's camera image processing is far more natural, especially in terms of goddamn crap oversharpening S23 does. I'm trying to fix this garbage S23's camera into something usable from system's camera. Although GCam provides excellent results, its user experience is far from good and I wish to have better results with the system stock camera.
[Samsung Galaxy S23] MetaP:
Flashing firmware from a different model, even if the hardware seems similar, is generally not recommended and often not possible due to differences in hardware and firmware checks by the manufacturer. While the Samsung Galaxy S23 and S24 might share similarities in camera hardware, storage, and memory, the different chipsets (Exynos vs. Snapdragon) play a crucial role in how the firmware interacts with the device's hardware. Each firmware is specifically tailored to its respective device, including drivers, power management, and other system-level optimizations that are critical for the device's functionality and stability.

Key Considerations:

Compatibility Issues

The firmware checks for compatibility with the device it's being flashed onto. Manufacturers often include checks to prevent the flashing of incompatible firmware, which can lead to bricking the device.

Bricking Risk

Attempting to flash incompatible firmware can result in a bricked device, rendering it inoperable.

Void Warranty

Modifying the device's software in a manner not intended by the manufacturer can void the warranty.

Security and Stability

Even if you somehow manage to bypass compatibility checks and flash the firmware, there's no guarantee that it will work properly. This can lead to instability, security vulnerabilities, and loss of functionality.

Alternatives:

Given your concern with the camera's image processing, here are a few less risky alternatives to consider:

Camera Mods

Look for camera mods or tweaks specifically designed for the Galaxy S23. XDA Developers is a good starting point for such modifications, which can sometimes adjust or improve the image processing without needing to replace the entire firmware.

Third-Party Camera Apps

You mentioned GCam's excellent results but poor user experience. There might be other third-party camera apps that strike a better balance between image quality and usability. Exploring app stores for highly rated camera apps could yield some good options.

Custom ROMs

If there's a custom ROM available for the S23 that focuses on improved camera performance or allows more in-depth camera customization, this could be a safer route than flashing firmware from a different model.

While the desire for improved camera performance is understandable, flashing a different model's firmware carries significant risks and is generally not feasible due to hardware and software incompatibilities. Exploring camera mods, third-party apps, or custom ROMs designed for your specific model is a safer and potentially rewarding approach.
[Samsung Galaxy S23] Imperious Rooster:
Thanks chatgpt
[Samsung Galaxy S23] MetaP:
I
[Samsung Galaxy S23] chetszot:
Thanks for detailed reply :)
[Samsung Galaxy S23] Bill720:
Fellas, please try to stay on topic. @MetaP, it's not too difficult to see where chetszot is coming from, given how your reply reads, so, if you did generate it using software, (or copy-and-paste) then it would be helpful if you be transparent about that and cite the source. In any event, one-word (or in this case, single-letter) replies are thoroughly unhelpful, so I will have to insist that you refrain from those, going forward.

@Imperious Rooster, try to be nice.
[Redmi Note 12 4G] Matjaz001:
I am trying to sideload RO2RW however I get error: "Updater process ended with ERROR: 1"

Spoiler content hidden.

SOLUTION:

I.

For the RW2RO error I followed these steps (using OrangeFox):

After step 5 it switched from slot A to B, and because my touchscreen didnt work in slot B I used adb shell to format data and flash ro2rw

II.

After successfully flashing ro2rw my phone was stuck in boot logo for more than an hour (using EvoX and PixelExp)

To solve this I first installed this Ofox: https://github.com/chickendrop89/orangefox_device_xiaomi_tapas/releases/download/2023-12-09/OrangeFox-Unofficial-tapas.img

I then had to manualy switch to slot B and install ROM to slot A and using adb shell due to touchscreen problem (in the end never ended needing to flash RO2RW)

Here are the commands I used (some are unnecessary but I include them just in case):

Huge thanks to Himenaki
[Redmi Note 12 4G] Grippingly:
Having the same problem too
[Redmi Note 12 4G] Matjaz001:
if you boot to slot B, does your touchscreen work?

(twrp touchscreen forks fine for me in slot A, but does not in slot B)
[Redmi Note 12 4G] Himenaki:
Try installing orangefox, then flash ro2w again
[Redmi Note 12 4G] Grippingly:
I already in orangefox and it fails always
[Redmi Note 12 4G] Grippingly:
Here is the log
[Redmi Note 12 4G] Himenaki:
What flashing steps are you trying to follow?
[Redmi Note 12 4G] Matjaz001:
I have also tried using OrangeFox liek this:

1. flash orangefox

2. sideload preflash

3. sideload ROM (EvoX)

4. reflash orangefox

5. trying to flash RO2RW

I have also noted that if I boot to system between steps 4 and 5 I get the EvoX loading logo but it stays there, doesnt boot
[Redmi Note 12 4G] Himenaki:
Are you using the proper ro2w file?
[Redmi Note 12 4G] Matjaz001:
I have tried two different files:

one from here:

and another from here: https://www.ombob.eu.org/2024/01/redmi-note-12-step-by-step-to-flash.html
[Redmi Note 12 4G] Himenaki:
Try these flashing steps:

1) Wipe cache, dalvik-cache, data, metadata

2) Format data (type yes)

3) Reboot Recovery

4) flash Preflash

5) Flash ROM

6) Reflash custom recovery (if rom includes recovery)

7) Reboot recovery

8) Format data, metadata, cache

9) Flash Ro2w
[Redmi Note 12 4G] Matjaz001:
I followed your steps and I believe I got further:

After step 7, when i booted in slot B recovery, the touchscreen in orangefox wasnt working so I used adb shell to wipe partitions and then initiate sideload.

When I checked log it has "success" in name and says Complete.

However after that, when I boot the system I again get stuck in EvoX booting logo and nothing is happening...
[Redmi Note 12 4G] Himenaki:
Try flashing another rom, if they boot then the one your are currently flashing might be corrupted or just broken
[Redmi Note 12 4G] Himenaki:
And also after step 7, what you are experiencing might not be the touchscreen not working, it's a probably the unbelievable amount of lag, which you'll have to sit through
[Redmi Note 12 4G] Matjaz001:
I dont think its lag because I can control it easily via shell and it it responding immediately.

I have now installed pixel experience, but its been showing "G" booting for 5-10 min now...
[Redmi Note 12 4G] Himenaki:
Are you changing slots when trying to flash roms?
[Redmi Note 12 4G] Matjaz001:
When I am installing ROM I am in slot A, installing ROM on slot B.

After that it switches to slot B, where I do step 8 and 9
[Redmi Note 12 4G] Himenaki:
So you're not touching the switch slot button at all whatsoever right?
[Redmi Note 12 4G] Matjaz001:
no, all the slot switching is automatic
[Redmi Note 12 4G] Himenaki:
Are you trying to flash gapps after ro2w or no?
[Redmi Note 12 4G] Matjaz001:
no, just ROM
[Redmi Note 12 4G] Himenaki:
Hmmm weird, try the flashing steps I sent again using this ro2w
[Redmi Note 12 4G] Matjaz001:
will try

I have also noticed that after successfuly flashing ROM and wiping data, recovery software still says "No OS Installed" when rebooting
[Redmi Note 12 4G] Matjaz001:
I get error: 26 when using this ro2rw
[Redmi Note 12 4G] Himenaki:
Which ofox are you using?
[Redmi Note 12 4G] Matjaz001:
I belive it is 2024-01-20
[Redmi Note 12 4G] Matjaz001:
ok, I reflashed ROM and then RO2RW and both flashed ok, but I get same result - stuck at "G" boot logo
[Redmi Note 12 4G] Himenaki:
Try using the one I use, which is this

https://github.com/chickendrop89/orangefox_device_xiaomi_tapas/releases/download/2023-12-09/OrangeFox-Unofficial-tapas.zip
[Redmi Note 12 4G] Matjaz001:
I am unable to install it

I do: fastboot flash recovery <path>

flashes ok

then I do: fastboot reboot recovery

reboots to fastboot
[Redmi Note 12 4G] Himenaki:
Oh God please don't flash a zip file on fastboot, this is meant to be flashed on recovery
[Redmi Note 12 4G] Himenaki:
If you want to flash via fastboot, use the img version

https://github.com/chickendrop89/orangefox_device_xiaomi_tapas/releases/download/2023-12-09/OrangeFox-Unofficial-tapas.img
[Redmi Note 12 4G] Himenaki:
The command is fastboot flash recovery recovery.img
[Redmi Note 12 4G] Matjaz001:
still the same, stuck in fastboot
[Redmi Note 12 4G] Himenaki:
You probably nuked your boot partition by trying to flash a zip file on fastboot, try flashing a fastboot rom to fix that
[Redmi Note 12 4G] Matjaz001:
Im not exactly sure what do you mean by "try flashing a fastboot rom to fix that"

however I managed to flash your ofox to slot B (but not to slot A)
[Redmi Note 12 4G] Matjaz001:
I ended using your ofox version on slot B (with no touch) and then followed your steps 1-5, all via adb shell.

After that I booted to system and am not booted in PixelExperience setup screen, so it worked.

I will try once again with EvoX and report back, but HUGE thanks for all the support!
[Redmi Note 12 4G] Himenaki:
Glad to be of help 👍
[Redmi Note 12 4G] Himenaki:
By the way, if ever you're wondering what OrangeFox I sent you, it's this one
[Redmi Note 12 4G] Vicc_n:
i am stuck on boot logo after trying to flash gapps after ro2w, i also can't reboot to fastboot or recovery. Any help please.
[Redmi Note 12 4G] Himenaki:
What did you do to be unable to boot to fastboot or recovery?, Like what did you previously do before that happened
[Redmi Note 12 4G] Vicc_n:
i installed latest crdroid 10.0 vanilla build followed the following instructions:

[ROM][14.0][UNOFFICIAL] crDroid 10.0 for Redmi Note 12 4G[01/02/24]

crDroid 10.0 for Xiaomi the Redmi Note 12 [tapas/topaz] • Updated: 02/01/24 • Device: Redmi Note 12 4G (topaz/tapas) • By @NikitaSavc • Support • Download • Donate (YouMoney. For Russia only) Changelog: • Place volume panel on the right by...

xdaforums.com

i got to step 5 and reflashed ofox recovery, but when trying to reboot to recovery it rebooted to crdroid recovery.

i booted phone to fastboot and reflashed ofox again and it was successful

i flashed ofox zip then flashed ro2w and it was successful, then rebooted to recovery once more and flashed gapps.

this time i got error 1, i tried to reboot to recovery once more but i'm stuck on boot logo

my pc can't detect phone at this point so i'm unable to flash stock miui
[Redmi Note 12 4G] Himenaki:
So you can't boot to fastboot nor recovery no matter what you do now?, seems like a hardbrick
[Redmi Note 12 4G] Vicc_n:
i've only tried the volume button + power button method, any other suggestion?
[Redmi Note 12 4G] Himenaki:
If you can somehow gain adb connection to your phone then you do adb reboot recovery or adb reboot bootloader, otherwise your only option are the power buttons.
[8525, TyTN, MDA Vario II, JasJam General] mobileoneexpress:
can anyone help me please?

thanks
[8525, TyTN, MDA Vario II, JasJam General] ultramag69:
Do a search for and download Arcsoft mmscomposer.cab - I use 5.0.31.11.

Then run the configuration tool, if you have a rom that has it cooked in otherwise do a search, download the .cab and install it.

This should set you right...:D
[Nexus 4 General] Jiyu7:
I picked up an nexus 4 and am trying to install lineage os on it using this guide:

Install LineageOS on mako | LineageOS Wiki

wiki.lineageos.org

I am stuck on page 3, task 5

"Flash recovery on your device".

I downloaded the newest twrp and renamed it recovery.img, I put it into the same folder as fastboot.exe and I used the proper command "fastboot flash recovery recovery.img" and yet the same error occurs every time:

Cannot load 'recovery.img': no such file or directory

What do I do?
[Nexus 4 General] UReQ:
tried renaming it like twrp.img?
[Nexus 4 General] Jiyu7:
Ages ago.

Any renaming didn't help be it boot.img recovery.img twrp.img etc.. none of these (with the related command ofc) didn't work and returned the same error.
[Nexus 4 General] UReQ:
tried dragging recovery.img to command prompt?

fastboot flash recovery (dragged file)
[Nexus 4 General] Jiyu7:
I will try that and update you this evening!
[Nexus 4 General] Jiyu7:
That did the trick! Thank you
[Nexus 4 General] UReQ:
you are welcome
[Android TV General] smewhteguy:
After unlocking bootloader and rooting the ONN device I would like to do a factory reset but get the error found in attached photo. I can manually sign in but can't use Google home. Is there something I need to do to make this work again? Is my Tia

I've factory reset 3 times manually to see if that fixes but no luck.
[Android TV General] mchipser:
Same thing happened to me, I had to do it manually on the device and not use the home app..
[Android TV General] smewhteguy:
I was told I need to reflash stock vendor IMG then donate factory reset
[Samsung Galaxy Tab E  Questions & Answers] Neverin:
basically, I need help either getting the wifi situation fixed, or get a network connection of any kind on my Tab e SM-T377V. The end goal is to root the damned thing, but nearly everything i've treid needs a network connection. any help would be appreciated greatly.
[OnePlus 12] khalisz:
Hello,

Below the officials rom for your OnePlus 12 device.

The rom are updated to the lastest update.

OnePlus 12 official ROM_full package_9008 wire flash package_brick rescue package_downgrade package_firmware download​

Model information​

Bank of China = OnePlus 12 = PJD110, equipped with ColorOS

Overseas version = OnePlus 12, equipped with Oxygen OS

CPH2583 = US = American version

CPH2573 = IN = Indian version

CPH2581 = EU&PU = European version

Global = coming later

=> INFO MODERATION : Non authorized link - Link deleted

Original post from OnePlus community : https://community.oneplus.com/thread/1541327

This is what you need to unbrick your device with

Fastboot Enhance tool

.

I used it to unbrick my OP12 with the proper rom above.

- You need to pre-install related fastboot USB drivers to make sure the device can be recognize by the software.

- Only in fastboot or bootloader mode can the software recognize your device.

=> https://xdaforums.com/t/tool-windows-fastboot-enhance-payload-dumper-image-flasher.4310553

Thanks @xzr467706992

For enable the local update, you have to activate the developer mode.

Also if you want to do the local update instead of OTA update. You will need first to :

- Do a backup of your data !!!

- Disable all your Magisk module and reboot.

- Download the proper ROM for you device and copy to your device.

- For enable the local update, you have to activate the developer mode. Local update will be activated automaticly.

- See the attached video, where I show you how to access and do the local update.

- Select your rom and voila.
[OnePlus 12] thirtythr33:
so I have the US version, and I do not have local upgrade any longer, wtf is up with this
[OnePlus 12] churchmice:
The problem is the local update will grayout if the system has detected an OTA.
[OnePlus 12] nanodan:
Yup that's modern OnePlus for you. If you have the us/NA variant you cannot do local updates. You will have to wait for a custom recovery or some other method to update if you root. Stupid as hell.
[OnePlus 12] aygul12345:
So msm tool works great with Oneplus 12? I thought it was not able to use it because of authentication.
[OnePlus 12] aygul12345:
Lol is this real? And if you do a local upgrade with root what then?