yashsingh1/xdaforums huggingface dataset:
[Redmi Note 10 Pro] appendicitis:
View attachment 5958399

does anyone know what the name of that MIUI icon? I tried to hide it with system UI tuner but doesn't have any luck and currently playing with SetEdit to manually editing the icon_blacklist but since I don't know what the Xiaomi named those icon, I can't hide it.

so far I've been trying to use elem_bat, elem_wifi, etc. but with no luck, please if someone knows the what Xiaomi named the icon share it with me.
[HTC Tornado] man01:
I'm using "Plain Jane" Windows mobile 6.1 updated June 11 2008

The Color scheme's available to me are

1. Grey

2. Text black

3. Text white

4. Default

I want a blue or even a black color scheme, but I don't know if I need software or if I download a cab file.

found solution: Go to Modaco and search for color schemes.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] Zeepachi:
Hi! I can't seem to find the designated forum for Samsung Galaxy A03 so I'll be just asking here.

I recently flashed a stock rom on my device using Odin, but unfortunately after flash the phone is not turning on. Odin status was marked PASSED, didn't tick any other boxes except the default Auto Reboot and F. Factory Time.

Troubleshoot I did:

1. Used volume down and power, but nothing happened.

2. Connected usb chord to PC but it won't detect the phone.

3. Disconnected the battery, but still the phone still won't turn on.

Is there a way to fix this? Thanks for the help!
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] V0latyle:
Are you sure you flashed the correct firmware? If you tried to flash firmware for another model number, i.e. A035F on a A035M, you probably bricked your device.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] Zeepachi:
Yes, the firmware is correct.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] SubwayChamp:
Did you check that the bootloader unlock OEM toggle was enabled?

Are you sure that you flashed the right firmware for it?

Which CSC did you flash?

What about trying volume up + PWR buttons, trying to get recovery?

What about trying to send it again to download mode, and flash the same firmware version or a newer one?
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] Zeepachi:
Yes, I already unlocked the OEM on my phone. I flashed the correct firmware. What do you mean which CSC? I flashed the stocked CSC. I can't go to recovery and download mode.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] SubwayChamp:
Which procedure did you use to unlock bootloader?, if the bootloader was not really unlocked, then you´ll be limited for some operations, even, the OEM unlock toggle, has to remain in the enabled position, on every reboot, this means, that even the critical partitions were really unlocked, and ready to write to.

Usually/typically, you´ll find two CSC files inside the firmware, the non-HOME file make clear some settings, otherwise, device, can refuse to boot.

Use the three buttons for 10 seconds, then try, pressing the volume up button + PWR till some screen appears. If it doesn´t work, you may need the battery to drain completely, this is depending, if you really, flashed the right firmware, and/or, bootloader was allowed to do it.
[Philips, Sony, TCL Android TV] Marcyvee:
Hi guys. I want to root an old TCL 43UC6406, also know as percee tv or Thomson. It has MT85 chassis, and I've updated yesterday to the last V8-T658T01-LF1V602 firmware (oreo).

Looking on the web, I saw that on 4pda (a Russian forum) there was a lot of work around these models, such as pre rooted firmware, twrp or tools for install Magisk or SU, but every download link are death.

I can use ADB over WiFi, but not with USB cable since I updated to V602. When I was on v570 I was able to recognize my device from pc connected through USB, and reboot it into fastboot mode. Also fastboot was working, but after tried to boot a patched boot.img I get a boot loop, and I flash the v602 img update.

Do you know how to restore adb and fastboot? Because I think ADB over WiFi won't work in fastboot mode. Maybe I just miss some driver, but it's strange, because as I said, with v570 everything works.

So, what I wish to do now is dump the boot.img from the tv, patched it with Magisk and try to boot it from fastboot mode, but I don't know how to dump it. I have the last firmware, but I don't know how to extract it from a .pkg file.

Can anyone help me?

Obviously, the easiest way to root it is find that tools developed by the 4pda users, such as TLC_studio_3.rar or Root_TWRP_TCL_P60.exe

I also have an unofficial recovery, but 4pda says to not install it until the device is rooted.

That's the source on 4pda of all the stuff.

TCL P6046 Series [Android] - 4PDA

TCL P6046 Series [Android], [Телевизор][4K]

4pda.to

Thanks in advance.

I also have a light v574 and a stock v575 where to pick the boot.img, but I think to flash a different version is not a good idea.

Maybe could I also downgrade with the V575 OTA? and then patch that boot.img?
[Philips, Sony, TCL Android TV] Vladarius:
Hi Marcyvee, I am stuck on the same problem. Have you found any solution in the meantime?
[Shadow General] Viper Matrix Wireless:
T-Mobile Shadow

I need to get ahold of something that turns english into arabic but I have no idea where to look, does any know of anything?
[Shadow General] neosofts:
you will need a working version of smart arabizer..

still cant find one .. if i get somthing ill tell u..
[Realme GT 2 Pro] mitriemin:
go to another thread
[Realme GT 2 Pro] Oswald Boelcke:
@entrvan

I've remoevd the link from your above post. 4pda is not only another phone related website (and not at all affiliated with xda-developers) but also well known for the distribution of malware and warez. Links or references to 4pda and support for issues with that website are not accepted on XDA at all.

XDA Forum Rules (excerpt):

Please refrain from sharing links or references to 4pda in future.

Additionally, I suggest to consider to combine this thread with your other RUI related one:

https://xdaforums.com/t/rui-app-management.4607561/

This would much more follow the guidance on the XDA Forum Rules you're certainly aware about:

Please advise if you like support to merge both threads.

Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Realme GT 2 Pro] N3XUS9:
I did it and now my phone temperature increased without using it. I think we need to optimize this list as you are still removing essential services. Or at least, that's the sensation it gives to me.
[Realme GT 2 Pro] ZG_DEV:
Bookmarked.

thanks for this guide (:
[Realme GT 2 Pro] mitriemin:
I updated guide.
[Realme GT 2 Pro] legendebrune:
Works perfectly, thanks Entrvan

If use a relife 071 a like I did, it is way easier to get a successful test if you press gently but firmly the device against the sensor
[Realme GT 2 Pro] Sib64:
Thread closed as request from @mitriemin
[Realme GT 2 Pro] mitriemin:
Realme support promose open servers for global users before August.

Proof

What happend?

On realme forum write about close servers [25 May and later week promose open]. But for global users [IN region] servers dont work. First time servers work, but no give permission for unlock. In Jule servers closed and i`m checking status.

UPD. 31/08/22 | realme opened server 1 August, then close.

Deep Test don't work on global
[Realme GT 2 Pro] mitriemin:
I got tired of waiting and unlocked the bootloader via CN region
[Realme GT 2 Pro] Bozkurt_59:
B çok kötü bir şey
[Realme GT 2 Pro] yogurt321:
How do you change the region?
[Realme GT 2 Pro] Stano36:
What region do you have and what would you like to switch to?
[Realme GT 2 Pro] Bofahad:
Go CH unlock bootloader then back to IN
[Realme GT 2 Pro] yogurt321:
I have the ID region, maybe I will switch to the CN region, but mine is Realme 5 Pro
[Realme GT 2 Pro] Stano36:
Indonesia could have bootloader unlock option.
[Realme GT 2 Pro] yogurt321:
Alright, I will give it a try. thank you
[Realme GT 2 Pro] yogurt321:
Mine is stuck at "submitted for review" and it's been several days. Can you help me?
[Realme GT 2 Pro] Stano36:
Maybe they have a lot of applications, the approval time is up to 10 days.

Spoiler content hidden.
[Realme GT 2 Pro] yogurt321:
woah thank u so much for the information, sir
[Realme GT 2 Pro] KrakenIV:
How can I update to chines version from Europe a11? Because I'm stuck on Android 11
[Realme GT 2 Pro] mitriemin:
Guys, deep test dont work on global. I think unlock close for IN
[Redmi K20 / Xiaomi Mi 9T ROMs, Kernels, Recoveries] oOIPaBoIOo:
Sending 'cust' (0 KB)

FAILED (remote: 'Error: Last flash failed : Invalid Parameter')

fastboot: error: Command failed

wipe img and consequently twrp dont work. twrp reports several billion bytes as internal storage and is not writeable.
[Google Pixel 6 Pro] fillwithjoy1:
Hello! I attempted to install the Kirisakura kernel (raviantah 1.1.2) and my phone was last updated to June. I think I bricked my phone as it's completely stuck on the G icon loading screen when booting up. When I booted it into fastboot mode, adb console shows nothing and flash.android.com is unable to push an update through here. However if it's in rescue mode, adb detects it and I can send commands, but it doesn't show up at all in fastboot mode.
[Google Pixel 6 Pro] V0latyle:
If your phone is displaying the Google logo, the kernel has started to load, therefore the device is not hard bricked.

Reboot to bootloader and use ADB to flash the factory boot image.
[Google Pixel 6 Pro] fillwithjoy1:
That's where it all falls down. In fastboot mode, it is unable to see the device in ADB. Somehow flash.android.com can see it, but it is too unable to fetch the latest builds and trying to flash the build flashes an error. However if the phone is not in fastboot mode, adb can see it. Really unsure what to do

View attachment 5958755
[Google Pixel 6 Pro] fil3s:
You could sideload the ota. Here's more info.

Rescue mode?

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

developers.google.com
[Google Pixel 6 Pro] V0latyle:
Do you know how to use ADB platform tools via command line?

All you should need to do is flash the stock boot image. Reboot your phone to bootloader, connect to PC, and in ADB command line use fastboot flash boot <path to boot image>

If you need more information check the How To guides for this device
[Google Pixel 6 Pro] fillwithjoy1:
View attachment 5958761

But it isn't coming up on adb when I set it to fastboot mode :(
[Google Pixel 6 Pro] fillwithjoy1:
Looks like a possible solution, but I want to try to save the data before going with this solution
[Google Pixel 6 Pro] fil3s:
It shouldn't wipe data.
[Google Pixel 6 Pro] fillwithjoy1:
oh ok! I thought it would wipe the data, but I guess I can do that. Thank you so much!!
[Google Pixel 6 Pro] TechX1991:
if you're in the bootloader, same place you flashed the kernel originally, you shouldn't be using adb, but fastboot.

fastboot devices

this is the same as adb devices, but for fastboot

if it isn't detected, open device manager, and see if its just hanging out as an unknown device and install the Google Driver for Bootloader Interface.
[Google Pixel 6 Pro] fillwithjoy1:
Just a quick question, I have the June build installed. Can I sideload the newest build (July)?
[Google Pixel 6 Pro] fil3s:
Yeah. Get the latest build. It's all good
[Google Pixel 6 Pro] fillwithjoy1:
Thing is, I installed the Google USB driver and flash.android.com works, but this time it's just not appearing as a device

It's existing in my windows device manager here below

View attachment 5958771
[Google Pixel 6 Pro] V0latyle:
I think we need to clarify which mode is which

ADB, the Android Debug Bridge, can be used to describe the interface between PC and phone, but this actually consists of two parts:

adb.exe is used to interface with a running kernel such as recovery or system, and cannot see the device in bootloader/fastboot mode

fastboot.exe is used to interface with a device in bootloader mode and cannot see the device while in recovery or system.

Bootloader mode looks like this

View attachment 5958773

In this mode, the device should appear to ADB with the command fastboot devices, where you are instructing fastboot.exe to show connected devices in bootloader mode.

Recovery mode, if you don't enter the key combo, looks like this

View attachment 5958775

If you hold Power and click Volume Up, you'll get this screen

View attachment 5958777

In recovery mode, the device will appear to ADB using the command adb devices, where you are instructing adb.exe to show devices connected in ADB mode (recovery or system kernel)

It's important to know which mode you're actually in.

Reboot your device to bootloader by holding Volume Down and Power until the phone reboots, you should come to the bootloader screen shown above.

Plug it into your computer and make sure ADB sees it with fastboot devices

Report back and we'll go from there
[Google Pixel 6 Pro] fillwithjoy1:
Hello! Yes I am trying to get the computer to see it in bootloader mode, but it's not showing as this adb screenshot shows me trying to set it to bootloader mode, only for it to not get picked up by adb.
[Google Pixel 6 Pro] V0latyle:
You have to use the fastboot command, not ADB. Read my post again.
[Google Pixel 6 Pro] fillwithjoy1:
right.... i really just thought that i didn't need to read all that 🥶🥶. Thank you. Can I flash the Raviantah 1.0.2 kernel?
[Google Pixel 6 Pro] V0latyle:
There's a reason why I provided the information. We deal with this almost every day, and the most common problem by far is users who don't completely understand what they're doing or how to fix it because they didn't read all the instructions.

It was apparent to me that this might be the issue, so I was trying to make sure we are on the same page before moving forward.

Let's cross that bridge when we get to it. You've rebooted to bootloader and fastboot sees your device, correct? Did you do anything else?
[Google Pixel 6 Pro] fillwithjoy1:
Yes fastboot, sees my device

View attachment 5958829
[Google Pixel 6 Pro] TechX1991:
download the OTA instead of the fastboot firmware, and try via recovery with adb sideload? select apply update with adb

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

developers.google.com
[Google Pixel 6 Pro] fillwithjoy1:
It's getting recognised by fastboot, so everything is working normally. Just needed a refresher on what's adb and fastboot 😅
[Google Pixel 6 Pro] V0latyle:
Let's do one person at a time please so that he doesn't get confused.

@fillwithjoy1 Do you know what update you were on when your phone stopped working? If so, go here and download the zip that corresponds to the build that you're on.

Extract that zip, and inside it you'll see a bootloader image, a radio image, a couple scripts, and another zip for the system update. Unzip that file, you'll see a boot.img inside. Keep that window open for the time being.

Go back to your command window and type fastboot flash boot, leave a space after "boot", and drag the boot.img you've just extracted into the command window to populate the path. Hit enter, it should flash successfully.

Then, type fastboot continue to boot to Android.
[Google Pixel 6 Pro] fillwithjoy1:
Alright so I downloaded the zip, what do I do next?
[Google Pixel 6 Pro] V0latyle:
I edited my post.

Now you need to extract the boot image from it and flash it in fastboot. See the instructions in my post. If you are unsure about anything, ask before you go further.
[Google Pixel 6 Pro] TechX1991:
power hungry much... just trying to help because I've had this happen too and stated how i fixed it.
[Google Pixel 6 Pro] V0latyle:
Not being power hungry, I just don't want to confuse him with conflicting instructions. It's up to him whose help he wants
[Google Pixel 6 Pro] fillwithjoy1:
uhhhhhh, is there a way to check the actual OS version (just wanting to double check)?
[Google Pixel 6 Pro] V0latyle:
Not in bootloader mode unfortunately but it shouldn't matter that much. Do you remember the last time you updated?
[Google Pixel 6 Pro] fillwithjoy1:
I do know the phone had the june security update but I installed it on the may update.
[Google Pixel 6 Pro] Lughnasadh:
You flashed the kernel version for July. Since you are on the June build you want to flash 1.1.0.

Also, if you want to return to stock kernel you need to flash the stock versions of boot.img, dtbo.img, vendor_boot.img, vbmeta.img and vendor_dlkm.img since these images are all modified when flashing a custom kernel. If you had verity and verification disabled, there's no need to flash vbmeta.img.

Ok, I'll let you guys carry on...

EDIT: All get flashed in fastboot except for vendor_dlkm, which gets flashed in fastbootd. If you did have verity and verification disabled and for whatever reason you do decide to flash the stock vbmeta.img, just know you'll have to wipe. But as I said above, no need to flash that image if you had those flags disabled.
[Google Pixel 6 Pro] simplepinoi177:
glad you got it working...

As @V0latyle said (I'll be paraphrasing), please take your time and read & study thoroughly and make sure you understand what is going on and what you are doing -- especially when flashing custom kernels & any other kind of custom.

Also, @V0latyle, you should post a link to your thread on the difference between "hard" brick and "soft" brick; this most definitely was not a "hard" brick...so OP and others that might come across this might get a better understanding & clarification....
[Google Pixel 6 Pro] V0latyle:
It actually sounds like you might be more knowledgeable about this since I've never used a custom kernel with Pixels, so feel free to jump in
[Google Pixel 6 Pro] Lughnasadh:
Honestly, I would just have him update to the July firmware (unless there's a reason they want to be on June) to get everything back to stock and be up-to-date (keep data of course) and then flash the kernel again (correct version this time 🙃).

Also they should make sure they read the whole OP of the kernel thread before flashing.

I have to leave in a few minutes anyway...
[Google Pixel 6 Pro] fillwithjoy1:
Is it alright if right now in fastboot, I flash the 1.1.0 kernel?
[Google Pixel 6 Pro] Lughnasadh:
You don't flash the custom kernel in fastboot. Please read the OP of the kernel thread so you know the instructions.
[Google Pixel 6 Pro] fillwithjoy1:
Alright I did that, but now it's stuck on the Google logo and then restarting in a loop...
[Google Pixel 6 Pro] simplepinoi177:
EDIT: minutes too late....OP now bootlooping...

Oh man...OP seriously is looking like it's setting up to brick....at this point, how much benefit are you going to get from a custom kernel and/or do you fully understand & comprehend why?

Please, we implore you @fillwithjoy1,

take your time

. There's no rush. Read, then read again.... I suggest you read the whole process and each step at least 4 times (coming from the impression you give in this thread...). It really is just as me and V0latyle said;
[Google Pixel 6 Pro] fillwithjoy1:
Should I use adb sideload method instead?
[Google Pixel 6 Pro] simplepinoi177:
Did you flash the .zip from the Google Developer's site that was the Full Factory image, or did you attempt to flash the kernel (as I am afraid but suspect you did because of this quoted post

P.S.

seriously fillwithjoy1, slow down....! you are making things worse rushing....
[Google Pixel 6 Pro] V0latyle:
Like @Lughnasadh said, you have to follow the kernel instructions. I know how to recover using the factory firmware but if you want to install a custom kernel that's outside of my wheelhouse.

Since you were trying to install a custom kernel, if you wanted to return to stock to get the phone working again, the best option would probably be to sideload the OTA package like @TechX1991 suggested, because it'll automatically overwrite all the partitions that may have been changed. It won't wipe your data and is in fact generally the safest way to update. Let me know if you need instructions on how to do that.
[Google Pixel 6 Pro] fillwithjoy1:
Alright I'll do that (do I sideload May or June?)
[Google Pixel 6 Pro] simplepinoi177:
Based off of what @Lughnasadh said (quoted below), I would sideload July as you were initially flashing "the kernel version for July" (so you already have it) and it seems you intend to do again once your system is up and running right....that would be the update version you would want installed/established
[Google Pixel 6 Pro] fillwithjoy1:
Alright I'll try that then, thanks!
[Google Pixel 6 Pro] V0latyle:
You can't sideload updates older than what you already have, just FYI. The OTA package checks the currently installed version, and if it's newer than what you're trying to install, the update will fail.
[Google Pixel 6 Pro] fillwithjoy1:
Success! Got it working, but Magisk root got removed.

Alright so I attempted to remove dm-verity using the verity file from factory images, but then my phone gets stuck on Google and then black screen, bootlooping.

Now I am able to recover using adb sideload, but everytime I try to remove dm-verity, my phone bootloops. What can I do?
[Google Pixel 6 Pro] V0latyle:
You shouldn't need to remove dm-verity unless you're installing a custom kernel. I don't mess with it so I can't be of much help here.
[Google Pixel 6 Pro] Lughnasadh:
You don't need to disable verity and verification on the Pixel 6 series, even when flashing a custom kernel. That only applies to the Pixel 7 series. What is the reason you are trying to disable those flags?
[Google Pixel 6 Pro] fillwithjoy1:
Sorry for bothering you, but I tried to install the patched boot.img which also caused a bootloop. I did flash the entire phone with June firmware completely, so I'm unsure what to do now.
[Google Pixel 6 Pro] fillwithjoy1:
I thought I needed to, for installing the Kirisakura kernel
[Google Pixel 6 Pro] Lughnasadh:
It doesn't say to do that in the instructions/requirements in the kernel thread.
[Google Pixel 6 Pro] fillwithjoy1:
Alright I get you. By the way I cannot get my phone rooted, do you have any idea how to help? Thank you!
[Google Pixel 6 Pro] Lughnasadh:
Use Platform Tools 33.0.3

Extract the boot.img from your current firmware

Patch the boot.img in Magisk (Magisk Stable 26.1 would probably be best to use)

Place the patched boot image in your Platform Tools folder and open up a command prompt from that folder

Go into fastboot mode (adb reboot bootloader) and flash the patched boot.img

fastboot flash boot <nameofpatchedbootimage>

There are several "How To" threads in this forum as well. I suggest you take a look at those.
[Google Pixel 6 Pro] fillwithjoy1:
I did follow all these steps like usual, but then my phone gets stuck on the Google logo and black screens (looping)
[Google Pixel 6 Pro] simplepinoi177:
alright....since you want to barrel through and not take your time, I think it's time to point you to PixelFlasher, it has checks and protocols to make sure things are correct and you are doing things correctly and in order....

you seem to have all the pertinent tools required (platform tools 33.0.3, firmware image, magisk), that tool should get you rooted without bootlooping. You can even use it to flash the image to re-establish your system first...

First, get your system right in the way you did before with fastboot flashing the flash-all...
[Google Pixel 6 Pro] Lughnasadh:
Make sure you don't have any Magisk mods that may be causing it.
[Google Pixel 6 Pro] ThatAndroidGuy207:
I have run into this same exact issue, try just logging out of your Google account. If that does not work switch to a different chromium browser and try it again.
[Google Pixel 6 Pro] fillwithjoy1:
It wasn't an issue to do with the browser, I forgot I'm supposed to use the "fastboot" commands instead of typing "adb" 🤦
[Google Pixel 6 Pro] fillwithjoy1:
Not sure what was the issue, but I patched the wrong boot image, which caused some errors 🤦
[Google Pixel 6 Pro] amaroney55:
So why did all this different ways of flashing came about??? Like when I first started fastboot was the only way you was supposed to flash rom. Then the custom recovery way now sideloading. Dang just flashing a rom is getting more like Treble changes day by day it seems