Database Users

[Guide] Drivers & RRU Errors Solved

This guide is for anyone having issues with their HTC Hero drivers. It is aimed at Windows users and the guide was performed on Windows 7 x64 but relevant to older systems with minor adjustments (use common sense).
Most of it will be pictures, i'll try to fill in the rest in future and give it some layout but for the most part this process is easier to see than describe. Very much a work in progress.
Note: Unplug your phone from your pc for these processes until told otherwise. Remove any version of HTC Sync prior to 2.0.33 before doing these processes.
Might Need Apps:
HTC Sync for Android v1.5
HTC Sync for Android v2.1
USB Deview
Remove Old Drivers:
1. Start USBDeview by running the exe in the zip file
2. Remove any drivers which read like the following:
3. Reboot your machine
Installing The Correct Drivers:
1. Install the latest version of HTC Sync (2.0.40 or 3.0.5422)
2. Reboot
3. Right Click on Computer in your start menu and choose "Manage"
{
"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"
}
4. Select Device Manager on the left hand side.
5. Plug your phone into the PC and let the drivers install (you should see changes in device manager in real time). Under "ADB Interface" you should now see "My HTC" as seen in the picture.
This is correct and you should move onto the "Bootloader Drivers" section below. If you don't see this then carry on.
6. Right click on whatever you get under "ADB Interface" and do the following:
- Choose Update Driver Software...
- Browse my computer for driver software
- Let me pick from a list of device drivers on my computer
- Have Disk
- Browse
- C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 (last folder may be different)
- Select "androidusb.inf"
- OK
- Next
- Finish
You should now have the correct HTC Hero drivers installed. Move onto bootloader drivers section.
Bootloader Drivers:
Note: assumes you have the latest version of HTC Sync installed prior to doing this and have followed the driver process above to arrive here.
1. Switch off your phone and then hold Volume Down when you press the Power On button (Vol Down + Power).
2. You should have a white screen with some coloured text and 3 android's on skateboards. This is bootloader mode.
3. Now plug your phone into your pc and watch device manager change (this can take a minute or two). If "ADB Interface" doesn't show up or you get an "Unknown Device" error (perfectly normal - i think) then press the Back button and wait a couple of minutes then press volume Down again. This switches to Fastboot mode and back to Bootloader mode. AFAIK the drivers are the same so you should be able to do this process in either mode. You should get the driver "HTC Bootloader" or similar in your device manager. You need to repeat the steps above to change that to My HTC instead.
4. Right click on whatever you get under "ADB Interface" and do the following:- - Choose Update Driver Software...
- Browse my computer for driver software
- Let me pick from a list of device drivers on my computer
- Have Disk
- Browse
- C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 (last folder may be different)
- Select "androidusb.inf"
- OK
- Next
- Finish
You should now have the correct HTC Hero bootloader drivers installed. This will allow you to correctly install a RRU from HTC.

Brilliant guide! I have added it to my sig!

Nice one, thanks

Wow this worked 100% installed perfectly
thanks

Nexus 4 Not Recognized by ADB in Mac OS X

Hi Folks,
I am running Mac OS X 10.8.2 and I have ran into the following issues. I am trying to root a friend's Nexus 4 that's on 4.2.2, unlocked bootloader and USB debugging enabled/on.
I can easily root this on my Windows desktop but I thought I'd try out the Mac. Do note that I am not getting the "Allow USB Debugging" message that pops up on the phone when you connect it to a computer normally and you select Allow for the respective RSA key. The one that shows up after 4.2.2 is updated from 4.2.1.
I am not getting the above prompt when hooking up the phone to my Mac. *PS I removed the name of my MBP pro and the user name.
Okay so here are the two issues/scenarios:
1) I downloaded the latest ADB and Fastboot Mac OS X 64 bit files from the ADB dev tools website, etc. The files are "adb" and "fastboot"
When I type "./adb devices" since the "./" command is for Mac on the terminal, I get the following message and it does not show up any device listed.
{
"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"
}
Then when I type "./adb reboot-bootloader", I get the following:
__________________________________________________________________________________________________________
2) When I use an older adb and fastboot files from last year: "./adb_Mac" , "./fastboot_Mac" and "ADB-Install-Mac.sh", I get the following:
When I type in the adb devices command and the adb reboot-bootloader command:
The serial # shows up this time (Again I have crossed out half of it lol)
When typing in the reboot-bootloader command:
Now to my knowledge, I know that I am getting the device offline mode based on using the old ADB and Fastboot files. So the way to fix it, is to download the updated files but it doesn't result in anything at all.
With the updated ADB and fastboot files, and by booting into fastboot mode manually and then typing in ".fastboot devices", I get the Error Could Not Get Pipe Properties error in a loop.
Would appreciate the help folks!
T.I.A

Try this command
adb kill server
adb start server

scream4cheese said:
Try this command
adb kill server
adb start server
Click to expand...
Click to collapse
Beauty! I didn't know that it has to be done for the same in OS X. Query, does this have to be done every time or?

ADB Multi-Tool ( ADB logcat, pull push install and many more all in one tool )

Hello Everyone and Welcome to the ADB Multi-Tool thread by me​
Why i created this??
I believe we are all tired of typing into cmd to launch adb commands
So i created this tool to simplify our daily live and time typing and sometimes, making eror while typing
Basically its just simple having to press numbers to sideload files then typing the whole sentence in cmd​
Features of this ADB Multi-Tool
Has nearly all you need
ADB Install
ADB Push
ADB Sideload
ADB Pull
ADB Reboot and reboot recovery
*new ADB Logcat
*new ADB new file selector
Addon : Able to change promt font color ​
Coming features
Targeted for xperia devices with the ADB fastboot feature ( In progress testing )
Lots more unimaginable features comingggg
​
Screenies :
{
"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"
}
Downloads
ADB Multi-Tool v2 ​
Thanks - Credits
To Google for providing info on bat commands and their adb.exe
Windows for their command promt
Think I left you out or this is a copy of your work? PM me ​

Tutorials?
Tutorial on how to use
Extract the folder in zip to anywhere
Open it up and start ADB Multi-Tool.bat
Firstly add your files into the root of the folder
You can either select the file by entering option 5
( For ADB pull only in next release ) Type the file name exactly when asked for instance nFc.apk ( Case sensitive and file extension .zip .apk or .xxx needed )
Hey press what u want to do with that file
Bravo it should says done​
What is needed?
Your device drivers of course
Some brains​

Changelog and FAQ
Code:
[U] Version 1 [/U]
Initial release
[U]Version 2[/U]
UI redesign
File selection made easier alot
Added logcat
F.A.Q
Q : Hey it says cant find 'x' to install but i was sure i typed the file name correct
A : Make sure the file is in the root directory and make sure u added the file extension behind x.apk
Q : Hey eror: device not found
A : Make sure your device adb debugging mode is enabled in your developer options and your phone is connected
Q : It says what xxxxx permission denied?
A : Well make sure ADB permission is enabled in developer option or your su app, allow unknown install in security too
Q : Promt fc when I try to install or push the file, well i was sure i selected the file before doing so
A : Yes you did, but i am sure the file u selected contains spaces eg google camera.apk
Rename it to googlecamera.apk and I am sure it wont fc
Q : Hey I launch ADB logcat and i pressed any key, why nothing comes out? How do I stop it?
A : Well logcat is running, unless it says waiting-for-device, then you have to check your drivers properly. To stop logcat just press ctrl+c
Find your logcat.txt in the folder
Well many more are coming soon, so stay tuned
​

Lost ~180mb of RAM after flashing custom rom? Solution here.

This guide is for Mipad 1(mocha)
Download DiskInfo, if it says that you have only 1.8 GB of RAM, than this guide is for you.
1. You need to have ADB and fastboot drivers installed.
2. Download the nvboot.bin file, that is attached.
3. Put it into your ADB folder.
4. Enable USB debug on your device.
5. Open cmd in ADB folder and
A) Check if your device is attached properly.
Code:
adb devices
If it shows device status as 'device' everything is OK.
B)
Code:
adb reboot bootloader
If you see a rabbit on the screen, than everything is OK.
C) Write
Code:
fastboot flash nvtboot+nvtboot1 nvtboot.bin
C) Check the cmd's output, if you see OKAY there two times, than everything is OK.
D) Reboot.
E) ...
F) Profit!

Here is a file in an archive. Extract it to ADB folder.

correction
Star_king12 said:
Download DiskInfo, if it says that you have only 1.8 GB of RAM, than this guide is for you.
1. You need to have ADB and fastboot drivers installed.
2. Download the nvboot.bin file, that is attached.
3. Put it into your ADB folder.
4. Enable USB debug on your device.
5. Open cmd in ADB folder and
A) Check if your device is attached properly.
Code:
adb devices
If it shows device status as 'device' everything is OK.
B)
Code:
adb reboot bootloader
If you see a rabbit on the screen, than everything is OK.
C) Write
Code:
fastboot flash nvboot+nvboot1 nvboot.bin
C) Check the cmd's output, if you see OKAY there two times, than everything is OK.
D) Reboot.
E) ...
F) Profit!
Click to expand...
Click to collapse
Please, may be do you have a little error in last command line?.
where you put: fastboot flash nvboot+nvboot1 nvboot.bin
I must use: nvtboot in all words

JAMELGO said:
nvtboot in all words
Click to expand...
Click to collapse
Fixed.

Star_king12 said:
Fixed.
Click to expand...
Click to collapse
Ok!

Thanks for the guide

is this for mi pad 1 ????

ayushagarwal9753 said:
is this for mi pad 1 ????
Click to expand...
Click to collapse
Yup ;-;

Works! RAM went from 1.7 to 1.9Gigs.
Remember to unzip the file to get the .bin version.

not able
my device is not found in adb devices..kindly upload the required drivers for mi pad and clearly explain the procedure..whether the mi pad is to be put in fastboot or not..

rj4jhtconev said:
my device is not found in adb devices..kindly upload the required drivers for mi pad and clearly explain the procedure..whether the mi pad is to be put in fastboot or not..
Click to expand...
Click to collapse
I will not upload drivers here. The procedure is explained as clearly as possible.

Great!
Star_king12 said:
This guide is for Mipad 1(mocha)
Download DiskInfo, if it says that you have only 1.8 GB of RAM, than this guide is for you.
1. You need to have ADB and fastboot drivers installed.
2. Download the nvboot.bin file, that is attached.
3. Put it into your ADB folder.
4. Enable USB debug on your device.
5. Open cmd in ADB folder and
A) Check if your device is attached properly.
Code:
adb devices
If it shows device status as 'device' everything is OK.
B)
Code:
adb reboot bootloader
If you see a rabbit on the screen, than everything is OK.
C) Write
Code:
fastboot flash nvtboot+nvtboot1 nvtboot.bin
C) Check the cmd's output, if you see OKAY there two times, than everything is OK.
D) Reboot.
E) ...
F) Profit!
Click to expand...
Click to collapse
It worked! :fingers-crossed:
{
"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"
}

edconocerte said:
This guide is for Mipad 1(mocha)
Download DiskInfo, if it says that you have only 1.8 GB of RAM, than this guide is for you.
1. You need to have ADB and fastboot drivers installed.
2. Download the nvboot.bin file, that is attached.
3. Put it into your ADB folder.
4. Enable USB debug on your device.
5. Open cmd in ADB folder and
A) Check if your device is attached properly.
If it shows device status as 'device' everything is OK.
B)
If you see a rabbit on the screen, than everything is OK.
C) Write
It worked! :fingers-crossed:
Click to expand...
Click to collapse
Having 1.9GB and not 2GB is normal in custom ROM?

Jankev said:
Having 1.9GB and not 2GB is normal in custom ROM?
Click to expand...
Click to collapse
Yep. Stock and custom ROM show 1.9GB.

Star_king12 said:
Fixed.
Click to expand...
Click to collapse
If the system1 and 2 are merged what should I use of below?
Code:
fastboot flash nvtboot+nvtboot1 nvtboot.bin
Code:
fastboot flash nvtboot nvtboot.bin

Install TWRP Without Root. Xperia Z1 Lollipop 5.1.1

Fast go to the Setting/About phone then tap the "Build number" 5 time .
Then back now you show the "Developer options" Open it
then "On" it and on the "USB debugging" option .
Now Power Off your phone ,
Now Hold the 'Volume UP' button and connect with your pc.
Install ABD Driver on you pc.
If you don't have ADB Driver : www.mediafire.com/file/8p39tf9zudil916/adb-setup-1.4.3.exe
Download This File : www.mediafire.com/file/pvapp0t3oz2ty9m/Twrp.zip
Unzip The file , open folder , hold the "Shift Key" + Right Click !
Click "Open Commend windows here"
CMD commands :
fastboot devices
fastboot flash boot boot.img
fastboot reboot
Now press the Volume UP Button 10 Time..
Or, If you still have any problem check The Video : https://www.youtube.com/watch?v=qNbaHaBeZFo&feature=youtu.be
WoW You Have Done The work,:fingers-crossed: Enjoy IT..:good:

File Is Here !!!
If you don't have ADB Driver : www.mediafire.com/file/8p39tf9zudil916/adb-setup-1.4.3.exe
Download This TWRP File : www.mediafire.com/file/pvapp0t3oz2ty9m/Twrp.zip

I was under the impression that you cannot flash a kernel when the bootloader is locked?
Instead of making mirrors link the adb tools to its thread instead
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
https://forum.xda-developers.com/showthread.php?t=2588979

flash boot
emon415 said:
Fast go to the Setting/About phone then tap the "Build number" 5 time .
Then back now you show the "Developer options" Open it
then "On" it and on the "USB debugging" option .
Now Power Off your phone ,
Now Hold the 'Volume UP' button and connect with your pc.
Install ABD Driver on you pc.
If you don't have ADB Driver : www.mediafire.com/file/8p39tf9zudil916/adb-setup-1.4.3.exe
Download This File : www.mediafire.com/file/pvapp0t3oz2ty9m/Twrp.zip
Unzip The file , open folder , hold the "Shift Key" + Right Click !
Click "Open Commend windows here"
CMD commands :
fastboot devices
fastboot flash boot boot.img
fastboot reboot
Now press the Volume UP Button 10 Time..
Or, If you still have any problem check The Video : https://www.youtube.com/watch?v=qNbaHaBeZFo&feature=youtu.be
WoW You Have Done The work,:fingers-crossed: Enjoy IT..:good:
Click to expand...
Click to collapse
Hi i think i have a problem with the guide as you said i installed adb drviers and i opend cmd in the following location but when i turn my phone off then holding the volume up button and connect it to pc i hear that phone is connected and I see a blue light in notification light as well but i cant use the commands cause it wont show any device is connected
(Im already in dev mode and debuging usb is on)
thanks in advanced

HELP!installed driver! fastboot mode not work!I tried almost everything!
there is twrp 2.8.6.0 I want to update 3.3.1
{
"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"
}