yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6a] tamerlanjust:
is this mod current? Can I install the latest firmware with Android 14? Or are there more current versions?
[Google Pixel 6a] Max0nchik:
I can't say unfortunately, I sold this ugly smartphone, and took Xiaomi, which is much better
[Google Pixel 6a] tamerlanjust:
What Xiaomi did you buy?
[Google Pixel 6a] Max0nchik:
12x
[Microsoft Surface Duo Questions & Answers] pkhc:
Can anyone help me as my Surface Duo 1 after upgrade to Andriod 12L with factory reset. I forget the email address at Google and cannot confirm the device. I use the by pass method for Andriod 11 with no hope as the left screen was lock all the time and can do nothing for device setting. Anyone can help to by pass the Google account check? Great thanks in advance.
[Samsung Galaxy S23 Ultra] aeroengg:
My phone has 2 physical sim slots and an esim option. I have all 3 installed on my phone.

If I try to activate sim 2 I have to deactivate the esim. My question is if it is somehow possible to deactivate sim 1 and keep sim 2 and the esim active at the same time.

Thanks for your help
[Samsung Galaxy S23 Ultra] hoss_n2:
I think the Esim share the same IMEI with the sim 2 , so may be it is not possible , try it yourself and see I don't have access to esim in my country right now to test
[Samsung Galaxy S23 Ultra] aeroengg:
Thanks, I think you are right.
[Android Q&A, Help & Troubleshooting] Tamagnun:
Hi to everybody,

my MI 9T Pro has black/broken screen so I need to access it and/or replicate the screen by using the ADB facility.

It has the USB Debug enabled, but I cannot authorize the access from my laptop due to the black screen and broken touch, there is any possibility to bypass the authorization process?

I have already tried to connect a mini-docking station in order to replicate the screen via the USB-C to HDMI feature, but nothing appears on the external display.

Any suggestion?

Many thanks

Roberto

P.S.: the phone works, it receives call, it is connected to the wifi network and, if it is connected via USB to the laptop, the "adb devices" command returns its serial number followed by a sad unauthorized status...
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
Hello and good afternoon, Roberto.

Welcome to XDA! I hope you'll always get the support you require.

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

Note: Questions go in Q&A Forum

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

xdaforums.com

and the others. I've moved your thread to Android Q&A.

Thanks for your cooperation!

Regards

Oswald Boelcke

Senior Moderator
[Android Q&A, Help & Troubleshooting] Tamagnun:
Thank you Oswald, sorry for my wrong posting, I chose that thread because it was referred to ADB.

Kind Regards

Roberto
[Android Q&A, Help & Troubleshooting] IamTheBRAVE:
Don't know if it'll help, but the unauthorized message means a mismatch between pc and phone.

You can do this:

Go to C:/Users/<your username>/.android and delete a file called "adb key"

It's a hidden folder so activate that in folder options.

However, this will only trigger a new authorization message on the phone again.

The Android usb debugging notification gives you the option to switch the connection to be controlled from the phone to the PC side but it won't help if you can't see it.
[Android Q&A, Help & Troubleshooting] Tamagnun:
Thank you very much for the useful tip!!

In this folder I found two files with the same timestamp:

- adbkey (without extension)

- adbkey.pub

Do you think it's better to delete both, isn't it?

Any idea to connect to the smartphone the USB-C data cable AND an external keyboard at the same time, using an OTG adaptor?

I need to use the data cable for ABD because I'm afraid I didn't activate the wireless debug option on the phone AND the keyboard in order to try to grant the authorization when the popup "appears" (ehm... it cannot, but if it should be possible it woold appear!! :D)

Anyway, many many thanks for this first step!!
[Android Q&A, Help & Troubleshooting] IamTheBRAVE:
Both is ok.

I don't know, maybe a wireless keyboard ? Or an usb hub like this:

https://www.amazon.com/TargetGo-Splitter-Extender-Ultra-Slim-Microphone/dp/B0957JKBHZ

So you can plug both the keyboard and the phone cable. Not sure if it would work...

Good luck👍
[Android Q&A, Help & Troubleshooting] Tamagnun:
Hi Iam,

I'm performing some tests with an old phone (Note 4) in order to check your suggestion: unfortunately it's not possible to connect a keyboard (using an OTG cable, the phone is the "host" and devices are "clients") and to use ADBat the same time, because the standard data cable sets the phone like "client" and the PC like "host".

In fact in the OTG cable the pin 4 in the micro-USB connector is closed to GND, in standard data/charge cable the PIN 4 is not connected.

The idea to use a wireless keyboard is good, but with the black screen I cannot control BT connection or other.

In addition, I verified that the grant popup appears only if the phone is unlocked and also this is very hard with the black (and dead) screen.

I read in another thread (that I'm not able to find now...) that by copying the adbkey file from the PC .android folder to an internal android directory on th phone (something similiar to /data/adb/keys, but I don't remember well...) the smartphone authorizes the PC to connect via adb, do you now if this method could be a way to bypass the manual grant operation ?

Do you know a method to copy a file from PC to the phone by starting it in recovery mode?

Fastboot can help in this operation?

Thank you
[Android Q&A, Help & Troubleshooting] IamTheBRAVE:
Transferring files can only be done with adb push command.

I am not aware of a directory in the phone with the adbkey in it. So can't help you there...

Edit: found this

Storage location of "adb_keys"

I have a Galaxy s3 (I9300) that has a broken touch screen (display is fine). I therefore can not click the authorization dialog that pops up when I try to access the device via adb on any ROMs above

android.stackexchange.com

Hope it helps a little.
[Android Q&A, Help & Troubleshooting] Tamagnun:
Hi Iam, thank you for your help!

On GitHub I found the cmd to copy RSA key from the PC to the smartphone, it is:

adb push %userprofile%/.android/adbkey.pub /data/misc/adb/adb_keys

but the author wrote that it works only with rooted phones... and my broken one is not!!

Anyway I'll try and I'll write here the result of the test in order to share my experience.
[Android Q&A, Help & Troubleshooting] Tamagnun:
Nothing to do, it doesn't work...

The phone is switched on because if I connect it to the data cable on the PC I get this result:

C:\Users\rober>adb devices
List of devices attached
598261c1 unauthorized

and it is in RECOVERY MODE because I cannot find its IP address on the wifi router, but I cannot push the adbkey file:

C:\Users\rober>adb push C:\Users\rober\.android\adbkey.pub /data/misc/adb/adb_keys
adb: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

I don't have any idea to bypass the unauthorized state, due the host/client state it isn't possible to connect an external keyboard and the data cable at the same time, wireless keyboard cannot be paired without accessing the display so I dont' know how to proceed... sigh...

If someone has a suggestion I'll really appreciate it!
[Android Q&A, Help & Troubleshooting] IamTheBRAVE:
Found this. Can you try it?

Android - Enable ADB from recovery

Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com
[Android Q&A, Help & Troubleshooting] Renate:
What do you have for a screen lock? Swipe? Pattern? Numbers?

You need to tap and swipe the screen to get things done.

A plugged in mouse could do that if you only knew what you were doing.

If you have a digitizer (Wacom tablet) you can use that to do anything the screen can do.

Also, are you quite sure that the screen isn't responsive? It could be black but responsive.

I did a project to swipe patterns using a separate, rooted Android.

It works like a charm, but it's kind of a pain to set up.

See: https://xdaforums.com/t/accessing-my-phone-with-a-dead-screen.4542763/post-88013171

Hmm, it's actually more complicated.

I plug in a device and the authorization popup appears.

But, if I pull the plug, the popup disappears after a second.

You won't be able to get a USB digitizer working.

You'd need a Bluetooth digitizer, but that would have to be enabled too.

So you'd need the USB digitizer to enable the BT digitizer.

(By "digitizer" I mean any absolute pointing device.)

If there is an internal UART (hardware console) you might be able to simply type in the adb_keys.
[Android Q&A, Help & Troubleshooting] alecxs:
this script claims to by-pass the adb authorization by patching stock boot.img and resign with google test keys. it might work on locked bootloader (untested)

https://github.com/bkerler/android_universal

I don't know how it works, but you can hopefully write/flash partitions in EDL mode with this loader (untested)

https://xdaforums.com/t/no-auth-col...r-qualcomm-based-phones.4368989/post-88041131

there is also a linux executeable to reboot into EDL mode from fastboot

https://github.com/bkerler/edl

$ fastboot devices
$ ./fastpwn oem edl

to install the loader

$ python3 edlclient/Tools/fhloaderparse path/to/FHLoaderDir Loaders

if you don't have linux you can try the re_livedvdV4.iso from pendrive.

there is also executeable for windows to reboot EDL and another EDL tool for windows (credits: @Renate)

the downside of this, once you rebooted phone you cannot get back to its currently (AFU) unlocked state, which means all your files are no longer decrypted (BFU). you can install apps remotely only as long as the phone is decrypted and online, so maybe there is a better way (vysor?)
[Android Q&A, Help & Troubleshooting] Renate:
I see that the "fastpwn" is 12 MB. Seems a bit large. No idea what's in there.

Some abl's may support fastboot commands for getting to EDL.

I've never seen it clearly listed which do have that.

The standard fastboot filters all commands except for "oem".

fastboot tickle me elmo // will not even be sent because "tickle" is not on the command list
fastboot oem ridiculous command // will be sent since oem commands get a free pass

So if your device uses an oem command to get to edl it will work with the stock fastboot.

If it uses a special "first tier" command you will have to use a modified, lenient fastboot.
[Android Q&A, Help & Troubleshooting] Tamagnun:
Hi Iam, I found a similar page on GitHub and I tried to input the adb pull command (see my previous msg), but because the PC is not authorized there is no way to write anything on the phone by using abd.

Many thank for your tentative to help me.
[Android Q&A, Help & Troubleshooting] Tamagnun:
Hi Renate,

it is not possible to connect at the same time a USB keyboard (phone is the server by using an OTG cable) and a data cable (phone is the client in this situation) and as you have verified, when the data cable is disconnected, the grant message disappears...

I have a BT keyboard, but it is not possible to pair it to the smartphone working on a black screen, even if it was responsive.

Finally, I thing there isn't a way to bypass the grant message and authorize the phone "regularly", I think.

Where the UART should be present? Inside the phone? Uhhmmmm.... Even if I found it your idea would be to wire it by soldering directly on the mainboard? Too much difficult for my poor experience, sorry!

Many thanks for your answer.
[Android Q&A, Help & Troubleshooting] Tamagnun:
Before to start with replies, dear Alexc and Renate please let's apologize me because I'm absolutely newbie about these new devices, in order to clarify to you my (un)knowledge condition, let's consider that my last fw update was performed using the Odin tool on very old Samsung devices!

Thanks to your suggestions, now I know what is the fastboot and EDL (I read something on XDA and other sites), but I haven't understood if it is possible to read the userdata from one of these two boot states... anyway, I try to reply you, if you would want to continue to help me I'll be very grateful for this!

It is written that it is tested only up to Android 10, so I prefer to avoid to test this method on a smartphone that hasm't a working screen, it isn't possible to understand what happens on it.

https://github.com/bkerler/android_universal

I downloaded the firehose file for the chipset 855 but I'm not interested to flash a new firmware or similar...

OK, the previous is clear for me: now the smartphone is booted in fastboot mode and the utility can access it:

C:\Users\rober>fastboot --version
fastboot version 34.0.0-9570255
Installed as C:\Android-Recovery\platform-tools\fastboot.exe

C:\Users\rober>fastboot devices
598261c1 fastboot

Is the fastboot utility version the right one to operate on my smartphone?

Please let's explain me: if I'll reboot the phone to EDL (using fastpwn utility, fastboot oem command or another utility or method) I risk to lose my userdata ?

Sorry for the stupid question, but why I have to install a loader on the phone?

My Surface has Win10 and Ubuntu (I never use it but I have prepared a dual boot for any needs...).

I would prefer to use Windows utilities, but it is not mandatory...

Before to try to switch to EDL I need to understand if this operation will destroy my data or not, and what I can do from this EDL boot mode, I know it is posisble to flash the phone from scratch, but is it possible to read data by mounting phone partitions or similar?

For example, I listed the fastboot options and I found the possibility to FETCH a partition from the phone and copy it to the PC, this can help to access my data?

Maybe they are encrypted?

Do you have a schema or a list of all available partitions inside a MIUI 13 device? (I need to learn something before to proceed...)

So, the previous message is the reason I'm very carefull before to switch to EDL boot mode: is it enough to switch the phone to EDL in order to lock all data because they'll become definitively encrypted ?? :eek:

Please let's try to clarify me your suggestions and how to proceed...

Many many thanks for your patience
[Android Q&A, Help & Troubleshooting] Tamagnun:
Update: with the cmd fastboot getvar all I obtained the entire partions list, I tried to fetch one of this and the result is:

C:\Users\rober>fastboot fetch limits cache.ext4
fastboot: error: Unable to get max-fetch-size. Device does not support fetch command.

Not good, but at least I have answered to a couple of questions by myself... sigh...
[Android Q&A, Help & Troubleshooting] Tamagnun:
@alexc: two years and seven months ago you helped someone to retrieve userdata from a bricked MI 4C by suggesting the followiing process, can i do something similar on my MI 9T PRO?

What is the "programmer"?

As I wrote before, I downloaded the file prog_ufs_firehose_sdm855_ddr.elf but it is the firehose, not the programmer, isn't it ?

Many thanks, I spent all the night to try to acquire some knowledge, but I have too many dubts again...
[Android Q&A, Help & Troubleshooting] Renate:
When your Android boots it goes PBL (in ROM) -> xbl -> abl -> Android.

A Firehose loader is a custom replacement for xbl that it can load live.

Instead of loading all the rest of the stuff it just sits on USB and awaits commands.

Firehose, programmer, loader, .bin, .elf, .mbn can all be the same things.

Using EDL will not hurt your system or data (unlike fastboot unlock).

If you read back your userdata it will still be encrypted (if it was).

One thing that you can do is read back your entire image.

Then you will in any case be able to restore your device to exactly how it is right now.
[Android Q&A, Help & Troubleshooting] alecxs:
as Renate said, factory loader = firehose programmer. these files are rare for recent Xiaomi devices, the one linked is untested.

you can read and flash in EDL mode, so you can use the firehose programmer to read all partitions off device. booting into EDL mode won't erase anything, and you can exit EDL mode with Vol Down + Power (5 sec)

if you have linux simply follow the installation instructions. in case fastboot does not work check udev rules (or use sudo fastboot).
[Android Q&A, Help & Troubleshooting] Tamagnun:
Hi Renate, many thanks for your patience and your answers!

I think to have understood:

PBL = Primary BootLoader (is it commonly identified as the bootloader, isn't ? And it is the one that answer to the fastboot commands, I think...)

XBL = what is this?

ABL = maybe means Android BootLoader ?

Android is the OS, OK !! :cool:

Which BL does the recovery replace when the phone boots it ?

Good news!!

I was a little bit confusioned in my head with all that definitions, now it's more clear!

The prog_ufs_firehose_sdm855_ddr.elf I downloaded needs to be flashed on the phone or it is executed on the phone on the fly ? Maybe is it loaded in RAM or similar in order to be executed ?

Good news!

This means that I have to:

- boot the phone in fastboot mode

- try to switch it in EDL using one of the method explained by you and alexc in the previous posts

- run the prog_ufs_firehose_sdm855_ddr.elf

- download the userdata partition like a file on my laptop

- mount this file as ext4 formatted filesystem in order to access my data

I hadn't asked to Android to encrypt the filesystem, do you know if MIUI 13 (or Android 12) makes it by design ?

The other ext4 partitions could be downloaded and mounted too, isn't it ? (curiosity kill the cat!! :LOL:)

I think the mainboard (the display controller) is broken because during the different mount/dismount operations that I made in the past in order to replace the AMOLED and the battery a very tiny metallic piece is fallen into the small squared display connector (I didn't notice it immediately, ****!) and I'm quite sure it shorted the display controller and broke it.

So I'm not interested to flash the image on this phone or another one (I have a Xiaomi 12 Pro now) but only to access my personal data.

Many thanks for your explanation, sorry for my several questions and maybe the excessive prudence, but I don't want to brick it and because the black screen it is very difficult to understand what happens on the phone!

In the next days I won't have to spend on these operations, I'll keep you aware about my attempts on this threads.
[Android Q&A, Help & Troubleshooting] IamTheBRAVE:
Just from you asking so many questions, I myself learned a lot more than i knew so thanks to @Renate and @alecxs and you 👍
[Android Q&A, Help & Troubleshooting] Tamagnun:
Thank you alexc, you're writing the previous answer whilst I was replying to Renate, now I have only to follow your suggestions!

I think I will try to download the userdata partition (and maybe others also) on Windows system (fastboot+EDL+loader) because the fastboot is working well with this OS and when I'll have a copy of the images I'll mount them in Ubuntu to extract data.

I'll keep you aware on this thread.

Nice video in your signature!! :cool:

I understand that a lot of people ask the same things many times, and I can assure you I spent hours in looking for information, but please understand me: in two/three days (or better "nights", here in Italy is 1 am) I had to build the knowledge on this devices after years ans years of inactivity, in the next days I'll try to apply your suggestions!

Kind Regards
[Android Q&A, Help & Troubleshooting] Tamagnun:
Yeah!!

And I haven't renounced to try to write the adbkey file in the proper directory on the phone in order to authorize the communication between laptop and phone, so I'll be able to replicate the display of the device on the laptop monitor, but before to unlock, flash and other dangerous operations I need to retrieve the personal data I have into the phone's memory!
[Android Q&A, Help & Troubleshooting] Renate:
No, your normal fastboot is built into abl. fastbootd is built into recovery.

ROM means, literally ROM, physically built into the the IC and not changeable.

Not to be confused with the bad usage around here, "I built a new ROM for my Xiaomi 11".

The PBL knows about the IC, but has no idea what is connected.

The xbl is written/modified by the OEM so it knows important stuff, like what kind of dynamic RAM?, how much?, where's the charger circuit?, etc...

The Firehose locader, if compatible, is loaded into static RAM on the IC, because we don't have an xbl or Firehose loaded yet so we don't know where the dynamic RAM is.

No, because it's encoded.

I'm just telling you to make a 32GB backup so that if you screw up you can get back to here.

Reading your data requires you to fix what is broken on your device.
[Android Q&A, Help & Troubleshooting] Tamagnun:
OK, fastboot is part of the abl, not of the bootloder.

ROM is the read only memory, despite of many people confuse ROM with firmware, it's clear! :)

OK

OK, the xbl keeps specific device hardware information and configuration, clear.

Good! (y)

Ahi ahi ahi!!

And obvioulsy it isn't possible to decode it in any way, isn't it?

It's better than nothing, but it isn't so useful because...

... the idea to fix the display controller on the mainboard it is very difficult to do!

I'll be able to buy a new compatible TFT display in case the short circuit on the display connector had broken the display and not the mainboard, but normally a short circuit affects the driver (and this is part of the mainboard), not the "driven" (means the display).

Sigh!! :cry:

Anyway I'll try to download the userdata image, so I'll get experience with fastboot, EDL, loader, etc.etc.
[Android Q&A, Help & Troubleshooting] Renate:
No. We don't want to fix that. Why would we want to look at the screen?

We need a normal system running and ADB.

Putting Magisk on your device is one way to get rooted access.

Since Magisk uses a ramdisk (usually) you can add your adb_keys to / and your desktop will be authorized.

So, as I've been saying for the last few pages here, try that Firehose loader and see that it works.

We can pull the boot image and have it Magisk'ed on another device.
[Android Q&A, Help & Troubleshooting] alecxs:
@Renate nothing is possible in locked bootloader. unlocking bootloader is no option, because encryption keys are tied to lock state.

@Tamagnun the only hope is to find a way to authorize the adb connection. unlocking pin with OTG keyboard is not a big deal, but the adb connection on OTG is.

However it's worth a try with USB-C HDMI adapter to connect TV, then use the OTG for mouse/keyboard to connect the bluetooth keyboard. With the bluetooth keyboard it's finally possible to authorize adb.

it can be done all blind, but requires another phone that acts the same way. I have done this with two mouses taped together and clicked in parallel on both phones.

If you buy the same model, you can setup the same apps and pin, then create a list of keyboard input sequences needed to connect bluetooth keyboard. this sequence can be used on OTG keyboard for broken display.
[Android Q&A, Help & Troubleshooting] Renate:
As usual, we're locked in pointless speculation because the OP will not do a simple test.

On this device is EDL locked if the bootloader is locked?

We could discuss this for a week or somebody could just try it.

I just picked up a Walmart USB Type C to HDMI adapter.

Apparently none of my devices support it.
[Android Q&A, Help & Troubleshooting] alecxs:
EDL will work regardless of bootloader state of course. but modifications in boot.img (such as Magisk) won't boot on locked bootloader. except device is signed with google test keys, then AVBv2 re-signed boot.img could work.

but without a working loader the "blind" method is best option so far. or maybe some app that can remotely installed via google play. I never used Vysor but maybe it works out of the box.