yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] TigerB:
Hi,

I am new into this "custom ROM" topic. I have an old Samsung SII i9100 which I adventured in updating to Android 13.. but I think I have soft bricked my phone, lol.

Please, can I ask for help?

My first step here is to try to have TWRP installed on the phone... but after the try I am unable to access the normal operating system turning on the phone.

A couple of info around my adventure:

1- I have installed Samsung Android USB Driver on my Windows.

2- I have downloaded ADB and Fastboot and tried using it, but all I get is empty device list.

3- I have tried 2 different USB cables.

4- I have tried using different ports.

5- I have tried two different computers, one using Windows 11, one using Windows 7.

6- I have tried different versions of Odin (v3.12.3, v3.13.3, v3.14.4).

7- I have tried different versions of TWRP download - twrp-3.1.0-0-i9100.img.tar, twrp-3.6.0_9-0-i9100.img, twrp-3.6.1_9-0-i9100.img)

8- As far as I recall, I have turned on developer mode and USB debugging on my phone. (I can't access my phone to recheck is it is soft bricked).

9- I am no longer able to access recovery boot or normal boot on my phone. The only message I get is: "Firmware upgrade encountered as issue. Please select recovery mode in Kies & try again."

I have other old phones (SGN3 and SGN4), they also don't get the device shown up with ADB and Fastboot, but I didn't try installing TWRP on the yet as I am afraid of bricking them too.

Please, can I has for help on what to do? My goal is to have Android 13 running on my Samsung Galaxy SII - i9100 phone.
[HTC Desire 12 ROMs, Kernels, Recoveries, & Other D] singala_929:
Hi, I saw that was no recovery for this device so I decide to port one for my self.

When installed you need to format data(option where you need to type yes) and flash decrypter.

Bugs: Sd card is not showing (OTG works fine for me)

No keyboard with renaming files.

No battery percentage.

Surely some other.

I think anything else work fine.

Ported with recovery krzysiek546 gave.

If anyone would like to help fix bugs, I'll provide all files I have.

View attachment 5966183View attachment 5966181
[HTC Desire 12 ROMs, Kernels, Recoveries, & Other D] gumis1986:
Hello, I have a question about this port. Does clean software run normally without any issues. And how to make backup of the software. In case of failed installation of recovery. Sorry for my English. I hope you are understandable
[HTC Desire 12 ROMs, Kernels, Recoveries, & Other D] singala_929:
I think you dont need system backup because you can flash stock recovery, when you install TWRP you can backup system.
[HTC Desire 12 ROMs, Kernels, Recoveries, & Other D] alcatel4010x:
wow, didnt expect for this phone to get twrp. are there any possibillities for roms/gsis?
[HTC Desire 12 ROMs, Kernels, Recoveries, & Other D] notnoelchannel:
i can try building twrp by clean sources and with a device tree if y'all want
[HTC Desire 12 ROMs, Kernels, Recoveries, & Other D] singala_929:
if you want do it but I dont have this phone anymore and i think there is not any custom rom for this device so i dont see a point.
[HTC Desire 12 ROMs, Kernels, Recoveries, & Other D] singala_929:
no man sry dont have device and knowledge to do that xd
[HTC Desire 12 ROMs, Kernels, Recoveries, & Other D] alcatel4010x:
mines motherboard fried itself too
[Android Q&A, Help & Troubleshooting] Dchemist909:
Hi, I just joined here because im needing some help. Im trying to view the files of the mobile game "survivor.io" my goal is to see pictures & descriptions of unreleased content on pc win10. I have the latest apk downloaded from apkpure, what would be my next step to accomplish this? Thanks.
[Android Q&A, Help & Troubleshooting] parrots_:
You'll probably to decompile the APK. To do this, you could use APKTool.
[Android Q&A, Help & Troubleshooting] Dchemist909:
Yeah getting apktool to work has been a problem
[Android Q&A, Help & Troubleshooting] parrots_:
What issue have you been having?
[Galaxy Note 3 Q&A, Help & Troubleshooting] TigerB:
Hi... can I ask for help please?

I did a fresh installation / update of Google Authenticator (version 6.0) on my Samsung Galaxy Note 3, running Android Kit Kat (v4.4.2), and did a mass import using the QR code transfer from one phone do another... however the App does not seem to be working properly.

That happens is that the 6 generated codes are actually static (the don't update as time passes). The same issue is happening with my Samsung Galaxy Note 4. I have a Samsung Galaxy Note 8, running Android 9, which is working properly.

Please, has anyone also run into this issue / know the way around it?

Thanks!
[Galaxy Note 3 Q&A, Help & Troubleshooting] JJEgan:
I wonder if Kit Kat is now to old for Google Authenticator 6.
[Xiaomi Redmi Note 5 Pro Questions & Answers] MrDubsstep:
I'm getting confused with all this roms.

LineageOS with Android 11 - Official and Unofficial

Pixel Experience with Android 13 - Official and Unofficial

Apart from those, i heard about SparkOS like the best rom, but i see that is compatible with Redmi Note 5 Plus.

I'm from Europe and i see in the CPU-Z that my phone has Snapdragon 636.
[LeEco Le Pro3 Questions & Answers] rgr1:
Anyone having issues with the latest LineageOs builds for X720 (zl1)? A year ago I installed an update and after that my auto-rotate and a few other things didn't work properly.

I reverted to an older version (11/22/2022) and haven't updated since then. Can I update safely?
[Realme GT Neo 3] tigers2:
Hi there

Last night, I noticed that root doesn't work. I opened Magisk, and it showed a message "Your device requires additional setup", and it required a reboot. I pressed OK, then the phone rebooted in 5 seconds. However, after showing the "Realme" logo and the Orange State message, it turned off. Since then, I cannot turn it on, however, I can make it get to that screen by pressing all buttons on the phone at the same time, but it turns off after 5 seconds. It also gets to that screen if I press and hold Volume Up + Power buttons for a while. I noticed that the phone starts up by its wil sometimes (but turns off shortly then)l, and it heats up while connect to PC via the USB cable. I would like to flash the boot partition with the magisk-patched boot image (which I do after every software update) to attempt to repair it, but I cannot manage to find a way to enter fastboot.

Is there a way to enter fastboot/fastbootd mode in this case? Do you know any method to restore it? I appreciate any help
[Realme GT Neo 3] ZG_DEV:
Send some pics please
[Realme GT Neo 3] tigers2:
This screen is displayed for 5 seconds, then the phone turns off. When it was working, this, or a similar message was displayed for at least 20 seconds, then the phone started booting up Now it really won't start up, and possibly tries to reboot, and it succeeds after 30-60 minutes
[Realme GT Neo 3] ZG_DEV:
Look

It might boot if u relocked the bootloader

It seems that u messed up with patching the boot image
[Realme GT Neo 3] ZG_DEV:
Or maybe an old version of magisk

U need to download the latest magisk manager (V26) and repatch the boot image using it without unticking anything
[Realme GT Neo 3] tigers2:
I used Magisk 25.2, it didn't notify about updates. The magisk-patched A09 boot image has worked so far; I don't have access to any newer boot images. I would have been able to patch the A09 boot image with Magisk 26.1 on another phone, but I can't flash it now. Once I let Magisk patch the other boot slot before a software update, which resulted in a boot loop, but flashing the patched boot image solved the issue. The bootloader was not locked, nor did I intend/try to do so, I know that it breaks the phone. I remember that the option to lock/unlock the bootloader in Developer options (OEM unlock) was disabled after locking it.

I can't figure out what triggered this issue. Last time the boot image was flashed in June after an update, and it has worked so far. I didn't expect this situation to arise. If I had chosen to flash the boot image myself instead of letting Magisk try to do additional setup, perhaps it would be working now. And possibly I should have checked Magisk's GitHub page after that because v25.2 is really old.

If the bootloader got locked now, then I think it's most likely that the only hope is someone with access to the working flash tool. The MTKClientl doesn't work with Dimensity 8100.
[Realme GT Neo 3] ZG_DEV:
Wait u have ab boot slot ?

Next time when flashing a boot image flash it to the both slots using fastboot
[Android Q&A, Help & Troubleshooting] LouDBasS_101:
DOOGEE S89 Pro is an A/B partitioned device with recovery in ramdisk, which means that there is no recovery_a/b slot, the recovery is inside the boot_a/b image. There is no official TWRP image for DOOGEE devices (https://twrp.me/Devices/), and no unofficial TWRP image for this specific device (https://unofficialtwrp.com/devices/doogee/).

I've also tried to build a TWRP tree using the minimal-manifest-twrp for android 12 (https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-12.1), I always failed when I try

lunch twrp_<device>-eng

command so I guess I did not setup everything correctly because I never found a tutorial that explains what files do u have to change/rewrite/add in general for any device.

I've been trying to port the TWRP S88 Pro unofficial image to S89 Pro by unpacking the S88 Pro image (Carliv Image Kitchen), kind of merging it with the stock S89 Pro's one, flashing the boot.img, I got bootloop, I flash the previous working img with SPFlashTool and so on until I decided to stop and post a thread in this forum to see if anyone could help me or at least guide me through this process.

I've also tried to follow this "guide" (https://xdaforums.com/t/dev-how-to-compile-twrp-touch-recovery.1943625/) but I'm not able to do so because I'm not familiar enough with AOSP building.

I've also tried

twrpdtgen

but I get error because I input the boot.img which I think is not supported. I guess it only works for recovery.img.

Now I have 3 options:

-Port the S88 Pro TWRP image (which I think its easier)

-Build TWRP image using the github repo

-Use Dees_Troy guide

Could anybody enlighten my way in order to port the image?

Any other suggestions are welcomed.
[Asus Zenfone 9] palamosteliaro:
I tried activating the pocket mode, still the same with it off. I don't even know how to go to these screens, only obvious option on the lock screen is the camera (which never opens). Anyone knows what is being pressed to go to those screens and how to stop that from happening? Thanks in advance.
[Asus Zenfone 9] landsome:
Switch the screen unlocking method from 'Press or Touch' to 'Press only'. Had zero problems (literally zero) since then.
[Asus Zenfone 9] palamosteliaro:
I have never seen these options. Where is that setting?
[Asus Zenfone 9] landsome:
Settings > security > fingerprint > Screen off unlock
[Asus Zenfone 9] palamosteliaro:
That just requires to press the button to unlock with fingerprint. My phone doesn't unlock, the screen wakes up and somehow goes to that emergency menu. If I put an unregistered finger when its locked (with screen off) it just vibrates once, it doesn't unlock or open the screen. I don't see why setting that to press would make any difference with my issue.
[Asus Zenfone 9] landsome:
Have you even bothered to try it? Have you even given it a thought to see what might be happening? Or do you just refuse advice because you dislike advice that you yourself requested?

It's simple, really. If you set it without press, every time you brush your pants against the fp, it wakes up the screen, rejects the "fp", but then other areas of the screen get pressed - such as emergency calling.
[Asus Zenfone 9] palamosteliaro:
I actually did try it because why not and it didn't make a difference. As I mentioned, even with an actual not registered finger, it rejects it without the screen waking. It just does a small vibration. What I am seeing is the emergency call screen, which I just now found out you need to swipe (to get to the pattern unlock) and then press the emergency button at the bottom (which is actually pretty small). Its kinda hard to get to that screen, so I don't understand how it happens every time the phone is in my pocket.
[Asus Zenfone 9] landsome:
I had exactly the same problem and I - and many others - solved it that way.

It's simple to get to the screen in question. If you touch with an unrecognizable print a few times, the screen wakes to the pin screen. Under the numbers on that screen, there is an emergency call option. Touch that accidentally, and voila. You're just one screen away...

Basically, your phone keeps registering unrecognized touches constantly, from touching against the pants. I assume you don't get this problem if you just keep the phone in a closed bag that does not move.
[Asus Zenfone 9] palamosteliaro:
Oh you are right. I did try to unlock with unregistered finger many times and after 5 the screen woke up to the pattern unlock screen. However I did try putting it to press only and went to the super market. The second time I took the phone out, it was on the emergency screen again. Now I am suspecting that its the "double tap to wake screen" setting, I will check it next time I go out and see.

No matter what it is, one thing is for sure: The pocket mode setting does nothing or it doesn't work for some reason. Asus needs to fix, I never had that issue with other phones I used.
[Samsung Galaxy S21 Ultra] Isstopi:
View attachment 5966291View attachment 5966285Hello. I recently bought an American version of an Samsung S21 Ultra (Verizon Variant) and it's not working with my country's network bands. 3G barely works but it's more unstable and slow so it might just not be working at all. I've played around with the hidden settings of Band Selections but none of it seems to work. Would changing the firmware work and if yes then what firmware would be best for my SM-G998U? Check the pic attached for my country's network bands View attachment 5966289
[Nothing Phone 1] Shuyin10:
Hello !

Following my DAC problem, I came back to NOS (Paranoid before).

I went back to stock with 1.1.4 and updated to 1.5.6 using OTA.

But when I tried to configure my Google Wallet with my bank card, it was impossible! The application tells me that my smartphone is not certified or rooted!

Except that I've never rooted my phone, only unlocked the bootloader!

And in the Play Store > Settings > About, the device is not certified!

Except that I use my phone a lot to pay, so why isn't it certified?

Thanks in advance!

EDIT : the reason was the unlocked bootloader...i dont understabd why now...so
[Nothing Phone 1] dedors:
After having the certification since I rooted, I lost it on 1.5.4 without doing anything and tried a lot to get it back, without success.

After updating to 1.5.6 it's fine again, at least for now.
[Nothing Phone 1] franco985:
I have updated to 2.0.2 and now the device is not certified. Anyone knows hot to fix? thanks.

ps. bootloader is unlocked
[Nothing Phone 1] calinorg:
You kinda answered yourself - You have to lock the bootloader for play protect certification to work. If you're rooted, or have otherwise modified software, you can't lock until you're fully back to stock...
[Lenovo P11] mau0968:
Hi, my tablet started to show a bug with the microphone.

Every time I start or switch apps, It starts to record or transmit a very loud noise, and it keeps on until I say something.

Then it stops until I switch apps again.

This happens on all apps that use the microphone. It is surely a system or hardware issue.

Does anyone have this problem, or know how to fix it?

Thanks

Mauricio
[General Topics] xminirom:
Bootloader Unlocking:

* In PHONE *

** Go to settings > my phone > look for build number > tap 7 times

** Go Back to settings > System > Developer options

** Enable > USB debugging

** Enable > OEM Unlocking (You must have infinix ID and it should be Two weeks older before you can apply for Unlocking)

After completing Above steps

* In PC *

* Install Driver for your phone ( Search for samsung MTK driver. it is most updated and compatible with our phone)

** Driver for bootloader interface

** Driver for ADB interface

** Driver for Fastboot interface

** Connect Your Phone to PC > It will Ask for Debugging permission > tick Always > OK

* search for adb fastboot ++ tool > Extract it anywhere > click and open > Open CMD file

* Connect your phone > Type

*** adb shell

*** adb devices

*** adb reboot fastboot (do not close window)

* your phone will reboot to fastbootd Mode

* using volumn key select > Reboot bootloader mode > this will bring fastboot mode in phone

* Now in CMD window > Type

*** fastboot flashing unlock

* using Volumn UP button give YES permission or decline using Volumn Down button.

* After selecting volumn up > IN CMD you will see success msg

* DONE Unlocking.
[General Topics] Flixia:
Hi , do you have stock firmware for x6831 ? I'm thinking about rooting it. Need boot.img. there is one or two in web search , but i don't really trust unnamed website.
[General Topics] quantumcog:
did you find stock boot.img?

Edit: maybe you could dump boot.img using mtkclient by bkerler. I haven't received the phone yet so I couldn't try

Edit2: Successful
[General Topics] mildunderstand:
I'm considering giving it a root. I don't really trust unidentified websites, however there are one or two in web searches.
[General Topics] quantumcog:
Just dump the boot.img of installed firmware (I used mtkclient) and patch it then flash :)
[General Topics] quantumcog:
Pixel experience gsi also working ;). Tested using dsu
[General Topics] Flixia:
Hi man , sorry for late reply , i just log into xda. Nah , i didn't try to dump it , i just use gsi rom before , that devices i already sold to someone. But thanks for that mtk tools , never heard of it. Gonna try it soon.
[General Topics] rtyuakatsuki:
I already patch it and got bootloop how to fix ?

And it must be same version of the firmware ?
[General Topics] quantumcog:
Firmware must be same version

Or flash already patched version present in the telegram group
[General Topics] rtyuakatsuki:
oh no i flash diffrent version firmware boot.img may i do downgrade firmware ?

and what link of telegram group for hot 30
[General Topics] quantumcog:
Can't share due to xda rules but search on telegram
[General Topics] rtyuakatsuki:
what i must search or can you dm me ?
[General Topics] yazan.xda:
hi..are you still using that custom rom? did you face any problem? can you please provide us the installation guide?
[General Topics] quantumcog:
Sure.

STEPS:

Unlock Bootloader

reboot to normal fastboot.

disable vbmeta verification. You need stock rom for this. (fastboot flash --disable-verity --disable verification vbmeta_a vbmeta.img)

repeat this for vbmeta_b, flash vbmeta_system similarly.)

Now, reboot to fastbootd (the new fastboot mode) using "fastboot reboot fastboot"

now flash system_a with gsi by "fastboot flash system gsi.img"
[General Topics] yazan.xda:
you are using infinix hot 30 x6831 right? just wanna be sure because i have some requests if you have time please.

1- install nova launcher and set it as default from nova settings and then look if you still have the split screen option

2-while still using nova as default launcher start any app and then rotate the screen till the app turn to horizontal mode then press on recent apps button on navigation bar and see if it is working normaly (because when i do that on my recent apps show up for half a second and then disappear)

3-and last can you give my a link to the img file you used for testing the gsi rom because i wanna test it using sideloader first to see if it worth the risk

thank you
[General Topics] quantumcog:
I am not on stock. So, cannot test nova launcher. After Unlocking Bootloader, You can use any GSI for DSU, I used evolution_arm64-ab-7.9.7-unofficial-20230914.img.xz
[General Topics] yazan.xda:
thank you..but doesn't that mean that i can use evolution x as main rom? or i can only use it with sideloader? and then use pixel experience as you did....im kinda confused and sorry for bothing you
[General Topics] quantumcog:
You can use it as main rom.
[General Topics] infinitynet:
Guys. Pls, how to install evolution x? I can't find information
[Moto G7 Play Questions & Answers] Mecd:
I'm getting this message when I try to go online with my Uber driver app.

"Go online from a different device. Unable to authenticate device."

I had unlocked the bootloader so I thought that maybe that was the problem, so I locked it back up and I'm still getting the message. I was hoping someone here could help me figure out what the problem is. I'm running Android 10. Could that be the problem? I called Uber suck-port and they said it was phone problem.
[Moto G7 Play Questions & Answers] lordman1135:
hello; i have had the same problem today, my phone is with android 10 and its rooted.

anyone can help us?
[Moto G7 Play Questions & Answers] Suno09:
I'm also having the same issue, "Go online from a different device. Unable to authenticate device". I'm running Noble Rom OneUI5 rooted device. Worked fine all this while until this morning. Any ideas on what could be causing the issue and any work arounds to try. I added the Uber app to the Magisk Configure DenyList as well, which did not resolve the issue
[Moto G7 Play Questions & Answers] dvdzinnn:
Same problem. I lean what Uber APP now detect unlocked bootloader! Greetings from Brazil!
[Moto G7 Play Questions & Answers] carlosdeabreu10:
I have the same problem! The Uber application is detecting root or unlocked bootloader. even formatting gives the message: unable to authenticate this device, go online on another device
[Moto G7 Play Questions & Answers] Mecd:
Did anyone figure this out? I'm getting this message even after locking back the bootloader.

Did you figured it out?

Hi did you figured it out?

Hi did you figured it out?
[Moto G7 Play Questions & Answers] lordman1135:
No, i dont know how to resolve it
[Moto G7 Play Questions & Answers] Mecd:
Hi did you figured it out

Yeah me either. What version of Magisk are you using?
[Moto G7 Play Questions & Answers] lordman1135:
I use the last one, 26
[Moto G7 Play Questions & Answers] Mecd:
Was your root working and then this happened or did it happened as soon as you rooted it?
[Moto G7 Play Questions & Answers] lordman1135:
It was working, i went offline, after 5 Minutes i tried to go online and i have this Problem.

I think its come from Uber, not from root or device, i think that they blocked every device have a mock gps Apps or like that
[Moto G7 Play Questions & Answers] Laurent de Lyon:
I got this error message too (on an unlocked phone, with magisk root that was uninstalled long before this issue, without a custom recovery, also uninstalled long before this issue, and replaced with a normal recovery).

Just tried to use the app on another phone, which is unlocked and rooted. Still getting this error message. So It was automatically and immediatly blocked. Anybody tried flashing the latest version of Android, and also locking the bootloader in the process ? That's something I didn't try yet.
[Moto G7 Play Questions & Answers] Mecd:
I haven't tried that yet. From the looks of it Uber can detect evidence of a root even if the phones bootloader was again locked and phone flashed to its original stock image. It's also detecting root even prior to me adding any GPS spoofing module. Btw have you tried yet spoofing Ubers gps using Clone my app?