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!
HOW TO UNROOT (ALMOST) ALL ANDROID DEVICES (SIMPLIFIED)
Firstly, in order to unroot your android device, you need:
1) An update available for your phone or an old nandroid backup that has a previous version of your phone android version
2) A nandroid backup done before you attempt the following steps below
Once the above conditions are met, you are ready to UNROOT your phone!
Before you read the procedure, read how it works
below and get a better picture:
HOW
Firstly, one known method of unrooting is to install an available system update. However, stock updates are signed with official keys and custom recoveries only accept updates signed with their custom keys.
So, to unroot, you need to have stock recovery installed. One way to get your phone`s stock recovery back is contained in the update zip.
The update zip is the key, literally. Look through it and you will find (usually in the system folder) a file called recovery.img, which will be used as your new stock recovery.
By flashing in the image into recovery, you can now install updates, keep your previous applications, enjoy being unrooted and updated.
There are other unroot options that tailor to specific android phones and versions, but this solution should work on all android phones.
Why unroot? Because sending in a rooted phone for repair will void your warranty. Also, by having a rooted phone, you run the risk of a rogue rooted application that does unwanted stuff to your phone.
PROCEDURE
Step 1) If you still have your original stock recovery that came with your phone, continue. Else search for my previous thread: "[RECOVERY] Reverting to original(STOCK) recovery" and follow the steps there. You can use the update file you used to revert to stock recovery here as well or vice versa
Step 2) Reboot you phone
Step 3) Check for system updates and download them
Step 4) Wait until phone reboots. All your applications and user settings will be retained.
Step 5a) Open up a terminal emulator on your phone and enter "su" (Check if unroot)
Step 5b) If you cant turn your phone on to check if unrooted, boot into recovery mode, open up adb enter:
Code:
adb shell
su
Step 6) If you get "permission denied" or something like that from step 5a/5b,
CONGRATULATIONS! YOUR PHONE HAS BEEN SUCCESSFULLY UNROOTED!
Step 7) If you don`t want to void your warranty, you should unistall applications that require root, especially Superuser
To date, I have rooted and unrooted my phone (Backflip) 3 times without any problems. In case your phone can`t be booted up, only to the bootloader or recovery, DO NOT WORRY! You can use the adb (android debug bridge) to flash in the stock recovery, push/pull the updates and reboot the phone into recovery mode or normal mode!!!
Useful ADB commands
Reboot Phone
Code:
adb shell
reboot
Reboot Phone into recovery mode
Code:
adb shell
reboot recovery
Flash a new recovery image temporarily (resets when rebooting)
Code:
adb shell
flash_image recovery /sdcard/recovery.img
Flash a new recovery image that does not reset when rebooting
Code:
adb shell
flash_image recovery /sdcard/recovery.img
exit
adb shell
cd system
su
mount -o rw,remount /dev/block/mtdblock1 /system
rm recovery.img
mount -o ro,remount /dev/block/mtdblock1 /system
exit
exit
Push file to sdcard
Code:
adb push file.blah /sdcard/file.blah
Push file to sdcard
Code:
adb pull /sdcard/file.blah file.blah
Here`s wishing you good luck and a belated happy new year!
Err.. Pretty cool info there but what if you don't meet above three requirements? I mean there are noobs like me who'd rather jump onto flashing while forgetting about nandroids etc. I guess there should be a one click unroot utility for all android devices like we have for rooting.
im really confused.
if the phone has been rooted (using fastboot oemunlock - yes) then how can we "unroot" this device? till today there has not been a way to do so.
but if what ur suggesting relocks the bootloader (removes the cross at bootup) then woohoo!
The main point
ok, i think you guys dont understand what my point on unrooting is...
What im trying to say is:
Updating your phone software with an original OTA update on the original rom the came with your phone will automatically reset root. However, custom roms and recoveries dont accept OTA updates, so you need to flash back your original recovery first, nevermind if you have a custom rom.
If you don`t meet the requirements, then i`m sorry, you`ll just have to wait for an available system update like me. However if you get one, be sure to come back here if you want to unroot.
Creating a one/two click-unroot application
Actually, you may be right. The unroot procedures can also be carried out by adb alone , not by user interaction. So a desktop application can be created that automates the process
1) Open adb shell
2) Enter su
3) Pull the update zip from the phone
4) Recursive/y search the zip for the file recovery.img
5) Run 'flash_image recovery recovery.img'
6) Run 'adb reboot' to reboot phone
7) Phone will install update on stock update when rebooting complete
8) When update installed, root will be removed and your phone will be updated as well!
We can send keystrokes to the adb for the adb shell.
siidheesh said:
Actually, you may be right. The unroot procedures can also be carried out by adb alone , not by user interaction. So a desktop application can be created that automates the process
1) Open adb shell
2) Enter su
3) Pull the update zip from the phone
4) Recursive/y search the zip for the file recovery.img
5) Run 'flash_image recovery recovery.img'
6) Run 'adb reboot' to reboot phone
7) Phone will install update on stock update when rebooting complete
8) When update installed, root will be removed and your phone will be updated as well!
We can send keystrokes to the adb for the adb shell.
Click to expand...
Click to collapse
Shouldn't be too hard, probably only a simple script would suffice I'll see what I can come up with (if I can do anything ). Supply the script with your required update zip to make it work in a different way (maybe, I'm not great with details)
Automated Script
Can someone please clarify that this would work (as an unroot script):
1. Opens ADB shell
2. Enters su
3. (User) Supply script with stock update.zip - in case it's not on phone (correct if this is unnecessary)
4. recovery.img extracted from update.zip
5. recovery.img flashed to phone via 'flash_image recovery recovery.img'
6. Reboots phone via 'adb reboot'
That installs stock recovery, but what if there was no OTA update to install for that particular device? That's the only problem I can see with such a script, so I'm hesitant to make it right now (besides, I don't have my Nexus with me at the moment, so I couldn't test it).
Dumb question but would flashing a stock update.zip from the stock recovery remove root? Or does it have to be OTA? Never having done it before I'm not sure.
Edit: If it did have to be OTA, maybe you could find the original update.zip (ie. no updates before it) and flash that, so there would be a higher chance of an OTA update?
Different definitions
Sorry people, when i mean ota update, i dont just over-the-air updates, i am referring to original updates for your original android system that came with your phone.
siidheesh said:
Sorry people, when i mean ota update, i dont just over-the-air updates, i am referring to original updates for your original android system that came with your phone.
Click to expand...
Click to collapse
So just to clarify, you could install any stock ROM for your device and it would remove root? Specifically if it was installed through stock recovery.
Thanks, hopefully I might be able to make some progress after this
not as easy as it seems
jonathongrigg said:
Can someone please clarify that this would work (as an unroot script):
1. Opens ADB shell
2. Enters su
3. (User) Supply script with stock update.zip - in case it's not on phone (correct if this is unnecessary)
4. recovery.img extracted from update.zip
5. recovery.img flashed to phone via 'flash_image recovery recovery.img'
6. Reboots phone via 'adb reboot'
That installs stock recovery, but what if there was no OTA update to install for that particular device? That's the only problem I can see with such a script, so I'm hesitant to make it right now (besides, I don't have my Nexus with me at the moment, so I couldn't test it).
Dumb question but would flashing a stock update.zip from the stock recovery remove root? Or does it have to be OTA? Never having done it before I'm not sure.
Edit: If it did have to be OTA, maybe you could find the original update.zip (ie. no updates before it) and flash that, so there would be a higher chance of an OTA update?
Click to expand...
Click to collapse
You cant make an unroot script that easily. Im halfway working on a .net application that does it on desktop.
Also, almost all great things come with a *catch*. In this case, you need to wait for an ota update to be available. Or if you took a nandroid backup some time back and updated your version, you can revert back to the old verison and update again.
siidheesh said:
You cant make an unroot script that easily. Im halfway working on a .net application that does it on desktop.
Also, almost all great things come with a *catch*. In this case, you need to wait for an ota update to be available. Or if you took a nandroid backup some time back and updated your version, you can revert back to the old verison and update again.
Click to expand...
Click to collapse
Oh well, I didn't realise I figured you could do it all from the command line, so a script of some kind might do. That said I wasn't entirely sure as I couldn't test the theory (no phone )
siidheesh said:
In this case, you need to wait for an ota update to be available. Or if you took a nandroid backup some time back and updated your version, you can revert back to the old verison and update again.
Click to expand...
Click to collapse
Another win for stock Android phones No waiting months for OTA updates! Well good luck on your .NET application, I only know Java and Python, so I can't really help you there, sorry.
dont know
my phone (Backflip) isnt a very popular phone and there`s only one rom for it. to date, i`be only tried unrooting via stock updating. Stock roms may work too, but im not sure...
adb shell
jonathongrigg said:
Oh well, I didn't realise I figured you could do it all from the command line, so a script of some kind might do. That said I wasn't entirely sure as I couldn't test the theory (no phone )
Click to expand...
Click to collapse
actually, i did mention that the unroot procedure can be done entirely from the adb shell, which is also in command line. im just making a program to enter those lines in automatically. normal batch scripts cant write to the adb shell as it is a separate shell in the command prompt...
What about doing a factory reset?
hi, would these unroot methods still work on the new updated highly secured samsung galaxy s2?
because i got the phone simlocked hoping to unlock it for t-mobile so rooted the phone but it was been unsuccessful at taking the sim lock off, so i wanted to make sure that this will still work on this phone.
Also after unroot i assume the yellow triangle will disappear, right?
oh yea thanks for replies and help in advance. Love the site
total noob here, I rooted my tab awhile bk, now needs warranty. I used 'superoneclick', but didnt backup anything first that i know of. U mention nandroid backup, update available for my phone, where do I get that, and how? Embarrassed I know nothing about these terms, trying to learn. Could u help me, please?
where can I find the recovery.img?
thanks
Does this work on all roots?
My nexus 7 (2013) just did the stuck on X during start up thing. I have a bunch of photos from my vacation on it that I would like not to lose.
I've been reading up on adb and so far have installed the SDK and toolkit. My PC recognizes that my nexus is attached when I put it into adb sideload mode.
But I'm too new to know where to go from there. There is a lot out there about using the sideloader to do various things but haven't found anything that would help me so far.
Can I somehow use an adb backup command if install a zip file with the proper commands?
Is there a way to reinstall the OS via adb sideload to get the nexus running again without wiping the internal storage?
There have been some methods mentioned that involve have USB debugging enabled or the bootloader unlocked.
But I don't have USB debugging enabled and my bootloader is locked. I couldn't find a way to enable USB debugging without the nexus being able to start up. It looks like unlocking the bootloader requires a factory reset.
You can try to use adb to get your pictures. It's located in %sdk_folder%/platform-tools.
Simply use this command to get your files
Code:
adb pull /sdcard/Pictures /destination_folder
You can also push files to your sdcard while using the push command. I would try this to push a backup to the sdcard.
Are you able to get in recovery mode (CWM etc.)?
lective renzak
Most adb commands gives me "error:closed"
adb devices gives <serial number> sideload
I can upload a zip file via sideload. I just uploaded a zip file with an empty text document. It gave me an error that the update package failed which was expected.
I know nothing about update packages.
Is there one I could install that would get the nexus working without wiping out my pictures?
I was able to install an OTA update over the adb sideloader. So at least something is working.
I was hoping that installing the update would fix things but the nexus still gets stuck on X when starting up.
I'm wondering if I can insert something into the update installer script to do a backup or pull....
There is an install-recovery.sh script that I could potentially edit and then back up.
I there a command I could put into it that would do something equivalent to an adb pull or backup?
If anyone could give me a place to start, I'd really appreciate it.
I am in the same situation as you I have found nothing and only your posts on other forums!
If you have the stock configuration with usb debugging off and the bootloader locked, you're stuck. At least I couldn't figure out anything after many hours and weeks of asking. Had to bite the bullet and do a wipe. I rooted it when I did the wipe so I could try various recovery tools.
I tried dr fone and hexamob recovery and some other ones but no luck.
The nexus toolkit helped me out a bunch to try out adb commands and install a rooted system.
Sorry I don't have better news.
For backup services, I think shutterfly gives you unlimited photo only backups. For others you can do a combination of google drive, dropbox, amazon, etc. Amazon has some special thing for music I believe.
do u have the link for OTA zip file
AM struck at the same point with my Samsung note 3 . i need the link for ota update so that i can update my OS using ADB sideload . i tried downloading a zip file from sammobile but its gives me an error
E: footer is wrong
E: signature verification failed
i don't know what else i can do .
i tried DR fone i shows my pictures but never completes the backup process and shuts down.
plz help guys
What's your problem with the note 3? Solution likely different than my nexus issue. The Samsung phones do have a power button issue. Either doesn't work or gets stuck in the pressed position so when you try to start it continues to restart. If that's the case try fiddling around with power button. I find it helpful to pull the phone apart so I can get at the actual button.
i checked the power button is fine because it say up in recovery mode but keeps restarting in safe mode or normal mode. i need to either backup my data on the device using the recovery mode or update my device so that i can fix the corrupted OS. but when i try to do a OTA update using adb sideload and a zip file that i downloaded from sammobile it gives me this error :
E: footer is wrong
E: signature verification failed
. or just help me to backup my pictures using the recovery so that i can just do a factory reset any help would be appreciated. Thanks
Haha, got the same problems. But I do have USB Debugging on - does not help anything. Crazy, if you consider that files are there but you have to delete them in order to correct the stubbornness of the OEMs....
Hello experts!
Please see the steps I took, and help me figure this one out:
1. Installed MoboRobo on my PC
2. Connected the TV box, and got it recognized
3. Closed MoboRobo
4. Launched TPSarky.bat and followed instructions
5. *At this stage I might have pressed the space key to reboot too early, for one of the three reboots
6. TPSarky completed its work (meaning the UID=0 GID=0, and SuperSU was pushed)
7. Device booted, SuperSU was there, but upon launching, it said there isn't an SU binary installed, and SuperSU can't install it
I tried several advices from different forums:
A. Pushing a different SU with another Superuser app, or different versions of the SU management apps
B. Pushing the SU to /system/bin and also /system/xbin
C. Using Fastboot to install a custom recovery (as I can't do it via the device itself) to update the SU with a flashable ZIP, but Fastboot didn't recognize the device (ADB does recognize it)
D. Using RK Batch tool / Android tool to install the custom recovery, but it said "Load firmware failed", with no matter how many different recovery *.img files I tried (CWM or TWRP)
So now I'm kind of stuck in a situation, where ADB on my pc confirms the device is rooted (UID=0 , GID=0), but the device itself behaves like it's not.
Any advice per how to handle this? Maybe there's a way to unroot by going back to factory settings, and run TPSarky from scratch? Maybe a step I'm missing to complete the root on the device?
Please please please advise, this is killing me...