yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] swieder711:
I know that you tried to get into Fastboot. Pixel 6/6P also has a Recovery mode. I can get to it from a working phone.

I would think that there is someway to boot into Recovery mode from a dead phone via button combos.
[Google Pixel 6 Pro] vrda08:
Hy, how did you flashed? Via adb sideload or?
[Google Pixel 6 Pro] Thibale:
factory image with modified flash-all.bat

I'll do the exact same process when I'll get my phone back but this time I'll check the image name at least 3 times :)
[Google Pixel 6 Pro] Thibale:
Unfortunately not, I've tried every possible combinaison / timing

I'm convinced there is a way to boot from usb or to switch to a rescue mode or something but probably only with Google proprietary toolkit
[Google Pixel 6 Pro] 96carboard:
Just because it has two bootloader slots doesn't mean that you can switch between them if the currently active slot is completely borked. Unfortunately, you wrote a qualcomm bootloader to an exynos device.
[Google Pixel 6 Pro] Gilbot:
ugh my pixel is stuck in some mode with the screen off and button combos won't reboot it.

Any help is appreciated.

I botched the January update trying to fastboot install it. It rebooted to an error at bootup " Your device is corrupted and can't be trusted". I tried powering it on and it went to a google logo then went black. The phone is on, because I can hear the audible sound my pc makes when i plug it in, but no button combos will reboot it. The Android flash tool cannot find it either. -__-

Suggestions?

I'm Considering letting the battery die so i can charge and power it on.

EDIT: So it turns out the phone is in Rom Recovery mode. Still can't get the android flash tool to recognize it nor can i get it to reboot properly with button combos. Shows up as Rom Recovery Mode.
[Google Pixel 6 Pro] Morgrain:
What exactly did you do to "botch" it? Did you also install the wrong Bootloader? (Snapdragon vs Exynos?)
[Google Pixel 6 Pro] wolfeyes30:
January update did the same to me. Black screen for a long time but I kept the power and volume key down pressed for a very long time and fastbootd appear and had to factory reset. Then it booted up.

Edit: it might have been power and volume up key.
[Google Pixel 6 Pro] DanielF50:
The only thing I can suggest regarding no display output is unplugging the device & holding the power button down for ~30 seconds to 1 minute to see if it will reboot to anything. If that doesn't work at all then the only thing you can do is wait for it to completely die & see if you get any display when you plug it in a later date.

Have you tried right clicking on "backup" in device manager and installing the USB drivers from Google? I've never heard of "Rom Recovery Mode", but if you can get the display back & it shows the standard recovery mode (like this), you should be able to sideload the January OTA file from here and boot as normal.

As far as I'm aware, AFT will only recognise a device in fastboot mode & the new "Pixel Repair" website doesn't support the Pixel 6/Pro yet, so unfortunately that won't be of much use.

Edit: regarding OP's issue: I'm surprised that it allowed you to flash the wrong bootloader at all. Normally, if you attempt to flash images between devices (or the right images to the wrong partitions) it usually rejects the image & the bootloader should absolutely have this type of protection.
[Google Pixel 6 Pro] Azerox:
I would defo try booting it in bootloader with both ways, vol up and down.

It might boot but not show any signs of it.

Then try some command in fastboot to see if it reacts.

If it does boot (without signs) your PC should recognize something.

If that does not work then yea you're screwed.
[Google Pixel 6 Pro] Gilbot:
Ok, so the "backup" is unrelated to the pixel, you can ignore that.

I didn't do anything i haven't done with previous pixels. I did have magisk installed. I disabled all modules, tried to OTA the update, but it would fail. So I downloaded the january update, rebooted to fastboot install it, knowingly wiping the device completely and starting fresh. Everything looked fine, then it rebooted to the "Your Device is Corrupt" message and booted to a google logo. I tried force rebooting with power+volume up and the screen went black into this mode.

Gonna let it die and see if it will power on as no button combo does anything
[Google Pixel 6 Pro] Thibale:
Yes I was very surprised as well there was not even a basic device check prior flashing the bootloader. The script flash the bootloader right away without asking for confirmation even if the device is not the right one.
[Google Pixel 6 Pro] Aquariuslt:
My P69 bricks in same issue after April OTA (with magisk rooted).

The "Pixel ROM Recovery" shows in Mac Devices

Any suggestions or document about it?
[Google Pixel 6 Pro] cultofluna:
Unfortunately if you've flashed wrong bootloader you're done ...

RMA is the only option
[Google Pixel 6 Pro] roirraW "edor" ehT:
Official Google Android Flash Tool

(OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)

I can attest that it solved many folks' issues where nothing else helped over the last five months.
[Google Pixel 6 Pro] Aquariuslt:
I have tried, but adb cannot detect any devices
[Google Pixel 6 Pro] roirraW "edor" ehT:
What variant of the Pixel 6 Pro do you have? Is it factory unlocked? Is it from a carrier? When it was still working, had you enabled "OEM unlocking" in Developer Options? If OEM unlocking isn't already enabled before it bricked, then this method won't work.

Otherwise, if it is enabled, try:

Reboot the computer. Try different USB ports. Try the cable that came with the phone, or try some other cables.

Got any access to a Windows PC to try all these things?
[Google Pixel 6 Pro] Aquariuslt:
What variant of the Pixel 6 Pro do you have?

- US 12GB + 256GB Black

Is it factory unlocked?

- Yes, I have rooted via magisk before

Is it from a carrier?

- No

When it was still working, had you enabled "OEM unlocking" in Developer Options?

- Yes

Reboot the computer. Try different USB ports. Try the cable that came with the phone, or try some other cables.

- All tried before (using different USB cabale from P6P P4XL and others)

Got any access to a Windows PC to try all these things?

- There no Windows PC in my workspace, I will try install bootcamp windows on my mac and try these operations again
[Google Pixel 6 Pro] Aquariuslt:
Use my college's Windows PC and try all these steps.

Still can not detect devices.

confirms that Android Studio / Android SDK / Google USB Driver installed
[Google Pixel 6 Pro] roirraW "edor" ehT:
Very strange. Still try a different cable with that PC too? The Platform Tools and USB driver are up to date?
[Google Pixel 6 Pro] Aquariuslt:
Will try with other PC and port later.

Confirmed that platforms tools is latest 33
[Google Pixel 6 Pro] roirraW "edor" ehT:
By the way, I should've asked sooner, when you said this originally, are you saying you bricked it the same way as the OP in this thread (flashing an image for the wrong Pixel)? If not, what exactly happens? If you did do the same thing - you flashed the image for the wrong Pixel, then there's probably nothing you can do other than RMA it, and try to get it covered under warranty.

SDK Platform Tools latest version is 33.0.1 - just in case it makes a difference from 33.0.0.
[Google Pixel 6 Pro] Aquariuslt:
will double confirm platform version.

for wrong image, I can confirm all the boot.img/magisk updated boot.img all for P6P raven. (1% might using wrong update version for raven devices, e.g. march boot.img with april update?, i will check bash history later..)
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm not positive I understand, but it sounds like you did not flash an image for the wrong phone. Using a mix of partitions from different months' updates shouldn't keep you from fixing the device, so if you can detail as much as possible what steps you took that ended with your device "bricked", it might be helpful.
[Google Pixel 6 Pro] Aquariuslt:
checking my bash history after today
[Google Pixel 6 Pro] roirraW "edor" ehT:
If you look at the contents of the flash-all.sh file that comes in the full firmware zip, normally the bootloader (not boot) is flashed first:

if ! [ $($(which fastboot) --version | grep "version" | cut -c18-23 | sed 's/\.//g' ) -ge 3103 ]; then
echo "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
exit 1
fi
fastboot flash bootloader bootloader-raven-slider-1.1-8167057.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-raven-g5123b-97927-220225-b-8226700.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-raven-sp2a.220405.004.zip

(commonly, you should remove the -w from the last line so it doesn't wipe your phone)

Of course, I don't know if you already had done that, nor why you were doing things the way you were, or what you were trying to accomplish, but knowing the why and what isn't necessarily going to help the situation, so I'll ignore those for now. :)

Had you already performed the bootloader update process, and rebooted it into the new bootloader?
[Touch Pro, Fuze General] WDawn:
Possible fix for "broken glass" issue and "white noise screen" issue.

I've been plagued by the broken glass screen and the white noise issue as long as I've been using TF3D. When i shut it off, everything runs perfect. On the other hand, TF3D looks very nice. So I've been looking for a solution to have the nice looks and a reliable device.

Last week I installed Memmaid (this is unfortunately not free), in the tab "quick cleaner" I check all the options and autorun it every night.

Since then i've not had once, the broken glass screen, the white noise screen or an device not waking up. I've been running this for 10 days now. Before I had these problems almost on daily basis when running TF3D. Nothing else has changed in my configuration.

I'm running the DCS 1.5 ROM.

I don't know if there is any free software that does the same thing as Memmaid but if somebody knows another option it would be great to share.

Anyway, I can now say that even with TF3D enabled, the device is very stable.

Hope this helps.
[Touch Pro, Fuze General] topspeclt:
Whe I first bought the device I got 'broken screen' effect two times. When I loaded on my apps and customised Tf3D (with my music library etc) the 'broken screen' has never happened again.

Thankfully,
[Amazfit] e1thx:
Hello

I have the amazfit gtr 47mm. When I start training via the application, the current training is not displayed on the watch face. Watch connected to the official app. Someone might be able to advise something, thank you.
[General Topics] Cyndaquissshhh:
Why do you need to update your emojis? Read here!

How to update your emojis​

Method 1: Build your Magisk module via Emoji Replacer [RECOMMENDED]​

With this method, you will build your Magisk module. It is not as complex as it sounds—it only takes a few minutes. Note that you may need a regularly updated keyboard such as Gboard or Microsoft SwiftKey to be able to use these emojis.

Part 1: Download the latest Noto Color Emoji​

1. Go to this link. That always points to the latest Noto Emoji release from Google's GitHub repository. Then download the .zip or .tar.gz archive. This will take time since the files are somewhat large.

💡Tip: You can download this file instead. When you do, you can skip step 2. Be careful since that points to the NotoColorEmoji.ttf file straight from the repository, so it may be unstable or experimental.

. Get the NotoColorEmoji.ttf file from the archive. It is inside the fonts folder. Then place it somewhere you'll remember.

Part 2: Use the Emoji Replacer app​

Install the Emoji Replacer app by @RickyBush_.

Tap on the Settings icon on the top right of the screen then check the "Install a custom emoji .ttf file" option.

Go back to the main menu and tap on the folder icon.

Select the NotoColorEmoji.ttf file and tap OK.

Tap "Create a Magisk module".

Wait for it to finish then tap "Flash this module".

Reboot after it has finished flashing.

ENJOY!​
[General Topics] xabu:
Nice lesson. Thank you.
[General Topics] KingUsman:
Is there anyway you could upload the new iOS emoji file to zfont?
[General Topics] bigPAL:
Hello. Can I use a different font other than default when I create an emoji font?
[Lenovo P11] Nexgan:
Hello,

I've recently bought a Lenovo P11 tablet to take notes. When drawing with a pen, however, I have this problem (and I have verified it by enabling touch detector in developer options): when I lay the pen/finger on the screen, there is an area (I would say 2-3 cm) where the cursor doesn't move even if I move the pen. When I exit that area, a line gets drawn between where I started and where I arrived, but this is wrong as I may have drawn curves in the middle of the two.

This leads to two things:

* When I want to draw something rounded (like a "2"), the upper part gets drawn as a line unless I draw it very big.

* When I want to draw something small, only a dot gets drawn because I didn't leave the "area" and therefore didn't trigger the cursor.

Now I am pretty sure this is a software problem, as if it were a problem with the screen this wouldn't happen only at the start of the line.

Also, I'm sure this is not because of the application I'm using (OneNote), as I've tested with the developer options to show the cursor and in any place in the OS, when I start drawing, the cursor is stuck at where I've begun.

Anyone can help?

Thanks.
[Lenovo P11] otanger:
was it a solution?
[HTC Wings] stopfen:
Hi,

I tried different (stereo)-headsets from motorola and jabra. The transmitted audio is not very loud, I tried the headsets with a bluetooth-connection to my windos-XP and it was much louder.

Is there any setting that sets the transmitted volume?

The volume button doesn't seem to affect the bluetooth volume, only the normal speaker and headphone.
[HTC Wings] nielswillems:
Pocket Tunes volume booster

Hello,

Do you know pockettunes?

It's a nice prog with A2DP & AVRCP support.

And for you.... a volume booster :) up to 15db.

Not always perfect sound, sometimes a little scratchy, not disturbing.

I hope attachment will do it.

I have problems with uploading

[EDIT: ok, no attachment, sorry.. tou can search google for a torrent with the file ''Pocket Tunes 4.1 for Windows Mobile.zip'']
[HTC Wings] stopfen:
Ha!

Thanks so far! Now the music part can be solved.

But how can I do that with phone calls?
[Samsung Galaxy S21 FE] flipp0:
More or less all android phones during the past year have used 20:9. For me, who do not like super tall phones it is nice that Samsung chose a slightly wider aspect ratio on this phone (same as iphone). Most tech sites (including gsm-arena list the wrong aspect ratio 20:9, 2400x1080).
[Samsung Galaxy S21 FE] flipp0:
Am I the only one who note the 19.5:9 aspect ratio?

Almost all tech sites claim 20:9 and 1080x2400. I have asked several people who own S21 FE to check and they all confirm 1080x2340.

GSM-arena still show 20:9;

Samsung Galaxy S21 FE 5G - Full phone specifications

www.gsmarena.com

Dxomark recently made the same mistake:

Samsung Galaxy S21 FE 5G (Snapdragon) Display review: Good video rendering

The Samsung Galaxy S21 FE 5G display’s rendering of still and moving content is good in indoor and outdoor conditions, DXOMARK tests show.

www.dxomark.com
[Samsung Galaxy S21 FE] Ugglaimossen:
Yesterday I was at the local store and grabbed all phones to have a feel about this. I also like wide phones. My current phone, the Mate 10, is 78mm wide! Fantastic! (16:9 screen, like the LG G4 I had before).

Have long waited for something to suit me. But now this S21 FE is not bad at all. In fact, considering the weight and spec I think it looked so good so I ordered one :)

Did a table here with body ratios in case someone are interested. I think the Iphones have good ratio but they have one big problem, they are Iphones.

View attachment 5539665
[Samsung Galaxy S21 FE] nanolitho:
You're not alone. I'm not a fan of a tall, skinny phone.
[Samsung Galaxy S21 FE] nanolitho:
Ha, we must be related. Ordered an FE just for this reason. Coming from a Mate 10 Pro, and before that an LG G4.
[Android Q&A, Help & Troubleshooting] Realokman:
Please, let me know the valid source , those actually work. not fake. please.
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
@Realokman

Prior to your next posting please read the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

I've moved the thread to Q&A.

Regards

Oswald Boelcke

Senior Moderator
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
@Realokman If a game requires you to pay for it, please do so. Thread has been closed!

XDA Forum Rules (excerpt):

Regards

Oswald Boelcke

Senior Moderator
[Touch Diamond, MDA Compact IV General] milillicuti:
Hello.

I have small problem, but it is making me crasy ...

I can't get the email tab back !

I use Advanced Config, which doesn't do anything when i add this tab.

And the email tab is not available in Diamond TF3D config ...

Please can someone help me ?

Thank you so much ...
[Touch Diamond, MDA Compact IV General] milillicuti:
a little UP ... :)
[Touch Diamond, MDA Compact IV General] milillicuti:
I found the solution : just use the Restore function (appearance tab) of Diamond TF3D config.
[General Questions and Answers] khalidhotaky:
Hi all,

i have updated to latest date android 9 with binary 5. previously i was on binary 2. Now i want to go back to that version of my firmware which had binary version 2 of bootloader. I don't care about my bootloader as i know it can't be downgraded back. I just want to use my previous build firmware with current bootloader. Is that possible ? if yes how can i do that ? What if i extract my old system.img.lz4 file from AP and make it odin flashable and flash it through odin while in download mode ? will i brick my device or not ? pleas advice how can i go back to my previous build of firmware. My phone is Samsung galaxy A6 (SM-A600T).
[General Questions and Answers] Droidriven:
Bootloader binary version is not the only binary version that you need to be concerned with. If the binary version of your currently installed system is higher than the binary version of the system binary in the binary 2 firmware, you will not be able to downgrade the system partition.

Your question can be resolved with these simple questions:

1) What is the System binary version of your currently installed system? Boot into download mode and look at your S binary version.

2) What is the System binary version of the firmware that you want to downgrade to?

3) Is the System binary version of the firmware that you want to grade to lower than or equal to your currently installed System binary? If it is lower than your currently installed firmware you can't downgrade, if it is equal to your currently installed firmware then you can downgrade.
[General Questions and Answers] khalidhotaky:
Thank you for your great reply, to answer your question and solve my query i really need your help. the below answers regarding your questions may help you answer me with right solutions.

1. Currently Booted to download mode and found that RP SWREV: B:5 K:5 S:5

2. I EXACTLY DON'T KNOW, but you can find i think from my old firmware's name as it is A600TUVS2BSG1_A600TTMB2BSG1_TMB

3. I think after seeing the above two answers, you may be able to solve your third question by yourself as i am not able to answer you about this one.

let me know if you need any addiontal information, i really want to solve my query and downgrade back to my old firmware, I was able to to downgrade to android 8 with same version of bootloader v5 binary and was hoping that i could be able to upgrade back to my earler PIE, but later i knew that i wasn't able to do so, and that android 8 was a combination firmware which made me happy just for a small period of time.

Regards.
[General Questions and Answers] Droidriven:
No, you can't flash a binary 2 firmware, your currently installed binary shows that you can only flash a binary 5 or higher firmware. You will not be able to downgrade to the previous version, there is no way to bypass the binary block and there are no tricks to force it to downgrade. You are stuck with what you have, whether you like it or not.
[General Questions and Answers] khalidhotaky:
Thanks from your help, it was so sad to hear that. By the way I am thinking why the system should be the same binary version ? This rule was just added for bootloader I think, and now you are adding also this rule for firmware binary. What's the exact story here. We must be able to downgrade to our old firmwares except bootloader.
[General Questions and Answers] khalidhotaky:
Also can you please give your advise if the info on below link is valid or not, Is him lying?

https://xdaforums.com/t/downgrade-from-pie-to-oreo.3920731/
[General Questions and Answers] Droidriven:
No, bootloader is not the only binary that matters. There is bootloader binary, kernel binary and system binary. Your currently installed firmware has a bootloader binary 5, kernel binary 5 and system binary 5. This means that you can only flash a firmware that has a bootloader binary 5 or higher but not 4, 3, 2 or 1, or a kernel binary 5 or higher but not 4, 3, 2 or 1 and a system binary 5 other higher but not 4, 3, 2 or 1.

In the cases where users have successfully "downgraded" their firmware were not truly downgrading their firmware, they were flashing a firmware that has a lower android version but not a lower binary. For example, they could have an android 10 firmware with 4 binary installed and "downgrade" to an android 9 firmware that also has a 4 binary. In this case they are not "downgrading" the binary version, they are only downgrading the android version. If their currently installed firmware were android 10 with binary 5, they would not be able to downgrade to android 9 with binary 4.

Also, the link you posted is using TWRP to flash a Pie ROM. They are not using Odin to flash a downgraded firmware. They are flashing a custom file that was created to be flashed via TWRP, similar to flashing a custom ROM, this is not the same as flashing a stock firmware via Odin. This would only be useful to you if your bootloader is unlocked and if there is a TWRP for your device and if there is a downgraded firmware for your device that has been modified to be flashed via TWRP. Odin prevents flashing files with a lower binary, TWRP does not, TWRP will let you flash anything that is made specifically for your device and some things that were not made specifically for your device.

There are specific details involved in this that you just aren't understanding. I'm done trying to explain.
[General Questions and Answers] khalidhotaky:
Your replies has already made me understand every truth that I was not getting from reading too many articles and on internet forums, you are a really great personality, thanks from your great help and replies. You explained everything very well and after your explanations I am also done with problem. So sad from knowing these rules now. Hope I understood these things before my upgrade. Some people won't get clever like me until first they make a mistake and then know what have they done, anyways it's just not my fault. 50% is Samsung rules blamed for stuff like this. Shame on them for applying these rules on their users. If my phone kept the battery drain issue like this, I will sold it and will switch to iPhone after 17 years of android use. Thanks again mate for your great help.

Regards.
[General Questions and Answers] ioeg41:
Samsung's downgrade lock is a humiliation to users. Destroying the device's battery consumption is a mockery of the user's intelligence or an abandonment of Samsung's reputation.
[General Questions and Answers] ze7zez:
Your statement will not change anything. Accept that the economy is structured to increase sales and profits.