Database Info

Coby Kyros Internet Tablet MID7005-4G

HSN Launches Coby Kyros Internet Tablet 7" Android OS 2.1, 800MHz with 1080p HDMI review by me (note just click on the image to get to the review)
Coby Kyros Internet Tablet MID7005-4G Work-in-Progress Review by me
(note just click on the image to get to the review)

hi
hi where did you buy this ive been looking for a while?

I got a 7105-4g at k-mart yesterday.

Hey, I have a Kyros MID 7005-4G too. Unfortunately, it's pretty screwed at the moment. I'm looking for a recovery image for the device. If anyone can get me a recovery image of one of these, I'd be very grateful. I've tried a recovery image MID 7015, but they don't seem to be similar enough to work. Anyone?
Edit: On second thought, the Framework.jar file from an MID 7005-4G would help too.

Market
Yea, I just bought the MID7005 and it's cool. The resistant touchscreen is a little difficult at times. I really want googles market on it though. Id love to know how? Anyone?

clockworkmod/cyanogenmod/market on 7005
If you're interested in modding your 7005, I bought a used one on ebay. It was locked and the password lost by the previous owner when I got it, and it seems like it's been dropped because the charger is pretty intermittent. I don't think my battery is charging...
Anyway, if you want google market on it you will need to root your device and install a custom recovery.
What you will need:
SD card 1gb <
computer with the Android SDK (you need to use the ADB)
z4root
dump-recovery-signed.zip
clockworkmod recovery for the X5A-G
Cyanogenmod 7 for X5A-G
GAPPS (Google Apps) flashable zip
NOTES
***if you're very brave you can try using terminal emulator, but I don't recommend it. This tablet doesn't have a lot of power and crashing or freezing at any time during this process will almost definitely brick it. Just use the ADB and don't take the risk!***
I can confirm that both Clockworkmod Recovery and the Cyanogenmod 7 ROM for the X5A-G work on Kyros 7005.
1. install z4root and permanenty root. reboot
2. link removed at owner's request
you can get into the recovery by either holding home and power at bootup, or by enabling USB debugging on the tablet and then issuing the command
Code:
adb reboot recovery
Once you are in the recovery, select update from .zip file. This will trick your tablet into thinking it is preforming a firmware update, when in fact it is running a script that is backing up the recovery to your SD card.
3. download the x5a-g clockworkmod recovery .zip. Renaming it as 'update.zip' and attempting to flash using stock recovery does not work. You will have to do this manually, either via the adb or terminal emulator. I strongly suggest using the adb.
4. extract the clockwork mod recovery .zip file and find the recovery.img file. Copy recovery.img to the root of your sd card (in other words just drag and drop the recovery.img into the sd card)
5. obtain a root shell. If you don't know what that means you REALLY should not continue with this tutorial!!! open up a terminal/cmd prompt and start the adb.
Code:
adb shell
Code:
su
The prompt should now change to # indicating that you have gained root access. a prompt screen may show up on your tablet asking you to allow "unknown" root access. Click allow and proceed to the next step.
6. Flash the recovery.img from the root of your SD card
Code:
flash_image recovery /sdcard/recover.img
* I think this should go without saying, but you do have to insert the sd card into tablet and allowing android to mount it...
7. reboot into your new recovery
8. make a backup of your system. This is a precautionary measure to ensure that you will have at the very least a working system to boot back into. Reboot.
9. before you flash the cyanogenmod rom, you will have to do a factory reset and format /system from recovery. Once you've done this, you can proceed to flashing Cyanogenmod 7 rom. After the flash completes, reboot the tablet. Don't be alarmed or think that you've bricked your device. The first boot takes a LONG time. After you boot up for the first time you should be prompted to calibrate the screen. if the tablet doesn't automatically prompt you to calibrate the screen, fire the adb shell back up and enter the command
Code:
am start -a android.intent.action.MAIN -n org.zeroxlab.util.tscal/.TSCalibration
** it has been my experience that after first calibration the screen will not operate properly until after a reboot. Don't be alarmed! Just reboot using the command
Code:
adb reboot
since you probably won't be able to get the tablet to do so from the screen/buttons.
10. Once you have booted back into your tablet which should take considerably less time than the first boot after flashing, you will now be looking at the Cyanogenmod 7 desktop for the first time! Now you need to gain access to the google market. reboot into recovery, which can easily be done now from the shutdown menu.
11. flash the gapps .zip file and reboot
12. Your tablet will go through the "New Phone Setup" process. you will be prompted to set up a bunch of things, but you can skip past a lot of it. once you get to the desktop, connect to your wifi, open the market and off you go!

[Q] How bad did I brick my Kyros 7005??

Okay, where to start.. I think I have bricked my phone pretty good.
Here is the approximate list of things that happened.
I wanted to try to update to froyo, so I downloaded z4root, worked beautifully
Followed all the directions to install clockwork mod (including reading far enough ahead to find out the one in the directions was for the 7015, but gave the link for the 7005 version later) - Worked like a charm
BACKED UP SYSTEM as instructed
Then here is where things went south. I attempted to install the Cyanogen Mod froyo based. I followed the directions, including backing up softmac and wpa_supplicant files. And it would not start up. I could get it into recovery mode but not to start fully. I tried doing the restore, it couldn't mount the SD Card where the backup was. Being knowledgeable enough to dangerous in Linux, I used ADB Shell and tried various things to try to find out where the SD Card or recovery image failed. I had also been trying to locate FWDN as I saw people had done fixes with that, but I couldn't get it to load in FWDN "Mode". I figured if I could replace the recovery program on there that doesn't work with the one that does, it should in theory allow me to reboot into the correct recovery mode and let me pull the files from my SD Card. After about 15 minutes of shuffling around, I ended up mounting the \system folder where I found a file called recovery. Looked to be the right size. So I made a modified batch file that would instruct it to load from that folder.
After that mistake, all of the sudden, the vtc driver that I had installed did see the unit. I was like Joy! Joy! I fired up fwdn but since I didn't have the original files that it "liked" I used an lk.rom, but I think it wasn't from an X5A but from a lonpad. Now I don't even get COBY on the screen.
But wait, I'm even more dangerous. I got the hardware ID that it's currently using on the USB bus, edited first the vtc ini file to see if I can reload a different rom. It detects it, but FWDN gives me "bad boot" error or something like that. But I'm a trooper, if I'm gonna kill it, I'm gonna kill it good. I change the SDK/ADB driver to recognize the device. And it seems to recognize it. Then I went to try "fastboot flash recovery recovery.x5ag.img " which I had NEVER been able get the unit into fastboot mode, and it goes through and does it. Then I do a fastboot reboot to see if I can get it to come up in recovery mode, but I can't.
Then the final bright idea comes up on me.. Hey, I have the backup from SD card, what if I zip it up, call it update.zip, and do a fastboot update?
Now ADB can make some kind of connection to it, but when I try to shell I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
ADB State always reports device or unknown never bootloader
ADB remount comes back with remount failed: Invalid argument
ADB push into the / or /system folders (in an attempt to push a copy of sh there) fails saying read only file system
ADB push to /sys comes back with failed to copy: No such file or directory
So, that's where I am.. I think I really really REALLY bricked this thing... although the fact that I can still ADB to it leaves some shimmer of hope.
Thanks,
Joe

can u get into the boot loader at all? If so you are not Bricked you will just need to reinstall the entire system using fast boot. You may be able to restore the default OS using an update.zip file. It may be named something different for your device. All you do with that is place it on the root of the SD card and when the bootloader boots it finds the file and flashes the phone.

I can't get fastboot to recognize the device, it goes right to the ADB bridge. Where I can run some limited ADB commands that are recognized.. If I could get it to start up in fastboot mode, that would likely solve the issue, provided I can get the correct working update.zip file, rather than me trying to fudge one from the clockworkmod backup.

do you have any hardware buttons on device? turning on with volume up or down (or back) gives you differing USB ID's to device manager - obviously you want fastboot mode. (use device manager on ADB Bridge (Details) to get your ID - i think its DEED for fastboot and D00D for fwdn)
otherwise... you can force boot a new bootrom. It's what I did on my telechips device. Find tcboot.rom - put it in the same directory as fwdn
1. Open your device
2. Unsolder your battery + terminal
3. While turning on the device, place a short - screwdriver/pin etc - across pins 7/8 of the NAND chip (for 5 seconds)
4. FWDN should bring up a message about flashing bootrom
5. Reboot (and resolder battery cable)
Note: this obviously is pretty hardcore - but i went from brick, to black screen brick, to full restore via this method.

[ADB] Trying to backup - Birck? Hope not

Hi! I was trying to backup my Orange Monte Carlo following a Portuguese tutorial but I'm stuck in the middle and I've got no help! Hope you can provide some! These are the steps I followed (translated)
1 - Install ADB Made Easy;
2 - Open cmd;
3 - Activate cellphone debug mode;
4 - Connect via usb (without mass storage) and install drivers if request [it was requested and i installed];
5 - Run adb devices, it should show your device [it did];
6 - Run adb reboot bootloader, your cellphone will boot in Fastboot, wich is an Android image without menus [correct until here];
7 - Run fastboot devices, your device yor a question mark(?) should show up (advance to next step), else you miss drivers [step not completed];
cmd says 'fastboot' is not recognized as a command. Now my phone is stuck connected to the computer with an adriod pick and I have no clue on what to do next!

Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked

shanman-2 said:
Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked
Click to expand...
Click to collapse
Thank you! Do you have any idea why the last command doesn't work? I believe it has something to do with file location... I'm trying to backup my Monte Carlo. Next steps were to "fastboot boot recovery.img" and then backup.

It should be in the platform-tools directory of the android-sdk. Verify that it's there...if so cd to that directory and it should work

I already fixed it for myself, thanks! Now I can't seem to be able to install clockwork!
Doing <<fastboot boot "C:\Users\R&J\Downloads\recovery.img">> reboots the device but doesn't enter recovery.
Doing <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> , <<fastboot reboot>> and <<adb wait-for-device reboot recovery>> results the phone entering android's default recovery (no acess to backup feature).
Any way to help? Thank you!

The first command <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> is trying to write the recovery.img you downloaded to a recovery partition on your device. It may not be overwriting the original recovery.
try changing permissions by doing
adb shell
su
chmod 777 /recovery
then try to flash again

Lol it seems like I have been luck enough to solve my own problems, I have sucessfully installed ClockworkMod Recovery 4.0.1.4 unofficial MoDaCo Edition using a bat file . Now I can't seem to find a way to flash recovery back to stock. I though this was an option inside the modded recovery. Any tips? Thanks again!
EDIT: I have the stock recovery file . God... this tutorials I'm folowing aren't that noob friendly...

[Q] Velocity CRUZ T103 (PT701) bricked

Oh I am hoping someone here can help me out here. I just got this tablet, and tried to do the Froyo update, only to find out (too late) that this model is different and not up-gradable to the 2.2. After screwing around a bit with it, not sure what happened, but now the entire system is gone.
It boots to the Cruz logo, and sits there. ADB recognizes it, but I have no shell access, and when I do a ADB ls /system it lists only 2 files, with random numbers.
ADB remount - FAILS
ADB reboot fastboot - FAILS (just reboots it)
ADB reboot recovery - gets to recovery (in ADB devices) but tablet is blank, but no sh access
Vol + & power do nothing.
Vol - & power do nothing
While attached to my PC (Win7-64) and hit the reset and Vol -, it shows up as JZ4760 USB Boot, but Windows REFUSES to let me install any drivers for it. (Got the USBToolKit, but even after turning off driver signing, it still says they're not signed and refuses to load them)
I got the 2.0 firmware (default) so now what I need it a way to push the img files to the tab (hopefully)
Any ideas, or is this thing really a neat little brick now?
Thanks

No one?? Come on guys...I've been on this site for a long time, and have seen some of you pull out a brick and make a phone out of it again. LOL
I'm thinking if I can just get fastboot to load somehow on the tablet, I could issue commands from my PC to "push" the image files back over.
Question is: how do I get fastboot to get onto the tablet to load into???

I would like a copy of your firmware if still available for the cruz of course impossible to find as site is no longer hosted

[Q] can't use adb shell in recovery mode

I have a china tablet named Quest.I have accidentally repeated pattern lock more than 5 times.Now i am also forgotten the email address.So for hard resetting my tablet i simply booted my tablet into recovery mode.But it shows an android bot lying with red exclamation.After a spending hours i found a shortcut i.e,vol + and power to access recovery menu.But my tablet does'nt go to recovery menu even when i am pressed the keys.So i simply connected my tablet to my pc via usb and installed drivers. In adb command prompt i typed adb devices. Now my tablet is listed as 20110301 recovery. I can simply use only adb pull and push and reboot commands. But i cant access adb shell to unlock my tablet.
It simply says - exec '/system/bin/sh' failed: No such file or directory (2) -
WHAT TO DO???????????? pLz HELP ME!!!