yashsingh1/xdaforums huggingface dataset:
[Xiaomi 12 (Global)] NOSS8:
No updates for 6 months on the official website.

I'm closing the thread.
[Xiaomi 12 (Global)] khusika:
Moderator Announcement

Thread Closed as @NOSS8 request.
[Lenovo Legion Y700] mkolonko:
I'm trying to unlock the tablet, but fastboot doesn't recognize the device. Also, the device manager window shows the warning triangle on the driver, even if the device is correctly recognized as Legion Y700.

Did anyone had luck unlocking the device?
[Lenovo Legion Y700] Saumer:
open device manager and update(select) its driver to proper adb driver.

may be need to correct driver twice (bootloader,. fastboot - both select adb driver is ok)
[Lenovo Legion Y700] bloomfielderic:
Much easier to do it on Linux. Just fire up a Ubuntu VM
[Lenovo Legion Y700] LazaruXSoda114:
use motorola drivers instead (https://en-us.support.motorola.com/app/usb-drivers)
[Redmi Note 12 Pro / Pro Plus 5G] mino_ali:
Ok i have redmi note 12 pro plus its originally Chinese but i flashed indian rom on it bootloader unlocked and i have root access but for some reason the device doesn't got detecting on computers i tried in 2 deferent ones and no news but in. Device manager u can see the device and the original name its not about driver's i installed every driver i can but nothing new and for some reason when i restart the device it got detected but if i reconnected it won't be detected anymore so i thing flashing the rom again well fix it but i don't wanna do it that fast so any tips well be appreciated
[Redmi Note 12 Pro / Pro Plus 5G] Rares6567:
If it happens only in the rom you are Right Now, it may be a firmware issue. Can you tell me what rom are you using right now?
[Redmi Note 12 Pro / Pro Plus 5G] mino_ali:
I already fixed it i was using indian rom i flashed eea rom and im good
[Redmi Note 12 Pro / Pro Plus 5G] Rares6567:
Ok buddy! Glad it got fixed 😀. Have a nice day! ☺️
[Xiaomi Mi 11 Lite 5G] Vegeta72:
Hello Guys, I need please a root guide for my Xiaomi Mi 11 Lite 5G, 14.0.4 MIUI Version, Android 13 (V14.0.4.0 TKIEUVF) can someone please help me :/
[Xiaomi Mi 11 Lite 5G] ubi31:
you need to install twrp and flash magisk only
[ASUS ZenFone 8] nilezon:
Since Asus seem to have removed all firmwares from its web page, people with rooted phones are having a hard time keeping their phones up to date.

Could someone with working OTA please catch the OTA URL for 33.2010.2010.314 (using logcat) and post it here.

Thanks!

If you are at firmware 312 and not using an unlocked phone, please PM me and I'll help you retrieve the OTA link.

Edit:

I got the 314 OTA URL. Thanks to @dmd79 !

Mods, you may lock this thread.
[ASUS ZenFone 8] dohanin:
after downloading the delta file, how should I apply it to the phone?
[ASUS ZenFone 8] nilezon:
You rename the file to something more similar of a full update (i.e. "UL-ASUS_I006D-ASUS-[VERSION]-1.1.26-2308-user.zip) and place it on your phone (root of main storage). A notification will appear on next reboot.

For example, OTA to version "33.0210.0210.312" (above) can be renamed to:

UL-ASUS_I006D-ASUS-33.0210.0210.312-1.1.26-2308-user.zip
[ASUS ZenFone 8] D-IMAN:
Thanks for your hard work!

This might come in handy!

P.S. Asus jerks...
[ASUS ZenFone 8] skothiya:
Will this works?

Edit 1: i successfully installed the update.
[ASUS ZenFone 8] EricSlv:
Can anyone send me the link to the full file? I don't know how to follow the step-by-step instructions in the post with OTA collections.
[Samsung Galaxy S23 Ultra] thahim:
I have S23 Ultra 12 512 how can I downlod official one ui 6 without root or damaging my device.
[Samsung Galaxy S23 Ultra] butchieboy:
Lol, it's not even out yet..are you serious
[Samsung Galaxy S23 Ultra] butchieboy:
If I were you I would wait for official OTA because it really sounds like you are not very familiar with the process.
[Samsung Galaxy S23 Ultra] Klaudas:
https://xdaforums.com/t/install-one...d-galaxy-models.4615093/page-51#post-88895145
[Samsung Galaxy S23 Ultra] V0latyle:
Don't be rude.
[Samsung Galaxy S23 Ultra] s3axel:
As already written its not out yet, for official One UI 6 you'd need to wait a few months....

You can download/install the beta version, but as its a beta version it'll have a number of issues - so this is not recommended for daily use and also not for the inexperienced.... @Klaudas put up a link to the thread describing the procedure....
[Samsung Galaxy S23 Ultra] V0latyle:
@thahim As a friendly reminder please search before posting, our first and foremost rule:

As there is already a thread on this topic here as mentioned by @Klaudas above, I am closing this thread.
[Upgrading, Modifying and Unlocking] abubakar:
Recently switched back to Windows Mobile (Samsung Omnia) but it's locked to Vodafone UK. My question is, is there a similar patch around here that can unlock the phone, just like the patch i used last time to unlock my Hermes which was on Vodafone UK as well. Cause from searching the forums, buying the unlocking codes seem to be the only option to unlock Omnia.

As Omnia's on Windows Mobile as well, I believe there could be a patch, but couldn't find it even after searching. Can anyone point me to the right direction please?

Thanks in advance.:)
[Upgrading, Modifying and Unlocking] abubakar:
Will flashing a new ROM help? If not, how bout flashing a RADIO? Is flashing ROMS/RADIOS on Omnia done the same way as flashing on HTC phones such as (hermes)? I remembered back then, I needed to enter into a bootloader menu. And also flashing HardSPL before that
[Upgrading, Modifying and Unlocking] -PiLoT-:
as of yet its not really that well known, i think flashing custom roms may help but not the official ones
[Upgrading, Modifying and Unlocking] abubakar:
Owh so you mean flashing custom-cooked roms can actually unlock my Omnia? Thanks for the heads up!

Cheers
[Upgrading, Modifying and Unlocking] abubakar:
My preliminary thoughts are that if I flash a custom ROM, I can debrand any WinMo phones. Since it's debranded, it'll be unlocked. Am I right on this one?

I'm used to HTC phones, and I know bout the HardSPL and stuff like that. How about the Omnia? Has it got a specific procedure or steps to take before flasing roms to minimize the chances of bricking it?

I appreciate any replies. Thanks
[Upgrading, Modifying and Unlocking] _TB_TB_:
No, it won't be unlocked.
[Upgrading, Modifying and Unlocking] shollywood:
Debranding has NOTHING to do with unlocking.
[Upgrading, Modifying and Unlocking] abubakar:
Ok so flashing a custom ROM now won't unlock, just debrand? Is there a program out there that can unlock it? Cause its running on Winmo, so I assumed unlocking it wont be that difficult.

Thanks for your answers.
[General Questions and Answers] Wolverine998:
I'm really stuck. Don't know what to do, i compiled kernel for joyeuse, but it wont boot. Used many kernel sources from github, including LineageOS repo, positron miatoll kernel, etc. None seems to be able to boot on Xiaomi.Eu MIUI 14. Used compiler is Proton Clang. If someone can help me, it would be great. The kernel only bootloops, sometimes no vibration on startup, and sometimes it boots, but the screen remains black.
[Nothing Phone 2] HippoMan:
EVEN MORE UP-TO-DATE EDIT: It turns out that this issue is due to interaction between GravityBox A13 and Nothing OS. Although the errors manifest both in Tasker and MacroDroid, this actually seems to be due to GravityBox A13 badly interacting with the Nothing OS's System UI, and the problem is therefore also likely to manifest in other ways under Nothing OS. See the message below at the following link for more details: https://xdaforums.com/t/neither-the...rooted-nothing-os-2-0-0.4619413/post-88914283

EDIT: I originally described this solely as Tasker issues, but it turns out that the exact, same problems are occuring with MacroDroid. I have updated this OP to reflect this.

I have encountered a problem with the rooted-via-booting version of OS 2.0.0 2.0.2a that I'm running on my rooted Nothing Phone 2 ( rooted via boot per the instructions and resources in this thread: https://xdaforums.com/t/guide-unloc...k-and-patched-boot-images-model-a065.4605979/ )

The problem is that neither the Tasker utility nor the MacroDroid utility work properly on my rooted Nothing 2 phone under that OS.

I have used Tasker under various other rooted devices for something like 10 years with no problems, and I have also used MacroDroid on many of those phones, as well, again with no problems. Therefore, think this is specifically related to Nothing OS or maybe the code that's installed via rooting-via-booting.

Specifically, there are 2 problems that I've encountered so far when running Tasker and MacroDroid under Nothing OS, and no one in the official highly used Tasker forum has seen this problem under any other Android 13 OS's -- nor under any other OS's on any other devices.

(1) If I set a "run on boot" task or macro to fire off during Tasker's or MacroDroid's booting (which always has worked on all other devices and OS's), I get the following error as Tasker or MacroDroid start running on my rooted Nothing OS system:

System UI keep stopping

(i) App info

x Close app

(2) If a Tasker or MacroDroid "wait" action is invoked, it doesn't simply perform a delay like it's supposed to do and which has always worked under all other OS's and devices that I've used. Rather, here in my rooted Nothing OS system, this "wait" action causes the device to go to sleep, and the lock screen pops up, and this occurs both under Tasker and MacroDroid. This is totally incorrect behavior for the Tasker "wait" action and for the MacroDroid "wait" action.

The feedback I got in the official Tasker forum is that these errors seem to definitely be either device-specific or OS-specific issues, perhaps related to the way that the specific OS might have been rooted. No one has ever seen these problems in Tasker under any other OS's -- rooted or otherwise -- on any other devices. I get similar feedback in discussions about MacroDroid.

Has anyone else here seen these kinds of Tasker and MacroDroid errors under the rooted Nothing OS? If so, have you been able to fix them?
[Nothing Phone 2] ffejy462:
I haven't used tasker in years, but generally a good rule of thumb is to bring everything up to date as part of troubleshooting. The up to date version of this device is 2.02a. Magisk version is 26.1.
[Nothing Phone 2] HippoMan:
I'm already using Magisk 26.1.

I'll bring the OS up to 2.02a.

I didn't realize that there was a newer OS version than 2.0.0, so thank you!
[Nothing Phone 2] HippoMan:
I have now successfully upgraded to 2.0.2a, and this didn't have any effect on my Tasker problems.

As I mentioned above, no one has ever seen these problems with Tasker using any other devices or OS's, including Android 13, and including rooted and non-rooted devices. The Tasker people are saying that my problems are due to device and/or OS issues, and nothing to do with Tasker itself.

Without Tasker, this phone is useless to me, since I rely on Tasker for lots of features that I always install on my Android devices.

I'll periodically check back for newer OS versions, in case Tasker might finally start working in a future Nothing OS release.

PS: I was thinking that perhaps I could switch to MacroDroid, but now I realize that the exact, same problems occur under MacroDroid. I have updated this thread's OP to reflect that fact.

The fact that two distinct pieces of software cause exactly the same problems here under rooted Nothing OS (and on no other known devices or OS's) is further confirmation that these problems are specific to the Nothing Phone and/or to Nothing OS.
[Nothing Phone 2] dlads:
What exactly are you using tasker for?
[Nothing Phone 2] dlads:
That's mental mate...doesn't sound like a lot of fun at all...really doesn't.. so I guess the question is what is making the system fail when you attempt to use tasker.

In regards to installation, are you using a free / paid / cracked version of tasker?

Are you restoring it from another rooted device? I've via swift back up or titanium?

Are you adding one task at a time, ie: is it a specific task that's causing the problems?

Have you contacted the tasker developer?
[Nothing Phone 2] HippoMan:
I'm using the official, paid, supported version of Tasker. As I mentioned, it works fine under all other devices and OS's that I've run for something like 10 years or more. That's various devices from Google, OnePlus, and Samsung.

I am never restoring Tasker, but rather, always freshly installing it from the Play Store.

Even with no tasks defined, starting an initial version of Tasker under the Nothing 2 OS always immediately causes the "System UI keeps stopping" error that I've described.

And manually creating one, single Tasker task with the "wait" action and invoking that "wait" action always incorrectly causes the Nothing 2 device to sleep and brings up the lock screen. And the "wait" action always fails in exactly the same way in all other tasks and scenarios in which it's invoked.

And as I also reported, I get the exact, same erroneous behaviors under the Nothing 2 OS with a completely different app, namely MacroDroid, which also is the official supported and paid version, and which I also install from the Play Store ... and which also works properly under all of the Google, OnePlus, and Samsung devices on which I've run it.

Keep in mind that both Tasker and MacroDroid are completely distinct apps from different developers which just happen to offer similar event-based device-controlling functionality. And they both fail in exactly the same ways under the Nothing 2 OS, and they both work properly under all other known devices and OS's.

I've contacted the Tasker developer, and he hasn't encountered these erroneous behaviors under any other OS's and devices. He hasn't tried Nothing devices, however. He will probably get around to working on Tasker on a Nothing device, but he doesn't know when.

Similar feedback from the MacroDroid people.

Basically, there is something about the ways that Nothing devices and/or OS's handle the system UI and manage device events which differ from most (all?) other devices and OS's, and this causes problems with 2 distinct event-based, device-controlling, widely used apps.

PS: and believe it or not, all the stuff I do with Tasker actually is fun for me. I want to get my devices to work the way I want, and Tasker as well as MacroDroid very much help make that possible. People who utilize Tasker and MacroDroid also often have goals that are similar to mine.
[Nothing Phone 2] dlads:
I had something similar with substratum themes, it simply doesn't work well when certain apps open.. so for me if I theme all apps and system then running YouTube will fail system UI, simply doesn't like it at all.

Removing substratum fixes the failure.

By any chance do you have a susbtratum theme running or indeed anything else?

Have you turned on systemless and zygisk in Magisk?

Or if you have try it with them off.
[Nothing Phone 2] HippoMan:
Not using substratum.

Systemless and Zygisk are turned on. A little bit later, I'll turn them off and see whether that helps.

PS: But keep in mind that Zygisk and Systemless are on with some of my other devices, and that doesn't affect Tasker nor MacroDroid.

But I'll report my findings a little later.
[Nothing Phone 2] dlads:
Sorry man I'm running out of ideas, I wonder why tasker won't do what it's meant to do?

Is there an alternative?
[Nothing Phone 2] HippoMan:
As I've written above, I've tried MacroDroid as an alternative, and it generates the exact, same errors under the exact, same conditions. I still think that this occurs in both of these completely distinct apps because of how Nothing OS manages the system UI and how it manages device events.

Later today, I'll turn off Zygisk and Systemless Hosts and see if that helps.

PS: In the description of 2.0.2a that was shown to me when I did the OTA upgrade of that OS version, the change-log summary mentioned that work was done in that release to fix some System-UI-related errors. Perhaps more work is still needed on the Nothing OS 2 System UI code.
[Nothing Phone 2] HippoMan:
OK, I figured it out!!!

I had GravityBox installed as a module under Zygisk-LSPosed. That version of GravityBox is what was causing both errors, both in Tasker and in MacroDroid!

I prefer using GravityBox, because it fixes the Nothing OS UI much, much better (to my tastes) than "AOSP Mods" is capable of doing, but I can live without GravityBox for the time being. Anyway, the Android 13 GravityBox is being worked on, so upcoming versions might solve this problem under Nothing OS.

So ... I can now use both Tasker and MacroDroid!

Excelsior!
[Nothing Phone 2] dlads:
Process of elimination mate, defo should have mentioned you had xposed installed 😂

That'll do it.

Glad you're sorted buddy.. good times
[LG V20 Questions & Answers] mfaridi128:
I root my LG V20 with dirtysanta method, and after that install lineageos .

Today I upgrade to LIneageos 20.

for some reason I want remove root and have Lineageos with MindGapps application.

How I can do this?

I have Lineageos recovery.
[LG V20 Questions & Answers] V0latyle:
Questions do not belong in the Development section.

Thread moved.
[LG V20 Questions & Answers] dextructor:
You wasn't clear enough what root method you are using, but I'm assuming that was Magisk. So you'll have 2 paths forward:

1) Uninstall Magisk:

A) Open Magisk application and click "Uninstall Magisk", follow the instructions and it should reboot and have completely uninstalled after that.

or

B) Using the same apk that was used to install, just rename it to "uninstall.zip" or "uninstaller.zip" and flash it with your recovery.

2) Clean flash Lineage again: If the methods above don't work you can always clean install the ROM again, but make sure of having backups of your data first.

Official Magisk Uninstall documentation

Other Magisk removal guide
[Android Q&A, Help & Troubleshooting] rael7979:
Hi can anyone help me? I did root on my phone but ended up flashing the wrong TWRP and the fastboot mode didn't want to enter, neither the recovery mode nor the fastboot mode. So my cell phone went into bootloop a while later, and I ended up finger sucking because the cell didn't turn on or start in fastboot mode. Until then the PC or is connecting and disconnecting from the cell phone all the time and can not send a command.

(using translater)
[Android Q&A, Help & Troubleshooting] PhoneRepairHUB:
what model is this ?
[Android Q&A, Help & Troubleshooting] rael7979:
Infinix hot 11 m6765
[Android Q&A, Help & Troubleshooting] PhoneRepairHUB:
Can't find the model maybe it's a helios
[Android Q&A, Help & Troubleshooting] ZG_DEV:
You can flash your stock ROM by going into BROM mode, since your phone has mediatek chipset as you said "mt6765"

Wait a minute and I will return again
[Android Q&A, Help & Troubleshooting] ZG_DEV:
Is the phone called Infinix Hot 11 X662B ?
[Android Q&A, Help & Troubleshooting] rael7979:
No, Infinix hot 11 X689F
[Android Q&A, Help & Troubleshooting] ZG_DEV:
Ok

Here is the ROM download link

It is required to register to get the download link , idk why tf they did this

Infinix_Hot_12_X689F_MT6765_V1270_230608_11.zip | Firmware Drive

firmwaredrive.com
[Android Q&A, Help & Troubleshooting] ZG_DEV:
Whatever, if you want a step-by-step guide. Here you are :

Download the ROM

Download SP flash tool

Download MCT MTK BYPASS REV3

Download MediaTek Driver auto Installer

Download Sp Flash tool driver

Download VCOM drivers for sp flash tool

Install all mentioned drivers

About no.6 : If you face a problem while installation, pls tell me

Extract your STOCK ROM file

Open sp flash tool

Locate the scatter file ( it is in the ROM file, the scatter file is called scatter.txt or scatter.xml

Sp flash tool will locate the ROM files automatically, if there is a file that sp flash tool did not locate , please locate it manually

If you will flash only recovery, untick everything except for recovery

But if you will flash the whole ROM, select everything except for the preloader, flashing it will brick the phone

Before flashing, open MCT MTK BYPASS REV3, disable Windows defender real-time protection if it is not opening (note : do not use WINDOWS 11)

Select the chipset (mt6765)

Turn off your phone

Press on vol.up + vol.down button at the same time, release when connected to pc, click "bypass"

After it says "DONE", Go quickly to SP flash tool and click "flash" or "download"

And you are good to go !
[Android Q&A, Help & Troubleshooting] ZG_DEV:
If you want to unlock bootloader after flashing the ROM / recovery, tell me !
[Android Q&A, Help & Troubleshooting] zeeshanabbasi:
Hello there, I've got the same problem with my Infinix Hot 12 [X6817], I followed the whole thread but I got this error on Mediatek Bypass tool "

► Installing driver... [ERROR] MEDIATEK DRIVER NOT DETECTED". I don't know what to do also it's in bootloop and not going to turn off
[Android Q&A, Help & Troubleshooting] ZG_DEV:
You didn't install mtk driver auto installer or you didn't reboot your pc after installing/using mtk driver auto installer.

Also do not open MTK driver auto installer as administrator, open it normally.

Also, to force shutdown the phone, press the 3 buttons until it shuts down
[Android Q&A, Help & Troubleshooting] zeeshanabbasi:
thanks for the reply

I've done everything as you mentioned but still unable and got the same error. Plus my phone isn't forcing to shutdown it just restarting again and again (the problem occur when I flashed the wrong Boot.img with cmd)
[Android Q&A, Help & Troubleshooting] rael7979:
I am with the same problem and i did everything right, help
[Android Q&A, Help & Troubleshooting] mvikrant97:
Download the flash file from here.

This tutorial is for another Infinix phone but you just need the approproate firmware and flash with same steps.

https://xdaforums.com/t/how-to-guid...hing-with-sp-flash-tool-in-brom-mode.4623041/
[Android Q&A, Help & Troubleshooting] Fgbbbbsqqsvb:
hey, do you have stock ROM for Infinix Hot 11 X662B?

build number is X662B-H6913DE-R-GL-230808V457​

pls help

sorry if im annoying but my phone doesnt have wifi or bluetooth and i dont have stock ROM for it
[Android Q&A, Help & Troubleshooting] mvikrant97:
Which phone is it?
[Android Q&A, Help & Troubleshooting] ZG_DEV:
the latest version I found was V442

Infinix Hot 11 X662B Stock Firmware ROM (Flash File)

Download the official Infinix Hot 11 X662B Stock Firmware ROM (Flash File) for your Infinix Mobile. We also provide all other Infinix Stock Firmware.

firmwarefile.com
[Android Q&A, Help & Troubleshooting] Fgbbbbsqqsvb:
infinix hot 11 X662B
[Android Q&A, Help & Troubleshooting] mvikrant97:
How did this happen?

Did you flashed your before?
[Android Q&A, Help & Troubleshooting] Fgbbbbsqqsvb:
i rooted with magisk but with boot.img from the latest version (someone mentioned in another reply)
[Android Q&A, Help & Troubleshooting] xxazoz47:
how to bypass on MT6789 chip?
[Tilt, TyTN II, MDA Vario III Themes and Apps] volumnus:
Santa is bringing me a 16GB card for my AT&T Tilt (HTC 8925 WinMo 6.1). I'm currently using an 8GB card, and nearly all of my programs are installed to it. I have spent hours...no...DAYS getting my phone how I want it, so I'm understandably nervous about the prospect of changing cards.

Should I just copy the 8GB card onto the 16GB card, or should I instead do a hard reset bloatware removal and start from scratch. Now that I'm a little more experienced, it shouldn't take as long to install everything.

If anybody has advice, I'd be glad to hear from ya. Not long ago, I copied my own Garmin Mobile XT card to my 8GB card (with a few little hacks). I know Garmin won't work if I copy the 8GB card to the 16 GB card due to the piracy protection that uniquely identifies the storage card, but the other programs should transfer okay, right?

Thanks in advance.
[Tilt, TyTN II, MDA Vario III Themes and Apps] silversonic1:
If you use your PC to move everything off of the 8GB to the 16GB, there should be absolutely no problem (unless certain files just won't move) with, of course, the exception of programs that are secured. However, I can't think of any other programs that would give you trouble.