yashsingh1/xdaforums huggingface dataset:
[XPERIA X1 General] Rudegar:
without the source-code just changing the background colour would take a long time

reverse engineering

and sonyE is not much for opensource it seems
[XPERIA X1 General] iolaosx:
So it's impossible to do.. sh*t..
[XPERIA X1 General] Rudegar:
imho then it would prob be easier / faster to make a new fish panel from

scratch

of cause panels are written in pure c++ win32 so the development

is a bit more steap then if it was .net but if it was .net it would perform poorly

as is the curse of .net compact framework
[Moto G40 / G60] softwarexankit:
#MYUi #hanoip #MotoG60 #MotoG40Fusion

MYUi 6- OEM PORT V-2 Beta-3 (Hanoip)

Flavour : Global Android: 14

by Anand_>_

▪️ Download: Get here

Link deleted by moderator

▪️ Screenshots: Check here

▪️ Changelog:-

° Initial a14 myui-6 Global

° October security patch

° Decrypted

° Added KernelSu

© TWRP patched

Bug: Network related,

↪️ ( Solution )

Link deleted by moderator

Flash guide: Flash, format and reboot

Note: You can Flash GL_to_Cn module in magisk to get into CN mode, if you want.

Special Tips

❤️Contribute

Join @hanoipprojects

Follow @MotoG60Updates

Subscribe @HanoipFiles
[Moto G40 / G60] Wyrel:
Sadly it has network problems on Moto G60, and the solution didn't work on me, ill wait until a final version.
[Moto G40 / G60] softwarexankit:
Thanks for feedback contact to developer
[Moto G40 / G60] An0nY002:
Rom ta boa mas a rede móvel não funciona, fora isso ta muito bom.
[Moto G40 / G60] softwarexankit:
Tell me in English
[Moto G40 / G60] Rapier:
Thread closed and download links removed.

According to the FORUM RULES

Spoiler content hidden.
[Android Head-Units] cehamata:
Hello

I hope you are OK

Please, I need to update my android unit Allwinner QuadCore-R16

astar_d7:6.0.1 Mob30R

Which firmware fits these specifications attached? how i can install?

thank you
[General Questions and Answers] donkey_mi7k:
Hello!

I have been digging for HP tablet 10 2101 (US) firmware. Here's a little snippet of the device details:

[$ adb shell getprop | egrep -i "product|model" | sort | uniq
[ro.build.product]: [spruce]
[ro.product.board]: [J6F00UA]
[ro.product.brand]: [hp]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [spruce]
[ro.product.firmware]: [1.0.9.4.us]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [Hewlett-Packard]
[ro.product.model]: [HP 10]
[ro.product.name]: [engelmann]

HP website only seems to have a recovery image with 4.4 kitkat, which means this tablet is just a fancy paper weight now. Play store is just showing that this device is unsupported when I search for apps to install. I don't want to give in and accept defeat because it's not a bad tablet at least for watching youtube and netflix.

I figured asking before bricking the thing.

I don't mind taking a path down towards compiling if anyone can point me in the right direction.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ucops:
Hi,

I have a big problem.

After I tried to install rom it says

updating partition details

Failed to mount /system_root (block device required

Failed to mount /vendor (block device required)

Failed to mount /odm (block device required)

Failed to mount /system_ext (block device required)

can someone help me?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] jefffrom:
after flashing reboot beck to recovery then reboot to system you should be fine
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ucops:
it doesn't have os
[Android TV General] dmartins90:
Hi guys, I have a problem here, I have a system that runs well on all Asus box or tinker TVs, Raspbery, but in a specific version here of a TV box with Android 11, it's getting a margin at the top of the screen, it's like if everything was offset 1 or 2 pixels from the top where it should be 0.0 on the x and y axes. I'll show you with images to understand... Is it possible to fix this?

If you notice, you see that there is a displacement at the top, as if there was a margin, it is not glued to the top like 0.0 x and y. This is ok on other devices;

View attachment 6033823

Here is the bottom part, if you notice it is ok, leaning against it, unlike the image above which has a margin at the top

View attachment 6033825
[Android TV General] Not_Rich:
Silly question but does your tv remote have a zoom or fit picture button?
[Android TV General] dmartins90:
First, thank you for getting back to us. So actually this happens with all other TVs and monitors, but only with this TV box with this firmware. So I think it could be something in the firmware or in the Android view.
[General Questions and Answers] crvgezk:
Mod edit: Thread closed as OP removed the openings post content. Oswald Boelcke, Senior Moderator

deleted
[Redmi Note 10S] Syntaxis_:
Hello everyone!

A new custom firmware has been developed for our device (THE AUTHOR IS NOT ME)

Spoiler content hidden.

What is LibreMobileOS? - Rich Featured Privacy Focused Mobile OS

Spoiler content hidden.

Spoiler content hidden.

Have fun!
[Redmi Note 10S] ZG_DEV:
Thanks for publishing the rom !
[Redmi Note 10S] Syntaxis_:
Have fun!
[Redmi Note 10S] Ibazeta:
Does it have the option to wake up the screen with double tap?
[Redmi Note 10S] Syntaxis_:
I think you'll can enable it in settings. Because it based on LineageOS and it have this function.
[Redmi Note 10S] Rishik Y:
Thanks for sharing the link!
[OnePlus 11] ZG_DEV:
Thanks for the guide, mate:)
[OnePlus 11] Causical:
Hi great guide, forgive me for not entirely understanding the point of this, but how does this differ from doing something like booting a KSU image, granting Magisk super user privileges and direct installing, then when the time comes choosing restore image, doing the update and then installing Magisk again to inactive slot? Am I missing something, does Magisk not restore the image properly in some cases as opposed to others? Why in your scenario would Magisk restore the images properly so you could update easily just because you manually wrote the partitions in terminal?

EDIT: oh okay, so I think you're saying you had already flashed a rooted init boot on a14 but there isn't a compatible KSU image so far that will boot in order to allow you a direct install of Magisk...so wait, does that mean that Magisk's "restore images" function is solely reliant on doing a direct install? So your problem is actually that "restore images" doesn't work with a patched and flashed init_boot?
[OnePlus 11] shootind5nukes:
You are correct. Restore images won't work with a flashed patched init_boot. This guide allows you to restore images so you can take updates. Otherwise you must remove magisk and use fastboot to flash stock init_boot, then you can take the Ota update. This is why KernelSu is the preferred way, but it doesn't work with android 14 on our phone yet.
[OnePlus 11] Causical:
One more question, does this also imply that a patched init_boot can be written to the partition in terminal emulator to obtain root?
[OnePlus 11] shootind5nukes:
No. Root is needed to be able to write to the partitions.
[OnePlus 11] binary**#:
Excellent work mate. But I have a query. Up until the step which I have quoted from your guide [which infact covers the majority of the guide], we have simply flashed the stock init_boot. So can't we take a much shorter approach of extracting the payload, getting the stock init_boot, and flashing it?

Did you opt for this approach as it doesn't require downloading the entire firmware?
[OnePlus 11] shootind5nukes:
I'm sorry I don't understand what you mean. I got the stock init_boot from payload. The purpose of this guide is to show someone how to find the correct partition(dev/block/sde63) so the phone can be flashed AFTER the phone is booted. So yes you can just extract init_boot from payload and flash it. But flashing it via fastboot you will lose root. My guide shows you how to find exactly where to flash it with dd in terminal so you keep root and get the direct install option, thus getting the restore images options.
[OnePlus 11] binary**#:
This helped. Thanks!

On a side note though, your guide helped me with another useful finding. For subsequent OTAs, if we need the patched init_boot files, we could simply use those "dd block" commands to extract the files directly from the device without the need to download the entire firmware.
[OnePlus 11] shootind5nukes:
I agree. This opened up many things to me. Can't tell you how many posts I've seen with people looking for their boot.img and init_boot files after they root. If you are on Android 14 and want to be able to take updates easily my guide will solve that. Remember that to use my guide, or just dd, you must already be rooted. So if you root using init_boot and flashing via fast boot the init_boot you extract is not the stock and is already patched. In that example you'd still need the stock file that you used magisk to patch in the first place, which is what I did. Even after you do a direct install magisk still patches init_boot I believe so it's best to keep the init_boot from payload handy.
[OnePlus 11] shootind5nukes:
Update.

This works on 14.0.0.201
[OnePlus 11] ahasae:
can someone provide the init_boot files we use
[OnePlus 11] lloydsw:
Thanks so much for this. I inadvertently forgot to restore images before I updated to 14, so I've been rootless for four days. I finally had time to get and patch an image today & re-rooted. Now I'm glad to have an image to restore before the next OTA update.

Ott topic: I see I have about a dozen backups. Is there any harm deleting the old backups?
[OnePlus 11] shootind5nukes:
Which phone model do you have?
[OnePlus 11] BeachNYC:
Thank you for this. It sure seems that this has all gotten much more complicated than it ever was before, but maybe it will seem easier with repetition.

I, too, am at a loss as to just how we get these init_boot files. I'm running 14.0.0.201(EX01) on CPH2451. I am not yet rooted, and unclear how I get the boot files from the full OTA I downloaded through Oxygen Updater and installed. (One post provided information that began with installing Python, and that is just way above my intelligence or competence level!)

I understand the importance of Magisk being able to restore images, and can follow your directions regarding how to do so. But I'm not sure how I get to the point of being rooted on Android 14 so that I can proceed. (And yes, I know there are several posts purporting to explain how to accomplish this, but I'm really not knowledgeable enough to know when there's a typo in the suggested command or which of four (or more!) methods to try.)

Thanks for your patience with those of us who are sorta slow. :(
[OnePlus 11] cabagekiller:
you have to dump the payload.bin file and find the init_boot image for you respective version of OP11
[OnePlus 11] abc1054:
Here is a web Link I used to root Oneplus 11 with magisk
[OnePlus 11] abc1054:
init_boot_201.stock.img already given in this forum for your phone 14.0.0.201(EX01) on CPH2451. Then Follow this website.
[OnePlus 11] ahasae:
CPH2451
[OnePlus 11] abc1054:
CPH2451 14.0.0.201(EX01)
[OnePlus 11] shootind5nukes:
Look in my first post. That's the stock init_boot from cph2451 on 14.0.0.201
[OnePlus 11] deechte:
Forgive me for asking, but are you actually sure of that? When I got the Oneplus 11 it was running A13. I rooted it by flashing a patched init_boot.img to it. So no KernelSU. I patched that init_boot.img on the phone with Magisk, when it obviously wasn't rooted yet. That produced a backup folder with the unpatched init_boot.img in it in /data/. I was able to do all OTA updates from Oneplus using remove Magisk > Restore images after that.

Now with A14 something else went wrong and I lost root. I followed the exact same steps and there now is a new Magisk backup folder from that date. I unpacked the init_boot.img.gz file that's in it on my PC and with md5 concluded that it's the same as the stock init_boot.img from the A14 package. I assume that can be used for Restore images like I was able to on A13.
[OnePlus 11] shootind5nukes:
For me it didn't work. Maybe something in magisk changed? It definitely didn't work for me.
[OnePlus 11] shootind5nukes:
Here's why I dont see how magisk makes a backup yet of all the needed files. If we use magisk to patch init_boot, when does it make a backup? Are you implying that it makes a backup of everything you patch? So if you use your phone to patch my completely different phone would magisk make a backup of that file during the patch? Let's assume it doesn't because you could brick your device if it made backups of anything you patched and restored the wrong file later. I believe magisk does make some backup files when you let it finish rooting your phone after you flash a patch init_boot, however it does not have your original init_boot. So even if you do restore images at that point the update would not go through. This has been my experience many times. If we follow my guide then let magisk do a direct install then we can successfully use restore images and the update work.

Like I said this is my experience though. To test this I will try an update with a patched_init boot and restore images. I'll report back if it works, but I know in the past is hasn't worked for me 100% of the time.
[OnePlus 11] deechte:
I don't have the answers. Indeed if Magisk kept a backup of anything it patched, even if that would be a file for a different device, restoring that would cause problems. I don't know if it does keep a backup of everything, neither if that would all be restorable.

I do know that it has kept a backup of my stock Android 13 init_boot.img that I successfully used to restore. And I do know that it has made a backup again of my stock Android 14 init_boot.img. I'm confident that'll work in the future.
[OnePlus 11] megaslx:
if I use a full ota package to perform a local update,do I still need this method?

I assume the ota procedure will write the stock init_boot img to the inactive slot so that magisk can do the backup thing correctlly
[OnePlus 11] shootind5nukes:
If you are already rooted let magisk install to inactive slot, assuming you initially rooted using kernelsu you should be good.
[OnePlus 11] megaslx:
you are right,I'm still on A13 and using kernelsu.

so the problem with maigsk and ota is patched init_boot will cause ota update failure?
[OnePlus 11] shootind5nukes:
yes
[OnePlus 11] BeachNYC:
I didn't really understand what this was all about until I decided to update to Android 14, got the Magisk "no images to restore" message, and followed your instructions. They were incredibly clear and easy to follow, and the update was successful. Thank you so much for putting this together.
[OnePlus 11] shootind5nukes:
See above. His experience was exactly like mine.
[OnePlus 11] cahir1495:
Could someone send me latest stock boot.img and init_boot.img for CPH2449?
[OnePlus 11] deechte:
Download the full package with Oxygen Updater and extract it from the payload.
[OnePlus 11] cahir1495:
The problem is that I messed something up with magisk and I can't boot my phone, it keeps rebooting at splash screen
[OnePlus 11] deechte:
Which version do you need?
[OnePlus 11] deechte:
Well today version 14.0.0.304 became available, so I was eager to test. Unfortunately, the OTA became available before Oxygen Updater had it. And like I had seen back on Android 13, the local update option is greyed out when an incremental upgrade is available over the air. So I can't proceed with the full update from OU. Does anyone know how I can remove the information on the incremental update? Rebooting with flight mode on doesn't do it.
[OnePlus 11] cahir1495:
Nevermind, I'm currently using EDL. However, thanks
[OnePlus 11] shootind5nukes:
Have you tried the localupgrade that opp uses? What I mean by that is go into settings, then apps, then in app info hit open. It let me local upgrade that way when other methods didn't work.
[OnePlus 11] deechte:
Which app from the list do you mean?

I've found my own solution though. I've turned off mobile data on my device, turned off my Wi-Fi access point (maybe turning on flight mode will achieve the same, I'd have to try next time), then went to this app in settings > apps and deleted cache and data:

It's package name com.oplus.ota.

Then rebooted my phone and the incremental OTA update was out of the way and the local update option was no longer greyed out.
[OnePlus 11] deechte:
So now that my incremental update problem is solved, I updated from 14.0.0.201 to 14.0.0.304. I used the easy way from this post, with this as my starting point.

It worked fine, Magisk Restore Images worked. So I still see no need for the hard way as described in the OP.
[OnePlus 11] shootind5nukes:
That's the app I was referring to. Glad you found a work-around.
[OnePlus 11] shootind5nukes:
Not sure. From my experience and the experience of others it doesn't work. Glad it works for you. Phones do weird things.

Edit. When you flash init_boot what's the exact command you use?
[OnePlus 11] deechte:
I extracted the init_boot.img from the payload file from the full 14.0.0.201 update zip, copied that to the unrooted phone, patched it with magisk, copied back to PC and then

fastboot flash init_boot magisk_patched_boot.img
[OnePlus 11] flynmoose:
Anyone have this happen? I took the upgrade on a CH2451 (NA) from 13->14 using the OTA method I've used in the past. Reinstalled Magisk before I allowed it to reboot. It rebooted and did the optimiziation routine but once booted it does not recognize the SIM. I did all the normal sim things and couldn't get it to work. Finally right before I did a hard reset, I flashed the stock init_boot in this thread to B slot which was the active slot(which obviously killed my ROOT).

Reboot and viola - I have SIM active and can make calls. But no matter what method I use to patch init_boot (this thread or Magisk and flash from fastboot) - the device boots but it kills the sim card access.

I'm stuck. Am I missing something or did I somehow get a bad update that has gooned the radio. Seems like if that were the case it wouldn't work with the stock init_boot.

Guess I'm living without root for now.
[OnePlus 11] Mr. Pi dot:
Hi,

I followed the steps as described by @shootind5nukes and it was clearly reproducible, thanks for the tutorial. First of all I made the dumb mistake and replaced init-boot in both slots with ADB root to the stock files and directly rebooted. I lost root, realized the error, re-patched init_boot via Fastboot and then I chose "direct install" in Magisk after replacing the init-boot files again via ADB. It went well and seems to be a great workaround for the problem to not be able to temporarily uninstall Magisk, because the uninstall and "restore files" option throws an error otherwise.

I am on CPH2449 and never experienced any SIM card issues so far. I extracted the init_boot from the current 14.0.0.304 version with payload-dumper. Did you do so as well, or did you take "any" init_boot from the web?

P.
[OnePlus 11] appileh:
"Now when an update comes you can use Magisk to restore images to get the update then do Install to Inactive after the OTA. I put this guide together fast so if I missed something just letme know."

When can we do the restore images and apply after OTA? In which part of the process? Download & verify or Install?
[OnePlus 11] deechte:
For the record, effortlessly updated CPH2449 from 14.0.0.304 to 14.0.0.401 today in the same manner.
[OnePlus 11] Mr. Pi dot:
Hi,

@deechte - thank you for your update. For some reason I (in contrast to you) initially faced the problem that I could never choose "Restore Images", Magisk always threw an error message. According to Google, several user have this problem if they root via Magisk with a patched init-boot.img file. By using this Workaround (i.e. replacing init_boot.img files in filesystem via ADB with stock ones and then choose "manual install" in Magisk again), I finally was able to apply "restore Image" in Magisk, install OTA full package in other slot and keep root. Update to Version 14.0.0.401 went flawlessly without any issues. So if someone is facing the same issue, I would highly recommend this workaround. But I agree - If Magisk works in your Install as intended. there is no need to do it the "hard way".

P.
[OnePlus 11] shootind5nukes:
After your rooted and your follow my guide, then restore images. After that install the update. After the update is done it will ask you to reboot, STOP. Then go back to magisk and choose the install to inactive(OTA) option. It will reboot you.
[OnePlus 11] shootind5nukes:
I always extract from payload.
[OnePlus 11] appileh:
So i got an ota. When i want to Restore image i get the next error: 'Stock backup does not exist'. Any idea how to fix? Can i use the init_boot.img?

And what are the steps? Anyone..
[OnePlus 11] shootind5nukes:
Follow my guide in the first post. Literally exactly why I made this guide
[OnePlus 11] appileh:
Thanks sir. I think i update again the normal way and re-root. After that i will check it out.
[OnePlus 11] Skkyee:
Hello, I have some questions.

1. I know that CPH2451 has no full ota packages, so you should restore stock image first before update.

But I'm currently in CPH2449 EU edition which have full ota packages. Do I need to restore stock image before full package ota update.

Or can I restore stock image and do incremental update?

2. Maybe this method also work? I've try it with my Mi 8.

fix-magisk-stock-backup-does-not-exist.md

GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

* first I create a image backup manually following this method

* than I restore stock image using magisk app and do direct installation than reboot

* after reboot there will be a new image backup, so I just delete the older backup created manually by myself.
[OnePlus 11] wfred:
If you're on 2449 with full update downloads you don't need to restore images.

Download the full update & install using the local update option

STOP

Open Magisk and install to inactive slot

Reboot
[OnePlus 11] Skkyee:
Thanks.

But what if I restore images first, can I update using incremental packages like CHP2451
[OnePlus 11] TheSayaMan:
btw kernelsu is now available for crdroid/watchdogs and is much better at hiding root.

an open letter to those seeking ksu on crdroid/watchdogs

https://storage.googleapis.com/7072696d6573/boot_ksu.img you are welcome,

xdaforums.com
[OnePlus 11] ablak44:
During the last two 2449 EU updates I download the full package via Oxygen Updater. But the device boots up immediately after the update and I can't install Magisk into the second slot. I have already lost Root twice and have to do the entire root procedure ( init.boot) from the beginning. How to do it correctly?
[OnePlus 11] deechte:
I've dropped instructions in this thread that work for me every time (CPH2449), including going from 14.0.0.401 to 14.0.0.501 yesterday. See post #48.

You can check if there are images to restore by going to /data/ with a root browser and check if there is one or more magisk_backup_* folders there from previous times you patched an init_boot.img.
[OnePlus 11] ablak44:
I don't have previous images because I reset to factory settings after the first failed update with Magisk. If I run a local installation of the image downloaded via Oxygen Updater, when will I install Magisk to the inactive slot? Unless you do it now before installing locally?
[OnePlus 11] deechte:
I don't entirely understand your question. If you lost root, these instructions don't apply. They are just for updating and keeping root.
[OnePlus 11] ablak44:
I have Root. Should I click >>Extract<<? And then there will be >> Install<<? Will it install immediately and I won't have time to install Magisk?
[OnePlus 11] topstarnec:
I have done all the processes as you written. In case there is an OTA update, what should I do? Uninstall Magisk > restore image, then?

How to use the /dev/sde32 and /dev/sde63 ? How to re-root after OTA without a computer?
[OnePlus 11] deechte:
The instructions are very clear on what to click on what moment, follow those exactly. I don't know if it'll work though without restoring images.
[OnePlus 11] wfred:
It should work fine, but I've always preferred full over incremental so I can't say for positive