Hello everyone!
This is my first post here so I hope everything I try to explain is according to the rules as far as I read it.
I need to root my Doogee S88 pro mobile since I need test and develop some AR stuff. The standard apps are not accesible by the playstore so I need to bypass that. For doing that I need to root my phone (this is what I read at least).
So... I installed the doggee usb drivers from their website for my phone, usb debugging is activated and OEM is activated as well. I downloaded the most recen platform tools and the usb-cable should be fine since I find the phone with
Code:
adb devices
I execute the following commands:
Code:
adb devices
adb reboot bootloader
fastboot devices
I get the small Fastboot text in the lower left corner. Then if I try to execute
Code:
fastboot flashing unlock
or
fastboot flashing unlock-critical
I only get back <waiting for device>
As said I installed the usb drivers provided by doogee. But: In the device manager I can see the following:
{
"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"
}
Also I periodically (every 10 seconds) hear the sound as if a usb-device is disconnected. Afterwards the device manager refreshes the list.
So... it is a driver issue? I tried updating the drivers but picking manually the folder where driver files are located leads to no result. Automatic search as well. If it is a driver issue - where can I get the appropriate driver files? Thank you for any hint.
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
Unfortunately that didnt help either. Dunno... What I did was: I switched to my Lnux OS and over there it worked out of the box (only needed to install adb and fastboot from repositories).
Related
Hi, i am new to the xda developers forum and i got a question about the android debugger, since i'm clueless what to do after several hours of searching :silly:
I have an Sony Tablet S with ICS version 4.0.3.r1a (not rooted) and i want to use it for app developing.
Sadly sony does not provide drivers out of the box, so i have to search for working drivers myself. I know, they provide a description of lines, you have to add to the google driver, and i have tried two different methods to get adb working, but my devices still does not show up in the adb devices list.
method 1 (automated driver installer): http://forum.xda-developers.com/showthread.php?t=1488822
method 2 (google driver modification): http://esupport.sony.com/US/p/suppo...=684a6e492d1523ff4081def0a00b48a1&info_id=878
The device seems to use the driver, since it shows up as Android Composite ADB Interface in the devmgmt, but it still does not show up in the adb devices list.
Here some Facts about my os and settings:
My PC:
OS: Win7 ultimate x64
adb-version: 1.0.29
google usb-driver version: 7.0.0.1
My Tablet:
Android-Version: ICS 4.0.3.r1a
USB-Debugging is enabled
Other sources for apps are allowed
here some pictures of my file contents & devices:
{
"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"
}
My head is smoking atm, so i hope you know more about drivers and adb as i do and maybe someone of you had the same problem and can help me, i would be really greatful.
So long,
r3bel
Finally i found a solution of my problem...
As simple as it was, i could kick myself ... the driver seems to have a problem with my usb 3.0 controller, the adb finds the device if it is plugged into a usb 2.0 port.
maybe this helps others who have the same problem
I had same problem (it was working before) and I did system restore to get it to work.
Then I could able to root my tablet.
How did you solve the usb problem?
Hello everybody,
want to ask your advice in re: following issue
I am going to use nextbook NX868QW8G tablet as an embedded advertisement solution ie it should start when external power gets plugged in. I can find a normal tech desc of this model in the internet even on the official site.
It have almost the same look&hardware as NX785QC8G availabe at wallmart but have slightly another cpu mtk8382 and embedded 3g modem which was the decisive factor since we need tablets to be updated remotely.
Here are system settings:
{
"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 have done the following:
1) rooted device via cydia impactor - root check apps from gplay are saying its rooted now + it has auto instaled chainfire SU to the tablet. For some reasons cydia impactor thinks its HTC ONE X. I have installed a PdaNetA4150 and it also considers it as HTC phone. I have tried to install drivers for nextbook8 I have found in internet but window doesnt recognize them as appropriate. At the moment device is recognized as unknown MT65XX Android phone
2) run adb reboot-bootloader
3) run fastboot oem unlock
4) run fastboot oem off-mode-charge 0
I have tried doing it manually and through cydia impactor but in both cases the command thread for #3 and #4 seems to be in an infinite sleep - just displays "..." in command line shell and cydia impactor simply gets frozen for a couple of minutes then throws timeout exception.
I think its waiting my input after #3 however the screen remains black and it does nothing when I press on vol up/down/power buttons. Fastboot prints "OK [X sec]" when I call fastboot reboot from another shell window.
In regards to the adb drivers and etc - device is visible through both 'adb devices' and 'fastboot devices' commands. For some reasons
Please advice in which direction to seach and digg.
Any help will be highly appreciated,
Max
Hi, I have a problem, I keep receiving subscription ads requests, it seems that it is from my cellphone company, since you can see the sim image in there but I am not sure. This are some examples:
{
"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"
}
Background info: (running Android 6.01, 26.3.B.0.131)
So I used to be on a cell phone company which had this subcription ads request (Movistar), but I changed to another one which they say they do not have any of that (Tuenti), with the same number, and they are both owned by the same company (Otecel), so maybe some settings from the old operator were kept in the new ones, I have talk and talk and talk with them, and i just keep receiving this ads.
Is Root the solution?
Maybe if root my device, I can disable the sim services app, or I do not know something else, and I would not receive this ads again, or what do you guys recommend me.
Hello, have you tried to 'adb hide' or 'adb disable' the STK apk? No root required AFAIK
Pixelado said:
Hello, have you tried to 'adb hide' or 'adb disable' the STK apk? No root required AFAIK
Click to expand...
Click to collapse
No, I have not tried not, because I do not know how to do it, could you please teach me , please noob steps
Sorry for being so late haha.
I'll assume you're using Windows 7 or newer.
Steps:
- Get ADB and proper drivers for your devices (Flashtool ships with all of this)
- Enable dev settings on your phone
- Enable USB debugging. Disregard all warnings
- Connect your Xperia to your PC via USB cable
- Wait for drivers to install
- Open a terminal/command prompt on your PC, point it to a directory where you have an ADB executable (adb.exe) (you can do this by opening the flashtool libs folder, eg: c:\flashtool\x10flasherlib, and right-clicking anywhere on the window while keeping the SHIFT key pressed)
- Issue the following command:
-- adb devices
Your phone should ask for authorization now. Grant it
- Issue the following command(s):
-- adb shell (this gives you access to your device's terminal from your PC)
-- pm disable com.android.stk
If the above command fails, try:
-- pm hide com.android.stk
- You're done
You can avoid using a PC by using a terminal emulator on your device AFAIK. I might be wrong though.
Hello there,
my issue is that when i go in bootloader mode, i have a blackscreen, then my phone switch off. The system ui (custom rom Crdroid) and the recovery (orange fox) are working well.
I recognize also that when i reboot, i don't have anymore the MI logo where you have the status of your bootloader when it's unlocked.
More of it, when i plug it on windows , i cannot access to its usb storage (i tried also in mounting it through twrp, but same issue), nothing appears. For example, with an "adb devices" cmd command, no device can be found.
When i check the Windows devices manager, i can see an "unknown usb device" (i tried to force to reinstall drivers on it like the latest google usb driver, but windows refuse it, saying that it has the best and latest one for it).
{
"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"
}
Debugging mode is well enabled
Drivers have been reinstalled (the latest miflashtool install all what is needed)
Nothing appears on my smartphone when i plug it to windows (before i had a notification ot choose in charge mode, usb mode, etc...)
Plug to different usb port has been done without succeess
The phone doesn't appear in miflashtool obv
Restoring a previous backup didn't change the issue (i'm using the custom rom crdroid).
I guess all the things are linked but how i can fix it if i don't have access anymore to my bootloader mode to be able to flash some *.img via fastboot or if i cannot transfer files to my phone to operate in recovery, and more WHAT to do?
I hope you guys, will be able to help. The issue can be really annoying, and stuck me in "no rom update and no transfers of anything possible" situation.
Thank you beforehand
@bonbonboy
Try flashing the firmware through recovery from here https://androidfilehost.com/?fid=11410963190603850663 then reboot device and send it to bootloader via command adb reboot bootloader
It works like a charm!
Mi logo back, adb commands run, usb transfers work and no more error in the device manager.
You saved my day :good::good::good: Thanks a lot !
Hello,
I am trying to install the PACEField ROM on my Amazfit A1609 (Chinese version) but I can't list the watch in fastboot in order to boot on the temp root boot image.
Commands:
Code:
$ ./adb devices
List of devices attached
2b9e2c22 device
Code:
$./adb shell reboot bootloader
The watch reboot and displays the Fastboot screen
Code:
$./fastboot devices
Nothing listed and
Code:
$ ./fastboot getvar all
< waiting for any device >
Stays on "waiting for any device" (with and without sudo).
Details
ADB/Fastboot version:
I use ADB and fastboot from the Android SDK :
Code:
./adb --version
Android Debug Bridge version 1.0.40
Version 4986621
Code:
./fastboot --version
fastboot version 28.0.1-4986621
Android file transfer displays an error message (can't access device storage)
{
"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 use the original USB cable
I am on a the last MBP with USB C port so the watch is connected through a dongle (the HooToo's one).
I have seen that windows users have to install some drivers in order to get fastboot access. Is there any drivers available for OS X ?
What are the others possible problems ? Is there any other way to install the ROM without fastboot getting full access ?
Fastboot is broken on macOS since High Sierra and it doesn't seem that Google is bothered enough to fix it... The last version that works somehow for me is version 1.0.36 from this repo:
https://android.izzysoft.de/downloads
Somehow because it may hang after 1 or 2 commands, so you must restart the watch manually and start again.