Database Users

huawei x5 proplem

i just bought it today
my computer never read it i tried too much but it never read it just recharging
but i want root it but i cant becouse cant read it to install adb drivers
sory for my english

http://forum.xda-developers.com/showthread.php?t=803682
read this tutorial, you can root your phone easily

acremr said:
http://forum.xda-developers.com/showthread.php?t=803682
read this tutorial, you can root your phone easily
Click to expand...
Click to collapse
thanks
my proplem is
computer cant recognize my mobile to install usb drivers
i tried flash another firmware but still the same

most probably your computer does not have the device drivers.
install Hisuite:
http://www.huaweidevice.com/resource/mini/201105239635/hi_suite_en/
This software will also install the necessary drivers

Druida69 said:
most probably your computer does not have the device drivers.
install Hisuite:
http://www.huaweidevice.com/resource/mini/201105239635/hi_suite_en/
This software will also install the necessary drivers
Click to expand...
Click to collapse
thanks for fast replay
i installed but no way ...i think i have something on the mobile cuz it cant even give me alert

hummm
try go to settings > applications
then check the box "Unknown Sources"
Then below go to Development
check boxes "USB debugging" and "Allow Mock Loactions"
See if it works then
---------- Post added at 10:38 PM ---------- Previous post was at 10:36 PM ----------
if this doesn't work either try downloading the windows drivers for the U8800
http://www.mediafire.com/?5z6i5cv8l6br292

no it is not working also
this is my first time see this realy
could u help me use this code *#*#2846579#*#*
usb port setting
i have on it
normal mode
google mode
cts test mode
manufacture mode
authentication mode
other mode ( need the name of port)

[Q] nexus 4 bootloader problem

i bought my nexus 4 recently and now i thought of rooting it and installing cwm so when tried to update my device drivers when my nexus 4 is on in normal mode,thenn the drivers got updated but when i kept the device in fastboot mode and tryed to install the drivers but it says error 10 the windows found the drivers but error occurred while trying to install drivers,so due to this my device is not able to be rooted..so now what to do i need to root my nexus 4..can any one help :crying:

Just install the drivers from here, http://forum.xda-developers.com/showthread.php?t=1514942. Uninstall your current driver through device manager first.

DrFredPhD said:
Just install the drivers from here, http://forum.xda-developers.com/showthread.php?t=1514942. Uninstall your current driver through device manager first.
Click to expand...
Click to collapse
ur link cant solve my problem still the same problem continues.code 10 this device cannot start.

kchaitanya707 said:
ur link cant solve my problem still the same problem continues.code 10 this device cannot start.
Click to expand...
Click to collapse
attachments

kchaitanya707 said:
attachments
Click to expand...
Click to collapse
unninstall every driver(also delete)
reboot pc
and install using universal naked driver

opssemnik said:
unninstall every driver(also delete)
reboot pc
and install using universal naked driver
Click to expand...
Click to collapse
which one do i need to install android_apxusb or android_winusb.

opssemnik said:
unninstall every driver(also delete)
reboot pc
and install using universal naked driver
Click to expand...
Click to collapse
do i need to uninstall nexus 4 which is under portable devices in the device manager or only android composite ADB interface under android phone.

kchaitanya707 said:
do i need to uninstall nexus 4 which is under portable devices in the device manager or only android composite ADB interface under android phone.
Click to expand...
Click to collapse
every nexus/adb/android etc related driver
---------- Post added at 11:50 AM ---------- Previous post was at 11:50 AM ----------
kchaitanya707 said:
which one do i need to install android_apxusb or android_winusb.
Click to expand...
Click to collapse
nono, u download,extract to a folder,put the device in, and when you select to install the driver, select that you know the driver location, and then select the folder where u extracted it

[ROOT] Amazon Fire TV 2 (Updated)

NOTE: This rooting method has been superseded by @rbox with his recovery and pre-rooted images. I will not be updating this method for 5.0.5. Please see the following links to use the safer recovery rooting and updating method:
http://forum.xda-developers.com/fire-tv/orig-development/firetv-2-recovery-installer-t3309785
http://forum.xda-developers.com/fire-tv/development/firetv-2-recovery-t3309780
http://forum.xda-developers.com/fire-tv/development/firetv-2-sloane-prerooted-stock-images-t3309783
This is an updated thread for rooting the Amazon Fire TV 2. A simpler preloader rooting procedure was developed and has been tested by a number of users, but the guides were not updated until now. We have decided to publish the guides on the wiki section of the repo website since it allows other primary contributors to edit the guides as well so we can share the work (currently just @ImCoKeMaN). For those interested in jumping straight to it follow the link below:
https://gitlab.com/zeroepoch/aftv2-tools/wikis/home
I have also uploaded the associated zip files to this thread as sort of a mirror. The above guide provides support for Windows, Mac OS X, and Linux. As of right now the procedure supports 5.0.3.1 and 5.0.4, but a unique zip file is required for each version. It does check the version when starting the root procedure so you'll have a chance to grab the correct one just in case. The original scripts are all located and will continue to be maintained in the git repo located here:
https://gitlab.com/zeroepoch/aftv2-tools
This new thread will serve as a place to ask questions and discuss the newer rooting procedure while the old thread will be more historical or for advanced users who are trying some new things using the preloader interface.

What do you mean by "Power cycle the Fire TV"? Do I simply pull the power and replug it? Thanks.

SupaJ said:
What do you mean by "Power cycle the Fire TV"? Do I simply pull the power and replug it? Thanks.
Click to expand...
Click to collapse
yes

Where can I check to find out which mediatek vcom driver I should get? You say based on your model. Where do i check that?
I see my model but where do I cross reference my model to a particular mediatek driver?
NVM: I see that it's one link... my bad. Thought it was multiple links

Once I've rooted, will the root access persist through subsequent automatic system updates?

I tried the ubuntu way and it is stuck on waiting for preloader... I am using a USB transfer cable, ubuntu 15.10, vmware 12 pro, and I have no luck getting past running the initial python script.

BigMatza said:
Once I've rooted, will the root access persist through subsequent automatic system updates?
Click to expand...
Click to collapse
No. Applying OTAs after rooting is extremely dangerous. I'm working on recovery and prerooted update packages to allow safe updates.

I still can't get past "Waiting for preloader" this seems pretty straight forward, what am i missing? Thanks for any help.
---------- Post added at 06:35 AM ---------- Previous post was at 06:06 AM ----------
Have you found a fix for your issue?
---------- Post added at 06:36 AM ---------- Previous post was at 06:35 AM ----------
rester555 said:
I tried the ubuntu way and it is stuck on waiting for preloader... I am using a USB transfer cable, ubuntu 15.10, vmware 12 pro, and I have no luck getting past running the initial python script.
Click to expand...
Click to collapse
Have you found a fix for your issue yet?

Worked fine for me using Windows 8.1 64 bit, Fire OS - 5.0.3.1.
Fire TV 2 is now rooted. Thanks Zeroepoch

FatKris said:
I still can't get past "Waiting for preloader" this seems pretty straight forward, what am i missing? Thanks for any help.
---------- Post added at 06:35 AM ---------- Previous post was at 06:06 AM ----------
Have you found a fix for your issue?
---------- Post added at 06:36 AM ---------- Previous post was at 06:35 AM ----------
Have you found a fix for your issue yet?
Click to expand...
Click to collapse
It seems for me that the computer is not recognizing the fire TV correctly over the USB cable. I am wondering if USB A to A is different from a USB transfer cable. It sees my device as a combo drive.

OOPS! My Fire TV 2 is rebooting randomly after root. I have had 3 reboots in the space of half-hour. Please, wow do I fix this? Thanks.

rester555 said:
It seems for me that the computer is not recognizing the fire TV correctly over the USB cable. I am wondering if USB A to A is different from a USB transfer cable. It sees my device as a combo drive.
Click to expand...
Click to collapse
Yes there is a difference you need just an a to a cable with no box or chips in it that is your issue.
---------- Post added at 08:16 AM ---------- Previous post was at 08:12 AM ----------
rester555 said:
Where can I check to find out which mediatek vcom driver I should get? You say based on your model. Where do i check that?
I see my model but where do I cross reference my model to a particular mediatek driver?
NVM: I see that it's one link... my bad. Thought it was multiple links
Click to expand...
Click to collapse
You can use the driver from the driver folder in the zip. The other link was just for the install instructions. They are both going to work but the dl process was somewhat shady from that instruction site link so @zeroepoch included it in the zip.

ImCoKeMaN said:
You can use the driver from the driver folder in the zip. The other link was just for the install instructions. They are both going to work but the dl process was somewhat shady from that instruction site link so @zeroepoch included it in the zip.
Click to expand...
Click to collapse
There are three drivers in there. Install all of them?

no just need the x64 for most cases actually.

FatKris said:
I still can't get past "Waiting for preloader" this seems pretty straight forward, what am i missing? Thanks for any help.
---------- Post added at 06:35 AM ---------- Previous post was at 06:06 AM ----------
Have you found a fix for your issue?
---------- Post added at 06:36 AM ---------- Previous post was at 06:35 AM ----------
Have you found a fix for your issue yet?
Click to expand...
Click to collapse
Try disabling your Antivirus. Mine was preventing the script from getting past that step.

Thanks for this! Got my AFTV2 rooted using these updated tools, its very automated now! Great work guys.
I originally rooted 5.0.3.1 using ubuntu VM in the video guide, I updated to 5.0.4 and re-rooted with the updated tools in the same VM and it worked a treat, very simple. Literally one cmd in the bash shell.

I am using linux mint, i updated to 5.0.4 OTA, i tried the directions given, but getting an error: serial protocol mismatched.
Waiting for preloader...
Found port = /dev/ttyACM0
Handshake complete!
Extracting build.prop...
ERROR: Serial protocol mismatch

@zeroepoch my guess is the IO controller or the MediaTek device itself has extremely slow transfer speed. Hence why it takes 2 hours to write the addresses?
Edit: I finally got the right cable and I am in the process of writing the addresses from the image files. One of the addresses that is being written to it is hanging for a long time... Could it be that the transfer got interrupted... The prompt blinks at one address now for about 10 minutes?
So I read the readme and I think I have to rerun the batch file when it gets stuck.
EDIT 2: killed the process and it's running fine again after restarting.
And FINISHED! Thanks Zeroepoch and IMCOKEMAN!!

DigitalBobby said:
I am using linux mint, i updated to 5.0.4 OTA, i tried the directions given, but getting an error: serial protocol mismatched.
Waiting for preloader...
Found port = /dev/ttyACM0
Handshake complete!
Extracting build.prop...
ERROR: Serial protocol mismatch
Click to expand...
Click to collapse
That sounds like a flaky USB connection. It does a check in places where it echos back the data and its saying it mismatched.

Now to figure out what I want to do with root...

Android x86 issues HP pavilion x2

So I have a HP pavilion x2 10 detachable pc that has been nothing less then a pain in the grass its a lollipop IMG and it'll boot off USB i can get it going but there is no audio and after installation and I take USB out I get a kernel panic it won't let me run fsck it says my fstab file is missing (I can write that myself) but what the hell is going on here? There isn't even adb so its not like I can logcat this I'm bloody stumped

So just find its stock rom and reflash it.....there's nothing you can do ....by the way try to copy-paste adb folder and vold.fstab from any android device...hope this helps but as far as drivers are concerns i guess it is blown and gone case and you have no choice but to reflash or put in service centres....or contact tech support

Its not a actual android or came stock w win 8 I'm trying to convert it

Ive got it.so it is win 8 loaded and you want to use it as android tab.....well you can download the AOSP(Android Open Source Project) stock nexus or any sort of firmware from internet (github,android .com or at any other site) and dont forget to check android version and the SHA1 & MD5 values...........go download it...probably it is .iso or .img file like the way u download in android.........put it ,install or flash it....i guess this helps.or if you have any PC,download change my software android edition...... And connect that tab to PC(ensure rooted and fastboot unlock to prevent any sort of mishap and back it up..) Then tap to start...it will verify the device and then starts downloading os and driver then tab gets reboot and voila.......... ( update :::: visit http://www.android-x86.org/download and download any one of the version.... Here x86 is for the windows ...if it runs windows then any of them will be compatible......)
But DON'T FORGET TO DOWNLOAD PATCH FILES(IF ANY) AND READ THE .PDF AT END CAREFULLY IN ORDER TO ATTEMPT THIS. Hope this help but dont forget to backup and factory reset the device
---------- Post added at 08:38 AM ---------- Previous post was at 08:19 AM ----------
Download latest and stable one if available

Tanmoy Mitra said:
Ive got it.so it is win 8 loaded and you want to use it as android tab.....well you can download the AOSP(Android Open Source Project) stock nexus or any sort of firmware from internet (github,android .com or at any other site) and dont forget to check android version and the SHA1 & MD5 values...........go download it...probably it is .iso or .img file like the way u download in android.........put it ,install or flash it....i guess this helps.or if you have any PC,download change my software android edition...... And connect that tab to PC(ensure rooted and fastboot unlock to prevent any sort of mishap and back it up..) Then tap to start...it will verify the device and then starts downloading os and driver then tab gets reboot and voila.......... ( update :::: visit http://www.android-x86.org/download and download any one of the version.... Here x86 is for the windows ...if it runs windows then any of them will be compatible......)
But DON'T FORGET TO DOWNLOAD PATCH FILES(IF ANY) AND READ THE .PDF AT END CAREFULLY IN ORDER TO ATTEMPT THIS. Hope this help but dont forget to backup and factory reset the device
---------- Post added at 08:38 AM ---------- Previous post was at 08:19 AM ----------
Download latest and stable one if available
Click to expand...
Click to collapse
I've tried x86 that's what I'm having issues w I'll try a nexus version

audio issue with hp
Shiftydogit said:
Its not a actual android or came stock w win 8 I'm trying to convert it
Click to expand...
Click to collapse
Hello,
I have a laptop hp HP Pavilion x2 - 10-n105nl and I have instaled a custom rom : Bliss-v10.0-PC_Beta--OFFICIAL-20171229-1246android_x86_64.iso .
The installer I used for is : Androidx86-Installv26.0003.exe.
Everything works almost fine but the audio doesn't works at all. I would like to know if somebody installed some different Bliss version that suite better my tablet than mine.
There are a lot of differents bliss rom and maybe there is one that can works fine with my tablet
I will appreciate any answer or advice.
Thanks a lot
Max
p.s sorry for my english

[SOLVED] MTP driver issues Windows 10 Pro N

I have tried all the possible solutions described in the forum and in other places, but pitifully without success.
To this day, I have not been able to get Windows 10 Pro N to recognize my Nexus 6p.
The MTP driver appears as unsigned digitally. The ADB driver appears as correct.
As a solution I reinstalled Windows 10, provisionally solved. But then Windows was updated and the error returned.
Any suggestions?

Have you tried installing the Google driverset via the SDK Manager?

redduc900 said:
Have you tried installing the Google driverset via the SDK Manager?
Click to expand...
Click to collapse
How do I do what you mention?
Enviado desde mi Nexus 6P mediante Tapatalk

https://dl.google.com/android/repository/tools_r25.2.3-windows.zip
Once you have downloaded and installed the Android SDK Manager above you run the program as an administrator. Choose what you want to install. If you don't already have them you want Android SDK Tools and Android SDK-Platform-tools at the top (which would give you the most current ADB installation) and Google USB Driver is at the bottom under extras. You don't really need anything else unless you plan on doing Android programming. Just check what you want to install and click the button that says install packages.
---------- Post added at 11:36 PM ---------- Previous post was at 11:26 PM ----------
You could also go this route:
http://www.technobuzz.net/install-google-nexus-6p-usb-drivers/
which will install the Nexus drivers plus Huawei's phone interface program HiSuite. I must have installed this way because HiSuite opens every time I connect my Nexus 6P to the computer and I just close the program since I never use it.

jhs39 said:
https://dl.google.com/android/repository/tools_r25.2.3-windows.zip
Once you have downloaded and installed the Android SDK Manager above you run the program as an administrator. Choose what you want to install. If you don't already have them you want Android SDK Tools and Android SDK-Platform-tools at the top (which would give you the most current ADB installation) and Google USB Driver is at the bottom under extras. You don't really need anything else unless you plan on doing Android programming. Just check what you want to install and click the button that says install packages.
---------- Post added at 11:36 PM ---------- Previous post was at 11:26 PM ----------
You could also go this route:
http://www.technobuzz.net/install-google-nexus-6p-usb-drivers/
which will install the Nexus drivers plus Huawei's phone interface program HiSuite. I must have installed this way because HiSuite opens every time I connect my Nexus 6P to the computer and I just close the program since I never use it.
Click to expand...
Click to collapse
I tried the last option without success.
In the first description, what is the way to install the tools

yamilmanzur said:
I tried the last option without success.
In the first description, what is the way to install the tools
Click to expand...
Click to collapse
Read this thread
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page527

RoyJ said:
Read this thread
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page527
Click to expand...
Click to collapse
i will try

If you have any drivers installed now uninstall them by opening driver manager going to view->show hidden devices. Go to Android Device, and delete all the entries in there.
Now start by installing minimal adb and fastboot.
Then download this, extract it to a folder, plug in your phone. Make sure USB debugging is on
Then begin to follow this guide until you get to the have disk part. Close the video now. When you get to the have disk part, select android_winusb.inf from the folder I linked you to on Google Drive. Then you just next thru everything. This should work for your 6P.

I have solved using the Nexus toolkit. With this tool I can finally install the MTP drivers and that Windows recognizes my phone
Enviado desde mi Nexus 6P mediante Tapatalk

Honestly I rarely even connect my 6p to my desktop over usb anymore. MTP on win 10 is so atrocious. If I'm trying to transfer larger files or a picture folder windows will simply hang in the "calculating time required to copy" step, then trying to cancel will freeze everything. I've tried drivers, solutions etc to no avail. Best thing I've found is transferring files over wifi direct by using the ftp module in es file manager. You should definitely try it out, saves me lots of headaches!

longjohnsteve said:
Honestly I rarely even connect my 6p to my desktop over usb anymore. MTP on win 10 is so atrocious. If I'm trying to transfer larger files or a picture folder windows will simply hang in the "calculating time required to copy" step, then trying to cancel will freeze everything. I've tried drivers, solutions etc to no avail. Best thing I've found is transferring files over wifi direct by using the ftp module in es file manager. You should definitely try it out, saves me lots of headaches!
Click to expand...
Click to collapse
I did not know the function of transferring files via FTP. I was testing send anywhere app and was pleasantly surprised
Enviado desde mi Nexus 6P mediante Tapatalk

longjohnsteve said:
Honestly I rarely even connect my 6p to my desktop over usb anymore. MTP on win 10 is so atrocious. If I'm trying to transfer larger files or a picture folder windows will simply hang in the "calculating time required to copy" step, then trying to cancel will freeze everything. I've tried drivers, solutions etc to no avail. Best thing I've found is transferring files over wifi direct by using the ftp module in es file manager. You should definitely try it out, saves me lots of headaches!
Click to expand...
Click to collapse
I find transferring files via MTP on Windows 10 much faster and easier than using WiFi method. There must be something wrong with your drivers setup. It always works flawlessly for me.
---------- Post added at 04:05 AM ---------- Previous post was at 04:04 AM ----------
yamilmanzur said:
I have solved using the Nexus toolkit. With this tool I can finally install the MTP drivers and that Windows recognizes my phone
Enviado desde mi Nexus 6P mediante Tapatalk
Click to expand...
Click to collapse
That's good to know. Never really tried the various tool kits

quick update: MTP kept hanging at the calculating time required of a big transfer. Completely uninstalling and reinstalling every android driver through a toolkit has seemed to work so far.

mali_ said:
How did you do it? I'm using windows N version and I can't get mtp to work. I don't want to install the media feature pack.
Click to expand...
Click to collapse
I'm sorry but I can not help you, since my current phone is another and not the Nexus 6p

mali_ said:
But the issue is not limited to the nexus 6p. It is a windows issue in the N versions and occurs for any device that uses MTP.
Click to expand...
Click to collapse
May be, but I remember that with the Nexus toolkit I had solved it

mali_ said:
How did you do it? I'm using windows N version and I can't get mtp to work. I don't want to install the media feature pack.
Click to expand...
Click to collapse
If you can't get it figured out using the Google USB drivers, install the Nexus Root Toolkit (NRT) by WugFresh. It has a driver installation and testing tool. It will work. There is also a NRT support subforum dedicated to the N6P. You can also use MTP in TWRP natively if you have TWRP installed.

mali_ said:
Yes, I already tried that before posting. The driver installs fine but my phone isn't detected, exclamation mark in device manager.
Click to expand...
Click to collapse
Well you didn't try it properly because it works 100%. If you remove all the old drivers from Device manager *and* using USBDeview, it will work. Try it again and follow the instructions to the letter. You should also swap cables just in case, so you can rule out a defective or damaged cable. You'd be surprised how often this happens. NRT will install drivers for use with ADB and Fastboot. After you finish, run Step 4 to confirm. The toolkit is just automating what most people do manually. This is not an issue with Windows, you probably have an old USB driver conflicting, and that is what USBDeview is used for. What about using MTP in TWRP... Is it working?