Kyros MID-7015 and 7005 Ultimate Guide Discussion Thread

[gdsims231]

I have been working on this all day. I am frustrated and stuck. Using terminal emulator and soft keypad when I type reboot recovery, I get reboot: Operation not permitted What gives? please advise

 

[gdsims231]

My soft keyboard was covering up accept as superuser. Worked like a champ.. On to the next issue......

 

[gdsims231]

I am at the same step pheebs. Once I got throught he recovery and reboot I have no clockwork (or dont know where to find it). I typed the line in listed above and bet file not found. Ran root again, typed the line in emmulater again....same result...!!!!AARRGGGHHH

 

[sable]

When I am in command prompt and I go to cd/android-sdk-windows/tools "Enter". When I type adb shell it tells me that its not a recognizable internal or external command.

Please help

i was using the same command :
cd/android-sdk-windows/tools and the same thing :
its not recognizable internal or external command
so i google and found this:
cd C:\
cd android-sdk-windows
cd platform-tools
Type: adb shell and press enter.
Type: su and press enter.
Type: flash_image recovery /sdcard/recovery.img and press enter.
Press and hold the CTRL button, then press C.
Type: adb reboot recovery and press enter.

for me this worked

 

[Trauma]

I am having issues at installing the USB drivers. I go to "available packages" and check the "google addons" and it responds with this
"Failed to fetch URL http://innovator.samsungmobile.com/android/repository/repository.xml/addon.xml, reason: Server returned HTTP response code: 503 for URL: http://innovator.samsungmobile.com/android/repository/repository.xml/addon.xml"

is there anyway that someone can post an alternate download link?

 

[Legend777]

I'm getting a files needed screen and this is what is says

The file 'WinUSBCoInstaller.dll' on Android WinUsb installation disk is needed.

any help would be great

 

[padrict]

i have tried both methods to make this work but cannot. I have done everything I was supposed to do and have tried to boot recovery using terminal emulator and SDK cmd. I updated the firmware from Coby before starting the process - so according to all of the forums, it should be a snap, correct?

When I boot to recovery with both methods, the recovery.img is not available, only the update.zip from Coby.

Any help would be appreciated

 

[padrict]

i did, but i got the prompt message after i type: mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
it shown mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak file not found
do i missing something?

I did this also and ended up with the result. Any ideas?

 

[robinsonmac]

It took me a week but I finally got it to work after re-rooting with z4root v. 1.3.0. Then put recovery.img & the market zip file on the root level of the sd card, meaning not in any folders. Start the virtual terminal app & typed su, superuser then asks to allow, now this is very important, you have to clear the keyboard so you can push the allow button that the keyboard covers. once you push allow the # appears and you can continue.

 

[padrict]

It took me a week but I finally got it to work after re-rooting with z4root v. 1.3.0. Then put recovery.img & the market zip file on the root level of the sd card, meaning not in any folders. Start the virtual terminal app & typed su, superuser then asks to allow, now this is very important, you have to clear the keyboard so you can push the allow button that the keyboard covers. once you push allow the # appears and you can continue.

did the same exact thing. Still not able to boot to recovery image.

 

[reber3522]

Hey I got my Kyros yesterday, and I have been having a problem trying to get into the AppsLib. I am connected to Wi-Fi (have already checked that), but when I try to go an register to get a AppsLib account the website keeps saying that it is under construction. I have sent the developers an email asking when this is going to be fixed with no response. I am trying to root this thing, and Im trying to see if anyone else is having the same problems. Let me know what you think, or possibly another way that I can get the file manager and all the things that I need to do this.

 

[Vernon17]

i have the same issue.. i have not been able to get into the appslib all day. i was able to do it last week.

 

[rambg]

Someone please answer this, I also have the 7005 and want to root it. I just dont want to follow these instructions and brick my tablet.

Yes. It works but needs to download the right ClockRevoeryMod file. Check my previous post on page 1. I have rooted on my 7005 model.

 

[rambg]

Here is the link. Some how I copied my local drive. USB INF

For quick, here is the content of USB.INF. You can edit and copy to your file using notepad.



;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 08/11/2009,2.0.0010.00002
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat

;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg

[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1

[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64

[Google.NTx86]
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED&MI_01
; Android Eclair
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF

; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01

[Google.NTamd64]
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED&MI_01
; Android Eclair
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01

[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT

[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall

[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys

[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install

[WinUSB_Install]
KmdfLibraryVersion = 1.7

[USB_Install.HW]
AddReg = Dev_AddReg

[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"

[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles

[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01007.dll,WdfCoInstaller","WinUSBCoInstaller.dll"

[CoInstallers_CopyFiles]
WinUSBCoInstaller.dll
WdfCoInstaller01007.dll

[DestinationDirs]
CoInstallers_CopyFiles=11

[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64

[SourceDisksFiles.x86]
WinUSBCoInstaller.dll = 1
WdfCoInstaller01007.dll = 1

[SourceDisksFiles.amd64]
WinUSBCoInstaller.dll = 2
WdfCoInstaller01007.dll = 2

[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"

 

[reber3522]

rambg, this is not making sense, how is this going to get me the file manager that I need to start the rooting process? what do i need to do with the file you posted?