yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] WoKoschekk:
What exactly didn't work? Do you get a message "please enable OEM unlock"? Or "command failed" or "waiting for any device"?

Each of these outputs indicates another error and it's important for us here to know them.

Android Flash Tool is no option because it needs the OEM unlock toggle to be enabled. Also any method via fastboot mode.

Last option is an OTA-update to the next build version of A13 that will be released in +/- two weeks. You must sideload it via recovery.

In recovery mode ADB is enabled by default. You do not need USB-Debugging.

While setup wizard is running, ADB is useless. But not in recovery mode. Your device must be recognized with 'adb devices'!!
[Google Pixel 7] weinbers:
command failed, unfortunately. And ADB doesn't recognize the phone in recovery mode.
[Google Pixel 7] WoKoschekk:
Which command? Which output?
[Google Pixel 7] WoKoschekk:
it seems that your driver (fastboot) is working well. Otherwise you would get 'waiting for any devices'.
[Google Pixel 7] CassieSassie:
This post helped me. Dont know how.

https://xdaforums.com/t/stuck-on-co...ck-from-android-14-beta.4586263/post-88546163
[Google Pixel 7] WoKoschekk:
@weinbers You should try that asap! :)
[Google Pixel 7] weinbers:
I followed that procedure and got the same "settings keeps stopping" message at step 9 - couldn't get to next step. So close😊. But thanks anyway!
[Google Pixel 7] weinbers:
Well. I just got closer... maybe.

First, there's a procedure out there involving turning on talkback, going to youtube etc. but that still gave me the same error.

Per a comment above, I tried to update via sd card. With the ota on an SD card. I tried to install it but got an error that the sdcard is an unknown volume and couldn't be mounted.

But I discovered if I put the phone in sideload from adb first and then plug the phone in, it is recognized in ADB!! Progress.

When I sideloaded the ota (after a factory reset), it successfully completed, giving me "install from ADB completed with status 0)" but upon reboot and initiation of the setup procedure, I still get stopped at the same point - set up crashes at copy data screen.

I then tried to flash the full package but got an error that the:

"ERROR: recovery: footer is wrong" ,

"update package verification took .2 sec. (result 1)"

"ERROR: recovery: signature verification failed"

"ERROR: recovery: error 21"

"install from ADB completed status 2"

"installation aborted"

I can't find info on those error or status codes.

Any other thoughts before I trade this in on a 7a (my screen turns on so it should be accepted as a trade-in?
[Google Pixel 7] CassieSassie:
Sorry m8 :(
[Google Pixel 7] manjaroid:
Unless you would prefer 7a over 7, warranty coverage probably comes with a repair request in your situation. It'll take about a week but if you have the option of a local walk-in shop like uBreakiFix you might get the phone back next day.
[Google Pixel 7] WoKoschekk:
needs to be formatted in FAT32
[Google Pixel 7] WoKoschekk:
From ADB? With ADB commands?

That's the reason why we need screenshots or at least the exactly commands you entered! This was wasted time for everybody here!
[Google Pixel 7] bobby janow:
I think we were all just trying to get him to recover the system without having to send it back. But the fatal flaw was not flipping the OEM switch before installing or rolling back. It's not necessary to unlock the bl but you need to be able to and the OP can't. I think purchasing the 7a and then sending back the 7 is the only way forward now unless he can figure something out.
[Google Pixel 7] weinbers:
Great idea, there tomorrow
[Google Pixel 7] manjaroid:
First you'll need to setup the RMA with Google. The process should let you select a partner in your area instead of shipping the phone.
[Google Pixel 7] weinbers:
Thanks for that, but I do have one in my area. I have an appt. today.
[Google Pixel 7] bobby janow:
In a situation like this one what could a repair shop do? I don't think they can reflash a system image but I guess they can replace the motherboard? Curious how this goes.
[Google Pixel 7] manjaroid:
Since the problem is all software I had the same thought. But worth a try I figure.
[Google Pixel 7] simplepinoi177:
It's probably as @WoKoschekk says, it's probably simply formatted wrong.

That's real interesting! I had the thought that you had to select "Apply update from ADB" in order to trigger the detection in Device Manager, but when I did it myself on my device, it immediately detected it; so I figure yours didn't need it either.

You should really do the factory reset after applying the ota (as doing it before is "formatting" things before the OTA settles and re-establishes things).

I'm curious what you mean "full package"....do you mean "Full Factory image" or, for somehow some reason wasn't flashing/installing a "full package" of the OTA image (even though we gave you the proper link from Google's official developers page)? If it is the former, you can't flash Full Factory images through ADB....

Since he got to the point of "install from ADB completed with status 0", I'm sure he did the usual command of "adb sideload ota.zip". But, it is a bit as you say, where I've seen an instance (around XDA) where it states completed "status 0", but after stating some errors...

I'm curious on this too; it really is only a software/system issue. But like most repair depots and other corrective profession, unless the parts are worth more than the trouble, they'll simply just replace the parts where it will properly reset things and get things working than find out the real reason what was causing the issue...
[Google Pixel 7] weinbers:
RESOLUTION

I took the phone over to the local Asurion and the tech said the phone got hot, so while I was there talking, he was able to open a ticket at Google (even tho one was already open) and got authorization for a new motherboard.

Unfortunately he didn't have any in stock and said it would be Tues. or Wed. to get one. But while we were talking, the morning mail brought one so I may have it back this afternoon with a new MB and therefore new OS.

Thanks everyone for all the help and suggestions along the way.
[Google Pixel 7] WoKoschekk:
The recovery fstab file of the Pixel 7 (located at vendor_boot.img/ramdisk/system/etc) has an entry for a USB device. But only 'vfat' or in other words FAT32 is accepted to get the flash drive mounted correctly. If you do so you will be able to navigate through the whole filesystem to choose your desired zip file.

To put it plain and simple (because it's always a bit confusing...): The term 'Apply update from sdcard' refers to a physically external storage such as a micro-SD card or an USB flash drive.

That's a important fact since Google uses the term 'sdcard' in all other areas of Android to describe the internal storage '/data/media/0'.

As @simplepinoi177 already mentioned: Not every ZIP file is a flashable ZIP. You need a certain folder hierarchy and a update-binary and a updater-script to process files and flash them through recovery.

It's the same mistake as users do when getting errors in TWRP. In recovery mode you only see the status screen. Detailed informations are recorded in recovery.log (see menu 'view recovery logs'). But to make it simple: exit code 0 = success and all others (1-255) not. https://linuxconfig.org/list-of-exit-codes-on-linux
[Google Pixel 7] bobby janow:
So what happened with the new motherboard?
[Google Pixel 7] weinbers:
Had to update the imei numbers with my mobile carrier but now working fine, other that a couple of app issues. But at least I have a working phone
[Google Pixel 7] simplepinoi177:
I know OP had his issue resolved (not through any means via software, but by replacing hardware systemboard), just wanted to input what @Lughnasadh posted in another thread that relates; in case someone with the same issue comes upon this thread....
[Google Pixel 7] bobby janow:
And a simple addition to that is: Make sure either you have an unlocked bootloader or have flipped the OEM switch to allow it in an emergency. Oh yeah, and backup all your files and pictures not in the cloud.
[Google Pixel 7] weinbers:
Just an update to my saga...

My problem restoring 13 from the 14 beta is now well documented and wide spread. BTW, I did not want an unlocked bootloader and was able to get the phone up and running again.

So after 2 motherboard replacements by an authorized repair center (the first was the wrong one), temporarily losing my phone number of 20 years, I reinstalled everything only to discover the main camera no longer worked... I was done - I needed a working phone.

So I traded in my 7 for a 7a. Got a hefty trade in, free case and free series-a ear buds.

Again, thanks to all who helped!
[Fire TV Q&A, Help & Troubleshooting] ForbEx:
Hello, I'm thinking about rooting my firecube which is on fire OS 6 with blocked updates. There's a new root method and bootloader unlock and my ask is, will be on rooted & Bootloader unlocked Cube 2 Netflix work? Because I read that, devices with unlocked bootloaders loose Widevine L1 certification, which is important for services like Netflix is..
[Philips, Sony, TCL Android TV] andrija2509:
Hello,

I forgot password for my TCL P6046, so I can't change TV inputs and i can't do factory reset. I thought reinstalling firmware would help, but it didn't. Anyone have any advice?
[Philips, Sony, TCL Android TV] stasiof:
Bellow is thread for your TV model......MT58 platform...

https://xdaforums.com/t/downgrade-file-for-tcl-c6-current-version-v8-t658t01-lf1v534.4122589/
[Samsung Galaxy S10 Questions & Answers] NULL0B:
(system SurfaceFlinger : Attempt to update InputPolicyFlags without permission ACCESS_SURFACE_FLINGER)

It apears to be trigered by hwcomposer process accesing to surface flinger as system user without SURFACE_FLINGER permission being declared on the rom.

To reproduce install this app then you will see hw composer errors whe it updates.

Logcat Reader Professional - Apps on Google Play

Android's most advanced log reader

play.google.com

Also can scrooll arround in launcher with adb logcat.

I tracked the bug downloading A12 surfaceflinger impl and tracing binder calls and results that hwcomposer is runing as user system (ps -Af) which doesn't have surface sflinger specific permission, it needs to run as graphics user, that's the one with that permission (/system/etc/permission/platform.xml)
[Samsung Galaxy S10 Questions & Answers] tuyluogluu:
Me and all sams s9-n9 owners (using a12 Noble rom)have this problem..i hope u'll solve it soon. 🤗
[Samsung Galaxy S10 Questions & Answers] tosunkaya:
Today i found this logcat spammer bug with logcat reader on G973FXXSGHWC1 and stumbled upon your thread. did u find any solution? It causes battery drain. is this exist on G973FXXUGHWC3 or G973FXXSGHWC2 too?

Is an uninstalled or disabled system app causing this? Samsung Keyboard, Samsung Pay, Reminder, Game Booster, Accessibility have ACCESS_SURFACE_FLINGER permission.

edit:

flashed G973FXXUGHWC3 and G973FXXSGHWC2, problem still exists.
[FYT Android Head Units] mmmm58:
Howdy all,

Got myself an unknown FYT unit but it only has 2 RCA outs (left and right).

Seems like some other variants have 4 RCA outs (FL, FR, RL, RR).

Is there a way to add those missing outputs? I'm assuming they actually there on the RCA breakout socket (there are 2 unused pins)

Thanks and regards!
[Realme GT 2] Prajwal_Beast:
To REMOVE the warning - Orange State Your device has been unlocked and can't be trusted Your device will boot in 5 seconds - on UNLOCKED RMX3312 & RMX3311

Install ADB DRIVERS & follow in POWERSHELL

adb devices

adb reboot fastboot

RMX3312 goes to FASTBOOTD mode

fastboot flash abl <drag & drop OrangeState-Warning_Remover.img>

fastboot reboot

P.S. : fastbootd != fastboot mode

P.P.S. : If in fastboot type

fastboot reboot fastboot

Now, UI looking similar to RECOVERY will be there instead of BOOTLOADER
[Realme GT 2] b0nb0n3v:
Thank you! It's compatible with rmx3311?
[Realme GT 2] karayemis:
Worked for me too on RMX3311
[Realme GT 2] smashda:
@Prajwal_Beast is it possible to put in a custom images?

I couldn't figure out what type of files are in the .img.
[Realme GT 2] Prajwal_Beast:
I don't think it's possible to put a custom image!
[Realme GT 2] legendebrune:
Thank you for your work! is it compatible with realme gt 2 pro (RMX 3300 or RMX3301)? Thanks
[Realme GT 2] Prajwal_Beast:
i'm not sure - works on RMX3312 - Try & let me know - I can update the thread
[Realme GT 2] gx7x:
showing me this @Prajwal_Beast View attachment 5998253
[Realme GT 2] Prajwal_Beast:
try this - fastboot reboot fastboot & then flash it
[Realme GT 2] GH©ST:
Hello sir @Prajwal_Beast , can this file and method be used in another phone models i currently have

Realme GT Neo 5Se ( RMX3700 )

Android 13 RUI 4.0

OS version : RMX3700_13.1.0.113(CN01)

With unlocked bootloader, Root And Lsposed.

Thanks in advance 😃
[Realme GT 2] Prajwal_Beast:
nope - this works on gt2 only
[Realme GT 2] Deleted member 12745820:
Does not work, DO NOT FLASH on RMX3311 bricked my phone and is vibrating with black screen.
[Realme GT 2] Prajwal_Beast:
nope! it works for most of the users of RMX3311! You'd have messed something up!
[Realme GT 2] Prajwal_Beast:
Yes - it's possible will make a tutorial soon
[Realme GT 2] Prajwal_Beast:
[TOOL][SPLASH][QCOM]Change oppo/realme/oneplus boot splash image

This tool I called it opsplash. :eek:This tool does not support mtk device, qualcomm only!:eek: cause it can unpack/repack oppo splash format image. pic from my cygwin terminal If you like my tool, you can buy me a cofface. Donate ...

xdaforums.com
[Samsung Galaxy A52s 5G] abdalhakiem:
Can i downgrade the binary version of a52s from u2 to u1
[Samsung Galaxy A52s 5G] Simon1511:
Nope, thats not possible.

The binary version is an anti-rollback feature that's supposed to prevent you from flashing older firmwares that eventually have security issues.
[Samsung Galaxy A52s 5G] abdalhakiem:
If i install custom rom will it help ?

The main proplem is the mobile data network is week in onui 5.1
[Samsung Galaxy A52s 5G] Simon1511:
Binary version is not tied to the ROM you're using, it's baked right into the bootloader/firmware. You can't ever again downgrade that.
[Android Q&A, Help & Troubleshooting] KASO2END:
Hi

I have been working on my s10 5g lately and searching and understanding how to root it, and I have been successful in doing so but there is a problem which I think is very very bothersome.

my phone keep losing root access whenever it's rebooted, I thought it's was a miscalculation or a mistake in the process of rooting but turns out the s10 series and the note and my s10 5g have a certain method to activate the root which has been installed I read about it and it says you have to plug the phone to a working pc and do a button variations which is volume button up + bixby button + power button with the USB-C plugged into the pc I tried many things to solve this problem but believe me nothing worked for me it's like I find a brick wall whenever I try to solve it please help anything would do here's the process of rooting my phone if anyone is wondering

.

.

.

.

.

.

.first I download the firmware version of my phone which is a s10 5g exynos SM-G977N

.then after I download the firmware I copy the AP.....Md5 file to my phone to be patched by magisk(version26.1)

.after that I turn off my phone into download mode and plug it to my pc

.I boot up Odin version 3.14

.then I place the BL file and the CP file and the CSC file and place the patched AP file in

.then begin the process I boot up my phone and my phone is rooted but whenever it turns off or gets rebooted the root access is gone (btw the first time i rooted my phone it has gone into a boot loop and I had to hard reset it I only had root access in the second attempt)

Any help is much appreciated and I hope I get it soon
[Android Q&A, Help & Troubleshooting] ze7zez:
Use the previous version of Magisk.
[Android Q&A, Help & Troubleshooting] KASO2END:
Which one and do I keep using the same method
[Android Q&A, Help & Troubleshooting] V0latyle:
25.2, and yes use the same method
[Android Q&A, Help & Troubleshooting] KASO2END:
Okay I'll get back to you
[Android Q&A, Help & Troubleshooting] KASO2END:
Okay I just done about everything I got magisk 25.2 and patched the AP file with it and rooted it but I still lost root access when I rebooted my phone

EDIT: the images shows everything

EDIT: I think everytime I reboot it I boots to the stock boot.img instead of the magisk boot.img I think so??

EDIT: I tried rebooting from magisk to recovery and it worked
[Android Q&A, Help & Troubleshooting] Mewcury:
I’ve the same phone and same issue. There’s nothing you can do. The phone just isn’t made for rooting. Either don’t ever let it turn off or get another phone
[Samsung Galaxy A34] clackityclack:
Havn't rooted a device for many years. I now own a "A34 5G" (Model name SM-A346E/DSN). Where can I find rooting instructions per device these days ?

thanks
[Samsung Galaxy A34] V0latyle:
Did you search before posting?

Magisk installation instructions
[Samsung Galaxy A34] Mentain:
Thank you for the installation instruction

papa's pizzeria​
[Samsung Galaxy A34] willydu:
Hello, I am the Taiwan version of A3460. The bl lock has been unlocked, but after flashing into the magisk of Ap, I did not boot into the recovery mode by myself, and it was directly stuck at Samsung.

Then it restarted until the word Samsung didn’t move. How can I solve it? My model is A3460
[Samsung Galaxy A34] willydu:
{Mod edit: Quoted post has been deleted. Oswald Boelcke, Senior Moderator}

Thank you I'll try again tonight
[Samsung Galaxy A34] fil3s:
On my a34 5g the ramdisk = yes. So I can boot into magisk normally
[Samsung Galaxy A34] mvikrant97:
{Mod edit: Quoted post has been deleted. Oswald Boelcke, Senior Moderator}

@Oswald Boelcke
[Samsung Galaxy A34] prorounak:
Please make a tutorial on how to root samsung galaxy A34 if u have successfully rooted your device. There are many root tutorials out there and people are using different methods to root the phone (which is confusing). I will be grateful if someone can make a root guide. Please 🙏 :cry:
[Samsung Galaxy A34] Phi Eridani:
I followed this guide, specifically this part about Samsung phones. It worked for me.
[Samsung Galaxy A34] Zobbster:
Using the guide from the post above, I've completed the patching process, but I'm struggling to get Odin to actually flash the files - it sees the device and adds it, all the files are correctly loaded in their correct sections, but Odin sits at the initialisation stage:

~

<ID:0/007> Odin engine v(ID:3.1301)..

<ID:0/007> File analysis..

<ID:0/007> Total Binary size: 253 M

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

The handset is a SM-A346E/DSN. The device's bootloader is unlocked, I've generated all the files 3 times over from 2 different firmware downloads, the patched files were transferred over adb, I've tried 3 separate PCs, 3 different versions of Odin, multiple cables and I'm now into day 3 of what should be a 5 minute job.

Can anyone help?
[Samsung Galaxy A34] AtomicStryker:
If you google "Odin stuck Initialzation", it links you to a thread in this very forum where people discuss possible issues and solutions.

My general advice would be to triple-check you really executed every step of the instructions.
[Samsung Galaxy A34] Zobbster:
Thanks, but that's partly why I've spent so long trying to get it to work - going down the rabbit holes of 'fixes' that just didn't work. Either that or my search-fu is terribly weak.

I'm even at the point now where I'm wondering if the handset has a block on certain fastboot/Odin commands. But that'd be ridiculous, right?
[Samsung Galaxy A34] AtomicStryker:
Well, apparently Odin is "leaked" as in it is not officially provided or supported by Samsung. However, Heimdall is open source https://github.com/Benjamin-Dobell/Heimdall and performs the same job. So try that? The instructions say Heimdall is for Linux but they do have Windows support.

EDIT: It hasnt been updated in a while, but maybe its worth the attempt. You are just trying to upload a file after all
[Samsung Galaxy A34] Zobbster:
Thanks again for the help, it's greatly appreciated. I'll try with Heimdall and report back!

EDIT: IT WORKED! Absolutely no idea why Odin wouldn't, but Heimdall did. Again, many thanks for your help AtomicStryker.
[Samsung Galaxy A34] fil3s:
Since my post was removed, I'll put the instructions here in text format.

The A34 5G by Samsung model A346E is easy to gain root access on, let's dive in

Credits for this stripped down guide go to John Wu aka topjohnwu creator of the magisk app

Unlocking the bootloader

Power off your A34 smartphone and hold volume up and volume down at the same time and plug it into your PC

Long press volume up to unlock the bootloader

*all data on the device will be lost, so make sure to back up any important documents*

To bypass Vaultkeeper run through setup and connect to wifi, enable developer options and confirm the bootloader is unlocked under enable OEM unlock and greyed out

Next, you'll need the stock firmware which can be downloaded using frija or by downloading from samfw website

We'll also need Odin flashing tool and the USB driver

Get magisk from here and install it

You'll need the platform tools (ADB)

We will need to know the CSC for downloading from frija which can be found in about phone > software information > service provider software information

You can see my CSC is OPS in the above screenshot

Install the magisk app on your phone

Extract the firmware and send the AP tar file to your phone. Open magisk > install > select and patch a file, select the AP tar file

Now we're going to use ADB to pull the patched AP file back to our device

adb pull /sdcard/Download/magisk_patched_[random_strings].tar

Note: you will need the exact name of the file. Right-click on the patched AP file, and select 'properties', copy the file name and insert it into the appropriate field

Power off the phone and hold volume up and volume down and plug the phone into the PC.

Open Odin and insert the files CP, BL, CSC and the patched AP file into the corresponding slots and tap start

If all went well, Odin will display 'pass' and the phone will factory reset and reboot.

Open the magisk app and let it complete installation and reboot

For bricks see this post

If you get an annoying prompt that a service provider update is available and needs to reboot also uninstall the CID manager

In adb type ;

adb shell

pm disable-user --user 0 com.samsung.android.cidmanager

pm uninstall --user 0 com.samsung.android.cidmanager

Conclusion

If you want to update the software version on your a34 5g handset just use frija to download the firmware and flash in Odin using the home_csc file and make sure to patch the new AP file with magisk
[Samsung Galaxy A34] lux aeterna:
Hey everyone!

I was wondering if I can root my phone and then reverse the process. That is unlock bootloader, root, run some apps that I'd like to check and then unroot and lock bootloader again.

The reason I want to revert the process is that I'll have my phone fixed by Samsung official service and I don't want to void my warranty.

Thank you in advance!
[Samsung Galaxy A34] AtomicStryker:
Not possible. Unlocking the bootloader flips a permanent bit, called "Knox". Your phone will forever after be branded as tampered with. There is no known workaround other than acceptance.
[Samsung Galaxy A34] lux aeterna:
Thank you very much!
[Samsung Galaxy A34] fil3s:
If you unlock the bootloader and use Samsung pay, Samsung health etc. You can kiss them goodbye. Samsung don't want their phones unlocked/rooted.

One possible way to keep the bootloader locked and not trip Knox is to use wireless debugging with shizuku.
[Samsung Galaxy A34] lux aeterna:
Thanks for your reply!

Does that mean that I'll be able to root my device or that I'll be able to run apps that require root access?