TAKING A SCREENSHOT IN RECOVERY MODE VIA DDMS
INTRO - Many guys have the doubt that whether one can take a screenshot in recovery mode or Not ...... Well it is possible to take a screenshot in the recovery mode.let me help you to know how to....i made this guide soo Noob friendly, that too along with the picture's ..
The only way to take a screenshot in the recovery mode is via DDMS.....for more Awesome info on DDMS please have a look at this Thread.....(click me)
1) Install Java JDK :-Before installing the Android SDK, you’ll have to install Oracle’s Java development kit. You can download it from here...(click me !!)
Even if you already have the Java runtime (JRE) installed, you’ll need to install the JDK as well.
{
"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"
}
After installing Java JDK , you can now download the Android SDK from Google .
NOTE:- If you see a any type of Java-related error during installation, then download and install the x86 version of the JDK, not the x64 one ..
Click to expand...
Click to collapse
2) Installing android SDK:-Download Android SDK from here...(click me !!!)
After clicking on "DOWNLOAD FOR OTHER PLATFORMS" , you will get an extended menu ..
After downloading the .exe file , then Double click on the .exe file and install it in C:\ Drive or on whichever drive you wanna install .
Click to expand...
Click to collapse
Click to expand...
Click to collapse
3) Android SDK Setup
Click to expand...
Click to collapse
Once the Android SDK is downloaded and installed, launch the SDK Manager application from your Start menu.
Enable the Android SDK tools and SDK Platform-tools checkbox and click the Install button. This downloads and installs the platform-tools package, which contains ADB and other utilities.
After installing these packages , Go to the place where you installed ANDROID SDK . IN MY CASE , IT IS :-
Code:
C:\Program files(x86)l\Android\android-sdk\tools
If you used a different install location, you’ll find DDMS in the tools directory,inside your ANDROID-SDK directory .....
MOST IMPORTANT :- To DDMS with your device , you must Enable USB DEBUGGING and you install your device driver's
1) you must enable USB debugging on it. You’ll find this option under Developer Options on your device’s Settings screen
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
2)You must install your device drivers :- Individual OEM USB drivers for windows are available for each manufacturer and are listed in the official document ..
After you have downloaded you device drivers, then we have to install on our pc. for that :-
a) connect the device to the computer
b) right click on MY COMPUTER and click manage
c) go to devices > other devices and right click on device and select update driver software.
d) you should see an option to " BROWSE MY COMPUTER FOR DRIVER SOFTWARE" , which you nedd to click on and point to the location of your device driver installation file..
Click to expand...
Click to collapse
Click to expand...
Click to collapse
To test whether DDMS is working properly, connect your Android device to your computer using a USB cable
..Now it will show the devices connected ..
Now that you have sucessfully installed DDMS and now we are good to go further..
NOW GO TO ANDROID FOLDER AND OPEN TOOLS
2)NOW RUN MONITOR.bat AS ADMINISTRATOR
3)NOW ANDROID DEBUG MONITOR WILL APPEAR ..
TIME TO TAKE A SCREENSHOT....
Troubleshooting ;-
sometimes it will not recognize a Device in recovery mode..So in this case ,either uninstall your device drivers and then reinstall it OR refresh your device list in the DDMS device panel..... GOOD LUCK TAKING A SCREENSHOT :fingers-crossed:
I am not from this section..just waned to share my guide in your section..heres a link to my original guide.... link = click me...!!
Thank you,
P.007
Screenshots in recovery mode
Nice guide. Reserved for future use.
Sent from my Galaxy Ace GT-S5830 using xda premium
This is very useful, THANKS :good:
Clean and simple, thanks! :good:
it works on normal android system with me
but it wont work on the recovery (android system recovery) & on custom recovery (CWM)
even if i mount the usb storage under the recovery (monitor recognise the phone) , screenshot is just empty white
also in (android system recovery) the phone is recognised by monitor only when i press "adb / side load" thing
i want help :\
Related
guys um trying to recover my S3 internal memo
the thing is I can't get to backup my data
I can't even connect my phone through adb
um new to this, I did install the SDK manager, and I do have the adb.exe running in my task manager
this is what I get
postimage(dot)org/image/up4i85xet/
please help...
987123 said:
guys um trying to recover my S3 internal memo
the thing is I can't get to backup my data
I can't even connect my phone through adb
um new to this, I did install the SDK manager, and I do have the adb.exe running in my task manager
this is what I get
postimage(dot)org/image/up4i85xet/
please help...
Click to expand...
Click to collapse
Check my signature. Download the tool kit and choose any of the available devices, back up your data (Full backup), then when you want to restore your stuff, select Full Restore. It's as simple as that.
Galaxy S III is currently not fully available, but any of the device forms will do
Lg
Edit:
Oh, and you're doing it completely wrong. If you downloaded the SDK for Windows, all you need is the Windows shell (CMD, PowerShell).
And you only need to type in:
Code:
adb start-server
adb backup <-f<File location>.ab> <-apk><-system><-all><-shared>
and to restore:
Code:
adb start-server
adb restore <path-to-file>.ab
dude nothing is working
please take it easy on me, um not an expert tell me what to do step by step in details
thanx a lot mate
PS: if it does any better I can go to windows 7 I have my laptop right next to me
987123 said:
dude nothing is working
please take it easy on me, um not an expert tell me what to do step by step in details
thanx a lot mate
PS: if it does any better I can go to windows 7 I have my laptop right next to me
Click to expand...
Click to collapse
I wasn't going hard on you
Those were easy steps, you don't have to be an expert. I'm not one, either. I don't even know how to code in Java ^^
Like I said, just download my tool kit, hit "Thanks" on the OP and if you like the tool kit, buy the donate version :laugh:
The Galaxy S III form should be finished in the next few updates, but the next update (Coming sometime this week) shall have some even more impressive features which you can use
Lg
familyguy59 said:
I wasn't going hard on you
Those were easy steps, you don't have to be an expert. I'm not one, either. I don't even know how to code in Java ^^
Like I said, just download my tool kit, hit "Thanks" on the OP and if you like the tool kit, buy the donate version :laugh:
The Galaxy S III form should be finished in the next few updates, but the next update (Coming sometime this week) shall have some even more impressive features which you can use
Lg
Click to expand...
Click to collapse
I entered your link, cant find any tool kit, u mean usb drivers ? or adb drivers ?
Dude, Beatsleigher & M4gkman's Universal Android Toolkit... It's written in orange, next to my Twitter link...
Lg
Sent from my GT-I9300 using xda app-developers app
access nedaptem
familyguy59 said:
Dude, Beatsleigher & M4gkman's Universal Android Toolkit... It's written in orange, next to my Twitter link...
Lg
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
so I installed the "release install" first then the patch
but when I try to open it an error window pops up saying "a referral was returned from the server"
987123 said:
so I installed the "release install" first then the patch
but when I try to open it an error window pops up saying "a referral was returned from the server"
Click to expand...
Click to collapse
Please post such things in the development thread
And then also write which operating system you are using, which version you downloaded/you're using and then I can help you
Lg
familyguy59 said:
Please post such things in the development thread
And then also write which operating system you are using, which version you downloaded/you're using and then I can help you
Lg
Click to expand...
Click to collapse
sorry dude I was kinda on a hurry when I replied
I really appreciate your help
I used this version ( 2.0.3 ) the same thing is for the patch
I have a windows 8
987123 said:
sorry dude I was kinda on a hurry when I replied
I really appreciate your help
I used this version ( 2.0.3 ) the same thing is for the patch
I have a windows 8
Click to expand...
Click to collapse
Follow this to backup your phone (make sure u have installed drivers on comp) :
1. enable USB debugging Settings > Developer, enable developer options, then enable USB debugging
2. open the sdk and plug your device in
3.navigate to where adb is. you’ll find the adb.exe file in the platform-tools folder. With the default installation settings, the location is: C:\Users\"NAME"\AppData\Local\Android\Android-sdk\platform-tools.
(replace name with your account name)
4. In that folder hold shift and right click and select Open command window here.
5. type
Code:
adb devices
to test if your device can comunicate with adb
You should see a device in the list – if you see no devices, adb can’t communicate with your device because its driver isn’t installed properly.
6. type
Code:
adb backup -apk -shared -all -f C:\Users\NAME\backup.ab
(again replace the word name)
After running this command, you’ll have to agree to the backup on your device. You can also encrypt the backup with a password here, if you like.
{
"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"
}
Done!
To restore your backup in the future, run the following command:
Code:
adb restore C:\Users\NAME\backup.ab
(again replace the word name with your backups name)
Hit the thanks button if i helped
987123 said:
sorry dude I was kinda on a hurry when I replied
I really appreciate your help
I used this version ( 2.0.3 ) the same thing is for the patch
I have a windows 8
Click to expand...
Click to collapse
Thread only, please. That way other users have a chance to discuss the same problem and I really can treat it as a problem.
And you might want to have a look at this: http://sourceforge.net/p/universalat/discussion/general/thread/2e2a5c18/?limit=50#75bc <- That tells you how to write a bug report and that way I can really have a look at it and change stuff in necessary.
Lg
{
"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"
}
I would keep it short. Don't ask questions. This device dump is straight away coming from the device. So if you want to get started with something, here is the boot, system and recovery images. If you need anything else, let me know below in the comments. Please do not ask for review videos, benchmark tests, camera quality, blah, blah. You have the YU forum to ask such questions. Thank you and enjoy.
Download: here
reserved
good to see a dev like u here,its enough for expecting support for Yureka:good:
That was so quick mate thanks for sharing it
will look forward for more development
Can someone please upload the build.prop only?
CosmoDroid said:
Can someone please upload the build.prop only?
Click to expand...
Click to collapse
here
https://github.com/YUPlayGod/android_device_yu_tomato/blob/cm-11.0/system.prop
good work
Can anyone pls tell me how to flash this file??? And my phone is rooted and in cwm recovery.... But i want stock recovery to flash the update?? So plsss
Need to flash
Ashok sha said:
Can anyone pls tell me how to flash this file??? And my phone is rooted and in cwm recovery.... But i want stock recovery to flash the update?? So plsss
Click to expand...
Click to collapse
the recovery stock is inside the zip http://forum.xda-developers.com/yureka/development/tool-one-tool-t3006128
androidgalaxyman said:
the recovery stock is inside the zip http://forum.xda-developers.com/yureka/development/tool-one-tool-t3006128
Click to expand...
Click to collapse
Bro i downloaded the zip...now pls tell me how to flash this??
Steps
Ashok sha said:
Bro i downloaded the zip...now pls tell me how to flash this??
Click to expand...
Click to collapse
1. Enable android debugging mode in the mobile device.
2. using the usb cabel to connect and download & install PDA Net drivers.
3. Extract the package and go inside folder called "TREASU* like that.
4. click open the command line windows.
5. Type adb devise , it will show the list of devices connected. This is actually cross checking your devices properly connected with debugger.
6. Moreover go to the mobile setting, -> security -> tick unknown sources.
7. in the same command line go back upward one directory, you can find all*****.bat file, run it.
8. it will give the steps.
9. First do unlock the boot loader.
10. restart the mobile , then again install the customer recovery.
11. Then again using this tool to root.:laugh:
Tool is straightforward to use.
androidgalaxyman said:
1. Enable android debugging mode in the mobile device.
2. using the usb cabel to connect and download & install PDA Net drivers.
3. Extract the package and go inside folder called "TREASU* like that.
4. click open the command line windows.
5. Type adb devise , it will show the list of devices connected. This is actually cross checking your devices properly connected with debugger.
6. Moreover go to the mobile setting, -> security -> tick unknown sources.
7. in the same command line go back upward one directory, you can find all*****.bat file, run it.
8. it will give the steps.
9. First do unlock the boot loader.
10. restart the mobile , then again install the customer recovery.
11. Then again using this tool to root.:laugh:
Tool is straightforward to use.
Click to expand...
Click to collapse
Bro shall i use flashify app to install this recovery.img
Why u want to do that
Ashok sha said:
Bro shall i use flashify app to install this recovery.img
Click to expand...
Click to collapse
Hi Mate, whats the show stopper to this procedure to do with that tool. its good to use that.
I wanted to go back to the Stock CM11S but couldn't download the flashable zip from the Cyngn support page. Can anyone instruct how to use this dump to revert back to CM11S?
Download from Yu Forum and also follow easy steps mentioned there. Here is link
http://forums.yuplaygod.com/threads/factory-images-and-flashing-tools-official.2178/
Bricked Qualcomm 9008 mode
vishal_android freak said:
I would keep it short. Don't ask questions. This device dump is straight away coming from the device. So if you want to get started with something, here is the boot, system and recovery images. If you need anything else, let me know below in the comments. Please do not ask for review videos, benchmark tests, camera quality, blah, blah. You have the YU forum to ask such questions. Thank you and enjoy.
Download: here
Click to expand...
Click to collapse
Hi there, could you please provide me the complete eMMC dump of our Yu, off course except all partitions that could be found inside CM11 stock fastboot update zip (except these partitions: NON-HLOS/modem, boot, recovery, system, userdata, aboot, hyp, rpm, sbl1, tz).
I really need those files to recover my Yu. I'm leaving in Indonesia, so I can't get it replaced.
Hey all,
--> I'm trying to flash TWRP to my Sony Z5 Compact, but the flash fails during the writing process of the .img file
--> It gives me the following error: FAILED (remote: Command not allowed)
--> I am currently running build number 32.3.A.2.33
--> The phone is NOT rooted (but this should not matter I think... because I cant do that either if I cant write anything to my phone...)
Things that I have already done:
1. I enabled OEM unlocking in the developer options.
2. I enabled USB-Debugging in the developer options
3. The ADB and Fastboot drivers are working correctly
Does anyone know how I can fix this issue? I have already browsed the web for a fix, found a lot of people having the same issue, but nothing has worked for me.
Thanks in advance!
Horizon
i didnt see you unlocked the bootloader, i guess this is the problem
Here link:
https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
its the easy part,
besure you backup everything bootloader for me did factory rest
i did with CMD terminal
{
"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"
}
its always good idea to backup also DRM keys also unlock takes your warranty
A. Install the Android SDK and the device drivers
1. Download and install the Android SDK. The SDK Manager is included in Android Studio, but you don’t need to install more than the basic Android command line tools. These can be found at the bottom of the page.
Tip: Take note of the installation path, you may need to access specific files later.
a. If you are running Windows: You need to install additional drivers.
1. When completing the installation, open the Android SDK Manager and go to the Extras folder to install the Google USB driver.
2. Download and install an updated Fastboot driver. This is the standardandroid_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony devices.
3. Replace the original android_winusb.inf-file with the downloaded file in theusb_driver folder, located in the Android >sdk > extras > google folder on your computer.
b. If you’re running OSX or Linux, you are not required to install any additional drivers.
2. On your device, turn on USB debugging by going to Settings > Developer options and click to enable USB debugging.
a. If your device is Android Jelly Bean 4.2 or newer: Developer options are hidden by default. To enable, tap on Settings > About Phone > Build Version multiple times. Then, turn on USB debugging by going to Settings > Developer options.
B. Connect to Fastboot
1. Turn off your Xperia™ Z5 Compact.
2. Connect a USB-cable to your computer.
3. On your Xperia™ Z5 Compact, press the Volume up button at the same time as you connect the other end of the USB-cable.
a. Windows users: When asked for a driver, open the Devices and Printers directory, click on the fastboot driver and press Update. Browse and point towards the location of the new android_winbus.inf file.
4. When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder.
5. Enter the following command:
fastboot devices
Click to expand...
Click to collapse
6. Verify that you get an answer back without any errors.
C. Enter unlock key
WARNING! The command below contains your unlock key. If you perform this step, you will unlock the boot loader. This may void your warranty and/or any warranty from your operator.
1. If you still want to unlock the boot loader of your device, enter the following command:
fastboot -i 0x0fce oem unlock 0x(here your code you got by sony)
Click to expand...
Click to collapse
2. Verify that you get an answer back without any errors.
D. Done!
You have now unlocked the boot loader of your device
good luck, update if got it right
PS .i posted my imei by mistake hope i didnt miss to remove another :X
Hey man! Thanks for the quick response! Went right to work with it this morning... and it fixed it!
--> I completely missed the next steps from Sony. for some reason I thought that OEM unlocking option would do the magic lol..
--> After I unlocked it through cmd it was a breeze from there! Got my TWRP on there and the Lineage ROM
Thanks!
So I just got my phone today and I was trying to root it (with magisk boot patch) but after using the unlock app and enabling USB debugging fastboot still wasn't showing the device.
There was no option in the developer settings for OEM unlock..
I don't know if it is a bug or am I just missing something, is there anyone who can help me ?
Did you connect to wifi or mobile networks?, you need to be online
NisseGurra said:
Did you connect to wifi or mobile networks?, you need to be online
Click to expand...
Click to collapse
Yes of course otherwise the app won't unlock
*Is it ok for there to be no OEM unlcok option in the developers settings ?
danielbr14 said:
Yes of course otherwise the app won't unlock
Click to expand...
Click to collapse
Unlocked, rebooted, full wiped and add network again?
NisseGurra said:
Unlocked, rebooted, full wiped and add network again?
Click to expand...
Click to collapse
Yes, when I boot it clearly states that the bootloader is unlocked yet I don't have the OEM unlock option in the developers settings..
But if the bootloader are unlocked why you need the oem toggle?, Did you try to flash magic?
NisseGurra said:
But if the bootloader are unlocked why you need the oem toggle?, Did you try to flash magic?
Click to expand...
Click to collapse
Because the device still doesn't show up on fastboot (it does on ADB)
{
"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"
}
Did you try "fastboot devices"?
windows driver correct?
NisseGurra said:
Did you try "fastboot devices"?
windows driver correct?
Click to expand...
Click to collapse
No I tried to install everything that this guide says to, but the phone still shows up with an incorrect driver
Try the google drivers
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
NisseGurra said:
Try the google drivers
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Click to expand...
Click to collapse
I tried it but When I point it to the driver it says it can't find a driver for my device
danielbr14 said:
I tried it but When I point it to the driver it says it can't find a driver for my device View attachment 5681607
Click to expand...
Click to collapse
And if you try to install it from device manager?
NisseGurra said:
And if you try to install it from device manager?
Click to expand...
Click to collapse
That's what I did, is there a way to install it without the device manager?
danielbr14 said:
That's what I did, is there a way to install it without the device manager?
Click to expand...
Click to collapse
I would delete all installed drivers for Zenfone 9, reboot, change usb-port and install googles drivers.
But as this more an windows issue its difficult to assist remote
NisseGurra said:
I would delete all installed drivers for Zenfone 9, reboot, change usb-port and install googles drivers.
But as this more an windows issue its difficult to assist remote
Click to expand...
Click to collapse
I already tried it, and to be honest I don't think it is something that I am doing. adb detects the phone is both when it isbooted and when it is in the bootloader. Its only during fastboot that windows shows a missing driver the device...
The OEM Unlock toggle is usually unavailable (grayed out) when the bootloader is unlocked. It's possible this is the reason why it doesn't show up.
As for being unable to issue fastboot commands, it sounds to me like a driver issue, like others have stated.
OK, Finally managed to track down the correct driver thanks to this post and download this driver
FYI for anyone who encounters the same issue just open device manager and right click on your unrecgonized device (needs to be already in fastboot mode) the click update and select the driver from the zip file you just downloaded according to your PC then just finish installing it and everything should work.
danielbr14 said:
View attachment 5681497
No I tried to install everything that this guide says to, but the phone still shows up with an incorrect driver
Click to expand...
Click to collapse
Check windows update then optional update. There will be an Asus ADB driver to install.
danielbr14 said:
OK, Finally managed to track down the correct driver thanks to this post and download this driver
FYI for anyone who encounters the same issue just open device manager and right click on your unrecgonized device (needs to be already in fastboot mode) the click update and select the driver from the zip file you just downloaded according to your PC then just finish installing it and everything should work.
Click to expand...
Click to collapse
Just the answer I was looking for. Thank you for sharing!
Quite counter-intuitive that the trcick is to install Win8 drivers for Win10, but presumably they are the same but should have been downloaded automatically in Win10.
mickey36736 said:
Check windows update then optional update. There will be an Asus ADB driver to install.
Click to expand...
Click to collapse
Hopefully this is an option for most people, but, for the record, this did not work for me.
Windows 10 had a bunch of suggestions there but none of them were from Asus.
Perhaps it's glitched and they are in an invisible overflow - my optional driver section has exactly 10 entries. no more and no less, which I find a little suspicious.
Hi all,
first of all: yes, I've used the search function but I couldn't find a solution.
I have a Nord 2 5G device and want to install Evolution X Custom ROM.
I followed the instructions in this forum (and other websites) and managed to downgrade to OOS 11 in order to get into fastboot. The adb command to boot into fastboot mode also worked and my device is saying
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. If you want to exit fastboot mode, please long press volume up and power buttons simultaneously.
Click to expand...
Click to collapse
However, the fastboot command to flash TWRP does not work. On the command line I can only see
< waiting for any device >
Click to expand...
Click to collapse
and I continuously hear the Windows device attached/device detached chime. The device manager shows this:
{
"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"
}
After opening the properties, I can see this:
As it's German. It says:
The drivers for this device have not been installed. (Code 28).
There are no compatible drivers for this device.
Click to expand...
Click to collapse
So obviously I need additional drivers. I have downloaded the USB drivers from this website: https://developer.android.com/studio/run/win-usb, chose install from hard drive and pointed to the directory I have unzipped the driver set but Windows can't install them. I have also downloaded the OnePlus driver set from https://oneplusdriver.com/download-oneplus-driver and installed them.
Still, it doesn't work.
I am at the end of my rope now. What did I do wrong?
Thanks in advance!
I have same problem did you find solution
mckinley87 said:
Hi all,
first of all: yes, I've used the search function but I couldn't find a solution.
I have a Nord 2 5G device and want to install Evolution X Custom ROM.
I followed the instructions in this forum (and other websites) and managed to downgrade to OOS 11 in order to get into fastboot. The adb command to boot into fastboot mode also worked and my device is saying
However, the fastboot command to flash TWRP does not work. On the command line I can only see
and I continuously hear the Windows device attached/device detached chime. The device manager shows this:
View attachment 5835135
After opening the properties, I can see this:
View attachment 5835137
As it's German. It says:
So obviously I need additional drivers. I have downloaded the USB drivers from this website: https://developer.android.com/studio/run/win-usb, chose install from hard drive and pointed to the directory I have unzipped the driver set but Windows can't install them. I have also downloaded the OnePlus driver set from https://oneplusdriver.com/download-oneplus-driver and installed them.
Still, it doesn't work.
I am at the end of my rope now. What did I do wrong?
Thanks in advance!
Click to expand...
Click to collapse
Have you try to use platform-tools? It has adb and fastboot. I have always used that and no problem
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Look in Eigenshaften > Details > "Device instance path" (k.A. Gerätepfad?).
What's the VID/PID?
Is that in the stock INF file in android_winusb.inf?
If you want, you can just use Zadig drivers. I can give you "fastbogus.exe".
https://zadig.akeo.ie/
Select "WinUSB".
HamdiPiixel said:
I have same problem did you find solution
Click to expand...
Click to collapse
Yes, the thing is, I've installed the drivers in the wrong way. I'll try to give a step-by-step guide:
Go to Device Manager and find the Device (will have the yellow triangle. Right-click on it and choose upgrade driver (hope that's what's shown in the english version of Win 11). You'll see this:
Click the second option. You'll see this:
Here, choose the second option at the bottom. That's where I did it wrong. I selected the drivers in the dropdown menu and that doesn't work.
Click there...
and click there to select the diver *.inf file in the usb_driver folder.
That should work. It's important that you use the official Google Drivers (at least it was important here).
Hope that works.
mckinley87 said:
Yes, the thing is, I've installed the drivers in the wrong way. I'll try to give a step-by-step guide:
Go to Device Manager and find the Device (will have the yellow triangle. Right-click on it and choose upgrade driver (hope that's what's shown in the english version of Win 11). You'll see this:
View attachment 5856845Click the second option. You'll see this:
View attachment 5856867
Here, choose the second option at the bottom. That's where I did it wrong. I selected the drivers in the dropdown menu and that doesn't work.
View attachment 5856869
Click there...
View attachment 5856871
and click there to select the diver *.inf file in the usb_driver folder.
That should work. It's important that you use the official Google Drivers (at least it was important here).
Hope that works.
Click to expand...
Click to collapse
Hi,
I managed to install the ADB google drivers so I can now at least see Fastboot devices response properly but I do not know how to unlock the bootloader as the command "fastboot oem unlock" is not recognized and there is still no menu for the bootloader unlock (only the message on the black screen)
If anyone could help I would be be very grateful.
Thank you.
Best Regards
Lad