Database Info

[Q] Nexus S USB Mount Problems [Q]

My phone can only charge but not be recognized on USB, when I plug it into my computer it says it's unrecognizable from my computer (like an error pops up). It wasn't like this before I installed the new update to the cygeonmod rom. I tried going back to stock gingerbread, other roms. Like at least 4 roms i've tried I just don't know what to do now. Any Ideas?

Are you trying to access the storage or use development tools (like adb) via USB?
Also, have you tried with a different USB port (preferably one on the motherboard of your computer)?

WindSlash said:
Are you trying to access the storage or use development tools (like adb) via USB?
Also, have you tried with a different USB port (preferably one on the motherboard of your computer)?
Click to expand...
Click to collapse
I'm just trying to access the storage, I've tried different usb ports but it just keeps saying USB Device Not Recognized.

I'm assuming you're using Windows... can you go under Device Manager and see if there is one with an exclamation mark (!) when your device is plugged in?

WindSlash said:
I'm assuming you're using Windows... can you go under Device Manager and see if there is one with an exclamation mark (!) when your device is plugged in?
Click to expand...
Click to collapse
yes theres and exclamation mark when I plug it in and it says (!) Unknown Device.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Anyone got any solutions?

tdog1o1 said:
My phone can only charge but not be recognized on USB, when I plug it into my computer it says it's unrecognizable from my computer (like an error pops up). It wasn't like this before I installed the new update to the cygeonmod rom. I tried going back to stock gingerbread, other roms. Like at least 4 roms i've tried I just don't know what to do now. Any Ideas?
Click to expand...
Click to collapse
Had the same problem and it ended up being a faulty USB cable. Pretty unlikely, but try a different cable and see if that helps.

XK72 said:
Had the same problem and it ended up being a faulty USB cable. Pretty unlikely, but try a different cable and see if that helps.
Click to expand...
Click to collapse
I've tried different usb cables with different computers and with different usb slots in each computer. Nothing works. Is it possible that my nexus s is missing a file allowing me to connect usb to my computer? Because every computer I use it says USB DEVICE NOT RECOGNIZED so I was just wondering if that's the case.

tdog1o1 said:
I've tried different usb cables with different computers and with different usb slots in each computer. Nothing works. Is it possible that my nexus s is missing a file allowing me to connect usb to my computer? Because every computer I use it says USB DEVICE NOT RECOGNIZED so I was just wondering if that's the case.
Click to expand...
Click to collapse
It sounds like your problem can be isolated to the phone, but I'm not familiar with working in a Windows environment. I'd try booting into (the phone's) Recovery and seeing if you can mount the drive from there. Might help you isolate whether or not your issue is related to a particular volume.

XK72 said:
It sounds like your problem can be isolated to the phone, but I'm not familiar with working in a Windows environment. I'd try booting into (the phone's) Recovery and seeing if you can mount the drive from there. Might help you isolate whether or not your issue is related to a particular volume.
Click to expand...
Click to collapse
I tried that going into the phone's recovery mode and plugging in the usb cord and it still says the same thing. When I go into further like clicking the message it gives me a Code 43 warning on my computer. I also tried hard factory resetting my phone when I was on the phone with Samsung and that didn't work either. Everything was fine before I flashed Cygenmod rom on my phone everything was perfect.

tdog1o1 said:
I tried that going into the phone's recovery mode and plugging in the usb cord and it still says the same thing. When I go into further like clicking the message it gives me a Code 43 warning on my computer. I also tried hard factory resetting my phone when I was on the phone with Samsung and that didn't work either. Everything was fine before I flashed Cygenmod rom on my phone everything was perfect.
Click to expand...
Click to collapse
Have you installed the drivers from http://developer.android.com/sdk/win-usb.html?

XK72 said:
Have you installed the drivers from http://developer.android.com/sdk/win-usb.html?
Click to expand...
Click to collapse
I tried it and nothing is working.

Can you go back to Device Manager?
Double click on the "Unknown Device", then click on "Details" tab, under "Property", select "Hardware Ids", and take a screenshot of what's there?

WindSlash said:
Can you go back to Device Manager?
Double click on the "Unknown Device", then click on "Details" tab, under "Property", select "Hardware Ids", and take a screenshot of what's there?
Click to expand...
Click to collapse
Here you go.

Interesting... now let me ask you from another angle, with the phone connected and USB debugging on, are you able to access the phone using adb devices / fastboot?

download and install PDANet
worked like a charm for me, installed my usb drivers to my phone which i had problems with just like you.

WindSlash said:
Interesting... now let me ask you from another angle, with the phone connected and USB debugging on, are you able to access the phone using adb devices / fastboot?
Click to expand...
Click to collapse
No i'm not able to access it with fastboot or adb devices. All it says is USB device not recognized.

Nexus S Woes
I had the exact same story and errors as tdog1o1, and the ONLY fix I found useful was on an mp3 forum.
" I had code 43 problems with my usb ports until I found a thread on MSI's website. My front panel usb ports connected to a 9 pin usb header on the motherboard. Only 8 pins are needed. If pin 9 has a black ground wire then remove it. I didnt give this fix much hope but it fixed my problems! "
After many hours of driver installs, front usb port changes, and a dozen reboots, this actually worked!
I merely used the USB at the back of the computer and Voila!
Looks Wind Slash nailed it at the beginning of this thread.

Nexus S
I am having the exact problem, have found a solution.

[Q] Stuck in Clockwork Mod Recovery with no access to external SD

On friday i booted down my TF101 B70 and when i booted it back up could not get into Android, tried Cold Boot Linux tried Wipe Data. Did not work.
I do still have my ClockworkMod Recovery v5.5.0.4 which i keep booting into.
The problem is I am able to access the interal memory but my superwipe and Revolution HD files are not on there (if this is fixed, i will never make that mistake again)
I formatted my 2gb micro sd and loaded superwipe and revolutionHD, but cwm recovery does not see it.
I hooked up the TF101 to my pc to see if there was any way I can get access to the internal SD but i cannot connect as it is an unknown device on Win 7 64bit, which i cannot find drivers for. (Tried Asus Sync, Tries Asus' page for usb, even tried the APX drivers)
My question is how can i gain access to the internal SD to place my superwipe and revolution hd to flash and save my beloved TF101? is there a way i can access it with ADB? im pretty sure mine is the SDKv2 which is not accessible (sorry if i wrote that wrong)
any insight will help. Thanks!

use adb push command to send giles from the pc to the main storage or use gnufabio's recover install http://forum.xda-developers.com/showthread.php?t=1346180 to install a cwm version which could access external sd card

do i do adb push from and set the tf101 into apx mode or while in cwm recovery?

BiohazardPL said:
do i do adb push from and set the tf101 into apx mode or while in cwm recovery?
Click to expand...
Click to collapse
You can use ADB in recovery. DO NOT put the Superwipe script back in because once you use it, it will wipe everything again. Just ADB push your ROM file to internal sd and use option inside CWM to wipe your TF.

when i am in APX mode, usind adb shell i get " error: device not found"

when i am in recovery, win7 cannot find the right driver for the device. it just sits in "other devices" in device manager as "Transformer"
btw, thank you guys for your input.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is what Win 7 64bit shows when I am in ClockworkMod Recovery v5.5.0.4

I've never really used adb under win. have you installed the dev drivers from asus site? i don't have theexact url at the moment, i'm sorry.

from asus' site i only tried the asus sync and ASUS_Android_USB_drivers_for_Windows. i will see if they have dev drivers on their page.

Nothing that i could find on the Asus site:
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101&p=20&s=16
I also installed from SDK Manager "Google USB Driver" still nothing

Try the driver out of ViperMod.
http://forum.xda-developers.com/showthread.php?t=1427125
When you're in the Device manager right click and chose update driver.
Point it to the driver location.

tried those, still will not accept those tried from within the "Driver" folder and Android MTP and tethering each one by itself.
This driver business is driving me nuts.

What about ASUS sync? That's what work for me

yep same issue. I just tried on a win xp 32bit netbook.
when i connect the TF101 it shows up as an Unknown device but the device name is "Transformer" and no matter what driver i try, it does not install the driver.
maybe is there something weird about Clockwork Mod Rocovery v5.5.0.4

installed Asus sync on win xp 32, did not update the drivers, also went directly into c:\program files\ASUS\ASUS Drivers for Windows\ that also didnt like it.
what is it with this ver of CWM that it wont like the drivers?

BiohazardPL said:
yep same issue. I just tried on a win xp 32bit netbook.
when i connect the TF101 it shows up as an Unknown device but the device name is "Transformer" and no matter what driver i try, it does not install the driver.
maybe is there something weird about Clockwork Mod Rocovery v5.5.0.4
Click to expand...
Click to collapse
But people with that CWM used ADB to fix the same problem you are having though.
Can you find someone in real life who already has transformer and adb drivers working on their computer? You should plug your TF into their computer and see if ADB works. If adb still doesn't work, then it's safe to say you are screwed I think.
Or find a working transformer and plug that into your computer and see what happens with drivers.

there is something weird about it that i have never experianced using cwm on a sgs2 and sgs.
when i go into CWM, and try for instance "install from sd card" then "choose file from sdcard" it takes a good 5 minutes to pull up anything, all you see for a while is the cwm logo in the center, then after about 5 6 minutes all the folders i have on there appear.

another thing i just noticed right now, after i reboot from cwm there a destinct click from the device on the back where the camera is....
this is not looking good
EDIT: nvmd supposedly this is normal
http://www.transformerforums.com/forum/asus-transformer-general-discussions/761-click-noise-2.html

horndroid said:
But people with that CWM used ADB to fix the same problem you are having though.
Can you find someone in real life who already has transformer and adb drivers working on their computer? You should plug your TF into their computer and see if ADB works. If adb still doesn't work, then it's safe to say you are screwed I think.
Or find a working transformer and plug that into your computer and see what happens with drivers.
Click to expand...
Click to collapse
will try that as soon as i have access to one

Another uopdate,
I booted with the Up Vol + Power to Coldboot linux, after letting it sit there for about 10 mintes the MTP driver popped up on my win 7 64. the driver installs, but in device manager it says the "device cannot be started"

Trying to install /e/OS on FP3, but it hangs on fastboot on Windows 10

Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone point me into the right direction?

Nijs said:
Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
Can someone point me into the right direction?
Click to expand...
Click to collapse
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I do not see the interface you mention, however, I see 'Android' under 'other devices' and 'FP3' under 'portable devices' and 'Google Nexus ADB Interface' under SAMSUNG Android Phone (I did not install this, I assume Windows did this in the background).
Which option should I select to install the driver manually? Or none of them?

Doogee S68 Pro - Fastboot commands not working

Hi. So i have this issue. My brother has this phone (Doogee S68 Pro) and like a month ago almost every app in the system started to crash. Even 3rd party apps. I tried to update Android System WebView but it was already on latest version so i tried to opt-in to beta versions and no difference here. He also did make a factory reset through recovery mode and the problem still persists. So resetting the device to factory mode doesn't solve this issue. So i told him i could flash a custom ROM to see if that solves the problem. Only custom ROM for that device i could find was LineageOS 17.1. So i unlocked OEM, enabled USB debugging and adb commands work. Only issue is that when i access fastboot and type "fastboot devices" the command line doesn't output any text. It just send the command and nothing happens. Not even "waiting for any device". Only when i type some random stuff like "fastboot erjsifjes" then it says "waiting for any device". I also tried to install universal adb drivers, but the device shows up as Kedacom USB Device in device manager without any yellow exclamation mark or anything. It just shows up like it's properly installed and it works. But when i try to type any fastboot command other than "fastboot devices" it says "waiting for any device". I'm lost. I tried every possible way to make this work but no luck. What am i doing wrong? I disabled driver verification in Windows 10 (idk how it's named in english i'm using czech version but you know what i mean), so the drivers were installed properly. Is there any way how i can bypass the fastboot? I was looking in the recovery menu and there's a method to install "update" via ADB. So can i unlock bootloader this way? Help me please i don't know what to do now. I'm lost...

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adb commands work in system but not in fastboot

To get Fastboot working install the Doogee USB Driver suitable to your phone:
Doogee S68 Pro USB Driver for Windows (Official Mobile Driver)
Download the official Doogee S68 Pro USB Driver for your Doogee Mobile. We also provide all other Doogee Mobile drivers for free.
gsmusbdriver.com

Uhhh. I don't wanna disappoint you but i have already tried to install them. Both of the drivers included there . That was actually the first thing i tried. When the official drivers didn't work i tried installing universal ADB drivers, still same issue. Anyway i decided to buy a new phone. This piece of s*** is outdated anyways. If the apps didn't crash i wouldn't tried to flash custom ROM which i can't anyways.

Stupid question : Your phone is in Fastboot mode when you try the Fastboot commands right ?!
Are you using the latest version of the ADB and Fastboot Tools ?
You could try installing the following tool : https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Make sure you use a USB 2.0 port if possible!
If not then try a USB Hub between the phone and the PC or Laptop
Other things you could try :
- Use Windows 7 instead of anything newer.
- Use a Linux distro instead of Windows for the ADB and Fastboot part.
Good luck!

Update:
I got in touch with Doogee support and their technician. The problem was in trying to flash ROM in fastboot mode. They provide me SP Flash Tool which is used to flash ROMs, recovery, bootloader, etc. But the device needs to be turned off. This is kinda new for me, 'cause every time i was flashing ROMs or anything, i was doing it in fastboot mode with fastboot commands. The SP Flash Tool worked. Kinda. It allowed me to flash stock ROM successfully but it didn't solve the crashing apps issue. So yeah. I managed to progress further but still not the result i was hoping for. Still wanting to flash LineageOS 17.1 based on Android 10 in a hope that it'll solve my problem. When i tried flashing TWRP recovery straight up made for Doogee S68Pro with SP Flash Tool, it shows "Red State" message (see attachment) while booting the system (not able to enter recovery mode). Any ideas how to disable "verified boot"? I am able to access recovery through adb commands from system, however it enters the stock recovery menu, not TWRP which i did flashed. What am I doing wrong?

nero355 said:
Stupid question : Your phone is in Fastboot mode when you try the Fastboot commands right ?!
Are you using the latest version of the ADB and Fastboot Tools ?
You could try installing the following tool : https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Make sure you use a USB 2.0 port if possible!
If not then try a USB Hub between the phone and the PC or Laptop
Other things you could try :
- Use Windows 7 instead of anything newer.
- Use a Linux distro instead of Windows for the ADB and Fastboot part.
Good luck!
Click to expand...
Click to collapse
Yup.
- Device was in fastboot mode while typing fastboot commands. But not a single response from console.
- ADB and Fastboot was downloaded before creating this topic so i assume it was the latest version. Downloaded straight up from official Google page.
- Tried every single USB-C cable that i found, combined with every single USB port on my computer. (that took some time but need to be checked)
- To assure it was not my desktop PC what was potentially the problem, i also tried my brothers desktop PC with totally different HW components and operating system (his was W10, mine W11).
- I was thinking of creating dualboot system on my PC with W11 (primary) and W7 (secondary for this purpose) to try if that was the issue. (still open possibility)
- Same answer above

The drivers ( adb & fastboot ) you downloaded from Google are to be used with Google devices: you have to make use of the relevant drivers provided by DOGEE.

CaptainFedora said:
Update:
Still wanting to flash LineageOS 17.1 based on Android 10 in a hope that it'll solve my problem. When i tried flashing TWRP recovery straight up made for Doogee S68Pro with SP Flash Tool, it shows "Red State" message (see attachment) while booting the system (not able to enter recovery mode). Any ideas how to disable "verified boot"? I am able to access recovery through adb commands from system, however it enters the stock recovery menu, not TWRP which i did flashed. What am I doing wrong?
Click to expand...
Click to collapse
From : https://www.getdroidtips.com/lineage-os-17-1-doogee-s68-pro-android-10/
This should be the way : https://www.getdroidtips.com/twrp-recovery-doogee-s68-pro/
So no VBmeta.img needed it seems ?!

Yes! I was using the method mentioned in the first link. Never found that second link you provided. It looks very promising! I'm gonna try it in this week and post report. Man, that would be awesome.

You have to modify the usb driver .inf file. Add this rows to end of [Google.NTamd64] section:
;Doogee S68 Pro
%SingleBootLoaderInterface% = USB_Install, USB\VID_0E8D&PID_201C
%SingleAdbInterface% = USB_Install, USB\VID_0E8D&PID_201D&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E8D&PID_2006&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
Need a computer restart (shif+Restart in start menu) and have to switch off the signed drivers recommandation.

Hi ksanci ,and thank you very much it is work for me

Access phone on computer with broken screen

Basically, my Redmi note 8 pro screen broke and I can neither touch nor see anything on the screen I can't authorize it to connect to MTP because it defaults to charging, ADB only shows up in recovery, and fastboot the phone is connected to the internet via mobile data. My objective is to get vysor to recognize the device so I can mirror the screen I have Pixel Experience 13 any help would be awesome the device is still connected and accessible by google because i can ring it in find my devices
Maybe turning talkback on would help but it doesn't wanna turn on

Mystic1243 said:
Basically, my Redmi note 8 pro screen broke and I can neither touch nor see anything on the screen I can't authorize it to connect to MTP because it defaults to charging, ADB only shows up in recovery, and fastboot the phone is connected to the internet via mobile data. My objective is to get vysor to recognize the device so I can mirror the screen I have Pixel Experience 13 any help would be awesome the device is still connected and accessible by google because i can ring it in find my devices
Maybe turning talkback on would help but it doesn't wanna turn on
Click to expand...
Click to collapse
You can use scrpy via usb.
Download it here

mvikrant97 said:
You can use scrpy via usb.
Download it here
Click to expand...
Click to collapse
I can't authorize USB Debugging without unplugging from the computer and then plugging in the mouse to press Yes
And double clicking on the scrcpy executable flash a terminal window really quickly then exits

If USB Debugging successfully got enabled on phone, then you can run ADB shell commands when phone gets booted into Recovery mode.

jwoegerbauer said:
If USB Debugging successfully got enabled on phone, then you can run ADB shell commands when phone gets booted into Recovery mode.
Click to expand...
Click to collapse
I can see the phone through recovery mode yes but what commands can help me in this case

Mystic1243 said:
I can see the phone through recovery mode yes but what commands can help me in this case
Click to expand...
Click to collapse
The recovery is TWRP

Mystic1243 said:
I can't authorize USB Debugging without unplugging from the computer and then plugging in the mouse to press Yes
And double clicking on the scrcpy executable flash a terminal window really quickly then exits
Click to expand...
Click to collapse
I fixed my Nokia 8 Sirocco display today but the thing is my phone was already authorised to access ADB before,
so I have no problem in accessing it on my computer through SCRPY.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mvikrant97 said:
I fixed my Nokia 8 Sirocco display today but the thing is my phone was already authorised to access ADB before,
so I have no problem in accessing it on my computer through SCRPY.
View attachment 5867593
Click to expand...
Click to collapse
I can access ADB in Fastboot and recovery though and bootloader is unlocked , Know of any solutions?

You can't access ADB when in Fastboot mode: simply technically not possible.

jwoegerbauer said:
You can't access ADB when in Fastboot mode: simply technically not possible.
Click to expand...
Click to collapse
I can use fastboot commands is what i mean but idk what commands to use in either TWRP or fastboot

OMG: Take note that Fastboot deals with device's bootloader, whereas Recovery deals with device's Android OS.
Because phone has an SD-card slot ( ready for microSDXC cards - uses shared SIM slot ) then if the SD-card gets mounted by default at boot time then you can try to copy the Android data in question onto microSDXC card using Android's dd command.
FYI: Before copying the data make sure the partition where the data are housed gets decrypted.

jwoegerbauer said:
You can't access ADB when in Fastboot mode: simply technically not possible.
Click to expand...
Click to collapse
It's a bit of an uncommon combination, but you could configure to use both fastbootd and adb.

Mystic1243 said:
The recovery is TWRP
Click to expand...
Click to collapse
I'm aware that you might have thought about this but just out of curiosity.
I contacted a trusted local spare parts vendor in my area and he said that the display costs around ₹950.00 only in India which comes to $11.51 USD.
I repair phones so if you stay here in India I can assisst you in that. Please let me know.

mvikrant97 said:
I'm aware that you might have thought about this but just out of curiosity.
I contacted a trusted local spare parts vendor in my area and he said that the display costs around ₹950.00 only in India which comes to $11.51 USD.
View attachment 5867673
I repair phones so if you stay here in India I can assisst you in that. Please let me know.
Click to expand...
Click to collapse
No sadly im not in india sorry

jwoegerbauer said:
OMG: Take note that Fastboot deals with device's bootloader, whereas Recovery deals with device's Android OS.
Because phone has an SD-card slot ( ready for microSDXC cards - uses shared SIM slot ) then if the SD-card gets mounted by default at boot time then you can try to copy the Android data in question onto microSDXC card using Android's dd command.
FYI: Before copying the data make sure the partition where the data are housed gets decrypted.
Click to expand...
Click to collapse
I can access the data already in TWRP i just cant extract it because its encrypted and TWRP doesn't support PE encryption AFAIK

What is PE encryption? Never heard of this.

PE = Pixel Experience FBEv2 encryption. one can enable usb-debugging and authorize RSA from init script, no need to decrypt userdata in TWRP. we can place init scripts in system/etc/init or vendor/etc/init or if rooted with Magisk in boot.img overlay.d
Accessing my phone with a dead screen
So my phone screen connector was liquid damaged. No touch or display. It's an Essential Phone which supports HDMI output, however I can't unlock it because I don't see the lock screen on the monitor I just see a lock icon. I have...
forum.xda-developers.com