yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A32 5G] drakeheart77:
I've been out of the loop for awhile but I thought I'd go ahead and give this A32 5G root access. Prior to this phone I never needed to root any of my devices. Since this dinky phone can't even handle Pokemon GO that's all the reason I need to root.
[Samsung Galaxy A32 5G] TimmyP:
I think you are still out of that loop.
[Samsung Galaxy A32 5G] ksaves2:
No OEM unlock in the latest Samsung a32 5g phones in the developer mode. Been searching all day online and I'm bushed. Am getting scared it isn't possible with the SM-A326U phones. Tried adb and fastboot as I've run Linux since 1992 and even though I get a connection, only the commands that get phone information and reboot it work. Can't do anything without an unlocked bootloader. OEM unlock appears locked into oblivion for users which is ashame. I will never buy any Samsung product ever again. The phone was what was handed to me as my Nexus 6p's were obsoleted by the changeover to 5G by my provider. No backwards capability otherwise I'd still be using my rooted 6p's

Kurt
[Samsung Galaxy A32 5G] MiTHuntress:
I was going to buy the Samsung a32 5g phone in hopes to root it. The phone I have is the Samsung A20 which also cannot be unlocked. I went into developer options and turned on "Force allow apps on external" to free up space on the A20 phone. It helped some but now after months of using the phone this way my phone storage says full all the time. I have uninstalled some apps I don't use and still have not much storage space freed. I don't understand this company's reasoning with locking phones in the US like this. Samsung has been my go-to cell phone company for years. This is so disappointing. Thanks for sharing before I wasted my coins on another crap phone.
[Samsung Galaxy A32 5G] TimmyP:
Get used to it. As more and more phone companies integrate things like NFC payments, etc and focus on security phones are gonna be less rootable in general in the future.

PS this phone is rootable if you are on BL3.
[Samsung Galaxy A32 5G] andioshelp:
Can anyone help me get an unlock bootloader dump for b3 or older
[Samsung Galaxy A32 5G] financeledger:
contact me
[Samsung Galaxy A32 5G] Forumuser3:
Would u help me too pls?
[Samsung Galaxy A32 5G] GalaxyA325G:
I read all the posts in this thread, most of which conflict, but the gist seems to be that this particular phone isn't rootable, am I right?

Mine is T-Mobile, the SMA326U.
[Samsung Galaxy A32 5G] ShaDisNX255:
Correct. "U" (U.S.) and "W" (Canada) variants have their bootloaders locked. As of today I've only seen paid methods to unlock them with some exceptions like S8 and S9 that have exploits.
[Samsung Galaxy A32 5G] TimmyP:
Idk if they are still active, but I can vouch for their services. I have a very different A326U now. Completely customized rom and MUCH better performance. It plays every Gamecube, Wii, PS2 game ive thrown at it!
[Xiaomi Poco X3 Pro] hameem3105:
I'm on miui version 12.5.3 RJUINXM. I have been getting lots ghost touches lately and its really annoying. This is mainly the reason i have decided to install Arrow OS.

Anyone out there getting ghost touches on arrowos? Will changing the ROM fix the problem or, should i just wait for another miui update?
[Xiaomi Poco X3 Pro] 0b4:
Nothing fixes the ghost touch issue, I tried every rom and every version of MIUI. Totally pointless. If you have warranty, use it, and send back this piece of c**p.
[Xiaomi Poco X3 Pro] hameem3105:
Did you use pixel plus ui? I hear its quite stable
[Xiaomi Poco X3 Pro] 0b4:
I did. Didn't solve ghost touch for me.
[Xiaomi Poco X3 Pro] hameem3105:
So, did you claim your warranty?
[Xiaomi Poco X3 Pro] 0b4:
The store disappeared where I bought the phone from so I don't have warranty...
[Xiaomi Poco X3 Pro] AxisKiku:
Wait for the new firmware, that might solve the issue.
[Xiaomi Poco X3 Pro] 0b4:
It won't.
[Xiaomi Poco X3 Pro] allan_sundry:
There's a rumor at the 4pda portal that ghost ghost touch issue could fixed by setting tight connection between display cable and motherboard.

Another rumor is connection between case usage and ghost touch.
[Xiaomi Poco X3 Pro] jon-e-k:
I contacted xiaomi's local office rather than the store, they asked for proof of purchase but issued the RMA. Just waiting to get it back fixed (hopefully)
[Xiaomi Poco X3 Pro] TioCareca:
Ghost touch is related to display panel, tianma or huaxing, tianma got ghost touch...

It may be hard to fix because fixing tianma ghost touch may cause huaxing to became buggy, i saw that on poco f1 as rom devs needed to make 2 version of the roms to each panel until a middle term could be reached...

Xiaomi got that bad habit to get 2 different panels to same phone...
[Xiaomi Poco X3 Pro] ValgarBaldr:
I never experienced ghost touch in any factory or custom ROM
[Xiaomi Poco X3 Pro] fudi2002:
12.5.3 has been complained about by several, including me. I switched back to 12.0.6, perfect ever since. On the other hand, several people confirmed by telegram that 12.5.4 is good.
[Xiaomi Poco X3 Pro] Skytsengel:
i have the same problem... i dont have warranty of the phone so, i have a piece of ****... i need to buy a new phone... i cant wait to another version of miui... itso so annoying for me
[Xiaomi Poco X3 Pro] rana103:
Same experience here also. Although after 12.5.4 tried custom rom. Ghost touch is like my neighbor now. Any custom rom u trying now after 12.5.4 ???
[Xiaomi Poco X3 Pro] Areasu:
Update to 12.5.5 it solves it
[Xiaomi Poco X3 Pro] jpl90:
Hi, I bought a few days ago an X3 Pro 6GB and it also has the Tianma panel :(. So far, no issues, but I'm reading bad experiences everywhere...

I would really love to try custom roms, but in that case isn't warranty voided? Or how do you manage to try custom roms and then claim warranty?

Thanks!
[Xiaomi Poco X3 Pro] osmosi:
Flash stock and relock bootloader. Then go to service centre.
[Xiaomi Poco X3 Pro] jpl90:
But isn't it necessary to request something specific to Xiaomi for unlocking the bootloader? I mean, Xiaomi should know that the bootloader has been unlocked in that device, right? They just don't check?

Thanks!
[Xiaomi Poco X3 Pro] osmosi:
Bootloader unlocking doesn't void warrenty. So technically you should be able to get service without locking. But in reality sometimes local service centres cerate problems and refuse service service when bootloader is unlocked. So to avoid all the drama it is advised to relock if you can.

Edit- Depends on the country. According to Xioami India bootloader unlocking doesn't void warrenty. Don't know about other countries.
[Xiaomi Poco X3 Pro] d_g_m_2000:
that depend on the country, here in mexico if u unlock the bootloader it doe vod your warranty, aside, the 12.5.5 solve the ghost touch
[Xiaomi Poco X3 Pro] osmosi:
Yes. My Bad. I should have mentioned that.
[Xiaomi Poco X3 Pro] drsandeshdahal:
I disabled game turbo and used microsoft launcher for few days, and ghost touch issue is completely gone. I dont know if it was game turbo or the launcher issue.
[Xiaomi Poco X3 Pro] d_g_m_2000:
they say that firmware 12.5.5 solve it...
[General Questions and Answers] Reyyanyaqub:
Hello is there any php 7 server app for android which is free and works on android KitKat I know there is ksweb but it need me to buy everything just to start it even and termux us not available on android KitKat and I do t have enough memory to buy a now phone or PC pls help
[ASUS ROG Phone 5 / 5s] twistedumbrella:
DO NOT LOCK THE BOOTLOADER WHILE ROOTED!

When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader.

Locking the bootloader will not fix most issues. It will allow you to use apps that check for an unlocked bootloader without the need for any additional modification. That is the ONLY benefit.

If you still want to lock your bootloader, make sure you can say yes to each of the following:

1. Have you restored the stock boot.img / vendor_boot.img and the phone functions normally?

Spoiler content hidden.

2. Have you made a backup of everything you do not want to lose when wiping the phone?

Spoiler content hidden.

3. Have you flashed raw firmware and made sure the phone and updates function normally?

Spoiler content hidden.

4. Have you performed a factory reset and made sure the phone functions normally?

Spoiler content hidden.

Once you have verified all of the above requirements, you are now ready to lock the bootloader.

Spoiler content hidden.
[ASUS ROG Phone 5 / 5s] twistedumbrella:
Reserved for QA information
[ASUS ROG Phone 5 / 5s] twistedumbrella:
Based on new information, it does seem possible to repair the issues caused by converting.

That said, this guide is still quite relevant. After all, most of the issues people were having were caused by unlocking the bootloader, converting, rooting, and locking the bootloader. The warning for possibility of not being able to unlock have been removed, but the info about restoring to stock before locking has been left.
[ASUS ROG Phone 5 / 5s] chairman011:
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
[ASUS ROG Phone 5 / 5s] falhumai96:
@chairman011 what variant of the phone it is (e.g. CN or WW or US, ...etc.)? Also, when they returned it to you and you were able to unlock it again, was it on the original firmware (or any version in its lineage (i.e. not a ROM that's not original))?
[ASUS ROG Phone 5 / 5s] nexusnerdgeek:
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
[ASUS ROG Phone 5 / 5s] falhumai96:
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?

I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
[ASUS ROG Phone 5 / 5s] twistedumbrella:
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
[ASUS ROG Phone 5 / 5s] mhrs.11:
So, basically the bootloader unlock for tencent devices will always locked unless asus uodate their unlock app or has their been another way around it yet?
[ASUS ROG Phone 5 / 5s] twistedumbrella:
The unlock app should unlock the bootloader at least once. Unlocking it a second time has mixed results.
[ASUS ROG Phone 5 / 5s] 0v3rkill:
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.

Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol

Oh! and my rog is not the china version thanks :)
[ASUS ROG Phone 5 / 5s] Andrologic:
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
[ASUS ROG Phone 5 / 5s] 0v3rkill:
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks 😊
[ASUS ROG Phone 5 / 5s] Andrologic:
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.

https://xdaforums.com/t/raw-firmware-collection-and-guide.4287497/
[ASUS ROG Phone 5 / 5s] 0v3rkill:
Hi there, I did follow and did the raw setup it did got me through the boot loop. However, its stuck on the system start up updating screen and stays in 0%.
[ASUS ROG Phone 5 / 5s] 0v3rkill:
Darn i thought im already dead! i didn't even know how i fixed it hahahaha! but its working now successfully downgraded to android 11 because its the only firmware i found and managed to make it work again combination of alot of research in google and here xda. working 100% imei two of them, finger print and sn are all intact. thanks guys
[ASUS ROG Phone 5 / 5s] nexusnerdgeek:
For these few reasons I have to give up root & lock the boot-loader: 1. Financial apps stop working from time to time causing much grief; 2. I've used root functionality precisely for nothing for a year I've had it; 3. It was getting all too complicated to keep up with it all.

(The original intention for unlocking/rooting was to get some sort of unofficial VoLTE and VoWiFi for the mobile operator of my choice; however, it didn't help. Then a newer firmware implemented VoLTE and VoWiFi! So my impatience, admittedly couldn't be known at that point in time, backfired.)

I've nothing to preserve on the phone, due to having a Moto G 5G backup phone. I only had it working with adb & fastboot in my Linux laptop (up to date Fedora 36). I had no working Windows laptop then. But I do now. However, adb on Windows says the device is "unauthorised" (as expected); fastboot in it doesn't list the device. So I might be limited to my Linux laptop only. The phone was previously working on the last A11 WW firmware fine.

I've tried to follow the steps from the original post of this thread. First one worked with vendor_boot, dtbo & boot images (used only 18.0840.2202.231 versions of them). Second N/A. With third step, flash_raw_and_wipe_data.sh fails by core dumping.

Right now, the phone boots to fastbootd & not further. Any help is much appreciated.

(I think I'm inching towards fully bricking this phone. I'm not there yet, but getting closer :). It'd be nice to get it working again without root & with locked boot loader. Any help is much appreciated.)
[ASUS ROG Phone 5 / 5s] nexusnerdgeek:
This is where I'm at while executing step 3 of the initial guide in this post:

When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.

(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)

Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.

While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".

(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)

I don't think it can boot any further at the state that it's in now.

I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?

I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.

In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
[ASUS ROG Phone 5 / 5s] Andrologic:
Confirm that you can send fastboot commands to the device. It's a prerequisite for flashing the original boot img back or doing a RAW flash if boot looped. That's the very first step you need sorted and confirmed. Sounds like you may not be in the right Fastboot mode. The RAW version doesn't matter too much as long as it's in line with your device version, you just need it to get back up and can upgrade normally to other versions.
[ASUS ROG Phone 5 / 5s] nexusnerdgeek:
Thank you @Andrologic for the hint that I might have been attempting to flash when the phone was in the wrong section of the boot process. Indeed it was: From the boot-loader, the phone ought not to have been progressed to Recovery mode for the raw firmware flashing to work. That was my mistake.

Now I was able to successfully flash the raw firmware image cited in the initial post. Even right before the firmware update, I've noticed that the phone doesn't always boot to boot loader when powered on. Since flashing raw firmware, I haven't been able to get it to boot even to boot loader. At best it loads some sort of garbled graphic screen of some sort (possibly Android setup screen??).
[ASUS ROG Phone 5 / 5s] nexusnerdgeek:
Actually I needed patience as usual. The most recent problem was due to depleted battery by the look of it. After charging the phone using its charger for an hour, I was able to boot it successfully and it went straight to ASUS ROG Welcome screen (with music, language selection and all).

As recommended in the original post, I'll proceed with updating it all the way to up-to-date A12 firmware version from ASUS website. Then I'll attempt boot loader lock. 🤞

Thank you for your help.
[ASUS ROG Phone 5 / 5s] nexusnerdgeek:
The instructions provided in the OP worked great. Got a successfully-working-with-a-locked-bootloader phone now. Thank you all for working out the meticulous/intricate steps & related firmware links etc to make it possible.

(From Android 11 raw firmware 18.0840.2106.83, within Android itself, updating to Nov A12 firmware 31.0810.1226.139 downloaded from ASUS website didn't work; however updating it to the highest A11 18.0840.2202.231 & then jumping from there to Nov A12 update 31.0810.1226.139 did work.)

(And oh, up-to-date Fedora with its native android-tools package provided fastboot tool worked just fine for all fastboot work; so there was no need for Windows platform for it, which is simply great.)
[ASUS ROG Phone 5 / 5s] Stone Collector:
I have a question. I didn't alter[install] any other system image but have TWRP installed. In addition, I have both, rooted and unrooted my device in past [using magisk]. So, should I proceed or not?

Thanks
[ASUS ROG Phone 5 / 5s] twistedumbrella:
As the post says, if you lock the bootloader while rooted, the image fails verification. If you have a custom recovery installed and lock the bootloader, you risk the same outcome.

Plenty of people have thought they were above taking simple precautions or that it didn't apply to them. You can see how that turned out by all the "please help me!" threads.
[ASUS ROG Phone 5 / 5s] Stone Collector:
Thanks. I will flash the original firmware directly.
[ASUS ROG Phone 5 / 5s] beanbean50:
Damn! wish I knew/read about this a few days ago!

Trading in my flip 3 for the flip 5 I did a factory reset then relocked the bootloader, but it wouldn't boot up to the OS anymore (the charging port broke months ago, so couldn't do any ADB or whatnot)

I've sent it to them still in the same state with a little note apologising and hoping they can fix it.. fingers crossed
[Redmi Note 10] AhmedRadowan25:
Recently I installed Twrp by nebrassy with pixel experience plus rom.In the recovery at first i try to backup nandroid in a usb drive via otg.I select all available partition for backup.Everything was fine.But at the ending of backup process, when system part was backing up it shows backup error, deleteing files.Then i try to back up in internal storage.In this senario, Twrp shows backup was successfull at n.. secods.But when I boot into system I found no backup file of twrp in my internal storage.I tried it twice,But same result.Now, is there any way to successfully back up nandroid in my device?
[Moto G9 Play Questions & Answers] siddharthk02:
I am unable to reset moto g9. It says Not Valid OS cannot be found. The device will not boot. What should I do??
[Moto G9 Play Questions & Answers] rayid mohammad:
moto g9 xt2083-3 blankflash
[General Questions and Answers] tidan38:
hi, how is the combination of iem shure se846 headphones with the earmen sparrow usb dac?
[OnePlus 7T Pro (Regular & McLaren) Q & A] antonello66:
Salve, volevo chiedervi informazioni.

Ho un OP 7 T Pro Mclaren Edition, volevo installare Android 12 sarebbe possibile? Ho già sbloccato il BL, grazie.
[OnePlus 7T Pro (Regular & McLaren) Q & A] seadersn:
switch to english pls
[OnePlus 7T Pro (Regular & McLaren) Q & A] orb3000:
We use English as the preferred language in the forums, you can always use google translate.
[Galaxy Note 4 Q&A, Help & Troubleshooting] EvgeniyDragunov:
Hey guys can someone please point me to latest STOCK rom that i can flash with TWRP?

Thx.
[Galaxy Note 4 Q&A, Help & Troubleshooting] flairepathos.info:
Hi

you just need to get stock firmware file

get(extract) the system.img

copy to phone/sdcard

flash with twrp to system

if that fails flash the system image only in bootloader(fastboot)

or the firmware flasher(system.img only)
[Xiaomi Mi 10 Ultra Questions & Answers] Marcohome:
I can't connect the T-mobile network by Mi10 Ultra. This is the first time I brought thIs Phone to US. There's no signal at all when I put the SIM card into my Phone. Did anyone solve this issue before? I've actived the VoLTE and VoWIFI button in this ROM, which's the native Chinese MIUI ROM 12.5. Appreciate any expert in this forum is able to help me on this. I saw some people said in this forum they're able to connect T-mobile with no problem. Aslo attached the phone screen copy for reference.
[Xiaomi Mi 10 Ultra Questions & Answers] Marcohome:
I am in Boston downtown so Tmobile network should be very good.
[Xiaomi Mi 10 Ultra Questions & Answers] inasense:
Wish I could be of more help but I also have Mi 10 Ultra on stock CN rom and using T-Mobile's network in Western Pennsylvania without issue. I literally turned the phone off, put the sim in, turned on, and received signal.
[Xiaomi Mi 10 Ultra Questions & Answers] Marcohome:
Thank you @inasense . Did anyone has my experience and did something effectively to fix it?
[General Questions and Answers] natsupasu:
Today I updated my OPPO A53 [CPH2127] and everything works just fine.

but after I restart the device, the refresh rate become 60hz even the 90hz option is turned on. The only one thing that rendered at 90hz is lockscreen.

Is there any solution to this problem?
[General Questions and Answers] tiwry6:
I have a way, you just load setedit 4x
[Xiaomi Mi 10T / 10T Pro Questions & Answers] rajatapaus00:
I would really like to try xiaomi.eu on mi 10T, but it needs open boot loader, which can be detected, and then all app's don't work.

Yes I know you can use magisk and have an eternal battle with safety net while some apps still refuse to work (Mcdonalds is a good example).