yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] craigacgomez:
If you want to re-lock the bootloader, you need to have a completely stock ROM or have a ROM with a custom avb key flashed. Anything else will show the error you noted.

You should be able to solve this by flashing the stock OTA in recovery mode.
[Google Pixel 7 Pro] dimm0k:
I can get into the bootloader, however here I'm seeing the message that the bootloader is already locked! tried flashing the November update, but getting the failed message that I need to be unlocked

when I try to get to recovery mode through the bootloader, it immediately spits me back out to the message that there's no valid operating system and to press the power button to power off
[Google Pixel 7 Pro] AmyClaraRose:
Seems like you messed up and bricked your device try seeing if you can unlock your bootloader still if not contact whoever you got device off and report for warranty
[Google Pixel 7 Pro] NippleSauce:
FYI, the bootloader is one of the functional recovery modes.
[Google Pixel 7 Pro] Beefheart:
Try the online Google flash tool. This is what I used to flash back to stock after unrooting my device to run some tests. Although in my case, as you're meant to, I performed the flash prior to re-locking the bootloader, so it might not work for you.

Android Flash Tool

flash.android.com
[Google Pixel 7 Pro] dimm0k:
unfortunately that was a no go for me as well... tells me I need to unlock to perform any of the functions

that said, any possibility the guys at Ubreakifix would be able to get this fixed?
[Google Pixel 7 Pro] Beefheart:
Unlikely. This now needs a logic board swap I suspect. You can't unlock the bootloader as you toggled the OEM switch in developer options then relocked the bootloader before flashing stock, you can't boot to Android to untoggle that switch to allow another fastboot unlock command because you have a non-stock image installed with a locked bootloader, and you can't flash back to stock.

Sorry to say, your phone appears to be bricked.
[Google Pixel 7 Pro] Beefheart:
Send it back for a warranty swap. The bootloader is listed as being locked, so unless they delve deeper, it's not obvious the end-user is at fault rather than the device simply refusing to boot one day for no apparent reason.
[Google Pixel 7 Pro] dimm0k:
should I try sending it back for a warranty swap or would sending it into Google for repairs not be a good idea?
[Google Pixel 7 Pro] Beefheart:
Did you buy it direct from Google? If so that could be an issue, as they're likely going to try to diagnose the fault prior to sending out a replacement, and will discover it's caused by you before refusing a replacement. Where as if you bought it from some a third party vender, they will likely just swap it without any in depth checks.
[Google Pixel 7 Pro] dimm0k:
I purchased this from Amazon when they had the $200 Amazon GC offer... they're allowing me to return the phone, but if I were to buy it again from them it would be at full price. for some reason they are not allowing exchanges/replacement. that said, I was exploring if it would be worth sending to Google for a repair... when you say they in the last sentence, are you referring to Google or the third party vendor?
[Google Pixel 7 Pro] Beefheart:
That's their policy. I bought a Logitech MX Keys for £65 in a UK deal about 10 months ago. When it developed a fault, they offered me a full refund but point blank refused an exchange for a new keyboard, which annoyed me no end as it had gone up to £105 at that point. But it can work the other way around too and you can be the one with the money in your pocket. I've had that happen too.
[Google Pixel 7 Pro] dimm0k:
damn, that is rather disappointing! that said and from your response, I guess it's better to go and return to Amazon then...
[Google Pixel 7 Pro] schmeggy929:
The question is, can you use the GC when you purchase another phone?
[Google Pixel 7 Pro] dimm0k:
unfortunately Amazon thought of abuse this way and priced it so that the device was $200 less from the get-go and charging $200 for the GC
[Google Pixel 7 Pro] Gerr1:
Doesn’t matter what they say, if the device is in warranty, just write them that the device is damaged. They must replace it.
[Google Pixel 7 Pro] jorvind:
Hello! I'm sorry I am pretty confused right now, I installed the November OTA update after uninstalling all Magisk modules, but forgot to disable Magisk Hide. Here are the steps I've taken to try to get root back on my phone:

1. Went to Google's website

2. Downloaded the Factory image for this version of update

3. Extracted the boot.img file and patched it with Magisk 25.2 (25200) (33)

4. Sent back to computer, and opened adb

4. Used "adb reboot bootloader"

5. Tried both "fastboot boot (the patched img)", and "fastboot flash boot (the patched img)"

I got the message

Sending 'boot_a' (65536 KB) OKAY [ 0.412s]

Writing 'boot_a' OKAY [ 0.090s]

Finished. Total time: 0.506s

None of these options seemed to work after the phone restarted however, I tried using the hidden Magisk and it told me to reinstall the app, so I deleted it and reinstalled it from the Magisk github. However, it's still showing "Installed N/A" in Magisk. I'm not sure what to do, may I please have some help haha-

My steps taken on installing the OTA update:

1. Removed Magisk modules (but forgot to turn off Magisk hide!)

2. Tried clicking Uninstall in Magisk and "Restore Image" but was hit with the error ""stock image does not exist."

3. Flashed original boot.img file using FKM (Franco Kernel Manager)

4. Used Direct Install in Magisk and rebooted phone

5. Still had error "stock image does not exist."

6. Downloaded the OTA image from Google

7. Changed the name to OTA.zip and placed into platform-tools

8. Connected phone and opened ADB

9. "adb fastboot recovery"

10. "adb sideload OTA.zip"

11. confirmed that the update worked in phone settings

btw, these are some additional information about my phone

Pixel 7 Pro, updating from Android 13 October Update to Android 13 November Update
[Google Pixel 7 Pro] Lughnasadh:
To root the Pixel 7 series you need to patch the init_boot.img, not the boot.img.

fastboot flash init_boot <nameofpatchedinit_boot.img>
[Google Pixel 7 Pro] jorvind:
Ohhh thank you so much! Nothing else changes right? and it wont reset my phone or anything right
[Google Pixel 7 Pro] Lughnasadh:
That's the only difference from earlier Pixels when rooting. It won't reset your phone.

If you want to use a custom kernel you will have to disable verity and verification, which will cause you to wipe your phone if doing it for the first time.
[Google Pixel 7 Pro] jorvind:
Ohh thank you so much! I just did it, confirmed it worked! :DD
[Samsung Galaxy S22 Ultra] Brixster:
I want to use the international version of the S22 Ultra, and after comparing the bands in the phone with the AT&T network I'm on, the phone seems to have all the same 5G bands and every 4GLTE band except 14, 29, 30.

I live in a fairly populated city in the northeast that is fully 5G enabled, and want to know whether my signal strength or speed would be negatively affected because of the missing LTE bands?

Part of what I'm confused about is whether this LTE deficiency is even an issue as long as I'm connected to a 5G tower and getting the 5G signal? Also, from what I've read, it seems that these missing bands are not the ones primarily used by AT& T, but rather for carrier aggregation, though I'm not sure what means!

I could really use some help and advice on this from you guys. Thanks!
[Samsung Galaxy S22 Ultra] ze7zez:
Identical bandwidth is not enough. The transmission protocols are also different. AT&T is the Another World.
[Samsung Galaxy S22 Ultra] Brixster:
Could you please elaborate and explain? The regular US version of the S22 Ultra obviously works fine on the AT&T network. The international version roams fine on the AT&T network. Samsung is not building such diverse variants of the same model that they wouldn't work everywhere, right?
[Android Q&A, Help & Troubleshooting] charlene17:
Hi,

Needing dark theme because of eyesight I've discovered theme park and found it very helpfull with one caveat at least, I can't change folder background color. I'm also using nova launcher but none of the 2 seems to do a thing.

Any idea ?

Thanks.
[Android Q&A, Help & Troubleshooting] blackhawk:
What model and OS version?
[Android Q&A, Help & Troubleshooting] charlene17:
It's a S10+ android 12 one UI 4.1
[Android Q&A, Help & Troubleshooting] blackhawk:
By folders you talking about these?

View attachment 5763303

I'm still running Android 9, One UI 1.5 I think there was another color individual folder option but it won't run on my version. Lol, I refuse to upgrade as Pie runs too good.

The Good Lock app updates tend to lag the OS OS upgrade releases. A quaint Samsung tradition🤣 If that's the case Samsung will... eventually... fix it.
[Redmi Note 8 Questions & Answers] shubh_n00b:
Whenever I connect mobile data or play a sound on the device speaker the phone just crashes and goes into bootloop and only turns on when I connect a charger. I first thought my battery was bad but without data connection it lasts as expected for 5-6 hours. I've also tried flashing multiple Roms but the problem persists. Does anybody have any idea what this issue is?
[Magisk] jorvind:
Hello! I'm sorry I am pretty confused right now, I installed the November OTA update after uninstalling all Magisk modules, but forgot to disable Magisk Hide. Here are the steps I've taken to try to get root back on my phone:

1. Went to Google's website

2. Downloaded the Factory image for this version of update

3. Extracted the boot.img file and patched it with Magisk 25.2 (25200) (33)

4. Sent back to computer, and opened adb

4. Used "adb reboot bootloader"

5. Tried both "fastboot boot (the patched img)", and "fastboot flash boot (the patched img)"

I got the message

Sending 'boot_a' (65536 KB) OKAY [ 0.412s]

Writing 'boot_a' OKAY [ 0.090s]

Finished. Total time: 0.506s

None of these options seemed to work after the phone restarted however, I tried using the hidden Magisk and it told me to reinstall the app, so I deleted it and reinstalled it from the Magisk github. However, it's still showing "Installed N/A" in Magisk. I'm not sure what to do, may I please have some help haha-

My steps taken on installing the OTA update:

1. Removed Magisk modules (but forgot to turn off Magisk hide!)

2. Tried clicking Uninstall in Magisk and "Restore Image" but was hit with the error ""stock image does not exist."

3. Flashed original boot.img file using FKM (Franco Kernel Manager)

4. Used Direct Install in Magisk and rebooted phone

5. Still had error "stock image does not exist."

6. Downloaded the OTA image from Google

7. Changed the name to OTA.zip and placed into platform-tools

8. Connected phone and opened ADB

9. "adb fastboot recovery"

10. "adb sideload OTA.zip"

11. confirmed that the update worked in phone settings

btw, these are some additional information about my phone

Pixel 7 Pro, updating from Android 13 October Update to Android 13 November Update
[Magisk] zee3are0:
Similar problem...

An OTA caused a loss of root (pixel 6 pro, unlocked). Tried to go into a hidden magisk and disable modules, but everything greyed out, unable to. Tried to uninstall the manager (I was using an old MagiskAlpha build), and thought it worked, though it must have left something behind. Updating wouldn't work - would give me a failure.

Flashed new factory image, installed new magisk manager, patched boot.img in new magisk manager, loaded boot.img, and I have root; adb shell su works, all my old apps that worked with root work, but no magisk manager recognizing that I have root - and therefore no modules - working. So, no charging management, safetynet is borked, no lsposed, etc. Have uninstalled/reinstalled mm numerous times. No luck. Tried loading it from adb (version right now was downloaded from topjohnwu's github directly onto phone, then I manually added the canary URL, and updated to canary. No luck.)

I've dug through adb shell pm list packages and can't find anything that looks like an old version of magisk at all anywhere anymore. I think I had three different versions on the phone, but they are all gone. No luck with a freshly installed manager. Still can't see root even though it's there. Any ideas?

Of note: I have a work profile and two users on the phone. However, I can't find anything even using --user for all three users. Only thing even close I see is com.lsposed.manager still installed. That shouldn't be a factor, but I can't think of anything at this point.

TB checker, under "check root" gives pass for everything except SU binary, 2nd SU binary, root via native, and magisk specific.

Under Check xposed, I have fail for dual/work profile and xprivacyLua, and com.topjohnwu.magisk under PM Sundry APIs. Everything else is Pass.

I had never granted TB checker root before; Termux on the other hand works fine with su (as does adb shell), and Root Essentials shows root fine.
[Magisk] zee3are0:
One other thing... /data/adb/magisk was dated; all the other directories in /data/adb were new, but magisk was from my last update of MagiskAlpha, and when I looked at util_functions.sh it was aligned to my old (uninstalled) magisk alpha build
[Xiaomi Redmi 5A Questions & Answers] FP__96:
I'm starting to get annoyed with this issue. Been trying to unlock my device but it keeps saying "Couldn't verify, please wait a minute or two and try again." I've already tried using a VPN changing the location to USA. As well as using my mobile data, enabling OEM unlock and USB debugging but still nothing is working! WHY!?
[Xiaomi Redmi 5A Questions & Answers] enjoy_life:
I had the same problem several days ago. You need to flash the developer ROM (Nougat) via EDL mode to be able to unlock the bootloader. And yes, you will need to disassemble the phone for that.
[Xiaomi Redmi 5A Questions & Answers] nitinule:
When it starts unlocking, after 30% remove the device.

it will go to 99% and stop.

Connect your device and your device will get unlocked
[G3 Q&A, Help & Troubleshooting] Sensei-:
So when I try to install TWRP (for Lineago OS) I was getting the "fastboot_init" screen and wasn't able to pass it. After some research I found out that my software may be the issue, so to turn the normal state of my phone I flashed this kdz file with LG Flash Tool 2014 in Download Mode.

After that, I booted. I was able to hear the constant starting song with black screen right after I saw the LG logo. After restarting the phone, I'm only able to see charging info and a red light when I plug a usb.

Notes:

- I tried to force restart with Power + Volume Up combination.

- First photo is not mine (shows the same thing)
[G3 Q&A, Help & Troubleshooting] Sensei-:
Problem solved. Try the keyword "soft bricked".

Note that you enter the download mode if you, unplug battery & USB and press Volume Up connect the usb that you attached it to a PC.
[Samsung Galaxy Tab S6 Questions & Answers] Sage:
Tab S6 Lite is on the list.. though haven't seen our beloved unit announced. :(

Anyone know anything?

Usually i am not that fussed as there is always Custom ROMs available to keep it up to date.. Though custom ROMS don't seem very common for this device!
[Samsung Galaxy Tab S6 Questions & Answers] Sage:
Android Authority says yes!

Here's every Samsung device eligible for four (or more) major Android updates

Samsung has listed all the Galaxy devices eligible for long-term Android OS updates, including flagships, tablets, foldables, and more.

www.androidauthority.com
[Google Pixel 7 Pro] J0nhy:
Anybody been able to get this working?

I tried it but to be honest i have no idea what to do lol

GitHub - ThomasKing2014/Pixel7_32bit_helper

Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] Lughnasadh:
Already a thread started pertaining to this subject here.
[Google Pixel 7 Pro] danw_oz:
yeah everyone...
[Samsung Galaxy S22 Ultra] ratchetrizzo:
Question, i've been reading that android 13 breaks sideloaded apps from other markets.

Last thread I read on said other market was about the pixels force closing all sideloaded apps and launchers.

Is this a problem on the tmobile S22U A13 update or should everything work like it did on 12? I have updates disabled through a package disabler just in case.

I also don't want to factory reset and reinstall things.

Just want to know if I bite the bullet and do the upgrade (if its there) will I have issues or will things still work without fiddling with individual permissions on apps.

My note 9 is still on A8 (cause it seems the updates for that phone break it so I left well enough alone)
[Samsung Galaxy S22 Ultra] ratchetrizzo:
nevermind, i upgraded and everything works and it's a lot faster and i got the november update too
[Samsung Galaxy Watch 4] jbenci:
I would find it useful to follow GPX files on my runs, I know the GW5 can do this, but since the hardware is almost identical, would it be possible to backport Samsung health from the 5 to 4? If not, are there any 3rd part apps with this functionality?
[Samsung Galaxy Watch 4] shiftr182:
I have the option on my GW4. View attachment 5763883
[Samsung Galaxy Watch 4] hoss_n2:
How did you get this
[Samsung Galaxy Watch 4] DaReDeViL:
To export :

In your phone's S-Health, go to history and open a session, click on the top right 3-dots menu, export to GPX

To import (works only for cycling):

Click on cycling exercise, choose route target, import gpx
[Samsung Galaxy Watch 4] wroublin:
Hi, sorry for excavating the topic - does it still work for you? On my GW5 (without pro) there's no option to open gpx route on watch - only works on the phone.
[Samsung Galaxy Watch 4] DaReDeViL:
Hi. Same on GW4 ...
[Realme 9i] JigSaaw:
Official Bootloader Unlock For Realme

realme Community

Welcome to realme Community, your virtual playground to learn the latest tech news, win exclusive prizes, or simply chat about realme!

c.realme.com
[Moto G Power (2021)] jazzybird2009:
how to remove a custom operating system from a Motorola g power (2021) phone?
[Moto G Power (2021)] sdembiske:
If you did a nandroid backup (e.g., TWRP etc.), do a full 'clean restore (i.e., wipe cache, Dalvik cache, system AND format data > Yes (important).

If not, do the same full wipe, reboot to fastboot and flash the stock rom. You could also try the Motorola "Rescue and Smart Assistant" but I'm not sure it will work in your particular case.
[Moto G Power (2021)] Deleted member 11919173:
If you want to go back to stock ROM or "OS" consider this method unofficial works on RETCA not sure about other devices, Verizon for sure needs its own software, The requirements of this method are Windows 10/11, Motorola's USB Drivers and a working Fastboot. Download the stock ROM from here https://mirrors.lolinet.com/firmware/motorola/borneo/ match the model of the device, Extract the firmware guessing it's in Downloads folder open that folder in the Terminal here's an example "cd C:\Users\smoke\Downloads" then here are commands to flash converted from the xml files

fastboot getvar max-sparse-size

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash vbmeta vbmeta.img

fastboot flash radio radio.img

fastboot flash bluetooth BTFM.bin

fastboot flash dsp dspso.bin

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash recovery recovery.img

fastboot flash super super.img_sparsechunk.0

fastboot flash super super.img_sparsechunk.1

fastboot flash super super.img_sparsechunk.2

fastboot flash super super.img_sparsechunk.3

fastboot flash super super.img_sparsechunk.4

fastboot flash super super.img_sparsechunk.5

fastboot flash super super.img_sparsechunk.6

fastboot flash super super.img_sparsechunk.7

fastboot flash super super.img_sparsechunk.8

fastboot flash super super.img_sparsechunk.9

fastboot erase carrier

fastboot erase userdata

fastboot erase metadata

fastboot erase ddr

fastboot oem fb_mode_clear

fastboot reboot

This has worked for me never had a problem don't expect the same outcome, I would read the terms and services you agreed to when unlocking the bootloader.
[Moto G Power (2021)] LethalGamer2121:
Mind if I ask what custom ROM you were using? I haven't seen any for this phone yet
[Samsung Galaxy Core.] klof44:
Hi,

I was trying to root a Samsung Galaxy A01 Core I had lying around but messed up somewhere in the process and can't figure out how to get it to boot back into android. I've tried different versions of TWRP and OrangeFox but none of them seem to work with this model. The closest I've gotten to booting android is getting the samsung logo by flashing a stock ROM that does identify as Samsung Official in download mode. I can't interface with it through ADB or fastboot and I've tried all the fixes I could find such as a different cable, extracted PIT and removing the SIM card. This phone is not at all important but I would like to use it for projects.

Is there any hope of getting this phone back into working order? Please say something if there is any information that could help.
[Xiaomi Mi 11 Lite 5G] Monarch1:
within three months of purchase, the phone began showing " the phone is destroyed" message and stopped working. Service centre did factory reset but nothing happened. They replaced the motherboard but it started behaving erratically. It is not working with Jio sim. It is informed that only refurbished motherboard is being supplied by Company for repairs during warranty. Now again they said they will replace with new motherboard. On the whole, phone appears to be cheap and unsound.
[OnePlus 6 Guides, News, & Discussion] arunmcops:
Hi.

You have heard of Renegade Project, for installation of Windows 10/11 ARM64 on Snapdragon 845 devices. There are many issues with the drivers, which result in Qualcomm Crash Dump or Blue screen. After multiple trials and errors, I finally figured the definitive guide for installation of Windows 10 ARM64 on OnePlus 6. This d guide does not requires installation of any drivers as all the drivers and MS Office for ARM, are preinstalled. It is a bootable recovery image of my own working build.

Although initial setup needs to be done and this will render the android system unbootable:

1. Copy parted to root of sdcard/storage of the phone

2. Boot the latest twrp recovery:

adb shell
cp /sdcard/parted /sbin/ && chmod 755 /sbin/parted
umount /data && umount /sdcard
parted /dev/block/sda

Remove all partitions Note: Android will be removed

rm 17
rm 16
rm 15
rm 14

Make necessary partitions (128GB model)

mkpart esp fat32 6559MB 7000MB
mkpart win ntfs 7000MB 120GB
mkpart pe fat32 120GB 121GB
mkpart userdata ext4 121GB 125GB
set 14 esp on
quit

Reboot to twrp and format the partitions

adb shell
mkfs.fat -F32 -s1 /dev/block/by-name/pe
mkfs.fat -F32 -s1 /dev/block/by-name/esp
mkfs.ntfs -f /dev/block/by-name/win
mke2fs -t ext4 /dev/block/by-name/userdata

Reboot to twrp and copy pe folder to adb folder:

adb push pe /sdcard/pe/
adb shell
mount /dev/block/by-name/pe /mnt
cp -r /sdcard/pe/* /mnt

Now flash the UEFI boot image for Oneplus 6 from bootloader

fastboot flash boot boot.img

Copy Backupimage.win (which was downloaded) and DISM++ to a pendrive, wait for PE image to boot. Connect usb keyborad, mouse and pendrive via USB-C Hub.

In command prompt, enter following commands:

diskpart
select disk 0
list part
select part 14
assign letter=Y
exit

Now open Dism++ARM64.exe and click on REcovery tab ---> System Restore

Browse and select backupimage.wim from pendrive, and select destination (C:\) and check "Add Boot".

Now wait patiently as i may take some time.

After Restore is finished, enter following commands in Command Prompt:

bcdedit /store Y:\efi\microsoft\boot\bcd /set {Default} testsigning on
bcdedit /store Y:\efi\microsoft\boot\bcd /set {Default} nointegritychecks on
bcdedit /store Y:\efi\microsoft\boot\bcd /set {Default} recoveryenabled no
shutdown -s -t 0

Remove all USB devices/Hub and let the phone boot.

Enjoy.

Everything except Camera, is working.

Acknowledgements:

1. TWRP

2. Renegade Project

3. Microsoft

4. Oneplus

Download Links: Mediafire Link