I have a ZEKI 10" TBQC1063B tablet. It apparently an updated version in that it now comes with Google Play Store app installed from the factory. It has Android 4.1.1.
I started to try to Root the device, but was unsuccessful.
In my quest to debug Rooting, I started trying playing with ADB directly. I quickly discovered I could not get to 'first base' with ADB.
Yes, I have USB DEBUGGING enabled, and when my tablet is plugged into my PC, the tablet shows that icon of the Android face in the status line in the lower right screen.
I started to try different drivers (reading that such might be the cause of ADB not working), even though all of the appear to be working OK when I check in Device Manager. One of the attempts I made at drivers led me to those offered as part of PDAnet. While using PDAnet's drivers didn't seem to help, I did stumble upon a CLUE. The CLUE is that while installing the PDAnet drivers, PDAnet did successfully install its own app onto my tablet. I think that such requires ADB to work, no? Could someone confirm such (or not)?
I tried a PC program called AdbDriverInstaller. When I first tried it, it reported a Device Status error of "Driver Incorrectly". So, I uninstalled that driver (I belive at that point it was the PDAnet one), and installed a new driver from a collection called UniversalAdbDriverSetup6. Now, that looked better. AdbDriverInstaller now shows:
{
"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"
}
Looking better?
My problem is that ADB DEVICES still shows no devices:
Does anyone know of anything else to try? This is about the limit of my expertise.
Try!
You can try using different port...i suggest you clean up all the Drivers and then install them correctly!:silly:
Kunal.Kene.1797 said:
You can try using different port...i suggest you clean up all the Drivers and then install them correctly!:silly:
Click to expand...
Click to collapse
Thanks, but I am not sure what you mean,
After trying each driver, I uninstalled and delete it. Is there something else I should be doing to "clean up" ?
How do you install them correctly, other than simply installed them? Device Manager seems to think the ADB device is working correctly.,
WaltA said:
Thanks, but I am not sure what you mean,
After trying each driver, I uninstalled and delete it. Is there something else I should be doing to "clean up" ?
How do you install them correctly, other than simply installed them? Device Manager seems to think the ADB device is working correctly.,
Click to expand...
Click to collapse
Unplug your tablet then reconnect it.
Type in cmd prompt:
Code:
adb kill-server (Hit ENTER)
adb start-server (Hit ENTER)
You should see your device..
Also, this is a good tool..makes adb system wide as well HERE
Also, not sure when Android implemented this, you might see a box up asking for you to grant the PC permission to use ADB, grant it
WaltA said:
Click to expand...
Click to collapse
lacoursiere18 said:
Unplug your tablet then reconnect it.
Type in cmd prompt:
Code:
adb kill-server (Hit ENTER)
adb start-server (Hit ENTER)
You should see your device..
Click to expand...
Click to collapse
I unplugged and plugged my tablet in a few times (over a course of several days while I tried to debug this on my own). Both my PC and my tablet have been powered on/off and rebooted over that time too.
I believe I showed I ready tried those commands, with no success.
TBQC1063B Zeki tablet
Zeki TBQC1063B
Any roms available? This one seems to be stuck. I can get to the boot list, but haven't found a new rom for it. Or even the factory rom.
Related
I've tried everything. IT WILL NOT recognize my phone.
When trying to install the drivers it says the Authenticode does not have permission. I got the damn drivers directly from Android.com but it still doesn't think its authentic. Because of this, o cannot get the computer to recognize it as an adb device to root the phone.
I'm going nuts now. 2 days with literally 8 to 10 hours of trying with no success.
Can someone please please PLEASE help me?
I was having the same issue. Install PDAnet. Works like a charm. The program installs the drivers for you. You can uninstall the program after you get the drivers working if you'd like.
http://www.junefabrics.com/android/
rk0 said:
I was having the same issue. Install PDAnet. Works like a charm. The program installs the drivers for you. You can uninstall the program after you get the drivers working if you'd like.
http://www.junefabrics.com/android/
Click to expand...
Click to collapse
Didn't work.
During "installing drivers" it gave me this error (err=0xe000023f).
uoY_redruM said:
Didn't work.
During "installing drivers" it gave me this error (err=0xe000023f).
Click to expand...
Click to collapse
http://www.junefabrics.com/android/driver.php
Tried USBDeview, doesn't seem to let me uninstall anything even though it says you can.
Nothing appears to work.
This is what I keep getting, no matter what I do:
{
"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"
}
and what makes no sense is when trying to manually install new hardware, it SHOWS there are authenticodes for those drivers:
theres a way of turning off driver signature checks, try that
http://www.google.com/search?q=windows+7+disable+driver+signature
Are you on Vista or a Windows server version?
I had the same issue, turned out it was a hardware bug.
I sent it to the repair center at HTC in United Kingdom and i had it returned 5-6 days after, working and with locked bootloader
britoso said:
theres a way of turning off driver signature checks, try that
http://www.google.com/search?q=windows+7+disable+driver+signature
Are you on Vista or a Windows server version?
Click to expand...
Click to collapse
Vista.
I've tried a few of those suggestions and non of worked. Most involved the bcedit trick but its disabled or doesn't exist in the newer security updates.
Vista 32 bits or Vista 64bits ?
in hardware management console what do you see ? yellow question mark ?
Sometimes you need to go in it and find your device to check the HID number and copy it manually in the driver *..inf files to be detect by your OS.
I remembered doing this for my G1 long time ago (years).
If you can, get your hands on another n1 or android device to see if its a hardware problem with the phone, which i doubt. Also try a diff OS.
uoY_redruM said:
I've tried everything. IT WILL NOT recognize my phone.
Click to expand...
Click to collapse
This is for windows 7 64bits : http://tinyurl.com/2548qh4
take a look @ post #4
Hope you solve your problem !
In case you have Windows 7 you can try the following.
http://www.killertechtips.com/2009/...gning-in-windows-7-using-group-policy-editor/
Are you installing the usb drivers using the utility in ADB? If not, delete the drivers in hardware manager, and try installing them with the utility.
I had no problems doing this on Vista, but I prefer to use ADB on Linux.
Sent from my Nexus One using XDA App
hey .
maybe i´ve got something for you.
download my file here
install the binaries and then reboot (i said you don't have to, but i think in your case it would be better)
EDIT: is the debug function enabled in your device?
OK, after a few hours and still no success with Vista, I went to storage and pulled out my personal PC I built that hasn't run in a few years thanks to corrupt hard drives.
I spent 4 hours repairing and fixing the hard drives and SUCCESS, I got it to detect it on my Windows XP PC.
NOW! Still not working! In the command prompt, it shows adb devices as one connected but still when I do an adb push nothing happens. Just recycles the adb menu....
Any suggestions?
Your first mistake is using a PC that you know is not working properly. Try a known working pc.
Sent from my Nexus One using XDA App
Try using a Linux distribution. Saves a lot of time and headache.
or just reinstall your windows. win7 would be better than vista.
malevolent000 said:
Your first mistake is using a PC that you know is not working properly. Try a known working pc.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The PC I'm using now IS working. It recognizes adb device but wont push the flash images or anything.
Two days ago I tried to use Easy Root ToolV11 to root my device that's running 14.1.1.A.0.402 Model D6503, it said "waiting for device".
I looked something up a bit and tried to install ADB driver, but nothing shown up in my detected ANDROID device list even though it was already plugged in to my PC.
I also tried to set up ADB PATH by following a tutorial in this thread http://forum.xda-developers.com/showthread.php?t=2559009 but it didn't work.
In my device manager my device is under "portable devices" instead "android devices"
I also tried towelroot on my phone. It said that my phone is rooted, but root checker said "This device does not have proper root access"
Ps. usb debugging mode and unknown sources are enabled
edit:
The driver that was install for my device is from microsoft. (see pictures below)
I uninstalled the driver and it was reinstall again every time i plugged my device in. I tried to update the driver, but it said that my driver is already up to date.
GalosSide said:
Two days ago I tried to use Easy Root ToolV11 to root my device that's running 14.1.1.A.0.402 Model D6503, it said "waiting for device".
I looked something up a bit and tried to install ADB driver, but nothing shown up in my detected ANDROID device list even though it was already plugged in to my PC.
I also tried to set up ADB PATH by following a tutorial in this thread http://forum.xda-developers.com/showthread.php?t=2559009 but it didn't work.
In my device manager my device is under "portable devices" instead "android devices"
I also tried towelroot on my phone. It said that my phone is rooted, but root checker said "This device does not have proper root access"
Ps. usb debugging mode and unknown sources are enabled
Click to expand...
Click to collapse
Are you using Windows 8?
cpumaster said:
Are you using Windows 8?
Click to expand...
Click to collapse
im using windows 7 sp1
also I just realize that i cannot use Sony PC Companion to do anything with my device it said that internet connection is required, but I am already connected.
Not sure but perhaps the drivers were not correctly installed. Try this?
http://forum.xda-developers.com/showthread.php?t=2635830
hush66 said:
Not sure but perhaps the drivers were not correctly installed. Try this?
http://forum.xda-developers.com/showthread.php?t=2635830
Click to expand...
Click to collapse
I'm still getting the same problem with the driver install.
I think i know what the problem is right now. The driver that was install for my device is from microsoft. (see pictures below)
{
"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 uninstalled the driver and it was reinstall again every time i plugged my device in. I tried to update the driver, but it said that my driver is already up to date.
Well, I just plugged in my Z2 to my PC and checked the driver details and it's exactly the same as yours. So it might not be an issue with the driver after all.
You mentioned that you have already done the ADB setup but it didn't work. When you said "it didn't work", do you mean the ADB couldn't be setup, or did you mean you still got the "waiting for device" message? To check if your ADB has been setup properly, go into the command prompt and type adb devices. You should see a serial number (of your phone) as the response.
And you should also have had the fastboot drivers installed. Use this tool to install fastboot drivers: http://forum.xda-developers.com/showthread.php?t=2588979
hush66 said:
Well, I just plugged in my Z2 to my PC and checked the driver details and it's exactly the same as yours. So it might not be an issue with the driver after all.
You mentioned that you have already done the ADB setup but it didn't work. When you said "it didn't work", do you mean the ADB couldn't be setup, or did you mean you still got the "waiting for device" message? To check if your ADB has been setup properly, go into the command prompt and type adb devices. You should see a serial number (of your phone) as the response.
And you should also have had the fastboot drivers installed. Use this tool to install fastboot drivers: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Finally it work!!!!
I'm rooting right now and it's stuck at cleaning up......what do i do now
GalosSide said:
Finally it work!!!!
I'm rooting right now and it's stuck at cleaning up......what do i do now
Click to expand...
Click to collapse
restart the install.bat file.. happens from time to time that it get stuck on cleaning up.
Check the official thread about Easy Root and you'll see loads of people had the same problem.
Just re-run the program and it will work.
Frantiic87a said:
restart the install.bat file.. happens from time to time that it get stuck on cleaning up.
Check the official thread about Easy Root and you'll see loads of people had the same problem.
Just re-run the program and it will work.
Click to expand...
Click to collapse
I did and it said "insmod: init_module '/data/local/tmp/wp_mod.ko' failed (File exists)"
edit:
I restart my phone and root again. It's finally rooted.
Thank you every one for helping me.
Thank you!
sorry we facing the same problem so please tell me if found a solution
ADB FASTBOOT Drivers
Nothing worked for me accept this one.
I went there downloaded this driver installed it and it did its magic.
https://www.driveridentifier.com/sc...14379&scanid=92D42FEE7DDD4826835F8C3C3611A400
Hi all,
think i bricked/ defected my Pace today. The idea was a mod with german language so i began to read here at xda for info. I'm on iOS now but modding on Android is nothing new for me, i modded some mobiles before, everthing workedtill today. I unlocked the bootloader and installed the mod, something went wrong i think, maybe i tried an incorrect image or something else, i don't know. After installing the watch wanted to update via OTA an after that it was shown as a Stratos in the Huami Amazfit Tool, sn was NULL an so on. The watch booted to os but the app was not able to read the QS Code for connection, touch doesn't work...
I can't say which ways i tried the last 6 to 8 hours to repair it and now i'm sure there is no bootloader/ software anymore on the watch. It starts with Amazfit Logo and stops with "No Command" & and the triangle. The only way to connect is in Fastboot, which shows chinese signs at the bottom of the display. There is no connection possible on ADB or otherwise.
Is there any way to get back the software on my watch? Maybe download mode which starts from my pc or something else? I'm on win 10 here, there is no linux machine or something else.
Thanks for reading
If you can get to fastboot and recovery, you have not deleted the bootloader.
Follow this guide: https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Quinny899 said:
If you can get to fastboot and recovery, you have not deleted the bootloader.
Follow this guide: https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Click to expand...
Click to collapse
Hi,
i tried this yesterday for about 10 to 15 attempts, but after step 4 there is no adb connection for step 5 and adb commands doesn't work. Getting the watch in fastboot is no problem anymore for me after last night
You have flashed Stratos firmware on your Pace, that's why touch didn't work. If the unbrick tutorial didn't work for you, then you should check your drivers: both drivers for adb and fastboot (they are different) should be installed and working properly. Sometimes you must re-connect the watch for the computer to detect it when the mode change, I usually keep Device Manager when I am using Windows to check this.
Or try AmazeROM installer, it has an option to start flashing from fastboot and it will guide you through the process.
Hi all,
sorry for my later post but under week i have no time for doing things like this here.
I checked adb and fastboot on the pc, installed system wide and works, fastboot drivers seems to be ok, but i have no idea how to check adb drivers. It's all the same, if i try this guide https://forum.xda-developers.com/sma...azfit-t3547300 or if i install amazeos with installer. The watch is recognized in fastboot but afterwards switching to adb there is no new connection, it's still in fastboot and does not switch to anything, i can restart it when amazeos installer script runs but nothing happens and if i let it run for about three hours the watch is still in fastboot and nothing happens there. In the device manager i see only an ADB Testing Device when in fastboot connected, on adb nothing happens there.
I tried everything on a clean win 7 machine, in this case the watch won't even recognize, so i could't run an installer or try to use the unbrick guide.
Just for information, it was Stratosfied which killed my watch in my mistake, but after that i think i deleted all with Amazfit Tools for doing the worst case for me here an unplugged it before reinstalling something else.
I attached some pics of the watch, first is after starting and directly after Amazfit logo, second is in fastboot with this method https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829, Point two there is not reachable, only point one fastboot, but in it i can't do anything though.
{
"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"
}
And for information, every fastboot command will be determind with "The command is not allowed"
Long story short:-
My device is locked usnig "surelock" so i don't have access to anything on it. I want to remove it and put any OS which will let me use my tab in normal way. I don't want any data from my tab, i just want it to function like a normal tablet. Due to this lock i almost can't do anything on my tablet. I am stuck only on one screen.
ABOUT DEVICE:-
TABLET - Lenovo Tab 4 10 TB-X304L
I don't know the android version but it was manufactured in 2018. and is now out of warranty.
WHAT I HAVE DONE TILL NOW
Tried Hard Reset:-
Ofcourse i tried doing a hard reset on it but in fastboot mode it didn't had any hard reset option. (since images are not allowed or maybe i don't know how to put my image using url i will type what it showed to me in italics.)
FASTBOOT MODE
PRODUCT_NAME -
VARIANT - QRD eMMC
BOOTLOADER VERSION-
BASEBAND NUMBER-
SECUREBOOT - enabled
DEVICE STATE - locked
now when i went in recovery mode it showed
REBOOT SYSTEM NOW
REBOOT TO BOOTLOADER
APPLY UPDATE FROM ADB
APPLY UPDATE FROM SD CARD
MOUNT/SYSTEM
VIEW RECOVERY LOGS
RUN GRAPHICS TEST
POWER OFF
2. Now since there is no hard reset so i tried to update the firmware using adb. After a lot of work i was able to find the firmware file for my tablet (still not sure if it is perfect for my tablet) other sites claimed to have it but asked for money.
Ok then i tried to flash the device it with the firmware using both adb and sd card but it showed this error in tablet. This error came while using sd card
E:footer is wrong
E: signature verification failed
E: error: 21
Installation aborted
While using adb from pc it detected the sideload but it showed this error
Total xfer: 0.00x
and Installation Aborted was showed in tablet.
FINALLY
I am finally posting it here to know what possible solutions are left for me. This tablet is quite expensive for me so i want to make it work badly. Please help if you can. I am okay with any operation system.
@Serjeel_Ranjan
Take note that with tablet's Stock Recovery you can only flash a Stock ROM / OTA - means a ROM / Patch that is signed by tablet's OEM/Carrier.
To get rid off of SureLock app you can try this
Code:
adb devices
adb shell "am kill com.gears42.surelock"
adb shell "am start -a android.intent.action.MAIN"
adb reboot
2nd command kills SureLock. 3rd command ask you for home app: a window comes up, select TouchWiz Home and select Always, Android home screen will come up.
Finally uninstall the SureLock app.
its shows this single error.
error-closed
{
"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"
}
plese tell if you are able to view the image.
@Serjeel_Ranjan
Screenshots provided shows you are running in wrong ADB mode.: Sideload mode.
To leave Sideload mode enter
Code:
adb devices
adb reboot
Then run the command sequence as previously listed
see when i do type the commands in fastboot mode. my device is not detected in adb mode but detected as fastboot device
how ever in sideload mode device is detected but no commands are running
@Serjeel_Ranjan
The "error:closed" you are receiving is most likely due to outdated and/or not-matching ADB driver.
Download the official Lenovo driver matching your device from here.
Good luck.
I installed the exact driver for my device from the website but that didn't made any difference.
Hello. I recently brought back my x820 to life. I need a phone.
It had TWRP and a custom rom. I tried to wipe and I actually wiped too much. So I had to install stock rom again because for some reason, lineage gave me an error at install (like it wasn't the right rom but it really was since I found it here https://download.lineageos.org/x2).
So I try to install TWRP again: twrp-3.7.0_9-0-x2.img found here: https://eu.dl.twrp.me/x2/
I launch ADB on a cmd prompt
- adb devices (List of devices attached e816a730 device). Super it's working and recognized
- adb reboot bootloader (phone miraculousely reboots in fastboot mode - YAY)
- fastboot devices ....... goes back to c:\ADB .... no devices found
So I reinstall ADB (from here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/). Y to all, reinstall drivers and everything. Reboot PC. Do everything again.....still the same weird fastboot < waiting for devices >.
Devloper options are enabled.
OEM is unlocked.
USB debugging is ON.
Cable has been changed.
Cables have been plugged on USB 2.0 ports (in the back), on 2 different computers.....still the same thing.
*#*#76937#*#* typed in and AT ports enabled.
Could someone have the kindness to help me figure out what's wrong with what I'm doing? I'm usually pretty comfortable with rooting, flashing etc....but I'm clueless here.
Thanks for any help or input.
First off, please install the Android SDK Platform Tools [instead of 15 seconds ADB installer]
Once done, install the Fastboot Drivers on your PC.
The ADB Tools [Platform Tools, 15 seconds installer, etc] don't have Fastboot binaries, so you will only be able to execute ADB-related commands and not the Fastboot ones.
Thanks.
I downloaded the fastboot drivers. But I can't seem to install them. In fastboot mode, I see this in my device manager:
{
"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 follow instructions from here: https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/ (your link). Although I'm on windows 10.
When I try to update driver, whatever I do, I get this error:
Which means "the folder doesn't contain any compatible driver for your device. If it contains a driver, make sure it can work for x64 computers".
So I'm pretty sure it's a driver problem. Is there a way to completely uninstall previous drivers and go from scratch again? Or any cleverer solution?
Try removing the faulty device then disable driver signature enforcement and install drivers.
https://avalonsciences.com/wp-conte...Signature-Verification-on-Windows-8-or-10.pdf
Thanks to both of you. Especially to you binary who pointed me on the right tutorial. I was doing something wrong when updating drivers in fastboot mode. I chose a device before locating the .inf file.
YES
NOOOOOOOOOOOOOOOOOOO
The bottom screen was taken from here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
"Show all devices" MUST be selected before going a step further apparently. All 3 drivers were installed flawlessly. TWRP was flashed successfully. I just need to figure out why it's still the old stock recovery showing up when I VOL+ and POWER start.
Cheers guys.
lucky24i said:
I just need to figure out why it's still the old stock recovery showing up when I VOL+ and POWER start.
Click to expand...
Click to collapse
Glad that you were able to rectify the driver issue. As far as TWRP is concerned, as soon as you flash it, boot straight to it [without booting to the system] and then check out the result.
In some instances, the device tends to replace TWRP with stock recovery upon boot. So avoid booting to the OS and use fastboot reboot recovery to straightaway boot to TWRP after flashing it.
Thanks. Working great