[TUTORIAL]How to take Screenshots in Recovery mode [Tested][Noob Friendly] - Galaxy Ace S5830i General

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:​

Screenshots in recovery mode​​

Awesome Guide Puneeth :thumbup::thumbup:
With these Now it ll help to New users :thumbup::thumbup:
Sent from my Ace-i

I think it was already included in your DDMS guide?

Taking screenshots in recovery with ddms wasn't a success for me... I'll try this method also... Now, I'm reading your instructions carefully... Hope this time it'll result in success.
Sent from my GT-S5830i using xda app-developers app

brijeshep said:
Taking screenshots in recovery with ddms wasn't a success for me... I'll try this method also... Now, I'm reading your instructions carefully... Hope this time it'll result in success.
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
Good luck

Awesome!!! is this DDMS capable of sending commands to the phone while in recovery too? that would be indeed awesome.. I've had really bad luck signing zips for CWM xD

El_Dark said:
Awesome!!! is this DDMS capable of sending commands to the phone while in recovery too? that would be indeed awesome.. I've had really bad luck signing zips for CWM xD
Click to expand...
Click to collapse
You can use any adb command in recovery mode till its stock recovery
And you don't need to sign Flashable Zips

Related

ADB Driver - Access is Denied

So I just installed Windows 7 on my machine and was trying to ADB with my Android since I used it ALL the time on Windows XP.
I put the phone in Debug mode and plugged into my computer and told it the location of the driver. It seems to work well for a second and then it tells me that there was a problem installing the driver. It then says:
HTC ADB Composite Device Driver (not sure exactly of this...)
Access is Denied
Click to expand...
Click to collapse
Anyone else seeing anything similar on Vista or Windows 7? BTW I already tried this in Safe Mode as well.
Stigy said:
So I just installed Windows 7 on my machine and was trying to ADB with my Android since I used it ALL the time on Windows XP.
I put the phone in Debug mode and plugged into my computer and told it the location of the driver. It seems to work well for a second and then it tells me that there was a problem installing the driver. It then says:
Anyone else seeing anything similar on Vista or Windows 7? BTW I already tried this in Safe Mode as well.
Click to expand...
Click to collapse
I have mines working perfectly on Win7. Maybe you don't have admin rights on your computer? Just a guess
xidominicanoix said:
I have mines working perfectly on Win7. Maybe you don't have admin rights on your computer? Just a guess
Click to expand...
Click to collapse
Nope I have administrative rights and even tried it in safe mode.
Would you be able to zip up the drivers you used or link to where you downloaded them from?
So strange.
Even if you have admin rights, UAC can f it up.
Make sure you right click on command prompt and click "Run as Administrator"
Also, do you have x64? That requires a signed drivers. I don't remember if the ADB drivers were signed by microsoft, but if they aren't, it won't work unless you apply the work around
http://forum.xda-developers.com/showthread.php?t=532719
The link in this thread usbdeview seems to fix alot of driver issues
Stigy said:
Nope I have administrative rights and even tried it in safe mode.
Would you be able to zip up the drivers you used or link to where you downloaded them from?
So strange.
Click to expand...
Click to collapse
i got mines from the 1.6 sdk .. x64
Simple Solution
Here is a simple solution without having to read that long thread:
For future reference, here is how to install the drivers or fix the drivers should they not be working.
Everything you need is contained within this:
http://www.divshare.com/download/8845496-f72
This is the howto documentation
This is how to get your android phone to connect to you PC
to use functions like adb and other developer tools.
If you have installed the phone before but adb function dont work
then:
1) Run USBDeview
2) Select the list item(s) that have the word "android" within the description
3) Right Click > Uninstall
If you have done the above, or are plugging your phone in for the first time:
1) Plug in phone
2 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
2 b) If no message appears or you get a message saying drivers failed
to install. Goto device manager
2 b i) start > All Programs > accessories > run
type devmgmt.msc and press ok.
3 b) find the android device in device manager, it will have a warning icon
next to it and be in a section like unknown.
4 b) Right click and install driver
5 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
Click to expand...
Click to collapse
USBDeview is awesome but....
Even after removing all of the drivers associated with my device, as soon as I try to install the fresh new drivers, I still get "Access Denied" at the end of the install.
digimancer said:
Even after removing all of the drivers associated with my device, as soon as I try to install the fresh new drivers, I still get "Access Denied" at the end of the install.
Click to expand...
Click to collapse
I have this same issue on an Ideos U8150 and on XP... At one point in the past it was working (before I flashed Cyanogen 7). Since then I have tried numerous driver packages, both specific to my phone and generic, and have had no luck getting past the access denied error.. I have even gone as far as changing the registry permission as well as checking all of my folder permissions... I am stumped.
Adb root - run that from command prompt.
B-man007 said:
Even if you have admin rights, UAC can f it up.
Make sure you right click on command prompt and click "Run as Administrator"
Also, do you have x64? That requires a signed drivers. I don't remember if the ADB drivers were signed by microsoft, but if they aren't, it won't work unless you apply the work around
Click to expand...
Click to collapse
I know it a while ago since you posted this but still, it helped me fix the "Access denied" thing which i didn't know how to fix. I installed ADB drivers 3 times... anyways, tnx :good:
So If you are like me you had this same issue in 2022. Idk if it will be a fix for you but it was for me.
follow this youtube video for the exact setup so you can get hopfully the same out com to the T.
{
"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"
}
1. make sure you're in administrator mode for command prompt.
2. The file name has changed from what it was so instead of doing
cd adb\platform-tools_r30.0.4-windows\platform-tools
It's now this
cd adb\platform-tools\
This will get you to the correct path if you followed the file placement in the video.
next all you have to do is type
adb devices on the command prompt. to test if it worked
other things that you might have to try is seeing if the driver it self is being blocked. you might also have to turn off and back on developer mode. View other posts in this thread if it's still stuck for you. Hopefully I helped one person at least.

[TOOL] Android commander. ADB App/file manager/installer for windows

NOT TO BE CONFUSED WITH ANDROID CONTROL ON THE PORTAL TODAY
Check out this awesome tool!
install and adb/sqlite/apksigning files at bottom put together by me for you!
http://androidcommander.com/
http://forum.xda-developers.com/showthread.php?t=597098
Program Features:
Explore files:
- copy multiple files/dirs between Phone and PC
- copy multiple files/dirs between Phone folders
- delete multiple files/dirs from Phone
- new dir and rename options
- drag&drop multiple files/dirs in to progrm
- drag&drop files/dirs between program tabs
- partitions size info
- bookmarks
Manage apps:
- windows integration WINDOWS WILL "know" apk files! double click to install to phone!!!!!
- backup multiple apps to any dir on Phone/PC
- batch/single apps install
- install as private
- install on SD (Froyo+ only)
- update app
- batch/single uinstall apps
- uninstall with option to keep data or not
Console:
- type any shell command
- run sh script from PC
and more...
- flashing zip and img files
- options to reboot, reboot to recovery, reboot to bootloader, power off device
- device screenshots (beta)
- signing apk/zip files
{
"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"
}
Looks like just what I needed, huge THANKS!
Looks awesome. I wish that my PC (or my brain) wasn't broken.
I haven't been able to get ADB (of any kind, from any source) to run on my win7 64 bit machine...ever. I've had the SDK installed for a while now and have tried several times to get ADB working- today is no different.
Try the adb setup link in my sig!
But you don't need to know how to use adb to use this program
Edit: I got it. The link in your sig is what saved me. Checking this out now. Thanks!!
Well it work with windows xp?
Sent from my GT-I9000 using XDA Premium App
leezrd said:
Well it work with windows xp?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
well the site only says you need " Windows "
so probably.. no harm in trying...
TRusselo said:
well the site only says you need " Windows "
so probably.. no harm in trying...
Click to expand...
Click to collapse
Ok well thanx for helping with this wether works or not
Sent from my GT-I9000 using XDA Premium App
sorry but i dont have xp to try it and the authors website quoted in first post only says windows, im sure if there was more of a requirement he would have said so.
it runs on my win7 64x and that is usually the last supported windows so i would think xp is ok...
Doesn't recognize my phone. Droid Explorer does but this didn't. I already have adb installed on my win 7 64bit laptop.
did you point the program to where adb is installed?
TRusselo said:
did you point the program to where adb is installed?
Click to expand...
Click to collapse
Yes I did. Not sure why it won't recognize my phone.
Trouble getting hard adb root on Captivate GB 2.3.5 ROM
Android Commander 0.7.9.9 at http://androidcommander.com/ xda link http://forum.xda-developers.com/showthread.php?t=597098
I have a Samsung Captivate running a modified stock leaked GB 2.3.5 One flash ROM that has been Fugu rooted. TiBU, Rom Toolbox and other Super User apps all work.
So this program by PanPiotr looks like just what the noob in me is after, and I'm sure a few others out there too.
Once installed the program seems to be fine. I have one problem that I can't seem to overcome. That is getting a hard or adb root on the phone. I have tried to follow the instructions of PanPiotr but I don't have a boot.img file in my nandroid BU as outlined in his FAQs. Only cache.img, data.img, sd-ext.img and system.img I can use unyaffs-windows to extract the files in these but the default.prop appears to be calling to be loaded from ro.com.google.clientidbase=android-samsung, which I can't seem to find.
I can modify the default.prop ro.debuggable=0 to =1 with root explorer but just doing it in the root doesn't help. I can't seem to find out which IMG file in my nandroid BU has or how to modify the default.prop file loader to get the ro.debuggable=1 to take or stay.
Consequently the Root Access indicator always says Root Access:NO
Any help would be appreciated.
TYIA
Bud
May have this worked out.
So I flashed a custom rom and kernel. Connected Android commander to phone and I have Root access:OK. Program works great. Thanks PanPiotr.
On the brighter side of all this while in recovery mode of the new kernel (CornKernel_UCKJ3_v403) I found a way of switching the toggle for debugging enabled to on if that kernel works with the rom I was on then that will work. It should so I'll give that a try and let you know.
EDIT:
So I just finished and this worked brilliantly. Hope it helps someone else.
Bud
WOW nice tool very needed
+1
please add option for screen shots for more resolutions
Or to manually edit screen size CUSTOM.
I am using this on my sensation and image is captured but due to wrong resolution rows are shifted
Nice app bro.

Problem with USB Debugging

I bought SGN at Thursday and I want to install CWM so I can change ROMs.
But I cant get USB Debugging to work. When I connect USB cable to my phone it shows only icon for usb not for debugging in status bar. Of course USB Debugging is checked on in development.
My Android SDK is working fine because I also have ZTE Skate which SDK detects normally and I can use It.
I have installed: Java JDK 1.7, latest Android SDK and .net framework 4. But I don't think that problem is here...
Also because I cannot instal Samsung Kies ( it give me a message: some files are corrupted. if the problem persists please reinstall the program ) I installed SAMSUNG_USB_Driver_for_Mobile_Phones_1_5_6_0.zip hoping that this will help to Android SDK detect my phone but no luck...
I tried uninstalling every driver for samsung, deleted samsung kies, deleted java, android sdk and installed from scratch, tried another USB port, tried another USB cable but still no luck... In Device manager my phone is detected like 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"
}
I'm using Win7 x64 SP1
Can someone help me ?
Pablo87 said:
I bought SGN at Thursday and I want to install CWM so I can change ROMs.
But I cant get USB Debugging to work. When I connect USB cable to my phone it shows only icon for usb not for debugging in status bar. Of course USB Debugging is checked on in development.
My Android SDK is working fine because I also have ZTE Skate which SDK detects normally and I can use It.
I have installed: Java JDK 1.7, latest Android SDK and .net framework 4. But I don't think that problem is here...
Also because I cannot instal Samsung Kies ( it give me a message: some files are corrupted. if the problem persists please reinstall the program ) I installed SAMSUNG_USB_Driver_for_Mobile_Phones_1_5_6_0.zip hoping that this will help to Android SDK detect my phone but no luck...
I tried uninstalling every driver for samsung, deleted samsung kies, deleted java, android sdk and installed from scratch, tried another USB port, tried another USB cable but still no luck... In Device manager my phone is detected like this:
I'm using Win7 x64 SP1
Can someone help me ?
Click to expand...
Click to collapse
Check unknown sources under settings>security.
And
Under developer options uncheck adb over network
Sent From My GT-N7000 Using XDA Premium.
sahilarora2003 said:
Check unknown sources under settings>security.
And
Under developer options uncheck adb over network
Sent From My GT-N7000 Using XDA Premium.
Click to expand...
Click to collapse
You ment Aplications > Unknown Sources ?? Thas is checked.
And under Development there is no option ADB over network.
I'm using Android 2.3.5 ( KJ1 )
Someone else ??
http://forum.xda-developers.com/showthread.php?t=1424997
Here is dr.ketans guide for rooting,once rooted just follow directions from developer of the rom u wanna flash
Hope that helped
korado said:
http://forum.xda-developers.com/showthread.php?t=1424997
Here is dr.ketans guide for rooting,once rooted just follow directions from developer of the rom u wanna flash
Hope that helped
Click to expand...
Click to collapse
Did you read what I wrote ?? I cannot install CWM and root if my phone isn't recognized by Android SDK.
And I know to find guide for rooting and cwm by myself I'm not such a noob...
Pablo87 said:
Did you read what I wrote ?? I cannot install CWM and root if my phone isn't recognized by Android SDK.
And I know to find guide for rooting and cwm by myself I'm not such a noob...
Click to expand...
Click to collapse
But why do you need Android SDK to root Note on GB, I rooted it with Doomlord's method and I never installed SDK, Samsung drivers are enough for that.
I mean, in my personal opinion there is no sense in downloading the Android SDK, using ADB and manually entering commands if you don't have to.
What about dr.ketan sticky guide thread in development section?
And every device that i rooted and installed cwm recovery was recognized by adb. That is always the first step. Your device must be recognized by adb before you can run .bat file for rooting. When I type "adb devices" in cmd there is no my SGN listed. How can i root or install cwm without ADB ?
EDIT: I'm on stock gb 2.3.5
Sent from my GT-N7000 using Tapatalk 2
I fixed my problem !! Forget to change my android-sdk directory after reinstall.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Pablo>cd C:\Program Files (x86)\Android\android-sdk
C:\Program Files (x86)\Android\android-sdk>adb kill-server
C:\Program Files (x86)\Android\android-sdk>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
304D19E6105C9E2F device
C:\Program Files (x86)\Android\android-sdk>
And I'm rooted with installed CWM
I used this guide:
http://forum.xda-developers.com/showthread.php?t=1329360
Pablo87 said:
And I'm rooted with installed CWM
I used this guide:
http://forum.xda-developers.com/showthread.php?t=1329360
Click to expand...
Click to collapse
Cool, enjoy!!
Sent from my GT-N7000

[GUIDE] Set up Android SDK (ADB) for Windows 8 / 8.1 / [ADB][Bootloader][Fastboot]

Android SDK - Powerful tool and easy to set up for use with your HTC One M8
{
"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"
}
The Reason that you would want to use Android SDK is because its very easy, it's well updated and it just WORKS! There is much more use with HTC devices with adb then with Samsung when it comes to the daily things like splash screens, radio updates, firmware. You will be dealing a lot with the bootloader and fastboot flashing. So to help out, I will post a helpful guide to help you get started for use with the HTC One M8.​
Click to expand...
Click to collapse
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
1. Download Android SDK For Windows
2. Click the
either the 32bit version or 64bit version
3. Create a folder in the C: and name it Android. See below
4. Place adt-bundle-windows in the Android Folder you just created. Use WinZip, WinRAR or 7-Zip to extract the contents inside the folder. See Below
5. Once extracted, Double click SDK Manager and instal all 4.4.2 and 4.3 items and under tools (SDK Tools and Platform Tools). See Picture Below
6. After all packages are installed and updated, download the latest HTC Sync Manager and install once download completes
7. Once Sync Manager completes installation process, go to control panel and uninstall HTC Sync Manager only, you will see HTC Driver in there as well (LEAVE IT THERE)
8. Important, make sure you enable developer options and turn on USB Debugging. Instructions Below if you are unsure how to do that
1. Go to Settings > About > Software information > More > Tap Build Number 5x
2. Once you get notification saying Developer options is unlocked go back to > settings
3. Click Developer options
4. Add check in the box USB Debugging
9. Plug phone into the computer and let it install all the drivers, you should see pop ups.
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\sdk\platform-tools
2. In Command prompt type
Code:
adb devices
3. If your output shows your device attached like below, then you are good to go!!!
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\sdk\platform-tools
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
Reserve if needed
Updated OP
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks
Nice tutorial. This should help a lot of people.
via sexy M8.
Added to FAQ Guide Q8
BD619 said:
Added to FAQ Guide Q8
Click to expand...
Click to collapse
Thanks man
Sent from my HTC6525LVW using Tapatalk
very simple anyone should b able to follow these steps

Question My computer doesn't recognize the phone in fastboot even with drivers installed

Hi all,
I really need your help, my computer doesn't recognize the phone in fastboot, I've installed different drivers and none of them work, in device manager it appears as Android with the yellow exclamation mark. I've already enabled USB Debugging mode, not sure what am I missing, please help.
Check in another USB Port, use original xiaomi's wire...and install latest USB drivers
I have the same problem, i'm using the original xiaomi wire and already installed lastest usb drivers.. the fact is that when I plug in the cell phone in fastboot mode the computer keeps sounds as connecting and disconnecting the device (I used two wires and two different computers)
Yup exact same thing, I hope somebody knows how to fix it and help us out.
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Ricardo 182 said:
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Click to expand...
Click to collapse
I'll try that, thanks for the help.
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
seyren00 said:
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
Click to expand...
Click to collapse
Can you please tell me how do I do that?
Ricardo 182 said:
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Click to expand...
Click to collapse
Tried that but still don't recognize the phone
seyren00 said:
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
Click to expand...
Click to collapse
worked perfect for me! thank you!
liam_lost said:
Can you please tell me how do I do that?
Click to expand...
Click to collapse
{
"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"
}
seyren00 said:
View attachment 5365973
Click to expand...
Click to collapse
Thanks I tried but not sure why it shows this android one
liam_lost said:
Thanks I tried but not sure why it shows this android oneView attachment 5366067
Click to expand...
Click to collapse
Thats it bro, change that to Xiaomi Composite MDB interface, the first time my cellphone showed the same.
Ricardo 182 said:
Check in another USB Port, use original xiaomi's wire...and install latest USB drivers
Click to expand...
Click to collapse
Hi, where do I get the USB drivers? Even the official website says to make sure that "your PC has necessary drivers", but they don't provide any link where you can get them.
The Unlock Tool only has a "Check" button next to the version number, which says "5.5.224.24(Already latest)" and again, no drivers check. There are tons of fishy websites that claim to have the drivers and I have already tried several of them, but no success. Your help would be much appreciated.
Pino76 said:
Hi, where do I get the USB drivers? Even the official website says to make sure that "your PC has necessary drivers", but they don't provide any link where you can get them.
The Unlock Tool only has a "Check" button next to the version number, which says "5.5.224.24(Already latest)" and again, no drivers check. There are tons of fishy websites that claim to have the drivers and I have already tried several of them, but no success. Your help would be much appreciated.
Click to expand...
Click to collapse
https://c.mi.com/thread-3221402-1-0.html try using this guide bro.
seyren00 said:
https://c.mi.com/thread-3221402-1-0.html try using this guide bro.
Click to expand...
Click to collapse
Thank you, unfortunately, it didn't work for me. My device is still not showing up.
liam_lost said:
Hi all,
I really need your help, my computer doesn't recognize the phone in fastboot, I've installed different drivers and none of them work, in device manager it appears as Android with the yellow exclamation mark. I've already enabled USB Debugging mode, not sure what am I missing, please help.
Click to expand...
Click to collapse
Hi, after almost 2 days of constant researching and trying and failing and testing, I have finally figured it out! You need two things: MediaTek Driver and disabling Driver Signature Enforcement in Windows 10. It's because normally, the (64-bit) Windows 10 system won't allow you to install an unsigned driver and the Mediatek Driver is unsigned.
Here are the steps:
1. Press the Windows key on your keyboard, open PC settings
2. Go to Update & Security
3. Go to Recovery tab
4. Press & hold Shift key on your keyboard and click the Restart now button (in the Advanced startup section)
5. Select Troubleshoot ->Advanced setup -> Startup Settings and press Restart
6. Press 7 number key corresponding to "Disable driver signature enforcement" entry.
The system will now boot with the Driver Signature Enforcement disabled (it's going to be automatically enabled with the next restart). Download the Mediatek Driver (official source), unzip the file. Here's how I installed the driver:
1. Press the Windows key, type Device Manager and open the utility program
2. Click the top item in the list (your PC's name) and click Action in the menu and select Add Legacy Hardware.
3. Click Next in the Wizard, select Install hardware manually, and again Next and Next again.
4. Click Have Disk, Browse, navigate to the unzipped folder: SmartPhoneDriver > x64 > Unsigned infs and select the file android_winusb.inf. Click OK and select Media Tek Inc. in the left pane and then Next and Finish.
Your phone will now finally appear in the Unlock Tool.
This should work for all Note 10s users who also happen to have a 64-bit Windows 10 machine. Let me know how it went for you.
hey Guys, i´m new in the forum. But i had the same problem and i´m bringing the solution.
This error happens because Windows doesn´t recognize the bootloader, then you must install manually the bootloader´s driver and connect again your phone, so simple. I´m attaching the driver in this post.
Cheers.
download google usb driver: https://developer.android.com/studio/run/win-usb
connect phone to pc in fastboot mode. then go to device manager and update related driver named: android.
choose have disk and select Android_USB.inf file. then highlight Android bootloader interface and install driver. in win 10 must disable driver signature verification
seyren00 said:
View attachment 5365973
Click to expand...
Click to collapse
After searching for a long time, I found that this is the solution that works 100%. At last I was able to register the unlock of the bootloader today after a week of searching how to do it, since the driver did not work, thank you.

Categories

Resources