I have a ICOO D70PROII tablet, with a Rockchip 3066. After installing the Chainfire 3D driver, the tablet stucks at ICOO boot screen, even before the Android animation. I've started the tablet in recovery mode (appears the Android guy with the open bonnet and a red exclamation point).
I have the ADB drivers installed, i can access to almost everything in the ADB tool, except the "adb shell" command, even pushing up the mksh file to /system/bin.
The fastboot doesn't work, because the tablet turns off the screen, but appears in Device Manager an unknown driver, that I can't find the driver for it.
The RKBatchTool 1.3 and 1.5 doesn't recognize the tablet.
The only way I can see to fix this is doing the job in ADB command line, but the only way that I know to uninstall the Chainfire 3D driver is in Shell. Could anyone help me in this problem?
I made a small and simple recording showing the driver, RKBatchTool error and ADB errors. (please copy the following link to the browser's URL bar, I can't post direct links)
youtube.com/watch?v=4iQi5SkKGe4
Best regards and thank you in advance,
Ivan Santos.
IvanSantosPT said:
I have a ICOO D70PROII tablet, with a Rockchip 3066. After installing the Chainfire 3D driver, the tablet stucks at ICOO boot screen, even before the Android animation. I've started the tablet in recovery mode (appears the Android guy with the open bonnet and a red exclamation point).
I have the ADB drivers installed, i can access to almost everything in the ADB tool, except the "adb shell" command, even pushing up the mksh file to /system/bin.
The fastboot doesn't work, because the tablet turns off the screen, but appears in Device Manager an unknown driver, that I can't find the driver for it.
The RKBatchTool 1.3 and 1.5 doesn't recognize the tablet.
The only way I can see to fix this is doing the job in ADB command line, but the only way that I know to uninstall the Chainfire 3D driver is in Shell. Could anyone help me in this problem?
I made a small and simple recording showing the driver, RKBatchTool error and ADB errors. (please copy the following link to the browser's URL bar, I can't post direct links)
youtube.com/watch?v=4iQi5SkKGe4
Best regards and thank you in advance,
Ivan Santos.
Click to expand...
Click to collapse
Did you make a backup B4 installing Chainfire?
ken.okech.94 said:
Did you make a backup B4 installing Chainfire?
Click to expand...
Click to collapse
I didn't. But even I've made a backup, I can't connect the tablet to the computer with RKBatchTool and I can't install the Rockchip 3066 driver, only the ADB Android driver (which i can connect via adb).
Use ADB
IvanSantosPT said:
I didn't. But even I've made a backup, I can't connect the tablet to the computer with RKBatchTool and I can't install the Rockchip 3066 driver, only the ADB Android driver (which i can connect via adb).
Click to expand...
Click to collapse
Google a pre-made adb backup specifically for your tablet and restore it via adb. Or you can just use fastboot to flash a new ROM.
ken.okech.94 said:
Google a pre-made adb backup specifically for your tablet and restore it via adb. Or you can just use fastboot to flash a new ROM.
Click to expand...
Click to collapse
Did you read what I said?
I have the ADB drivers installed, i can access to almost everything in the ADB tool, except the "adb shell" command, even pushing up the mksh file to /system/bin.
The fastboot doesn't work, because the tablet turns off the screen, but appears in Device Manager an unknown driver, that I can't find the driver for it.
The RKBatchTool 1.3 and 1.5 doesn't recognize the tablet.
Click to expand...
Click to collapse
IvanSantosPT said:
Did you read what I said?
Click to expand...
Click to collapse
I think adb shell doesnt work because your tablet has not yet booted and will not be booted as long as it is in the current state.
Your only hope is RK Batch tool. Uninstall all current versions and the drivers you have in your computer and try reinstalling this and the drivers.
https://mega.co.nz/#!TIFwFCob!YniP23RpZH6hRj1Q-WSYvgQ4v28FUjU2qJ8b_4xLJXg
Your only hope!
ken.okech.94 said:
I think adb shell doesnt work because your tablet has not yet booted and will not be booted as long as it is in the current state.
Your only hope is RK Batch tool. Uninstall all current versions and the drivers you have in your computer and try reinstalling this and the drivers.
mega.co.nz/#!TIFwFCob!YniP23RpZH6hRj1Q-WSYvgQ4v28FUjU2qJ8b_4xLJXg
Your only hope!
Click to expand...
Click to collapse
Thank you, I reinstalled the driver and it worked. I installed the CWM 6.0.2.7 and all was working fine. Then I installed the CyanogenMod for RK3066 (cm3066.com) and the device doesn't boot, doesn't even shows the battery charger indicator and I can't mount or format anything in the CWM. I've lose the SD card, but I will borrow someone and try to reinstall the CWM, because I can't go to the RKBatchTool option.
Y u so Ungrateful?
IvanSantosPT said:
Thank you, I reinstalled the driver and it worked. I installed the CWM 6.0.2.7 and all was working fine. Then I installed the CyanogenMod for RK3066 (cm3066.com) and the device doesn't boot, doesn't even shows the battery charger indicator and I can't mount or format anything in the CWM. I've lose the SD card, but I will borrow someone and try to reinstall the CWM, because I can't go to the RKBatchTool option.
Click to expand...
Click to collapse
<<<<<<<<<<<<<<<<<<<<Hit thanks button if I helped , dude.
ken.okech.94 said:
<<<<<<<<<<<<<<<<<<<<Hit thanks button if I helped , dude.
Click to expand...
Click to collapse
No problema. But now I can't even reflash the CWM or the ROM, the tablet is soft bricked.
UPDATE: To access to the Downloading Mode, I had to click Vol+ plus Vol- when I connect the device to USB port. I am trying to flash with official firmware.
UPDATE 2: I've noticed that the ROM that I installed damaged the kernel, and now I need someone's boot partition dump.
UPDATE 3: I downloaded the oficial ROM from soft.aoicoo.com/soft/show.asp?id=285 and flashed the device. Then the device started! I installed the CWM 6.0.2.7 and then installed DarkwaterV2 CM ROM (not required). The tablet is working better than never with 10279 points scored in AnTuTu Benchmark v3.3! Thank you all!
Related
winxp sp3 sony tablet s when put in recovery mode for flashing the mtp driver
shows yellow (!).when i try to install driver manually it trys to start but comes
back with code 10.with tablet in normal mode winxp sees mtp & adb drivers.
the problem is only with recovery mode.tryed all i can think of and read all
solutions but driver still fails to start.so i can,t flash fw!. i really need help with
this one. please someone help i`ll give you a big thanks. i know i am not the
only one with this problem.i hope this is clear enough.
Same problem here:
Everything's fine in normal boot, but in recovery mode, I can't install the MPT driver. Win7pro. It tries to install, but ends up with a Code28 (something in the INF file is invalid, can't tell the english error message, because I have German Win7).
This seems to cause my problem flashing to R5a by AiO or the auto flasher by condi.
I get the exact error message on the tablet, as shown in post #72 in this thread:
[FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery
Trying since four nights...
At least I managed to flash and root to 4.0.3 R2a from the "unrootable" 3.2 R10 by flashing via recovery mode to Sony original ICS R2a (downloadable from sony) and then using the AIO 5.3 to root. Don't know why this way is not published here... Tried updating to 3.2.1 etc, nothing worked... the found the links to sony's fw and thought "WTF! Let's try ICS R2a, worst case is an also unrootable Tablet but with ICS". Worked, and was rootable then.
Just ignore the problem. I believe seeing the alerted MTP USB Device in Windows Device Manager when your tablet is in Recovery Mode is being cause by your tablet's borked Android System Recovery Revision 36 (i.e., Rev.36). This problem did not occur with earlier revisions of Android System Recovery. Normally, no MTP USB Device (or Sony Tablet S) should be displayed or even installed for Recovery Mode because a tablet in Recovery Mode cannot provide MTP functionality. Recovery Mode only requires Android Composite ADB Device be installed. Normal Mode, however, requires both Android Composite ADB Device (but only when the tablet's USB Debugging is turned on) and MTP USB Device, which Windows Device Manager renames and displays as Sony Tablet S.
You are basically right... it was ADB drivers, not MTP.
I tried all possible drivers from the list, also some "phone" devices. And YES!! Windows accepted one of them...
After that, I had no problem flashing my tablet to ICS R5a!!
please, could somebody who has writing permission in the dev forums, tell Condi, that the AiO 5.3 tools tells you to check this driver ONLY AFTER you are NOT stuck in "status7" error!!!!!
You do NOT get the message in the terminal box, IF you are stuck.
That would have saved me one or two nights trial and error...
But, after all, I have a nice working ICS R5a on my tablet S
I will post a how-to for other 3.2 kernel10
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
phc1234 said:
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
Click to expand...
Click to collapse
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
android phone dosent show in device manager
ThreeEyes said:
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
Click to expand...
Click to collapse
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
phc1234 said:
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
Click to expand...
Click to collapse
But by manually updating the driver and choosing manually, you can assign ANY driver to any device - it may not work or even do some damage to the system, but basically, it's your choice!
Take the device with the "!" and give it the right driver...
"CAT" above is right with rel5 and 5a that they changed the recovery rev to 36 and this rendered the
tablet s from loading any mtp driver or seeing the android phone entry in device manager so no way
to install adb driver.this has killed conis AIO tool flashing firmware and roms until someone breaks
the lockdown sony put in.
Hi, I'm new to this site..
So when I could not find stock recovery I tried this so called CMW recovery touch version, and as soon as I installed it my device doesn't boot anymore. it stuck at iBall logo and stuck there forever! I tried to connect it to Computer via USB. apparently, WinXP cant not find the device or any USB device for that matter. But somehow when I hold. and press Back key and Power button, the device LED is on(means somehow alive) with a blank screen and WinXP find ?USB Device!(?)
How to I restore my tablet! please help...
This tablet is Rebranded!
Info:
Model:iBall Slide i6012
RAM:1GB
INTERNAL MEMORY:8GB
SCREEN: 800×480 CAPACITIVE TOUCH
CPU:1.2gz Allwinner A10
Android Version :ICS 4.0.4
Please help me......
I've tried "use pin to restore " and "button combination " but not luck!
Before installing this,I install another WORKING(KIND OF) cwm modified. img.
You need a recovery specific to your device, provided you flashed it to the correct, i.e. recovery, partition.
thanks
bodh said:
You need a recovery specific to your device, provided you flashed it to the correct, i.e. recovery, partition.
Click to expand...
Click to collapse
The problem is that Window can not find my device. Sometimes it only appear as USB device and other times it doesn't recozniged at all. I tried updating ADB driver but that dont do any help...
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1 try these.
also, "A. Install the drivers
1) Do not install the Samsung drivers or the pdanet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
2) Download the drivers from here;
3) Install the drivers. This step is the only part of the entire process that is not easy to explain, and may cause users some issues, depending on what drivers they had installed previously, what OS they are using, etc. etc. Bourne-nolonger has put together a very detailed step-by-step on how to install them. If you don't know how to install them, have a look at his post here. Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). If you are using Windows 8, you will need to do this before installing the drivers."
from http://forum.xda-developers.com/showthread.php?t=1626895
I'll try it!
bodh said:
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1 try these.
also, "A. Install the drivers
1) Do not install the Samsung drivers or the pdanet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
2) Download the drivers from here;
3) Install the drivers. This step is the only part of the entire process that is not easy to explain, and may cause users some issues, depending on what drivers they had installed previously, what OS they are using, etc. etc. Bourne-nolonger has put together a very detailed step-by-step on how to install them. If you don't know how to install them, have a look at his post here. Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). If you are using Windows 8, you will need to do this before installing the drivers."
from http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
I'll try it....
USB is death!
hello again!,
I tried that and it does not work!
Computer can not even find my device.
When I plug in charger or USB cable,tab is light up and display iball logo and from there it stuck!
I mean it stuck forever!
What is APX mode?
Somehow when I press Menu and while still holding I pressed the power button simultaneously and my Computer Show "Unrecognized USB Device".
Please anyone help me. I dont even have the stock firmware to flash(if required) with!
Their Customer service is neglecting me and I'm really pisses!
Give me some light anyone
fastboot can not even open in my computer when I download and try to open! it said "can't find Winusbapi.dll"
while "winusbapi.dll" was in the same folder as the "fastboot.exe"!
I'm very new to this and it would be a great help if you can guide me to revive my only tablet!
After a little research, do you mean this recovery? [Not cwm at all] http://www.slatedroid.com/topic/35183-custom-recovery-for-c8a8m7/
Did you choose an option to flash it through partitions and storage menu? Did it allow you to back up your stock setup first (hopefully, if it is cwm-modeled)? If not, then I'm not sure I can help. Looks like your recovery is a recovery AND a kernel, packed into one [just leaned about this from a recent xda story]. I also found this: https://github.com/namko/midRecovery/downloads, with several other BETA versions. Maybe it would help you to google "iball slide". There is a stock 4.1.1 image on xda, which could also help. But overall, it looks like there is not much development for this device, and you should've researched the risks BEFORE tampering with your device!
p.s. I do not know what apx mode is. Also, is winusbapi.dll something that needs to be installed? Click it and see!
completely invisible to Computer.
Hi, can you show me the stock 4.1.1 image. I tried to find it but couldn't get it.
Please post a link here....
No, I did not flash with that modified recovery.
I'm. still amaze how a recovery.img can kill my tablet.
Im stuck in iBall logo. whenever I plug in tablet light up even if I switch it off before charging.
Window can only find my device as "Unknown USB Device ".
I updated ADB and still doesn't work.
I tried google and can not find anything other than piece by piece similarities.
all I want is to flash the stock recovery back!
I can not do it because my ADB is not recognizing my tablet!
I really appreciate your help though!
kcisrael said:
Window can only find my device as "Unknown USB Device ".
Click to expand...
Click to collapse
What ID "Unknown USB Device" in Device Manager?
I was wrong, it's an AOSP based rom; but it's a beta, and i will not recommend it, as it is probably quite far from stock. You didn't answer if that slate droid link is the recovery you took. That says it is not flashed, but rather externally booted.
This kind of recovery.img could kill a tablet in the following way: it looks as though these devices have both the kernel and the recovery together. [there's a recent xda article about a sony bootloader that addresses this.] If the kernel is bad, the device does not boot. Can you try a factory reset from your recovery's menu? So which recovery do you have, i.e. what does it say along the top?
can't see recovery menu
bodh said:
I was wrong, it's an AOSP based rom; but it's a beta, and i will not recommend it, as it is probably quite far from stock. You didn't answer if that slate droid link is the recovery you took. That says it is not flashed, but rather externally booted.
This kind of recovery.img could kill a tablet in the following way: it looks as though these devices have both the kernel and the recovery together. [there's a recent xda article about a sony bootloader that addresses this.] If the kernel is bad, the device does not boot. Can you try a factory reset from your recovery's menu? So which recovery do you have, i.e. what does it say along the top?
Click to expand...
Click to collapse
No, I did not flash with that recovery link you provided.
And I can not go beyond the "iBall" logo in the tab. So,no recovery menu. Also I tried all sort of Factory reset like "key" combination and "pinhole", none of them works!
can you help?
AllexBast said:
What ID "Unknown USB Device" in Device Manager?
Click to expand...
Click to collapse
hi,
ID:USB\VID_1F3A&PID_EFE8\5&1D3934BB&0&3
Need to remove the "Unknown USB Device" and install the driver again
No luck!
AllexBast said:
Need to remove the "Unknown USB Device" and install the driver again
Click to expand...
Click to collapse
Still the same!!!
kcisrael said:
Hi, I'm new to this site..
So when I could not find stock recovery I tried this so called CMW recovery touch version, and as soon as I installed it my device doesn't boot anymore. it stuck at iBall logo and stuck there forever! I tried to connect it to Computer via USB. apparently, WinXP cant not find the device or any USB device for that matter. But somehow when I hold. and press Back key and Power button, the device LED is on(means somehow alive) with a blank screen and WinXP find ?USB Device!(?)
How to I restore my tablet! please help...
This tablet is Rebranded!
Info:
Model:iBall Slide i6012
RAM:1GB
INTERNAL MEMORY:8GB
SCREEN: 800×480 CAPACITIVE TOUCH
CPU:1.2gz Allwinner A10
Android Version :ICS 4.0.4
Please help me......
I've tried "use pin to restore " and "button combination " but not luck!
Before installing this,I install another WORKING(KIND OF) cwm modified. img.
Click to expand...
Click to collapse
Download these USB debugging drivers...
http://www.mediafire.com/download/53vp6c6ka86rk3q/iBall_slide_Debugging_drivers.zip
and install them in your PC...
hope your PC will recognize your slide
bro how to hard reset using keys..??
kcisrael said:
hi, i'm new to this site..
So when i could not find stock recovery i tried this so called cmw recovery touch version, and as soon as i installed it my device doesn't boot anymore. It stuck at iball logo and stuck there forever! I tried to connect it to computer via usb. Apparently, winxp cant not find the device or any usb device for that matter. But somehow when i hold. And press back key and power button, the device led is on(means somehow alive) with a blank screen and winxp find ?usb device!(?)
how to i restore my tablet! Please help...
This tablet is rebranded!
Info:
Model:iball slide i6012
ram:1gb
internal memory:8gb
screen: 800×480 capacitive touch
cpu:1.2gz allwinner a10
android version :ics 4.0.4
please help me......
i've tried "use pin to restore " and "button combination " but not luck!
before installing this,i install another working(kind of) cwm modified. Img.
Click to expand...
Click to collapse
plz help me how to hard reset>>>
I have had my new Visture V97HD Retina display tablet for a week now and I am having few problems understanding what is happening with drivers/adb/fastboot and recovery. I managed to install the Win 8 RK3188 rockchip driver, but had to do it with USB debugging/disabled and driver signing disabled. Then I installed the rockchip update.Then I installed PDAnet 64bit and run a RK3188 root script and all seemed to have worked OK. Rootchecker now tells me the device is rooted. The trouble is I don't have any recovery. When I try to boot into recovery I get the little Android with red exclamation mark. Also when I run ADB cmds the device is not recognized. When USB debugging is enabled and I attach the device. I get message from the device to connect via USB, then another question asking me to press here for USB storage. When I accept and connect I can see the device in explorer but still not recognized in ADB. What is happening and what can I do to fix this?
Confused
Mossey said:
I have had my new Visture V97HD Retina display tablet for a week now and I am having few problems understanding what is happening with drivers/adb/fastboot and recovery. I managed to install the Win 8 RK3188 rockchip driver, but had to do it with USB debugging/disabled and driver signing disabled. Then I installed the rockchip update.Then I installed PDAnet 64bit and run a RK3188 root script and all seemed to have worked OK. Rootchecker now tells me the device is rooted. The trouble is I don't have any recovery. When I try to boot into recovery I get the little Android with red exclamation mark. Also when I run ADB cmds the device is not recognized. When USB debugging is enabled and I attach the device. I get message from the device to connect via USB, then another question asking me to press here for USB storage. When I accept and connect I can see the device in explorer but still not recognized in ADB. What is happening and what can I do to fix this?
Confused
Click to expand...
Click to collapse
I still really could use some help!
Mossey said:
I still really could use some help!
Click to expand...
Click to collapse
I've successfully rooted v97hd using how2 on vondroid.com. it worked for original FW and also for the latest from 05/05/13. But I need to get some image to flash. what did you want to flash ? I have the same issue with the bootloader...
I was trying to do this http://forum.xda-developers.com/showthread.php?t=2577826 and got up to replacing system.odex and everything crashed now it wont get past yellow load screen. I have safestrap but dont have more than one backup. Every time i run Adb come up with error:closed .I thought factory reset would fix but didnt now ive lost hope. HDX7 Help needed pls
and i tryed adb on multiple computer with no luck + different drivers. does show up in devices
Solved
that usual guy said:
and i tryed adb on multiple computer with no luck + different drivers. does show up in devices
Click to expand...
Click to collapse
Needed to input adb sideload rom.zip (Zip was also in file name but shouldn't be) and flashed to stock firm ware
Reflash?
Fixed
johnwaters said:
Reflash?
Click to expand...
Click to collapse
I fixed it by installing a new rom from adb
May i ask you a question?
How to connect adb?? i'm not connect adb...what is your os? win?or linux?
um.. please tell me the tutorial how to connect adb?
cjdfyd2 said:
How to connect adb?? i'm not connect adb...what is your os? win?or linux?
um.. please tell me the tutorial how to connect adb?[/QUOTE
I had safestrap so I put it in adb sideloader mode. And your device should be detected in device manager, if not install the right drivers. then go in cmd and navigate to adb file in platform tools from the package you should've downloaded. Then enter adb USB devices and it should show it connected. -windows xp
Click to expand...
Click to collapse
The titel says it all , and I need some help. I can still go in recovery but adb won't recongize my HTC, but I can still find it in fastboot. I formatted the sdcard, so I have nothing on there. Help would be much appreciated.
vsp33ddyv said:
The titel says it all , and I need some help. I can still go in recovery but adb won't recongize my HTC, but I can still find it in fastboot. I formatted the sdcard, so I have nothing on there. Help would be much appreciated.
Click to expand...
Click to collapse
Oh, trust me that's not your phone being bricked. You guys seriously need to know the correct vocabulary.
Bricking the phone: The phone's only use is to use it as a literal brick. It does not turn on, does not recover, does not charge, does not do anything and it can never be restored.
HOX+ can NOT be bricked unless you are S-Off'ed. Now that we got that out of the way,
you seem to understand that ADB is the solution here, that you need to sideload a rom, the question that you have is the adb does not recognize your phone, so follow these steps:
-Connect the phone using a different usb port, (basically thats the easiest thing), if its 2.0 then try 3.0 and vice versa.
-Restart your computer
-Restart your phone
-If you are on windows Vista and later, open start menu search for "cmd" then right click and run it as administrator, then you need to cd to your adb directory.
Code:
cd C:\Android\sdk\platform-tools
for example. then try adb devices.
Anyway hope you get it to work and have fun
Ghand0ur said:
Oh, trust me that's not your phone being bricked. You guys seriously need to know the correct vocabulary.
Bricking the phone: The phone's only use is to use it as a literal brick. It does not turn on, does not recover, does not charge, does not do anything and it can never be restored.
HOX+ can NOT be bricked unless you are S-Off'ed. Now that we got that out of the way,
you seem to understand that ADB is the solution here, that you need to sideload a rom, the question that you have is the adb does not recognize your phone, so follow these steps:
-Connect the phone using a different usb port, (basically thats the easiest thing), if its 2.0 then try 3.0 and vice versa.
-Restart your computer
-Restart your phone
-If you are on windows Vista and later, open start menu search for "cmd" then right click and run it as administrator, then you need to cd to your adb directory.
Code:
cd C:\Android\sdk\platform-tools
for example. then try adb devices.
Anyway hope you get it to work and have fun
Click to expand...
Click to collapse
The only thing I can do is use fastboot , thx for noticing that I know I need adb sideload If I look in devices on my PC I can see 'ONE' with a yellow triangle next to it ( so this means drivers) I downloaded my HTC drivers and I right clicked on the device and then update from PC , I go to the folder where I installed it and click on search and it says it can't find a driver for this device.
I also tried 4 different USB ports both 2.0 or 3.0 , no result. I also tried to install TWRP instead of cmw but on TWRP my touchscreen doesn't work while on cmw it does. So i went back and flashed my recovery to cmw again ( I tried version 2.6 - 2.7.0.1 , no result )
So my problem right now can be solved once my device can be recognized by my PC. (Have HTC maneger installed , also downloaded drivers formy phone , got fastboot and adb on my PC )
For anyone who knows thanks
vsp33ddyv said:
The only thing I can do is use fastboot , thx for noticing that I know I need adb sideload If I look in devices on my PC I can see 'ONE' with a yellow triangle next to it ( so this means drivers) I downloaded my HTC drivers and I right clicked on the device and then update from PC , I go to the folder where I installed it and click on search and it says it can't find a driver for this device.
I also tried 4 different USB ports both 2.0 or 3.0 , no result. I also tried to install TWRP instead of cmw but on TWRP my touchscreen doesn't work while on cmw it does. So i went back and flashed my recovery to cmw again ( I tried version 2.6 - 2.7.0.1 , no result )
So my problem right now can be solved once my device can be recognized by my PC. (Have HTC maneger installed , also downloaded drivers formy phone , got fastboot and adb on my PC )
For anyone who knows thanks
Click to expand...
Click to collapse
Hmmm. I would say in the device manager right click on the one and uninstall. Then in fastboot mode unplug and replug the device, let it install fastboot again and then try if adb can read it now.
Ghand0ur said:
Hmmm. I would say in the device manager right click on the one and uninstall. Then in fastboot mode unplug and replug the device, let it install fastboot again and then try if adb can read it now.
Click to expand...
Click to collapse
Still can't read it...
This has happened to my phone twice... fixed it the first time by using USB deview to remove all Android/HTC drivers, then reinstalled them with the HTC Sync installer. Couldn't get that to fix it last time though, so I tried another computer and it worked just fine. So my advice would be to find another computer and try it.
911jason said:
This has happened to my phone twice... fixed it the first time by using USB deview to remove all Android/HTC drivers, then reinstalled them with the HTC Sync installer. Couldn't get that to fix it last time though, so I tried another computer and it worked just fine. So my advice would be to find another computer and try it.
Click to expand...
Click to collapse
YES THIS IS WHAT WORKED ONLY I DID SOME OTHER STEPS TOO!!! Now I got adb running again and I can only push , I'll explain later in a full tutorial how to fix this now you guys can help me , I'm trying to download a cyanmod for my HTC because the stock is german and I can't download it , so can anyone upload the cyanmod endeavouru for me I keep getting error 502 bad gateway I almost fixed it !!!!! I need it badly !
OOkay so I thought I had figured it out , I uste TWRP to push files from PC to my Phone , then I installed cmw and tried to install the ROMS , but apperantly my roms were deleted. (I can't use TWRP because I need touch and the touch doesn't work , while in cmw the touch does work)
So if we can fix the TWRP touch I will know how to fix my problem !
I fixed the problem
I fixed the problem , thread how comming soon !
Here is my thread http://forum.xda-developers.com/showthread.php?p=52550145