yashsingh1/xdaforums huggingface dataset:
[Google Pixel Questions & Answers] badabing2003:
You can try Android Flash tool or PixelFlasher

Is wipe an option?

If yes then choose force.

If you use PixelFlasher, you can generate a support file and I can take a look.

With PF enable advanced settings and choose the following options.

View attachment 5943987
[Google Pixel Questions & Answers] roirraW "edor" ehT:
Android Flash Tool requires USB Debugging to be enabled, doesn't it?
[Google Pixel Questions & Answers] badabing2003:
Yes it does, and I missed that statement in OP. But I see that he was able to do fastboot operations so USB debugging must be enabled.

We need some clarity about the device.
[Google Pixel Questions & Answers] V0latyle:
Factory flash didn't work, I suspect there's something going on other than software
[Google Pixel Questions & Answers] Kurt Von Nugget:
fastboot flash bootloader --slot=all bootloader-sailfish-8996-012001-1908071822.img completed successfully, but device still bootloops.

Didn’t bother trying fastboot erase data, as it doesn’t sound like you think it would make any difference, but if anybody feels strongly that I should go ahead and try it anyway, please let me know.

I was trying to avoid that, of course, but if every non-wipe method I try fails anyway, I might as well be open to it. For now, I was going to try your PixelFlasher with support file suggestion, but what’s the difference between PixelFlasher.exe and PixelFlasher_Win_2019.exe?
[Google Pixel Questions & Answers] roirraW "edor" ehT:
Actually, does the Android Flash tool even work with the Pixel 1? I vaguely recall attempting to unsuccessfully use it with one of my spare old Pixel 1s (that still work fine - I just wanted to flash stock with it), but also the view full list link at https://flash.android.com/welcome says (TL;DR - Pixel 2 and newer):

Not trying to kick a dead horse. :)
[Google Pixel Questions & Answers] badabing2003:
Try PixelFlasher without wipe and Force options, see if it makes a difference

Then you can provide support file and we can check to see if there is anything obvious.

Keep Wipe and Force options as a last resort.

You're flashing bootloader only, with PF you should flash full factory, in case other partitions are corrupt.

The difference between the two versions is that 2019 works on Windows 7, which is built with Python 3.8 (latest supported Python on Windows 7)

If you're on a newer OS, just use PixelFlasher.exe
[Google Pixel Questions & Answers] V0latyle:
At this point you may as well.

Where are you seeing this?

Don't believe so, I don't think it even worked on my Pixel 2
[Google Pixel Questions & Answers] badabing2003:
Release Release v5.3.3.0 · badabing2005/PixelFlasher

#79 Bug-fix: Package Manager column stays unsorted when filtered. Warn users that extract the contents of firmware and use the image inside as firmware, which is no good. Warn users of Android Plat...

github.com
[Google Pixel Questions & Answers] V0latyle:
He already flashed the factory image, it didn't make a difference.

I think there's something wrong with the flash device. All the partitions are contained on the same memory chip; the partitions are divided by address, so if the first partition is 32k, it's from 0x0000 to 0x7FFF

So, it's possible that there's a "bad" memory address that's somewhere in the space that's occupied by the /boot partition. This means it probably writes fine, but the boot image fails verification when loading so the device recycles to bootloader.

Just a guess
[Google Pixel Questions & Answers] roirraW "edor" ehT:
Except for the radio.img, since they haven't used the flash-all.bat or specifically flashed the radio. For what it's worth - not that I expect that to make any difference.

Is it worth switching slots and then using the flash-all.bat (with or without the -w)/PixelFlasher? Edit: In case one slot's slightly bad, and the other isn't?
[Google Pixel Questions & Answers] badabing2003:
That is why I suggest flash both slots, full image.

That will assure that everything is flashed, and if anything goes wrong during flashing, we'll see it in the logs and hopefully that would be helpful.
[Google Pixel Questions & Answers] Kurt Von Nugget:
PixelFlasher wants me to select the Pixel Phone Factory Image, but NOT any specific file extracted from a ZIP, so I selected the file “Android.10.0.0.Sailfish.QP1A.191005.007.A3.2019-12 - sailfish-qp1a.191005.007.a3-factory-d4552659.zip” that I downloaded and had PixelFlasher process it, but PixelFlasher complains:

So I went back into that extracted ZIP, which contains both “image-sailfish-qp1a.191005.007.a3.zip” and “bootloader-sailfish-8996-012001-1908071822.img”. When I have PixelFlasher process “image-sailfish-qp1a.191005.007.a3.zip”, I get this system dialog:

I clicked on OK, and it presented “image-sailfish” as an available boot image. I’ve selected that, and PixelFlasher’s console box displays:

As you probably know, “boot.img” is a file within “image-sailfish-qp1a.191005.007.a3.zip”.

I’m confused: “boot.img” is a valid bootloader, but “bootloader-sailfish-8996-012001-1908071822.img” is not?

EDIT/Update:

I had saved the file as custom name “Android.10.0.0.Sailfish.QP1A.191005.007.A3.2019-12 - sailfish-qp1a.191005.007.a3-factory-d4552659.zip”, but just tried it again as originally named “sailfish-qp1a.191005.007.a3-factory-d4552659.zip”, and that worked, but still only offers me “boot.img” for selection after processing. I’m given to understand that “boot.img” is a kernel, not a bootloader. But, again:

I don’t see any way to select a bootloader rather than “boot.img”. Please advise.
[Google Pixel Questions & Answers] badabing2003:
Where did you get a factory file named liked that?

Or did you rename it yourself?

The filename should be: sailfish-qp1a.191005.007.a3-factory-d4552659.zip

Leave the file intact, don't unzip it, don't rename it, just download it and point PF to it.

The filename convention Google uses is consistent across their devices and PF uses that to extract device mode, expected checksum ...

If you rename the file, then PF won't be able to do it's job.

If you extract the contents, and feed the image, then it won't have all the necessary files.

Just download and point to it.
[Google Pixel Questions & Answers] Kurt Von Nugget:
Guilty as charged. Please see bottom of my previous post:

I’m in the habit of giving custom names to practically everything I download, but for software, I generally keep the original filename at the end of my customized name, just in case it turns out to be important. Obviously, in this case, it did, but that possibility didn’t occur to me until after my first attempt to utilize PixelFlasher. Also, for all of my preceding attempts to follow V0latyle’s suggestions, the name of the outer zip file didn’t matter.

In any case, I’m still confused about your directive “You’re flashing bootloader only”, versus PixelFlasher only offering the file “boot.img” for selection, and not the file within the zip that actually has “bootloader” as part of its name.

I do appreciate your (and V0latyle’s) bearing with me, though. Thanks.
[Google Pixel Questions & Answers] badabing2003:
Check in my signature for links to PixelFlasher thread and Github, both links describe the steps required to flash the factory image.

Why do you want to select the bootloader?

After processing the firmware, select the boot that it listed.

then select the following options

(first try without wipe and force)

If that does not work, second try with wipe and force

Then hit Flash Pixel Phone button
[Google Pixel Questions & Answers] Kurt Von Nugget:
Because you specifically wrote “You’re flashing bootloader only”, and I knew there was a file within the zip named “bootloader-sailfish-8996-012001-1908071822.img”.

Anyway, both flashes (with and without WIPE and FORCE) completed. Alas, more bootlooping followed each operation. See attached logs.

Attached: “2023-07-02 09;50;57 - PixelFlasher - FA68T0303468 Google Pixel Flashes.zip” (5,408)

Contents:

“2023-07-02 09;50;57 - PixelFlasher - FA68T0303468 Google Pixel Flashes\”

“2023-07-02 09;32;55 - PixelFlasher - FA68T0303468 Google Pixel Flash [No Wipe].txt” (8,659)

“2023-07-02 09;50;57 - PixelFlasher - FA68T0303468 Google Pixel Flash [Wipe+Force].txt” (14,813)
[Google Pixel Questions & Answers] badabing2003:
I said that because I saw that you were flashing bootloader only and needed to flash full factory.

I didn't say to repeat that, in any case

Please click on the big support button and generate a support file from PF and provide that.

you can also do it from the help menu.
[Google Pixel Questions & Answers] Kurt Von Nugget:
Sorry about that!

Attached: “support_2023-07-02_11-10-49.zip” (26,246)
[Google Pixel Questions & Answers] badabing2003:
Nothing obvious is showing up, I'm beginning to think that what @V0latyle said about memory might be true.

There's two more things you could try.

1- Download this twrp.

and issue the following command

fastboot boot twrp-3.2.3-1-sailfish.img

If you manage to get into twrp then do this

From within TWRP format data

Download the full OTA image for your device from here.

From within TWRP sideload the downloaded image adb sideload sailfish-ota-qp1a.191005.007.a3-394b5899.zip

2- Not sure if it would help, but can definitely try.

Even though we flashed both slots, I want to make sure we attempt to boot to both slots, but for that to be possible you need to remove the system_other.img

In PF click on right of "Open Folder" icon (the second one, it should open an explorer in the directory where it unpacked the zip.

Double click on image-sailfish-qp1a.191005.007.a3.zip file, and you should see something like this

select and delete system_other.img

save the zip (keep the same name)

Repeat the wipe + force option.

when done, and PF detects your phone (probably in bootloader mode) pay attention what slot it reports.

Then click on the Set Active Slot button to change to the alternate slot.

rescan the device

See if it switches to the other slot.

Hopefully one of the two fixes your issue, otherwise I might have to raise the white flag :(
[Google Pixel Questions & Answers] Kurt Von Nugget:
Both processes completed. Sadly, neither one put the kabosh on subsequent bootlooping. Second one did indeed appear to have been successful in switching slots (was B before the switching sequence > switch > bootlooped until forced off > back into bootloader mode [if that’s what Volume Down + Power is] > reconnected to computer > PF then indicated slot A).

I guess that’s it, huh. Well, many thanks to you and @V0latyle for trying, anyway. I feel like my Pixel’s whole life is flashing before my eyes. (Pun intended.)
[Google Pixel Questions & Answers] badabing2003:
So you were able to get into twrp? and achieve sideload?

Sorry to hear that it still did not work 😥

If you are able to get into twrp, you might want to try flashing LineageOS

Who knows, you might get lucky, I know it's a hail marry but you have nothing to lose by trying.
[Google Pixel Questions & Answers] Kurt Von Nugget:
Sorry for not being specific enough about what was completed, but no such luck. After doing fastboot boot twrp-3.2.3-1-sailfish.img, it was just another bowl of bootloops. All I could do was force it off and try the second suggestion.
[Google Pixel Questions & Answers] badabing2003:
Ah,

Sorry for your misfortune, perhaps an excuse to upgrade your phone.
[Google Pixel Questions & Answers] V0latyle:
At this point I'm beginning to think it's something else. If my theory about a bad memory address was correct, he'd still be able to live boot an image. But, there's no error message given when the bootloader recycles. I've never played with an OG Pixel so I'm not sure what normal behaviour is but it almost seems like the bootloader thinks it's doing what it's supposed to be doing, but whatever it's doing isn't happening. Bad RAM maybe?

F for your Pixel, @Kurt Von Nugget
[Google Pixel Questions & Answers] badabing2003:
Could it also be that the bootloader is not jumping correctly to the correct boot address because the cells that the address is written to are worn and messed up?
[Google Pixel Questions & Answers] V0latyle:
Possibly. But I'm with you on upgrading. Time for something new
[Google Pixel Questions & Answers] Kurt Von Nugget:
But that Pixel and I have been through so much together in the past month and a half, and I thought for sure our time with each other would be longer! :-)
[Google Pixel Questions & Answers] V0latyle:
I feel it brother. I felt the same way when my laptop died after upgrading the GPU. Then my car threw a rod. In both cases I just fixed them... But phones are a lot cheaper and also harder to repair.

My recommendation: Get a refurbished Pixel 5 or 5a. I love my 5, it's now 3 years old. I had the battery replaced a few days ago but other than that I have had zero problems.
[Google Pixel Questions & Answers] Kurt Von Nugget:
Thanks, I’ll keep that in mind. Gonna go somewhere and check things out today, but I actually have Verizon’s insurance on all devices on our plan, so I’m guessing my options will be limited if I go that route.
[Google Pixel Questions & Answers] V0latyle:
Well, in that case you can take it to a uBreakiFix and tell them that it won't boot and the battery is worn out. They'll replace the mainboard (which means your data will be gone), the real cost of the whole job is somewhere in the $500 range so make sure you check your deductible if you have one
[Google Pixel Questions & Answers] Kurt Von Nugget:
Huh. I hadn’t heard of them, but a quick web search tells me that uBreakiFix was acquired a few years ago by Asurion, which is the name of a business with a nearby physical location that I’ve been directed to by my local Wireless Zone/Verizon. In fact, uBreakiFix’s web site lists a local address for themselves that’s actually the same as the one printed on the Asurion business card I was given.

Oh, I figure it’s already gone, what with all the wiping and forcing I did yesterday.
[Google Pixel Questions & Answers] V0latyle:
Yeah, Asurion bought the company

True
[Android Software/Hacking General [Developers Only]] lunar.gg:
Android FRP REMOVAL using ADB

Please note that this has only been tested on a Samsung Galaxy A04s as i dont have any other Android devices to test it on.

This assumes you have already enabled ADB Debugging (maybe using the dialer method)

Reset phone via recovery mode

Continue through setup until you get to the FRP screen

Run these ADB commands:

adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1

Select to login with the Google Account

Create a Google account instead of logging in

Follow the rest of the setup

Profit

I will be honest and say, i dont 100% know how and why this works, but i have a general idea:

The ADB commands will tell the system that the user has already completed all the setup steps

and when you log in or in this case register the Google account, it will check for those values, see that the setup has already been completed, and therefore not check / validate if the logged in Google account is the same as the one before it.

But in my case i was able to bypass the factory reset protection using this method. Do let me know if this method works for you, so we can establish if its Samsung specific, or if its version specific.

Update (Completely removing FRP instead of just bypassing it)​

You can completely remove it by following these steps:

Download and open SamFW (sketchy tool, i know. But it gets the job done).

Locate and click the button with blue text that says "Remove FRP (Security from August 2022 to December 2022)".

Note: This step will not disable FRP, as its outdated, but it can be used to enable USB Debugging.

Open the dialer on your device and enter *#0*# (or a similar code).

Wait for the device to attempt enabling ADB. It may not work immediately, so be patient and try a few times.

Eventually, a dialog will appear on your device asking if you want to allow USB Debugging. Accept this prompt.

Run the ADB commands provided above.

Instead of going through the device's setup normally, simply reboot the device.

Once the device has rebooted, navigate to Settings > About Phone > Reset > Factory Data Reset.

Perform a full factory data reset on your device.

After the reset is complete, your FRP will be removed, and the device will be restored to its original state.

Dont be afraid to ask if you have any other questions :)

~ Lunar
[Android Software/Hacking General [Developers Only]] V0latyle:
To be clear, it doesn't sound like this removes FRP, just bypasses it.

However, since you've been able to add a new account, see if you can remove all accounts then perform a factory reset and see if the FRP screen comes up again.
[Android Software/Hacking General [Developers Only]] lunar.gg:
It does remove it, i took some more time to research it, and was able to remove it completely on multiple different devices (a04s & a20e)

You can completely remove it by following these steps:

Download and open SamFW (sketchy tool, i know. But it gets the job done).

Locate and click the button with blue text that says "Remove FRP (Security from August 2022 to December 2022)".

Note: This step will not disable FRP, as its outdated, but it can be used to enable USB Debugging.

Open the dialer on your device and enter *#0*# (or a similar code).

Wait for the device to attempt enabling ADB. It may not work immediately, so be patient and try a few times.

Eventually, a dialog will appear on your device asking if you want to allow USB Debugging. Accept this prompt.

Run the ADB commands provided in my original post.

Instead of going through the device's setup normally, simply reboot the device.

Once the device has rebooted, navigate to Settings > About Phone > Reset > Factory Data Reset.

Perform a full factory data reset on your device.

After the reset is complete, your FRP will be removed, and the device will be restored to its original state.
[Android Software/Hacking General [Developers Only]] vst555:
SAMSUNG NOTE 20 Android 13 not working
[Android Software/Hacking General [Developers Only]] TechX1991:
This shouldn't work in 99.9% of cases, because you can't enable USB Debugging while in setup/while a device knows its FRP.

With SamFW, I've been successful, but you have to enable debugging before anything in original post
[Android Software/Hacking General [Developers Only]] mvikrant97:
https://xdaforums.com/t/samsung-galaxy-frp-unlock-thread.4596293/page-7#post-88753163
[Android Software/Hacking General [Developers Only]] vst555:
Samsung NOTE20 Android 13 FRP NOT Working , because SamFW testmode FRP . NOTE 20 USB debugging not enable
[Android Software/Hacking General [Developers Only]] thomasvtt:
This is for all the late comers here. This is a post I have found which is working and helpful on FRP bypass; https://www.samsungsfour.com/tutori...ock-on-samsung-galaxy-android-smartphone.html
[Android Software/Hacking General [Developers Only]] nan4:
Are any of those methods possible using only an old Linux machine or a tablet with Android 8.1.0?

Since this thread is so old I posted that question as a new thread in the same forum and a mod deleted it so I'm bumping this old thread instead.
[Android Software/Hacking General [Developers Only]] nan4:
I have a newer phone and it's already locked from trying the Talkback method, so only the first and last methods on that site might work.

The first, Unlock Go, installs in WINE on Linux Mint with the Windows version set properly but when the app is launched WINE gives an error dialog saying the program "encountered a serious error and needs to close." It says this could be a problem with the program or WINE. I haven't researched it further yet.

The last method is FRP Hijacker by Hagard. It appears to install properly via WINE but when launched immediately closes with no error message. That's probably just a glitch but I've seen trojans that behaved like that so I'm keeping the laptop offline for now.

Suggestions on getting either of these to work, or another method to try?
[Android Software/Hacking General [Developers Only]] Fieldo:
It took some hours to figure out, but you are a ****ing legend. I was able to access my old phone with this. Thank you SO MUCH!
[Android Software/Hacking General [Developers Only]] nan4:
right on. which method worked for you?

I'm stuck waiting until I can borrow a windows computer to try UnlockGo and FRP Hijacker.
[Android Software/Hacking General [Developers Only]] Fieldo:
I enabled ADB with the android utility tool and then I simply followed the main instructions of this post and I was able to create a google account at the login screen. My main problem was that I couldn't use ADB with the phone, so I had to enable it through my computer.
[Android Software/Hacking General [Developers Only]] rommerguy123:
Guys I have a trekstor surftab breeze 10.1 quad plus (android 5.1) nd I found out how to enter google on setup but you can't install anything, so

Important step: connect to a wifi

1 open the keyboard

2 hold the comma button or at button and press the settings

3 press google keyboard settings

4 in the settings press the three dots and about google keyboard

5 press privacy policy

6 after a page pops up press the google logo

7 do what you want
[Android Software/Hacking General [Developers Only]] miketaylor888:
Hi there,

I'm currently dealing with FRP issues on my device and I'm exploring different methods to bypass it. Your method seems promising, but I'm also curious about the vnROM Bypass.From your experience, which method do you think would be easier for someone like me to try out?
[Android Software/Hacking General [Developers Only]] nan4:
how is an APK supposed to help remove FRP? It can't be installed on a locked device, in my experience. Your post seems like spam and I wouldn't click the link.
[Android Software/Hacking General [Developers Only]] miketaylor888:
I understand your point. I'm also looking for a solution. Someone mentioned vnROM and addROM to me, which got me thinking about different methods.

If anyone has more information or suggestions, I'd appreciate it!
[Android Software/Hacking General [Developers Only]] miketaylor888:
and I think there's an option mentioned on a website where you can install the APK using an OTG cable and a USB drive. It sounds like it might work, but I haven't tried it myself yet.
[Android Software/Hacking General [Developers Only]] blackhawk:
Use methods found here or on the internet.

To avoid this in the future write down your Google account* name/password. Make sure that info is correct.

Before a factory reset delete your Google account and do the reset from settings rather than recovery. Otherwise you may have to take the long way home...

* same for Samsung etc accounts.
[Android Software/Hacking General [Developers Only]] lehmancurtis:
Frp bypass
[General Topics] speedo:
I am now using coreplayer 1.3.0. However, when I use the diamond skin for 1.2.5 in 1.3.0, i cannot type things in youtube search bar.

Anyone has the diamond skin which operate successfully in 1.3.0?
[Xiaomi 11T] ChokDK:
Hi.

Just bought a used Xiaomi 11T 5G, thatworks great in all ways except speaker volumen.

I've searched through posts about volumen here, but couldn't find any of the subject.

Audio (music) is loud, using Bluetooth is okay, but when calling and using speakers the volumen is way to low.

I've tried what I could find on the internet, from "use a toothbrush" over div settings to change location to USA + reboot.

Nothing seems to help.

The eq settings are not doing any difference for speaker calls.

I was about to try to use the 14.0.4 ROM last night, but suddently that version was available by update! :)

No difference at all :(

Any version, ROM, tweak, mod or whatever I can do to bring life into the speakers?

Sorry in advance if this is not the right place to post :unsure:

(Totally noob about this.. sorry)